diff --git a/AGENTS.md b/AGENTS.md index 297b99d5..968f012c 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,5 +1,14 @@ # 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 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, diff --git a/internal/author/skill/references/orchestration.md b/internal/author/skill/references/orchestration.md index a2aa982e..d92bb6d5 100644 --- a/internal/author/skill/references/orchestration.md +++ b/internal/author/skill/references/orchestration.md @@ -55,8 +55,7 @@ Every brief has: output it must report, plus the screenshots the reviewer must read. Say plainly: "report the exact commands and their observed results. Do not claim a check you did not run." -5. **Where it belongs** — the packaged templates, the repository's guidelines (README - and topic docs) and the packaged skill references the change is expected to touch, +5. **Where it belongs** — the packaged templates and the packaged skill references the change is expected to touch, so the committer can check and update them before it commits. 6. **The hard constraints block** (below). 7. **Publishing rules** (`references/delivery.md`). @@ -107,8 +106,8 @@ Adapt the scope and publishing lines per item; keep the rest. from the source that already owns them, not from new literals. - **Commit locally only, never push** — the committer stage commits, no other stage. - **Reflect the change where it belongs** — before committing, the committer checks - that the change is reflected in the packaged templates, the repository's guidelines - (README and topic docs) and the packaged skill references, updates anything stale, + that the change is reflected in the packaged templates and the packaged skill references, + updates anything stale, and states in the commit body what it checked or that nothing needed updating. - **Publish rules** — WIP artefact naming and LAN URLs per `references/delivery.md`. @@ -124,7 +123,7 @@ Adapt the scope and publishing lines per item; keep the rest. change approved without the images. - The committer is the only stage that commits, and it stages only the run's changed files. Before committing it checks that the change is reflected in the packaged - templates, the repository's guidelines (README and topic docs) and the packaged + templates and the packaged skill references, updates anything stale, and states in the commit body what it checked or that nothing needed updating. It must also select `input.server_changed_files` (the runner's captured evidence, `references/control.md`) alongside the implementer's