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/QA-TESTING.md

@@ -102,6 +102,10 @@ If a project's `playwright.config.ts` does not explicitly set `headless: true`,
 1. Do NOT stop at "tests pass" if acceptance criteria are not verified.
 2. Do NOT write narrow tests that only satisfy assertions while missing real workflow behavior.
 3. Do NOT claim completion without situational evidence for impacted surfaces.
+4. Do NOT edit tests to make them pass; assume the root cause is in the code under test unless the task is explicitly to fix the test.
+5. Do NOT fabricate sample data, stub responses, or mock around a real failure to produce a green result.
+6. Do NOT simplify, comment out, or narrow the feature/logic to dodge an error — debug the actual root cause.
+7. Do NOT reason about or claim behavior of code you have not opened and read.
 
 ## Reporting