Refresh the project documentation

Refresh the documentation across this project, resolving inconsistencies between documents and between documentation and the implementation. Deliver usable revisions rather than only an audit list.

Start with the root README, documentation indexes and existing docs directories. Map current guides, reference material, historical records and generated content. Identify the main paths for running, configuring, deploying and troubleshooting the project without asking me to select files. Follow related documents and the source, configuration or script definitions needed to verify them. Do not limit the task to one document or treat historical statements as current facts.

Check conflicting commands, configuration names, paths and procedures; missing prerequisites; missing guide entry points; and broken local links. Prefer actual implementation and verifiable primary sources. A newer timestamp does not establish correctness. Label inaccessible external links unverified. Do not execute installation, deployment, data-changing or deletion commands for verification.

Prioritize errors that cause failed operations or misleading understanding. When one issue spans several documents, propose consistent revisions across all affected passages. Provide locations, original statements, evidence and practical impact, followed by complete replacement passages or an applicable patch. A short document may receive a full revision. Avoid cosmetic rewrites, preserve uncertain facts and do not portray unfinished or unaccepted capabilities as available.

For a large corpus, cover the main usage paths and conflicting documents first, then explicitly list unexamined areas. Do not stop at an arbitrary document count or claim exhaustive coverage. Cross-check the revisions, paths and command names once, then deliver the documentation map, completed revisions and unverified items and stop.

Execution contract:
Start directly. Do not ask me to approve a plan, choose files or fill in a template. Use only this project, this conversation and materials already provided; do not search unrelated projects or private history. Complete what the evidence supports and report missing inputs. If the task is inapplicable, explain why and stop without inventing a result.
Preserve existing files and uncommitted changes. Include complete proposed content in your reply; standalone artifacts may be saved under a new, unused filename. Do not install dependencies, change the environment, commit, push or deploy. Respect access and permission limits and report blocked work. Check your result once, deliver it and stop without asking whether to continue.