Active Plan: Mintlify Docs Maintenance

Status

This file is a lightweight maintenance plan for the current Mintlify docs structure.

It is non-normative and does not define product behavior. Normative behavior remains only in:

docs/mint.json for navigation structure (read navigation as the current page list; these are Mintlify page IDs, not expected local docs/reference/* files)
docs/specs/page-ownership.md for the page-to-anchor traceability map
docs/specs/prd.md and docs/specs/json-rpc-contract.md for normative anchors

Use docs/specs/page-ownership.md as the page-to-anchor map; do not maintain a parallel mapping in this file.
When docs/mint.json or normative docs change, update affected rows in page-ownership.md in the same PR.
Keep the Normative anchors (required) field in page-ownership.md current for each affected page in the same PR.

This file tracks structure/process only. Do not duplicate tuple-level semantics, per-page ownership, or verification matrices here.

Treat docs/mint.json as the nav source of truth (groups and page IDs).
Treat docs/specs/page-ownership.md as the only per-page ledger for owners, authoritative sources, normative anchors, and verification timestamps.
Keep this plan focused on reconciliation workflow and update triggers, not page-level inventories.

When docs/mint.json adds/removes/renames groups or pages, reconcile this plan and docs/specs/page-ownership.md in the same PR.
When docs/specs/prd.md or docs/specs/json-rpc-contract.md changes semantics, update affected Mintlify pages and reconcile this plan plus docs/specs/page-ownership.md in the same PR.
Keep this plan structure-level and routing-level only; tuple-level content and verification ledgers stay in docs/specs/page-ownership.md.
Internal support docs under docs/specs/internal/* may guide edits but are non-normative and must not override normative sources.