Revise task creation policy for Coder instructions
Clarify the task creation policy for Coder in the charter or Coder's specific instruction: Coder must do all of its cleanup and improvements in its own session. It only creates follow ups if it notices something very important and unrelated to its own task. Do not just add this - rephrase all task creation related prose into a concise clear instruction.
Outcome
Charter's task-creation prose collapsed into one "Scope and follow-ups" rule (own-diff cleanup in session; file only unrelated bug/security/data loss; ignore the rest), coder licences + community charter aligned. Quick gate + changed-area tests green; PR #7358 queued. Memory: none applied.
Artifacts
Activity
- Created
- Run
- Runner started
- Awaiting response
- Awaiting response
- Awaiting response
- Awaiting response
- Awaiting response
- Runner resumed
- Runner ended (done)