Skip to content

fix: release v1.13.3 with helper report resilience#32

Merged
amariichi merged 1 commit intomainfrom
fix/helper-report-resilience-v1.13.3
Mar 15, 2026
Merged

fix: release v1.13.3 with helper report resilience#32
amariichi merged 1 commit intomainfrom
fix/helper-report-resilience-v1.13.3

Conversation

@amariichi
Copy link
Owner

Summary

  • Add MCP tool permission blockage detection after inject timeout: if no progress report arrives and assignment shows timeout, operator checks helper pane directly instead of firing rescue
  • Add zero-report inbox rule: if inbox has zero reports (not even progress) from a helper, treat the report channel as broken and check pane directly
  • Add helper-side fallback: if agent.report fails due to permissions, helper continues work and leaves results in terminal output

Context

Live helper smoke test after v1.13.2 showed both helpers completed their reviews successfully but never delivered agent.report to the owner inbox due to MCP tool permission prompts in fresh worktree environments. These three rules make the operator workflow resilient to that failure mode without requiring agent-specific permission configuration.

Test plan

  • npm test passes (258 pass / 0 fail)
  • uv.lock diffs verified: only project-own packages changed

🤖 Generated with Claude Code

Address three gaps observed during live helper smoke testing:
1. Operator checks for MCP tool permission blockage after inject
   timeout (no progress report = possible permission prompt, not stall)
2. Zero-report inbox = broken channel rule before rescue decisions
3. Helper fallback: continue work and leave terminal output when
   agent.report calls fail due to permissions

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@amariichi amariichi merged commit 4db7011 into main Mar 15, 2026
1 check passed
@amariichi amariichi deleted the fix/helper-report-resilience-v1.13.3 branch March 15, 2026 09:38
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