feat(reports): leftover-map explained leftover share on grouping comparison graphic (v2.68.0) - #851
Conversation
…arison graphic (v2.68.0)
Caption persisted leftover-map explained leftover share e on the grouping
comparison leftover-map graphic from already-named leftover_map_explained_share
(ADR 0311). Comparison copy uses leftover map comparison graphic explained
leftover share {label} so it stays distinct from hyphen leftover-map explained
leftover share {label} and from strip Leftover map comparison explained leftover
share. A missing or non-finite e omits that caption and keeps leftover-map
reconstruction and comparison graphic coverage notes. Rank-0 origin cells still
name R̂²/R² 0.00 when that explained leftover share is finite. Do not invent e
from leftover-map reconstruction or leftover residual. Never invent a leftover
score. Never invent a theta. No new columns.
|
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 |
|
Queue retry: leftover-map explained leftover share on grouping comparison graphic (v2.68.0 / ADR 0311). Independent APPROVE required before squash-merge. Do not self-approve. Next stacked increment is leftover-map unexplained leftover share on that comparison graphic. Issues #79 and #87 stay open. #96 is already closed. |
|
Cycle retry 2026-08-31 06:40 KST: exact head Next stacked increment (ADR 0312 / v2.69.0) captions leftover-map unexplained leftover share on the grouping comparison leftover-map graphic with distinct accessible name |
| [project] | ||
| name = "lineageweave" | ||
| version = "2.67.0" | ||
| version = "2.68.0" |
There was a problem hiding this comment.
🟡 Version bump leaves frozen lock stale
The version bump declares 2.68.0, but the frozen lock still identifies lineageweave as 2.65.0. Frozen installs can fail or package the old release.
Prompt for agents
Regenerate uv.lock from the updated pyproject.toml so the local lineageweave package entry records version 2.68.0. Verify the repository's frozen CI sync and backend Docker installation succeed with the refreshed committed lock.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Cycle 2026-08-31T06:40 KST: retrying GitHub writes (close/merge/comment/push). Head 2d6e8e7 v2.68.0 leftover-map explained leftover share on grouping comparison graphic. Not self-approving. Independent APPROVE required before squash-merge. |
|
Stacked #852 leftover-map unexplained leftover share on grouping comparison graphic (v2.69.0 / ADR 0312) is open on this head. Independent APPROVE required. Do not self-approve. Do not squash-merge onto the unprotected leftover base. |
Summary
Caption persisted leftover-map explained leftover share
eon the grouping-comparison leftover-map graphic whenformatLeftoverMapExplainedSharereturns a usable badge (ADR 0311 / v2.68.0). It omits independently from reconstruction, distance, and coverage. No SQL/new columns; never deriveefrom neighbouring statistics.Live authority
#850@40a6b04c1a1fe81dbb6297aadea9158b9b64495572df615a8fb1350217039c6a62007243a6322cccParent convergence
#851 inherited the ADR-governance regression as
74e22f0bb62997fad1bb4f978b9a50addaa1d49c. GitHub generated exact current-parent merge041c6d059a347d5683df84b96deca72589add23f, verified with parents#850@40a6b04c...and#851@74e22f0b...; its tree keeps ADR 0311/v2.68.0 and ADR 0304Proposed. That tree was recorded child-first as72df615a..., and the branch moved by non-force fast-forward only.Historical
799frontend tests/oxlint/py_compile evidence predates this exact head and is not transferred. Exact-head required/frontend/browser/a11y, PostgreSQL/k6 evidence, and independent approval remain outstanding. Direct descendants must be reconstructed before predecessor evidence transfers.Product invariants
eomits only its graphic caption and preserves usable reconstruction/distance/coverage captions.Keep Draft until exact-head evidence and independent approval exist. No self-approval, gate bypass, force push, or destructive rebase.