test(reports): reconstruct #878 comparison criterion-coordinate contract - #1033
Conversation
…on graphic leftover-map criterion markers independently of leftover-map post ξ markers (v2.93.0) Caption leftover-map comparison graphic leftover-map criterion markers with persisted leftover-map item coordinates through leftoverMapComparePlotCriterionBadge independently of leftover-map post ξ markers (ADR 0336). Rank-0 unused axes still name leftover-map item coordinates (0.00, 0.00). A missing or non-finite leftover-map item coordinate pair omits independently of leftover-map post ξ. Do not invent leftover-map item coordinates from leftover-map post ξ. 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 |
|
Reconstruction authority has moved non-force with its live parent. Exact head is now |
Reconstruction authority
259e2d1ad8545bda75873a15c9e1b0de13996e4f6db5cb714f58050e6a70c67618ca52fcdda3b41b617b97126a14337a4848f2b5663ada381ae693c0remains represented through the reconstruction ancestry rather than wholesale tree replaytests/test_grouping_comparison_graphic_criterion_item_coordinate_contract.pyProposedThe historical v2.93 source/docs tree is not replayed. Grouping-comparison criterion markers must consume only finite persisted item axes, preserve
(0.00, 0.00), omit invalid coordinates independently of post ξ, and use distinct comparison-graphic naming. Report criterion naming remains separate; ζ is never inferred from person axes, geometry, distance, rank, or other evidence.#1034 is based on this exact head. No ancestor validation receipt transfers. Keep Draft until the local contract is causally GREEN and fresh exact-head repository/security/browser/a11y/performance evidence plus qualifying independent approval are current. Localization remains owned by canonical #922/#929 translation-ledger boundaries.