From 9bb38f04010978292be17b04bba531720b59087b Mon Sep 17 00:00:00 2001
From: Tan <iammaithanhtan@gmail.com>
Date: Tue, 18 Aug 2026 16:58:58 +0700
Subject: [PATCH 1/7] docs: record C09A E5 closeout evidence

---
 docs/research/C09A-E5.md | 175 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 175 insertions(+)
 create mode 100644 docs/research/C09A-E5.md

diff --git a/docs/research/C09A-E5.md b/docs/research/C09A-E5.md
new file mode 100644
index 0000000..2be4b71
--- /dev/null
+++ b/docs/research/C09A-E5.md
@@ -0,0 +1,175 @@
+# C09A-E5 — PREVRANDAO Analyzer Closeout
+
+Status: Closeout candidate — final CI and independent review required
+
+Risk: R1 documentation/governance closeout
+
+Base branch: `main`
+
+Base SHA: `bc0b00b88b295cfaa10f4b976b852229a5ffab8d`
+
+Last reviewed: 2026-08-18
+
+## 1. Outcome
+
+C09 and C09A have completed the approved bounded Build path for the duplicate
+PREVRANDAO compatibility problem.
+
+The production result is one shared private Solidity/Foundry analyzer with two
+temporary public compatibility shells:
+
+```text
+wallet/PREVRANDAO_NOT_SUPPORTED
+bridge/NO_PREVRANDAO_RELAY_SELECTION
+```
+
+The old broad PREVRANDAO and blanket `mixHash` keyword heuristics are no longer
+the public emission path. Public findings require both bounded same-function
+behavior evidence and exact retained Foundry Arc Testnet ownership for the same
+concrete contract.
+
+The compatibility inventory remains:
+
+```text
+19 known / 16 default / 7 wallet / 4 canonical
+```
+
+Both public IDs remain default-critical and non-canonical during the temporary
+compatibility period.
+
+## 2. Delivered phases
+
+### C09 research and decision
+
+- C09-R1: parser, premise, ownership, dependency, and public-surface audit.
+- C09-R2: complete Solidity/source and deployment-association corpus.
+- C09-R3-A: bounded Solidity source/value-flow feasibility.
+- C09-R3-B: bounded Foundry `run-latest.json` Arc ownership feasibility.
+- C09-D: Build selected with one private analyzer and two compatibility shells.
+
+### C09A implementation
+
+- E1 — PR #63, merge `d829278f26669f6190a516cb3c0efed9aca7f49c`:
+  production `@solidity-parser/parser@0.20.2`, lazy parser loading, and private
+  source analysis.
+- E2 — PR #65, merge `5d368d7ac0d75a00c9d6dfb65496304040a738f7`:
+  bounded same-function value flow, supported sinks, deterministic routing, and
+  scan-scoped cache behavior.
+- E3 — PR #68, merge `a4d3a5cb5ea6eb92fd18f84c01e4c2c61ac54903`:
+  exact Foundry ownership and composed private eligibility.
+- E4 — PR #67, merge `bc0b00b88b295cfaa10f4b976b852229a5ffab8d`:
+  public compatibility-shell migration, removal of broad keyword emission,
+  finding/remediation updates, demo coverage, catalog/taxonomy updates, and
+  installed-package regression coverage.
+
+## 3. Final analyzer contract
+
+A reportable record is intentionally bounded to reviewed evidence:
+
+- supported `.sol` source;
+- exact PREVRANDAO source family;
+- same-function bounded value dependency;
+- approved selection, authorization, eligibility, allocation, recipient, winner,
+  ordering, relay, relayer, validator, sequencer, or committee sink;
+- one deterministic shell owner;
+- exact concrete contract identity;
+- retained Foundry broadcast ownership from
+  `broadcast/<Script>.s.sol/<chainId>/run-latest.json`;
+- exact Arc Testnet chain ID `5042002`;
+- valid exact deployed contract address;
+- no conflicting Arc/non-Arc ownership.
+
+Unsupported or ambiguous evidence fails closed.
+
+## 4. Dependency and package impact
+
+C09A adds the exact production dependency:
+
+```text
+@solidity-parser/parser@0.20.2
+```
+
+The dependency is MIT licensed and has no runtime transitive dependencies in the
+reviewed package metadata. The package smoke gate verifies external parser
+resolution, declaration-type isolation, source-map provenance, packed-artifact
+boundaries, lazy loading, dependency withdrawal/restoration behavior, and
+installed execution.
+
+ArcReady does not add `solc`, `solc-js`, Tree-sitter, a Foundry binary, or a
+second Solidity parser for C09A.
+
+## 5. Supported grammar and explicit limits
+
+C09A is not a general Solidity security analyzer, CFG engine, SSA engine, taint
+engine, or symbolic executor.
+
+The supported production surface remains deliberately narrow and fail-closed.
+It does not claim support for arbitrary:
+
+- cross-file or cross-contract value flow;
+- inheritance, modifier, library, or imported-symbol resolution;
+- mutation graphs, deep alias graphs, branch joins, loops, or recursion;
+- generic Yul analysis;
+- compiler-version inference;
+- Hardhat or custom deployment adapters;
+- live RPC, explorer, bytecode, transaction, or runtime verification.
+
+Foundry evidence is static retained artifact evidence only. A finding does not
+prove that a deployment is currently live, that bytecode matches a current
+chain state, or that any transaction succeeded.
+
+## 6. Compatibility-shell limitation and later trigger
+
+The two public IDs are retained only for compatibility with existing wallet and
+bridge preset contracts.
+
+A later separately reviewed milestone may consolidate or retire one or both
+shells when at least one of these conditions is met:
+
+- usage evidence shows one shell has negligible material value;
+- a stable existing preset can truthfully own the full supported finding surface;
+- a versioned public migration can preserve configuration compatibility without
+  silently losing coverage;
+- real user evidence justifies a broader or different ownership model.
+
+No shell consolidation should be bundled into C09A closeout.
+
+## 7. E4 validation evidence
+
+The merged E4 delivery recorded:
+
+- `corepack pnpm verify:full`: pass;
+- 41 package test files / 2,683 tests passed;
+- 5 / 5 workflow tests passed;
+- fixtures, lint, build, and installed-package smoke passed;
+- broken demo: 14 findings, including the reviewed Foundry-backed PREVRANDAO
+  examples;
+- independent adversarial review: APPROVE with 0 blocker / 0 major / 0 minor;
+- independent focused review: 1,119 / 1,119 tests plus a three-sink end-to-end
+  probe passed.
+
+## 8. E5 final gate
+
+This closeout branch must pass the repository's normal CI and documentation
+checks against current `main`.
+
+Before merge, confirm:
+
+- repository CI passes on the exact closeout head;
+- Repository Verification passes;
+- ArcReady Action Smoke passes;
+- ArcReady Example passes;
+- candidate diff and clean-repository checks pass where applicable;
+- independent review reports 0 blocker / 0 major / 0 minor;
+- roadmap and backlog describe C09/C09A as complete and make C10 the next
+  sequenced engineering milestone.
+
+## 9. Next milestone
+
+After this closeout merges, the recommended engineering sequence moves to C10:
+versioned App Kit compatibility.
+
+C10 should model official versioned chain identifiers, operations, tokens,
+adapters, and support tables. It should not continue hardening the deprecated
+generic capability guard or broaden ArcReady into a generic static-analysis
+platform.

From 1cb6368b88e85e2c4851df25904138be794cf619 Mon Sep 17 00:00:00 2001
From: Tan <iammaithanhtan@gmail.com>
Date: Tue, 18 Aug 2026 16:59:34 +0700
Subject: [PATCH 2/7] docs: complete C09A execution plan

---
 docs/exec-plans/completed/C09A.md | 189 ++++++++++++++++++++++++++++++
 1 file changed, 189 insertions(+)
 create mode 100644 docs/exec-plans/completed/C09A.md

diff --git a/docs/exec-plans/completed/C09A.md b/docs/exec-plans/completed/C09A.md
new file mode 100644
index 0000000..baaf4dc
--- /dev/null
+++ b/docs/exec-plans/completed/C09A.md
@@ -0,0 +1,189 @@
+# C09A — Bounded PREVRANDAO Analyzer Implementation
+
+Status: Complete
+
+Planning risk: R2
+
+Implementation risk: R3
+
+Owner: ArcReady maintainers
+
+Decision record: `docs/research/C09-D.md`
+
+Closeout evidence: `docs/research/C09A-E5.md`
+
+Completed: 2026-08-18
+
+## 1. Goal
+
+Replace the two broad PREVRANDAO keyword heuristics with one production private
+analyzer that emits only when both reviewed evidence layers are proven:
+
+1. bounded Solidity source, same-function value dependency, and supported sink;
+2. exact retained Foundry contract-to-Arc deployment association.
+
+Retain the existing wallet and bridge public IDs as temporary compatibility
+shells without adding a new runtime preset, finding category, or public ID.
+
+## 2. Final architecture
+
+C09A delivers one shared private analyzer with scan-scoped reuse. It owns lazy
+Solidity parser loading, bounded source/function ownership, direct and approved
+one-binding value flow, supported sink classification, deterministic shell
+routing, Foundry broadcast association, and composed eligibility.
+
+The public compatibility shells are:
+
+```text
+wallet/PREVRANDAO_NOT_SUPPORTED
+bridge/NO_PREVRANDAO_RELAY_SELECTION
+```
+
+Each private eligible record has exactly one shell owner. Selecting both presets
+does not duplicate one underlying record.
+
+The old broad PREVRANDAO and blanket `mixHash` keyword emission path was removed
+in E4.
+
+## 3. Delivered phases
+
+### E1 — dependency and private source analysis
+
+PR #63 merged as `d829278f26669f6190a516cb3c0efed9aca7f49c`.
+
+Delivered:
+
+- exact production `@solidity-parser/parser@0.20.2` dependency;
+- lazy parser loading;
+- bounded `.sol` source ownership and source records;
+- fail-closed handling for unsupported or malformed evidence;
+- packed-package parser boundary verification.
+
+### E2 — bounded value flow, sinks, and routing
+
+PR #65 merged as `5d368d7ac0d75a00c9d6dfb65496304040a738f7`.
+
+Delivered:
+
+- direct and approved one single-assignment same-function flow;
+- supported selection, authorization, eligibility, allocation, recipient,
+  winner, ordering, relay, validator, sequencer, and committee sinks;
+- safe-observation and unsupported-flow classification;
+- deterministic wallet/bridge shell ownership;
+- scan-scoped analyzer reuse.
+
+### E3 — Foundry ownership and composed eligibility
+
+PR #68 merged as `a4d3a5cb5ea6eb92fd18f84c01e4c2c61ac54903`.
+
+Delivered:
+
+- bounded `broadcast/<Script>.s.sol/<chainId>/run-latest.json` adapter;
+- exact project-root, contract, chain, CREATE transaction, and address ownership;
+- exact Arc Testnet chain ID `5042002`;
+- fail-closed conflict, ambiguity, malformed-artifact, and sibling-root behavior;
+- private eligibility only when source/flow and Foundry ownership match the same
+  concrete contract.
+
+### E4 — public compatibility-shell migration
+
+PR #67 merged as `bc0b00b88b295cfaa10f4b976b852229a5ffab8d`.
+
+Delivered:
+
+- removal of the old keyword detector behavior;
+- public conversion from exact shared eligibility records;
+- source-scoped actionable finding and remediation copy;
+- no duplicate finding across both presets;
+- catalog, taxonomy, demo, fixture, reporter, scoring, severity, `failOn`, and
+  installed-package regression coverage;
+- inventory preserved at `19 known / 16 default / 7 wallet / 4 canonical`.
+
+E4 recorded `corepack pnpm verify:full` passing, 41 package test files / 2,683
+tests passing, 5 / 5 workflow tests passing, build/lint/package smoke passing,
+and independent adversarial review at 0 blocker / 0 major / 0 minor.
+
+### E5 — closeout
+
+Closeout evidence is recorded in `docs/research/C09A-E5.md`.
+
+E5:
+
+- records merged phase commits and final inventory;
+- records parser/package impact and supported boundaries;
+- records Foundry-only deployment coverage and unsupported surfaces;
+- records the temporary compatibility-shell limitation and later retirement or
+  consolidation trigger;
+- moves C09 and C09A from active to completed plans;
+- makes C10 the next sequenced engineering milestone;
+- requires current-head CI and independent review before the closeout PR merges.
+
+## 4. Final dependency contract
+
+Production dependency:
+
+```text
+@solidity-parser/parser@0.20.2
+```
+
+The reviewed dependency is MIT licensed with zero runtime transitive dependencies
+in its package metadata. ArcReady does not add `solc`, `solc-js`, Tree-sitter,
+a Foundry binary, or another Solidity parser in C09A.
+
+Package smoke verifies parser externalization and provenance, declaration type
+isolation, packed-artifact boundaries, lazy loading, dependency withdrawal and
+restoration, and installed-package execution.
+
+## 5. Supported evidence boundary
+
+A reportable record requires all of the following within the reviewed bounded
+surface:
+
+- supported complete `.sol` input;
+- exact supported PREVRANDAO source form;
+- same-function bounded value dependency;
+- approved behavior sink;
+- exact concrete contract identity;
+- deterministic shell owner;
+- exact retained Foundry broadcast evidence;
+- Arc Testnet chain ID `5042002`;
+- valid exact deployed address;
+- no ambiguous or conflicting ownership.
+
+Unsupported or ambiguous evidence fails closed.
+
+## 6. Explicit non-goals and limitations
+
+C09A does not provide general:
+
+- Solidity CFG, SSA, taint, symbolic execution, or vulnerability analysis;
+- cross-file or cross-contract value resolution;
+- arbitrary inheritance, modifier, library, import, mutation, alias, loop, or
+  recursion analysis;
+- generic Yul analysis;
+- compiler-version inference;
+- Hardhat or custom deployment adapters;
+- live RPC, explorer, bytecode, transaction, or runtime verification.
+
+Foundry evidence is retained static artifact evidence only. A finding does not
+claim that a deployment is live, bytecode matches current chain state, or a
+transaction succeeded.
+
+## 7. Compatibility period
+
+Both public rule IDs remain default-critical and non-canonical during the
+compatibility period.
+
+A later separately reviewed milestone may consolidate or retire the shells only
+from concrete compatibility or usage evidence. C09A itself does not add a new
+`solidity` preset, public category, public rule ID, schema, or canonical
+FindingV2 rule.
+
+## 8. Completion result
+
+C09A completes the Build disposition selected by C09-D while preserving the
+product boundary: Arc-specific, local-first, CI-friendly, conservative, and
+fail-closed.
+
+The next sequenced engineering milestone is C10: versioned App Kit
+compatibility.

From dc39238fe07a6f7c22e6ba22157d21b764e49e59 Mon Sep 17 00:00:00 2001
From: Tan <iammaithanhtan@gmail.com>
Date: Tue, 18 Aug 2026 16:59:50 +0700
Subject: [PATCH 3/7] docs: complete C09 replacement plan

---
 docs/exec-plans/completed/C09.md | 102 +++++++++++++++++++++++++++++++
 1 file changed, 102 insertions(+)
 create mode 100644 docs/exec-plans/completed/C09.md

diff --git a/docs/exec-plans/completed/C09.md b/docs/exec-plans/completed/C09.md
new file mode 100644
index 0000000..ab456d2
--- /dev/null
+++ b/docs/exec-plans/completed/C09.md
@@ -0,0 +1,102 @@
+# C09 — PREVRANDAO Value-Dependency Replacement
+
+Status: Complete
+
+Owner: ArcReady maintainers
+
+Decision record: `docs/research/C09-D.md`
+
+Implementation closeout: `docs/exec-plans/completed/C09A.md`
+
+Completed: 2026-08-18
+
+## 1. Product problem
+
+ArcReady previously exposed two default-critical rules for one underlying Arc
+compatibility problem:
+
+```text
+wallet/PREVRANDAO_NOT_SUPPORTED
+bridge/NO_PREVRANDAO_RELAY_SELECTION
+```
+
+The former implementations relied on broad Arc/PREVRANDAO keyword proximity and
+blanket `mixHash` matching. That evidence could not prove that PREVRANDAO affected
+a supported behavior or that the exact contract was associated with Arc.
+
+C09 replaced that evidence model rather than hardening the old heuristics.
+
+## 2. Research result
+
+C09-R1 through C09-R3-B established a bounded, fail-closed implementation path:
+
+- exact PREVRANDAO source evidence can be owned to concrete Solidity
+  contract/function ranges;
+- direct and one reviewed local binding can be traced to approved same-function
+  behavior sinks without building a general data-flow platform;
+- comments, strings, mutation, ambiguity, unsupported syntax, and wider flow can
+  fail closed;
+- one exact Foundry `forge script` broadcast artifact family can associate a
+  concrete contract with Arc Testnet without live RPC or explorer calls.
+
+The research did not authorize general Solidity analysis, broad deployment
+framework support, or live-chain claims.
+
+## 3. Decision
+
+C09-D selected **Build** with this architecture:
+
+- one shared private analyzer;
+- two temporary compatibility shells preserving the existing public IDs;
+- no new runtime `solidity` preset or public finding category;
+- exactly one shell owner for each eligible private record;
+- public critical emission only when supported source/value evidence and exact
+  Foundry Arc ownership are both proven for the same concrete contract;
+- preserve inventory `19 known / 16 default / 7 wallet / 4 canonical`;
+- keep both rules non-canonical FindingV2 rules.
+
+## 4. Implementation result
+
+C09A completed the selected Build path in E1 through E5.
+
+Merged implementation phases:
+
+- E1 / PR #63 — private Solidity parser/source analysis;
+- E2 / PR #65 — bounded dependency, sink, routing, and cache behavior;
+- E3 / PR #68 — Foundry ownership and composed eligibility;
+- E4 / PR #67 — public compatibility-shell migration.
+
+The final implementation removes broad keyword emission, preserves public IDs and
+preset behavior, and emits only source-scoped findings backed by the reviewed
+bounded evidence contract.
+
+Full implementation and closeout details are maintained in:
+
+```text
+docs/exec-plans/completed/C09A.md
+docs/research/C09A-E5.md
+```
+
+## 5. Final limitations
+
+C09/C09A intentionally do not add:
+
+- general Solidity CFG, SSA, taint, symbolic execution, or vulnerability
+  analysis;
+- unrestricted cross-file, cross-contract, import, inheritance, or mutation
+  resolution;
+- Hardhat or generic deployment-framework support;
+- live RPC, explorer, deployed-bytecode, runtime, or transaction-success
+  verification;
+- a new public rule ID, preset, category, schema, or canonical rule.
+
+Foundry `run-latest.json` is retained static artifact evidence only.
+
+## 6. Compatibility follow-up
+
+The wallet and bridge public IDs remain temporary compatibility shells. A later
+reviewed milestone may consolidate or retire them only when concrete usage or
+compatibility evidence justifies the migration.
+
+The next sequenced engineering milestone after C09A closeout is C10: versioned
+App Kit compatibility.

From 1420a570ff5420db9ccd1ba6cd59887adf80e865 Mon Sep 17 00:00:00 2001
From: Tan <iammaithanhtan@gmail.com>
Date: Tue, 18 Aug 2026 17:00:04 +0700
Subject: [PATCH 4/7] docs: move C09A plan to completed

---
 docs/exec-plans/active/C09A.md | 470 ---------------------------------
 1 file changed, 470 deletions(-)
 delete mode 100644 docs/exec-plans/active/C09A.md

diff --git a/docs/exec-plans/active/C09A.md b/docs/exec-plans/active/C09A.md
deleted file mode 100644
index 1f66edf..0000000
--- a/docs/exec-plans/active/C09A.md
+++ /dev/null
@@ -1,470 +0,0 @@
-# C09A — Bounded PREVRANDAO Analyzer Implementation Plan
-
-Status: Planned
-
-Planning risk: R2
-
-Implementation risk: R3
-
-Owner: ArcReady maintainers
-
-Base branch: `main`
-
-Base SHA: `16e3d00a26784655d5049fbffab6618e34e98297`
-
-Planning branch: `docs/c09-d-bounded-build-decision`
-
-Decision record: `docs/research/C09-D.md`
-
-Last reviewed: 2026-08-06
-
-## 1. Goal
-
-Replace the two existing PREVRANDAO keyword heuristics with one production
-private analyzer that emits only when both of these evidence layers are proven:
-
-1. bounded Solidity source, same-function value dependency, and supported sink;
-2. exact Foundry contract-to-Arc deployment association.
-
-Retain the two existing public rule IDs as temporary compatibility shells without
-adding a new runtime preset, finding category, or public ID.
-
-## 2. Current state
-
-Current public rules:
-
-```text
-wallet/PREVRANDAO_NOT_SUPPORTED
-bridge/NO_PREVRANDAO_RELAY_SELECTION
-```
-
-Both are default critical and both currently rely on broad Arc text plus
-line-level PREVRANDAO or `mixHash` matching. The bridge rule adds same-line relay
-or randomness words.
-
-C09 research established:
-
-- blanket `mixHash` equivalence is unsupported;
-- symbol presence does not prove behavior;
-- R3-A source/value analysis is feasible within a bounded grammar;
-- R3-B exact Foundry Arc ownership is feasible for one artifact family;
-- no production parser dependency or behavior has yet been introduced.
-
-## 3. Target architecture
-
-### Shared analyzer
-
-Create one private analyzer with a scan-scoped cache. It owns:
-
-- lazy parser loading;
-- supported `.sol` discovery;
-- AST parse and diagnostics;
-- source and function ownership;
-- bounded binding and sink classification;
-- concrete contract identity;
-- Foundry broadcast discovery and parsing;
-- exact contract-to-chain association;
-- private record composition and deterministic ordering.
-
-The analyzer returns private records only. It must not import public finding or
-reporter types.
-
-### Compatibility shells
-
-The existing wallet and bridge rule modules become thin adapters.
-
-They may:
-
-- request the shared private records;
-- filter records by the reviewed shell ownership class;
-- convert each owned record into the existing public Finding shape;
-- apply existing config severity overrides through normal runtime execution.
-
-They must not:
-
-- parse source independently;
-- re-run Foundry association independently;
-- contain PREVRANDAO or `mixHash` keyword detection;
-- emit the same private record twice;
-- borrow Arc ownership from broad text.
-
-## 4. Private record contract
-
-Each reportable private record must include enough evidence for deterministic
-conversion and review:
-
-```text
-sourceFile
-contractName
-functionName
-sourceKind
-sourceOffset
-bindingKind
-sinkKind
-sinkOffset
-shellOwner
-foundryArtifactPath
-chainId
-contractAddress
-confidence
-```
-
-The record must not claim runtime behavior, transaction success, deployed bytecode
-identity, or live-chain verification.
-
-### Shell ownership
-
-Allowed values:
-
-```text
-bridge-relay
-wallet-compatibility
-```
-
-`bridge-relay` requires a supported sink whose exact function, collection, or
-selected-entity identifiers establish relay, relayer, validator, sequencer, or
-committee behavior.
-
-`wallet-compatibility` owns the remaining supported selection, authorization,
-eligibility, winner, recipient, allocation, and ordering records during the
-compatibility period.
-
-Ambiguous shell ownership fails closed and emits no public finding.
-
-A record emits only through its exact owner shell when that shell rule is
-selected. The other shell never borrows it. E2 must pin wallet-only, bridge-only,
-both-presets, neither-owner, and ambiguous-owner behavior. When both shells are
-selected, one eligible private record still becomes exactly one public finding.
-
-## 5. Dependency and packaging contract
-
-C09A-E1 may add exactly:
-
-```text
-@solidity-parser/parser@0.20.2
-```
-
-as a production dependency only after the dependency review passes.
-
-Required dependency checks:
-
-- exact version and integrity are recorded in `pnpm-lock.yaml`;
-- package license is MIT-compatible;
-- installed and packed contents are measured;
-- zero runtime transitive dependencies are confirmed;
-- Node 22 import succeeds;
-- tsup ESM build and declaration generation succeed;
-- packed ArcReady package can lazy-load the parser;
-- non-Solidity scans do not import the parser;
-- no `solc`, `solc-js`, Tree-sitter, Foundry binary, or additional parser is
-  introduced.
-
-The parser should remain external to the main tsup bundle only when the packed
-package includes and resolves it correctly. Bundling or externalization must be
-decided from package smoke evidence, not assumption.
-
-## 6. Supported source grammar
-
-The first production version supports only R3-reviewed complete `.sol` source
-families.
-
-### Source forms
-
-- exact `block.prevrandao`;
-- one approved direct cast around the source;
-- one same-function single-assignment local binding;
-- exact inline assembly `prevrandao()` assignment;
-- `block.difficulty` only after a separately reviewed exact post-Paris EVM-target
-  evidence adapter exists.
-
-`block.difficulty` should remain disabled in E1–E4 unless that adapter is
-implemented and independently reviewed within the same bounded milestone.
-
-### Supported sinks
-
-- direct modulo/index collection selection;
-- approved direct relay, validator, sequencer, committee, winner, recipient,
-  allocation, authorization, eligibility, and ordering expressions;
-- same function and same contract only;
-- deterministic earliest reportable candidate when multiple source occurrences
-  exist.
-
-### Safe observations
-
-The analyzer must not report:
-
-- unused reads;
-- diagnostic returns;
-- logs or event-only observations;
-- explicit zero compatibility assertions;
-- hashing without a supported behavior sink;
-- deterministic replacement logic.
-
-## 7. Foundry ownership contract
-
-Supported artifact family:
-
-```text
-broadcast/<Script>.s.sol/<chainId>/run-latest.json
-```
-
-Required evidence:
-
-- normalized repository-relative paths;
-- same bounded project root for `src/` and `broadcast/`;
-- no empty, dot, parent, absolute, backslash, vendor, or sibling-root paths;
-- integer path chain ID;
-- integer JSON `chain` field equal to the path chain ID;
-- exact concrete contract definition outside comments and strings;
-- exactly one concrete definition for the deployed contract name;
-- `CREATE` transaction;
-- valid 20-byte deployed address;
-- exact Arc Testnet chain ID `5042002`;
-- no conflicting non-Arc deployment for the same exact contract;
-- no conflicting Arc addresses.
-
-Malformed, incomplete, fuzzy, duplicate-owner, conflicting, unsupported-adapter,
-or absent evidence emits no public finding.
-
-C09A does not execute `forge` and does not query RPC or explorers.
-Foundry v1.7.1 is the reviewed schema baseline only; runtime validates structure
-and does not claim which Foundry version produced an artifact.
-
-## 8. Implementation phases
-
-### C09A-E1 — dependency and private parser source records
-
-Scope:
-
-- complete the dependency and packaging review;
-- add the exact approved parser dependency if all gates pass;
-- implement lazy parser loading;
-- parse only `.sol` candidates;
-- recognize exact source forms and source ownership;
-- return private source records only;
-- keep both public rules behavior unchanged until E4.
-
-Required tests:
-
-- exact package/version/integrity assertions;
-- parser load and lazy-load instrumentation;
-- comments, strings, abstract contracts, malformed syntax, unknown nodes, and
-  missing ranges fail closed;
-- R3-A canonical and adversarial source corpus is ported or reused without
-  weakening expected classifications;
-- package build and packed-package smoke pass.
-
-Exit:
-
-- independent review `APPROVE` with 0 blocker / 0 major / 0 minor;
-- no public finding change.
-
-### C09A-E2 — bounded binding, sink, and shell routing
-
-Scope:
-
-- implement direct and one single-assignment local flow;
-- implement approved same-function sinks;
-- classify safe observations and unsupported flow;
-- assign exactly one reviewed shell owner;
-- maintain deterministic source and sink offsets;
-- return private records only.
-
-Required tests:
-
-- direct, cast, one-binding, assembly, safe, unsupported, and adversarial cases;
-- mutation, shadowing, duplicate declarations, joins, loops, cross-function,
-  cross-contract, unsupported Yul, and ambiguous shell ownership fail closed;
-- bridge and wallet shell-routing corpus;
-- wallet-only, bridge-only, both-presets, owner-not-selected, and ambiguous-owner
-  behavior;
-- repeated analyzer request in one scan returns the same cached records;
-- no public finding change.
-
-Exit:
-
-- independent review `APPROVE` with 0 blocker / 0 major / 0 minor.
-
-### C09A-E3 — Foundry adapter and composed eligibility
-
-Scope:
-
-- implement the reviewed Foundry JSON adapter;
-- prove exact project-root, concrete contract, chain, transaction, and address
-  ownership;
-- compose R3-A-style source records with R3-B-style Arc ownership;
-- mark private records eligible only when both layers match the same exact
-  contract and project root;
-- still emit no public findings.
-
-Required tests:
-
-- 16 canonical project cases;
-- 9 ownership adversarial cases;
-- malformed JSON, duplicate definitions, abstract-only source, comment/string
-  spoofing, missing address, non-CREATE, conflict, sibling root, vendor, and
-  traversal pressure;
-- source record for one contract cannot borrow another contract's artifact;
-- source project cannot borrow a sibling project's artifact;
-- no public finding change.
-
-Exit:
-
-- independent review `APPROVE` with 0 blocker / 0 major / 0 minor.
-
-### C09A-E4 — compatibility shells and public migration
-
-Scope:
-
-- delete the keyword detector logic from both public rule modules;
-- integrate both shells with the shared analyzer;
-- convert only eligible records owned by that shell;
-- update finding copy, remediation, docs, catalog, taxonomy confidence, tests,
-  fixtures, inventory assertions, and report expectations;
-- preserve both IDs, default scheduling, default `critical`, and normal config
-  severity overrides;
-- prevent duplicate findings when both presets are active;
-- preserve inventory target `19 / 16 / 7 / 4`;
-- keep both rules non-canonical FindingV2 rules.
-
-Required finding copy:
-
-- state that an exact Arc-deployed contract has a supported behavior dependency
-  on PREVRANDAO, whose value is zero on Arc;
-- identify the exact contract/function and supported sink class;
-- recommend deterministic selection or an external randomness source appropriate
-  to the application;
-- state that analysis is static and Foundry-artifact-based;
-- never claim live deployment or transaction success.
-
-Required tests:
-
-- wallet-only, bridge-only, both presets, explicit severity overrides, off,
-  failOn, scoring, reporters, instrumentation, deterministic order, fixtures,
-  demos, CLI, package smoke, and clean-repository checks;
-- no duplicate finding for one private record;
-- no finding for projects without exact Foundry Arc association;
-- no finding from `mixHash`, comments, strings, broad Arc text, or unsupported
-  Solidity flow.
-
-Exit:
-
-- independent review `APPROVE` with 0 blocker / 0 major / 0 minor.
-
-### C09A-E5 — closeout
-
-Scope:
-
-- run final full repository verification;
-- record merged phase commits and final inventory;
-- document parser dependency and package impact;
-- document supported grammar, Foundry-only coverage, unsupported surfaces, and
-  compatibility-shell limitation;
-- move C09 and C09A plans to completed;
-- update roadmap and backlog;
-- record later shell consolidation or retirement trigger.
-
-Exit:
-
-- final independent review `APPROVE` with 0 blocker / 0 major / 0 minor;
-- CI, Repository Verification, Action Smoke, Example, candidate diff, and clean
-  repository checks pass.
-
-## 9. Files likely to change
-
-Expected production and test scope includes:
-
-```text
-package.json
-pnpm-lock.yaml
-packages/arcready/package.json
-packages/arcready/rules/shared/prevrandao-analysis.ts
-packages/arcready/rules/wallet/prevrandao-not-supported.ts
-packages/arcready/rules/bridge/no-prevrandao-relay-selection.ts
-packages/arcready/core/rules/catalog.ts
-docs/rule-catalog.md
-packages/arcready/test/wallet-rules.test.ts
-packages/arcready/test/bridge-rules.test.ts
-packages/arcready/test/cross-preset.test.ts
-packages/arcready/test/rule-taxonomy.test.ts
-packages/arcready/test/fixtures.test.ts
-packages/arcready/test/rule-execution-instrumentation.test.ts
-scripts/demo-fixtures.ts
-```
-
-Additional package, fixture, or snapshot files may change only when required by
-verified build/package behavior or intentional finding changes.
-
-## 10. Risk controls
-
-- separate E1 through E5 into independently reviewable PRs or commits;
-- do not combine dependency introduction and public finding migration in one
-  semantic phase;
-- no force push or history rewrite;
-- fail closed for every unsupported or ambiguous evidence dimension;
-- preserve both public IDs until a later reviewed compatibility decision;
-- never add a `solidity` preset or category in C09A;
-- never import research prototypes directly into production;
-- port behavior from reviewed contracts, not by copying research code without
-  production review;
-- no live RPC, explorer, compiler, or Foundry execution;
-- stop and redesign if caching or shell routing requires a general plugin system;
-- do not expand grammar from incidental implementation convenience.
-
-## 11. Non-goals
-
-C09A does not include:
-
-- general Solidity CFG, SSA, taint, symbolic execution, or vulnerability
-  analysis;
-- arbitrary compiler-version inference;
-- arbitrary imports, inheritance, libraries, modifiers, Yul, or cross-file value
-  flow;
-- Hardhat or custom deployment adapters;
-- new public presets, categories, IDs, schemas, or plugin registries;
-- canonical FindingV2 promotion;
-- live-chain verification;
-- C10 implementation.
-
-## 12. Validation
-
-Every semantic phase must run its focused tests plus:
-
-```powershell
-corepack pnpm exec prettier --check .
-git diff --check
-corepack pnpm verify:full
-```
-
-Dependency and public-integration phases must also verify:
-
-```powershell
-corepack pnpm pack
-```
-
-and run the packed package in a clean temporary project against:
-
-- a non-Solidity repository;
-- a supported Foundry Arc project;
-- a Solidity project without exact Arc ownership;
-- a project containing both wallet and bridge presets.
-
-## 13. Completion contract
-
-C09A is complete only when:
-
-- both old keyword detectors are removed;
-- one shared analyzer provides all source and ownership evidence;
-- supported findings require exact source, sink, contract, Foundry artifact, and
-  Arc chain evidence;
-- each private record is owned by exactly one public shell;
-- both public IDs remain compatible without duplicate findings;
-- inventory remains `19 known / 16 default / 7 wallet / 4 canonical`;
-- parser dependency and packed-package behavior are verified;
-- no unsupported grammar or deployment adapter emits a finding;
-- all semantic phases receive independent `APPROVE 0/0/0` reviews;
-- full repository verification and product workflows pass;
-- closeout evidence is recorded.
-
-No production implementation begins before C09-D and this plan are independently
-approved and merged.

From 455a0a3d44640ff0178c7723942928277901942e Mon Sep 17 00:00:00 2001
From: Tan <iammaithanhtan@gmail.com>
Date: Tue, 18 Aug 2026 17:00:12 +0700
Subject: [PATCH 5/7] docs: move C09 plan to completed

---
 docs/exec-plans/active/C09.md | 562 ----------------------------------
 1 file changed, 562 deletions(-)
 delete mode 100644 docs/exec-plans/active/C09.md

diff --git a/docs/exec-plans/active/C09.md b/docs/exec-plans/active/C09.md
deleted file mode 100644
index a4750f3..0000000
--- a/docs/exec-plans/active/C09.md
+++ /dev/null
@@ -1,562 +0,0 @@
-# C09 — PREVRANDAO Value-Dependency Replacement Plan
-
-Status: Decision selected; implementation pending
-
-Planning risk: R1
-
-Proposed implementation risk: R3
-
-Owner: ArcReady maintainers
-
-Base branch: `main`
-
-Base SHA: `c17c8b4cf2288df825ef5d677b5fc9eba5674b74`
-
-Planning branch: `docs/c09-prevrandao-replacement-plan`
-
-Decision record: `docs/research/C09-D.md`
-
-Implementation plan: `docs/exec-plans/active/C09A.md`
-
-Completed research evidence:
-
-- C09-R1: parser and ownership audit
-- C09-R2: 52-case source and project corpus
-- C09-R3-A: bounded Solidity value-flow prototype
-- C09-R3-B: bounded Foundry deployment-association prototype
-
-Selected disposition: Build one private analyzer with two temporary public
-compatibility shells. Production remains blocked until C09-D and C09A are merged
-and independently reviewed.
-
-C09A is the next implementation milestone. The compatibility inventory target
-remains `19 known / 16 default / 7 wallet / 4 canonical`.
-
-Last reviewed: 2026-08-06
-
-## 1. Product problem
-
-ArcReady currently exposes two default critical rules for one underlying Arc
-compatibility problem:
-
-```text
-wallet/PREVRANDAO_NOT_SUPPORTED
-bridge/NO_PREVRANDAO_RELAY_SELECTION
-```
-
-Both rules use file-level Arc keywords and line-level PREVRANDAO keywords. The
-wallet rule reports any active occurrence. The bridge rule adds relay or
-randomness words on the same line.
-
-Neither detector proves that the opcode value affects application behavior.
-Both detectors also treat `mixHash` as equivalent source text without sufficient
-official support.
-
-C09 replaces these duplicate keyword heuristics with an evidence-backed model of
-Arc-owned PREVRANDAO value dependency. It must not preserve blanket symbol
-matching merely to retain finding count.
-
-## 2. Pinned first-party premise
-
-Current Arc documentation states:
-
-- Arc targets the Prague EVM hard fork;
-- `PREVRANDAO` always returns `0` on Arc;
-- the value does not provide randomness on Arc;
-- bridge contracts must not use `block.prevrandao` for relay shuffling or random
-  selection;
-- bridge integrations should replace such dependency with an external oracle or
-  deterministic round-robin design.
-
-Pinned Arc sources:
-
-- `https://docs.arc.io/integrate/infrastructure`
-- `https://docs.arc.io/integrate/infrastructure/bridges`
-
-Current Solidity documentation states:
-
-- `block.prevrandao` is the post-Paris beacon-chain random value;
-- inline assembly `prevrandao()` is introduced for Paris and later targets;
-- `block.difficulty` becomes a deprecated alias for `block.prevrandao` for
-  post-Paris EVM targets;
-- inline assembly `difficulty()` is disallowed for post-Paris targets.
-
-Pinned Solidity sources:
-
-- `https://docs.soliditylang.org/en/latest/cheatsheet.html`
-- `https://docs.soliditylang.org/en/latest/using-the-compiler.html`
-- `https://docs.soliditylang.org/en/latest/yul.html`
-
-These sources do not establish blanket source-text equivalence between
-`mixHash` and PREVRANDAO.
-
-## 3. Current implementation audit
-
-### Wallet rule
-
-`packages/arcready/rules/wallet/prevrandao-not-supported.ts` currently:
-
-- scans every file discovered for the wallet preset;
-- gates on broad Arc words or Arc Testnet chain ID;
-- matches `block.prevrandao`, `PREVRANDAO`, `prevrandao`, or `mixHash` on any
-  active line;
-- skips obvious comments, documentation lines, and negative guidance;
-- emits one file-level critical finding.
-
-The current wallet test proves only one same-file Arc chain ID and one direct
-`block.prevrandao` assignment. It does not prove a randomness or behavior sink.
-
-### Bridge rule
-
-`packages/arcready/rules/bridge/no-prevrandao-relay-selection.ts` currently:
-
-- scans every file discovered for the bridge preset;
-- gates on broad Arc and bridge words;
-- matches the same PREVRANDAO and `mixHash` keyword set;
-- additionally requires a relay, selection, shuffle, or randomness word on the
-  same line;
-- emits one file-level critical finding.
-
-The current bridge test uses a direct modulo expression, but the detector itself
-does not parse that value dependency.
-
-### Catalog state
-
-Both catalog entries already acknowledge:
-
-- low default confidence;
-- symbol presence does not prove application behavior;
-- same-line relay/randomness words do not establish selection dependency;
-- blanket `mixHash` equivalence is not sufficiently documented.
-
-C09 must resolve those admitted limitations rather than only rename or merge the
-existing regexes.
-
-## 4. Decision: Research / Replace
-
-C09 must not harden either current keyword detector.
-
-The existing public rules are replacement candidates. Research must end in one
-reviewed implementation disposition:
-
-1. **Build shared analyzer with compatibility shells.** Implement one private
-   bounded Solidity analyzer and use thin legacy rule integrations only where
-   preset compatibility requires them.
-2. **Build one consolidated public rule.** Introduce one public rule only when
-   its preset, finding category, public ID, compatibility migration, and inventory
-   behavior are all explicitly reviewed.
-3. **Advice-only migration.** Default-exclude or downgrade the old rules when
-   reliable value dependency cannot be proven within product limits.
-4. **Retire.** Remove unsupported heuristics when neither a bounded analyzer nor
-   useful optional guidance is justified.
-
-`Replace` is the migration action, not the final implementation disposition.
-
-A successful C09 outcome cannot leave both current critical keyword heuristics
-unchanged.
-
-## 5. Public-ID and preset constraint
-
-ArcReady currently has only three runtime presets and rule categories:
-
-```text
-wallet
-bridge
-app-kit
-```
-
-The `solidity` value currently exists only as an internal rule-pack label. It is
-not a runtime preset or a public finding category.
-
-C09 must not add a new `solidity` preset merely to obtain a cleaner rule name.
-Doing so would widen config schemas, CLI behavior, project detection, reporters,
-fixtures, documentation, and compatibility contracts.
-
-The research decision must compare these bounded options:
-
-### Option A — shared private analyzer, two temporary public shells
-
-- one parser and evidence model;
-- legacy wallet and bridge rule IDs remain temporarily;
-- each shell emits only analyzer records applicable to its preset contract;
-- duplicate execution and duplicate findings are prevented;
-- one later migration may retire or consolidate the shells.
-
-### Option B — one existing ID survives
-
-- choose either wallet or bridge ID as the public rule;
-- document why that preset truthfully represents all supported sinks;
-- define behavior when only the other preset is selected;
-- deprecate or retire the other ID without silently losing coverage.
-
-### Option C — one new public ID
-
-- introduce a new ID only after explicitly reviewing its existing-preset
-  placement;
-- do not add a new runtime preset or category in C09;
-- provide a bounded compatibility period for both old IDs;
-- keep deterministic order and inventory counts explicit.
-
-C09-D must select exactly one option before production integration begins.
-
-## 6. Candidate bounded source surface
-
-The private feasibility prototype may inspect plain Solidity `.sol` files only.
-It must fail closed for unsupported syntax.
-
-Initial exact source candidates:
-
-- direct `block.prevrandao` expression;
-- direct inline assembly `prevrandao()` result;
-- optional `block.difficulty` only when the same repository proves a post-Paris
-  or later EVM target through an exact supported compiler configuration;
-- direct or one single-assignment same-function local binding;
-- no arbitrary bare `PREVRANDAO` identifiers;
-- no blanket `mixHash` matching;
-- no JavaScript, TypeScript, JSON, YAML, Markdown, or prose matching.
-
-Supporting `block.difficulty` without proven compiler/EVM-target context is not
-approved. Supporting inline assembly does not authorize general Yul analysis.
-
-### Parser and dependency feasibility
-
-The package currently depends on TypeScript and does not include a Solidity
-parser. C09 must not assume that the TypeScript compiler can parse Solidity or
-prove contract/function ownership.
-
-C09-R1 must compare bounded parser inputs:
-
-- a maintained Solidity parser dependency;
-- compiler-produced standard JSON AST supplied as research input;
-- a deliberately narrow custom tokenizer/parser for only the approved grammar.
-
-The comparison must record:
-
-- supported Solidity and Yul versions;
-- malformed-source and recovery behavior;
-- source offsets and deterministic AST ownership;
-- licensing, maintenance, package size, and supply-chain risk;
-- test-only versus production dependency cost;
-- whether generated or compiler AST input would change the user workflow;
-- fail-closed behavior for unsupported syntax.
-
-A research prototype may use a temporary test-only parser dependency or retained
-AST fixture. No production dependency or compiler requirement is authorized
-before C09-D selects an implementation architecture.
-
-## 7. Candidate reportable dependencies
-
-A source occurrence is not reportable merely because it reads PREVRANDAO.
-
-A candidate critical or warning finding must prove that a supported value reaches
-one direct behavior sink inside the same function and same contract candidate.
-
-Initial sink families for feasibility testing:
-
-- modulo or index selection from a non-empty collection;
-- relay, validator, sequencer, committee, winner, or recipient selection;
-- direct shuffle or ordering key;
-- direct lottery, raffle, allocation, assignment, or sampling decision;
-- direct authorization or eligibility branch;
-- direct storage of a value explicitly named and consumed as a randomness seed
-  within the same bounded function.
-
-The prototype must distinguish:
-
-- reading or logging the value;
-- returning the value from a diagnostic function;
-- comparing the value to zero as a compatibility check;
-- hashing the value without a supported behavioral sink;
-- storing an unused value;
-- using the value in a reportable decision.
-
-Only the last class is a candidate compatibility finding.
-
-## 8. Arc ownership contract
-
-C09 must not borrow Arc ownership from unrelated repository text.
-
-Research must test bounded ownership sources such as:
-
-- exact Arc Testnet chain ID in a supported deployment configuration;
-- exact official Arc RPC or imported `arcTestnet` evidence in a same-project
-  deployment surface;
-- an exact supported Foundry or Hardhat network configuration associated with
-  the contract deployment path;
-- explicit Arc-only contract or deployment naming only when paired with stronger
-  configuration evidence.
-
-Unsupported ownership includes:
-
-- an arbitrary `Arc` comment or string;
-- README or documentation prose;
-- an unrelated wallet or bridge file elsewhere in the repository;
-- a multichain configuration without contract-to-network association;
-- imported or computed network values that cannot be resolved safely;
-- a Solidity contract with no deployment ownership evidence.
-
-A `.sol`-only parser cannot prove that the contract is deployed to Arc merely
-because another repository file mentions Arc.
-
-C09-R3 must therefore separate ownership feasibility:
-
-### C09-R3-A — source and value-dependency feasibility
-
-- evaluate Solidity source ownership, function ownership, bounded local flow, and
-  supported sinks using explicit synthetic ownership input in the research
-  harness;
-- do not treat that harness input as proof that production repository ownership
-  exists;
-- determine whether the parser can classify source/value behavior independently
-  of deployment association.
-
-### C09-R3-B — deployment-association feasibility
-
-- separately test one bounded association between a Solidity contract and an
-  exact Arc deployment configuration;
-- define the accepted file types, directory relationship, contract/deployment
-  identifier ownership, ambiguity rules, and deterministic ordering;
-- fail closed for imported, computed, multichain, duplicate, or conflicting
-  deployment configuration;
-- treat meaningful production emission as blocked when no reviewed association
-  can prove that the analyzed contract targets Arc.
-
-The first production implementation must not silently convert synthetic R3-A
-ownership into repository evidence. Wider project association requires a
-separate reviewed capability.
-
-## 9. Required source corpus
-
-C09-R2 must materialize complete-source fixtures with unique IDs and expected
-classification. The corpus must separate source evidence, Arc ownership,
-value-flow evidence, sink ownership, and public-emission eligibility.
-
-### Positive candidate dimensions
-
-- direct `block.prevrandao % relayers.length`;
-- direct cast then modulo;
-- one single-assignment local seed binding then direct modulo;
-- direct relay or winner array indexing;
-- exact direct authorization branch derived from PREVRANDAO;
-- exact inline assembly `prevrandao()` with a supported direct sink;
-- both LF and CRLF;
-- one supported Arc ownership shape.
-
-### Safe or non-reportable dimensions
-
-- value read but unused;
-- logging, event emission, debug return, or diagnostics;
-- explicit zero-compatibility assertion;
-- comment, documentation, string, test description, and identifier name;
-- negative guidance;
-- hashing without a supported sink;
-- dead assignment;
-- Ethereum-only or unknown deployment ownership;
-- a correct deterministic replacement;
-- a file that mentions Arc but deploys elsewhere.
-
-### Unsupported dimensions
-
-- aliases deeper than the approved bound;
-- mutation, reassignment, branch joins, loops, recursion, callbacks, or modifiers;
-- imported values or inherited helper functions;
-- cross-contract and cross-file flow;
-- computed array, collection, or sink ownership;
-- assembly blocks beyond exact direct `prevrandao()` extraction;
-- unknown compiler or EVM target for `block.difficulty`;
-- inline assembly `difficulty()`;
-- arbitrary `mixHash` identifiers;
-- malformed Solidity;
-- generated sources and vendored dependencies unless explicitly in scan scope.
-
-### Adversarial dimensions
-
-- unrelated PREVRANDAO read and relay words on the same line;
-- relay selection and PREVRANDAO in different functions;
-- multiple contracts in one file;
-- supported source occurrence owned by one contract and sink owned by another;
-- comments between tokens;
-- shadowed local variables;
-- duplicate declarations;
-- source strings containing Solidity snippets;
-- a value overwritten before the sink;
-- a sink that uses another seed;
-- collection length zero or unknown when the expression depends on modulo;
-- multiple candidates with deterministic earliest selection.
-
-## 10. Research phases
-
-### C09-R1 — premise, inventory, and architecture audit
-
-- pin current Arc and Solidity semantics;
-- inventory both public IDs, exports, presets, catalog metadata, tests, fixtures,
-  reporters, and default finding-count impact;
-- document public preset/category constraints;
-- inventory Solidity parser, compiler-AST, and narrow-tokenizer options;
-- record parser version coverage, malformed-source behavior, licensing,
-  maintenance, supply-chain, and production-dependency cost;
-- remove blanket `mixHash` equivalence from the proposed premise;
-- define the minimum Arc ownership and value-dependency evidence.
-
-### C09-R2 — complete-source corpus
-
-- materialize the required positive, safe, unsupported, and adversarial cases;
-- record separate internal classifications for source, ownership, dependency,
-  sink, and public-emission eligibility;
-- include exact old-rule false positives and false negatives;
-- add machine validation for fixture IDs and expected fields.
-
-### C09-R3 — private disposable feasibility prototype
-
-#### R3-A — parser, source, and dependency experiment
-
-- use only the reviewed research parser input selected by R1;
-- parse Solidity without changing public rule behavior;
-- use explicit synthetic Arc ownership input only to isolate parser and
-  value-dependency feasibility;
-- prove exact contract/function source ownership, bounded local flow, and
-  supported direct sinks;
-- evaluate direct `block.prevrandao` first;
-- evaluate inline assembly and `block.difficulty` only as separate bounded
-  families;
-- run the complete corpus and source-level pressure shapes.
-
-#### R3-B — bounded Arc deployment association
-
-- test one explicit association between the analyzed contract and an exact Arc
-  deployment configuration;
-- keep file types, directory relation, identifiers, ambiguity, and conflict
-  handling bounded and deterministic;
-- run deployment-association false-positive and false-negative pressure cases;
-- report production public-emission eligibility as blocked when the association
-  cannot be proven.
-
-Discard the prototype if either experiment requires a general Solidity data-flow
-platform, unrestricted cross-file analysis, or an unreviewed production parser
-dependency.
-
-### C09-D — implementation and migration decision
-
-Independent review must select:
-
-- shared analyzer with compatibility shells;
-- one surviving existing ID;
-- one new ID under an existing preset;
-- Advice-only migration; or
-- Retire.
-
-The decision must also pin:
-
-- final rule ID or temporary IDs;
-- preset registration and finding category;
-- default severity and confidence;
-- old-ID deprecation or removal behavior;
-- inventory and fixture-count changes;
-- duplicate prevention and deterministic order;
-- canonical FindingV2 eligibility or explicit non-eligibility.
-
-No production implementation begins before C09-D is approved.
-
-## 11. Build phases if authorized
-
-Only a C09-D Build disposition may authorize these phases.
-
-### C09-E1 — parser and source ownership
-
-- implement the approved private parser boundary;
-- recognize only approved source forms;
-- reject `mixHash` and unsupported `block.difficulty` cases;
-- prove supported Arc deployment ownership;
-- emit private records only.
-
-### C09-E2 — bounded dependency and sink proof
-
-- prove direct or approved one-binding local value flow;
-- prove exact supported behavior sinks;
-- fail closed for mutation, aliases, joins, cross-function flow, and unsupported
-  assembly;
-- maintain deterministic offsets and classifications.
-
-### C09-E3 — public integration and legacy migration
-
-- integrate only the C09-D-approved public-ID strategy;
-- prevent duplicate execution and findings across wallet and bridge presets;
-- update catalog, docs, tests, inventory, fixtures, scoring, reporters, and CLI
-  expectations intentionally;
-- retain or deprecate old IDs only as explicitly approved;
-- do not introduce a new runtime preset or generic plugin registry.
-
-### C09-E4 — closeout
-
-- independently review every semantic phase;
-- run full repository verification;
-- record final IDs, counts, supported grammar, unsupported cases, and expansion
-  triggers;
-- move this plan to completed only after merge evidence is recorded.
-
-## 12. Non-goals
-
-C09 does not include:
-
-- a general Solidity AST, CFG, SSA, taint, symbolic-execution, or data-flow
-  platform;
-- vulnerability analysis or randomness-quality auditing outside the Arc
-  compatibility premise;
-- runtime deployment verification or RPC calls;
-- oracle selection or implementation;
-- cross-file inheritance or library resolution;
-- arbitrary Yul analysis;
-- blanket `mixHash` equivalence;
-- automatic support for all compiler versions or EVM targets;
-- a new `solidity` runtime preset or public category;
-- changes to canonical FindingV2 before a separate eligibility review;
-- C10 App Kit implementation.
-
-## 13. Risk controls
-
-- keep research artifacts private or under `docs/research` and test-only scope;
-- do not add a production Solidity parser dependency before C09-D;
-- do not change either production rule during R1 through R3;
-- use complete-source fixtures rather than keyword obligations;
-- keep source recognition, Arc ownership, value dependency, sink proof, and
-  public emission as separate internal decisions;
-- prefer bounded false negatives over critical false positives;
-- preserve current public IDs until C09-D selects a migration;
-- no force push or history rewriting;
-- every semantic phase requires independent blocker, major, and minor counts;
-- stop and redesign if one shared rule requires a new runtime preset or a general
-  analyzer framework.
-
-## 14. Planning validation
-
-This planning PR changes executable behavior: none.
-
-Required checks:
-
-```powershell
-corepack pnpm exec prettier --check docs/exec-plans/active/C09.md
-git diff --check
-```
-
-The plan requires independent review before merge.
-
-## 15. Exit criteria
-
-C09 planning is complete only when:
-
-- official Arc and Solidity semantics are pinned without contradiction;
-- the unsupported blanket `mixHash` premise is explicitly removed;
-- current false-positive and false-negative classes are documented;
-- the Arc ownership boundary separates synthetic source experiments from
-  production deployment association;
-- parser and dependency feasibility is explicitly gated;
-- reportable value-dependency and sink families are explicit;
-- public-ID and preset constraints are documented;
-- the corpus and prototype phases are bounded;
-- no production implementation is authorized by the plan itself;
-- independent review reports `APPROVE` with zero blocker, major, and minor
-  findings.
-
-C09 implementation is complete only after a later C09-D disposition and all
-authorized build or migration phases are merged, reviewed, verified, and closed
-out.

From 2addb2c67422af9566a140392d2955faeefd2cc4 Mon Sep 17 00:00:00 2001
From: Tan <iammaithanhtan@gmail.com>
Date: Tue, 18 Aug 2026 17:00:56 +0700
Subject: [PATCH 6/7] docs: close C09A roadmap milestone

---
 docs/roadmap.md | 74 ++++++++++++++++++++++++++++++++-----------------
 1 file changed, 49 insertions(+), 25 deletions(-)

diff --git a/docs/roadmap.md b/docs/roadmap.md
index 5bc8275..92a98c8 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -1,7 +1,7 @@
 # ArcReady Roadmap
 
-**Status:** Active roadmap after C09-D Build selection
-**Last reviewed:** 2026-08-06
+**Status:** Active roadmap after C09A closeout
+**Last reviewed:** 2026-08-18
 
 ArcReady is an Arc-specific, repository-level static compatibility analyzer for
 projects being ported from Ethereum or other EVM environments to Arc.
@@ -63,7 +63,9 @@ ArcReady currently includes:
 - rule taxonomy, maturity, confidence, documentation, and detector-limitation
   metadata;
 - deterministic private FindingV2, CoverageV2, ScanResultV2, and `json-v2`
-  contracts.
+  contracts;
+- bounded Solidity PREVRANDAO source/value analysis with exact retained Foundry
+  Arc ownership for the C09A compatibility shells.
 
 The private canonical runtime remains exactly four rules in stable order:
 
@@ -89,6 +91,10 @@ ArcReady still has no general:
 - SARIF, baseline, or suppression workflow;
 - precise line-and-column FindingV2 regions.
 
+C09A adds one bounded Solidity parser-backed capability for a prioritized Arc
+compatibility problem; it does not establish a general Solidity analysis
+platform.
+
 These limits are intentional. Infrastructure is justified only when it unlocks
 a prioritized rule with clear product value.
 
@@ -221,31 +227,49 @@ Inventory is now 19 known / 16 default / 7 wallet / 4 canonical. The R3
 prototype remains research-only. Revisit Retire after one compatibility period
 or earlier if usage evidence shows no material value.
 
-### C09 — Build selected: bounded PREVRANDAO dependency analyzer
+### C09 / C09A — Complete: bounded PREVRANDAO dependency analyzer
+
+C09-R1 through R3-B established bounded Solidity source/value feasibility and one
+exact Foundry contract-to-Arc association family. C09-D selected Build: one
+private analyzer with two temporary public compatibility shells.
 
-C09-R1 through R3-B are complete. The reviewed research established bounded
-Solidity source/value feasibility and one exact Foundry contract-to-Arc
-association family.
+C09A implemented that decision in four production phases plus closeout:
 
-C09-D selects Build: one private analyzer with two temporary public compatibility
-shells. Both old keyword detectors must be removed. A critical finding requires
-both a supported same-function behavior dependency and exact Foundry Arc
-deployment ownership for the same concrete contract.
+- PR #63 / E1: exact `@solidity-parser/parser@0.20.2` dependency and private
+  Solidity source analysis;
+- PR #65 / E2: bounded same-function value flow, supported sinks, shell routing,
+  and scan-scoped reuse;
+- PR #68 / E3: exact Foundry ownership and composed eligibility;
+- PR #67 / E4: public compatibility-shell migration and removal of broad keyword
+  emission;
+- E5: final documentation/governance closeout.
 
-C09A is the next implementation milestone. It must retain the two public IDs,
-prevent duplicate findings, add no `solidity` preset or category, preserve
-inventory `19 / 16 / 7 / 4`, and keep the rules non-canonical. Production remains
-blocked until the decision and implementation plan are approved and merged.
+A public finding now requires both a supported same-function behavior dependency
+and exact retained Foundry Arc Testnet ownership for the same concrete contract.
+The two existing public IDs remain default-critical temporary compatibility
+shells, duplicate emission is prevented, no `solidity` preset or category was
+added, inventory remains `19 / 16 / 7 / 4`, and both rules remain non-canonical.
 
-### C10 — Research/build: versioned App Kit compatibility
+Foundry evidence is static retained artifact evidence only. C09A does not claim
+live deployment, bytecode identity, runtime behavior, or transaction success.
+The completed plans are:
+
+```text
+docs/exec-plans/completed/C09.md
+docs/exec-plans/completed/C09A.md
+```
+
+### C10 — Next: versioned App Kit compatibility
 
 Model official versioned chain identifiers, operations, tokens, adapters, and
 support tables. Do not keep hardening the deprecated generic capability guard.
 
+C10 should remain bounded to versioned first-party compatibility evidence and
+must not expand ArcReady into a generic App Kit or TypeScript analysis platform.
+
 ## Adoption and developer-experience track
 
-With C07C integration complete, prioritize product usefulness before expanding
-deep semantic infrastructure:
+Prioritize product usefulness before expanding deep semantic infrastructure:
 
 1. maintain a small public broken/fixed demo project;
 2. improve onboarding and GitHub Action usage;
@@ -301,13 +325,13 @@ The following remain outside the near-term roadmap:
 
 ## Current recommended next step
 
-1. Review and implement C09A as a bounded analyzer and compatibility-shell
-   migration.
-2. Continue C10 after C09A closeout unless new user evidence changes priority.
-3. Keep native write analysis blocked pending first-party premise clarification.
-4. Continue gathering real unsupported-pattern and false-positive/negative
-   evidence.
+1. Plan C10 as a bounded versioned App Kit compatibility milestone.
+2. Keep native write analysis blocked pending first-party premise clarification.
+3. Continue gathering real unsupported-pattern and false-positive/negative
+   evidence, including C09A compatibility-shell usage evidence.
+4. Revisit C09A shell consolidation or retirement only through a separately
+   reviewed compatibility decision.
 5. Reopen deferred C06B2, C07C, or C08 families only from concrete usage
    evidence or a separately approved milestone.
 
-The private canonical runtime remained exactly four rules throughout C07C.
+The private canonical runtime remains exactly four rules.

From 8e2785f7d67303cc98014edd260367d5353d5095 Mon Sep 17 00:00:00 2001
From: Tan <iammaithanhtan@gmail.com>
Date: Tue, 18 Aug 2026 17:01:25 +0700
Subject: [PATCH 7/7] docs: close C09A backlog sequencing

---
 docs/rule-development-backlog.md | 69 ++++++++++++++++++--------------
 1 file changed, 40 insertions(+), 29 deletions(-)

diff --git a/docs/rule-development-backlog.md b/docs/rule-development-backlog.md
index ad77985..826b8f3 100644
--- a/docs/rule-development-backlog.md
+++ b/docs/rule-development-backlog.md
@@ -1,7 +1,7 @@
 # ArcReady Rule Development Backlog
 
 **Status:** Active decision record
-**Last reviewed:** 2026-08-06
+**Last reviewed:** 2026-08-18
 **Applies to:** Active and proposed ArcReady static-analysis rules
 
 ## Purpose
@@ -93,14 +93,12 @@ The private canonical runtime remains exactly four rules.
   E1, E2, and E3 on 2026-08-04.
 - Native write analysis is Research and blocked by contradictory first-party raw
   `value` decimal premises.
-- The completed write surface is an exact viem local-account
-  transfer to canonical Arc USDC using one exact client, request, and direct
-  nonzero `parseEther` literal.
+- The completed write surface is an exact viem local-account transfer to
+  canonical Arc USDC using one exact client, request, and direct nonzero
+  `parseEther` literal.
 - The thin existing-rule integration defines one private write-candidate kind
   and a deterministic at-most-one read/write selection policy while preserving
-  C06B1 behavior when no write candidate exists. Candidate offsets are private
-  ordering metadata, emitted findings remain file-level, and expression-level
-  output is deferred to a separate R3 prerequisite.
+  C06B1 behavior when no write candidate exists.
 - E1, E2, and E3 each received an independent `APPROVE` with zero blocker,
   major, and minor findings. The final `corepack pnpm verify:full` gate passed
   before merge.
@@ -125,13 +123,20 @@ The private canonical runtime remains exactly four rules.
 
 ### `wallet/PREVRANDAO_NOT_SUPPORTED`
 
-- Decision: C09A compatibility-shell migration implemented; closeout pending.
-- Priority: P1.
+- Decision: Complete for C09A bounded compatibility-shell migration.
+- Priority: P1 compatibility maintenance only.
 - Impact: Required change.
-- Retain as a temporary compatibility shell over one shared private analyzer.
-- Emit only exact owned non-bridge records when this shell is selected.
-- Remove the current keyword detector and all blanket `mixHash` equivalence.
-- Preserve non-canonical status and inventory during the compatibility period.
+- Canonical status: Non-canonical.
+- Retained as a temporary compatibility shell over one shared private analyzer.
+- Emits only exact owned non-bridge records when this shell is selected.
+- Broad PREVRANDAO keyword detection and blanket `mixHash` equivalence are no
+  longer the public emission path.
+- Public emission requires bounded same-function behavior evidence plus exact
+  retained Foundry Arc Testnet ownership for the same concrete contract.
+- Preserve default-critical behavior and inventory during the compatibility
+  period.
+- Revisit consolidation or retirement only through a separately reviewed
+  compatibility decision backed by real usage evidence.
 
 ### `wallet/NO_ETH_GAS_LABEL`
 
@@ -196,14 +201,20 @@ It must not be used as an implementation base.
 
 ### `bridge/NO_PREVRANDAO_RELAY_SELECTION`
 
-- Decision: C09A compatibility-shell migration implemented; closeout pending.
-- Priority: P1.
+- Decision: Complete for C09A bounded compatibility-shell migration.
+- Priority: P1 compatibility maintenance only.
 - Impact: Required change.
-- Retain as a temporary relay/validator/sequencer compatibility shell over the
-  shared private analyzer.
-- Emit only exact owned bridge-relay records when this shell is selected.
-- Remove the current keyword detector and prevent cross-shell duplication.
-- Preserve non-canonical status and inventory during the compatibility period.
+- Canonical status: Non-canonical.
+- Retained as the temporary relay/validator/sequencer compatibility shell over
+  the shared private analyzer.
+- Emits only exact owned bridge-relay records when this shell is selected.
+- Broad keyword emission was removed and cross-shell duplication is prevented.
+- Public emission requires bounded same-function behavior evidence plus exact
+  retained Foundry Arc Testnet ownership for the same concrete contract.
+- Preserve default-critical behavior and inventory during the compatibility
+  period.
+- Revisit consolidation or retirement only through a separately reviewed
+  compatibility decision backed by real usage evidence.
 
 ### `bridge/BRIDGE_CONFIRMATIONS_ONE`
 
@@ -216,8 +227,8 @@ It must not be used as an implementation base.
 
 ### `app-kit/APPKIT_CHAIN_IDENTIFIER_VALID`
 
-- Decision: Build.
-- Priority: P2.
+- Decision: Build under the next C10 versioned App Kit compatibility milestone.
+- Priority: P0 next sequenced work.
 - Impact: Blocker.
 - Requires version-aware App Kit argument or configuration ownership.
 
@@ -232,7 +243,8 @@ It must not be used as an implementation base.
 
 - Decision: Replace.
 - Priority: P2.
-- Design a versioned compatibility rule from official support tables.
+- Design a versioned compatibility rule from official support tables in C10;
+  do not keep hardening the deprecated generic capability guard.
 
 ### `app-kit/APPKIT_CUSTOM_RPC_RECOMMENDED`
 
@@ -277,14 +289,13 @@ C06B2  Complete: exact direct viem parseEther write MVP; native remains blocked
 C08-D  Complete: Advice-only disposition selected
 C08A   Complete: default-excluded deprecated attestation advice
 C09-D  Complete: bounded Build disposition selected
-C09A   Next: implement private analyzer and compatibility shells
-C10    Then: add versioned App Kit compatibility analysis
+C09A   Complete: bounded PREVRANDAO analyzer and compatibility shells
+C10    Next: versioned App Kit compatibility analysis
 ```
 
-C09-R1, C09-R2, C09-R3-A, and C09-R3-B are complete. C09-D selects Build, and
-C09A is the next approved sequencing target. Production remains blocked until
-the decision and implementation plan merge. The compatibility inventory target
-remains `19 known / 16 default / 7 wallet / 4 canonical`. Other analyzer
+C09-R1 through C09-R3-B, C09-D, and C09A E1-E5 are complete. The final C09A
+compatibility inventory remains `19 known / 16 default / 7 wallet / 4 canonical`.
+C10 is the next approved sequencing target after closeout. Other analyzer
 expansion should not interrupt this sequence without real user evidence.
 
 ## Expansion triggers