Skip to content

fix: approval and Woke follow-ups from the upstream sync review - #171

Merged
pandec merged 3 commits into
devfrom
fork/approval-woke-followups
Aug 24, 2026
Merged

fix: approval and Woke follow-ups from the upstream sync review#171
pandec merged 3 commits into
devfrom
fork/approval-woke-followups

Conversation

@pandec

@pandec pandec commented Aug 24, 2026

Copy link
Copy Markdown
Owner

Two small defects surfaced by the post-sync merge review, unrelated to the merge itself.

Hermes approvals. The acceptAlways decision (added upstream for Codex in pingdotgg#8058) fell through Hermes's decision mapping to a silent reject_once. It now maps to allow_always, with a unit test on the exported mapping. Unreachable today since only Codex offers the option, but the decision union is provider-agnostic.

Woke indicator gating. The sidebar Woke pill and the chat wake banner suppressed themselves whenever a change request would auto-settle the thread, without checking the fork's auto-settle master gate. With the gate off the thread never settles, so the wake signal was lost. Both sites now suppress only while threadAutoSettleEnabled is on. Mobile has no change-request suppression on its wake signal, so nothing to change there.

Checks: vp check, vp run typecheck, and the focused Hermes adapter suite (25 tests) pass.

Implemented by Claude Fable 5 via Claude Code.

pandec added 3 commits August 24, 2026 12:08
A client sending the new acceptAlways decision to Hermes fell through the
decision mapping's default and silently rejected the request. It now selects
the allow_always option like acceptForSession does. Unreachable today (only
Codex offers the option) but the decision union is provider-agnostic.

Implemented by Claude Fable 5 via Claude Code.
The sidebar Woke pill and the chat wake banner suppressed themselves whenever
the thread's change request would auto-settle it, ignoring the fork's
auto-settle master gate. With the gate off the thread never settles, so the
wake signal must stay visible. Both sites now apply the suppression only
while autoSettleEnabled is true.

Implemented by Claude Fable 5 via Claude Code.
Review follow-up: the Woke suppression also ignored the explicit keep-active
pin and servers without the threadSettlement capability — both leave the
thread active, so the wake signal must show. The predicate now lives in
client-runtime as changeRequestMutesWakeSignal with tests, used by both the
sidebar pill and the chat banner, and the two stale settled-tail comments
were corrected.

Implemented by Claude Fable 5 via Claude Code.
@pandec
pandec merged commit cb6f21d into dev Aug 24, 2026
1 check passed
@pandec
pandec deleted the fork/approval-woke-followups branch August 24, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant