Repository navigation
Manual verify: Watch mode (#32) #418
Description
Feature: Watch mode — long-running file system monitoring and GitHub polling.
Why manual verification needed:
- Requires sustained process execution (hours/days)
- Needs real GitHub API integration
- Involves timer/polling infrastructure that's hard to unit test
Test approach:
- Start squad in watch mode with
--watchflag - Create a new issue on GitHub and verify Ralph picks it up within the polling interval
- Close the issue and verify Ralph detects the state change
- Create a new PR and verify triage occurs
- Let the process run for several hours to verify no memory leaks or crashes
- Test graceful shutdown (Ctrl+C should clean up watchers)
Success criteria:
- ✅ Process remains stable for extended periods
- ✅ GitHub events are detected within expected polling intervals
- ✅ Resource usage (memory, file handles) remains stable
- ✅ Graceful shutdown without orphaned processes
Related: Issue #32
Activity
github-actions commentedon Mar 15, 2026
📋 Assigned to FIDO (Quality Owner)
Issue: #418 — Manual verify: Watch mode (#32)
FIDO will pick this up in the next Copilot session.
test: SDK feature parity tests for #340
test: SDK feature parity tests for #340 (#422)
Fix github#428/github#401: Verify input buffering covers all paths (g…
bradygaster commentedon Mar 24, 2026
Closing for now — will reopen once SDK-first (#341, #347) is complete. These manual verification items depend on SDK parity being finished first.