[b3hr4d]

What

icp deploy -e production upgrades B3Note's mainnet canisters only on the machine that first deployed them. .gitignore left out all of .icp/, where icp-cli records each environment's canister ids, so from any other clone the same command finds no ids and creates new canisters. So does -e ic, icp-cli's built-in mainnet environment, which has none of B3Note's ids anywhere.

A new frontend is a new origin, so Internet Identity gives every user a new principal, and note.b3pay.net still points at the old canister.

Changes

• .icp/data/mappings/production.ids.json: backend xeka7-ryaaa-aaaal-qb57a-cai, frontend 4lidq-zqaaa-aaaap-abkbq-cai. Written by icp canister link (icp-cli 1.6.0), so it is exactly what icp-cli writes.
• .gitignore: ignore only .icp/cache/ (local network state), as icp-cli's docs advise and b3pay-hub does.
• --no-create in the README's "Deploying to mainnet", icp.yaml's header comment and pnpm deploy:production, so a missing id stops the deploy instead of creating a canister. The README says why not to use -e ic.
• frontend/tests/production.test.ts: the recorded ids must equal the ones origins.ts signs in for and calls.
• Left as is: scripts/migrate-mainnet.sh still links both ids with --force before it reinstalls; with the file committed, that rewrites the same ids.

Evidence

• Fact: on 2026-10-27, icp deploy frontend -e ic on main bc3d6b5 printed "Creating canisters: [frontend] ✘ failed to create canister: Insufficient cycles. Requested: 2000000000000 cycles, available balance: 1_481_753_760_859 cycles". With more than 2 T cycles on the deploying identity, it would have created a new frontend.
• Fact (icp-cli 1.6.0, run on this branch): icp environment list prints ic, production and local. icp deploy --help lists --no-create: "If any canisters do not exist, error instead of creating them". icp canister link writes .icp/data/mappings/<env>.ids.json.
• Fact (icp-cli's docs at v1.6.0): docs/concepts/project-model.md says to gitignore .icp/cache/ and to consider tracking .icp/data/, and docs/migration/from-dfx.md says .icp/data/ "should be committed to version control".
• Fact (checked 2026-10-27): the live frontend's ic_env cookie lists PUBLIC_CANISTER_ID:backend=xeka7-ryaaa-aaaal-qb57a-cai and PUBLIC_CANISTER_ID:frontend=4lidq-zqaaa-aaaap-abkbq-cai, the ids recorded here.
• Fact: in a scratch repo, git pull of this kind of change into a clone that already had the (until now ignored) file succeeded and left the committed copy in place.
• pnpm format:check, pnpm typecheck and pnpm test (61 tests) pass. Four faults each failed the new test and were reverted: a wrong frontend id, a renamed canister, the file missing, and a different backend id in origins.ts.
• Not run: any deploy. Nothing here touches mainnet.

---

Generated by Claude Code