01d5dad9b9
Rewrite the workflow documentation to describe how the system actually works: the agent (the session) is the brain and advances the queue by hand through the `pipelines` CLI. There is no orchestration script, no driver, no polling loop and no lane machinery, and none may be written. - references/work.md: rewritten end to end. The queue-driver script (drivers/workd.sh), the claim-file ledger with atomic renames, the PAUSED marker and the poll loop are gone. State is now the server (authoritative for run state), the queue file (authoritative for intent) and the conversation. The agent reads the queue, picks the item, creates its worktree/branch and launches it with `pipelines run <pipeline> <brief> --json --yes`; progress is event-driven via a background `pipelines wait <run-id> [...]` (never polled); on completion the agent reconciles with `pipelines inspect <run-id> --json`, verifies it landed and starts the next item. - references/queue.md: the landing gate runs the command directly (`git merge-base --is-ancestor <branch> main`, exit 0 = landed) instead of a `land-check.sh` helper; the never-delete-branch / never-remove-worktree rules are kept, and the waiting section states the agent advances the queue by hand. - references/orchestration.md: intro and "Running and watching" state the agent-driven, event-driven model; "Pipeline choice" names the current set (Android, TUI, Server, Generic, Plan and land, UI sweep, Probe) by area and records the retired names. - references/debugging.md: "Duplicated work after a driver restart" became "…after a session restart", resuming from the queue file not a cursor file. - SKILL.md: the routing row no longer says "queue driver". - AGENTS.md: the maintenance workflow names the current pipeline set instead of the retired `Pipelines maintenance - plan implement review`. - internal/tui/AGENTS.md: the restart line no longer names lanes. - docs/notes/agent-driven-work-model.md: the docs-fold note recording that docs/cli.md needs its "Scripted runs"/`--wait` framing aligned to the event-driven model, and that the dated evidence docs stay as they are. Checked before committing: no packaged template directory exists in this repo, so none needed updating; internal/author/install.go's managed file inventory needs no change (no packaged reference was added or removed — the 13 listed files all match internal/author/skill/references/); no stale `queue driver`/`workd.sh`/ `claim-file` references remain anywhere under internal/author. Genuine device tooling (android/scripts/capture_png.sh-style) and server-side polling prose were left alone. Checks: `go test ./internal/author -count=1` ok; `go build ./...` clean; `go vet ./...` clean; `gofmt -l .` clean.
3.2 KiB
3.2 KiB
Work documentation now describes the agent-driven model
What this item changed
The workflow documentation was rewritten to describe how the system actually works:
the agent (the session) is the brain and advances the queue by hand through the
pipelines CLI. There is no orchestration script, no driver, no polling loop and no
lane machinery, and none may be written.
internal/author/skill/references/work.md— rewritten end to end. The queue-driver script (drivers/workd.sh), the claim-file ledger with atomic renames, thePAUSEDmarker and the poll loop are gone. The ledger is now the per-project markdownqueue.md(authoritative for intent) plusnotes.md; run state is read from the server (pipelines inspect <run-id> --json); the agent launches each run itself withpipelines run <pipeline> <brief> --json --yesfrom the item's worktree and is woken by a backgroundpipelines wait.internal/author/skill/references/queue.md— the landing gate now runs the command directly (git merge-base --is-ancestor <branch> main, exit 0 = landed) instead of aland-check.shhelper; the waiting section states the agent advances the queue by hand and there is no driver.internal/author/skill/references/orchestration.md— the intro and "Running and watching" state the agent-driven, event-driven model; "Pipeline choice" now names the current set (Android,TUI,Server,Generic,Plan and land,UI sweep,Probe), chosen by area, and records the retired names.internal/author/skill/references/debugging.md— "Duplicated work after a driver restart" became "…after a session restart", resuming from the queue file rather than a cursor file.internal/author/skill/SKILL.md— the routing table row no longer says "queue driver".AGENTS.md— the maintenance workflow section names the current pipeline set instead of the retiredPipelines maintenance - plan implement review.internal/tui/AGENTS.md— the "do not restart … the lanes …" line no longer names lanes.
delivery.md, operations.md and verification.md were swept and needed no change:
they contain no driver, poll loop, cursor file or lane guidance. Genuine device tooling
(android/scripts/capture_png.sh) is left alone.
Shared documents this change makes stale
No README or topic doc still teaches the scripted driver model. One topic doc needs a
wording alignment for the event-driven model; the docs-fold writer should apply it
when it next folds notes:
docs/cli.md— its "Scripted runs" section frames runs as scripted automation, and its--waitparagraph is the only follow-a-run guidance. It should state that the agent (not a script) advances work, and thatpipelines wait <run-id> [run-id ...]run as a background task is the event-driven wait. Thewaitcommand's own flag text is already recorded separately indocs/notes/wait-command.md.
Do not change
- The dated evidence documents (
docs/pipeline-performance-review.md,docs/chat-verification.md,docs/app-integration-verification.md) describe the scripted era as it was and stay as they are. internal/author/install.go's managed file inventory needs no change: no packaged reference file was added or removed.