Skip to content

feat(reports): leftover-map incomplete post coverage on graphic display (v2.40.0) - #814

Draft
seonghobae wants to merge 9 commits into
feat/leftover-map-plot-item-coverage-v2390from
feat/leftover-map-plot-incomplete-v2400
Draft

feat(reports): leftover-map incomplete post coverage on graphic display (v2.40.0)#814
seonghobae wants to merge 9 commits into
feat/leftover-map-plot-item-coverage-v2390from
feat/leftover-map-plot-incomplete-v2400

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add persisted incomplete-post coverage to the leftover-map graphic (ADR 0283 / v2.40.0) without deriving dropped counts from other fields.
  • Preserve parent post/item coverage and ADR 0274–0282 semantics; UI/read-model only, no SQL or theta/score authority.

Current exact ancestry

Current parent is exact #813 44ace39111664a9b39a81e575a8dbdf06506050f. Current #814 product is bd90a974b72c649c423a7b99ee47dae1d8236b0e, promoted non-force from workflow-free tree d326c0f9e1e08d0c59c2526abcacf094e816cf09 after run 34043779954 completed GREEN. ADR0283 remains Proposed, runtime/package/frontend remain synchronized to 2.40.0, and the only inherited moved-parent delta was the rank-boundary test. Isolated convergence GREEN does not transfer hosted exact-product-head checks or approval.

Descendant authority

#815 is current at c02dffc264f70283ff7ff2d07bfe83a47bd13e10, #816 at 4d81c881469496fedeb8d9bb98cd485209df2089, #817 at aa47c96e15084d0b944558b980edef34133f8040, #818 at de3a61988768bcfddcab1dec3dfe3c60f9a89743, and #819 at f37ca315e3c48fa37bbcafe96e46c5d7dab991b7, all through verified non-force current-parent convergence. #820 is the earliest stale descendant; run 34054337875 reconstructs its valid singular-value v2.46 delta from exact #819 while repairing the observed current-parent conflicts and ADR/release state. #821 stays dependent under a distinct future ADR/release identity.

Keep Draft. Fresh exact-product-head required checks, applicable rendered browser/Storybook/a11y evidence, authenticated acceptance where applicable, and qualifying independent approval remain required. No force-push, destructive rebase, self-approval, gate weakening, synthetic status, predecessor-evidence transfer, or invented measurement values.

…ay (v2.40.0)

Caption the leftover-map graphic display with persisted leftover-map
incomplete post coverage (ADR 0283). After make seed, closest and
farthest leftover pairs sit above the member list with a plot caption
that matches leftover-map incomplete post coverage; click a post
marker or a pair button opens that post.

A missing, non-integer, or negative dropped count, or a dropped count
that contradicts usable complete-case integers, omits that leftover-map
incomplete post caption. Dropped 0 is shown when that persisted dropped
count is a non-negative integer. Do not invent dropped posts from
scored minus used, plotted marker count, leftover-map distance,
leftover-map rank, leftover-map post coverage, leftover-map item
coverage, or the count of unused axes. Never invent a leftover score
or a theta. UI-only; no new columns.
@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.

Copy link
Copy Markdown
Contributor Author

Cycle write retry 2026-08-30T20:25+09:00. Head 7729287 is stacked on #813 (feat/leftover-map-plot-item-coverage-v2390@de2a8a8b). UI-only ADR 0283 leftover-map incomplete post coverage on the graphic. Do not squash-merge onto an unprotected leftover base. Independent collaborator APPROVE required; Copilot/Devin COMMENT is not independent APPROVE. Do not self-approve.

@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: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

Copy link
Copy Markdown
Contributor Author

Cycle 2026-08-30T11:32Z write retry: leftover-map incomplete post coverage (#814 @ 7729287) stays stacked on #813 and unmerged. No independent APPROVE exists on this org (only collaborator is seonghobae). Copilot/Devin COMMENT is not independent APPROVE. Do not squash-merge this layer onto leftover-coordinates (#782). Do not self-approve. Next buyer increment this cycle is leftover-map incomplete item coverage on the graphic (ADR 0284 / v2.41.0) stacked onto this head — UI-only caption from persisted incomplete_item_count; never invent incomplete as scored−used or from criterion marker count; omit when missing/non-integer/negative or when the dropped count contradicts usable item complete-case integers; show dropped 0 when persisted. Pair-list note stays post complete-case (ADR 0168). Grouping comparison strip (ADR 0149) does not gain this caption. No new columns. Synthetic fixtures only. NVIDIA_NIM_API_KEY only.

Copy link
Copy Markdown
Contributor Author

Frontend vitest on this head: leftoverMapCoverage + leftoverMapPlotLayout + LeftoverMapPlot + LeftoverPairList + i18n — 245 passed. UI-only ADR 0283. Leave open for independent collaborator APPROVE. Copilot/Devin COMMENT is not independent APPROVE. Do not self-approve. Do not squash-merge onto #813.

Copy link
Copy Markdown
Contributor Author

Cycle 2026-08-30T11:42Z: leftover-map incomplete item coverage is now stacked as #815 (feat/leftover-map-plot-incomplete-item-v2410 @ 63092de) onto this head. #814 stays open and unmerged. No independent APPROVE. Do not squash-merge onto leftover-coordinates (#782). Do not self-approve. NVIDIA_NIM_API_KEY only. Synthetic fixtures only.

@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 stack authority shows parent #813 has advanced from de2a8a8b… to a Draft repair line and carries an intentional Vietnamese-copy RED. This v2.40 successor was still Ready on the stale parent snapshot, so it has been returned to Draft. A second valid inherited defect is present here: pyproject.toml declares v2.40.0 while runtime lineageweave.__version__ remains v2.20.0. Preserve ADR 0283, add the release-version synchronization RED, align runtime provenance to v2.40.0, and inherit the parent RED/contracts without promoting predecessor evidence.

@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 on d837883c67fa9753f4b0cbf4326d33759bdd98eb: this PR is still Draft but ADR 0283 is Decision status: Accepted. Preserve the incomplete-post coverage delta, but when #813 produces its repaired current-parent tree and #814 is reconstructed non-force, carry ADR 0283 forward as Proposed until the reconstructed exact head has qualifying acceptance evidence. Do not add a branch-local status-only fork before the parent moves.

@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 0283 is Accepted while this PR remains Draft and has no qualifying unchanged-head independent acceptance. Preserve the valid v2.40 incomplete-post coverage delta, but keep the decision Proposed until normal integration. This should be repaired as part of the current-parent reconstruction now that #813 has converged; do not close or flatten the child.

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
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