Prompt: Bootstrap Implementation Repository

Use this prompt inside an implementation repository such as anuvax-cms, anuva-python-server, anuva-unity-video-creator, or a future implementation repository.

Bootstrap or refresh this repository as an Anuva implementation repository.

First inspect the repository structure, existing docs, existing AGENTS.md, mkdocs.yml, hooks.py, package/build files, tests, CI configuration, and any generated artifacts. Preserve useful existing content and unrelated user changes.

Required implementation repository structure:
- mkdocs.yml
- hooks.py
- docs/index.md
- docs/stylesheets.css
- docs/bootstrap/BootstrapContext.md
- docs/core/
- docs/state/
- docs/process/
- docs/changes/
- docs/process/ChangeWorkflow.md

Do not create or update AGENTS.md until all of these exist:
- docs/bootstrap/BootstrapContext.md
- docs/process/ChangeWorkflow.md
- docs/core/
- docs/state/
- docs/process/
- docs/changes/

If docs/bootstrap/BootstrapContext.md is missing, stop immediately. Tell me to generate the Bootstrap Context from anuva-main-video-creator and manually copy it to docs/bootstrap/BootstrapContext.md in this repository. Do not generate ChangeWorkflow.md, docs/core, docs/state, or AGENTS.md without BootstrapContext.md.

If BootstrapContext.md exists but required folders or MkDocs files are missing, create the required structure first:
- mkdocs.yml pointing to the docs folder
- hooks.py at the repository root
- docs/index.md
- docs/stylesheets.css
- docs/bootstrap/
- docs/core/index.md
- docs/state/index.md
- docs/process/
- docs/changes/index.md

Then proceed in this order:
1. Create or refresh docs/process/ChangeWorkflow.md using the Implementation Repository Change Workflow structure from anuva-engineering-handbook. Keep the same numbered sections and Standard Prompts.
2. Create or refresh docs/core, docs/state, docs/process, and docs/changes documents based on docs/bootstrap/BootstrapContext.md and the repository contents.
3. Create or refresh AGENTS.md so it references docs/bootstrap/BootstrapContext.md, docs/process/ChangeWorkflow.md, docs/core, docs/state, and repository verification commands.

MkDocs requirements:
- Use Material for MkDocs.
- Set the docs source to the project docs folder.
- Add nav groups for Bootstrap, Core, State, Process, and Changes.
- Use Mermaid-compatible fenced code blocks.
- Include Mermaid diagrams in new docs under docs/core, docs/state, docs/process, and docs/changes.

Do not invent implementation details. Use BootstrapContext.md and current repository contents as source of truth.

After edits, run:
- git diff --check
- mkdocs build --strict, if available
- repository-specific checks when implementation files changed

Summarize:
- files created or updated
- structure verified
- AGENTS.md preconditions satisfied
- docs added or updated
- verification run
- verification that could not be run
- remaining gaps

BootstrapContext Missing Example

If docs/bootstrap/BootstrapContext.md is missing, Codex should stop with a response like:

I cannot continue bootstrapping this implementation repository yet because docs/bootstrap/BootstrapContext.md is missing.

Please generate the Bootstrap Context from anuva-main-video-creator and copy it to:

docs/bootstrap/BootstrapContext.md

After that, I can create docs/process/ChangeWorkflow.md, build the core/state/process/changes docs structure, and then generate AGENTS.md.