Stop engineer prompts from iterating against live CI #1587

New issue

Closed

opened 2026-07-28 04:17:25 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-28 04:17:25 +00:00

Member

Context

Parent goal: #1574. Observed run: #1584.

The credential rotation tracked in coilyco-bridge/agentic-os-kai#776 is complete. This issue owns the remaining Ward prompt correction.

Outcome

Make Ward's engineer and QA seeds obey the sealed-role rule that these roles may inspect live CI but must not debug or iterate against it.

The current review-gate language directs an engineer to fetch status, patch, push, and repeat until green. That conflicts with the governing role contract and previously caused an engineer to absorb unrelated work into a live-CI probe cycle.

Required behavior

Replace every engineer and QA prompt that directs repeated CI pushes with the sealed-role boundary.
Permit read-only status and log inspection.
Permit one locally grounded corrective push only when repository evidence proves the change.
After a live-only or repeated failure, require a separate interactive issue containing the exact run, first actionable error, local proof state, and operator verification request.
Keep director and Ops authority distinct. Do not transfer live remediation authority into engineer prompts.
Update the relevant workflow documentation. This is a behavior correction, not a docs/FEATURES.md change.

Acceptance criteria

Regression tests reject phrases or behavior equivalent to push and repeat until green in engineer and QA seeds.
Tests preserve read-only CI observation and one locally proven corrective push.
Tests require a separate interactive operator handoff for repeated or live-only failures.
Repository validation passes.

Headless execution boundary

Implement and prove this correction through repository tests. Do not trigger, mutate, or repeatedly probe live CI for acceptance.

## Context Parent goal: #1574. Observed run: #1584. The credential rotation tracked in coilyco-bridge/agentic-os-kai#776 is complete. This issue owns the remaining Ward prompt correction. ## Outcome Make Ward's engineer and QA seeds obey the sealed-role rule that these roles may inspect live CI but must not debug or iterate against it. The current review-gate language directs an engineer to fetch status, patch, push, and repeat until green. That conflicts with the governing role contract and previously caused an engineer to absorb unrelated work into a live-CI probe cycle. ## Required behavior * Replace every engineer and QA prompt that directs repeated CI pushes with the sealed-role boundary. * Permit read-only status and log inspection. * Permit one locally grounded corrective push only when repository evidence proves the change. * After a live-only or repeated failure, require a separate interactive issue containing the exact run, first actionable error, local proof state, and operator verification request. * Keep director and Ops authority distinct. Do not transfer live remediation authority into engineer prompts. * Update the relevant workflow documentation. This is a behavior correction, not a docs/FEATURES.md change. ## Acceptance criteria * Regression tests reject phrases or behavior equivalent to `push and repeat until green` in engineer and QA seeds. * Tests preserve read-only CI observation and one locally proven corrective push. * Tests require a separate interactive operator handoff for repeated or live-only failures. * Repository validation passes. ## Headless execution boundary Implement and prove this correction through repository tests. Do not trigger, mutate, or repeatedly probe live CI for acceptance.

coilyco-ops added the

priority

label

2026-07-28 04:17:25 +00:00

coilyco-ops referenced this issue

2026-07-28 04:18:57 +00:00

Stabilize Ward for safe autonomous burndown and verified releases #1574

coilyco-ops referenced this issue

2026-07-28 04:22:42 +00:00

Close fail-open gaps in actor admission PR 1583 #1585

coilyco-ops added

autonomy