fix(.claude/ATT): renumber duplicate sections in EN sources

Two numbering collisions surfaced during the DE translation pass:

1. autoattended-orchestrator-spec.md had two §11 sections:
   §11 Cross-Language Parity Matrix (original)
   §11 Context Fidelity (added in §14/§15/§16 batch)
   The latter is renamed to §11A (matching what the DE version already
   does), with subsections §11.1..§11.6 → §11A.1..§11A.6. The §10 DoD
   checklist references and the README adoption-table anchor are
   updated accordingly.

2. agent-coordination-mcp-spec.md had two §1.3 sections:
   §1.3 The universal wire format (added with the wire-format fold-in)
   §1.3 What this spec is NOT (original)
   The latter is renumbered to §1.5, restoring monotonic ordering
   §1.1, §1.2, §1.3, §1.4, §1.5.

Pure renumbering — no content changes. The DE/ translations already use
the corrected numbering.

Author: AdaWorldAPI

.claude/ATT/README.md

@@ -31,7 +31,7 @@ docs in `.claude/EN/` didn't have, now incorporated:
 |---|---|---|---|
 | 1 | Typed `status.json` schema + 5-value `StageStatus` enum (attractor Appendix C: `{outcome, preferred_label, suggested_next_ids, context_updates, notes}`) | [`autoattended-orchestrator-spec.md` §9](./autoattended-orchestrator-spec.md#9-status-file-schema) | Adopted **with `auto_status=false` mandatory** (see "Where it conflicts" below). |
 | 2 | DOT graph DSL for the workflow + lint rules (attractor §2 grammar + §7 validation: `reachability`, `start_no_incoming`, `goal_gate_has_retry`, `condition_syntax`) | [`autoattended-orchestrator-spec.md` §6](./autoattended-orchestrator-spec.md#6-sprint-plan-format) (DOT + YAML mirror) + [§7](./autoattended-orchestrator-spec.md#7-validation-rules) (WAVE-001..WAVE-017 with ERROR/WARNING severity) | Adopted with three wave-specific additions: `unique-write`, `declared-shared`, `auto-status-false`. |
-| 3 | Context Fidelity ladder (attractor §5.4: `full` / `truncate` / `compact` / `summary:low/medium/high` with token budgets + edge > node > graph > default precedence) | [`autoattended-orchestrator-spec.md` §11](./autoattended-orchestrator-spec.md#11-context-fidelity) | Adopted with one tightening: `fidelity=truncate` does NOT exempt a worker from the §3.3 Reading-Depth-Ladder of `anti-skim-agent-spec.md`. |
+| 3 | Context Fidelity ladder (attractor §5.4: `full` / `truncate` / `compact` / `summary:low/medium/high` with token budgets + edge > node > graph > default precedence) | [`autoattended-orchestrator-spec.md` §11A](./autoattended-orchestrator-spec.md#11a-context-fidelity) | Adopted with one tightening: `fidelity=truncate` does NOT exempt a worker from the §3.3 Reading-Depth-Ladder of `anti-skim-agent-spec.md`. |
 | 4 | In-loop tool-call loop detection (attractor coding-agent §2.10: last 10 calls scanned for length-1/2/3 repeating patterns → inject steering warning) | [`anti-skim-agent-spec.md` §6](./anti-skim-agent-spec.md#6-tool-call-loop-detection) + AP9 in [§9](./anti-skim-agent-spec.md#9-anti-pattern-catalog-ap1ap9) | Adopted verbatim; elevated to a system-level invariant. PP-13's post-hoc AP9 catches what the in-loop detector misses. |
 | 5 | Definition-of-Done checklists + Cross-Provider Parity Matrix per spec (attractor §10-style conformance tables) | Each NLSpec ends with `§ Definition of Done` + `§ Cross-{Language,Provider} Parity Matrix` | Adopted as the structural template. The 26-repo rollout is now machine-checkable. |
 

.claude/ATT/agent-coordination-mcp-spec.md

@@ -92,7 +92,7 @@ configuration defaults, parity matrices). Rationale:
 Use prose for: section overviews, rationale paragraphs, conflict
 explanations. Use tables for: everything else.
 
-### §1.3 What this spec is NOT
+### §1.5 What this spec is NOT
 
 - Not a workflow engine. Wave / sprint structure is in
   [`autoattended-orchestrator-spec.md`](./autoattended-orchestrator-spec.md).

.claude/ATT/autoattended-orchestrator-spec.md

@@ -481,8 +481,8 @@ An implementation is conformant if it satisfies ALL of:
       (§3.4); zero N-mini-commit anti-pattern detected.
 - [ ] Chunking discipline enforced: files > 150 lines written via
       `tee -a` (§5.5).
-- [ ] Context Fidelity ladder (§11) is implemented with precedence
-      edge > node > graph > default and the §11.2 token budgets
+- [ ] Context Fidelity ladder (§11A) is implemented with precedence
+      edge > node > graph > default and the §11A.2 token budgets
       treated as guidance (hard cap is `worker.max_brief_tokens`).
 - [ ] `fidelity=truncate` does NOT exempt a worker from the
       `anti-skim-agent-spec.md` §3.3 reading-depth ladder.
@@ -505,13 +505,13 @@ An implementation is conformant if it satisfies ALL of:
 
 ---
 
-## §11 Context Fidelity
+## §11A Context Fidelity
 
 > **Adopted from `attractor-spec.md` §5.4.** This is the one pickup
 > that requires its own section because it changes how briefs are
 > rendered to workers.
 
-### §11.1 Why fidelity matters
+### §11A.1 Why fidelity matters
 
 A 12-worker wave runs the orchestrator's brief through each worker.
 If every worker inherits the full orchestrator context, a wave's
@@ -521,7 +521,7 @@ which is wasteful when bundles are small and well-scoped.
 Fidelity modes let the orchestrator dial how much of its context
 each worker inherits, per-edge / per-node / per-graph.
 
-### §11.2 Four modes + token budgets
+### §11A.2 Four modes + token budgets
 
 | Mode | Token budget (approx.) | When to use |
 |---|---|---|
@@ -534,7 +534,7 @@ each worker inherits, per-edge / per-node / per-graph.
 These budgets are guidance, not hard caps; the hard cap is
 `worker.max_brief_tokens` (default 8000, configurable per §8).
 
-### §11.3 Precedence ladder
+### §11A.3 Precedence ladder
 
 Per attractor §5.4, fidelity is resolved with edge > node > graph >
 default:
@@ -547,7 +547,7 @@ worker.fidelity =
  || "compact"                                                 # built-in default
 ```
 
-### §11.4 Interaction with proof-of-read
+### §11A.4 Interaction with proof-of-read
 
 Fidelity controls what the **orchestrator** passes to the worker. It
 does NOT control what the **worker** reads from disk. A worker on
@@ -565,14 +565,14 @@ In particular:
   summary is NOT a substitute for the read (the same rule that makes
   a compaction summary not a substitute for the JOURNAL file).
 
-### §11.5 Validation rule
+### §11A.5 Validation rule
 
 | Rule | Description | Severity |
 |---|---|---|
 | `WAVE-016 fidelity-budget` | If a worker node declares `fidelity=truncate` AND `tier_1_gates` are required, the orchestrator MUST verify the worker's brief still includes the §6.2 required attributes. | ERROR |
 | `WAVE-017 fidelity-precedence` | The §11.3 precedence is observed; conflicting declarations resolve in the order edge > node > graph > default. | WARNING |
 
-### §11.6 Worked example
+### §11A.6 Worked example
 
 A wave-12 sprint with mixed bundle sizes: