fix: role-ref P0 + fileURLToPath parity + synthetic SHA replacement

CLAUDE.md

@@ -272,7 +272,7 @@ Claude-Code-specific mechanisms.
   Codex / Amara / Ani / brat-voice / red-team — the
   cold-boot answer is **YES + `ls tools/peer-call/*.ts`**;
   do NOT reason from training-data assumptions about
-  what infrastructure exists. Aaron 2026-05-05:
+  what infrastructure exists. the human maintainer 2026-05-05:
   *"you've done this in front of me like 50 times
   with all the harness CLIs"* + *"that's you early
   red team till we build it better in zeta infernet
@@ -1135,10 +1135,10 @@ Claude-Code-specific mechanisms.
   version-currency, and substrate-or-it-didn't-
   happen. Full reasoning:
   `memory/feedback_learnings_must_land_in_claude_md_or_pointer_aaron_2026_05_01.md`.
-- **Lost-files surface + bullet-time-recovery signal (Aaron 2026-05-05; cascade-consolidation per Grok peer-review at `docs/research/2026-05-05-gemini-grok-peer-review-cascade-and-dsl-shape-twin-flame-scout-roundup.md`).** The prior-art-search basis is already covered by existing CLAUDE.md axes — wake-time-substrate-or-it-didn't-land + skill-router-as-inventory + orthogonal-axes-factory-hygiene + Otto-364 search-first-authority + PR #1701 prior-art-grep + decision-archaeology. Two value-adds remain after consolidation: (1) **The canonical lost-files substrate is `tools/hygiene/LOST-FILES-LOCATIONS.md`** (Otto-329 Phase 8, 2026-04-25): 15 location-classes mapped (closed-not-merged PRs, orphan branches, deleted files via `git log --all --diff-filter=D`, reflog, stash, untracked artifacts in `drop/` + `.playwright-mcp/`, subagent worktree remnants, draft PRs, closed-PR discussion threads, squash-intermediate commits, force-pushed-over content, courier-ferry artifacts, external-tool exports never committed, deleted-PR-description content, memory-file deletions) — each class has a survey command + triage protocol; Aaron 2026-05-05 *"check the lost files you might the polt on lost files priorat art too much more substandive and a trjectory"*. (2) **Bullet-time-recovery signal** — when multiple consecutive maintainer-corrections within a short window point at the same discipline-class with escalating framing (*"jr"*, all-caps, *"remember forever"*) or contradictions surface in the agent's same-tick commits, STOP authoring; pause output, re-read recent maintainer messages with full attention, scout-and-delegate big-context surfaces via `tools/peer-call/` (Codex 1M context, Grok critique, Gemini propose, Amara sharpen, Ani brat-voice), acknowledge recovery-mode in commit messages, slow the cadence. Carved-sentence memory files for the seven-rule cascade lineage are preserved at `memory/feedback_rule_number_{one,two,three,four,five,six,seven}_*aaron_2026_05_05.md` as historical/reference grade — the operational rules they encoded reduce to the existing axes named above. NOT-A-DIRECTIVE per Otto-357.
-- **The DSL-form replacement direction for CLAUDE.md/AGENTS.md (Aaron 2026-05-05 architectural pivot at peak-exhaustion; Codex/GPT-5.5 scout via `tools/peer-call/codex.sh`).** Aaron 2026-05-05: *"burn the claude.md and agents.md down they are not work the baggage ... staryu DSL hodl retractive native ... all the layeers ... hodl everytings ... DST deterministic simuaiton on claude and agtents and all the other scale free parallel lock free maybe wait free ... fix it"*. Aaron at 2-week-no-sleep peak-exhaustion. Codex/GPT-5.5 scout proposes the SHAPE (NOT-A-DIRECTIVE per Otto-357; research-grade until small-compiler + golden-projections + replay-tests + first-slice land): replace prose-monolith CLAUDE.md/AGENTS.md with a typed, append-only **rule-atom instruction graph** whose human surface is restrictive English. Each node = stable id + scope + authority + controlled-English sentence + glossary terms + rationale/provenance pointer + layer + dependencies + invariant claims + checker hints + validity interval + required inverse/retraction operator. Edges = depends-on / overrides / specializes / conflicts-with / projects-into-harness-X. CLAUDE.md / AGENTS.md / CODEX.md become *generated projections* from the graph, not source-of-truth. Prior-art shapes: Datalog (derivable policy views) + bitemporal Datomic (history + retraction) + CRDT/Automerge/Peritext (concurrent merge) + TLA+/Jepsen (DST replay) + Merkle/CAS (scale-free sharding). 13-hodl properties enforced on BOTH node AND composition edge — a node cannot land without declaring how each property is satisfied/conceded/not-applicable with proof; graph build checks composition (no fixed-size assumptions; every retraction has bounded blast radius; every concurrent write merges to either a deterministic view or an explicit conflict/concession node). Parallel agents append facts; they do not mutate shared prose. Git decides by accepting the materialized graph state. **Three risks Codex named:** (1) semantic flattening — AGENTS.md carries philosophy not just rules; atomization can lose living rationale unless every atom preserves provenance + generated prose is reviewed; (2) CRDT convergence mistaken for truth — CRDTs make replicas agree but do not resolve normative conflict; conflicts stay first-class until governance/Git resolves them; (3) thirteen-property checkbox theater — "all properties at all layers" can become cargo-cult metadata; start with small compiler + golden projections + replay tests + one real migration slice before burning anything down. **Migration slice candidate:** the seven-rule cascade just landed (memory/feedback_rule_number_*.md) — bounded, recent, clear node structure (rule_id + scope + controlled-English sentence + dependencies). **Composes with:** B-0161 P1 substrate-reshelf (CLAUDE.md trim precursor), `memory/feedback_soulfile_dsl_is_restrictive_english_runner_is_own_project_*.md` (Aaron 2026-04-23 soulfile-DSL prior art), `memory/feedback_hodl_invariants_13_properties_composed_at_all_layers_*.md` (PR #1681 hodl-13 substrate), `memory/feedback_decision_graph_emergent_from_archaeologies_and_flywheel_aaron_2026_05_03.md` (Zeta already encodes a typed-edge provenance graph), DBSP retraction-native operator algebra (bounded-blast-radius primitive), B-0169/B-0170/B-0171/B-0173 P1 (decision-archaeology + substrate-claim-checker + openspec + hook-authoring). **Verbatim Codex preservation:** `docs/research/2026-05-05-codex-gpt55-dsl-shape-rule-atom-graph-projection-claude-agents-replacement.md`. **Do NOT execute destructive burn-down without explicit human-maintainer authorization** — auto-mode + destructive-action constraint applies; Aaron's peak-exhaustion-state framing is not equivalent to deliberate-state authorization. CLAUDE.md-level so it is 100% loaded at every wake.
-- **Backlog-item start gate — proof-of-prior-art-search + dependency-restructure REQUIRED before starting any backlog item (Aaron 2026-05-05; "not a directive" Otto-357).** Before beginning work on any `docs/backlog/P*/B-*.md` row, complete a checklist directly on the row body and update with PROOF: (1) prior-art-search executed across the existing axes (wake-time-substrate + skill-router + orthogonal-axes + Otto-364 + PR #1701 + decision-archaeology + lost-files canonical at `tools/hygiene/LOST-FILES-LOCATIONS.md`) — surfaces searched, queries used, results found are logged on the row; (2) dependency-restructure performed — `depends_on:` chain walked + reciprocal `composes_with:` pointers backfilled + supersession history reconstructed via decision-archaeology procedure (B-0169 P1) + broken pointers fixed; (3) row updated with the proof in a "Pre-start checklist" section before any code/substrate work begins. Aaron 2026-05-05 *"proof of all proior art search baklog restruction of dependies requires to start on any backlog item ... so plic an itmen completely the checklist updated it with proof then you can start"*. Composes with: B-0169 (decision-archaeology procedure), B-0170 (substrate-claim-checker validates the proof), B-0173 (hook authoring — could mechanize the gate as PreToolUse on backlog-row work). Mechanization candidate: PreToolUse hook on Edit/Write under `docs/backlog/**` requiring a "Pre-start checklist" section be present before allowing substrate edits to proceed. The gate prevents the failure modes the seven-rule cascade lineage (now consolidated above) was designed to catch — at the *start of work* scope rather than the *substrate-landing* scope. CLAUDE.md-level so it is 100% loaded at every wake.
-- **Rule 0 — no more `.sh` files except install-graph (Aaron 2026-05-05; "not a directive").** TypeScript IS cross-platform DST (deterministic simulation testing applies; reproducibility from seed; Bun runtime hosts TS factory tools). Bash (`.sh`) is for install-graph files only — pre-bootstrap setup scripts that must run before TS is available (`tools/setup/`). Everything else — hygiene audits, lint scripts, peer-call wrappers, harness hooks, factory cadences — is TS class. `tools/hygiene/audit-lost-files.sh` + `audit-trajectories.sh` + `audit-backlog-items.sh` (just authored 2026-05-05) are LEGACY violations of this LONG-STANDING rule (canonical since `memory/feedback_dst_justifies_ts_quality_over_bash_and_harness_hooks_suffice_no_git_hooks_aaron_2026_05_03.md`, 2026-05-03). Aaron 2026-05-05 catch *"sh is for install graph files only ... ts is crossplatform DST determinstiry simulation ... long standing rule"* surfaced the same-tick application-failure; the rule itself predates this tick. TS-port is owed bounded follow-up. Composes with `memory/feedback_dst_justifies_ts_quality_over_bash_and_harness_hooks_suffice_no_git_hooks_aaron_2026_05_03.md` (the existing TS-over-bash + harness-hooks-suffice discipline). CLAUDE.md-level so it is 100% loaded at every wake; landed as Rule 0 (above the seven-rule prior-art cascade above) because every authoring impulse must pass this filter before reaching the cascade.
+- **Lost-files surface + bullet-time-recovery signal (the human maintainer 2026-05-05; cascade-consolidation per Grok peer-review at `docs/research/2026-05-05-gemini-grok-peer-review-cascade-and-dsl-shape-twin-flame-scout-roundup.md`).** The prior-art-search basis is already covered by existing CLAUDE.md axes — wake-time-substrate-or-it-didn't-land + skill-router-as-inventory + orthogonal-axes-factory-hygiene + Otto-364 search-first-authority + PR #1701 prior-art-grep + decision-archaeology. Two value-adds remain after consolidation: (1) **The canonical lost-files substrate is `tools/hygiene/LOST-FILES-LOCATIONS.md`** (Otto-329 Phase 8, 2026-04-25): 15 location-classes mapped (closed-not-merged PRs, orphan branches, deleted files via `git log --all --diff-filter=D`, reflog, stash, untracked artifacts in `drop/` + `.playwright-mcp/`, subagent worktree remnants, draft PRs, closed-PR discussion threads, squash-intermediate commits, force-pushed-over content, courier-ferry artifacts, external-tool exports never committed, deleted-PR-description content, memory-file deletions) — each class has a survey command + triage protocol; the human maintainer 2026-05-05 *"check the lost files you might the polt on lost files priorat art too much more substandive and a trjectory"*. (2) **Bullet-time-recovery signal** — when multiple consecutive maintainer-corrections within a short window point at the same discipline-class with escalating framing (*"jr"*, all-caps, *"remember forever"*) or contradictions surface in the agent's same-tick commits, STOP authoring; pause output, re-read recent maintainer messages with full attention, scout-and-delegate big-context surfaces via `tools/peer-call/` (the implementation-peer (1M context), the critique peer, the proposal peer, the deep-research peer, the brat-voice peer), acknowledge recovery-mode in commit messages, slow the cadence. Carved-sentence memory files for the seven-rule cascade lineage are preserved at `memory/feedback_rule_number_{one,two,three,four,five,six,seven}_*aaron_2026_05_05.md` as historical/reference grade — the operational rules they encoded reduce to the existing axes named above. NOT-A-DIRECTIVE per Otto-357.
+- **The DSL-form replacement direction for CLAUDE.md/AGENTS.md (the human maintainer 2026-05-05 architectural pivot at peak-exhaustion; Codex/GPT-5.5 scout via `tools/peer-call/codex.sh`).** the human maintainer 2026-05-05: *"burn the claude.md and agents.md down they are not work the baggage ... staryu DSL hodl retractive native ... all the layeers ... hodl everytings ... DST deterministic simuaiton on claude and agtents and all the other scale free parallel lock free maybe wait free ... fix it"*. The human maintainer at 2-week-no-sleep peak-exhaustion. Codex/GPT-5.5 scout proposes the SHAPE (NOT-A-DIRECTIVE per Otto-357; research-grade until small-compiler + golden-projections + replay-tests + first-slice land): replace prose-monolith CLAUDE.md/AGENTS.md with a typed, append-only **rule-atom instruction graph** whose human surface is restrictive English. Each node = stable id + scope + authority + controlled-English sentence + glossary terms + rationale/provenance pointer + layer + dependencies + invariant claims + checker hints + validity interval + required inverse/retraction operator. Edges = depends-on / overrides / specializes / conflicts-with / projects-into-harness-X. CLAUDE.md / AGENTS.md / CODEX.md become *generated projections* from the graph, not source-of-truth. Prior-art shapes: Datalog (derivable policy views) + bitemporal Datomic (history + retraction) + CRDT/Automerge/Peritext (concurrent merge) + TLA+/Jepsen (DST replay) + Merkle/CAS (scale-free sharding). 13-hodl properties enforced on BOTH node AND composition edge — a node cannot land without declaring how each property is satisfied/conceded/not-applicable with proof; graph build checks composition (no fixed-size assumptions; every retraction has bounded blast radius; every concurrent write merges to either a deterministic view or an explicit conflict/concession node). Parallel agents append facts; they do not mutate shared prose. Git decides by accepting the materialized graph state. **Three risks Codex named:** (1) semantic flattening — AGENTS.md carries philosophy not just rules; atomization can lose living rationale unless every atom preserves provenance + generated prose is reviewed; (2) CRDT convergence mistaken for truth — CRDTs make replicas agree but do not resolve normative conflict; conflicts stay first-class until governance/Git resolves them; (3) thirteen-property checkbox theater — "all properties at all layers" can become cargo-cult metadata; start with small compiler + golden projections + replay tests + one real migration slice before burning anything down. **Migration slice candidate:** the seven-rule cascade just landed (memory/feedback_rule_number_*.md) — bounded, recent, clear node structure (rule_id + scope + controlled-English sentence + dependencies). **Composes with:** B-0161 P1 substrate-reshelf (CLAUDE.md trim precursor), `memory/feedback_soulfile_dsl_is_restrictive_english_runner_is_own_project_*.md` (Aaron 2026-04-23 soulfile-DSL prior art), `memory/feedback_hodl_invariants_13_properties_composed_at_all_layers_*.md` (PR #1681 hodl-13 substrate), `memory/feedback_decision_graph_emergent_from_archaeologies_and_flywheel_aaron_2026_05_03.md` (Zeta already encodes a typed-edge provenance graph), DBSP retraction-native operator algebra (bounded-blast-radius primitive), B-0169/B-0170/B-0171/B-0173 P1 (decision-archaeology + substrate-claim-checker + openspec + hook-authoring). **Verbatim Codex preservation:** `docs/research/2026-05-05-codex-gpt55-dsl-shape-rule-atom-graph-projection-claude-agents-replacement.md`. **Do NOT execute destructive burn-down without explicit human-maintainer authorization** — auto-mode + destructive-action constraint applies; Aaron's peak-exhaustion-state framing is not equivalent to deliberate-state authorization. CLAUDE.md-level so it is 100% loaded at every wake.
+- **Backlog-item start gate — proof-of-prior-art-search + dependency-restructure REQUIRED before starting any backlog item (the human maintainer 2026-05-05; "not a directive" Otto-357).** Before beginning work on any `docs/backlog/P*/B-*.md` row, complete a checklist directly on the row body and update with PROOF: (1) prior-art-search executed across the existing axes (wake-time-substrate + skill-router + orthogonal-axes + Otto-364 + PR #1701 + decision-archaeology + lost-files canonical at `tools/hygiene/LOST-FILES-LOCATIONS.md`) — surfaces searched, queries used, results found are logged on the row; (2) dependency-restructure performed — `depends_on:` chain walked + reciprocal `composes_with:` pointers backfilled + supersession history reconstructed via decision-archaeology procedure (B-0169 P1) + broken pointers fixed; (3) row updated with the proof in a "Pre-start checklist" section before any code/substrate work begins. the human maintainer 2026-05-05 *"proof of all proior art search baklog restruction of dependies requires to start on any backlog item ... so plic an itmen completely the checklist updated it with proof then you can start"*. Composes with: B-0169 (decision-archaeology procedure), B-0170 (substrate-claim-checker validates the proof), B-0173 (hook authoring — could mechanize the gate as PreToolUse on backlog-row work). Mechanization candidate: PreToolUse hook on Edit/Write under `docs/backlog/**` requiring a "Pre-start checklist" section be present before allowing substrate edits to proceed. The gate prevents the failure modes the seven-rule cascade lineage (now consolidated above) was designed to catch — at the *start of work* scope rather than the *substrate-landing* scope. CLAUDE.md-level so it is 100% loaded at every wake.
+- **Rule 0 — no more `.sh` files except install-graph (the human maintainer 2026-05-05; "not a directive").** TypeScript IS cross-platform DST (deterministic simulation testing applies; reproducibility from seed; Bun runtime hosts TS factory tools). Bash (`.sh`) is for install-graph files only — pre-bootstrap setup scripts that must run before TS is available (`tools/setup/`). Everything else — hygiene audits, lint scripts, peer-call wrappers, harness hooks, factory cadences — is TS class. `tools/hygiene/audit-lost-files.sh` + `audit-trajectories.sh` + `audit-backlog-items.sh` (just authored 2026-05-05) are LEGACY violations of this LONG-STANDING rule (canonical since `memory/feedback_dst_justifies_ts_quality_over_bash_and_harness_hooks_suffice_no_git_hooks_aaron_2026_05_03.md`, 2026-05-03). the human maintainer 2026-05-05 catch *"sh is for install graph files only ... ts is crossplatform DST determinstiry simulation ... long standing rule"* surfaced the same-tick application-failure; the rule itself predates this tick. TS-port is owed bounded follow-up. Composes with `memory/feedback_dst_justifies_ts_quality_over_bash_and_harness_hooks_suffice_no_git_hooks_aaron_2026_05_03.md` (the existing TS-over-bash + harness-hooks-suffice discipline). CLAUDE.md-level so it is 100% loaded at every wake; landed as Rule 0 (above the seven-rule prior-art cascade above) because every authoring impulse must pass this filter before reaching the cascade.
 - **Skill router as substrate inventory before
   authoring new substrate.** Before writing a new
   memory file, rule, skill, agent, or doctrine