docs(harness): biome-clean rule + parallel-wave orchestration

- add .dispatch/rules/biome-clean.md (0 warnings/0 infos; no `!`/useLiteralKeys),
  wired into the every-agent scoping map + canonical invocation
- package-agent: note biome zero-tolerance; verify line clarifies 0 warnings AND 0 infos
- ORCHESTRATOR: document parallel-execution waves (2a) + agent-failure recovery
  patterns (5a) + concurrency caveats

1 files changed, 12 insertions, 0 deletions

diff --git a/.dispatch/rules/biome-clean.md b/.dispatch/rules/biome-clean.md
new file mode 100644
index 0000000..4cd5e83
--- /dev/null
+++ b/.dispatch/rules/biome-clean.md
@@ -0,0 +1,12 @@
+# Rule: biome is zero-tolerance (0 warnings, 0 infos)
+
+`bunx biome check` must finish with ZERO warnings AND ZERO infos — not just zero errors.
+"Clean" means there is no "Found N warnings" / "Found N infos" line at all. Fix the code;
+NEVER add a `// biome-ignore` comment and NEVER relax the biome config to silence a finding.
+
+Two findings recur — pre-empt them:
+- **No postfix non-null assertions (`value!`).** Narrow with an explicit guard
+  (`if (x === undefined) throw new Error(...)`) or a tiny `assertDefined` helper — this both
+  proves the intent and narrows the type. (Most common in tests.)
+- **No `useLiteralKeys`.** Use dot access for identifier keys (`obj.foo`); reserve bracket
+  access for genuinely dotted / dynamic keys (`obj["a.b"]`).