chore(nightly): bump @aztec/* to 5.3.0-nightly.20260918

[AztecBot]

Nightly bump of @aztec/*, .aztecrc and the Nargo.toml pins from 5.3.0-nightly.20260827 to 5.3.0-nightly.20260918.

Healthcheck run: https://github.com/AztecProtocol/aztec-packages/actions/runs/35388323568 (tag v5.3.0-nightly.20260918, next @ a2db7b7)

Local verification — all green

step	result
node scripts/update.js	13 files repinned, yarn install clean
yarn workspace @aztec-kit/contracts-aztec build	compile + codegen clean, 4 artifacts
yarn format:fix	no changes
yarn build	7/7 tasks
yarn test	11/11 tasks, e2e 10 passed (8.9m)

No migration fixes were needed — the bump is a pure repin.

⚠️ CI will fail at "Install Aztec toolchain (public)" — upstream blocker

.github/actions/setup installs the CLI from

https://install.aztec.network/${VERSION}/install

and that object does not exist for any nightly after 5.3.0-nightly.20260909. Probed just now on both the public host and its origin (install.aztec-labs.com):

nightly	installer asset	npm package
5.3.0-nightly.20260909	200	published
5.3.0-nightly.20260910 … 20260918	404	published

The nightly and v5-nightly aliases on install.aztec-labs.com/aliases/ both still resolve to 5.3.0-nightly.20260909, so the toolchain-side release pipeline has not published anything for eight days while npm has kept publishing daily. The per-version versions manifest 404s for the same range.

This is not specific to this PR or to the container — CI hits the identical URL, so the build, integration and e2e jobs will all fail at the setup step until upstream republishes the install assets.

To get local signal anyway, the toolchain was assembled by hand: the last published per-version installer (20260909) is fully generic apart from a hardcoded VERSION= and the versions manifest it fetches, so it was re-pointed at 5.3.0-nightly.20260918 with the 20260909 manifest (noir v1.0.0-beta.25, foundry 1.4.1, node 24.12.0) supplied locally. That installs @aztec/aztec@5.3.0-nightly.20260918 from npm and the matching native tools; aztec --version reports 5.3.0-nightly.20260918. Every result in the table above comes from that toolchain.

Caveat on that workaround: the noir/foundry pins are 20260909's, because the real 20260918 manifest was never published. Contract compilation and the full e2e suite pass against them, so they look correct, but they are inferred rather than authoritative.

Recommended handling: fix the install-asset publishing upstream, then re-run this PR's CI unchanged. The repin itself needs no further work.

---

Created by claudebox · group: aztec-kit-nightly · Slack thread