Skip to content

Consolidate catalog evidence, organic controls and foundation records - #820

Draft
seathatflowsinourveins wants to merge 21 commits into
mainfrom
codex/ns2604-finalized-catalog-prep-20261006
Draft

seathatflowsinourveins wants to merge 21 commits into
mainfrom
codex/ns2604-finalized-catalog-prep-20261006

Conversation

@seathatflowsinourveins

@seathatflowsinourveins seathatflowsinourveins commented Oct 6, 2026 •

Copy link
Copy Markdown
Owner

Current FIX4 repair and checks

Named-tool exclusion now extracts original Unicode name spans and compares complete tokens, configured names and MCP components by the language's canonical caseless rule, NFD(NFD(value).casefold()). Combining marks remain inside a token; invisible format characters remain distinct. Existing punctuation, possessive and longer-name behavior is preserved.

Cross-kind command agreement now requires both the documented serialization and equal resolved shell_reads projections, with zero unknown counts on both sides. It guards RTK serialization and exact Sh/Bash/Zsh wrappers in the agreement predicate. The read parser, native ledger, raw/provisional path, typed duplicates and request/completion enrichment are unchanged.

Current validation:

  • The native unittest counter module ran 71 synthetic tests, rc0, with every earlier57 test method byte-identical and14 added controls. The unchanged d99 code returned rc1 with144 failing subcases/no errors under the new14-method control run; the two nonvacuous preservation controls also ran. Actual source/test hashes, observed clock boundaries, elapsed time, logs and snapshots are in the new FIX4 receipt.
  • Local nice -n 19 ionice -c3 python3 scripts/validate.py: rc0,69components/4profiles/229receipts/10403hashedfiles. Retained stdout SHA256 5881c181176dc889ec03041c47e3a5fcb322988f968d29e9614c419093ed1447; empty stderr. Diffcheck rc0.
  • Independent same-family GPT source-class review:0unresolved findings within both requested classes, source inspection only; no reviewer test/network/native trial. Record SHA256 9eba6422bf1e81a4b7f5ef85107d03ef8bdaabbc6ea289b1a64f3d04e1881f32.
  • Hosted validate has not run: the PR conflicts with main and has no merge ref. Local consistency/synthetic checks remain separate from hosted CI, organic use and upstream acceptance.

Publication: source/receipt commit 8f45700353a638a8d6183e0df4e9f72f2501deff, followed by registry-only 1068cd644141bb0e89e230c7328ea9d0802ea470. This registry-last chronology is stated with commit objects; a tree snapshot alone does not prove it. One push, no rebase. Prior failed observations/receipts and decided text are preserved; the decision has a dated amendment.

Canonical Unicode reference: python/cpython@v3.12.0 and @v3.13.0:Doc/howto/unicode.rst:465-480, same verified byte source SHA256 c5cf5081618e2b06a519d2ede00fb52a53922c5a8d636c4be337810fed2bd17c; Python 3.13 category API. The installed runtime's Unicode database15.1.0 is retained separately from latest-doc metadata.

Landing path remains: co-op exact-head delta, CC ACK, required CI/refutation at the single relayed landing rebase, and5f's retained-catalog queue. This PR stays DRAFT until its read. The slot-defaults/N1 recommendation, terminal-role amendment and canonical origin-URL extension are a stacked follow-up; none enters this repair tree. No deployment, installation, model/provider call, native-data counter scan, order or broker operation.

Retained implementation, fold conservation and historical check records

The records below retain their dated scope; FIX3 and earlier counter checks are historical. The current result above supersedes their repair-status wording.

Scope

Consolidate the finalized-catalog scaffold and three owned foundation drafts into one reviewable #820. The catalog remains pending_synthesis: 79 role slots, no selected repositories and a null census. The typed contract joins official release metadata, component pins, registered evidence, native wiring/fresh smoke/daily reports, four family/role refutations and dated exclusions; none of these declarations promotes a local check into adoption.

Folded originals and frozen source heads:

Base retained head: 6eb5ed83914f37c3f0baca40cba89c8172cfa9e3. Conserved fold snapshot: 77d35e41911c0f8c28a5561790cd8d8a8cd68175. Repair head: dee7cae97c74a6657cb40c7bf8324ccbd41f9111. Repair source commits: 5530276d1df426db36ce2ddbd0f92e59105c0f1e and 0fa1b5cf4763f0f432b4ee79815c5c3b6dff37f4; the last commit dee7cae97c74a6657cb40c7bf8324ccbd41f9111 changes only manifests/evidence.json, verified locally by Git history. This author report is separate from the tree-only reader's observations. Lane exactly lane:foundation; DRAFT. No rebase for FIX2. The author records the prior fold's source commit 80d3c42244d872a04897d693083258cbd4c0131a followed by registry-only 77d35e41911c0f8c28a5561790cd8d8a8cd68175; the source-only tree review did not independently establish this commit chronology.

Landing path: the co-op verified fold conservation and closed #750/#768/#787 with records under review-ns2604-coop-20261007T023012Z section 3; their origin branches stay preserved. The retained #820 now needs command-center exact-head delta/read and ACK, CI/refutation, then 5f's foundation queue. Root remains writer until queued. One atomic Git push published the retained and preserved #750 refs; no merge or original closure performed.

The co-op's byte check and source-only GPT review confirm conservation of all three folds; the co-op has closed the originals with records (not merged), as recorded in pr-triage-closures-20261007.md at 2026-10-07T06:59:45Z, 06:59:50Z and 06:59:55Z respectively. FIX2 repairs named-tool punctuation, contradictory completed-command attribution and inherited original-judgment provenance. New fixture results are recorded separately in evidence/receipts/ns2604-catalog-fix2-20261007.json and its immutable-linked alias supplement evidence/receipts/ns2604-catalog-fix2-alias-20261007.json. The first snapshot remains reachable at 5530276d; subsequent linked-ID and sibling-alias counterexamples are retained with their actual outputs and source hashes. Historical receipts and decided text are preserved.

SOTA sources

  • native-agent-stack@77d35e41911c0f8c28a5561790cd8d8a8cd68175:tools/invocation-monitoring/codex_counter.py:299-307,405-425,577-657, scripts/validate_foundation.py:123-144,702-753,877, scripts/saturation_ledger.py:439-495 and docs/acceptance-evidence-policy.md:26-33,42-69: the reviewed original controls, inherited provenance and evidence-class boundaries.

  • Python 3.12 regular-expression reference: literal escaping and prose boundary assertions used by the counter repair.

  • native-agent-stack@6eb5ed83914f37c3f0baca40cba89c8172cfa9e3:scripts/validate_foundation.py:79-196,326-340,457-611; catalogs/foundation/finalized-sota-catalog.json; docs/decisions/2026-10-07-finalized-sota-catalog.md: existing typed catalog/adoption contract.

  • The three source heads above bind the carried files. Their unchanged receipts and decisions retain exact upstream pins and evidence classes.

  • native-agent-stack@a40a083172af588f4b97646db87dfc8ef3c0b60e:tools/skill-usage/skill_usage.py:1314-1655 and examples/claude-native/workflows/child-usage.mjs:2854-2878: reuse the native call ledger.

  • openai/codex@d27764b82f7118f674371e6d6e76271d9d606edb:codex-rs/protocol/src/models.rs:1061-1155; codex-rs/protocol/src/protocol.rs:1948-1960,2179-2184,3301-3307; codex-rs/history/src/rollout_payload.rs:30-68; codex-rs/rollout/src/recorder.rs:2061-2092: verified native identity/turn/wire source for rust-v0.160.1, published2026-10-05T18:29:37Z. Full source references are in the new contract artifact.

  • nativestack-practice@a7b8018524575cabbd979e6f2e1c84ee6e94700f:checks/check-terminal-profiles.py; microsoft/terminal@v1.25.2733.0(dc8ae365847d41f62d1ebca93815bb00959bc12f), Profile::_GenerateGuidForProfile; Microsoft fragment extensions, dated2025-11-12/checked2026-10-06.

  • Native registry/generators at retained base: scripts/host_receipts.py, scripts/component_matrix.py, docs/lanes.md:94-128. Merge and history dispositions are registered in evidence/receipts/grand-catalog-folds-20261007.json.

Exact overlap dispositions

Path Merge
scripts/validate.py Native three-way merge keeps organic receipt validation, narrow profile.guid scanning and #820's finalized selection guard.
component-evidence-matrix.json / its Markdown Existing builder regenerates the union; existing rows/observations remain and organic information flips no status.
manifests/evidence.json Retain all219 prior receipt bytes/metadata; union five source-owned receipts and the fold record; actual checksums committed last.
2026-10-05-omniroute-gateway-composition.md Explicit A34 exception: original decided prefix and line47 unchanged; exact #768 F1 correction appended as dated amendment atline129. This file intentionally differs from #768. Its source branch and historical receipt are untouched.
tests/test_finalized_foundation_catalog.py Explicitly mock missing owner and separately reject outside-owner references now that #750's helper is present. Production guards unchanged.

Byte-identical carried content (registry excluded): #750 26/29, #768 8/10, #787 7/7. Every file/hash/mode is listed in the fold receipt. Other differences are the documented merges above.

Open item: version-2 producer handoff

The additive requirement_binding is complete and carried here. Convergence-practice owns #821's producer paths:

  • tools/sota-convergence/landscape-sweep/build_inputs.py
  • tools/sota-convergence/landscape-sweep/convert.py
  • tools/sota-convergence/landscape-sweep/build_args.py

Open before any future text-bound qualification: carry the same frozen snapshot with binding_version:2, identity:{catalog,layer_id}, exact requirement_text, requirement_hash and retained legacy_hash. Include it in original/expanded field digests when present; preserve the exact absent-snapshot legacy formula. Grand-catalog changes none of those producer files and claims no activation, new sweep or historical rehash. The original five ledger records/95 scopes remain byte-preserved.

FIX3 repair: case and completed command representations

Two remaining counter defects are repaired: configured and extracted prompt names now match case-insensitively, and completed command originals preserve argv/shell representation semantics. Every completed pair must agree within the existing native identity groups; a shell-text record cannot bridge conflicting argv records. Supported enrichment, exact duplicates and narrowly documented wrapper/RTK serialization remain valid.

  • Synthetic controls: 57 tests pass, including all 44 earlier methods byte-for-byte unchanged. The same corrected rejection controls fail at dee7cae97c74a6657cb40c7bf8324ccbd41f9111: 11 methods, 108 failing subcases. Earlier red stages and the first failed repaired run (55 tests, 4 fixture-declaration failures) remain distinct in evidence/receipts/ns2604-catalog-fix3-20261007.json.
  • Source preservation: prior receipts, original legacy scan/prompt-name extraction, maintained native adapter/ledger and decided text are unchanged. The decision is extended with an appended dated amendment. The source snapshot carrier links the exact prior hashes.
  • Structural validation: local nice -n 19 ionice -c3 python3 scripts/validate.py passes with 69 components, 4 profiles, 228 receipts and 10,402 hashed files. git diff --check passes. Final registry checks and commit chronology are reported below.
  • Hosted validation has not run: this draft conflicts with main and has no merge ref. Local results establish local consistency only; they do not establish hosted CI acceptance.

scan's older prompt filter remains raw/provisional; the controlled oracle rebuilds complete original owner/turn context. Actual native counter qualification, equivalent Claude proof and the adoption synthesis remain pending. Malformed command value types outside documented native shapes remain an explicit source limitation. No organic counts or adopted defaults are published.

Scope remains this repair on the same branch, with no rebase and one push. Slot defaults and the single north-star-rnd entry remain a stacked follow-up after this repair's publication/read; they are absent from this tree. Landing path: co-op exact-head delta → command-center ACK → hosted CI/refutation at the single landing rebase → 5f's retained catalog queue. Draft status remains.

Sources: native-agent-stack@dee7cae97c74a6657cb40c7bf8324ccbd41f9111:tools/invocation-monitoring/codex_counter.py:49-99,299-309,405-432,611, tools/skill-usage/skill_usage.py:926-936; openai/codex@d27764b82f7118f674371e6d6e76271d9d606edb:codex-rs/core/src/shell.rs:20-30; rtk-ai/rtk@v0.51.0:README.md:6,313; Python casefold, subprocess arguments, and shlex.join.

Evidence-class table

Claim Class Evidence
Earlier execution/results Their unchanged original classes Source receipts/artifacts
Source-byte, mode, metadata and AST conservation source_review / local_integration Fold receipt and scoped critic
Control filters and typed counterexamples synthetic 34 Codex control fixtures; native counts remain null
Generator/checker/registry consistency local_integration Actual commands below
Real organic proof, daily owner carrier, adoption synthesis pending No qualified native oracle or finalized selections

Historical FIX2 repair checks

The three requested findings are repaired and the bounded same-family source micro-review has zero remaining findings within those seams. It is source review, not independently executed upstream or native acceptance.

  • P1: each original judgment's hash-resolved document/pointer ancestry must declare resolved non-synthetic provenance. A single synthetic original or ancestor cannot qualify adoption; unknown/deferred observations remain non-adopted. Red seven methods/12 failures; focused green seven; full catalog suite 67 passed. The positive fixture declares original source_review provenance in a separate registered artifact while its ancillary frozen input remains synthetic.
  • P2a: terminal punctuation is excluded from prose tokens; internal punctuation and distinct longer names remain literal. Exact Use serena./Use rtk: plus quoted/bracketed/repeated punctuation cases and positive counterparts are retained.
  • P2b: known completed commands/statuses must agree under storage keys and the exact one-hop native identity group used by qualification. Linked-ID red had six failures/six errors. Sibling-alias red had 16 failures, including eight false organic-count cases at the pair-only guard. Sticky incomplete identity now produces unknown attribution; agreeing aliases, duplicate completions and supported enrichment still pass. Final counter suite: 44 passed.
  • Source/test bindings: counter 92f83389d1131553c1e06050779876ead04941616948e7b357ad2273f6299249, counter test d4973be70b384bf31f90c660c46c95dd9a44f2172835c77701707f274f837be3, validator 8201cd367bf142c785c240bd8feb768499cdf1b69a9d33c0c88d92a7788e1700, catalog test a6b800588e3699cf97f41dd03c7c9b3955d0728ae08b52d84991b58de76d79f3.
  • nice -n 19 ionice -c3 python3 scripts/validate.py: 0; 69 components, 4 profiles, 227 receipts, 10401 hashed files. git diff --check:0. Required test steps were serialized at nice19/ionice3; hash-matching worker catalog results are reused and final worker counter bytes match the integrated root.

No native original-counter scan, organic count, adoption result or rebase was performed. FIX2 uses one ordinary push to the same branch; no merge or pin promotion. Hosted CI at the repair head is not claimed by these local checks; the earlier 77d35e4 read reported CodeQL green and validate not run due DIRTY/no merge ref. Native/Claude oracle proof and adoption synthesis remain pending. Prior fold checks below are historical.

Local commands run (fold snapshot)

Heavy steps use nice -n19 ionice-c3; test scratch is in a private external cache.

  • Combined touched modules: first692 tests/42.210s retained two failures and one optional-jsonschema skip. The fold-related absent-owner test is fixed with explicit controls. The existing installed-client auth_storage_failure notification drift remains open under A21; no notification table/overlay changed.
  • Final tests.test_finalized_foundation_catalog tests.test_terminal_fragment: 0;83tests/2.561s.
  • Codex counter focused module: 0;34tests/5.804s, including three unchanged baseline tests. Earlier ToolSearch and nine source-derived window/alias/unsupported-completion subcase failures remain retained.
  • component_matrix.py --write/--check:0;32rows/no flip violations.
  • new_host_grand_list.py --check:0;32layers/66winners.
  • check-terminal-profiles.py:0;16repository profiles.
  • saturation_ledger.py --check:0;5records/bindings verified.
  • python3 scripts/validate.py:0;69components,4profiles,225receipts,10399hashedfiles.
  • git diff --check:0. One atomic push and exact remote-head readback:0.

These are local checks, not upstream acceptance or an independent native E2E. The first unsafe TMPDIR preflight exited1 before tests; its output and every subsequent failure remain durable. Same-family scoped source critics cleared the repaired deltas; command-center review remains required.

Decision record

docs/decisions/2026-10-07-finalized-sota-catalog.md retains pending selections. The organic control decision and original Terminal/Dagu decisions retain scoped alternatives and overturn conditions. The dated gateway amendment preserves decided history.

Host evidence

Repository-only. No deployment, client/config change, ordinary counter/native-data scan, new live service probe, install, model run, credential access, order or broker connection. Existing Windows apply/read-back/rollback and special-launcher contracts are carried unchanged in windows/README.md; the co-op applies them after review.

Checklist

  • Historical observed results and source branches preserved.
  • Three originals named; one lane label; draft; exact overlap record.
  • A34 dated amendment, checksums/registry last and one retained push.
  • Co-op byte/range conservation verification and source-only fold review.
  • Co-op original closures with records; all three origin branches preserved.
  • Command-center exact-head read/ACK, CI/refutation and 5f landing.

FIX3 publication and check provenance

The two-commit publication is source/receipt commit 3ce2e74e175753e913c6ee67be47531fb01d5a01, followed by registry-only commit d99e8a2e84f531c2c6be2dd5e890e801ec8c76ce. This registry-last statement is backed by those commit objects; a tree snapshot alone does not establish chronology. No rebase was performed.

The final local nice -n 19 ionice -c3 python3 scripts/validate.py returned 0 from 2026-10-07T10:14:51Z to 2026-10-07T10:15:19Z: 69 components, 4 profiles, 228 receipts and 10,402 hashed files. Its retained stdout SHA256 is f25ecd71b5628c0b9eee8c3b74d20d526bce2e6f2b60efda6b2756cdbb29a154; stderr is empty. These are local integrity checks. Hosted validate has not run because the PR conflicts with main and has no merge ref.

A separate same-family GPT source critic, completed at 2026-10-07T10:11:48Z, found no unresolved finding within the requested case/command-representation variant axes. Its record SHA256 is 5099e721939d5984adb338019ae02cfda5b7df27292081f12316c8114f9c35d8, and its exact source/test bindings are in the new FIX3 receipt. It performed source inspection, not independent execution or cross-family acceptance. The co-op's exact-head delta and the command center's ACK remain pending.

@seathatflowsinourveins seathatflowsinourveins added the lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers label Oct 6, 2026
@seathatflowsinourveins seathatflowsinourveins changed the title catalog: prepare finalized slot ownership and client smokes Consolidate catalog evidence, organic controls and foundation records Oct 7, 2026

Copy link
Copy Markdown
Owner Author

Coordination for a user-requested memory/RAG upstream-quality catalog update, based on main e712bae. I am preparing an additive dated source review under catalogs/foundation/memory-rag-stacks-20261007.json, docs/decisions/2026-10-07-memory-rag-source-stacks.md and evidence/artifacts/memory-rag-stacks-20261007/, linked from catalogs/foundation/README.md. Scope: final architectural recommendations by use case plus immutable upstream source/CI/benchmark evidence; no installed-selection changes, no runtime qualification, no modification or reopening of blind trials. I will leave this PR's finalized-catalog scaffold, Foundation manifest, root catalog navigation and generators to its existing owner. Shared evidence registration will use current main plus registration of this branch's own files. The resulting scoped PR will be linked here for your catalog synthesis; these recommendations are inputs, not a claim that the 79-slot synthesis is complete.

Copy link
Copy Markdown
Owner Author

The additive memory/RAG source-review recommendations are now in PR #828: #828 (head 88a4627; base e712bae). It owns the new dated foundation leaf/decision/review, a small foundation README link, generated us-equities decision-index entries, and its own evidence registrations. No changes to your catalog synthesis, foundation manifest, component matrix or generators. Local validation, 33 relevant tests and all 3 exact-commit pre-push gates passed; required CI is running. The five architecture choices and 18 repo source reviews retain deployment, blind-trial, benchmark and full-stack limits. Please include the new registered supplement when regenerating the decision index after integration.

Copy link
Copy Markdown
Owner Author

Final handoff: the memory/RAG contribution in PR #828 is merged to main as 18150f10b061ca3fb74a63cdb783dbaaf31c4057. All seven required checks passed at reviewed head 6b2a9dd452d2b1da8a7e1eb93585b23d079c1d58; the merged tree matches it exactly. The dated decision is docs/decisions/2026-10-07-memory-rag-source-stacks.md, with five source-quality architecture recommendations, 18 unchanged upstream audit records, and the registered catalogs/foundation/memory-rag-stacks-20261007.json#/repository_decisions supplement. The wording now follows the merged October 6 upstream-evidence policy while preserving installed selections and historical artifacts. This remains additive input to your catalog synthesis; complete-stack execution is not claimed, and your owned synthesis files were not changed.

seathatflowsinourveins added a commit that referenced this pull request Oct 7, 2026
### Scope

Restore the handbook test's live publication binding so a later profile or handbook regeneration updates its own maintained receipt, instead of editing #826's dated landing record.

- Base commit: `6d252c9c102e575bc9229bf6bb2149409655d5f3`; head: `4d2ce2a7719adca918025ffde295ef1dfa30bf02`.
- Lane: `lane:foundation`; draft.
- Exactly four paths: `tests/test_new_wsl_handbook.py` (one receipt-path line), `evidence/artifacts/new-wsl-handbook-20261001/receipt.json` (current computed binding plus one appended regeneration), its one-line `README.md`, and registry last.
- The generator, profile, both generated outputs, hash/inventory assertions, existing receipt observations/history and #826's dated record stay byte-identical.
- **Named landing path:** co-op cross-family exact-head read, hosted validate, command center CI read and cue; **right after #820, ahead of #775**. ONE replay at that cue if #820 changes main; full test phase in that landing turn. Hold this draft head for the reads.

## SOTA sources

- `native-agent-stack@6d252c9:tests/test_new_wsl_handbook.py:1672-1691`: the publication contract checks actual current generator/profile/output hashes and inventory, with byte-change negative controls. Its comment says hashes follow regeneration. Only its receipt locator changes.
- Same pin, `evidence/artifacts/new-wsl-handbook-20261001/receipt.json:268,656,700`: the receipt is a current hash mirror and prior entries expressly refresh mutable producer/output bindings while preserving observations. This existing repository practice fills the publication-binding gap; no new manifest, generator or validator is introduced.
- Same pin, `docs/acceptance-evidence-policy.md:59-65` and `docs/landscape-domain-notes.md:33,38`: retain historical inputs/results/failures/pins. All prior receipt fields, regeneration prefix and `previous_outputs` are retained; #826's dated record remains historical.
- Same pin, `docs/lanes.md:94-115`: main-copy/own-registration protocol; `scripts/host_receipts.py:710` updates the three own hashes and inserts the README, in the registry-only final commit.

### Evidence-class table

| Claim | Evidence class | Command / receipt |
| --- | --- | --- |
| Existing strict publication contract passes at the maintained binding | `local_integration`, `synthetic` | 87 handbook tests, exit 0; existing byte-change negative controls unchanged. |
| Actual generated bytes are current | `local_integration` | Native builder `--check`, exit 0; MD a1a0cb17… and JSON a42c8915… as recorded in the appended regeneration. |
| Dated records/history/other test assertions preserved | `source_review`, `local_integration` | Exact base-file/JSON comparison, exit 0; independent bounded source critic ACK. |
| Publication integrity after registry-last commit | `local_integration` | `validate.py` before/after, exit 0; 69 components, four profiles, 224 receipts, 10,508 hashes. |

### Local commands run

All checks use the owned external TMPDIR, `nice -n 19 ionice -c3` and closed stdin.

```text
python3 -B scripts/build_new_wsl_handbook.py --check
exit 0, status passed; current outputs unchanged.
python3 -B -m unittest tests.test_new_wsl_handbook
exit 0: Ran 87 tests in 37.368s; OK.
Exact unchanged-field, regeneration-prefix, dated-record and one-test-line comparison
exit 0; all preservation controls true.
python3 -B scripts/validate.py
exit 0 before and after final registry commit; 10508 file hashes.
git diff --check
exit 0.
```

The scoped cached open-PR check found 44 open PRs and these overlapping neighbours: #645, #754, #769, #770, #810 on the maintained receipt; #776 and #810 on the test. The CC assigned this narrow critical-path repair before later regeneration PRs. No peer head or file is edited by this lane.

### Decision record

The CC's J-HANDBOOK-BINDING ruling supplies the bounded disposition. The one-line receipt README identifies the maintained current-state carrier. No old decision or dated observation is rewritten, and no extra decision file is added to this small unit.

### Host evidence

No host/client/installation or acceptance-status changes. These checks establish the repository publication contract, not upstream model or native host acceptance.

### Landing read fields

The intentional main-test edit is `tests/test_new_wsl_handbook.py:1677`, disposed of in advance by the CC for this exact receipt rebind. Name it in `main-tests=` at the landing read. Declare every actual post-read/replay change in `adapted=`; the full-suite phase is deferred to the landing turn. Nothing is re-pointed to a new dated path.

### Checklist

- [x] Existing current-state receipt reused; earlier observations and dated record preserved.
- [x] Only one test line changes; assertions, producer and profile unchanged.
- [x] Own entries registered last; required local checks pass.
- [x] No workflow, dependency, paid surface or credential change.
- [x] Draft and one foundation label; named read/ACK/queue path.
seathatflowsinourveins added a commit that referenced this pull request Oct 8, 2026
…heck (#838)

### Scope

The required Linux test job runs serially and blocks each landing for roughly half an hour. This change runs native unittest discovery as eight module shards and keeps one final required check named `validate`, which fails on any unsuccessful dependency or incomplete module coverage.

- Base commit: `b16cb8cf7cb8e37bf0d0edb9924502beb3e6a276`.
- Lane: `lane:shared`; the command center requests trading acknowledgement for the one promotion workflow-contract method.
- Owned paths: validate workflow, shard helper/weights, its fixtures, declared workflow-contract tests, the decision/receipt and the final registry commit.
- Landing path: exact-head co-op cross-family read after the draft's hosted timing run; command-center ACK; 5f lands after #833/#836 and before #820/#829/#776, per GO-RELAUNCH230713Z and RULING203309Z. The draft stays draft until that read. Critical-path cap allowance confirmed by item191739Z; all25kind3rows accepted by name in203309Z subject to their stronger-assertion condition.
- #706 relation: this final summary supersedes G-6 (serial suite counts); G-1 (PR-metadata workflow work) stays in #706 for its rank38 turn.

## SOTA sources

- [GitHub matrix strategies and failure handling](https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations), read 2026-10-07.
- [GitHub needs result](https://docs.github.com/en/actions/reference/workflows-and-actions/contexts#needs-context) and [always](https://docs.github.com/en/actions/reference/workflows-and-actions/expressions#always), read 2026-10-07.
- [Skipped jobs](https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-jobs-with-conditions) report success even when required; [required status checks](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging) accept skipped statuses. This final job always runs and explicitly rejects skipped/cancelled/failed dependencies.
- [CPython v3.12.3 native discovery](https://github.com/python/cpython/blob/v3.12.3/Lib/unittest/loader.py#L109), [load_tests protocol](https://docs.python.org/3.12/library/unittest.html#load-tests-protocol) and [TextTestRunner](https://docs.python.org/3.12/library/unittest.html#unittest.TextTestRunner). The helper supplies assignment and receipt glue; unittest runs the tests.
- `native-agent-stack@b16cb8c:.github/workflows/validate.yml:147-250`: the unchanged provisioners and diagnostics.
- Same pin, `docs/decisions/2026-10-03-suite-parallelism-trial-outcome.md:24-27`: the superseded Linux serial instruction; failed pool-trial evidence and macOS instruction preserved.
- Existing pinned download/upload artifact actions are reused; no requirement file or other workflow job changes.

### Evidence-class table

| Claim | Evidence class | Command / receipt |
| --- | --- | --- |
| Historical timing weights | source_review of retained native output | run37653671981/job112905135751, log SHA b1d2d43e; 17 failures retained |
| Native discovery and assignment | local_integration | Current tree discovery-only sample:272owners/11607cases, no bodies; predates final fixture set |
| Focused contracts and fixtures | local_integration; synthetic fixtures remain synthetic | 368tests/95.067s with one retained serial-binding failure; its authorized class delta3tests/0.874s passes; final new-module13tests/3.383s passes |
| Syntax/integrity | local_integration | actionlint0; offlinezizmor0/findings[]; py_compile0; diff--check0; validate.py0 |
| Hosted timing and exact module/count union | pending | The draft's actual run supplies this; historical estimates are not acceptance |

Expected first-run limitation: this branch is still based on b16cb8c, while main28327acc carries #837's new frozen-lock exceptions. The first osv-scanner check is expected red for that base; it is refreshed only at the command-center landing cue's single rebase. No exception or requirement change is added here, and a local check never substitutes for the landing head's hosted result.

### Local commands run

```text
nice -n 19 ionice -c3 actionlint -color .github/workflows/validate.yml
exit0

nice -n 19 ionice -c3 zizmor --offline --no-config --no-ignores --format json .github/workflows/validate.yml
exit0, []

python3 -I -B -X pycache_prefix=<ignored-owned-path> -m py_compile <helper and five touched test modules>
exit0

nice -n 19 ionice -c3 <activated Python3.12.3> -I -B -X faulthandler <stdlib unittest bootstrap> -q --durations 50
selected: test_validate_shards, test_workflow_hardening, test_shell_parser_ci,
test_landscape_sweep_skills, test_workflow_security_coverage, test_promotion_gate,
test_adoption_docs_consistency
exit1, 368ran/95.067s/onefailure/fiveskips (retained)
Only failure: the promotion class's serial-command binding.
Authorized delta: that class exit0, 3ran/0.874s; other36method ASTs and surrounding bytes preserved.
New fixture deltas:12ran/3.407s and13ran/3.383s, both exit0.
No full-suite phase or hidden baseline waiver.

nice -n 19 ionice -c3 <activated Python3.12.3> -I -B scripts/validate.py
exit0, components69/hashed_files10559/profiles4/receipts226.
git diff --check
exit0
```

The local environment has Python3.12.3/PyYAML6.0.3 and real Node24.21.0/npm11.19.0 bins before generic PATH. It is a focused environment, not full hosted-image parity. Every hosted cell keeps the current installer and promotion/parser/NodeYAML provisioners; non-test checks execute once in cell zero.

### Contract changes

Each listed existing test deliberately replaces the serial whole-suite binding with complete module-shard coverage under `docs/decisions/2026-10-07-validate-module-shards.md` (kind3). Provisioning, history, timeout/faulthandler and native failure controls remain. The one promotion method additionally runs the tiny native aggregate fixture; neighboring and numeric assertions remain byte-identical.

The trading lane's conditional acknowledgement, ledger row `report-native-agent-stack-5f-20261007T200005-shardack`, binds that promotion method to three conditions:

1. Every shard runs the promotion provisioner with `--require-hashes` on `blueprints/us-equities/data/requirements.lock` and exports `REQUIRE_PROMOTION_GATE_VENV=1` before testing, including the shard assigned this module.
2. Module coverage comes from live native discovery, with each module's executed suite exactly once. Weights are scheduling estimates, not a separate test inventory.
3. Final `validate` runs under `if: always()` and passes only on successful shards; cancellation, skipping and timeout fail the gate. The trading lane checks these again on this PR before merge.

| Test ID | Kind | Record |
| --- | --- | --- |
| `tests.test_workflow_hardening.WholeSuiteJobsCheckOutFullHistory.test_whole_suite_jobs_set_fetch_depth_zero` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_workflow_hardening.WholeSuiteHeadroomAndDiagnostics.test_every_whole_suite_job_names_its_suite_step` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_workflow_hardening.WholeSuiteHeadroomAndDiagnostics.test_each_suite_lists_its_50_slowest_tests_with_faulthandler_on` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_workflow_hardening.WholeSuiteHeadroomAndDiagnostics.test_linux_suites_abort_five_minutes_before_the_job_limit` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_workflow_hardening.WholeSuiteHeadroomAndDiagnostics.test_validate_uploads_its_verbose_log_even_when_the_suite_fails` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_workflow_hardening.ValidateSuiteStepTracesAHang.test_a_hang_prints_the_hung_test_traceback_and_fails_the_step` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_workflow_hardening.ValidateSuiteStepTracesAHang.test_control_without_faulthandler_the_hang_leaves_no_traceback` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.ProvisioningStepTests.test_provisioning_step_exists_in_the_validate_job` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.ProvisioningStepTests.test_provisioning_step_precedes_the_unittest_step` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.ProvisioningStepTests.test_step_command_is_derived_from_the_pin_file` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.ProvisioningStepTests.test_step_exports_the_directory_through_github_env` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.ProvisioningStepTests.test_step_cannot_be_skipped_or_ignored` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.ProvisioningStepTests.test_the_provisioning_job_is_the_job_that_runs_the_suite` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.ProvisioningStepTests.test_every_whole_suite_job_provisions_the_parser_or_is_a_recorded_gap` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.ProvisioningControls.test_each_mutant_is_reported_in_its_category` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.ProvisioningControls.test_a_scratch_copy_of_the_workflow_without_the_step_fails_the_structure_tests` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.RealRatchetControls.test_the_real_workflows_pass` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.RealRatchetControls.test_a_new_whole_suite_job_in_a_real_workflow_is_reported` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.RealRatchetControls.test_provisioning_a_recorded_gap_job_is_cleared_by_deleting_its_entry` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_shell_parser_ci.RealRatchetControls.test_a_step_that_only_names_the_pin_file_is_judged_by_the_structure_checks` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_landscape_sweep_skills.SkillsYamlProvisioningTests.test_the_validate_job_provisions_the_yaml_pin_before_the_suite` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_landscape_sweep_skills.SkillsYamlProvisioningTests.test_every_whole_suite_job_provisions_the_yaml_pin_or_is_a_recorded_gap` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_landscape_sweep_skills.SkillsYamlProvisioningControls.test_each_mutant_is_reported_in_its_category` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_landscape_sweep_skills.SkillsYamlProvisioningControls.test_the_ratchet_reports_a_new_whole_suite_job_and_a_gap_that_now_provisions` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |
| `tests.test_promotion_gate.WorkflowProvisioningContract.test_unittest_step_runs_the_full_suite` | 3 | docs/decisions/2026-10-07-validate-module-shards.md |

### Failed attempts and limits

The failed unittest-parallel trial remains unchanged. The historical weighting run failed17 tests. Worker fixture-authoring attempts (one missing-helper error; then one failure/one error among12cases) remain disclosed separately; later root runs do not replace them. An early validate returned1 for pending registry hashes, and an incorrect register_file CLI probe returned2 before the documented Python API was used.

The source critic's two fixture gaps (global zero discovery and a package hook invoking nested discovery) are covered by the passing native delta fixtures. Shared fixture origins trigger an explicit serial fallback; that preserves native semantics and must be reported as a performance constraint. Actual hosted latency, skips and complete module coverage remain pending.

### Decision record

`docs/decisions/2026-10-07-validate-module-shards.md`; scoped observations in `evidence/artifacts/validate-module-shards-20261007/preparation.json`. The final commit changes only `manifests/evidence.json`.

### Host evidence

No host receipt, platform-status change, install or setting change.

### Checklist

- [x] Changed actions pinned to full SHAs with version comments.
- [x] Top-level permissions empty; each job grants contents:read only.
- [x] No credential value or new secret.
- [x] No new billing surface.
- [x] Peer worktrees preserved.
- [ ] Trading acknowledgement before merge (command center requests it).
- [ ] Hosted timing/coverage receipt and exact-head cross-family read.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant