Stabilize upload stress coverage - #88
Merged
Merged
Conversation
Add atomic reindex generation safeguards, RAG answer cleanup, application/mockup route updates, verification tooling, and focused browser stability fixes.
Refine WA health site and program mappings used by document organization.
Use the shared document organization profile helper for document drawer filters.
Stabilize local project identity mocking in UI smoke tests and broaden generated document classification labels.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…etry-main # Conflicts: # src/components/clinical-dashboard/document-search-results.tsx # tests/indexing-v3-agent.test.ts # tests/worker-visual-capture.test.ts
…etry-main # Conflicts: # tests/ui-stress.spec.ts
BigSimmo
pushed a commit
that referenced
this pull request
Jul 29, 2026
`Static PR checks` went red on f6a13cd: the branch-review-ledger guard found 2 exact duplicate records at lines 1276/1277, repeating the ref/HEAD/scope of lines 1272/1273. This is ledger #88's exact watch condition. `docs/branch-review-ledger.md` carries `merge=union` in .gitattributes so concurrent appends survive, but a same-hunk merge can keep both the incoming and existing copy. Repeated origin/main syncs on this PR duplicated two PR #1383 babysit records from claude/test-coverage-analysis-2vcd8a. Verified both pairs byte-identical (664 and 352 chars) before touching anything, then removed only the later copies. The ledger contract allows removing exact duplicates and forbids rewriting surrounding records, so the diff is 2 deletions and 0 additions. check:branch-review-ledger now passes: 1231 table records, union merge active, six cells each, no conflict markers, mojibake, heading records, or duplicates. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01361jh3eYVjJCzXWjAhdZiF
BigSimmo
pushed a commit
that referenced
this pull request
Jul 29, 2026
Merge 9f7a629 brought origin/main into this branch, and merge=union kept both copies of four records this branch already carried from an earlier main merge. Static PR checks went red on the ledger guard: - 4 exact duplicate review record(s) found at line(s) 1277, 1279, 1280, 1281. - 4 record(s) repeat the same ref/HEAD/scope (line pairs 1270 and 1277; 1275 and 1279; 1272 and 1280; 1273 and 1281). This is the #88 watch condition exactly. All four pairs are byte-identical, so only the later copies are removed -- the one mutation the append-only contract permits. No record is edited and none is lost: 4 deletions, 0 additions, and the unique-row sets before and after are identical. The rows belong to three other branches (clinical-design-system-update-e34ca9, test-coverage-analysis-2vcd8a, document-reader-condensed-view), not to this one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01361jh3eYVjJCzXWjAhdZiF
BigSimmo
pushed a commit
that referenced
this pull request
Jul 29, 2026
Resolved docs/outstanding-issues.md by keeping this branch's updated #98, #102, #104 and #105 entries (the ones this PR rewrites) and adding main's new #108 and #109 rows; the rest of the conflict was prettier re-padding column widths after a summary-cell length change. next-id stays at 110. Removed four exact-duplicate branch-review-ledger rows produced by the union merge driver keeping both copies of rows present on this branch and on main - the duplication risk tracked as #88.
BigSimmo
pushed a commit
that referenced
this pull request
Jul 29, 2026
The merge=union driver keeps both copies of rows present on this branch and on main; the guard flags them as duplicate ref/HEAD/scope records (#88).
BigSimmo
pushed a commit
that referenced
this pull request
Jul 29, 2026
Dropped two union-merge duplicate ledger rows (#88).
BigSimmo
pushed a commit
that referenced
this pull request
Jul 30, 2026
The 9df21db main sync re-duplicated the claude/white-element-positioning-t607pk pr-babysit row (lines 1329/1335, byte-for-byte identical), failing check:branch-review-ledger and with it Static PR checks and the PR required aggregate. This is ledger #88 recurring on every main sync: merge=union keeps both sides of a row that both branches appended. Removing an exact duplicate is the one mutation the append-only contract permits. Verified identical with diff before deleting the later copy. check:branch-review-ledger: 1296 table records, no duplicates. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01361jh3eYVjJCzXWjAhdZiF
BigSimmo
added a commit
that referenced
this pull request
Jul 30, 2026
* fix: ledger merge driver dedupes exact rows on sync Replace stock merge=union with a custom ledger driver that unions concurrent appends and drops byte-identical twins, add ledger:dedupe for checkouts without the driver, tighten Run PR babysit append policy, and close #88 now that the residual exact-dupe class is gated. * feat: rotate branch-review ledger into quarterly archives (L4) Add ledger:rotate to move older dated rows into docs/archive/branch-review-ledger-<yyyy-qN>.md, teach lookup/sweep/check to read the archive corpus, bootstrap by archiving pre-2026-07-29 rows, and mark maturity backlog L4 done. Also fix the CLI entry guard so check-branch-review-ledger no longer falsely matches as the ledger CLI. * fix: harden ledger CLI entry guards against suffix false-match check-branch-review-ledger.mjs ends with branch-review-ledger.mjs, so a bare endsWith guard can execute the wrong CLI when modules import each other. Match on a path segment instead. * fix: add JSDoc types for ledger rotate helpers TypeScript inferred calendarQuarterStart(value = new Date()) as Date-only and dropped `before` from rotateLedgerMarkdown's options object, which failed Static PR typecheck on the hygiene tests. * issues: drop L4 from #86 Remaining; capture #126 quarterly rotate L4 shipped in #1418. Track a quarterly ledger:rotate reminder so the live table does not grow unbounded again. * docs: mark L4 DONE and clarify ledger merge/rotate residual risks Progress summary table still said OPEN after L4 shipped. Document exact-only dedupe, install-required merge driver, and quarterly rotate practice. --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
BigSimmo
pushed a commit
that referenced
this pull request
Jul 30, 2026
main's #1418 (ledger merge dedupe + L4 quarterly archive rotation) and #1413 both edited docs/outstanding-issues.md, so this was a real content conflict rather than staleness: git merge-tree --write-tree confirmed CONFLICT before any resolution was attempted. Resolved by taking main's version of the ledger wholesale and re-applying this branch's five-row archive move on top, so neither side's work is lost: - from main: #88 and #97 archived, new open row #126 (quarterly ledger rotation) with queue order 35, the #23 "When" update (release-browser-matrix no longer blocked by pr-required), the #86 detail update, and the issues:next-id bump to 127. - from this branch: #95, #96, #104, #109 and #115 moved from Open items to Resolved / archive. No row from either side was dropped, and no id appears in both tables. Verified: 121 rows (52 open, 69 archived), marker next-id=127 above the highest; each of #88, #97, #95, #96, #104, #109, #115 resolves to exactly one archive row and #126 to one open row; zero conflict markers remain. npm run verify:cheap -> EXIT=0; "Gate-manifest OK: all 29 verify:cheap gates are enforced in CI"; "Test Files 431 passed (431)"; "Tests 4496 passed | 4 skipped (4500)". npx prettier --check . -> "All matched files use Prettier code style!" Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011YdPS2KhKqz2buzsUgmX3c
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Verification