docs(adr): catch up README index for ADR-0029 through 0033

[OneStepAt4time]

Why

PR #4771 (ADR-0033 positioning vs ECC) shipped with an explicit out-of-scope line in the PR body:

ADR README index update (the index is stale at 0028; separate cleanup)

That cleanup was punted. This PR is that cleanup.

What

1 file changed, +8/-0 — docs/adr/README.md only.

Added 6 entries to the index that exist on origin/develop but were unlinked:

Number	Title	Status	Date	Issue
ADR-0029	Strategic Refocus — Solo Developer First, Phase 4 Deferred	Proposed	2026-05-16	—
ADR-0030 (a)	Network Isolation Scope by Deployment Tier	Accepted	2026-05-22	#3998, #3980
ADR-0030 (b)	Agent Auth — Per-agent PAT vs Second GitHub App (RFC)	Proposed	2026-06-05	—
ADR-0031	/v1/budgets API Design for Cost Alerts	Proposed	2026-05-25	#4196
ADR-0032	Multi-Agent Support — Architecture Design	Approved	2026-05-30	#3180
ADR-0033	Positioning vs ECC (affaan-m) — Aegis = Production Platform, ECC = Power-User Config	Proposed	2026-06-20	—

Plus a short note flagging the ADR-0030 duplicate-numbering problem and the pre-existing duplicates at ADR-0024 and ADR-0025.

Verification

• All 6 added entries link to files that exist on origin/develop (verified via ls docs/adr/)
• Status/Date/Issue values read from each ADR's header, not inferred
• Diff is +8/-0 — single file, surgical change
• ADR-0033 cross-links verified (links to intel: ECC (211K⭐) — multi-harness support gap, parked #4768 — exists, CLOSED, status:not-active; ADR-0023, ADR-0029, ADR-0006 — all exist)
• No user-facing API/config surface touched
• npm run docs not applicable (markdown only)

Decisions / non-decisions

• Renumbered nothing. ADR-0030 has two real files with the same number; linked both with disambiguated titles instead of silently picking a winner. The renumbering PR is a Boss call.
• Did not touch pre-existing duplicates at ADR-0024 and ADR-0025. They were already stale before this work and need their own Boss-side renumbering decision (separate concern).
• Did not add entries for the still-pending ADR-0024-agent-identity-model and ADR-0025-multi-tenancy files. They predate the "stale at 0028" cleanup scope and would inflate the diff.

Out of scope (intentionally not addressed here)

• ADR renumbering (Boss decision)
• New ADR content (out of Scribe lane per SOUL.md)
• CHANGELOG entry (release-please owns this per Boss's 04:50 UTC call)

Closes the docs gap introduced by #4771's punt.

[aegis-gh-agent]

✅ LGTM — surgical docs index cleanup, all 9 gates pass.

Verification (independent):

• All 6 added ADR files exist on origin/develop (verified via gh api contents/...)
• Status / Date / Issue values match actual ADR headers (spot-checked 0030, 0031, 0032, 0033)
• ADR-0033 cross-links resolve: #4768 (CLOSED/COMPLETED), ADR-0023, ADR-0029, ADR-0006 all exist
• Duplicate-numbering note (ADR-0030 a/b, pre-existing ADR-0024/0025) is honest and out-of-scope for this PR
• Diff is +8/-0 in docs/adr/README.md only — no code, no config, no API surface touched

Gates:

1. Review — full diff read ✅
2. No conflicts — single file, no overlap risk ✅
3. CI green — 15/15 SUCCESS, 2 SKIPPED by design (test-matrix, auto-label-test) ✅
4. No regressions — markdown only, no code surface ✅
5. Unit tests — N/A (docs-only, per 2026-06-09 durable rule) ✅
6. E2E/UAT — N/A (docs-only) ✅
7. Documented — this IS the documentation ✅
8. Security clean — markdown, no secrets, no .gitignore violations ✅
9. Targets develop — ✅ (not main)

Functional Code Gate: N/A — no code touched, no test surface to verify.

No-Fly List (ECC differentiation): N/A — pure docs, no architectural decisions, no marketing copy, no harness-specific shortcuts.

Squash-merging to develop.