feat(arc-adapter): Arc profiles, money, config, and readiness probe (B01 core)

[selezenart]

Summary

Implements the core of B01 — SDK and Arc network compatibility for the Coder B
lane as a standalone package, packages/arc-adapter.

It pins the toolchain, encodes the Arc deployment profiles, defines the
settlement-config-v1 variable surface, and adds a fail-closed readiness probe
and a sanitized redaction boundary. The package installs, lints, typechecks,
tests, and builds on its own, with no root workspace composition and no
credential, so the packet closes independently as the lane's independence model
requires.

This is a partial B01. See "Anything a reviewer should know" below.

Scope and acceptance criteria

• The change is limited to the stated milestone or issue.
• Acceptance criteria are listed and satisfied.
• No unrelated cleanup is included.

Acceptance criteria addressed, per milestones/coder-b/B01-sdk-network-compatibility.md:

• B01.1 version compatibility matrix — Node, TypeScript, viem, Vitest, and
  ESLint tested together in an isolated package. Rejected combination recorded
  below.
• B01.2 Arc deployment profiles — testnet constants pinned; mainnet profile
  present but valueless; settlement amounts separated from display formatting;
  no silent network, token, or precision override.
• B01.4 configuration schema — every variable classified public / secret /
  optional / human-only, with placeholder-only example rendering.
• B01.5 readiness probe library — chain ID and token bytecode assertions,
  identity-format validation that prints no credential, and a hard split
  between "unavailable" and "identity mismatch".
• B01.6 fixture capture boundary — deny-by-default redaction plus an
  assertion helper usable as a test guard on committed fixtures.

Not in this PR: B01.3 (Memo and policy compatibility spike) and the
testkit-settlement fixture package.

Product and security invariants

• Tenant isolation remains fail-closed.
• Sponsor authorization, auditability, and daily caps remain enforced where applicable.
• Recipients cannot modify sponsor controls or access sponsor-only data.
• No secret, token, production identifier, or personal data is committed or pasted into review prompts.
• Any non-applicable invariant is explained below.

Invariant notes:

No durable state, no domain table, no migration, and no transaction submission
is touched, so the tenant-isolation and sponsor-control rows are not applicable
to this diff. The invariants this change does carry:

• Money is never floating point. Values are canonical integer strings and
  bigint. There is no number arithmetic on a monetary value and no parser
  from number. Comparison against the spending cap is bigint, so an amount
  above the cap cannot slip through by float rounding.
• Amounts are rejected, not normalized. "01", "1.0", "+1", "1e6"
  and " 1" are errors. Accepting them would let two distinct strings describe
  one amount and break the payload fingerprint that the duplicate-settlement
  guard depends on.
• Testnet only. Arc Testnet is the sole enabled profile. Enabling a mainnet
  profile requires pinned values, an enabled flag, and explicit human
  authorization together; authorization alone is refused, and the mainnet
  profile has no values to authorize.
• Secrets. ONESHOT_PRIVY_APP_SECRET is classified secret and is read by
  nothing in this package. Redaction is deny-by-default on both key name and
  value shape, so an unclassified new provider field is redacted rather than
  leaked.

Validation

Commands and results:

cd packages/arc-adapter
npm install    : PASS (156 packages, 0 vulnerabilities)
npm run lint      : PASS (eslint, strictTypeChecked)
npm run typecheck : PASS (tsc --noEmit)
npm run test      : PASS (5 files, 99 tests)
npm run build     : PASS (tsc --project tsconfig.build.json)
git diff --cached --check : PASS (no whitespace errors)
staged-tree secret scan   : PASS (only an npm integrity hash and the
                            deliberate fake key literal the redaction
                            detector is tested against)

Independent review evidence

Gate A — exact candidate tree before push

• Base commit SHA: 9dc541d08daf4e9a9c338c562fb1fbe6ac6be04a (branch point)

• Candidate tree SHA: 5e49be7a785149da36b40861ad55a6ad6e8e2a26

• Candidate commit SHA: a1d8599afef17e668afe26fc26cccca1b7db4103

• Reviewer tool: free-pi-cli

• Reviewer model: glm-5.3-flash

• Verdict: PASS, but bound to a superset tree, not this exact head.

• Findings or residual risks: a FreePi review returned VERDICT: PASS with zero
  blocking findings over tree 3351a19e455024cf65de3f9fb400d8eac5df4080, which
  is the B02 branch containing B01 and B02 together. Every file in this PR was
  reviewed, but that tree is not this PR's head tree
  (b7b6942d46f0cc05d4c5784eee49ed68300777d0), so the exact-tree binding that
  .agent/IMPLEMENTATION_LOOP.md requires is not satisfied. Treat the content
  as reviewed and the tree identity as unbound.

• The reviewed tree equals the committed tree.

Gate B — exact remote PR head

• Reviewer tool: free-pi-cli

• Verdict: NOT RUN

• Gate B reviewed the current remote head and matches Gate A's approved tree.

• Agent policy / repository-policy and all applicable CI checks pass (repository-policy, Markdown and Mermaid, ESLint and TypeScript all pass; Workers Builds: oneshot fails on develop too and is pre-existing).

Both gates are unrun on the owner's instruction to proceed without them while
no deployment target exists. Treat this PR as not independently reviewed.
Package-local validation above is the substitute evidence.

Risk and rollback

Residual risks:

• Arc constants are not yet verified against official Arc documentation.
  Chain 5042002 and the USDC interface 0x3600...0000 are taken from
  milestones/CONTRACTS.md, not from a primary source. B01.2 requires the
  primary-source check before these are treated as pinned. The readiness probe
  is what catches a wrong value at runtime, but the constants themselves still
  need confirming.
• Dependency versions are pinned exact and will need a scheduled refresh;
  eslint@9.39.1 already reports as outside its supported window.
• IDENTIFIER_SHAPE for Privy wallet and policy IDs is a conservative shape
  guess. B02 should replace it with the real documented format.

Rollback: additive new package on a short-lived branch. Revert the commit or
close the PR. No migration, deployment, shared configuration, or durable state
is involved.

Human merge

• A human owner has reviewed the evidence and will perform the merge.

Anything else a reviewer should know

Base is develop, not main. .agent/AGENTS.md and
.agent/IMPLEMENTATION_LOOP.md forbid targeting main for feature work.

Two judgment calls worth checking:

1. No endpoints in the profile table. The first draft of profiles.ts
   contained invented rpcUrl and explorerUrl hostnames. That is exactly the
   guessed default that develop@d6758dd removed from the plan, so they were
   deleted. RPC and explorer are now operator configuration, and
   profiles.test.ts asserts that no profile contains any http(s):// string
   so they cannot creep back.

2. TypeScript 7 rejected. TypeScript 7.0.2 is published, but
   typescript-eslint constrains typescript to >=4.8.4 <6.1.0 at every
   published version including the latest 8.69.0. Choosing TS 7 would mean
   dropping type-aware linting on the package that validates chain identity and
   money. Pinned TypeScript 5.9.3 instead.

One bug the tests caught: the redaction key matcher originally missed
x-api-key, because the pattern list held apikey and api_key but not the
hyphenated spelling. Key matching now strips case and separators before
comparing, so one pattern covers every spelling a provider might use.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	oneshot	798f00e	Sep 07 2026, 01:35 PM