Skip to content

docs: refresh exact open PR evidence #378

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
seonghobae merged 4 commits into from
Aug 21, 2026
Merged

docs: refresh exact open PR evidence #378

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
af3ecea
docs: refresh exact open PR evidence
seonghobae Aug 21, 2026
5053028
docs: record buyer-surface verification evidence
seonghobae Aug 21, 2026
45e3f47
docs: pin baseline update head
seonghobae Aug 21, 2026
333c705
docs: refresh merged PR evidence
seonghobae Aug 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
108 changes: 97 additions & 11 deletions docs/product-technical-gap-baseline.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -35,22 +35,80 @@
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-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`
`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 #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`
`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`
`9f8f4b742759e15ad34c7ef09c401dbc8b1d1ae5`, base
`8bed77e7e7b91b633bb92d3a82d0187c387206af`; its runtime boundary fixes are
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: `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
Comment on lines +84 to +86

@devin-ai-integration devin-ai-integration Bot Aug 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 PR #380 merge hash duplicates PR #370 head

PR #380's merge_commit hash 9f8f4b742759e15ad34c7ef09c401dbc8b1d1ae5 is identical to PR #370's open head hash (product-technical-gap-baseline.md). A merge commit and an open PR head are distinct commits, so this evidence hash is wrong.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

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
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
Expand All @@ -64,7 +122,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
Expand All @@ -74,10 +158,12 @@ 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. 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.
Expand Down
Loading