docs: point Active 6-Week Execution Plan links at live 2026-03-05 plan

[scarmani]

Source

The P2 docs archive pass (feature p2-tree-and-archive) repointed the live
"Active 6-Week Execution Plan" links to the archived
docs/archive/status/2026-02-25-EXECUTION_NEXT_6_WEEKS.md instead of the live
docs/status/EXECUTION_NEXT_6_WEEKS_2026-03-05.md. The p2-docs scrutiny gate
flagged this as BLOCKING: the live short-horizon plan still declares itself
canonical, yet the index/readme sent readers to the archived predecessor.

Change (Tier 0, docs-only)

• docs/INDEX.md — repoint the "Active 6-Week Execution Plan" link to the live
  status/EXECUTION_NEXT_6_WEEKS_2026-03-05.md.
• docs/README.md — repoint the EXECUTION_NEXT_6_WEEKS ("Active short-horizon
  plan") link to the live ./status/EXECUTION_NEXT_6_WEEKS_2026-03-05.md.
• docs-site/docs/contributing/documentation-index.md — regenerated via
  doc_stats.py --write + sync-docs.js so the mirror matches.

The 2026-02-25 file stays archived; it is no longer linked as the active plan.

Validation (run on this branch's worktree)

• python3 scripts/check_docs_consistency.py → PASS (broken links, live→archive
  refs, metric drift, tier contradictions all PASS).
• python3 scripts/ci/check_docs_links.py → OK all internal markdown links and anchors resolve.
• rg sweep: no live (non-archive) doc links the "Active … Execution Plan" to
  2026-02-25-EXECUTION_NEXT_6_WEEKS.md (only docs-site/scripts/sync-docs.js
  still references the archive basename — see Deferred below).
• make lint → All checks passed!
• make test-smoke → Core/Server/Memory imports OK, Smoke tests passed.

Deferred (NOT in this PR — returned to orchestrator)

The two remaining scrutiny items cannot land cleanly right now because their
target docs-site mirror pages are path-frozen by open (conflicting/stale) PRs,
and the docs-build.yml sync gate fails on any un-committed mirror drift:

• Item 2 (docs-site/scripts/sync-docs.js DOC_MAP source → live plan +
  regenerate contributing/execution-next-6-weeks-2026-03-05.md): the exec
  mirror page is frozen by fix(ci): clear base security and smoke blockers #8461.
• Item 3 (docs/status/DOCUMENTATION_HYGIENE_AND_GAP_REGISTER.md wording +
  mirror): the hygiene mirror page is frozen by chore(deps): update audit-vulnerable Python locks #8460 and fix(ci): clear base security and smoke blockers #8461.

Risks

Docs-only; no code or API surface touched. Low risk.

[scarmani]

BLOCKED — do not merge as-is. Returning to orchestrator.

This PR's docs/INDEX.md + docs/README.md edits (repoint the "Active 6-Week
Execution Plan" links to the live status/EXECUTION_NEXT_6_WEEKS_2026-03-05.md)
are correct and were confirmed correct by both reviewers. But the required
regeneration of the docs-site mirror (docs-build.yml fails on any un-synced
drift) produces a broken raw link in docs-site/docs/contributing/documentation-index.md
that also fails tests/scripts/test_docs_site_sync_links.py::test_documentation_index_rewrites_status_and_planning_links.

The only clean fix is to change the docs-site/scripts/sync-docs.js DOC_MAP key
archive/status/2026-02-25-EXECUTION_NEXT_6_WEEKS.md → status/EXECUTION_NEXT_6_WEEKS_2026-03-05.md
(item 2), which regenerates docs-site/docs/contributing/execution-next-6-weeks-2026-03-05.md
from the archive (2026-02-25) content to the live (2026-03-22) content — a file
path-frozen by #8461. Item 3's hygiene mirror is frozen by #8460 + #8461.

Items 1+2 are inseparable, and items 2+3 require touching mirror pages owned by
the stale/conflicting PRs #8460 and #8461. Recommendation: resolve/close those
two PRs (or lift the freeze), then land items 1+2+3 in one Tier-1 PR. Details in
the mission library note.

[scarmani]

Claude independent model review

Reviewer: claude (anthropic) — independent adversarial model review via the Aragora Claude reviewer, grounded on the exact PR head.
Head: f72daaf (f72daaf), committed 2026-06-21T15:08:28Z.
PR: #8516.
Model family: claude

Verdict: PASS

All changes are documentation-only and verified internally consistent:

• sync-docs.js DOC_MAP key status/EXECUTION_NEXT_6_WEEKS_2026-03-05.md resolves under SOURCE_DIR (docs/) to an existing file — confirmed present.
• docs/INDEX.md and docs/README.md links now point at status/EXECUTION_NEXT_6_WEEKS_2026-03-05.md, which exists; no broken links.
• The docs-site copy body is byte-identical to the source plan (only Docusaurus frontmatter prepended), so no sync drift.
• No dangling references to the old archive/status/2026-02-25-EXECUTION_NEXT_6_WEEKS.md path remain (the archive file itself is correctly left in place).
• Hygiene-register text edits (docs-site + docs/status) are consistent with each other and now name the live plan path.

No correctness, security, or regression risk in this change set.

No findings.

dogfood: yes

[scarmani]

Gemini independent model review

Reviewer: gemini (google) — independent adversarial model review via Antigravity CLI harness, grounded on the exact PR head.
Head: f72daaf (f72daaf), committed 2026-06-21T15:08:28Z.
PR: #8516.
Model family: gemini

Verdict: PASS

• [P3] docs-site/docs/contributing/execution-next-6-weeks-2026-03-05.md (under CI/Gate Commands): Commands 1–6 reference python instead of python3, which is inconsistent with repository standards (e.g. AGENTS.md) and will cause execution failures in environments where python maps to Python 2 or is unregistered.

dogfood: yes