potiuk opened a new pull request, #503:
URL: https://github.com/apache/airflow-steward/pull/503
## Summary
- The terminal-tint helper tinted on every `Stop` event, so a turn that
merely *finished* (Claude idle until you start the next thing) looked
identical to one genuinely **blocked on your decision**. This reworks the
state machine to tint only when Claude actually wants you to act.
- Six hooks: `Stop`→`stop` (heuristic — tints only if the final assistant
message reads as a question/request; completion stays calm; needs
`python3`/`python`, else defaults calm),
`PreToolUse`[`AskUserQuestion`]→`wait`,
`PostToolUse`[`*`]→`reset`, `Notification`→`notify` (idle ping is a no-op),
`UserPromptSubmit`/`SessionStart`→`reset`.
- `PostToolUse` (not `PreToolUse`) now carries the general reset so it can
clear a tint the permission prompt itself set; the idle ping is a
deliberate no-op so it can't wipe a pending question's tint after ~60s.
## Type of change
- [x] Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM) —
`tools/agent-isolation/`
- [x] Documentation (`docs/`) — wiring table, install JSON, install-skill
checklist, README row
## Test plan
- [x] `prek run` (all hooks) passed on the commit — markdownlint, typos,
lychee, placeholders, skill-and-tool-validate
- [x] Helper is opt-in and cosmetic (no security control); verified live on
iTerm2 + macOS over an extended dogfooding period in `~/.claude/scripts/`
- [x] Script + all three doc references (README row, wiring table, install
JSON, checklist prose) updated in lockstep — no stale 5-hook/`Stop→wait`
references remain
## RFC-AI-0004 compliance
- [x] **Sandbox** — no new host access; opt-in cosmetic helper, off by
default
## Notes for reviewers
This promotes a locally-dogfooded enhancement to the framework's copy. The
behavioural core is the `Stop`→`stop` heuristic that reads the last assistant
message from the transcript (path on stdin) and the
`PreToolUse`→`PostToolUse`
swap for the reset path. Fail-soft: no `python3` → `stop` defaults calm.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
