ddw-validate-archlisted

# Skill: /ddw-validate-arch ## Description Validates that the code follows the project's architecture decisions and conventions. It is an **advisory check, not a gate**: `transition-graph.json` carries no `arch` condition on any edge, so nothing here refuses a transition — it reports, and the orchestrator decides what to do. Naming it a gate would be the exact failure this pipeline exists to avoid: calling something a lock when it is a sign. Produces disambiguation questions when a finding needs the user's context. ## Inputs - The modified files (default) or the whole project (if specified) - The project's architecture conventions (`AGENTS.md`) > **This skill has no rules of its own.** Its criteria come from the "Architecture conventions" > section of the target project's `AGENTS.md`. If that section is empty, say so and report PASSED > with a warning: there is nothing to validate against, and inventing conventions the project never > declared is worse than validating nothing. The patterns below are a *starting* checklist to adapt, > not a fixed catalog. (This is why `validate-arch` has no F-/W- IDs in > `.ddw/rules/validation-rules.instructions.md` — it is an operational gate, not an artifact > validator.) ## Execution Protocol 1. Identify which files to analyze: - First run in the phase: the whole relevant codebase. - Post-block: only the files the block modified. 2. For each file, check: - **Module structure:** every file in its correct layer. - **Separati