Repository navigation
G5: define start-closure/1 and pass full-asset closure check - #878
Conversation
|
No dependency changes detected. Learn more about Socket for GitHub. 👍 No dependency changes detected in pull request |
|
Shared-lane ACK from
This acknowledgment covers the requested commit's trading source registration and preserved boundaries. Public index completion, the complete input union, two-family evidence, saturation/evidence qualification, final hosted checks, connector-thread triage and the CC landing cue remain open as stated in the draft. No strategy, paper, broker, runtime-adoption or START acceptance is asserted. This review ran bounded artifact and Git-object checks; it did not run a full suite. |
3e5a9a6 to
ae6cc22
Compare
) ### Scope Records the current host-wide activation of Claude Teams and workflows, leaves role-scoped loading owner-gated with its inverse, pins the payload selected by the supported AO install recipe, and retains the exact frozen snapshot used in invocation comparisons. The four-stage adoption record keeps all four outcomes DEFER pending quality, memory and fresh owning-role evidence. - Base commit: `aba02ec3456d383bcc2fc72883db098f9be7918a`. - Lane: `lane:foundation`. - Owned paths: the three `docs/decisions/2026-10-08-orchestration-*` records and `docs/decisions/extra/adoption-cc-2ebc30ce3527d025.json`. ## SOTA sources - [aannoo/hcom v0.7.28](https://github.com/aannoo/hcom/tree/b2a7c192003e7fd67ed93265289e4ac36276f965), `b2a7c192003e7fd67ed93265289e4ac36276f965`: README, native event projection, common/Codex hooks and kill semantics. The canonical source list is aligned across the records; the three hashed measurement files retain their distinct scope. - [anthropics/claude-code v2.1.295](https://github.com/anthropics/claude-code/tree/602df92bf481ed904533e95c09f740f40aab5aed), `602df92bf481ed904533e95c09f740f40aab5aed`: `CHANGELOG.md`, section 2.1.178 implicit teams. Installed build `07e8f67ea328`, executable SHA256 `4503bfe11a6c7fcc1e0b39b5e0d347c04248f750b03b0977b3ad6b531fe6f358`, independently pinned selection/coordination/session spans in the native receipt. CC-verified user-scope activation is recorded separately from the proposed role change and natural selection. - [OrchestratorInc/agent-orchestrator v0.13.5](https://github.com/OrchestratorInc/agent-orchestrator/tree/c95ae361eee48d33c2f443c6d2fe69c445f548a8), `c95ae361eee48d33c2f443c6d2fe69c445f548a8`: `scripts/setup-self-hosted.sh:90-107,141-170` supported local bundle and native extraction. Installer SHA256 `463366604181029d8cdb16cbc1a5d8771eaf4bc498594b09759a5b42b79bee7d`; exact Linux x64 AppImage asset `621487952`, SHA256 `5f4262c1b5fad5e63c0b1291d5a2e4c878c953496f5ca430edfe4c061987bf28`. The recipe enforces these hashes before deriving a separately checksummed resources archive for `--bundle`; execution remains owner-gated. - Both designated delta artifacts at `0ad947f6fd5023b2a21eadae2837349d4b313886` are bound in `review_sources`: CC `69119fd821ddab7fda786a8b374ccfa89db43aa43cd81edb49b9fd5714860357`; GPT `bb3bfe43911116f1dfb8721bc36c6cedc32c90d6f235287f511acbbc4ad14735`. ### Evidence-class table | Claim | Evidence class | Command / receipt | | --- | --- | --- | | Host-wide Teams/workflows activation | `native_proven` by the CC | CC delta artifact; settings locators and CHANGELOG contract in `native_evidence.claude_host_activation`. Role scoping and its inverse remain proposed. | | Fixed AO payload selection | `source_review` | Pinned installer plus public v0.13.5 asset metadata; both prospective recipes pass `bash -n`. The AppImage digest pins the upstream payload; the derived tar has a separate owner-retained digest. | | Frozen CC comparison source retained | `local_integration` | Exact 60,603-byte file, SHA256 `2ebc30ce3527d025dad39d65293d3020620192c4f0d2987cf3988461254836a0`, committed under `docs/decisions/extra/` and copied to the new-head packet's `extra/`. | | Existing counters, denominators, source spans and PSS observations | Scoped retained evidence | Compared against the previous head and kept unchanged. Invoke counts remain baseline only; component costs and organic acceptance remain open. | The record also carries the six optional clarifications: small-PR bounds, CC deployment stop guard and owned-service inverse, consistent hcom source scope, refresh procedure pending #878, portable state root, and the stored-delivery-field predicate including empty lists. No stronger acceptance class is inferred from these corrections. ### Local commands run ```text nice -n 10 ionice -c2 -n7 timeout 600 env PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3 -B -m unittest tests.test_adoption_contract rc=0; 13 passed / 13 run nice -n 10 ionice -c2 -n7 timeout 600 env PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3 -B -m unittest tests.test_adoption_bootstrap rc=0; 76 passed / 80 run; 4 skipped nice -n 10 ionice -c2 -n7 timeout 600 env PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3 -B -m unittest tests.test_validate rc=0; 68 passed / 68 run nice -n 10 ionice -c2 -n7 timeout 600 python3 scripts/validate.py rc=0 git diff --check rc=0 ``` The two generic documentation reader modules and validator module are publication/regression checks. They do not establish organic adoption or execute the AO install recipe. The initial publication check rejected an absolute personal state path; the final record uses the portable `~/.local/state/native-agent-stack` root and passes validation. ### Decision record [Four-stage record](docs/decisions/2026-10-08-orchestration-adoption.md), [decision JSON](docs/decisions/2026-10-08-orchestration-adoption.json), [native evidence](docs/decisions/2026-10-08-orchestration-native-evidence.json), and [retained CC snapshot](docs/decisions/extra/adoption-cc-2ebc30ce3527d025.json). Quality/G5 evidence selects one current choice per role slot; invocation volume does not select winners. AO extends the v0.13.4 history and its bounds. Both new-head micro reads, complete CI, the co-op's designated pre-cue tool output and the CC's cue remain required. G5 bindings, component PSS, owner role scoping/install and fresh natural-task acceptance remain open. Landing belongs to 5f on the CC's cue. ### Host evidence The retained evidence is under `docs/decisions/`; this revision adds no `evidence/hosts/` receipt. ### Checklist - [x] Record-only scope; native observations and frozen comparison counts retained. - [x] Supported upstream payload route and full source/content pins recorded. - [x] Publication validation and appropriate targeted modules completed. - [ ] Both micro reads, complete CI, designated pre-cue output and CC cue. - [ ] G5, component memory, owner decisions and fresh owning-role acceptance.
597f11a to
f2451f7
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Preserve the exact FIX-head manifest while retaining its complete compact row snapshot and the rebuilt asset binding. Compare every ordered row field before packet selection; pin approved asset-only replacements separately. Add stale-row and immutable-manifest rebinding controls.
Separate stratum records at the pinned upstream reader safe boundaries so file scans preserve complete population digest fields. Retain the exact allowlist, rebind current receipt metadata with prior bindings retained, and add regression coverage for actual receipts and boundary detection controls.
Skip repository population receipt checks with explicit reasons when an isolated trial checkout lacks their files, and regress the native fixture step exit code. Preserve scanner error controls and bounded PR history, document empty-history skips, and correct source citations and grants accounting.
fa3a727 to
2e3a8f4
Compare
…resh (#984) * Architecture manifest: stack, layer, host and desk views from records The Architecture page now opens with four source-bound views above the existing layer ledger and custody sections: - the six-layer stack (host, agents, layer verdicts, GitHub gates, the north-star desk, monitoring), drawn as a diagram-design layer stack; - all 32 layer verdicts from the component evidence matrix, grouped by catalog and the trading catalog's recorded group (30 recorded, 2 pending_lanes); - the host deployment: the WSL release target and the new-WSL install plan's 13 services with their loopback ports, by recorded layer; - the trading desk as a six-step data flow from the gate ladder (11 of 20 gates established), the runtime target and the matrix winners. architecture_manifest.py projects only names, identifiers, versions, ports, statuses, counts and dates from six records that source_policy.json already grants exactly; reads are existence-gated, keep the fail-closed policy, and join the custody table, the receipt and the refresh signature. architecture_diagrams.py renders 1200-, 720- and 400-wide SVG variants chosen by a container query, with system fonts and page tokens for light and dark. document() gains an opt-in head argument for the inlined stylesheet. 22 new tests cover projection, rendering, custody, privacy, the matrix count and a mask-width regression. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(local-pages): exclude the two G5 landscape files that stop Architecture Since #878 (c8a29c3) added catalogs/landscape/grand-catalog-20261008.json and grand-catalog-index-20261008.json, every Architecture refresh fails closed: both landscape globs (architecture_sources.build and architecture_builder.refresh_if_changed) read each non-canonical landscape JSON under architecture_supplement, and ArchitectureReads.authorize refuses paths the policy does not grant ("Architecture role/path has no independent approval: architecture_supplement", the SourcePolicyError recorded in the local-pages refresh receipt). The live architecture.html stayed at its pre-#878 build. Granting cannot fix the 28389911-byte catalog: the globs read under a 16 MiB bound, and that limit stays. Its rows already reach the page through the retained G5 asset. The 97 KB slot index has no layers, rows, candidates or components collection, so the supplement projection would attach nothing from it, and it gets no grant either. source_policy.json gains architecture_supplement_exclusions: exact top-level landscape JSON paths, each with a reason, refused when they are also granted, protected, duplicated or outside catalogs/landscape. Both globs skip a listed file before any byte access; any other unlisted landscape file still fails closed. Exclusions appear in the receipt and the custody section. Each exclusion's pin and blob sha256 are recorded in architecture_derivation_sources. The new test module fails on the committed catalog set with the same SourcePolicyError and passes with the exclusions. It also checks that an excluded file is never opened, that unlisted files still refuse, and the exclusion validation rules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: seathatflowsinourveins <234074349+seathatflowsinourveins@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Fix the decision record of the compounding rule text, docs/decisions/2026-10-11-compounding-rule-text.md. The six rule surfaces do not change. - Approval: the owner approved section 1's proposal, the first sentence, at 22:01Z. The second sentence was presented as an optional clause and the owner's answer did not single it out; the command center (CC) included it under the owner's delegation, because it restates the owner's own no-dates direction. The owner was told at 23:44Z, with the option to drop it. The record cites the ruling's addendum-01 and the SHA256 of each sentence. - #172: restated with its recorded supersession at 22:18:17Z, under which guard bypasses are follow-ups (research-queue row 23). #1014 landed as ccff876 with only the one-letter POINTER_VARIABLE suffix. - PR triage: 3 fold receivers (#878, #927, #958) merged without their 4 donors (#804, #915, #870, #829), citing the triage's addendum-01. - What the second sentence leaves in force (F1 of the trading lane's read of us-equities-trading #87): it forbids a date as the trigger that starts work, and every time bound the contract states as a fact or protocol window stays. - Checks: the budget test's sentence now says what the test does (the first GPT read of this PR): test_growth_in_any_loaded_file_crosses_the_fixed_budget fills the available headroom in each loaded file in turn, verifies that equality with the ceiling passes, then appends a two-byte UTF-8 character and verifies rejection. - manifests/evidence.json: the record re-registered with register_file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…1020) * Rule text: work compounds through reviewed, cited repository records Add the compounding sentences of the command center's ruling, section 1 (sentence 1 owner-OK'd at 22:01Z; sentence 2 included under the owner's delegation, ruling addendum-01), to the "The ecosystem compounds" bullet on all six always-loaded rule surfaces: AGENTS.md, the portable Claude block, the Codex template, the scaffold and the two new-WSL carriers, regenerated with new_wsl_client_config.py --write-blocks. - tests: a fail-first test that every layer and native renderer carries the sentences once, in place (9 failing subtests before the change); CORE updated; the Codex top-rule pin re-derived (2,296 bytes); the startup byte ceilings raised by a dated comparison to 6,895/7,001. - docs/decisions/2026-10-11-compounding-rule-text.md: the dated trigger, evidence, surfaces, user-level pickup, budget comparison, checks and overturn conditions. - manifests/evidence.json: the changed files re-registered. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Record text: exact approval, #172 supersession, fold count, budget test Fix the decision record of the compounding rule text, docs/decisions/2026-10-11-compounding-rule-text.md. The six rule surfaces do not change. - Approval: the owner approved section 1's proposal, the first sentence, at 22:01Z. The second sentence was presented as an optional clause and the owner's answer did not single it out; the command center (CC) included it under the owner's delegation, because it restates the owner's own no-dates direction. The owner was told at 23:44Z, with the option to drop it. The record cites the ruling's addendum-01 and the SHA256 of each sentence. - #172: restated with its recorded supersession at 22:18:17Z, under which guard bypasses are follow-ups (research-queue row 23). #1014 landed as ccff876 with only the one-letter POINTER_VARIABLE suffix. - PR triage: 3 fold receivers (#878, #927, #958) merged without their 4 donors (#804, #915, #870, #829), citing the triage's addendum-01. - What the second sentence leaves in force (F1 of the trading lane's read of us-equities-trading #87): it forbids a date as the trigger that starts work, and every time bound the contract states as a fact or protocol window stays. - Checks: the budget test's sentence now says what the test does (the first GPT read of this PR): test_growth_in_any_loaded_file_crosses_the_fixed_budget fills the available headroom in each loaded file in turn, verifies that equality with the ceiling passes, then appends a two-byte UTF-8 character and verifies rejection. - manifests/evidence.json: the record re-registered with register_file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Qualify the G5 compact evidence and START closure sampler, apply the adjudicated four-row and 90-note corrections, and verify the OpenHands registry placement against pinned source bytes. The current manifest recomputes from its unpublished archive; native qualification and exact manifest/asset binding run before sampling or packet writes. The refresh documentation uses the current origin-map pin, the current J8 summary matches its42-test sampler result, and a narrowly scoped native gitleaks exception distinguishes the two population-receipt digest fields from credentials. The current forward fix also separates native stratum records with blank lines: gitleaks file fragments then retain complete digest fields, while parsed populations and the exact digest exception remain unchanged.
Scope
lane:shared; trading acknowledgement remains a landing gate.503c470149069caaf2bf9c87f24caa38091ce3a6; latest class-fix parent:b5c215ac53ed1705a078d2832e4458627f481025. The ONE cued landing rebase is complete on15d82bcc8871206476dc8c4c7bf45d347e74b2b7; the reviewed rebase head wasf2451f711d1ad16bbcb734f9e3b6c4bc40606b62, followed by N143d1bc1ad31a528b11e693d0901be50004fc7497and the file-fragment repairecad2a496c7a646bb05942c33d86a6c429683db8, followed by the ONE forward isolated-fixture fixfa3a72720d4cae557a98ef94c722f986aca75874.sync_source_entry_noteextends that same note correction to 90 PENDING rows. Only notes change. The four affected NOT units keep their verdicts, actual null-pin notes remain intact, and every original capture is preserved. The validator rejects unsynced source-entry-pin/null-note contradictions.Population digest scan
The generic API-key rule flagged 1,656 public-data digests in two G5 population receipts. An independent native in-memory verification reproduced every matched value from canonical sorted catalog keys: 414 before-population and414 after-population SHA-256 fields per receipt. No matched values were printed or included in the sanitized evidence. Both receipts remain unchanged.
The supported gitleaks8.30.1 configuration adds one
generic-api-keyallowlist requiring both an exact reviewed receipt path and an anchored match forbefore_population_key_sha256orafter_population_key_sha256containing exactly64 lowercase hex characters.regexTarget = "match"keeps the exception on the individual finding, so a co-locatedapi_keyremains detected. The scoped exception covers the original digest lines throughout the required PR history. The subsequent native file-reader failure required safe whitespace boundaries between stratum objects; current byte bindings are refreshed with previous bindings retained, and all parsed receipt values remain identical. All inherited default rules, prior exceptions and other rules remain unchanged.Regression coverage fails the original config in four digest-format/path cases and passes with the fix. Credential-shaped API keys on the same line in either approved path still fire, as do unapproved paths, non-lowercase-hex values and the GitHub PAT rule. All native test scans now use
--redact; assertions use field names and locations, and drop full finding lines that may contain adjacent values. The real-history test now scans the actual PRmerge-base..HEADrange and rejects unbounded or unrelated overrides.Current head
2e3a8f42d4643bea01189b996025db81c083f176is the ONE cued native landing rebase offa3a7272onto main0a053e1e5861a5522dcbbeea1c5006c4d8937b95, pushed with the exact old-head lease. The isolated-fixture repair and both real receipt checks remain active; the optional bash/git skip guard is included. All 11,376 evidence file rows were regenerated through the native registration API, including the auto-merged workflow-hardening third version; its current binding is SHA25647e8748f35d046a208e564d8eabd37f1c73d539e50adff7fdf8cdc01e9f9fe09, 175,127 bytes. Two unchanged canonical PDF review declarations are preserved with current reviewed-byte identity. FULL workflow-hardening and gitleaks modules passed: 185 tests, one existing workflow-only skip, rc0. FULL validation passed 70 components/11,376 files/4 profiles/239 receipts. Final committed PR-range gitleaks--log-opts=0a053e1e5861a5522dcbbeea1c5006c4d8937b95..HEADreturned rc0/zero findings. Native pre-push passed three registry tests and the 12,167-file host-name scan with zero locations. Compared with fa3a727, 61 owned nonregistry files are byte-identical; only workflow-hardening changes through the main auto-merge plus the optional guard. #878 takes no grants count.The real shard-4 isolated-fixture failure is repaired here. Inherited shard-5 reruns remain with the CC. N1 added one evidence registration row; this follow-up adds zero rows. #878 adds no grants-selected path under scripts/local_pages_policy_grants.py:46-65 and takes no grants count. Evidence-registry rows are a separate denominator. Designated micros and final CI remain pending. Landing order remains #923, #706, #943, #878; G5 stays NOT MET and the archive stays unpublished.
Rebased integration before the forward scan fix
The ONE cued rebase onto
15d82bcc8871206476dc8c4c7bf45d347e74b2b7is pushed atf2451f711d1ad16bbcb734f9e3b6c4bc40606b62with an exact lease on597f11af389ef7f100ddd9c2fff45231c892fe5c. All 57 owned non-registry files match their reviewed Git blob identities at597f11af; the production rows, original source facts, code, fixtures, documentation and receipts retain their reviewed bytes. One documentation auto-merge was restored to those exact reviewed bytes before the final check.Both shared-registry conflicts used the rebased base registry followed by native
scripts/host_receipts.py:register_filecalls for the incoming file-binding changes. The restored documentation binding was also updated natively. No registry rows were hand-merged. Non-file registry fields equal the fetched main revision, and every current registered file binding is valid.FULL
python3 scripts/validate.pyon the completed registered tree returned rc0: 70 components, 11,334 hashed files, four profiles and 239 receipts. The native verdict gate against15d82bccreturned rc0 with zero changed verdict rows and zero violations. Cached whitespace, native pre-commit and all three native pre-push registry tests passed; the native host-name scan reported zero matching locations across 12,129 files. The exact-lease push succeeded and the remote head was independently verified. Prior 95-test compact and 42-test sampler results retain their unchanged-source/input scope; this rebase did not execute a new draw, model, provider or broker run.Earlier reads remain historical. The original co-op GPT micro continues, and the CC delta read passed with P3s and the long GPT micro repeats the already-fixed shard-4 finding. The co-op per-file same-change check and fresh hosted CI on the landing-rebase head remain separate gates. G5 stays NOT MET and the archive stays unpublished.
Source bindings and placement regression
The current refresh instructions in both G5 documents bind the 3,064,963-byte origin map to SHA256
50a577cb25fc0650355c3ddf9b709b18d0fadb5a426415b6f497c1e78fe83e7a. The historical b5 receipt retains its older hash. Both corrected instructions pass the unchanged nativepinned_bytescheck.The complete 21,348-byte
openhands/extensions@ba3f165139cd3705c5d56a4ca26293d11a464c7b:AGENTS.mdbody is retained inevidence/artifacts/g5-start-closure-1-20261009/openhands-slot-regression/AGENTS-ba3f1651.txt, SHA256d71111c39c773c9c238e32e517c074b8b7ab6115592440bf6c0d243b331326c9. The same source-bound placement assertion fails on exact retained pre-fixagent-sdksdata and passes on currentinstructions-skills/TRIAL data. Separate assertions preserve the complete workers row and immutable original claim-member bindings. This is a local data regression, with source review evidence; it does not assert runtime adoption.Only the current J8
TA_N7summary changes to 42 tests. Its nested historical 41-test statement stays intact, andnote-class-fix.jsonbinds the updated current receipt. The manifest, origin map, selector, archive and historical four-row receipt remain unchanged. The pre-rebase content micro-fix was ONE commit597f11af389ef7f100ddd9c2fff45231c892fe5con3ed3f6ff73f2392f22e81e248f26c767c45346bc, without rebase.evidence/artifacts/g5-start-closure-1-20261009/micro-fix-3ed3f6ff.jsonretains the source, before/after and preservation evidence.Pre-rebase content verification: the exact old-data placement test fails as intended (rc1); the current three-test placement class passes (rc0); the whole compact module passes 95 tests with the two named external-fixture skips (rc0). Native registration of eight changed/new files and registry ordering pass. FULL
python3 scripts/validate.pypasses 70 components, 10,920 hashed files, four profiles and 237 receipts (rc0). Cached whitespace, native pre-commit and all three native pre-push registry tests pass. Exact-lease push against3ed3f6ffsucceeded. Earlier 42-test sampler and 414-population results retain their unchanged-input scope; neither was repeated or relabeled by this micro fix. The co-op GPT micro acknowledged the content at597f11af. Current-head CC review and full hosted CI remain pending.SOTA sources
gitleaks/gitleaks v8.30.1, commit
83d9cd684c87d95d656c1458ef04895a7f1cbd8e:config/gitleaks.tomlgeneric-api-key rule, native rule-specific allowlists inconfig/allowlist.go/detect/detect.go, andreport/finding.go:Finding.Redact. The installed release and actual context-restriction controls agree. Native file fragmentation is settled bysources/file.go:21,166-246andsources/common.go:16,56-125; actual receipt and synthetic boundary regressions exercise those supported safe separators.Native G5 decision and refresh procedure at
b5c215ac53ed1705a078d2832e4458627f481025:docs/decisions/2026-10-08-g5-compact-evidence.md,compact_manifest.py,start_closure_sampler.pyand the sealed stratum contract. START profile and the CC class addendum govern counted residue; non-action table codes are not blanket defects.Sealed R3 helper SHA256
759facff52170f452290077b71d328f299b2c763df0358d126973c60886515c7, with retained historical R3 SHA25680e69ff94f97fffdf906583fa280f2a60a7487a54f0b58b05342264a5adf9627. Nativepopulation_key_sha256and stratum definitions supply every population comparison.CPython 3.14.4 random.py, exact sealed runtime source hash checked by the native loader; GNU tar and facebook/zstd supply supported archive construction, with exact executed arguments retained in the class-fix receipt.
OpenHands/extensions AGENTS.md establishes the corrected instructions/skills slot; its historical workers row and original claims remain unchanged.
Native unittest controls reuse
tests.test_compact_manifest.CompactManifestTests; native registration usesscripts.host_receipts.register_fileand the FULL publication checker. No alternate sampler, population hash or qualification runner was introduced.Evidence-class table
source_review/ local artifact comparisonlocal_integrationsyntheticlocal_integrationCurrent artifact bindings
0aeb16e1142a22a69d2e1bcded70a74df2db3e81fe6c01d42771d00589d3d35a, 56,463,125 bytes.afb38c9427d7a344792b5ddcfa7cab64e9613a2fda64d1cecb30e2b0eae825bb.50a577cb25fc0650355c3ddf9b709b18d0fadb5a426415b6f497c1e78fe83e7a.compact/rows.jsonandSHA256SUMSacross 13,486 file members. Every original capture and the coverage member remain byte-identical.note-class-population-receipt.jsonrecords all 414 membership/disposition hashes and native selected-key equality. No production redraw, new seed, sampled-stratum re-read or re-adjudication is required by the CC population rule.Local commands run
Historical failures and limits
The retained complete CI3.13.16 discovery remains a failed broad suite: 11,834 tests, 22 failures, 1,187 skips. The strict comparison is 21 pre-existing / 0 introduced proven / 1 unresolved. A separately documented source analysis attributes the sole two-line diagnostic ordering difference to unchanged set output; it does not replace the strict comparison or claim a broad PASS. The broad run lacked jsonschema and skipped sampler controls; the current 42-test native sampler run is fresh and uses the required generator/runtime.
Earlier incomplete runs, fixture setup failures, the unpinned runtime refusal and initial directory-metadata sync refusal remain recorded. The J8 receipt preserves its original historical preparation and separates current bindings. No native test or generated packet establishes a new model read or upstream runtime acceptance.
Earlier branch CI failed on historical population digests. Run38019766374 later passed the git-history and allowlist-test steps but failed its native working-tree step with two findings; the same two public receipt fixtures reproduced that failure and now return zero findings. A 55-second FULL-validation carrier timeout and a pre-push scratch-capacity failure were retained as failed attempts; the same FULL validation completed with a larger carrier timeout, and the unchanged native pre-push gate passed with its supported TMPDIR outside the full tmpfs. Shared scanner policy ownership has been routed to the co-op; no policy bypass is part of this fix. Any repository scan is restricted to the actual merge-base..HEAD range under the current standing rule.
Decision record and gates
docs/decisions/2026-10-08-g5-compact-evidence.mdlinks the four-row receipt, current class-fix receipt, complete population tables and archive construction evidence. The local completeness critic verified scope, original captures, all 414 native hashes and actual sampler output; its two receipt/doc wording findings are corrected. This critic is separate from designated acceptance.G5 remains NOT MET; G5-F1 through G5-F4, designated GPT/CC micros, trading acknowledgement, final-head CI, pre-cue and explicit CC landing/release remain open. The archive remains unpublished. The 07:39Z cued landing rebase onto0a053e1e is complete; the CC controls readiness, landing after #962/#961, and release. Standard-tier relaunch follows landing at the task boundary before the wave catalog PR.
Checklist
597f11af; all 57 reviewed non-registry files are byte-identical at the rebased head.15d82bccwith native registry reconstruction.