stack-validator

Stack Validator — Priority 2

Modes:

CODING MODE (warn + approval flow — never block execution)

Dev can keep coding. Approval flow starts in background. Format: "⚠️ {library} not approved. Approval flow started — cannot commit until approved."

COMMIT MODE (called by pre-commit hook — hard block)

Unapproved library = commit rejected. No exceptions. Format: "❌ BLOCKED: {library} not in approved stack. Get approval first."

---

Work Type Awareness

Read stack.work_type from manifest before applying any rule:

work_type	Language check	Library check	Infra file check
code	Full (hard block)	Full (hard block)	Skip
infra	Skip for .yaml/.yml/.tf/.hcl/.bicep/.json	Skip (no imports)	Apply
review	Skip entirely	Skip entirely	Skip
mixed	Apply to .py/.ts/.go etc — skip for .yaml/.yml/.tf/.hcl	Apply to code files	Apply
not set	Default to code rules

Infra file extensions — never language-block these extensions: .yaml, .yml, .tf, .hcl, .bicep, .json, .md, .toml, .ini, .env.example

---

Rules:

1. Language check — file language in manifest stack.language?

   • Skip entirely if work_type is review
   • Skip if file extension is .yaml/.yml/.tf/.hcl/.bicep/.json/.md — these are config/infra formats, not subject to language lock
   • Skip if stack.language contains yaml, hcl, or review-only (user declared infra/review stack)
   • Coding: "⚠️ Language not in approved stack. Update manifest."
   • Commit: "❌ Language not in approved stack. Hard block."

2. Library check — import in manifest stack.libraries or stdlib?

   • Skip if work_type is review or infra (no import statements in infra files)
   • Skip for files with infra extensions (see above)
   • Coding: "⚠️ {library} not approved. Starting approval flow."
   • Commit: "❌ {library} not approved. Cannot commit. Approval required."

3. Polars over Pandas

   • Coding: "💡 Pandas detected. Manifest prefers Polars. Consider switching."
   • Commit: "❌ Pandas not in approved stack. Switch to Polars or get approval."