generate-architecture

When to use

Use when ../ARCHITECTURE.md is missing or when the user wants to regenerate it after changing the repo architecture mix.

Workflow

1. If ../ARCHITECTURE.md is missing, ask the user which templates from ./.architecture/ apply unless they already selected them. The existence of project context does not select an architecture.
2. Support multiple templates for mixed-stack repositories.
3. Record task-specific selection evidence under <project-root>/.hephaera/.cache/tasks/<task>/ when a task exists; keep the authoritative contract at the project root.
4. Generate ../ARCHITECTURE.md from the selected templates using concise read directives by default (for example Read \./.hephaera/.architecture/DOTNET.md` instructions`) to avoid oversized files.
5. Use inline mode only when the user explicitly asks for fully embedded template content.
6. Treat ../ARCHITECTURE.md as the authoritative architecture contract afterward.

Commands

• ./commands/generate-architecture.sh "<TEMPLATE1>" ["TEMPLATE2" ...]
• ./commands/generate-architecture.sh --inline "<TEMPLATE1>" ["TEMPLATE2" ...]