feat(reports): leftover-map origin on leftover-map leftover-axis independently of leftover-map comparison leftover-axis leftover-map origin (v2.115.0) - #927
Conversation
…pendently of leftover-map comparison leftover-axis leftover-map origin (v2.115.0)
Caption leftover-map leftover-axis leftover-map origin through leftoverMapAxisOriginBadge (ADR 0358). Distinct accessible name leftover axis leftover-map origin {origin}. Rank-0 unused axes still name leftover-map origin (0.00, 0.00). leftoverMapListOriginBadge 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.
|
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 |
|
Opened Draft stacked on #926 exact head |
|
Descendant Draft #928 ( |
Summary
Stacked on #926 exact head
ede308929b20f24a56c5ff3ae2211dd84d20f3ae.leftoverMapAxisOriginBadge(ADR 0358 / v2.115.0) names leftover-map leftover-axis leftover-map origin independently of leftover-map comparison leftover-axis leftover-map origin, leftover-map comparison graphic leftover-map origin, leftover-map graphic leftover-map origin, leftover-map comparison leftover-pair leftover-map criterion leftover-map origin leftover-map item coordinates, leftover-map axis origin ticks, leftover-map axis share, and leftover-map singular values.Current repair state
leftover axis leftover-map origin {origin}when leftover-map leftover-axis surface exists (leftover_map_axeslength > 0 OR leftover-axis ticks fromlayoutLeftoverMapPlot) and the origin badge is usable; rank-0 remains(0.00, 0.00).ζ, leftover-map axis share, or leftover-map singular valuesσ_k.Exact live merge boundary
#926@ede308929b20f24a56c5ff3ae2211dd84d20f3ae34595e41ee65b89a468efeebf64fee86eff881d9Keep Draft until #922-compatible i18n/accessibility evidence, exact-head terminal checks, and qualifying independent review exist. No self-approval, force-push, destructive rebase, bypass, or gate weakening. Do not squash-merge without independent APPROVE + exact-head required success.