You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 04c0791
Browse filesBrowse the repository at this point in the historyBrowse files
- Queued turn starts are unsettleable: new hasQueuedTurnStart (client)
detects a user message no turn has picked up (newest user message
strictly newer than every latestTurn timestamp; a failed session
start clears the block); canSettle and effectiveSettled refuse it,
and the decider enforces the same invariant server-side, so
just-requested work can be neither settled nor auto-settled by a
closed PR.
- Capability-aware classification: threads on environments without
threadSettlement (old server, or descriptor not yet loaded) never
partition into the settled tail on web or mobile — a tail with no
working un-settle/pin affordances was strandable. Unknown is treated
as unsupported.
- Post-settle navigation validates the CURRENT route before firing:
a navigation made while the settle was in flight wins.
- Scope flips clear the thread selection, and the bulk context menu
derives one exact actionable set (rendered rows only) so labels
count exactly what actions will touch.
- Settle/unsettle re-emissions are projected no-ops: duplicates keep
the existing updatedAt instead of churning ordering.
- Web settle-blocked failures use a settlement-specific error matching
mobile copy instead of ThreadArchiveBlockedError's archive wording.
- New coverage: queued-turn tests (client + decider), settled event
round-trip through the DB ProjectionPipeline, capability-gated
partition fixtures.
Co-Authored-By: Claude Fable 5 <[email protected]>
0 commit comments