gate-wiring

Gate: Wiring

Goal

Ensure the codebase is properly connected — no dead code, no orphaned files, no architecture violations. Code that compiles and passes tests can still be wired incorrectly.

Inputs

• {projectArtifactsRoot}/config.json -- architecture layers, project structure
• {repoStateRoot}/work/{selectedWork.id}/workflow.json -- selected work unit
• Changed files (via git diff)

Outputs

• Evidence file at {workDir}/evidence/wiring-report.md
• Gate status in the selected work's workflow.json
• Findings with specific file:line references and remediation

Constraints

Scope (MEDIUM freedom):

• Focus on changed files and their immediate dependents.
• Use git diff --name-only against main branch.

Analysis (HIGH freedom):

• Delegate to specwright-architect for structural analysis.
• The architect checks:
  • Unused exports: Public functions/types exported but never imported.
  • Orphaned files: Files not imported by anything in the dependency graph.
  • Layer violations: Imports crossing architecture layer boundaries (e.g., UI importing directly from database layer). Layers from config.json architecture.layers.
  • Circular dependencies: Import cycles that may cause runtime issues.
• Use real tooling when available (e.g., madge, knip, ts-prune).
• Fall back to LLM analysis when tools aren't configured.

Verdict (LOW freedom):

• Follow protocols/evidence.md#verdict-rendering.
• WARN severity for most findings (wiring issues rarely block functionality).
• BLOCK only for circular dependencies in changed files.
• This gate is advisory — it helps clean up, not block shipping.

Cross-unit integration (MEDIUM freedom, multi-unit only):

When verifying the final unit of a multi-unit design, run additional cross-unit wiring checks against the full feature diff. This catches integration issues invisible to per-unit analysis: missing cross-unit imports, interface mismatches, disconnected entry points.