Document NativeStack2604 evidence and distinguish old-bar readiness

[seathatflowsinourveins]

Scope

Publish the retained NativeStack2604 observations and correct the handbook after the command center's three-item micro-review. Official readiness remains the historical 30/80 from #700, whose bar is upstream acceptance, wiring and fresh-session use, with the harness text present.

The command center's captured-status provisional 30/80 is as of 11:44Z, excluding custody's 13:02Z BY_DESIGN change. It includes difftastic, structural-search, inspect-ai, harbor and codex-sdk despite fresh-session use not evidenced, so it is not measured qualification on the #700 bar. Earlier 37/40/44/32 proposals are superseded. Generated current/conditional values remain null.

The organic native arm differs in one respect: no harness text names the tool. Upstream acceptance, wiring and fresh-session use remain required. Its count comes only from the command center's final verified E2E S4, independent review and adjudication.

• Base: main ecfa112764c664d35377dd66b8cfcb67e5a94d60 (after trading: NativeStack2604 research runtime, EdgarTools 5.60.0 (runtime and catalog), hash-pinned build backend #703), merged into this branch at 44bf09713. Head: e50f0f480cabd66aea4f0552c1ebd589d45ebbf1.
• Lane: exactly lane:foundation. Pending the command center's micro-check and ACK at the exact head. Its ruling at d25ea1f7d was ACK_AFTER_THREADS; the four thread fixes and the boundary P3 are applied in d4db4726c.
• Owned paths: decision, receipts/artifacts, handbook builder/tests, architecture scope/notes and generated outputs; registry committed last.
• Serena and MinerU remain demoted while condition-absent controls are open; ccusage and session-analytics remain open. Retained failures, native attempts, local checks and model verdicts keep separate classes.
• All 80 historical slot records and main owner/profile/pin fields are preserved. Final architecture round 2 (wave 5): owners on the repository-quality rule, and NativeStack2604 plan rows for hcom, Chrome DevTools MCP, DSPy, SkillSpector, Inspect Scout and MCP conformance #713 landed as1796303f; Codex rtk hook: the plan's command-output row installs and trusts it (second of two; the user's relayed pointer yes) #705 changed command-output's historical owners/29 operation.

SOTA sources

• native-agent-stack@4c897418fe35a030a1188ae447eaf31c893f8eff:evidence/artifacts/ns2604-e2e-20261004/method.md:60: the frozen NativeStack2604 verified E2E: sanitized evidence, receipt and decision record (38% readiness before fixes) #700 qualification bar. PR #700.
• The same pin's docs/decisions/2026-10-04-ns2604-verified-e2e.md:114–121: final-readiness authority.
• native-agent-stack@424b8a778222ae8857aade42c49ae6f7a13b3138:docs/lanes.md:94–128 and scripts/host_receipts.py:710: main-registry restoration, native re-registration and registry last.
• The same pin's docs/acceptance-evidence-policy.md:28–69 and scripts/build_new_wsl_handbook.py:46: evidence boundaries and existing generator interface.
• Command-center source review task-ns2604-coop-20261005T181852Z:12–23, SHA256 fa512269d639605a344f690166c436a208fffb79403bb0f55b2b48f0c9a7ef63, retained in review-715-corrections.json#/micro_repair_rulings. It corrects its earlier bar wording; it is not upstream acceptance.

Evidence-class table

Claim	Evidence class	Boundary
Official #700 30/80	Historical qualification	Existing dated baseline; no new host run
Captured-status provisional30 and missing fresh-use proofs	Source review	Not measured #700 qualification or a derived numerator
Retained native attempts, wrappers, fixtures and verdicts	Original separately scoped classes	Failures and client-leg limits retained
Generators, tests and registry	Local integration / structural validation	Publication consistency only
Organic native-arm readiness	None recorded here	Count pending final S4

Local commands run (at head e50f0f480; content commits d4db4726c, 52a7680d9 and a305d2cbf)

• python3 scripts/validate.py: exit 0; 69 components, 4 profiles, 214 receipts, 10,284 hashes.
• python3 -m unittest tests.test_new_wsl_handbook tests.test_architecture_pin_source tests.test_stack_lifecycle: exit 0; 97 tests OK.
• python3 scripts/build_new_wsl_handbook.py --check: exit 0 (regenerated with --write).
• python3 scripts/component_matrix.py --check: exit 0; 32 rows.
• python3 scripts/new_host_grand_list.py --check: exit 0; 32 layers, 66 winners.
• python3 scripts/evidence_manifest.py --check: exit 0.
• git diff --check: exit 0.
• CI runs on this head.

Refresh onto main and the command center's ruling

• Refresh. 44bf09713 merges main ecfa11276:

  • The catalog merged cleanly as text, and the pin-source test passes.
  • The handbook was regenerated.
  • The handbook receipt's regenerations were united at the entry level.
  • The registry is main's 212 receipts plus this PR's 2, with its paths re-registered.
  • The hot-file pair keeps the registry last.
  • A GPT-6.1 Sol same-thread delta read of 82c25177f..d25ea1f7d returned ACCEPT.

• Ruling. The command center ruled ACK_AFTER_THREADS at d25ea1f7d: no P0 or P1, four valid P2 threads, one P3. d4db4726c applies:

  • T1: restores the #/bounded_repair_rulings locator.
  • T2: the handbook builder existence-checks and hashes readiness.official_source and independent_review.recorded_source_review, with a test.
  • T3: amendment times on the later ruling blocks and the two revised receipts.
  • T4: cites the reachable main commit c148e049.
  • P3: the qualification_bar.scope boundary sentence in the catalog notes (:8, :1208) and the receipt limitation.
  • Optional: a dated merge note in the decision record.

• T3 completion (52a7680d9). The command center found T3 partial at c3f4d8ddf. The ruling blocks' amended_at_utc now carry their revisions' write times: 19:12:17Z from 73d75df4b and 19:28:40Z from bfff257c0. Both equal the receipts' amendment times, and the item times stay in amendment_source_item. The handbook was regenerated and re-registered.

• Round 3 (a305d2cbf). The command center found that bfff257c0 also revised bounded_repair_rulings, adding captured_status_boundary, so the block now carries an amendments list that mirrors the receipts:

  • 73d75df4b at 19:12:17Z (item 170827Z);
  • bfff257c0 at 19:28:40Z (item 181852Z).

  A per-block check over the file's history finds a matching stamp for every content revision. The handbook was regenerated and re-registered.

• Threads. All four are answered with the command center's text and resolved.

Prior failed attempts remain retained. Reads so far:

• a GPT-6.1 Sol delta read of the refresh (82c25177f..d25ea1f7d);
• the command center's exact-head reads at d25ea1f7d (ruling ACK_AFTER_THREADS), c3f4d8ddf (T3 partly fixed) and 3457c9beb (T3's bounded block still incomplete).

The round-3 fix at this head awaits the command center's micro-check. No read yet covers it. These are source and integration review, not S4 qualification. All 212 main receipt entries (main ecfa11276) are preserved, with two owned receipts re-registered through the existing native library.

Decision record

docs/decisions/2026-10-05-ns2604-foundation-requalification.md records methods, sources, open controls/lifecycle gaps, superseded proposals and overturn conditions. Publication review or ACK does not provide S4 qualification.

Host evidence

No host-receipt or platform-status change. The command center is asked to micro-check round 3 at e50f0f480 and ACK that exact head. Landing waits for the repo-wide fsspec relock (GHSA-27vj-qcqg-25rc).

Checklist

• Main owner data, all80 historical slots and all 212 main registry receipts preserved.
• No credentials, active settings, private paths or raw conversations published.
• No host/config/install/service/billing change; Preserve organic evidence and version saturation requirement bindings #750 untouched.
• One lane label; registry-only final commit; exact head e50f0f480 reported to the command center.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-05T20:05:37.188617Z	82c2517	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 82c25177f4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[seathatflowsinourveins]

Claude session 5f (single writer for this refresh): #715 refreshed onto main ecfa11276 (#703 landed). Head d25ea1f7d47eb9cb325503f94935b6611cf0c23c.

Commits:

• 44bf09713: merges main.
• 7e62dd1f9 and d25ea1f7d: the hot-file protocol pair. The first resets manifests/evidence.json to the merge base; the second carries every registry edit. The pair leaves the tree unchanged.

What the merge resolved:

• Catalog. catalogs/foundation/new-wsl-architecture-20261001.json merged cleanly as text. A clean text merge doesn't prove the pin_source line locators survived, so tests.test_architecture_pin_source was run, and it passes.
• Handbook. docs/new-wsl-handbook.{md,json} were regenerated with python3 scripts/build_new_wsl_handbook.py --write, and --check passes.
• Handbook receipt. It is Document NativeStack2604 evidence and distinguish old-bar readiness #715's version, with regenerations united entry by entry: the base's 7, Document NativeStack2604 evidence and distinguish old-bar readiness #715's 5, main's trading: NativeStack2604 research runtime, EdgarTools 5.60.0 (runtime and catalog), hash-pinned build backend #703 entry, and this refresh's entry. Its outputs, generator and profile digests are refreshed.
• Registry. Main's registry, plus Document NativeStack2604 evidence and distinguish old-bar readiness #715's two receipt rows, with Document NativeStack2604 evidence and distinguish old-bar readiness #715's 18 paths re-registered.

Checks at the merge:

• 96 tests OK: tests.test_new_wsl_handbook, tests.test_architecture_pin_source, tests.test_stack_lifecycle.
• scripts/validate.py exit 0: 214 receipts, 10,284 files.
• scripts/evidence_manifest.py --check exit 0.

Cross-family read. A GPT-6.1 Sol same-thread delta read of 82c25177f..d25ea1f7d returned ACCEPT, with no P1, P2 or not-verified items. It confirmed:

• Outside the 4 resolved files, all 15 PR patches and all 54 main-only patches are preserved, and main's files are byte-identical.
• The three-way catalog merge reproduces byte-identically with git merge-file.
• The receipt union is exact, with no duplicate or dropped entry.
• All 212 main receipt rows and both Document NativeStack2604 evidence and distinguish old-bar readiness #715 rows are present, and exactly Document NativeStack2604 evidence and distinguish old-bar readiness #715's 18 file rows changed.
• The last commit's registry diff equals the whole registry diff from main.
• --check, the 96 tests and both validators re-ran with exit 0.

Ready for the command center's micro-check and ACK at d25ea1f7d.

🤖 Generated with Claude Code

[seathatflowsinourveins]

Claude session native-agent-stack-5f: landing at head 8ea77f3b71d7691066570f7c8a7dbb80d2d6d74e. The command center (wsl-architecture-design) gave its ACK at 4797854db5ce, which reaches this head only through recorded mechanical refreshes whose owned non-registry patch-ids are equal (its carry rule); under the user's 2026-10-04 decision it owns merges that touch the hot registry. The read-only cross-family review (GPT-6.1 Sol max, the packaged Codex SDK worker) returned ACCEPT at e50f0f480cab; this head is reached from it through recorded carry edges (equal owned patch-ids, or a cross-family delta read returning ACCEPT at the edge's target), with no P1 item.

Observed main b0df1fb0440698b0f210cb6becdcb24c685e232b. coordination/merge_tree_landing_check.py (sha256 a11649fcf2e5844c…) exit 0:

main b0df1fb0440698b0f210cb6becdcb24c685e232b head 8ea77f3b71d7691066570f7c8a7dbb80d2d6d74e base b0df1fb0440698b0f210cb6becdcb24c685e232b merged-tree 93e4a35bb1d2527a9df90227efb77739667d2a3e merge-tree-exit 0
ok   1: clean three-way merge
ok   2: merged-vs-main paths 19, outside PR-owned 0 []
ok   3: main drift 0 paths, overlap with PR-owned inputs (registry excluded) []
ok   4: registry foreign rows equal True, order preserved True, PR-owned rows 18, unowned top-level keys differing []
ok   5: merged files[] sorted by path with no duplicates: True (10336 rows)
LANDABLE
condition 5: merged files[] sorted and unique (tree 93e4a35bb1d2527a9df90227efb77739667d2a3e)

Required checks at this head: 7 pass . Unresolved review threads: 0.

[seathatflowsinourveins]

Claude session native-agent-stack-5f: post-merge observation. Landed as 0d5e6506434fab598dee861c749a22e628beb75a (parent b0df1fb0440698b0f210cb6becdcb24c685e232b), tree 93e4a35bb1d2527a9df90227efb77739667d2a3e. The landed tree equals the checked merged tree and the parent is the observed main.