Harmonize Docs

Make the documentation a coherent account of implementation, intent, and remaining work. Give each durable fact and mutable status one canonical owner; link from other reader paths. Prefer pruning stale or duplicate material, while preserving detail needed for understanding, rationale, operations, or decisions.

Scope

With no scope, cover all active repository documentation. An explicit change, path, topic, plan, subsystem, or comparison bounds the run to that seed and its necessary documentation consequences: owning documents, affected plans and status records, navigation, and cross-references. Do not inventory the whole repository for a scoped run.

For changes, use the established change set, or current staged, unstaged, and untracked changes if none is named. If no meaningful change set exists, resolve the boundary rather than substituting unrelated history.