Make proactive harness improvement explicit in the shared core - #881

### Scope

The dated readiness manifest still reports G6 as HOLD after #881 landed and the F9 receipt accepted G6a. Split that gate into G6a (MET), G6b (ongoing settings ownership), and G6c (ongoing records, #885/#886), and bind G5's six closure requirements without granting G5 acceptance. Update the matching R&D and follow-up state displays from the same accepted receipts.

- Base commit: `aba02ec3456d383bcc2fc72883db098f9be7918a`
- Lane: `lane:foundation`
- Owned paths touched: `tools/north-star/sources.json`, `catalogs/north-star/readiness.json`
- The existing builder regenerates the complete dated view, including current main-input provenance digests. Its 20 layer scopes and 36 SDK items remain. The evolving Monitoring status source matches the owner selector twice, so that single field becomes UNVERIFIED; its bounded snapshot is distinct from the separately preserved Monitoring follow-up.

## SOTA sources

- Existing reference implementation: [native-agent-stack at aba02ec, tools/north-star/build_readiness.py](https://github.com/seathatflowsinourveins/native-agent-stack/blob/aba02ec3456d383bcc2fc72883db098f9be7918a/tools/north-star/build_readiness.py), `Receipts.claim` and the supported `--write`/`--check` interface. This change uses the shipped receipt adapter and its digest-bound selectors. The gate-refresh procedure is documented in [tools/north-star/README.md, Refresh on a gate change](https://github.com/seathatflowsinourveins/native-agent-stack/blob/aba02ec3456d383bcc2fc72883db098f9be7918a/tools/north-star/README.md#refresh-on-a-gate-change).
- The original adapter's retained upstream survey is `research/fullspeed-20261008/ns-readiness-manifest/upstream-research.md` under the durable state root; the implementation follows [Python 3.13 re](https://docs.python.org/3.13/library/re.html) for exact text selection and [SLSA v1.2 verification](https://slsa.dev/spec/v1.2/verifying-artifacts) for the distinction between input identity and acceptance. This is a source-binding refresh of that accepted implementation.
- Gate evidence: `coordination/command-center/windows/f9-g6a-881-20261008/RECEIPT.md`, SHA256 `24906eaf9cc3f041ed6bd500dd41095e4282a551ad1403d80a76a709ce7cf6a1`; line 3 identifies [#881](#881 merge commit and timestamp, line 5 records F9 application, lines 14–15 record both fresh-session checks, and line 17 adjudicates G6a and the remaining G6 scopes. Installed `gh` 2.102.0 independently returned the same #881 merge metadata and OPEN draft record PRs [#885](#885) and [#886](#886).
- G5 requirements: `coordination/command-center/ITEM-ns2604-coop-20261008T210228Z.md`, SHA256 `d3868b6a0a81826407ade426c6f8a2c6511401177d3801eb24b3ae0e9023aa43`, lines 16–21. The six criteria cover population witnesses; row evidence with conservative PENDING dispositions; the mined-list census; validation of the full 368-star/45-field/2-document asset; both-family reads of 113 action rows plus seeded 59-row samples per stratum with zero defects; and a cued release of the hash-pinned asset. These fields record requirements rather than passed checks.

### Evidence-class table

| Claim | Evidence class | Command / receipt |
| --- | --- | --- |
| G6a is MET, #881 merged at `2026-10-08T20:41:37Z` as `e48de2e6fa1dd3b740af4793ea5824ea35476dba`, and F9/fresh-session checks are retained | source_review | F9 receipt at the SHA256 above; bounded `gh pr view 881 --json number,title,state,isDraft,mergedAt,mergeCommit,url` |
| G6b/G6c continue, with #885/#886 covering records | source_review | F9 receipt line 17; bounded GitHub PR metadata |
| G5 has six required closure conditions and remains the open START gate | source_review | G5 task record at the SHA256 above, lines 12 and 16–21 |
| The manifest reproduces the declared sources and joins each new gate field to exactly one retained selector | local_integration | Builder `--write`, `--check`, and focused gate/receipt integrity assertions, rc 0 |
| Adapter and page-publication regressions pass | synthetic | `tests.test_north_star_readiness`, 32 fixture tests, rc 0 |
| Repository publication integrity and scope pass | local_integration | `python3 scripts/validate.py`, rc 0; 70 components, 10,900 hashed files, 4 profiles, 239 receipts |

### Local commands run

```sh
nice -n 10 ionice -c2 -n7 python3 -I tools/north-star/build_readiness.py --write
# rc 0; 8 gates, 20 layers, 36 SDK items
nice -n 10 ionice -c2 -n7 python3 -I tools/north-star/build_readiness.py --check
# rc 0; manifest SHA256 0e2dba792fff6d4adbc13b47995474591f1024e8253bd7e5caf3a5c4db619aae
timeout 600 nice -n 10 ionice -c2 -n7 python3 -m unittest tests.test_north_star_readiness
# rc 0; 32 tests, OK
nice -n 10 ionice -c2 -n7 python3 scripts/validate.py
# rc 0; integrity and scope passed
git diff --check
# rc 0
```

Durable logs under `research/fullspeed-20261008/ns-readiness-manifest/`:

- `g6-split-targeted-tests.log`, SHA256 `fcee3223b60efc73e55954ea5d703f2b75952d3a6b8d9965e7127379f70b03cc`.
- `g6-split-publication-validate.log`, SHA256 `9106406d71891d803b9ed1569f54c5df6195c29846e57e0f1c284e993ce92652`.

### Decision record

This is the accepted gate-receipt refresh requested by task `task-ns2604-coop-20261008T212726Z`. The two named immutable source records above establish its scope; source selectors retain full digests and exact line locators. A replacement adjudication receipt would supersede these values through the same supported refresh procedure.

### Host evidence

This PR changes the readiness view and its selectors. Host-evidence receipt requirements are not applicable to its owned paths.

### Checklist

- [x] New/changed GitHub Actions are pinned to a full commit SHA with a version comment (no floating tags). Not applicable to this data refresh.
- [x] New/changed workflows declare top-level `permissions: {}` and grant each job only what it needs. Not applicable to this data refresh.
- [x] No secrets are printed, logged or committed; no new required secret was added without a documented owner.
- [x] No new paid hosting, subscription or billing surface was introduced.
- [x] Peer-owned untracked files and worktrees were preserved (not deleted, moved or overwritten).