Pinky UUU: the three honestities — pace, chip, reset clock (v1.78.0) #109
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/pinky-uuu-honest"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The three honestities round (owner findings #14/#15 + the quota-math calibration).
U1 - the honest pace: every pace projection derives from a RECENT ROLLING burn window (QUOTA_PACE_WINDOW_MIN, default 30 min) instead of the quota window's own average - idle/parked hours no longer dilute a full-speed fleet (the owner's 3.29 h vs calibrated 1.5-2 h). The real windows slope monitor-API usedPct samples (one per 5-min fetch, in-memory ring, reset-drop restart); the manual model scans model_usage. Every surface SELF-LABELS its math ("at pace (30 min)" / "window avg"), BOTH views on a >33% divergence. The calibration rig pins old 3.29 h vs pace 1.65 h.
U2 - the honest chip (finding #14): 'running' renders ONLY on genuinely running rows - honest_turn_status server-side (the interactive-renamed path's stale turn row no longer passes through onto dimmed rows), honestStatus on every client surface (badge, modal/drawer dots, dock).
U3 - the honest reset clock (finding #15): window-scale-aware wording - HH:MM only for same-local-day moments; a later day carries the weekday; six-plus days the date; humanized delta in tooltips; the throttle notice follows. A 7d reset NEVER renders a bare clock implying same-day.
U4 - the TTT F-1 fold: the census O-slash promise holds through the terminal state - a cancelled row keeps its master-kill breadcrumb (calm skull chip, no hammer).
Gates: fresh canonical suite green (1223 tests), Super-Linter green (six lanes), calibration rig green.