Skip to content

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) - #877

Draft
seonghobae wants to merge 4 commits into
feat/leftover-map-axis-tick-share-badge-v2910from
feat/leftover-map-compare-plot-tick-origin-badge-v2920
Draft

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)#877
seonghobae wants to merge 4 commits into
feat/leftover-map-axis-tick-share-badge-v2910from
feat/leftover-map-compare-plot-tick-origin-badge-v2920

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Current exact authority

Comparison-graphic origin ticks preserve distinct empty/share-only/σ-only/combined accessible-name states. Origin is the canonical formatted zero tick; share and σ remain independent, rank-0 zero evidence stays explicit, and no evidence is inferred from another.

Keep Draft until inherited/local REDs and fresh exact-head repository/security/browser/a11y/performance evidence plus independent approval are GREEN.

… leftover-map axis ticks (v2.92.0)

Caption leftover-map comparison graphic leftover-map axis origin ticks through leftoverMapComparePlotTickAxisBadge independently of leftover-map axis share and leftover-map singular values (ADR 0335). Origin 0.00 stays leftover map comparison graphic leftover-map axis {k} origin tick {value} so buyers can tell the rank-0 unused-axis location from leftover-map coordinate ticks. Share and σ omit independently. Do not invent leftover-map origin from share or σ. UI-only; no SQL; no leftover-map inner product, cosine, or length.
@coderabbitai

coderabbitai Bot commented Aug 31, 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

Leave this PR open for independent APPROVE. Do not squash-merge onto the unprotected leftover base. Do not self-approve. Devin/Copilot COMMENT is not APPROVE.

Stacked onto leftover-axis tick leftover-map axis share (feat/leftover-map-axis-tick-share-badge-v2910 / #875 @ d19f1fd). After independent review, retarget leftover-map stack onto leftover-coordinates (feat/leftover-map-coordinates-v2240 / #782) rather than squash-merging here. Issues #79 and #87 stay open. Do not merge #808 without independent APPROVE.

Cycle 2026-08-31 16:22 KST: GitHub writes work as seonghobae. #96 already closed (duplicate of #91). #875 left open (Devin COMMENTED, not APPROVE). This increment is leftover-map origin on leftover-map comparison graphic leftover-map axis ticks (ADR 0335 / v2.92.0). oxlint + tsc -b + vitest leftover-map + App + i18n 737 passed. Never invent leftover/theta. Do not persist leftover-map inner product, cosine, or length.

@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 1 potential issue.

Devin Review

Comment thread frontend/src/leftoverMapPlotAxisSingular.ts Outdated
This was referenced Aug 31, 2026
seonghobae added a commit that referenced this pull request Sep 3, 2026
…r-axis independently of leftover-map comparison graphic leftover-map origin (v2.114.0)

Caption leftover-map comparison leftover-axis leftover-map origin through leftoverMapCompareAxisOriginBadge (ADR 0357). Distinct accessible name leftover map comparison leftover axis leftover-map origin {origin}. Rank-0 unused axes still name leftover-map origin (0.00, 0.00). leftoverMapAxisOriginBadge stays unnamed. No SQL. Do not invent leftover-map origin from ζ, leftover-map axis share, or σ_k. Do not mix #877. Do not mix #890.
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.
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