feat: name leftover pair on the opened post and focus its evaluation row (v0.82.0)

[seonghobae]

Buyer impact

After make seed, click the closest leftover pair (or that same member). The opened post names This post sat closest to sales-lead after main effects. Read that evaluation row next. The sales-lead evaluation row is marked Closest leftover. A post that is not a leftover pair on the loaded report shows no leftover copy.

Scope

• Lift authorized leftover_pairs from the loaded period report (ADR 0026).
• A report fetch error clears leftover context — never an invented pair.
• Mark only the evaluation row whose criterion_code matches.
• Mean θ stays on the report panel. Do not invent leftover numbers. Do not invent a theta.

Exact head

4f6c8c606e1de32ccf1a5cb6dbf7e875adda1915 on feat/name-leftover-pair-on-opened-post-v0780.

Base: main @ 8c020aa (merged #220 RankWeave).

Review gate

• Do not mix into Role, responsibility, and agent ontology (v2.10.0) #74 or feat(ui): show business context on related-node chips (v0.75.0) #92.
• Independent exact-head APPROVE required before squash.
• Do not self-approve.
• Do not merge from this PR author.
• Owner/self COMMENT is not APPROVE.

Not in this slice

Leftover persist+list landed as #211. RankWeave landed as #220. TEPP is #214. naruon mailbox is #217. ThreadWeave conversations are #219. Keyverse identity is #221.

References

Jeon, M., Jin, I. H., Schweinberger, M., & Baugh, S. (2021). Mapping unobserved item–respondent interactions: A latent space item response model with interaction map. Psychometrika, 86(2), 378–403.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[seonghobae]

Exact head 4f6c8c6 is waiting on independent current-head APPROVE plus green exact-head required checks. This COMMENT is not APPROVE and is not a merge. Do not self-approve. Do not invent leftover numbers.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 8 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a367f6f8-c544-4fd2-99ff-81e92dc2c122

📥 Commits

Reviewing files that changed from the base of the PR and between 8c020aa and 0153d63.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (13)

• AGENTS.md
• ARCHITECTURE.md
• CHANGELOG.d/0.78.0-leftover-open-context.md
• CHANGELOG.d/0.82.0-focus-leftover-eval-row.md
• CHANGELOG.md
• docs/adr/0026-leftover-pair-open-context.md
• docs/adr/0027-focus-leftover-evaluation-row.md
• frontend/package.json
• frontend/src/App.css
• frontend/src/App.test.tsx
• frontend/src/App.tsx
• lineageweave/__init__.py
• pyproject.toml

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Cycle 2026-08-17T19:13 KST: exact head 4f6c8c6 has no independent review request today. GitHub OAuth scopes on this agent remain empty (X-OAuth-Scopes blank); git push and GraphQL review-request still fail closed. This COMMENT is owner/self and is not APPROVE. Do not squash-merge without an independent exact-head APPROVE. Do not mix into #74 or #92.

[seonghobae]

#225 (focus leftover evaluation row, ADR 0027) squash-merged into this branch, not main. Head is now 0153d63 (v0.82.0). After seed, opening Closest leftover names the leftover criterion and moves keyboard focus onto that IRT row.

Independent exact-head APPROVE still required before squash to main. Do not mix into #74 or #92.

[seonghobae]

Cycle retry 2026-08-17: write-path probe. Independent exact-head APPROVE still required. Do not self-approve.

[seonghobae]

Cycle 2026-08-17T20:10 KST: exact head 0153d63 (v0.82.0). Tests/SAST/Strix/OSV/Trivy/Scorecard green on this head. Independent exact-head APPROVE still required before squash. This COMMENT is owner/self and is not APPROVE. Do not self-approve. Do not mix into #74 or #92. Do not invent leftover numbers or a theta.

[seonghobae]

Cycle 2026-08-17T22:00 KST: GitHub writes work again. #96 is closed (weaker duplicate of merged #91). This leftover-open-context head (0153d63) still has no qualifying independent exact-head APPROVE.

Owner/self COMMENT is not APPROVE. Do not self-approve. Do not squash-merge without independent APPROVE plus exact-head required success. Copilot review requested on this head. Do not mix into #74 or #92.