fix(ci): decouple current GeoJSON receipt validation

[bartytime4life]

Goal

Repair the post-merge spec-hash receipt gate for the structural GeoJSON digest implementation merged through PR #2099, without rewriting its historical authoring receipt.

Failure record

The PR #2099 spec-hash run completed dependency installation and the deterministic no-network test step successfully. The final receipt step failed because the workflow also revalidated the pre-existing historical genrec-spec-hash-validator-20260806.json against the workflow's newly changed current bytes. That receipt accurately describes its earlier artifact state and should remain immutable; using it as a perpetual current-state assertion created stale receipt coupling.

During this follow-up, the first exact-head attempts also exposed an over-broad receipt artifact set and a one-character workflow job-name byte mismatch (validate-commmon-spec-hash). Those were corrected before the final exact-head run.

Base and exact head

• Base: main at 8ee05f3738c29344d055025bf47448150429e05e
• Exact head: c220b776e9bde12ba1fc15c109e8069fd8b43260
• Delivery: draft pull request
• Mergeable: yes

Changes

1. Preserve the historical PR feat(hashing): add deterministic GeoJSON feature digests #2099 authoring receipt unchanged.
2. Add data/receipts/generated/genrec-geojson-feature-digests-ci-repair-20260807.json as a current follow-up receipt.
3. Bind that receipt only to the two non-receipt artifacts modified by this follow-up: the workflow and durable tool documentation. The merged implementation and tests remain cited repository evidence rather than being misrepresented as newly authored files.
4. Change .github/workflows/spec-hash.yml to validate the new current-state receipt instead of treating the unrelated historical receipt as a mutable assertion about current workflow bytes.
5. Correct the existing workflow job-name typo and align its exact bytes with the receipt.
6. Correct tools/spec_hash/GEOJSON_FEATURE_DIGESTS.md so its status reflects that PR feat(hashing): add deterministic GeoJSON feature digests #2099 is merged rather than pending on a feature branch.

Directory Rules basis

This repair stays within existing responsibility roots:

• .github/workflows/ owns GitHub Actions orchestration.
• data/receipts/generated/ owns immutable AI-authoring process memory.
• tools/spec_hash/ owns operator-facing documentation for the existing hashing tool.

No new root or parallel schema, contract, policy, source, registry, proof, release, or publication authority is created.

Exact-head validation

PASS — spec-hash run 31147952118

At exact head c220b776e9bde12ba1fc15c109e8069fd8b43260:

• checkout without persisted credentials passed;
• repository Python setup passed;
• declared dependency installation passed;
• deterministic no-network spec-hash and GeoJSON digest tests passed;
• current generated authoring receipt integrity passed;
• trust-boundary summary completed.

Job: validate-common-spec-hash, job ID 92771333160.

PENDING / outside the bounded repair

• human review;
• unrelated repository-wide workflows may continue independently and are not evidence for or against this receipt-gate repair unless a causal failure is identified.

Trust boundary

This change repairs CI process-memory validation only. It does not alter GeoJSON digest semantics, reproject or validate topology, admit a source, resolve evidence, evaluate policy, approve review, promote lifecycle state, release, deploy, publish, or create public-use authority.

Commits

• e41e1f655d809028190341885ec1241d652e835a — initial historical-receipt decoupling
• de0850c99f6cf4df578d70f04e564341e8f3722f — narrow receipt to follow-up-authored artifacts
• c220b776e9bde12ba1fc15c109e8069fd8b43260 — align workflow bytes and correct job-name typo

Rollback

Close this draft and delete the branch before merge, or revert the eventual merge/squash commit after an authorized merge. Rollback restores the prior workflow coupling and stale documentation but requires no source deactivation, data migration, release withdrawal, cache invalidation, or public correction.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.