docs(roadmap): R-36 + R-37 collapse to SHIPPED (hub v0.67.0)
R-36: both halves delivered — the enabled-but-unprovisioned warning on the customer page (reusing the same predicate the offsite re-issue handler refuses on), and the related sub-item, auto-minting the self-bind link at customer creation AND RESET completion so the console banner's promised email is already true. Records the gap found while wiring it: PurgeCustomerResetDBState does not clear selfbind_tokens, so a pre-RESET link would have survived the reset; the skip paths now clear stale tokens. R-37: the post-RESET staleness banner, narrow by design — an in-flight reset does not trigger it, it clears itself on the first post-RESET report, and ties resolve to STALE because SQLite timestamps are second-resolution and a same-second report almost certainly predates the reset. Both red-proofed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Nn3VgQk9iwEGgyx6QJ2NvE
This commit is contained in:
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user