From ae285f55974ae521baaa817e98db2ff87a526735 Mon Sep 17 00:00:00 2001 From: rob thijssen Date: Fri, 7 Aug 2026 17:59:51 +0300 Subject: [PATCH] =?UTF-8?q?docs:=20stage=200=20complete=20=E2=80=94=20agen?= =?UTF-8?q?t=20login=20done,=20all=20three=20units=20active?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The interactive login is the one step in stage 0 that cannot be automated, and it is now done. preflight reports a present subscription login; tireless-runner is active alongside the api and poller. Recording it because the previous text said the runner was in `failed`, which was true for about an hour and is now exactly the kind of stale status this repo keeps trying not to leave lying around. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_013TxK1CWPkFXqdcXMJ4hVe6 --- doc/plan/design.md | 16 ++++++++-------- readme.md | 6 +++--- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/plan/design.md b/doc/plan/design.md index 4ad658e..f989d52 100644 --- a/doc/plan/design.md +++ b/doc/plan/design.md @@ -611,15 +611,15 @@ There is no invariant here that is merely written down. loads at `tireless.internal`, all three units are active, `tireless preflight` reports the expected billing mode, and the deploy workflow is green end to end. -**Deployed and verified, 2026-08-07.** The workflow runs green end to end; -`tireless-api` and `tireless-poller` are active on bob; `https://tireless.internal` -serves the dashboard and proxies `/v1`; the served certificate matches disk. +**Complete, deployed and verified, 2026-08-07.** The workflow runs green end to +end; all three units are active on bob; `https://tireless.internal` serves the +dashboard and proxies `/v1`; the served certificate matches disk; and +`tireless preflight` reports a present subscription login with the OpenCode lane +asserted non-Anthropic. -*Outstanding, and deliberately so:* `tireless-runner` is in `failed`, because the -interactive agent login has not been done as the service account on bob -(`script/infra-setup.sh` step 1). That is the invariant working — a runner with -no credentials refuses to start rather than pretending — and it is the one thing -in stage 0 that cannot be automated. +The interactive agent login (`script/infra-setup.sh` step 1) is done. Until it +was, `tireless-runner` sat in `failed` — which was the invariant working, not a +defect: a runner with no credentials refuses to start rather than pretending. Seven faults were found getting the first deploy green, and they are worth knowing because most were invisible rather than loud: diff --git a/readme.md b/readme.md index b42b2c5..1a41fd2 100644 --- a/readme.md +++ b/readme.md @@ -32,11 +32,11 @@ Full design, constraints and the staged implementation plan: Working: the domain model, routing, budgets, plan validation, the policy guards, configuration loading and validation, the four system prompts, and preflight. -The API and poller run on bob, the dashboard is served at +All three units run on bob, the dashboard is served at `https://tireless.internal`, and the deploy workflow is green end to end. -`tireless-runner` deliberately refuses to start until the interactive agent -login has been completed as the service account — see `script/infra-setup.sh`. +Nothing is polled or claimed yet — that is stage 1. The runner is up but has no +job store to claim from. Not built: Postgres persistence, the forge clients, the poll loop, and every agent executor. Stages 1–8 in §7 of the design document say what lands when.