Add architecture beliefs to manifesto and enhance software-architecture skill

- Add Architecture Beliefs section to manifesto with outcome-focused beliefs:
  auditability, business language in code, independent evolution, explicit over implicit
- Create software-architecture.md as human-readable documentation
- Enhance software-architecture skill with beliefs→patterns mapping (DDD, Event
  Sourcing, event-driven communication) and auto-trigger description
- Update work-issue command to reference skill and check project architecture
- Update issue-worker agent with software-architecture skill
- Add Architecture section template to vision-management skill

The skill is now auto-triggered when implementing, reviewing, or planning
architectural work. Project-level architecture choices go in vision.md.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CLAUDE.md

@@ -16,6 +16,7 @@ make install
 | Component | Purpose |
 |-----------|---------|
 | `manifesto.md` | Organization vision, personas, beliefs, principles |
+| `software-architecture.md` | Architectural patterns (human docs, mirrored in skill) |
 | `learnings/` | Historical record and governance |
 | `commands/` | AI workflow entry points (/work-issue, /manifesto, etc.) |
 | `skills/` | Tool and practice knowledge |
@@ -27,9 +28,10 @@ make install
 
 ```
 architecture/
-├── manifesto.md    # Organization vision and beliefs
-├── learnings/      # Captured learnings and governance
-├── commands/       # Slash commands (/work-issue, /dashboard)
+├── manifesto.md              # Organization vision and beliefs
+├── software-architecture.md  # Patterns linked to beliefs (DDD, ES)
+├── learnings/                # Captured learnings and governance
+├── commands/                 # Slash commands (/work-issue, /dashboard)
 ├── skills/         # Knowledge modules (auto-triggered)
 ├── agents/         # Focused subtask handlers (isolated context)
 ├── scripts/        # Hook scripts (pre-commit, token loading)