docs: bind product gaps to current evidence

docs/product-technical-gap-baseline.md

@@ -1,19 +1,19 @@
 # Product & Technical Gap Baseline
 
 ## 1. Known Parsing & Frontend Display Gaps
-- **Footnote Parsing**: `post=00505695-3e61-1fd1-83c5-263f88a9e77a` fails to recognize footnotes (li/oi level errors).
-- **Table Parsing**: `post=00505695-3e61-1fd1-80c6-86bb61c8ddc5` completely fails at parsing tables.
+- **Footnote Parsing**: `post=00505695-3e61-1fd1-83c5-263f88a9e77a` fails to recognize footnotes (li/oi level errors). Partial parser coverage is in LineageWeave PR #367; production/browser evidence is still pending.
+- **Table Parsing**: `post=00505695-3e61-1fd1-80c6-86bb61c8ddc5` completely fails at parsing tables. PR #367 covers malformed HTML row boundaries and empty cells; image tables and browser rendering remain open.
 - **Indentation**: Incorrect indentation rendering in `post=00505695-7571-1fd1-83c3-d521b187ad5b` and `post=00505695-3e61-1fd1-83c0-497b3c1c455e`.
 - **Image/Table OCR**: `post=00505695-7571-1fd1-83dd-3d22a61a5734` fails text recognition for tables inside images, markdown parsing fails, and image OCR description is too shallow for Ontology & Semantics.
-- **Math/Superscripts**: `post=00505695-9612-1fe1-83a7-e30153323f25` fails to parse superscripts like m^3 properly. Needs strict Ontology grammar for math formulas.
+- **Math/Superscripts**: `post=00505695-9612-1fe1-83a7-e30153323f25` fails to parse superscripts like m^3 properly. The semantic normalization path merged through PR #344, but the named real-post browser evidence and strict Ontology grammar still require verification.
 - **Missing UI Elements**: DAG (Directed Acyclic Graph) view is currently missing from the frontend for `post=00505695-7571-1fd1-83c5-895ed333cdbc`.
 
 ## 2. LLM Extraction & Knowledge Graph Gaps
-- **Multiple Project Extraction**: (Resolved) LLM prompt updated to request key_events as objects with project_name, separating events correctly.
-- **5W1H Missing**: (Resolved) LLM prompt updated to explicitly request 5W1H evidence items in the JSON output array.
-- **R&R and Keyman Missing**: (Resolved) LLM prompt updated to explicitly instruct using actual stated names rather than collective titles.
+- **Multiple Project Extraction**: A structured `key_events.project_name` implementation exists, but separate-event behavior still requires real-post runtime evidence.
+- **5W1H Missing**: A structured 5W1H evidence-item implementation exists, but completeness and provenance still require real-post runtime evidence.
+- **R&R and Keyman Missing**: Prompt and persistence paths exist, but actual-side/other-side affiliation, requester, assignee, and provenance still require real-post runtime evidence.
 - **Entity Resolution / Searxng**: Abbreviations like "한전" and "한국전력" are not mapped properly using Searxng and KG corroboration. 
-- **Meso-level Team Mapping**: (Resolved) Checked extraction logic; `team` mapping logic is present and correct, but LLM needed better explicit instruction which is covered by R&R resolution.
+- **Meso-level Team Mapping**: `team` mapping logic is present; affiliation and same-entity resolution still require ontology-backed runtime evidence rather than prompt-only confirmation.
 - **Base64 Image Omni-modal**: Current text-only embedding fails on images. Omni-modal LLM processing is required for images to capture layout, font size, colors, and spatial meaning.
 
 ## 3. General Architecture Gaps
@@ -24,3 +24,46 @@
 - **LLM Orchestration**: Ensure ALL LLM calls route through `contextual-orchestrator` utilizing API keys (BYTEZ, NVIDIA, OPENROUTER, OPENAI) with auto model discovery and optimal reasoning effort allocation (Fugu/Conductor/TRINITY research).
 
 *This document is continuously updated by the hourly automated agent loop.*
+
+## 4. Current Checkpoint Evidence
+
+The following states are evidence-bound and must not be changed to `merged` or
+`resolved` from intent alone:
+
+- LineageWeave PR #344: semantic metric normalization merged at `497ac120`; the
+  frontend and backend focused tests passed before merge. The named real-post
+  browser result remains an explicit follow-up.
+- LineageWeave PR #367: exact head `09500b59`; focused local tests passed (104),
+  while required GitHub Checks were queued and formal approval was absent at
+  the checkpoint.
+- LineageWeave PR #366: exact head `aef31c3c`; the customer-master authorization
+  fix derives downstream Keyman and relationship scopes from surviving entity
+  rows, not observed navigation-only entities. Required Checks and approval
+  remain external gates.
+- LineageWeave PR #345: application and Valkey caller OpenTelemetry spans are
+  merged. Raw telemetry remains outside the buyer evidence payload.
+- contextual-orchestrator PR #802: exact head `b2fe47e`; request session context
+  is propagated through local batch workers. No formal approval is recorded.
+- contextual-orchestrator PR #805: structured Responses and JSON-schema
+  orchestration remains a separate open merge prerequisite.
+
+## 5. 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
+and must not copy prompts, post bodies, images, provider responses, secrets, or
+an ad-hoc `user_account + post_id` session key. W3C trace context and bounded
+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
+
+1. Complete PR #367's protected Checks and verify the named footnote/table
+   posts in the authenticated browser.
+2. Resolve image DOM-region recognition, OCR, semantic table rendering, and
+   buyer-facing caption separation through contextual-orchestrator VISION.
+3. Verify 5W1H, multi-project event separation, Keyman affiliation, and
+   customer-master ABAC against authorized real PostgreSQL data.
+4. Keep the GRC and contextual-orchestrator OTEL evidence contracts aligned
+   with the exact merged application instrumentation.