From af3ecead7231f1d6e795e3ff6bc5d0f0cff1709c Mon Sep 17 00:00:00 2001 From: Seongho Bae Date: Fri, 21 Aug 2026 21:43:46 +0900 Subject: [PATCH 1/4] docs: refresh exact open PR evidence --- docs/product-technical-gap-baseline.md | 55 +++++++++++++++++++++----- 1 file changed, 46 insertions(+), 9 deletions(-) diff --git a/docs/product-technical-gap-baseline.md b/docs/product-technical-gap-baseline.md index 37dc22bf0..81c35a94d 100644 --- a/docs/product-technical-gap-baseline.md +++ b/docs/product-technical-gap-baseline.md @@ -6,7 +6,7 @@ > this repository, screenshots, tests, logs, or buyer evidence. ## 1. Known Parsing & Frontend Display Gaps -- **Footnote Parsing**: synthetic case `case-footnote-01` exercises numbered footnote recognition; PR #367 adds parser coverage, while authorized production/browser evidence remains pending. +- **Footnote Parsing**: synthetic case `case-footnote-01` exercises numbered footnote recognition; PR #367 merged the parser coverage, while authorized production/browser evidence remains pending. - **Table Parsing**: synthetic case `case-table-01` exercises malformed row boundaries and empty cells; image tables and browser rendering remain open. - **Indentation**: synthetic cases `case-indent-01` and `case-indent-02` retain incorrect indentation rendering coverage gaps. - **Image/Table OCR**: synthetic case `case-image-table-01` still needs region-aware table OCR, markdown rendering, and sufficiently detailed buyer-safe image evidence. @@ -35,22 +35,57 @@ The following states are evidence-bound and must not be changed to `merged` or `resolved` from intent alone: -Observed at `2026-08-21T11:16:36Z` from the GitHub API. A merged commit is +Observed at `2026-08-21T12:42:34Z` from the GitHub API. A merged commit is identified as `merge_commit`; an open PR is identified by its exact `head`. - LineageWeave PR #344: `merge_commit` `497ac120c2ea22f97ef2e4a4bcd15fc2a3610046`, merged at `2026-08-21T10:23:02Z`; focused tests passed before merge, while the authorized-runtime browser result remains open. -- LineageWeave PR #367: `head` - `5194d267b90430d7a27a9752a49d73617cb5756c`, base - `f66991699506ef14607de5946da1efcfd20ae6da`; focused parser tests passed, - while required Checks and independent approval remain external gates. +- LineageWeave PR #367: `merge_commit` + `7a0d025215fbd9f6510727c7139885b561296149`, merged at + `2026-08-21T11:56:07Z`; focused parser tests passed before merge, while + authorized production/browser evidence remains open. +- LineageWeave PR #349: `head` + `539b65287da5ac4635f6965c6dc21d7437dede9c`, base `main`; ontology + provenance explorer remains open and required Checks and independent + approval remain external gates. +- LineageWeave PR #368: `head` + `f45fcdebfd54bf236b55f5d892aeb6091b51ba5b`, base `main`; this baseline + checkpoint is updated by the stacked documentation PR for the newer queue + evidence below. - LineageWeave PR #366: `head` - `696f8d46372ef6f5af9eb1b2dbc30fff4e9c9f6c`, base + `588dc91f5689d77281cd6bbd10a8e922f9eaa159`, base `8bed77e7e7b91b633bb92d3a82d0187c387206af`; customer-master authorization scope is implemented, while required Checks and independent approval remain external gates. +- LineageWeave PR #369: `head` + `eb9e520cbac412b7f85f8ceddd86624515bb29cb`, base + `e88f3862215e76d0702204f29aba75ddc902d19f`; ontology source-window + continuation is open and required Checks and independent approval remain + external gates. +- LineageWeave PR #370: `head` + `74b92eb95360b14c7e4f2bc2679f580f4ce249f8`, base + `8bed77e7e7b91b633bb92d3a82d0187c387206af`; its runtime boundary fixes are + stacked in PR #376. +- LineageWeave PR #374: `head` + `f6ce19f8e10aa7ec2b0a95f3adbbea816bd39594`, base + `0a5a5799b444c44dc2952edc7227b1b96b97457e`; its post-chat atomic + reauthorization fix is stacked in PR #377. +- LineageWeave PR #376: `head` + `21880e937eedff6c314cb7af3d99ddca2792597f`, base `docs/customer-master-scope-adr`; + migration, relation-boundary, image-job transaction, and overflow-test fixes + are locally verified; required Checks and independent approval remain + external gates. +- LineageWeave PR #377: `head` + `16ab01a9ab7d88487a3c984e192709857f6cfd1c`, base + `repair/global-ask-atomic-rollback-v2203`; post-chat rollback and test + cleanup are locally verified; required Checks and independent approval + remain external gates. +- LineageWeave PR #371: `closed_without_merge` + head `4c3e43f9e96ecc2d868657dd9b0ce5524a15c76c`, closed at + `2026-08-21T11:59:57Z`; no merge commit exists, so ontology publication is + not claimed as delivered by this checkpoint. - LineageWeave PR #345: `merge_commit` `9316d281ae396cc1bc33ac3ba470a9e3afd41a90`, merged at `2026-08-21T09:08:31Z`; application and Valkey caller OpenTelemetry spans @@ -76,8 +111,10 @@ GRC evidence subjects. ## 6. Next Implementation Order -1. Complete PR #367's protected Checks and verify the synthetic footnote/table - cases in the authenticated browser; use the protected external corpus only +1. Let the protected Checks and independent approvals complete for stacked PRs + #376 and #377, then revalidate their parent PRs #370 and #374 at the exact + current head; PR #367 is already merged. Verify the synthetic footnote/table + cases in the authenticated browser and use the protected external corpus only for aggregate, non-identifying runtime evidence. 2. Resolve image DOM-region recognition, OCR, semantic table rendering, and buyer-facing caption separation through contextual-orchestrator VISION. From 505302847b1a257d1464460d3c72bf11344e48ae Mon Sep 17 00:00:00 2001 From: Seongho Bae Date: Fri, 21 Aug 2026 22:06:44 +0900 Subject: [PATCH 2/4] docs: record buyer-surface verification evidence --- docs/product-technical-gap-baseline.md | 30 ++++++++++++++++++++++++-- 1 file changed, 28 insertions(+), 2 deletions(-) diff --git a/docs/product-technical-gap-baseline.md b/docs/product-technical-gap-baseline.md index 81c35a94d..9859aa070 100644 --- a/docs/product-technical-gap-baseline.md +++ b/docs/product-technical-gap-baseline.md @@ -99,7 +99,33 @@ identified as `merge_commit`; an open PR is identified by its exact `head`. `f1b0cd48271e870571b022463e1ec2c857ae4a8a`; structured Responses and JSON-schema orchestration remain a separate open merge prerequisite. -## 5. Organization OpenTelemetry Evidence Boundary +## 5. Local Buyer-Surface Verification + +Observed at `2026-08-21T13:06:25Z` in the authorized local stack using a +synthetic browser account and aggregate-only evidence: + +- The first authenticated board load exposed a migration drift: `/api/posts` + returned a server error because the runtime lacked the event evidence + column expected by the current backend. Rebuilding and running the current + migration image applied the pending migrations through `0114`; the same + board then returned HTTP 200 for settings, current-user, lineage, and post + list requests. +- The authenticated browser loaded 50 post-list entries, opened the detail + popup, and rendered Event Lineage, Knowledge Graph, original-content, and + issue sections without a frontend error. An image-heavy summary returned + the explicit processing-state response (HTTP 503), so image evidence is not + claimed as live-ready. +- The exact PR #366 frontend head passed 177 tests and a production build. + Its browser build authenticated successfully and loaded the board; the + disclosure-summary focus path remains covered by the unit test because the + local authorized corpus did not expose a disclosure element in the sampled + popup. + +These observations are runtime evidence, not a claim that the corresponding +PRs are merged. The image-processing state and protected-corpus parsing cases +remain open gaps. + +## 6. Organization OpenTelemetry Evidence Boundary GRC PR #42 records organization-level OTEL acceptance evidence through the existing purpose-bound evidence contract. It does not become a raw span store @@ -109,7 +135,7 @@ OpenTelemetry attributes correlate the authorized operation across services; collector delivery, retention, access review, and no-export rollback are the GRC evidence subjects. -## 6. Next Implementation Order +## 7. Next Implementation Order 1. Let the protected Checks and independent approvals complete for stacked PRs #376 and #377, then revalidate their parent PRs #370 and #374 at the exact From 45e3f4750a251f2d1e4ee1da1bf07e614199e0b6 Mon Sep 17 00:00:00 2001 From: Seongho Bae Date: Fri, 21 Aug 2026 22:07:14 +0900 Subject: [PATCH 3/4] docs: pin baseline update head --- docs/product-technical-gap-baseline.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/product-technical-gap-baseline.md b/docs/product-technical-gap-baseline.md index 9859aa070..4fd74dcf1 100644 --- a/docs/product-technical-gap-baseline.md +++ b/docs/product-technical-gap-baseline.md @@ -54,6 +54,10 @@ identified as `merge_commit`; an open PR is identified by its exact `head`. `f45fcdebfd54bf236b55f5d892aeb6091b51ba5b`, base `main`; this baseline checkpoint is updated by the stacked documentation PR for the newer queue evidence below. +- LineageWeave PR #378: `head` + `505302847b1a257d1464460d3c72bf11344e48ae`, base + `codex/product-gap-baseline-20260821`; this checkpoint's local + buyer-surface verification is the current documentation delta. - LineageWeave PR #366: `head` `588dc91f5689d77281cd6bbd10a8e922f9eaa159`, base `8bed77e7e7b91b633bb92d3a82d0187c387206af`; customer-master authorization From 333c705294a4faa76869f34d3e08dc09d760487d Mon Sep 17 00:00:00 2001 From: Seongho Bae Date: Fri, 21 Aug 2026 22:13:27 +0900 Subject: [PATCH 4/4] docs: refresh merged PR evidence --- docs/product-technical-gap-baseline.md | 35 ++++++++++++++++++++------ 1 file changed, 27 insertions(+), 8 deletions(-) diff --git a/docs/product-technical-gap-baseline.md b/docs/product-technical-gap-baseline.md index 4fd74dcf1..0467192d9 100644 --- a/docs/product-technical-gap-baseline.md +++ b/docs/product-technical-gap-baseline.md @@ -35,7 +35,7 @@ The following states are evidence-bound and must not be changed to `merged` or `resolved` from intent alone: -Observed at `2026-08-21T12:42:34Z` from the GitHub API. A merged commit is +Observed at `2026-08-21T13:12:54Z` from the GitHub API. A merged commit is identified as `merge_commit`; an open PR is identified by its exact `head`. - LineageWeave PR #344: `merge_commit` @@ -69,23 +69,42 @@ identified as `merge_commit`; an open PR is identified by its exact `head`. continuation is open and required Checks and independent approval remain external gates. - LineageWeave PR #370: `head` - `74b92eb95360b14c7e4f2bc2679f580f4ce249f8`, base + `9f8f4b742759e15ad34c7ef09c401dbc8b1d1ae5`, base `8bed77e7e7b91b633bb92d3a82d0187c387206af`; its runtime boundary fixes are - stacked in PR #376. + now part of the current Customer Master stack; required Checks and + independent approval remain external gates. - LineageWeave PR #374: `head` `f6ce19f8e10aa7ec2b0a95f3adbbea816bd39594`, base `0a5a5799b444c44dc2952edc7227b1b96b97457e`; its post-chat atomic reauthorization fix is stacked in PR #377. -- LineageWeave PR #376: `head` - `21880e937eedff6c314cb7af3d99ddca2792597f`, base `docs/customer-master-scope-adr`; - migration, relation-boundary, image-job transaction, and overflow-test fixes - are locally verified; required Checks and independent approval remain - external gates. +- LineageWeave PR #376: `merge_commit` + `860545f7bece99359ec7b9840c675ddc14e9acbc`, merged at + `2026-08-21T13:10:45Z`; migration, relation-boundary, image-job transaction, + and overflow-test fixes are delivered in the Customer Master stack. +- LineageWeave PR #380: `merge_commit` + `9f8f4b742759e15ad34c7ef09c401dbc8b1d1ae5`, merged at + `2026-08-21T13:11:02Z`; the workspace-refresh and accessibility changes are + delivered in the current #370 head. - LineageWeave PR #377: `head` `16ab01a9ab7d88487a3c984e192709857f6cfd1c`, base `repair/global-ask-atomic-rollback-v2203`; post-chat rollback and test cleanup are locally verified; required Checks and independent approval remain external gates. +- LineageWeave PR #373: `head` + `bc91481dac7350975de7ec00f11d4e54f676eb2c`, base `main`; ontology + publication has unresolved review work and is not treated as delivered. +- LineageWeave PR #375: `head` + `34967730b4a9e663ff366b7fd8a91c21f98236f1`, base + `repair/global-ask-atomic-rollback-v2203`; one unresolved review thread + remains, so post-chat citation authorization is not treated as delivered. +- LineageWeave PR #379: `head` + `8d688c8b865092e7e52c7ff4cabbc01dcde9c9b0`, base + `feat/naruon-calendar-projection-contract-main`; one unresolved review + thread remains and it is outside the LineageWeave buyer-surface completion + claim. +- Legacy open PRs #258, #262, and #287 remain explicitly unmerged; their + current review/conflict state requires separate triage before any delivery + claim. - LineageWeave PR #371: `closed_without_merge` head `4c3e43f9e96ecc2d868657dd9b0ce5524a15c76c`, closed at `2026-08-21T11:59:57Z`; no merge commit exists, so ontology publication is