feat(reports): leftover-map axis share on leftover-axis ticks independently of leftover-map singular values (v2.91.0) - #875
Conversation
…dently of leftover-map singular values (v2.91.0) Caption leftover-axis ticks with persisted leftover-map axis share through leftoverMapAxisTickBadge independently of leftover-map singular values (ADR 0334). Share and singular omit independently. Rank-0 unused axes still name leftover-map axis share 0%. Do not invent leftover-map axis share from σ_k. Do not invent σ_k from leftover-map axis share. UI-only; no SQL; never invent a leftover score or a theta.
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Leave #875 open for independent APPROVE. Do not squash-merge. Do not self-approve. Stacked onto leftover-map comparison leftover-axis tick leftover-map axis share ( |
|
Retry GitHub writes this cycle. Leave #875 open for independent APPROVE. Devin Review COMMENTED (trailing blank line in leftoverMapPlotAxisSingular.test.ts) is not APPROVE. Copilot/Devin COMMENT is not independent APPROVE. Do not squash-merge. Do not self-approve. Stacked onto leftover-map comparison leftover-axis tick leftover-map axis share ( |
|
Cycle 2026-08-31 15:53 KST: leftover-axis ticks leftover-map axis share independently of leftover-map singular values (ADR 0334 / v2.91.0) is this PR at 8fa6042, stacked onto leftover-map comparison leftover-axis tick leftover-map axis share (#874 @ ba58c21). Local parallel 423ca26 is the same increment; do not overwrite this head. Frontend oxlint 0, tsc -b, leftover-map + App + i18n green. Devin/CodeRabbit COMMENT is not independent APPROVE. Leave open for independent APPROVE. Do not self-approve. Do not squash-merge onto the unprotected leftover base. After independent review, retarget leftover-map stack onto leftover-coordinates ( |
…tover-axis tick share tests git diff --check reported a new blank line at EOF in leftoverMapPlotAxisSingular.test.ts on leftover-map comparison leftover-axis tick leftover-map axis share distinctness. Keep a single terminating newline. No leftover-map caption change.
|
Cycle 2026-08-31 15:56 KST: pushed d19f1fd on this branch to drop the trailing blank line Devin flagged in leftoverMapPlotAxisSingular.test.ts ( |
|
Leave open for independent APPROVE. Do not squash-merge. Do not self-approve. Devin COMMENTED is not APPROVE. Stacked leftover-map increment: leftover-axis ticks leftover-map axis share independently of leftover-map singular values (v2.91.0 / ADR 0334). Next leftover-map increment stacks onto this head. Issues #79 and #87 stay open. Do not merge #808 without independent APPROVE. |
|
Retry GitHub writes this cycle (2026-08-31 15:45 KST). Leave #875 open for independent APPROVE on exact head |
|
Retry GitHub writes this cycle (2026-08-31 16:25 KST). Leave #875 open for independent APPROVE on exact head |
|
Leave #875 open for independent APPROVE. Do not squash-merge. Do not self-approve. Devin COMMENT is not APPROVE. Next leftover-map increment stacked onto this head ( |
Adopt exact reconstructed #874 as the repaired tree while preserving historical #875 as first parent. Retain v2.91 intent as an executable RED only: report leftover-axis ticks must expose persisted axis share independently of singular evidence, preserve finite zero, omit invalid evidence, and never infer share from singular values. No force update or stale source replay.
Adopt exact reconstructed #875 as the repaired tree while preserving historical #876 as first parent. Retain v2.92 criterion-marker intent as one executable RED: report graphic criterion markers must name persisted ζ item coordinates through the canonical coordinate formatter, fail closed on incomplete/non-finite pairs, preserve zero, and never infer item coordinates from post ξ. No force update or stale source replay.
Adopt exact reconstructed #875 as the repaired tree while preserving historical #877 as first parent. Retain v2.92 origin-tick intent as one executable RED: comparison-graphic origin ticks must use distinct four-state copy, identify only the canonical formatted zero tick, and never derive origin identity from share or singular evidence. No force update or stale source replay.
Current exact authority — 2026-09-21
abb9d2c2ef1ba7bccdf1a470272096225b34249166eab13b10d7e99f74503be3c77aef727c0a8df4473d5f20d69584db3eaa7e129f7a8650ecd472bb, feat(reports): leftover-map origin on leftover-map comparison graphic leftover-map axis ticks independently of leftover-map axis share and leftover-map singular values (v2.92.0) #877f294cc404a43ed011bba9b1291afad910838a669Ordinary/non-force convergence overlays the four report-axis tick share/singular deltas on repaired #874 ancestry. No predecessor receipt transfers.