feat: name leftover criterion on a matching calendar commitment (v0.89.0)

[seonghobae]

Buyer impact

After make seed, leftover calendar commitments read Closest leftover · sales-lead next to the due date. Click still opens that post. A commitment that is not a leftover pair stays unmarked. An empty calendar stays No upcoming commitments.

Leftover buttons above the member list stay (ADR 0018). This slice only labels the already-visible calendar commitment so a buyer who starts from Calendar still sees the leftover criterion.

Scope

• Authorized leftover_pairs already on the period-report payload mark matching calendar commitments (ADR 0030).
• Accessible name includes the leftover caption.
• Due date stays on the commitment. Do not invent leftover numbers. Do not invent a fused score or a theta.
• A report fetch error clears leftover badges and leaves the due list intact — never an invented pair.

Exact head

c790e3ef6834278469effc0089505e41af869549 on feat/name-leftover-on-calendar-v0890.

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

Frontend: 46 tests, oxlint clean.

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 of feat: name leftover criterion on an accepted Rankings hit (v0.88.0) #252 (Rankings leftover), feat: name leftover criterion on the matching report member (v0.87.0) #234 (member leftover), feat: show leftover pairs on the grouping comparison strip (v0.86.0) #233 (comparison-strip leftover), and feat: name leftover pair on the opened post and focus its evaluation row (v0.82.0) #224 (opened-post leftover copy).
• 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. Rankings leftover is #252. Member leftover is #234. Comparison-strip leftover is #233. Naming leftover on the opened post is #224.

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.

Allen, J. F. (1983). Maintaining knowledge about temporal intervals. Communications of the ACM, 26(11), 832–843.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 56 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: 956cc665-be78-4886-8fb9-13f7e839e64e

📥 Commits

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

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (10)

• AGENTS.md
• ARCHITECTURE.md
• CHANGELOG.d/0.89.0-leftover-calendar.md
• CHANGELOG.md
• docs/adr/0030-leftover-pair-on-calendar-commitment.md
• frontend/package.json
• 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]

Exact head c790e3ef6834278469effc0089505e41af869549 (v0.89.0 / ADR 0030) is ready for an independent current-head APPROVE.

Buyer contract: after make seed, leftover calendar commitments read Closest leftover · sales-lead next to the due date; click opens that post. A commitment that is not a leftover pair stays unmarked. Empty calendar stays fail-closed. Same authorized leftover_pairs already on the period-report payload. Never invent a fused score or a theta.

Do not mix into #74 or #92. Independent of #224 / #233 / #234 / #252. Owner COMMENT is not APPROVE. Do not self-approve. Do not merge from this author.