test(release-lines): enforce ledgered semantic parity

[zoeyrose]

Parent: #113
Depends on: #137

Outcome

Add a deterministic, read-only semantic comparison that enforces the
machine-readable release-line ledger instead of relying on periodic manual tree
diffs.

Scope

• Compare main and 1.x through stable content-catalog identities and the
  shared lossless content core using an explicit --other-root.
• Compare shared authored fields semantically, independent of harmless field
  serialization order.
• Permit release, provider, provenance, consumer, and tooling differences only
  through narrow records in feat(release-lines): record a machine-readable parity ledger #137's ledger.
• Fail on unclassified additions, removals, changed shared values, duplicate
  ports, missing companions, malformed records, and stale exceptions.
• Keep the command local, deterministic, network-free, and read-only.
• Never require or recreate maps/light-source-evidence/, capture manifests,
  screenshots, generated output, or mutable runtime state.
• Rebaseline only after the queued branch-native lighting companions reach
  their intended final state.

Required cases

• Exact cross-line patches.
• Equivalent authored results with line-specific integration.
• Intentional main-only provenance and 1.x-only release/runtime products.
• The two forcefield files whose name_pl and light_color records are merely
  ordered differently.
• A pending glower result until feat(lighting): consolidate glower illumination onto visible fixtures #103's main companion lands.

Terminal suffix enforcement

Run terminal delivery only after #138 and all substantive work have merged and
an immutable pre-ledger horizon has been frozen for each line. Treat authored
domain files, including maps/light-source-review.json, as substantive; they
are never terminal control-plane maintenance.

Before the first terminal merge, require the durable declaration in #154,
#113, and the program report to give, per line, the exact horizon, the exact
ordered count of remaining squash commits, and each ordinal's owning issue/PR
and exact changed-path allowlist.

The audit must fail unless each final suffix has exactly the declared length
and order and every ordinal has exactly its declared changed-path set. Any
missing, extra, or reordered commit, or any missing or out-of-allowlist path,
requires a newly frozen horizon and complete declaration before another
terminal merge.

Actual squash SHAs are recorded after merge in #154, #113, and the program
report and then checked against the declared ordinals. No commit may be
required to contain its own SHA.

Acceptance criteria

• The audit reports no unclassified shared authored-content difference in
  either direction at recorded immutable coordinates.
• Tests cover additions, removals, value changes, duplicate ports,
  malformed entries, and stale exceptions.
• Ordering-only differences do not create false positives.
• Pending ledger records fail once their owning issue is delivered or no
  longer matches the tree.
• Both branch validators, the cross-line audit, and git diff --check
  pass independently.

[zoeyrose]

Maintainer merge gate — terminal 1.x ordinal 2

Please squash-merge only PR #184 next.

• PR: test(release-lines): enforce semantic parity #184
• Base: 1.x
• Exact live base / observed ordinal-1 squash: 25bc88fa43d529d8c9fec568772632b6dccb800a
• Exact head: 6360d5be285caba2d708e1448e1f3f656d5aa909
• Reviewed result tree: 30e4ef7218c97b8bcd4d11f8a8e76820234bda48
• Shape: one commit; exactly the three declared ordinal-2 paths
• Merge state: mergeable / clean
• Reviews and comments: none
• Checks on this exact head: Content validation passed; post-ready conventional title passed; Ubuntu syntax prototypes passed; Windows syntax prototypes passed
• Validation: 21 focused parity tests; full 1.x aggregate passed 155 tests plus audits and package checks; paired terminal-candidate audit passed with 43/43 exceptions, two authored semantic equivalences, 8,105 definitions per line and zero definition drift, one classified reference delta, and seven exact patch outcomes; git diff --check clean; independent final-tree reviews found zero actionable findings

Required global order remains:

1. PR fix(release-lines): record parity ledger #182 (1.x ordinal 1) — merged and exact as 25bc88fa43d529d8c9fec568772632b6dccb800a
2. PR feat(release-lines): record parity ledger #183 (main ordinal 1) — merged and exact as f1fd473b4dac03e4bdb439a6925f136451ad53ef
3. PR test(release-lines): enforce semantic parity #184 (1.x ordinal 2) — merge now
4. PR test(release-lines): enforce semantic parity #185 (main ordinal 2) — still draft and unauthorized

After #184 merges, I will re-query both live tips, require its sole parent/tree/path set and total two-commit suffix to match the frozen declaration exactly, and durably record the actual squash SHA in #154, #113, and the program report before rebuilding or enabling #185. Do not merge #185 yet.

#139, #113, and #154 remain open; this gate does not authorize issue closure.

[zoeyrose]

Maintainer merge gate — terminal main ordinal 2 (final terminal merge)

Please squash-merge only PR #185 next.

• PR: test(release-lines): enforce semantic parity #185
• Base: main
• Exact live base / observed ordinal-1 squash: f1fd473b4dac03e4bdb439a6925f136451ad53ef
• Exact head: 7e5a180a6be1a8476ad4c37852f73cc2da6b3ac7
• Reviewed result tree: ecbb60b15202300421f93af76ce46e357281dcdc
• Shape: one commit; exactly the three declared ordinal-2 paths
• Merge state: mergeable / clean
• Reviews and comments: none
• Checks on this exact head: Content validation passed; post-ready conventional title passed; Ubuntu syntax prototypes passed; Windows syntax prototypes passed
• Validation: 21 focused parity tests; full main aggregate passed 153 tests plus audits and package checks; paired terminal-candidate audit passed with 43/43 exceptions, two authored semantic equivalences, 8,105 definitions per line and zero definition drift, one classified reference delta, and seven exact patch outcomes; git diff --check clean; independent final-tree reviews found zero actionable findings

Required global order:

1. PR fix(release-lines): record parity ledger #182 (1.x ordinal 1) — merged and exact as 25bc88fa43d529d8c9fec568772632b6dccb800a
2. PR feat(release-lines): record parity ledger #183 (main ordinal 1) — merged and exact as f1fd473b4dac03e4bdb439a6925f136451ad53ef
3. PR test(release-lines): enforce semantic parity #184 (1.x ordinal 2) — merged and exact as 0032e319dde316c2076832066fb5381177b34f42
4. PR test(release-lines): enforce semantic parity #185 (main ordinal 2) — merge now

After #185 merges, I will re-query both live tips, require its sole parent/tree/path set and both complete two-commit suffixes to match the frozen declaration exactly, record the actual squash SHA in #154, #113, and the program report, rerun final-tip validation/checks, and update #113/#154 as ready for human closure while leaving them open.

Do not close #139, #113, or #154 as part of this merge.

[github-actions]

🎉 This issue has been resolved in version 2.13.1 🎉

The release is available on:

• v2.13.1
• GitHub release

Your semantic-release bot 📦🚀