Records the operator policy set on 2026-08-11, matching cc-ci-orchestrator.
Work here goes branch → PR → merge it yourself once verified → operator reviews retrospectively.
No commits straight to main, and no waiting for review before merging — blocking would stall the
CI this repo runs.
The PR is not a gate; it is how the work stays legible after the fact. The description carries what
changed, why, and the evidence (harness output, a verified run, a before/after number).
Recipe repos are excluded: coop-cloud/<recipe> and its mirrors are created and verified but
never agent-merged, because those change what deploys on other people's infrastructure.
Also points at tests/STYLE.md, added in #17, before any test edit.
Records the operator policy set on 2026-08-11, matching `cc-ci-orchestrator`.
Work here goes **branch → PR → merge it yourself once verified → operator reviews retrospectively**.
No commits straight to `main`, and no waiting for review before merging — blocking would stall the
CI this repo runs.
The PR is not a gate; it is how the work stays legible after the fact. The description carries what
changed, why, and the evidence (harness output, a verified run, a before/after number).
**Recipe repos are excluded**: `coop-cloud/<recipe>` and its mirrors are created and verified but
never agent-merged, because those change what deploys on other people's infrastructure.
Also points at `tests/STYLE.md`, added in #17, before any test edit.
Operator policy (2026-08-11), matching cc-ci-orchestrator. Branch, PR, merge once
verified, operator reviews after. The PR is not a gate - it is how the work stays
legible - so the description carries what changed, why, and the evidence.
Recipe repos are explicitly excluded: created and verified, never agent-merged.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Records the operator policy set on 2026-08-11, matching
cc-ci-orchestrator.Work here goes branch → PR → merge it yourself once verified → operator reviews retrospectively.
No commits straight to
main, and no waiting for review before merging — blocking would stall theCI this repo runs.
The PR is not a gate; it is how the work stays legible after the fact. The description carries what
changed, why, and the evidence (harness output, a verified run, a before/after number).
Recipe repos are excluded:
coop-cloud/<recipe>and its mirrors are created and verified butnever agent-merged, because those change what deploys on other people's infrastructure.
Also points at
tests/STYLE.md, added in #17, before any test edit.