2 Commits

Include renames

Author	SHA1	Message	Date
HomerandClaude Opus 5.5	788db0ff4d	Harness spec 3.5.0: the watch command's hash puts the exit status after the bytes, so the output is hashed as it streams ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 12:13:38 +00:00
HomerandClaude Opus 5.5	e349d829a1	Harness spec 3.5.0: scheduled work on a linked computer ... Accept scheduled work (remote.scheduled, off by default) said as limits.scheduled; a scheduled turn is an agent session marked `scheduled` in the schedule's mode (Edit when none chosen, Plan refused, lowered to remote.max_mode) with its Min/Max; the answer reports status ok, silent, failed or cancelled and the final reply. Approvals wait the schedule's wait and go to the person through the server, then count as denied. _lembas/monitor runs a watch command under the mode's rules (one that would ask is refused) and answers a hash and an excerpt. Schedule routes of /api/v2 accept the device's token. team_add under a sub-manager names it (added_under). Conformance areas scheduled, silent, monitor; team cases changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 12:11:56 +00:00