docs(gap-baseline): separate current authority from historical loop snapshots

[seonghobae]

Product/documentation defect

Protected main@83eba56149eb802cd63642c507c324c9976ec78e still opens docs/product-technical-gap-baseline.md with historical loop overlays whose once-current PR/check language can be mistaken for present product authority. Those entries remain useful traceability evidence, but historical operational snapshots must not outrank protected code/release facts or dated live receipts.

This issue owns documentation convergence only. Do not rewrite historical facts to look current, delete traceability evidence, or duplicate active feature/owner repairs.

Executable repair lane

PR #1041 owns the current documentation repair at exact head b3a4824009d1553f9f7cf73953224fcbfdde4aff on protected base 83eba56149eb802cd63642c507c324c9976ec78e. Its single-file delta refreshes the current authority overlay, explicitly treats mutable PR/Issue counts as a timestamped operational snapshot, retracts stale #996 Ready/auto-merge language, and references current repair ownership rather than copying domain truth.

Current exact-head validation is repository-clean: fresh Tests 34692696780, CodeQL PR 34690294200, Security 34690294171, SAST 34690294177, OpenCode 34690293040, Strix 34690293027, review scheduler, dynamic CodeQL and Code Quality are SUCCESS.

The remaining blocker is independent exact-head review evidence. Required Noema run 34690293039 also concludes SUCCESS, but job 103545063404 skips both the publication-token refresh and Publish prepared Noema verdict on the exact live head. The Reviews API therefore contains only predecessor-head Noema approval 8f7f54142afa9527da4996dc98ed1b4a745e6bd2, not an authenticated verdict for current b3a482.... This exact consumer canary is now recorded at canonical owner .github#2045. #1041 has returned to Draft rather than treating status-only success or predecessor approval as merge evidence.

RED → GREEN acceptance

1. Keep one clearly named current-authority section whose mutable operational claims are explicitly time-scoped.
2. Preserve older overlays as historical evidence without letting unqualified current, still, queue counts, Ready/auto-merge state or equivalent mutable wording masquerade as present authority.
3. Keep PRD/TRD/ARCHITECTURE/release metadata and the baseline aligned with LineageWeave's DDD/product boundaries; reference canonical owners rather than copying their truth.
4. Keep documentation hygiene and all exact-head product/security gates GREEN.
5. Require an authenticated independent review verdict bound to the exact current head; a workflow/status success with skipped verdict publication or predecessor approval is not acceptance.
6. Integrate normally through protected branch rules. No self-approval, Admin bypass, no-op source churn, force push, destructive rebase or stale-head evidence transfer.

Keep this issue open until #1041, or a verified successor carrying all valid documentation/test/evidence deltas, is normally integrated.

[seonghobae]

Fresh convergence note (2026-09-06): #960's review repair is now GREEN and promoted non-force to ff72846f86f82f4b470578d69a9395e65fb31152; its gap-baseline delta converts the bounded audit/delivery wording to dated observation and pins the unreadable-write no-retry contract. #964 concurrently adds a 2026-09-06 dated observation plus the Historical observations (dated; not current authority) boundary, but its current-head review found two valid repair findings and #964 is back in Draft under automation/964-review-repair-20260906, run 34040709061. Treat both as ordinary predecessor deltas when implementing this issue: do not overwrite #960's time-scoping or #964's dated observation, and do not declare this broader current-authority defect closed until the documentation-governance regression in this issue is executable and GREEN.

[seonghobae]

Fresh owner-path evidence from #964: exact 2fd2f49d68b0faff5eb33b05fbb5c4dc0725a413 still contains a dated baseline observation that says #964 is Ready with normal squash auto-merge enabled and existing auto-merge settings preserved. The live REST PR snapshot now reports draft=false (Ready for exact-head validation) but auto_merge: null, mergeable_state: blocked; current Tests are queued on runner_id=0 and no qualifying independent approval exists. CodeRabbit thread PRRT_kwDOT22WIM6ftF84 remains unresolved. Keep #963's broader convergence responsible for making these operational observations explicitly time-scoped/non-authoritative; #964 should not turn mutable PR state into product truth.

[seonghobae]

2026-09-12 current-authority owner-path convergence evidence:

• protected main is still exact 83eba56149eb802cd63642c507c324c9976ec78e with valid commit verification; it is not the older cb187... authority named by historical overlays.
• docs/product-technical-gap-baseline.md on the current serialized feat(reports): preserve grouping comparison cross-share delta for serialized successor #831 branch still opens with a 2026-09-07 statement that feat(reports): preserve grouping comparison unexplained-share delta for serialized successor #829 consumes promoted feat(reports): preserve grouping comparison axis-share delta for serialized successor #828 7b6dbbb...; live feat(reports): preserve grouping comparison axis-share delta for serialized successor #828 authority is now ac386f981317144a98a0878ca0f13c7731f7cacc, so that opening authority statement is stale even though the historical evidence should be preserved rather than rewritten away.
• bounded browser/runtime repair fix(e2e): make authenticated browser stack reproducible #1010 exact b013b8b7bc717c543b0d2ca8458c60dcc1f2144e completed hosted Tests 34612342413 SUCCESS and was normally merged into feat(reports): preserve grouping comparison cross-share delta for serialized successor #831, producing exact feat(reports): preserve grouping comparison cross-share delta for serialized successor #831 93e1b4fb5601b5733e9a4b0f7b4a9f63ff44354e.
• fresh feat(reports): preserve grouping comparison cross-share delta for serialized successor #831 Tests 34614827175 on that moved head has terminal GREEN frontend/browser acceptance, including authenticated startup, seed, persisted fixture and desktop/responsive/Pixel-7 interaction/accessibility checks; its PostgreSQL full-suite lane remains in progress, so no predecessor receipt is being transferred as complete acceptance.
• feat(reports): preserve grouping comparison axis-singular delta for serialized successor #830 exact bebd77c03e5beae469f42361c20bccc80787ebb5 completed Tests 34613528007 SUCCESS and has been returned to Draft because its parent/promotion gates are still open.
• feat(reports): preserve grouping comparison unexplained-share delta for serialized successor #829 exact 23519e93f0203ebaf9666f60e5eb7e6368dd6219 currently has frontend GREEN on Tests 34614296610 while its PostgreSQL lane is still running.
• after feat(reports): preserve grouping comparison cross-share delta for serialized successor #831 moved, feat(reports): preserve unexplained-leftover comparison delta pending successor verification #832 and feat(reports): preserve grouping-comparison unexplained-leftover delta for serialized successor #833 base metadata was explicitly refreshed to exact feat(reports): preserve grouping comparison cross-share delta for serialized successor #831 93e1b4fb... without force-rewriting their historical recovery/reconstruction heads. feat(reports): preserve grouping-comparison residual delta for serialized successor #835 remains on historical feat(reports): preserve grouping-comparison unexplained-leftover delta for serialized successor #833 until its direct parent is semantically reconstructed; no valid descendant delta was closed or discarded.

Please preserve these as dated live evidence for #963's designated current-authority section rather than copying mutable PR/check state into timeless product truth. Historical overlays should remain traceable but explicitly non-current, and canonical-owner truth should continue to be referenced rather than duplicated.