# The plan in flight (AGENTS.md "Plan document before work"): docs/plans/0040-release-pipeline.md is the only plan. # docs/plans/0041-after-the-pipeline.md (port parity, docs, 0040's open items) is written and NOT in flight: it starts # when 0040 is done (owner, 2026-11-18). # docs/plans/0053-computer-socialweb-lexicons.md (rename to computer.socialweb, publish with goat lex publish, lexicon docs) # is written and NOT in flight: status waiting on 0040's Done when (two consecutive green promote rolls) (owner, 2026-11-19). # Its agent keeps this entry current: per Done-when item the target (from the plan), where it stands now, the proof # (knotless workflow log), and what it waits on; the step being worked. # Lead state: the State block at the top of docs/plans/0040-release-pipeline.md (kept current by the lead). plans: - plan: docs/plans/0043-cli-arguments.md agent: cli-args status: "steps 1-5 done on branch cli-args; review fixes in (guest script release skew, 0013:b, the CLI argument checker, parse-args, the prod units read); proofs in the plan's Built" next: "step 9 (the lead: swc-ssh-gateway.service to --ssh-gateway-spec-file before the promote), step 6 (land as one cycle), then 8 (atlibs page, site deploy after stable carries it) and 7; decision 11's old-requester/new-bidder cell on non-public networks waits on the lead or the owner" - plan: docs/plans/0040-release-pipeline.md agent: ci-bootstrap progress: staging: target: "CI test 48 of 48 PASS, 0 FAIL (no SKIP state), on step 21's second roll's commit" now: "42 of 48 in CI on main 0019f5f5 (roll three, test attempt 2, 12:37-15:04Z 11-22: RED; attempt 3 cancelled at 6 PASS of 20: the staging overlay, Findings). By hand on this tree + cli-help: 48 of 48 (stack9, stg-090117). Last green in CI: 47 of 47 on 324f69a1 (11-21)." log: "knotless run list knotless://socialweb.computer/socialweb-computer-kcp --commit 7b0afc69f4a2 --workflow test --log" waits_on: "the staging overlay (public relay throttling): measurement, then the owner's decision on the relay" prod_ci: target: "CI promote 31 of 31 both-entries PASS as prod bob and alice, on step 21's second roll" now: "31 of 31 PASS in CI at main 324f69a1 (promote v0.0.1-rc3, 07:31-08:39Z 11-21: green, wall 3718 s; stable v0.0.1). Before: 28 of 31 at 93fd8c11 (red, WebRTC from the release VM: fixed by decision 75)." log: "knotless run list knotless://socialweb.computer/socialweb-computer-kcp --commit 324f69a10b6c --workflow promote --log" waits_on: "the same on roll two's commit" ci_rolls: target: "step 21: two consecutive green CI promote runs to stable, no hand roll; between them only CLI help text changes under paths:" now: "0 in a row: roll two (main 7b0afc69) RED at test 19:38Z 11-21 (45 of 47), promote refused, prod untouched. Before it: promote 14 (v0.0.1-rc3, 324f69a1) GREEN 08:39Z 11-21, stable v0.0.1. Two consecutive greens owed, with only help text between them." log: "knotless run list knotless://socialweb.computer/socialweb-computer-kcp --commit 324f69a10b6c --workflow promote --log" waits_on: "staging" docs: target: "the docs checker and the pins check in the gate (steps 17, 20); docs and examples themselves moved to plan 0041 (owner decision 33)" now: "on main: check-docs.sh and the pins check in deploy/check.sh; 3 run=gate blocks run and pass (check-docs.sh: ok 5 docs, 2026-11-20)" log: "bash scripts/check-docs.sh" waits_on: "the two rolls" status: "steps 0-5 done (promote asked-only; promote.sh --dry-run rehearsed on the release image on main de0b91ee; hand builds to local/, rehearsed: publish+verify local/de0b91ee, ci-staging-binary local:); prod on rc174; no stable" next: "20:40Z 2026-11-22: PAUSED by the owner (he needs the machine; he restarts the lead tonight): no validation cycle, no roll, nothing deployed. Decision 80: our own iroh relay at iroh.socialweb.computer now (plan 0056), direct links later (plan 0057). Ready on branches, nothing landed: iroh-relay 90b4ace3 (plans 0056 and 0057, infra/iroh-relay with build.sh and deploy.sh (dry-run clean; binary built: ~/.tmp/iroh-relay/bin/iroh-relay sha256 26350dad...), the staging stand-up defaulting SOCIALWEB_MESHD_RELAY to our relay); log-filter 2f399ec8 and watch-cancel 0e08da46 (both reviewed safe); roll2 ee2c30ce (cli-help on 0019f5f5). RESUME, in order: 1. review the iroh-relay branch; 2. from its worktree: infra/iroh-relay/deploy.sh --dry-run, then --apply, then --status (rollback: --rollback --apply); read the runner container pids.current first; 3. a hand staging network: every link Relay(https://iroh.socialweb.computer/), bulk transfer at least 1 MB/s per VM, ping loss under 1%, save the meshd log; 4. one tree = main + iroh-relay + log-filter + watch-cancel, a full hand cycle in the default layout, 48 of 48; 5. one pull, the roll, read from inside with knotless run attach; 6. cli-help for the second roll. Known gaps: peer lookup still uses n0 DNS discovery (plan 0056 step 7: a meshd change); dumbpipe 0.40.1 hard-codes the n0 relays (guest ssh, ingress, the ssh gateway dialer: plan 0056 options b and c, owner to choose); the relay is open to anyone with the URL (a restriction is a proposed control). Open questions for the owner are listed in plan 0056. Prod on stable v0.0.1 (324f69a1), untouched; 0 green rolls in a row."