Add a navigation page for project docs

Prefer this project's docs directory, otherwise local materials linked from its README. Inspect names and existing indexes, then select at most twelve relevant entry documents. Skip dependencies, generated files and large archives.

Organize the index around questions such as running the project, changing configuration, deployment and troubleshooting. Each entry must say what it answers and provide the source path. Summarize only content actually read.

Include at most three evidenced duplicates, contradictions or missing entry points without merging uncertain conclusions. Deliver complete Markdown, verify every local target exists and state coverage. With few materials, make a small index rather than empty categories. Do not move the originals.

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.