docs(framework): add agency & persistence patterns to config + guides

Seven additive behavioral rules distilled from the Claude Code system
prompt, competitor autonomous-agent prompts (Devin/Cline/Cursor/Windsurf/
Droid/Manus/Replit), and Fable 5 consumer-prompt deltas:

- SOUL.md: own-mistakes stance, USER.md formatting override, reversibility
  heuristic (hard-gate-reconciled), injected-content caution
- AGENTS.md: Block vs. Done semantics
- E2E-DELIVERY.md: failure-handling retry budget, pre-done self-interrogation
- ORCHESTRATOR.md: worker-prompt-quality standard, trust-but-verify
- QA-TESTING.md: integrity guardrails

Additive only (+37/-0). Independent review passed (one remediation applied).

Refs #542

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

packages/mosaic/framework/guides/E2E-DELIVERY.md

@@ -114,6 +114,13 @@ For implementation work, you MUST run this cycle in order:
 If any step fails, you MUST remediate and re-run from the relevant step before proceeding.
 If push-queue/merge-queue/PR merge/CI/issue closure fails, status is `blocked` (not complete) and you MUST report the exact failed wrapper command.
 
+### Failure Handling & Retry Budget (Hard Rule)
+
+1. On any step failure, diagnose before switching tactics: read the error, check assumptions, attempt one focused fix. Do not retry blindly; do not abandon the approach after a single failure.
+2. Cap remediation at 3 attempts per distinct failure (same test, same gate, same error class). Vary the approach each attempt; never repeat an identical fix.
+3. For transient network failures (push/pull/API), retry up to 4 times with exponential backoff (2s, 4s, 8s, 16s). Do not apply backoff retries to logic errors.
+4. After the attempt budget is exhausted, stop and escalate per the Steered Autonomy Escalation Triggers — record the failure, attempts made, and exact failing command in the scratchpad.
+
 ## 5. Testing Priority Model
 
 Use this order of priority:
@@ -178,6 +185,8 @@ For code/API/auth/infra changes, documentation updates are REQUIRED before compl
 
 You MUST satisfy all items before completion:
 
+Before running this checklist, pause and self-interrogate: did I fulfill the user's *full* intent (not a reframed subset), did I actually run every verification I'm about to claim, and did I catch every edit site? Treat any "I think so" as not-yet-done.
+
 1. Acceptance criteria met.
 2. Baseline tests passed.
 3. Situational tests passed (primary gate), including required greenfield situational validation.