Skip to content

feat(reports): leftover-map incomplete item coverage on pair list (v2.44.0) - #818

Draft
seonghobae wants to merge 4 commits into
feat/leftover-map-list-incomplete-post-v2430from
feat/leftover-map-list-incomplete-item-v2440
Draft

feat(reports): leftover-map incomplete item coverage on pair list (v2.44.0)#818
seonghobae wants to merge 4 commits into
feat/leftover-map-list-incomplete-post-v2430from
feat/leftover-map-list-incomplete-item-v2440

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Summary

Caption the leftover pair list with persisted leftover-map incomplete-item coverage (ADR 0287 / v2.44.0). Missing, non-integer, negative, or complete-case-inconsistent dropped-item counts omit only that note; persisted dropped 0 remains visible. Do not derive dropped items from scored-used, marker counts, distance, rank, other coverage values, or unused axes. UI/read-model only; no SQL, theta/score authority, or persisted vector-derived score.

Valid local reconstruction evidence

The v2.44 reconstruction replayed only valid product delta aa3208959950637b52001457e7d4dfc1ef1764eb, reproduced release/governance REDs, changed only runtime to 2.44.0 and ADR0287 to Proposed, verified inherited contracts, and promoted workflow-free product bc971a402ef9faecb2f0b4ffd743092f4779d76b. This remains valid local repair evidence; predecessor checks/approval are not transferable.

Verified current-parent convergence

#817 is current at exact aa47c96e15084d0b944558b980edef34133f8040. Run 34053512204, job 101541202170, completed GREEN on exact prior #818 plus exact #817. It admitted only frontend/src/leftoverMapPlotLayout.test.ts, passed rank-boundary, frozen Python, ADR0287/package-version, layout/small-canvas/Vietnamese/coverage/i18n/LeftoverMapPlot/LeftoverPairList and oxlint contracts, and produced workflow-free tree 7d6ac8291e79f42f54de67a01c3bb0460741b6a8. That tree was recreated as product de3a61988768bcfddcab1dec3dfe3c60f9a89743 with first parent prior #818 and second parent exact #817, then advanced with force=false.

Isolated convergence GREEN proves the current-parent tree only; it does not transfer hosted exact-product-head checks or approval.

Descendant boundary

#819 has now converged non-force onto this exact #818 and is current at f37ca315e3c48fa37bbcafe96e46c5d7dab991b7. #820 is the earliest stale descendant. Its exact-current-parent reconstruction run 34054337875 preserves the singular-value v2.46 delta while repairing the two observed current-parent conflicts and ADR/release state. #821 remains dependent and must receive a distinct ADR/release identity after #820 converges. Do not replay historical convergence wholesale or transfer predecessor evidence.

Keep Draft. Fresh exact-product-head required checks, applicable Storybook/browser/a11y evidence, authenticated acceptance where applicable, and qualifying independent approval remain required. No self-approval, protection bypass, force-push, destructive rebase, or invented measurement values.

Jeon, M., Jin, I. H., Schweinberger, M., & Baugh, S. (2021). Mapping unobserved item–respondent interactions: A latent space item response model with interaction map. Psychometrika, 86(2), 378–403.

Gabriel, K. R. (1971). The biplot graphic display of matrices with application to principal component analysis. Biometrika, 58(3), 453–467.

….44.0)

Caption the leftover pair list with persisted leftover-map incomplete item
coverage (ADR 0287). Dropped 0 is shown. Do not invent dropped criteria from
scored minus used or plotted criterion markers. UI-only; no SQL; no new
columns. Never invent a leftover score. Never invent a theta.
@coderabbitai

coderabbitai Bot commented Aug 30, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Devin Review found 2 potential issues.

Devin Review

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📝 Info: Persisted count remains authoritative

leftoverMapIncompleteItemCount rejects contradictory usable coverage but never derives a replacement. Invalid companion counts leave a valid persisted dropped count intact.

(Refers to this code)

Devin Review

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

Comment thread frontend/src/App.tsx
Comment on lines +3877 to +3881
{incompleteItemCount !== null ? (
<p className="post-meta" role="note" aria-label={t(LEFTOVER_MAP_LIST_INCOMPLETE_ITEM_LABEL)}>
{tf(LEFTOVER_MAP_PLOT_INCOMPLETE_ITEM, incompleteItemCount)}
</p>
) : null}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📝 Info: List and plot labels stay distinct

The pair list uses its new accessible label while sharing the translated count message. The plot retains its separate label.

Devin Review

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

Copy link
Copy Markdown
Contributor Author

Cycle retry 2026-08-30T13:48Z: write path works. Independent APPROVE still required on exact head aa320895. No self-approve. Do not squash-merge onto the leftover base.

Copy link
Copy Markdown
Contributor Author

Stacked leftover-map pair-list post complete-case fail-close (ADR 0288 / v2.45.0) is #819 @ a2c9655 on feat/leftover-map-list-post-coverage-helper-v2450. Pair-list post coverage now goes through leftoverMapCoverageCounts so used-greater-than-scored, negative, or non-integer counts omit that note. Independent exact-head APPROVE still required on this PR and on #819. Do not self-approve. Do not squash-merge onto this leftover base.

Copy link
Copy Markdown
Contributor Author

Cycle retry 2026-08-30T13:55Z: GitHub writes work (comment/close/create-PR/push). Independent APPROVE still required on exact head aa320895. No self-approve. Do not squash-merge onto the leftover base. Token still empty X-OAuth-Scopes; repo permission is ADMIN. Next buyer increment this cycle is leftover-map complete-case coverage on the pair list as a distinct list note from the graphic (or grouping-strip leftover-map captions if post coverage is already distinct).

Copy link
Copy Markdown
Contributor Author

Write-retry this cycle (seonghobae MCP). #818 remains stacked leftover-map v2.44 incomplete-item pair-list coverage at aa320895. Do not squash-merge onto an unprotected leftover base. Do not self-approve. Independent APPROVE still required.

Parallel cycle already shipped feat/leftover-map-list-post-coverage-helper-v2450 @ a2c96551 (fail-close pair-list post coverage as v2.45 / ADR 0288). This cycle will stack leftover-map graphic axis singular values (σ_k) as v2.46 on that head if the PR lands onto current leftover-map tip, else on #818, without mixing into #74/#92 and without merging #808.

@seonghobae seonghobae left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Parent-first finding: this Ready PR depends on #817, which is already Draft on the unmerged leftover-map chain. Preserve the incomplete-item pair-list delta; return #818 to Draft until its prerequisites converge normally.

Preserve the #818 ADR 0287/product delta while inheriting the repaired #817 ancestry through a normal two-parent merge. No force-push or destructive rebase.
seonghobae added a commit that referenced this pull request Sep 5, 2026
Preserve #819 ADR 0288/product delta while inheriting current #818 ancestry through a normal two-parent merge. No force-push or destructive rebase.

@seonghobae seonghobae left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Current-head governance finding: ADR 0287 is Accepted while #818 remains Draft without qualifying unchanged-head independent acceptance. Keep the v2.44 incomplete-item pair-list delta, but when repaired #817 ancestry reaches this child, add an executable governance regression and set ADR 0287 to Proposed on the reconstructed candidate. This is a repair finding, not grounds to close or bypass the dependent PR.

@seonghobae seonghobae left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fresh descendant review adds one release-provenance blocker to the existing ADR0287 Draft-governance finding. This v2.44 child declares package version 2.44.0 while the historical runtime still reports lineageweave.__version__ = "2.41.0". Do not defer that drift farther down the stack. After #817 is cleanly promoted, reconstruct #818 non-force from the new exact parent, preserve only its valid incomplete-item pair-list product delta, require the existing release-synchronization contract to reproduce a RED, then apply the minimal runtime 2.44.0 correction together with ADR0287 Proposed. The old Vietnamese-source-blocker wording is stale; preserve the repaired parent authority instead of recreating it here.

seonghobae added a commit that referenced this pull request Sep 6, 2026
github-actions Bot added a commit that referenced this pull request Sep 6, 2026
seonghobae added a commit that referenced this pull request Sep 6, 2026
seonghobae added a commit that referenced this pull request Sep 6, 2026
github-actions Bot added a commit that referenced this pull request Sep 6, 2026
seonghobae added a commit that referenced this pull request Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant