#4079 "the plan gate" (21a701c): the default drops from 0.90 to 0.80.
Why: measured live, plans reworded from existing milestones scored 0.83–0.87 against the milestone they restated, and distinct plans 0.72–0.77. At 0.90 only an identical title matched.
The Settings default moves with it.
#4084 "Approval requested" (6eb5ef5): in the reporting-back skill, any action held for the operator's yes goes under its own Approval requested section near the top of the reply.
What it lists: each change numbered, why it needs approval, how to undo it, and what happens after.
Also: the Asks table gains an Approval row, and it is pinned by test_reporting_back_skill.
Plugin version 2026.09.15.1921.
CI: 21a701c green (run 6914); 6eb5ef5 set to merge when its checks succeed.
- **#4079 "the plan gate" (21a701c):** the default drops from 0.90 to 0.80.
- Why: measured live, plans reworded from existing milestones scored 0.83–0.87 against the milestone they restated, and distinct plans 0.72–0.77. At 0.90 only an identical title matched.
- The Settings default moves with it.
- **#4084 "Approval requested" (6eb5ef5):** in the reporting-back skill, any action held for the operator's yes goes under its own **Approval requested** section near the top of the reply.
- What it lists: each change numbered, why it needs approval, how to undo it, and what happens after.
- Also: the Asks table gains an Approval row, and it is pinned by test_reporting_back_skill.
- Plugin version 2026.09.15.1921.
CI: 21a701c green (run 6914); 6eb5ef5 set to merge when its checks succeed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01821k5B3Ysecp9fNYs92Kuy
Measured live after deploy: three plans reworded from existing active
milestones scored 0.83-0.87 against the milestone they restated, and the
nearest distinct plans 0.72-0.77. At the inherited 0.90 the semantic arm
matched nothing, so only an identical title was caught. 0.80 sits in the gap.
The Settings form's default moves with it (test_settings_defaults_agree).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01821k5B3Ysecp9fNYs92Kuy
A session's go-ahead request sat inside a completion list as "Blocked by the
permission check", and the operator read it as a fault rather than a question
waiting on them. The reporting-back skill now puts any action held for a yes
under a section headed "Approval requested", near the top of whatever reply
it is: each change numbered so part can be approved, why it needs them, how
it is undone, and what happens after. The Asks table gains an Approval row,
and the completion report's "Needs you" points at the section.
test_reporting_back_skill pins the heading and the row. Plugin version minted:
2026.09.15.1921.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01821k5B3Ysecp9fNYs92Kuy
bvandeusen
scheduled this pull request to auto merge when all checks succeed 2026-09-15 15:23:00 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
21a701c): the default drops from 0.90 to 0.80.6eb5ef5): in the reporting-back skill, any action held for the operator's yes goes under its own Approval requested section near the top of the reply.CI:
21a701cgreen (run 6914);6eb5ef5set to merge when its checks succeed.🤖 Generated with Claude Code
https://claude.ai/code/session_01821k5B3Ysecp9fNYs92Kuy