fix: route @aztec/viem to npm in docs examples + verdaccio allow_offline

[AztecBot]

Summary

Two small, related fixes for @aztec/* resolution in docs example builds and the aztec-up packaging:

1. docs/examples/ts/lib.sh — Add an AZTEC_NPM_EXCEPTIONS list at the top, so bare @aztec/viem in a config.yaml is routed to NPM_DEPS (proxied from npm) instead of being auto-linked to a non-existent yarn-project/viem.
2. aztec-up/bootstrap.sh — Bring in publish: allow_offline: true (and its comment) from cb/dd69e1f0bb2f (f66631b8c5). Prevents the local verdaccio from 503-ing fake-publishes when the npmjs uplink is briefly unreachable.

Why @aztec/viem needs an exception

parse_dependencies() treats every bare @aztec/* entry as a local yarn-project package and resolves it to link:.../yarn-project/<name>. @aztec/viem is a third-party fork on npm — there's no yarn-project/viem, so the auto-link blows up with "Link target does not exist". Existing configs work around this by spelling it npm:@aztec/viem@2.38.2; the exception list makes the bare form safe too.

Scan for other packages not published locally

Cross-checked everything used as @aztec/* against yarn-project/* and npm:

• @aztec/viem — the only one that needs the new exception (third-party, lives on npm, no local source)
• @aztec/bb.js, @aztec/noir-* — not in yarn-project/, but already handled via the explicit link:pkg:path form in configs (barretenberg/ts, noir/packages/*)
• Everything else is a workspace package in yarn-project/

So just @aztec/viem for now.

Not changed (intentionally)

Existing config.yaml files that say npm:@aztec/viem@2.38.2 are left alone — the npm: form still works, and it keeps the explicit version pin (2.38.2). The new exception is a safety net for the bare form, not a migration target.

Full analysis + verification: https://gist.github.com/AztecBot/fcbb5ff446d16891e758bcba38632ef3

ClaudeBox log: https://claudebox.work/s/b06b3be6cb06f86f?run=1