Programmable v4 Builder v0.5.1

Programmable v4 Builder v0.5.1

This release publishes the exact portable Builder package, generated plugin payload, manifest, SBOM, checksums, and
release receipt for one immutable Git revision. Publication does not establish model behavior, project approval,
deployment, audit, Registry acceptance, provider support, or live product evidence.

Intended version scope

• schema-bound open-world ProjectSpec, graph, architecture, repository-plan, and resumable-state compilation;
• first-class trade-capability compilation with explicit no-market handling, closed standard-v4/canonical-adapter
  manifests, and typed local quote/execution evidence that never claims route approval;
• closed capability contracts and executable semantic composition checks;
• typed v4 permission, callback, accounting, HookMiner, address, runtime, and PoolManager semantic bindings, plus an
  exact local standard-AMM Universal Router/Permit2 parity lane;
• source-derived semantic-coverage holds for underdeclared implementations;
• fresh-repository end-to-end eval infrastructure with encrypted sealed-after-design cases and explicit provider blocking;
• current upstream and local toolchain provenance, semantic rule ownership, and maintainability gates;
• portable Skill/plugin parity at package version 0.5.1.

Evidence boundary

The exact frozen commit, tree, skill tree, test commands, kernel campaign, eval hashes, installation receipts, and
remaining blockers belong in the generated release artifacts. The owner-authorized package release records model and
external behavior gates truthfully as unverified or EXTERNAL_BLOCKED; it does not convert them into passes or make a
behavior-qualified release claim. The public tag is an immutable distribution boundary, not an audit verdict.

The local release rehearsal performs no push, tag, GitHub release, publication, Registry write, deployment, signing,
approval, or onchain action.

Known limitations

• No host-native behavior receipt, Registry activation, production deployment, provider guarantee, or independent audit
  is claimed by the package release.
• Current source heads are drift canaries, not one compatibility set. Generated projects must use one exact tested
  dependency lane and revalidate every changed preimage.
• The standard Fee V2 exact-output witness remains sensitive to intervening swaps that change live rounding remainders;
  a stale witness reverts atomically but can cause ordering or gas grief.
• Model-backed release thresholds require multiple fresh runs across frontier, medium, and small tiers. When unavailable,
  only the complete harness and its external blocker are evidence.
• The 216-run model matrix and fork-dependent cases remain EXTERNAL_BLOCKED until independent agent and judge
  adapters, three named model tiers, an independent judge model, and a fork RPC are supplied. Structural and fake-agent
  harness passes are not substituted for those results.
• Universal Router evidence is an exact, local compatibility lane for allowance-transfer ERC-20 and native-ETH routes.
  The added V4Quoter/route tests cover only their explicitly supported modes and local state. They do not prove Permit2
  signature flows, deployed-address reachability, aggregator discovery, external fork execution, routing approval, or
  an audit of the generated project.
• The exact offline SDK/test compatibility tree currently carries 36 transitive npm advisories (17 low, 9 moderate,
  10 high, 0 critical). They are not treated as fixed or suitable for an application runtime merely because the local
  fixed-vector route tests do not exercise their network and tooling surfaces.
• Live upstream and package-deprecation visibility requires registry and GitHub network access. A rate-limited or
  unavailable endpoint remains an explicit external blocker; the scheduled read-only workflow does not silently turn
  missing observations into a clean result.