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 an Exact-head loop overlay: 2026-08-29 13:20 KST that calls fc13acaa... the protected main, names the then-open #782 stack, and describes then-current auto-merge/review state. Older overlays below repeat the same mutable-current language.

Those entries are useful historical evidence, but their placement and wording make an old operational snapshot look like present product authority. The repository's hygiene test currently protects only private-post leakage for this file; it does not prevent stale snapshot authority.

This issue owns documentation convergence only. Do not rewrite historical product facts to look current, delete evidence needed for traceability, or duplicate active feature repairs such as #960. Treat concurrent gap-baseline changes as ordinary deltas to adopt.

RED → GREEN acceptance

1. RED on current protected main: a documentation-governance test identifies that the first authority-like overlay predates and names a protected-main SHA different from the repository's declared current delivery baseline.
2. Introduce one clearly named current authority section whose claims are limited to code/release facts that can be verified from the repository or a dated live evidence receipt. Do not encode mutable PR/check counts as timeless product truth.
3. Move or relabel old loop overlays as explicitly historical, dated evidence. Preserve exact SHAs, dates, findings and buyer decisions; do not silently edit history.
4. Add a regression that prevents historical snapshots from using unqualified current, still, supersedes every older queue count, or equivalent mutable-authority wording outside the designated current section unless the statement is explicitly time-scoped.
5. Keep PRD.md, TRD.md, ARCHITECTURE.md, release metadata and the baseline consistent with the same DDD/product boundaries; do not claim an immutable release merely from package metadata.
6. Reconcile active dependency/release gaps by reference rather than copying canonical-owner truth. In particular, RankWeave publication remains owned by ContextualWisdomLab/RankWeave#35; LineageWeave consumer migration is deps(rankweave): consume canonical 0.18.0 package after owner publication #962.
7. Run documentation hygiene plus exact-head product gates, resolve review findings, and integrate normally without self-approval or protection weakening.

Current evidence boundary

#961 separately repairs runtime/package version identity and explicitly does not claim v2.28.0 immutable release readiness. #960 has a bounded review repair that time-scopes mutable audit/delivery wording on its own branch; retain that valid delta when this documentation authority converges rather than creating a competing source rewrite.

[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.