aif-rules-check

# Rules Compliance Gate Run a standalone read-only rules gate for project rules. This command checks rule compliance only; it does not replace `$aif-review` or `$aif-verify`. ## Step 0: Load Contract - Read `references/RULES-CHECK-CONTRACT.md` first. - Treat it as the canonical source for verdict semantics and report structure. - If examples in this file drift from the reference, follow the reference. ## Step 1: Load Config **FIRST:** Read `.ai-factory/config.yaml` if it exists to resolve: - `paths.rules_file` - `paths.rules` - `paths.plan` - `paths.plans` - `language.ui` - `git.enabled` - `git.base_branch` - `rules.base` - named `rules.<area>` entries - `workflow.plan_id_format` (default: `slug`) — used by the optional branch-based plan-context lookup in Step 2.3. Active values: `slug` and `sequential`. When `sequential`, the resolver globs `<paths.plans>/[0-9]{4}_<branch_stem>.md` first and falls back to `<paths.plans>/<branch_stem>.md` only if no numbered match is found. `timestamp` and `uuid` are **reserved values** and currently behave like `slug`. Treat any unknown value as `slug`. If config is missing or partial, use defaults: - `paths.rules_file`: `.ai-factory/RULES.md` - `paths.rules`: `.ai-factory/rules/` - `paths.plan`: `.ai-factory/PLAN.md` - `paths.plans`: `.ai-factory/plans/` - `git.enabled`: `true` - `git.base_branch`: detect the repo default branch from git metadata; fall back to `main` only when detection is unavailable - `rules.base`: `.ai-fa...