Files
pipelines/AGENTS.md
T
alan 05ae530442 Make Pipelines Docker-only with OpenCode and Pi
Install current verified harness releases inside Docker, preserve persistent accounts and settings, and provide separate interactive and pipeline model defaults with terminal onboarding and fuzzy pickers.

Add Docker-aware authoring transport, Pi stage execution, bounded workflow controls, reliable final-result readback and usage settlement, and finite short-lived CLI pipe draining. Keep dated installation evidence and packaged authoring guidance consistent.

Verified with a real Docker installation, both harness stages and interactive authors, the built-in plan/implement/review starter, independent host race/vet checks, installer tests, and packaged skill tests. Generated release receipts stay ignored in clean checkouts.
2026-10-11 23:00:25 +01:00

26 lines
1.5 KiB
Markdown

# Pipelines maintenance
When changing user-facing behavior or learning a confirmed runtime limitation,
update the relevant packaged OpenCode skill reference in
`internal/author/skill/references/` in the same change. 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 README/topic docs and the packaged reference consistent.
## Maintenance workflow
Top-level agents use the configured `Pipelines maintenance - plan implement review`
maintenance workflow for code changes. 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 the workflow is
unavailable, ask instead of silently bypassing it. Never hardcode a disposable
server URL as a project default; the configured endpoint is authoritative.