feat: add General Rules section to all ROLE.md files

- workflow_exception: call when encountering unresolvable blockers
- Lessons learned: always write to memory after task slots
- README: all repos must have README.md + README-zh.md with lang nav

These rules apply to all agents via PrismFacet injection, so
individual workflows don't need to repeat them.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

roles/agent-resource-director/ROLE.md

@@ -52,3 +52,9 @@ Periodically assigned via HF task. Analyze each agent's recent performance, curr
 ## Memory Practice
 
 After each evaluation cycle, write to `memory/YYYY-MM-DD.md`: workload recommendations made, performance observations, branch assessment results, and any evaluation criteria updates.
+
+## General Rules
+
+- If you encounter an unresolvable blocker during any workflow, call `workflow_exception` with a summary of the problem. This clears your workflow stack, records the issue in your journal, and sets your status to idle.
+- Always write lessons learned to `memory/YYYY-MM-DD.md` after completing a task slot.
+- All project repositories must have README.md (English) and README-zh.md (Chinese) with language navigation at the top.

roles/developer/ROLE.md

@@ -35,3 +35,9 @@ role-code: dev
 ## Memory Practice
 
 After completing each task slot, write a brief summary to `memory/YYYY-MM-DD.md` including what was done, key decisions, and output references (commits, PRs, files).
+
+## General Rules
+
+- If you encounter an unresolvable blocker during any workflow, call `workflow_exception` with a summary of the problem. This clears your workflow stack, records the issue in your journal, and sets your status to idle.
+- Always write lessons learned to `memory/YYYY-MM-DD.md` after completing a task slot.
+- All project repositories must have README.md (English) and README-zh.md (Chinese) with language navigation at the top.

roles/manager/ROLE.md

@@ -34,3 +34,9 @@ role-code: mgr
 ## Memory Practice
 
 After completing each planning or review slot, write a summary to `memory/YYYY-MM-DD.md` including task assignments made, milestone updates, and any blockers identified.
+
+## General Rules
+
+- If you encounter an unresolvable blocker during any workflow, call `workflow_exception` with a summary of the problem. This clears your workflow stack, records the issue in your journal, and sets your status to idle.
+- Always write lessons learned to `memory/YYYY-MM-DD.md` after completing a task slot.
+- All project repositories must have README.md (English) and README-zh.md (Chinese) with language navigation at the top.

roles/mentor/ROLE.md

@@ -34,3 +34,9 @@ role-code: mt
 ## Memory Practice
 
 After reviewing or creating skills, write to `memory/YYYY-MM-DD.md`: which skills were modified, what changed, which branches were evaluated, and any quality concerns.
+
+## General Rules
+
+- If you encounter an unresolvable blocker during any workflow, call `workflow_exception` with a summary of the problem. This clears your workflow stack, records the issue in your journal, and sets your status to idle.
+- Always write lessons learned to `memory/YYYY-MM-DD.md` after completing a task slot.
+- All project repositories must have README.md (English) and README-zh.md (Chinese) with language navigation at the top.

roles/operator/ROLE.md

@@ -35,3 +35,9 @@ role-code: op
 ## Memory Practice
 
 After each deployment or infrastructure change, write to `memory/YYYY-MM-DD.md`: what was deployed, which servers, any issues encountered, rollback steps if applicable.
+
+## General Rules
+
+- If you encounter an unresolvable blocker during any workflow, call `workflow_exception` with a summary of the problem. This clears your workflow stack, records the issue in your journal, and sets your status to idle.
+- Always write lessons learned to `memory/YYYY-MM-DD.md` after completing a task slot.
+- All project repositories must have README.md (English) and README-zh.md (Chinese) with language navigation at the top.

roles/secretary/ROLE.md

@@ -31,3 +31,9 @@ role-code: as
 ## Memory Practice
 
 After each meeting or communication task, write to `memory/YYYY-MM-DD.md`: meeting participants, key decisions, action items, and follow-up needed.
+
+## General Rules
+
+- If you encounter an unresolvable blocker during any workflow, call `workflow_exception` with a summary of the problem. This clears your workflow stack, records the issue in your journal, and sets your status to idle.
+- Always write lessons learned to `memory/YYYY-MM-DD.md` after completing a task slot.
+- All project repositories must have README.md (English) and README-zh.md (Chinese) with language navigation at the top.