1.9 KiB
Claude automation manager review and recovery
Run292 implemented the observer and completed two review/fix cycles, then failed its third review with remaining timer-retention and exited-host issues. The manager took over directly without creating a recovery workflow.
Resolved findings:
- Own observer callbacks acknowledge absent/invalid metadata and clear unknown snapshots; unrelated callbacks keep their prior unsupported response.
- Direct snapshots belong only to the same live process. Hosted reads use the actual non-attaching status and reject exited/unreachable hosts, with no historical cache fallback. Observation time stays separate from query time.
- Status reads honor cancellation after connecting and bound responses to4MiB.
- Observed future native automations prevent adapter idle/excess reaping and detached host idle cleanup. An empty native snapshot allows ordinary cleanup. Existing explicit operator shutdown/max-detached policy remains unchanged.
Manager verification uses real owned scratch subprocesses and private Unix sockets, not model inference or production sessions. It covers native callback ACK without a server, retention/empty cleanup, missing metadata clearing, operator permissions left pending, old/exited/replaced process refusal, active attachment preservation, bounded-spool survival, cancellation and response-size refusal.
Checks passed: focused native automation tests; focused race tests for Claude and claudehost; go build ./..., go vet ./..., go test ./...; git diff --check. Logs: /tmp/claude-automation-manager-focused.log, /tmp/claude-automation-manager-race.log, /tmp/claude-automation-go-final.log. Native Claude model-auth probes failed before Stop; real native schedule delivery remains unverified. No login/config changes or real chat prompts were performed. Old retained hosts are not restarted or retrofitted. The composer feature and combined deployment follow separately.