Document interim foundation/trading lane ownership (docs/lanes.md) - #180

Rerun scripts/component_matrix.py --write and
scripts/new_host_grand_list.py --write for the new receipts and hardware
profile. The manifests/evidence.json entries come from the recording and
generation tools. Shared hot-file edits are in the last commit, following
the proposed docs/lanes.md hot-file protocol (#180).

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

…runk, gitleaks (#185)

* Record macos-m5pro-20260924 hardware profile and foundation use receipts

Measure the Mac first seen in #176 with scripts/hardware_profile.py
--record-host (Apple M5 Pro, 18 cores, 24 GB unified memory, arm64) and
record native_proven use-stage receipts for rtk 0.49.0 (rtk git status),
worktrunk 0.79.0 (wt list) and gitleaks 8.30.1 (one-commit scan) with
scripts/host_receipts.py record. Every command ran outside the Claude Code
sandbox, in a scratch clone of main. The receipts await an independent
review, and macos-arm64 stays drafted_not_accepted.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Regenerate evidence reports and register macos-m5pro-20260924 evidence

Rerun scripts/component_matrix.py --write and
scripts/new_host_grand_list.py --write for the new receipts and hardware
profile. The manifests/evidence.json entries come from the recording and
generation tools. Shared hot-file edits are in the last commit, following
the proposed docs/lanes.md hot-file protocol (#180).

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Add independent reviews to the macos-m5pro-20260924 foundation receipts

An independent Claude Code session (a different session identity on the
same Mac) reproduced the recorded commands at bc8cee5 and appended step-8
reviews:

- rtk use receipt: agree. rtk git status proxies a real command and
  returns compacted output.
- gitleaks use receipt: agree. A real redacted scan of one commit with
  the repository config.
- worktrunk use receipt: needs_changes. Beyond wt --version, the only
  command is the read-only wt list. Nothing is created, switched or
  removed, so the worktrees layer's job is not shown. A fresh receipt
  with a create/list/remove cycle in a throwaway repository with
  reviewed hooks addresses it.

With the reviews, verdict_flip_candidates.py reports untested -> accepted
support on macos-arm64 for secrets-credentials/gitleaks,
security-supply-chain/gitleaks and token-efficiency/rtk. Recording the
flips remains a separate record_verdicts.py step.

Regenerated component-evidence-matrix and new-host-grand-list;
host_receipts validate (8), validate.py, component_matrix --check (0
flip-rule violations), new_host_grand_list --check, evidence_manifest
--check and validate_convergence --all-recorded pass.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Re-record macos-m5pro-20260924 worktrunk use receipt with a worktree lifecycle

The independent review at cef7a74 marked the worktrunk use receipt
needs_changes: it ran only wt --version and the read-only wt list. This
fresh recording runs a full lifecycle in a throwaway one-commit git
repository under $TMPDIR: wt switch --create wt-probe, wt list (two
worktrees), wt remove --foreground wt-probe, then wt list, git worktree
list, git branch --list and ls (only main left), and cleanup. All 8
commands exit 0.

Worktrunk hooks were inspected first. There is no user config
(~/.config/worktrunk absent: no user hooks, approvals or custom
worktree-path), no system config, no WORKTRUNK_* override and no project
.config/wt.toml. wt ran with stdin from /dev/null and without --yes.

The recorder derives the id from host, component, stage and UTC date,
so this same-day re-record replaces the file under the same id. The
list-only version and its needs_changes review remain in history at
cef7a74, and the new receipt says so in its limitations.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Regenerate evidence matrix and re-register the re-recorded worktrunk receipt

Rerun scripts/component_matrix.py --write and
scripts/new_host_grand_list.py --write (the grand list is unchanged) after
the worktrunk re-record. The manifests/evidence.json hashes come from the
recording and generation tools. Shared hot-file edits stay in the last
commit.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Re-record macos-m5pro-20260924 rtk, gitleaks and worktrunk use receipts per re-review

Address the re-review of 3772eb5 (PR #185 comment 5816561592) by
re-recording all three receipts in place. The recorder derives the id from
host, component, stage and UTC date, so each same-day re-record reuses its
id. The earlier versions and the rtk/gitleaks agree reviews remain in
history at cef7a74, and each receipt's limitations say so.

- All three: the install and pin sentence is now backed by retained
  commands. command -v <tool> is recorded with the pin source: the mise
  global config pin line for rtk (0.49.0) and gitleaks (8.30.1), and the
  host control plane's manifest.json for worktrunk (0.79.0), read through
  a CONTROL_PLANE_ROOT environment variable so the private path is not
  recorded. The limitation now reads "Supports conditional now; accepted
  needs an independent review."
- gitleaks: add a positive control. A throwaway repository commits
  gitleaks' documented sidekiq-secret test fixture, built at run time from
  split pieces so the value never appears in the receipt. The same scan
  exits 1 with exactly one finding, and the wrapper asserts both. The
  negative controls remain: the scratch clone's latest commit and the
  throwaway repository's clean commit, both exit 0.
- rtk: add a limitation that raw-output and failure-recovery behavior were
  not exercised.
- worktrunk: same lifecycle probe, with the pin evidence and new wording.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Regenerate evidence reports after re-recording the macos-m5pro-20260924 receipts

Rerun scripts/component_matrix.py --write and
scripts/new_host_grand_list.py --write. The re-recorded receipts start
without independent reviews, so the macOS state of rtk and gitleaks
returns from host_verified to untested until the requested re-review. The
manifests/evidence.json hashes come from the recording and generation
tools. Shared hot-file edits stay in the last commit.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Add independent agree reviews to the re-recorded macos-m5pro-20260924 receipts

A separate Claude Code session on the same Mac re-reviewed the three
receipts re-recorded at 19354be and reproduced every probe from its own
session:

- rtk: command -v with the mise pin line, rtk 0.49.0, and rtk git status
  compacted output. Agree.
- gitleaks: command -v with the mise pin line, 8.30.1, and both negative
  controls (no leaks). The sidekiq-secret positive control exited 1 with
  exactly one finding. Agree.
- worktrunk: no user, system, project or environment config, so no hooks
  and no --yes; the agent-ecosystem manifest pins 0.79.0; and the
  wt switch --create / list (2) / remove --foreground / list (1)
  lifecycle ran in a throwaway repository, then cleanup. Agree.

The claim text is now evidence-backed, the limitation wording is
corrected, and rtk's unexercised raw/failure-recovery behavior is
stated. With these reviews, verdict_flip_candidates.py reports untested
-> accepted support on macos-arm64 for worktrunk (git-github-automation,
isolation, workers), gitleaks (secrets-credentials,
security-supply-chain) and rtk (token-efficiency). Recording the flips
is a separate record_verdicts.py step by the owning lane.

host_receipts validate (8), validate.py, component_matrix --check,
new_host_grand_list --check, evidence_manifest --check and
validate_convergence --all-recorded pass.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Record agent-lab-e9's independent agree reviews on the macos-m5pro-20260924 use receipts

Independent review from the WSL authoring host (different machine and identity):
workflow wf_b3b5c3b4-c85 at bc8cee5 (14 agents, adversarially verified), plus a
re-check at cfa7574 of every requested fix: command -v plus mise/manifest pin lines,
the gitleaks sidekiq positive control (exit 1, one finding), the worktrunk
create/list/remove/list lifecycle, and corrected claim/limitation text.
Validators exit 0.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Re-record the macos-m5pro-20260924 use receipts from main commit 2d11464

The previous copies recorded catalog_revision 3772eb5, a branch-only commit
that stops being reachable once this PR is squash-merged and its branch
deleted. host_receipts.py validate would then fail. These copies were
re-recorded with the same ids from a detached scratch checkout of main at
2d11464, as adoption/update.md requires, so catalog_revision is a main
commit.

The commands, claims and limitations are unchanged apart from one sentence
appended to each history limitation that records this re-record. The fresh
receipts carry only their self entries. The independent agree reviews in
cfa7574 and aebc492 were bound to the replaced records, so they are
superseded and are not carried over; they remain in PR #185's history.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Hot-file protocol: take main's evidence.json, re-register this PR's evidence, regenerate reports

After rebasing onto main 2d11464, manifests/evidence.json is main's copy
with this PR's four evidence files re-registered by the repository's
register_file tool: the hardware profile and the three re-recorded use
receipts. component_matrix.py --write and new_host_grand_list.py --write
regenerate the derived reports. register_file serializes with ASCII
escapes, so one existing non-ASCII path that main stores literally is
re-encoded to the same JSON value. No other entry changes.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Add independent agree reviews to the main-bound macos-m5pro-20260924 receipts

The rtk, gitleaks and worktrunk use receipts were re-recorded from main
commit 2d11464 so that catalog_revision stays reachable after a squash
merge. This independent session (a different identity from the recorder,
on the same Mac):

- confirmed 2d11464 is an ancestor of origin/main;
- found commands, claims and results identical to the ea31d6f copies it
  reproduced earlier. Only the history limitation gained a re-record
  sentence;
- re-ran the gitleaks probe: the clean commit exits 0, and the
  sidekiq-secret fixture exits 1 with leaks found: 1.

Agree on all three. verdict_flip_candidates.py reports untested ->
accepted support on macos-arm64 for worktrunk (git-github-automation,
isolation, workers), gitleaks (secrets-credentials,
security-supply-chain) and rtk (token-efficiency). host_receipts
validate (9), validate.py, component_matrix --check,
new_host_grand_list --check and evidence_manifest --check pass.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Re-record agent-lab-e9's independent agree reviews on the main-bound macos-m5pro-20260924 receipts

The receipts were re-recorded from main 2d11464 (so catalog_revision survives
a squash merge), which reset their reviews. Commands, exits, claim, class and
host are identical to the copies reviewed at cfa7574; only a history
limitation sentence was added.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

---------

Co-authored-by: seathatflowsinourveins <[email protected]>
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>

…/lessons-20261005/...

The #149 correction named the CC's ledger as command-center/lessons-20261005/cc-corrections-20261005.md, the
form the brief prescribed. The CC recorded that as its correction #180: the ledger sits at
coordination/lessons-20261005/cc-corrections-20261005.md (state-root relative), a sibling of command-center/,
not under it. The doc keeps "(host state, not in this repository)"; the test now pins the true locator and
rejects the old form. Found by looking up the file name under the host state root; the CC confirmed it in #180.

Fail-before: with the new pin the module gives 9 OK and 1 assertion failure, 0 errors, on the 8b8c8f5 doc
text; 10 OK after. validate.py and evidence_manifest.py --check pass.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

…rrection #149) (#997)

docs: ai-memory --capture-assistant was not in force on this host (correction #149)

* docs: ai-memory --capture-assistant was not in force on this host (correction #149)

The maintenance doc said the allowlist installers carried --capture-assistant. 0 of 9 Claude and
0 of 7 Codex hook commands did: ai-memory bakes the flag only into the Stop command and only
preserves an opt-in already present (install_hooks.rs:689-701, 1104-1109 @ 89bd8ded;
render_shared.rs:1425-1427), so applications without the flag never added it. Claude was
re-staged with it on 2026-10-11; Codex waits for a trust refresh (trusted_hash changes).

Also: the HookArgs v2.6.3 range in the doc-contract test becomes :2961-2970, test 1 checks every
--check-capture block, a new test fails on the previous text, and the read kit's "repositories
commit the marker" comment is listed as a host note against .gitignore:73.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

* test: name the missing correction heading instead of raising ValueError

section_from() used str.index, so a document lacking the #149 heading (the 16f0a1f text) gave
3 test errors instead of contract failures. It now raises AssertionError naming the heading, and the
first #149 test no longer asserts on the whole document before extracting the section: the module
gives 6 OK on the head text and 4 assertion failures, 0 errors, on the 16f0a1f text.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

* docs: reconcile correction #149 with the dated qualification prose and pin it to the installed releases

Fixes the four Codex review threads on #997 (each verified valid at 805aca0):

1. Contradiction. The two paragraphs after the correction said, in the present tense, that both
   clients' assistant Stop excerpts are opted in and that Codex trust ended in a captured outcome.
   They now open "At the 2026-09-21 qualification" (git blame 54896e7 and every artifact under
   evidence/artifacts/memory-landscape-20260921 carry that date) and point at correction #149. A
   new test reads that prose, which correction_149_section stops before.
2. Unverified host state. The 0 of 9 and 0 of 7 counts, the earlier hook applications, the Claude
   re-stage and the pending Codex trust are labelled CC host measurements, cited to correction #149
   in command-center/lessons-20261005/cc-corrections-20261005.md and "not re-read by this change".
3. Pin. The host runs ai-memory 2.6.3 (385b81ea). install_hooks.rs:689-701, :1104-1109 and :1142
   and render_shared.rs:1425-1427 are byte-identical at the same lines in v2.6.3 and v2.6.0
   (89bd8ded), so both pins are cited and the test requires the v2.6.3 pin beside each cite.
4. Trust hash. Re-rendering changes the computed current hash; the stored trusted_hash is
   unchanged, the mismatch marks the hook modified, and the /hooks review writes the reviewed hash
   into trusted_hash (docs/decisions/2026-10-04-codex-rtk-hook-qualified.md Decision 1 at
   rust-v0.159.3; re-read at rust-v0.162.1 = 092d3acd, the installed codex-cli: discovery.rs:796-813
   and :715-721, hooks_rpc.rs:58-92). The test rejects "re-rendering changes ... trusted_hash".

tests/test_memory_landscape_capture_doc.py now has 10 tests: on the 805aca0 doc text the module
gives 6 OK and 4 assertion failures, 0 errors (one per thread); on this text 10 OK.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

* docs: cite correction #149's ledger by its true locator, coordination/lessons-20261005/...

The #149 correction named the CC's ledger as command-center/lessons-20261005/cc-corrections-20261005.md, the
form the brief prescribed. The CC recorded that as its correction #180: the ledger sits at
coordination/lessons-20261005/cc-corrections-20261005.md (state-root relative), a sibling of command-center/,
not under it. The doc keeps "(host state, not in this repository)"; the test now pins the true locator and
rejects the old form. Found by looking up the file name under the host state root; the CC confirmed it in #180.

Fail-before: with the new pin the module gives 9 OK and 1 assertion failure, 0 errors, on the 8b8c8f5 doc
text; 10 OK after. validate.py and evidence_manifest.py --check pass.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

* docs: date the installer lead and bound correction #149's Codex count to the native profile

Fixes the two upheld Codex threads on #997 at 03fc660 (4245318057, 4245318059). The third,
4245318064 (P1, layer-resolution record), is not accepted: the layer-resolution protocol (#1008)
governs layer adoption and verdict decisions, and this change adds no layer verdict. It corrects a
host-state claim under AGENTS.md "Corrections", which the pinned sources already cited (ai-memory
v2.6.3 = 385b81ea, Codex rust-v0.162.1 = 092d3acd) and the fail-before tests below satisfy.

1. The installer lead (4245318057). The retained 2026-09-21 record,
   evidence/artifacts/memory-landscape-20260921/native-commands.json:295-393 at 03fc660, shows the
   three installers run with --capture-assistant, exit 0 each, so the lead was true but undated; what
   it contradicted was correction #149's undated "The earlier hook applications ran without the
   flag". The lead now opens "At the 2026-09-21 qualification", cites that record and says it is not
   the hook state now. Correction #149 says the qualification's installers carried the flag, so the
   flag was lost before the 2026-10-11 measurement (the loss path is host history not reconstructed
   here), and names the two later flagless applications, the #144 repair and the 2.6.3 re-stage of
   2026-10-10. "Not in force" is dated 2026-10-11.
2. The second Codex profile (4245318059). hook-trust.json at 03fc660 lists seven hook commands for
   the native profile (:35-77) and seven for the Desktop profile (:279-321), 14 in all, so the CC's
   0 of 7 is one profile's. Correction #149 and the qualification prose after it now bound the count
   and the Codex conclusions (trust pending, capture off) to the native profile and say the Desktop
   profile was not measured.

tests/test_memory_landscape_capture_doc.py has 16 tests (10 kept, 6 new). On the 03fc660 doc text
the module gives 11 OK and 5 failures, 0 errors; on this text 16 OK. The new tests read the
artifacts: the line ranges the doc cites, the flag and exit code of the three installer records, and
seven commands per profile. manifests/evidence.json: hashes of the doc and the test re-registered
only.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>