# Pipelines maintenance ## Consent (hard rule) The operator owns this system. No change to it happens without their explicit consent in the current conversation: new pipelines or versions, definition and stage-prompt edits, orchestration scripts, briefs and the conventions they carry, the packaged skill and templates, deploys, installs and deletions. Read-only investigation and reporting need no consent. Ask first and name exactly what would change; a request for a fix is not consent for a particular mechanism. When a change alters user-facing behavior, or you learn a confirmed runtime limitation, record the stale documentation instead of editing the shared document in the same change: leave a per-item note at `docs/notes/.md` naming what changed and which packaged OpenCode skill reference in `internal/author/skill/references/`, README or topic doc is now stale and what should change there. The manual-only `docs-fold` pipeline folds `docs/notes/` into the shared docs and references; an item never edits a shared document itself. Keep `SKILL.md` a concise, task-directed index: preserve ask-first authoring and never preload every reference. Separate current capabilities, dated verification evidence, deployment state and unimplemented ideas. Do not turn mocked or structural checks into live claims. For new references, update `internal/author/install.go`'s managed file inventory. Run the author package tests: they check embedding, reference links, installation, upgrades and protection of user modifications. Never hand-edit an installed copy as the source of truth; refresh it with the current-source `pipelines skill install` only when installation is requested. Do not deploy runtime changes merely because the skill is updated. Keep the shared docs and packaged references consistent through the single `docs-fold` writer rather than editing them per item: leave a `docs/notes/.md` note. ## Maintenance workflow Top-level agents advance work through the `pipelines` CLI; **the agent is the brain** and there is no orchestration script, driver, polling loop or lane machinery, and none may be written. Choose the pipeline by the area the work is in — `Android`, `TUI`, `Server`, `Generic`, `Plan and land`, `UI sweep`, `Probe` — each reading the project's own map (`android/AGENTS.md`, `internal/tui/AGENTS.md`, `internal/server/AGENTS.md`) for how that technology is built, tested, run and captured. Inspect the retained plan/implement/review outputs and diffs, execute the checks independently, and iterate on concrete failures rather than trusting stage summaries. An executing stage performs its own role directly and never recursively launches a workflow. If a pipeline is unavailable, ask instead of silently bypassing it. Never hardcode a disposable server URL as a project default; the configured endpoint is authoritative.