Add code compliance audit template (spec+design → code)

[Alan-Jowett]

Summary

Add an \�udit-code-compliance\ template that audits source code against requirements and design documents. Answers: does the code implement what was specified?

Context

PR #35 shipped the \�udit-traceability\ template for cross-document specification drift (D1–D7). The \specification-drift\ taxonomy reserves D8–D10 for code compliance drift types. This is Phase 2 of the specification integrity roadmap.

Scope

New components needed:

• Template: \�udit-code-compliance\ — consumes requirements-document + design-document (optional) + source code; produces investigation-report
• Protocol: \code-compliance-audit\ (reasoning) — phased methodology for mapping spec claims to code behavior
• Taxonomy extension: Define D8–D10 labels in \specification-drift\ taxonomy (e.g., D8_UNIMPLEMENTED_REQUIREMENT, D9_UNDOCUMENTED_BEHAVIOR, D10_CONSTRAINT_VIOLATION_IN_CODE)

Reused components:

• \specification-analyst\ persona
• \investigation-report\ format
• \�nti-hallucination\ + \self-verification\ guardrails

Drift types to define

Label	Description
D8	Requirement exists in spec but has no implementation in code
D9	Code implements behavior not specified in any requirement
D10	Code violates a stated constraint (performance, security, etc.)

Acceptance criteria

• Template, protocol, and taxonomy extension created
• Manifest updated
• \ ests/validate-manifest.py\ passes
• Case study or scenario added to docs