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

[seonghobae]

Product/documentation defect

Protected main@83eba56149eb802cd63642c507c324c9976ec78e still contains historical loop overlays in docs/product-technical-gap-baseline.md. They remain traceability evidence, but mutable PR/check language must stay time-scoped and never outrank live protected code, PR/Issue authority, or immutable release facts.

Current documentation lane

Draft PR #1041 remains exact d188b85ddc0219fb3ed3c9930ae13f63beed295e with exactly one changed file, docs/product-technical-gap-baseline.md, and no temporary helper workflow residue. Its embedded top overlay is timestamped 2026-09-13 15:24 KST and is now historical rather than current authority because the Customer Master lane advanced after that snapshot. #1041's live PR body now carries the newer authority rather than pretending the file itself is current.

Fresh live authority at this issue update:

• security: separate resolved customer identity from source-post tenant ownership #1052 / fix(customer-master): separate customer resolution from source ownership #1055 exact 8448a2b4e06c6ef415dd98b3eaa1f7f36669fe94 is the single Customer Master source lane and is Ready only for exact-head validation admission. RED 6f1656d48eb43fce66e22d9cf05f6ad1bc580645 added the shared-eligibility equivalence contract; current head repaired both literal hint SQL paths while preserving the literal asyncpg/SAST boundary.
• Current fix(customer-master): separate customer resolution from source ownership #1055 Security and SAST are terminal GREEN; frontend lint/test/build/Storybook is terminal GREEN; full PostgreSQL Tests remains live. Required OpenCode has failed closed pending central exact-head verdict publication, Required CodeQL currently reproduces consumer-before-producer settlement, and Strix/Noema remain live. No predecessor receipt transfers.
• test(e2e): run authenticated FastAPI contract lane in hosted CI instead of service-wide skip #1057 remains the separate hosted PostgreSQL + local Keycloak development fixture + Valkey bearer/JWKS/RBAC/ABAC topology owner after fix(customer-master): separate customer resolution from source ownership #1055 settles. Do not duplicate that fixture in fix(customer-master): separate customer resolution from source ownership #1055.
• .github#1929 / canonical source PR .github#2106 own CodeQL run-wide settlement; the current LineageWeave fix(customer-master): separate customer resolution from source ownership #1055 canary has been attached there. .github#2045 and .github#2109 own Draft admission / unchanged-head Ready materialization. LineageWeave consumes downstream proof only.
• Draft PR fix(release): synchronize protected v2.28 runtime identity #961 exact 3bdec0504a65e63f44bd49ba15de37182a1672cc remains the single package/runtime version source repair; release: reconcile package and runtime version authority before next immutable release #1056 contributes immutable release/SBOM/provenance/reproducibility/rollback acceptance instead of creating another source writer. Protected main remains package/frontend 2.28.0 versus runtime 2.20.0 until normal integration.
• fix(security): bind relationship network to process scope #1042/fix(security): fail closed mixed-visibility period-report aggregates #1054/fix(security): bind persisted chat replay to reader scope #1047/fix(db): restore canonical migration ordinal identity #1049/fix(security): upgrade Vitest past GHSA-82fw-gwwq-j7x9 #1046 remain Draft under their own live authority. security: separate Post Chat read authority from shared persistence mutation #1053 remains the separate Post Chat durable-answer/persistence owner path and must not duplicate fix(security): bind persisted chat replay to reader scope #1047 replay authorization.
• OpenTelemetry LoggingHandler and PostgreSQL transaction-warning repairs remain with observability: remove deprecated OpenTelemetry SDK LoggingHandler #1036/fix(telemetry): use supported OpenTelemetry logging handler #973 and test(postgres): align person projection migration fixture with explicit transaction ownership #1038/fix(test): isolate projection migrations from seed transaction #1040; do not suppress or duplicate them.

Keep this issue open until #1041 or a verified successor carrying every valid documentation/evidence delta is normally integrated. Before merge require a current top overlay on one unchanged exact head, no helper residue, fresh applicable documentation/repository/security evidence, and qualifying independent review. Re-read protected main and every cited live owner immediately before promotion; if any head/base/status moves, normally converge the documentation rather than presenting a historical overlay as current.

No self-approval, Admin bypass, no-op churn, force push, destructive rebase, warning suppression, stale-head evidence transfer, skipped-E2E-as-GREEN claim, or permanent helper workflow.

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

[seonghobae]

docs/product-technical-gap-baseline.md has been refreshed on Draft PR #1041 exact 84de446e660dd952e4dcfaf9a73b76650c413ccb. Bounded refresh run 34726540322 completed SUCCESS and removed its own workflow; net changed path is again only the baseline document. The 08:51 KST overlay now records fresh 158 open PR / 36 open issue inventory, #1042 as the sole Ready validation admission while exact-head Strix remains live, #1054 returned Draft after full repository GREEN but missing central required workflow rematerialization (.github#2045), and the current #1047/#1046/#1049/#1052/#1053/release-metadata authorities. Keep #963/#1041 open and Draft until the documentation head itself finishes its current checks; this is an evidence refresh, not a release/promotion claim.

[seonghobae]

docs/product-technical-gap-baseline.md authority was refreshed again on #1041. Exact documentation head is now b4e98ea2f2776cee5a6f5873916f1cd38cdabb24; bounded run 34729620095 succeeded and removed its temporary script/workflow, leaving the net candidate baseline-only and Draft. The 09:46 KST top overlay records 159 open PR / 36 open issue inventory, #1042's unchanged live Strix admission, and new Customer Master ownership repair #1055 / issue #1052 (migration 0250 + Proposed ADR 0374, scoped capture with DB resource released before external verification, exact-source FOR SHARE revalidation, normalized association/read-model consumption, live PostgreSQL cross-tenant regression). It also records #1055's unchanged-head central-workflow materialization defect under canonical .github#2045 and keeps the protected-main release metadata mismatch as a blocker. Older overlays remain historical evidence only.

[seonghobae]

Gap baseline refresh completed on #1041 at exact c4550d20793509b4c98e98850221dab4ab5caa47. The top overlay is now 2026-09-13 10:14 KST and the PR remains Draft with one net changed path, docs/product-technical-gap-baseline.md; the bounded helper script/workflow self-removed. The overlay records #1042/#1055 as validation admissions, #1055 exact e11ff8698f20afc4ac628a6a86611ad1348c3fcb including review repairs and .github#2045 Ready-reconciliation canary, plus the protected-main 2.28.0 vs lineageweave.__version__ 2.20.0 release blocker. Older overlays are dated evidence only.

[seonghobae]

Current documentation authority correction: #977 advanced from b041ab7d... to test-only exact head 55d69ebbf2c8b31a9544fef470cff099ecb83578 after fresh review found three inherited selectors still asserting the pre-SC-2.5.3 Open leftover ... accessible name. Because #1041's committed docs/product-technical-gap-baseline.md still records b041ab7d..., I did not misrepresent that historical overlay as current or risk a lossy partial replacement of the 1,276-line traceability file. #1041's live authority body now explicitly marks the file snapshot historical for #977 and records current head/run/canary (35284829585, .github#712 comment 5722361921). A lossless baseline-source refresh remains required before #1041 can claim code-current documentation.

[seonghobae]

docs/product-technical-gap-baseline.md source is current again on #1041 exact edb946265e53c9e8943499771d9acbaddc4f01a7.

The previous full mutable baseline blob 1ddafda7b31ad42800dcb8c980d1e0a6237bc7dd was preserved byte-for-byte at docs/evidence/product-technical-gap-baseline-history-through-20260918.md before the current overlay was replaced. The live overlay now records #977 exact 5a8deac88b4b8f8a25466b57b234f9e63b4d39c9, fresh Tests 35288624582, canonical .github/main@64aa08d7..., and current #929/#932/#974/#983/#1115 owner boundaries. No historical RED/fix/fixture/contract/evidence was discarded.

#1041 remains Draft: exact-head Tests 35288851461 is skipped under Draft admission; Security 35288851479, SAST 35288851442, and CodeQL 35288851412 are queued. This closes the stale-baseline-source gap only; it is not product or docs acceptance.

[seonghobae]

Current overlay source is refreshed again at #1041 exact 93a6cb24a3645011650f642b701543a53b33231a. It now records #977 exact d08cb70f... and the newly executable Playwright/Chromium Storybook acceptance lane, plus the existing #961/#925 immutable-release owner path and the fresh fact that repository GitHub Release/tag inventories are empty. Historical evidence remains in the dated archive; no prior RED/fix/fixture/contract/evidence was deleted. #1041 remains Draft; current docs-head Tests 35293253585 is skipped by Draft admission and Security/SAST/CodeQL are nonterminal, so this is documentation currentness only, not acceptance.