fix(release-lines): reconcile and continuously audit main/1.x content parity

[zoeyrose]

Outcome

The cross-release-line reconciliation and continuous semantic audit are delivered at the exact final tips below. This issue is ready for maintainer closure but remains open by program policy.

Release line	Immutable pre-ledger horizon	Final tip	Final tree
1.x	07f9bd418926066503d569b8457175191176434d	0032e319dde316c2076832066fb5381177b34f42	30e4ef7218c97b8bcd4d11f8a8e76820234bda48
main	3ebb1710dd90a57779e4e025778f8ed9dec8053e	3beec723be15d9f58d6321f728f5d73d33a00013	ecbb60b15202300421f93af76ce46e357281dcdc

Delivered companion outcomes

Issue	1.x outcome	main outcome
#105	PR #112 merged	PR #111 merged; fresh-character apartment scenario maintainer-attested
#103	PR #114 already merged	PR #156 merged
#135	PR #157 merged	PR #158 merged
#136	authoritative descriptor already correct; explicit no-change exception	PR #159 merged
#91	PR #115 merged	PR #129 merged
#102	PR #116 merged	PR #161 merged
#99	PR #117 merged	PR #163 merged
#98	PR #118 merged	PR #165 merged
#95	PR #119 merged	PR #167 merged
#96	PR #120 merged	PR #168 merged
#86	PR #122 plus corrective PR #171 merged	PR #176 merged
#92	PR #123 merged	PR #177 merged
#90	PR #121 merged	PR #178 merged
#138	PR #179 merged	PR #180 merged
#137	PR #182 merged	PR #183 merged
#139	PR #184 merged	PR #185 merged

Exact terminal suffix

The declaration was frozen before the first terminal merge and matched without a new horizon:

1. 1.x ordinal 1 / feat(release-lines): record a machine-readable parity ledger #137 / PR fix(release-lines): record parity ledger #182: 25bc88fa43d529d8c9fec568772632b6dccb800a — exact six-path allowlist.
2. main ordinal 1 / feat(release-lines): record a machine-readable parity ledger #137 / PR feat(release-lines): record parity ledger #183: f1fd473b4dac03e4bdb439a6925f136451ad53ef — exact six-path allowlist.
3. 1.x ordinal 2 / test(release-lines): enforce ledgered semantic parity #139 / PR test(release-lines): enforce semantic parity #184: 0032e319dde316c2076832066fb5381177b34f42 — exact three-path allowlist.
4. main ordinal 2 / test(release-lines): enforce ledgered semantic parity #139 / PR test(release-lines): enforce semantic parity #185: 3beec723be15d9f58d6321f728f5d73d33a00013 — exact three-path allowlist.

Each line has exactly two ordered commits after its horizon. No commit was required to contain its own SHA; the actual squash SHAs were recorded after each merge in this issue, #154, and the program report.

Final semantic audit

• 61 post-fork horizon commits are represented exactly once in 32 outcomes.
• Classifications: 20 equivalent, 7 exact, 5 exempt, 0 pending.
• All 43 resulting-tree differences have exact, semantic, or narrow evidence-backed classification.
• Two authored forcefield paths are semantically equal despite record ordering.
• Both lines contain 8,105 catalog definitions with zero definition differences; one branch-native reference difference is classified.
• Seven exact outcomes have identical stable patch IDs.
• maps/light-source-review.json remains authored semantic evidence and was not treated as terminal maintenance.

Exact-tip validation

• Non-candidate paired audit passes on the real final squash commits with both terminal records reporting candidate: false.
• main: python3 tools/validate.py passes 153 tests plus all audits; package/resource checks exit zero.
• 1.x: python3 tools/validate.py passes 155 tests plus all audits; both release package checks pass.
• Both light audits pass with 117 archetypes, 10 artifacts, 11,682 instances across 638 maps, 6,338 explicit colors, 5,471 intentional neutral assignments, and zero unreviewed emitters.
• GitHub exact-tip checks pass on both lines: Content validation, Ubuntu syntax, Windows syntax, and Semantic release.
• git diff --check passes and both fresh worktrees are clean.
• No retired evidence directory/manifest, proof scene, capture tool/test, views, or evidence_focus field is tracked on either line.
• Optional renderer diagnostics remain outside the repository under ignored/deployment-owned output.

Closure readiness

All acceptance criteria are satisfied and no shared-authored outcome remains pending. Maintainers may close #113 after reviewing this exact-tip record. Do not infer closure of #154 from this issue automatically; #154 owns the final program-level human closure.

The planned single-main content consolidation remains follow-up work in #166 under atrinik/atrinik#357; it is intentionally separate from this completed two-line audit.

[zoeyrose]

Immutable terminal declaration

All substantive delivery through #138 is merged. The terminal candidates, exact remote trees, declared machine ledger, aggregate validation, complete cross-line candidate audit, and independent reviews are now proven. This declaration freezes the following horizons before the first terminal merge:

• 1.x: 07f9bd418926066503d569b8457175191176434d
• main: 3ebb1710dd90a57779e4e025778f8ed9dec8053e

Each line has exactly two remaining squash commits, ordered #137 then #139. The global maintainer merge order is:

1. 1.x ordinal 1 — feat(release-lines): record a machine-readable parity ledger #137 / PR fix(release-lines): record parity ledger #182
2. main ordinal 1 — feat(release-lines): record a machine-readable parity ledger #137 / PR feat(release-lines): record parity ledger #183
3. 1.x ordinal 2 — test(release-lines): enforce ledgered semantic parity #139 / PR test(release-lines): enforce semantic parity #184
4. main ordinal 2 — test(release-lines): enforce ledgered semantic parity #139 / PR test(release-lines): enforce semantic parity #185

1.x suffix

Ordinal 1 — issue #137 / PR #182; current head a142b2bec8688abd7591fee69df362935c888682; result tree 333351401a5f9f4632a2b8b7d9f0c7528ab64272; exact paths:

• contracts/release-lines/parity-ledger.json
• contracts/release-lines/parity-ledger.schema.json
• docs/RELEASE_LINES.md
• tools/release_line_parity.py
• tools/tests/test_release_line_parity.py
• tools/validate.py

Ordinal 2 — issue #139 / PR #184; current stacked head 090da66f8e748744cea94016e5a5ab8f2cad095f; result tree 30e4ef7218c97b8bcd4d11f8a8e76820234bda48; exact paths:

• docs/RELEASE_LINES.md
• tools/release_line_parity.py
• tools/tests/test_release_line_parity.py

main suffix

Ordinal 1 — issue #137 / PR #183; current head ce138497e43f44d10a59676b19fe725ffd01ef8d; result tree d245850bf6b5e3651364e0f9c3ecabe779dd76dc; exact paths:

• contracts/release-lines/parity-ledger.json
• contracts/release-lines/parity-ledger.schema.json
• docs/RELEASE_LINES.md
• tools/release_line_parity.py
• tools/tests/test_release_line_parity.py
• tools/validate.py

Ordinal 2 — issue #139 / PR #185; current stacked head af59641613fea9d5fa0cbd7e6ef8ba10f6d17e81; result tree ecbb60b15202300421f93af76ce46e357281dcdc; exact paths:

• docs/RELEASE_LINES.md
• tools/release_line_parity.py
• tools/tests/test_release_line_parity.py

Enforcement and evidence

• Final suffix length, issue/PR ownership, ordinal order, and every ordinal's complete changed-path set must match exactly.
• Any missing, extra, reordered, missing-path, or out-of-allowlist commit invalidates these horizons and requires a new complete declaration in chore(release-lines): complete the cross-line lighting and parity program #154, fix(release-lines): reconcile and continuously audit main/1.x content parity #113, and the program report before another terminal merge.
• After every merge, both live tips are re-queried, the resulting squash is audited against its ordinal, and its actual SHA is recorded in chore(release-lines): complete the cross-line lighting and parity program #154, fix(release-lines): reconcile and continuously audit main/1.x content parity #113, and the program report.
• No commit contains or is required to contain its own SHA.
• Authored-domain files, including maps/light-source-review.json, remain substantive and are not terminal control-plane maintenance.
• Retired evidence, manifest, proof-scene, capture tool/test, and capture-bound fields remain absent and fail closed.

Validation at the final candidate suffixes:

• full cross-line candidate audit: 43/43 tracked-tree exceptions, two typed authored order-only equivalences, 8,105 definitions on each line with zero definition drift, one classified reference delta, seven exact patch outcomes, exact two-commit suffixes and exact path sets;
• focused parity suite: 21/21;
• aggregate: 155 tests on 1.x plus release packaging; 153 tests on main (the final two mode regressions add to the previously completed 152/150 runs; focused and full audit rerun after the correction);
• both independent final reviewers report zero findings;
• all four remote result trees exactly match the reviewed local trees.

PRs remain drafts until their individual human gates. First permitted merge is PR #182 only. #113 and #154 remain open.

[zoeyrose]

Terminal squash record — 1.x ordinal 1

PR #182 was squash-merged at 2026-08-12T18:07:22Z.

• Actual squash SHA: 25bc88fa43d529d8c9fec568772632b6dccb800a
• Sole parent / immutable pre-ledger horizon: 07f9bd418926066503d569b8457175191176434d
• Result tree: 333351401a5f9f4632a2b8b7d9f0c7528ab64272
• Live 1.x tip: 25bc88fa43d529d8c9fec568772632b6dccb800a
• Independently refreshed live main tip: 3ebb1710dd90a57779e4e025778f8ed9dec8053e
• Suffix audit: exactly one commit after the horizon; no missing, extra, or reordered commit
• Changed paths, exactly matching declared ordinal 1:
  • contracts/release-lines/parity-ledger.json
  • contracts/release-lines/parity-ledger.schema.json
  • docs/RELEASE_LINES.md
  • tools/release_line_parity.py
  • tools/tests/test_release_line_parity.py
  • tools/validate.py
• Pre-merge checks: Content validation, conventional title, Ubuntu syntax prototypes, and Windows syntax prototypes all passed.

This records the resulting squash SHA after merge; no commit was required to contain its own SHA. The frozen horizons and remaining two-commit-per-line declaration are unchanged. The next authorized merge is main ordinal 1, PR #183. PRs #184 and #185 remain unauthorized.

#113 and #154 remain open; this is a tracking update, not closure.