setup-govlisted

# Gov install Automates `aitk gov install` by inferring the stack and extras from the current project, then shelling out to the CLI with the resolved arguments. ## Read the catalog Run this first to load the current stacks and rules. Never hardcode names. The catalog is the source of truth. ```bash aitk gov list --json 2>/dev/null ``` ## Detect the stack Read these from the project root in parallel: - `package.json`: dependencies and devDependencies - Root config files: `astro.config.*`, `next.config.*`, `vite.config.*`, `tailwind.config.*`, `tsconfig.json`, `pyproject.toml`, `go.mod`, `Cargo.toml` - `.claude/REQUIREMENTS.md` and `.claude/ARCHITECTURE.md` if present - Directory structure via `ls -1` of the project root and `src/` if present ## Match Match the detected evidence to the catalog: - Pick the closest stack. Match detected runtime or framework against stack names in the catalog. - Identify additional technologies not already covered by the picked stack. For each, find a rule whose `description` or `paths` points at that technology, then add it via `--add`. - Dedupe extras against stack rules. Do not add a rule the stack already pulls in. ## Gap handling If a detected technology has no matching rule, stop and surface the gap. Do not guess. Present three options: 1. Author a new rule in the toolkit at `governance/rules/<domain>/<num>-<name>.md` following `prompts/governance-rules.md`, commit, then re-run install. 2. Install the matching non-<tech> rules