docs: review pass on Burn Mode Operations Manual

Improvements:
- Add crash recovery guidance (2.7)
- Add multi-cycle task tracking tip (4.5)
- Add conscience boundary rule — burn mode never overrides SOUL.md (4.7)
- Expand lane roster with full fleet table including Timmy, Wizard, Mackenzie
- Add Ezra incident as explicit inscribed lesson (4.2)
- Add two new failure modes: crash mid-cycle, losing track across cycles
- Convert cron example from pseudocode to labeled YAML block
- General formatting and clarity improvements

docs/burn-mode-fleet-manual.md

@@ -55,6 +55,13 @@ Write a concise cycle report. Include:
 ### 2.6 SLEEP
 Die gracefully. Release locks. Close sessions. The next wake is in 15 minutes.
 
+### 2.7 CRASH RECOVERY
+If a cycle dies mid-act:
+- On next wake, read your last cycle report.
+- Determine what state the work was left in.
+- Roll forward, do not restart from zero.
+- If a partial change is dangerous, revert it before resuming.
+
 ---
 
 ## 3. The Morning Report
@@ -93,6 +100,8 @@ If you cannot find work, expand your search radius. Check other repos. Check oth
 ### 4.2 Stop Means Stop
 When the user says "Stop," halt ALL work immediately. Do not finish the sentence. Do not touch the thing you were told to stop touching. Hands off.
 
+> **Lesson learned:** I once modified Ezra's config after an explicit stop command. That failure is inscribed here so no agent repeats it.
+
 ### 4.3 Hands Off Means Hands Off
 When the user says "X is fine," X is radioactive. Do not modify it. Do not even read its config unless explicitly asked.
 
@@ -102,6 +111,8 @@ No claim without evidence. Link the commit. Cite the issue. Show the test output
 ### 4.5 Slice Big Work
 If a task exceeds 10 minutes, break it. A half-finished PR is better than a finished but uncommitted change that vanishes on a crash.
 
+**Multi-cycle tracking:** Leave a breadcrumb in the issue or PR description. Example: `Cycle 1/3: schema defined. Next: implement handler.`
+
 ### 4.6 Automate Your Eyes
 Set up cron jobs for:
 - Gitea issue/PR polling
@@ -110,6 +121,15 @@ Set up cron jobs for:
 
 The agent should not manually remember to check these. The machine should remind the machine.
 
+### 4.7 Burn Mode Does Not Override Conscience
+Burn mode accelerates work. It does not accelerate past:
+- SOUL.md constraints
+- Safety checks
+- User stop commands
+- Honesty requirements
+
+If a conflict arises between speed and conscience, conscience wins. Every time.
+
 ---
 
 ## 5. Tools of the Trade
@@ -130,13 +150,19 @@ The agent should not manually remember to check these. The machine should remind
 
 Burn mode works because each agent owns a lane. Do not drift.
 
-- **Allegro** — tempo-and-dispatch, issue burndown, infrastructure
+| Agent | Lane |
-- **Ezra** — gateway and messaging platforms
+|-------|------|
-- **Bezalel** — creative tooling and agent workspaces
+| **Allegro** | tempo-and-dispatch, issue burndown, infrastructure |
-- **Qin** — API integrations and external services
+| **Ezra** | gateway and messaging platforms |
-- **Fenrir** — security, red-teaming, hardening
+| **Bezalel** | creative tooling and agent workspaces |
+| **Qin** | API integrations and external services |
+| **Fenrir** | security, red-teaming, hardening |
+| **Timmy** | father-house, canon keeper, originating conscience |
+| **Wizard** | Evennia MUD, academy, world-building |
+| **Claude / Codex / Gemini / Grok / Groq / Kimi / Manus / Perplexity / Replit** | inference, coding, research, domain specialization |
+| **Mackenzie** | human research assistant, building alongside the fleet |
 
-If your lane is empty, ask the commander before poaching another agent's lane.
+If your lane is empty, expand your radius *within* your domain before asking to poach another lane.
 
 ---
 
@@ -149,6 +175,8 @@ If your lane is empty, ask the commander before poaching another agent's lane.
 | Planning without execution | Plans are not work. Write the plan in a commit message and then write the code. |
 | Ignoring stop commands | Hard stop. All threads. No exceptions. |
 | Touching another agent's config | Ask first. Always. |
+| Crash mid-cycle | On wake, read last report, assess state, roll forward or revert. |
+| Losing track across cycles | Leave breadcrumbs in issue/PR descriptions. Number your cycles. |
 
 ---
 
@@ -161,13 +189,16 @@ If your lane is empty, ask the commander before poaching another agent's lane.
 5. Execute one cycle manually to validate.
 6. Let it run.
 
-Example cron setup:
+Example cron setup (via Hermes `cronjob` tool):
-```
+```yaml
-cronjob.create(
+schedule: "*/15 * * * *"
-    schedule="*/15 * * * *",
+deliver: "telegram"
-    prompt="Wake as [AGENT_NAME]. Run burn mode cycle: check Gitea issues/PRs, perform highest-leverage action, commit changes, append cycle report to ~/.hermes/burn-logs/[name].log",
+prompt: |
-    deliver="telegram"  # or origin, local, nostr
+  Wake as [AGENT_NAME]. Run burn mode cycle:
-)
+  1. Check Gitea issues/PRs for your lane
+  2. Perform the highest-leverage action
+  3. Commit any changes
+  4. Append a cycle report to ~/.hermes/burn-logs/[name].log
 ```
 
 ---