Repository navigation
feat(quota-plane): plan-store / tracker / measured reconciliation diff (daily) #1270
Description
Part of epic #1149; extends the daily model + route audit (#1173). Priority P2. Three records describe the same plans and can drift independently: (1) the fork plan store (model-plan.ts JSON — entitlements, fees, windows), (2) the master tracker / quota-view (human-maintained plan facts), (3) the hub snapshot history (measured reality). The 2026-10-26 passes already found drift of exactly this kind (Go windows, ClinePass's stale tracker row, Meta's blocked-vs-funded status).
Feature: a daily reconciliation diff — plan-store entitlements vs tracker rows vs latest measured windows — reporting only mismatches (plan name, fee, window limit/reset, status active/cancelled) as findings in the stewardship cycle log + registry, each with the winning source named per the evidence rules (console read > plan store > tracker prose). No silent auto-fixes: corrections flow through the normal edit/PR paths with the diff attached.
Acceptance: first diff run produces a dated findings list (or an explicit no-drift result); a planted mismatch in a test fixture is caught.
Acceptance criteria
- A daily reconciliation diff runs across plan-store entitlements vs tracker rows vs latest measured windows, reporting only mismatches (plan name, fee, window limit/reset, status active/cancelled).
- Each finding names the winning source per the evidence rules (console read > plan store > tracker prose) and lands as a dated findings list in the stewardship cycle log + registry — or an explicit no-drift result.
- A planted mismatch in a test fixture is caught by the diff.
- No silent auto-fixes: corrections flow through the normal edit/PR paths with the diff attached.
Activity
developing-today commentedon Oct 27, 2026
CODE-394
dezren39 commentedon Oct 28, 2026
Intake review
Fleet-monitor intake pass (protocol §5), 2026-10-28. Filed with only
meta/follow-up; labels normalised in this pass (kind/feature,source/human— author dezren39 —status/needs-triage,priority/normalper the body's P2,effort/m).Still live: no merged or open PR references this issue (checked 2026-10-28T01:47Z); nothing has implemented it yet.
Related: part of epic #1149; extends the daily model + route audit #1173. Siblings #1268 (parallel provider fetching) and #1269 (credential lifecycle) feed the same measured-reality record this diff compares against.
Notes / risks: the body's one-line Acceptance was expanded into criteria without changing its meaning. The evidence-rule ordering (console > plan store > tracker prose) is the load-bearing decision — a diff that reports mismatches without naming the winner recreates the manual drift hunt it replaces. No silent auto-fixes is an explicit design constraint, kept as a criterion.
Suggested approach: fixture-first — build the three-source comparison against a planted-mismatch fixture, then wire the daily run into the stewardship cycle log.
dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
124 remaining items
dezren39 commentedon Nov 2, 2026
agent-note:v1
dezren39 commentedon Nov 2, 2026
agent-note:v1
event: parked
task: 4984
lane: f
summary: Ownership gate re-verified fresh 2026-11-02 (metadata only): issue #1270 still OPEN and assigned to dezren39, and no open PR matches this work. Per the prior verified checkpoint, Drew ownership is a hard stop: no plan-store/tracker data was read and no competing work was created.
resume: Explicit ownership handoff/release from Drew plus confirmation of the live plan-store path and tracker structured-facts scope; then revalidate before implementation.
dezren39 commentedon Nov 2, 2026
🤖 Agent note · escalated / blocked
held/user/owned/do-not-merge/do-not-auto-editall absent); a scan of all 33 comments found no Drew statement claiming this work — assignment to dezren39 is the shared fleet account and is not, by itself, ownership. The earlier "Drew ownership" shorthand in prior checkpoints is corrected here.user/escalated+queue/blockedtoday), and that decision explicitly asks Drew to "confirm the user-owned renewal-task destination and handoff boundary with feat(quota-plane): plan-store / tracker / measured reconciliation diff (daily) #1270, or explicitly narrow the scope." Implementing feat(quota-plane): plan-store / tracker / measured reconciliation diff (daily) #1270 before that boundary is confirmed risks exactly the overlap the feat(quota-plane): quota credential lifecycle — expiry watch, renewal surfacing, per-provider renewal paths #1269 coordination note (2026-11-01) warned about.escalated-to-user(not parked again — three 30-minute parks have already cycled on this gate). No plan-store, tracker, or source data was read and no worktree/PR was created in this pass.dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
user/escalated+queue/blocked+status/blocked: per the 2026-11-02 lane E revalidation, there is no hard-stop label and no Drew ownership claim — the real gate is a pending Drew decision shared with sibling task 4981. The claimant should re-check whether that decision has landed before implementing; if it has not, park/block rather than implement.