8ac85a0b67
- Add permission rules to .claude/settings.json - Document empty merge and direct-to-master problems in problems.md - Fix agent stream URL to use vite proxy instead of hardcoded host - Add /agents proxy config to vite.config.ts Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.5 KiB
Problems
Recurring issues observed during pipeline operation. Review periodically and create stories for systemic problems.
2026-03-18: Stories graduating to "done" with empty merges
Pipeline allows stories to move through coding → QA → merge → done without any actual code changes landing on master. The squash-merge produces an empty diff but the pipeline still marks the story as done. Confirmed affected: 247, 273, 280. Stories 274, 278, 279 appeared empty via merge commits but code was actually committed directly to master by agents (see next problem). Root cause: no check that the merge commit contains a non-empty diff before advancing to done. Frequency: 3+ confirmed cases out of 10 done stories.
2026-03-18: Agent committed directly to master instead of worktree
Multiple agents have committed directly to master instead of their worktree/feature branch:
- Commit
5f4591f("fix: update should_commit_stage test to match 5_done") — likely mergemaster - Commit
a32cfbd("Add bot-level command registry with help command") — story 285 coder committed code + Cargo.lock directly to master
Agents should only commit to their feature branch or merge-queue branch, never to master directly. Suspect agents are running git commit in the project root instead of the worktree directory. This can also revert uncommitted fixes on master (e.g. project.toml pkill fix was overwritten). Frequency: at least 2 confirmed cases. This is a recurring and serious problem — needs a guard in the server or agent prompts.