amadan
AGENTS.md: the agent finishes a root-performed adoption; the sweep grace is the backstop
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+6
−1
AGENTS.md+6 −1
CI passed — run details
diff --git a/AGENTS.md b/AGENTS.md| index cdca5b6a0..455dd458c 100644 |
| --- a/AGENTS.md |
| +++ b/AGENTS.md |
| @@ -344,7 +344,12 @@ anything. |
| poll it at 2s and run the full pass set. Direct-bucket promotes (pinfra |
| scripts) don't bump but canary/* channels are name-scoped fast anyway. |
| Blocked stages relay to a root pass (`carlos-stage.path` — must be armed; |
| - update-platform-binary.sh does it). `carlos deploy` is the member one-command |
| + update-platform-binary.sh does it). That root pass stages, repoints and |
| + stamps in ~8s but cannot cycle the agent's exec children, so the agent's |
| + 2s tick finishes the job: a warm instance whose route is stamped with the |
| + version its symlink names is cycled at once (`convergeAdopted`, #231). The |
| + activator sweep's 90s grace is only the backstop. `carlos deploy` is the |
| + member one-command |
| form: ship → promote → wait until `X-Carlos-Version` on the URL reports the |
| shipped build over 2xx. Verify deploys with that header (`curl -sI |
| --resolve`), never a cached answer. `-I` is fine for the VERSION header, but |