Archprint

Check the current change, including uncommitted edits, against the rules this repo adopted with archprint init or generate, and report only the violations the change introduces (file, line, rule, and the evidence for the rule), plus those it fixed and any exceptions allowed with a reason in .archprint/config.json. Use it before finishing a change. Compares with `base` (a branch or commit, default origin/HEAD). Read-only: the files of the base commit are copied to a temporary folder outside the repo and deleted afterwards; it runs no git hooks and changes nothing in the repo. Returns status "skipped" with the reason when the repo has not adopted rules.

Explain one rule from archprint_scan in depth, by its id, label or ESLint name (e.g. AP-002, env-access, no-lib-to-app, "lib !-> app" or archprint/no-lib-to-app): its statement, gate status, adoption (enforce, review, or report-only, as in archprint_scan), observed conformance and confidence floor, and every file that breaks it (scan lists only a few). For the forbidden-import rules (AP-001, AP-002) it also returns each confidence-gate condition with its value and threshold, how to fix a violation, and when not to adopt the rule. A rule the team stated in CLAUDE.md or AGENTS.md and adopted (its id starts with doc-) comes back with the sentence the team wrote, its source line, what it enforces in plain words, its evidence and its exceptions. Read-only.

Verify the rules a repo states in its context files (CLAUDE.md, AGENTS.md, .cursor/rules, ...) against its code. Read those files, then map each rule-like sentence to one template, quoting it exactly. archprint checks the quote is in the file and the mapping matches real files, measures how many files follow or break it, and returns a gap report: enforce now, enforce with a baseline (broken today, with the files), already an archprint rule, check the mapping, or guidance only. Show the report to the user: adopting a rule is their decision. Templates, with globs relative to `path` in ESLint syntax: "forbid-import" (files must not import `targets`, path globs matched on the file an import resolves to, or `packages`, specifier globs, each optionally limited to named `imports` such as {"name": "next/cache", "imports": ["unstable_cache"]}); "forbid-usage" (files must not use a global named in `usage`, such as "fetch", "window" or "process.env"); "forbid-file" (no new file may match `files`); "inferred" (the sentence is a rule archprint_scan lists; `rule` is its id); "none" (no template fits; give the `reason`, e.g. a style rule a standard linter covers). Read-only.

Recommend an architecture rule set for this repo from its evidence and detected stack: what to enforce now, what the code already follows that archprint reports but does not write a rule for yet (reportOnly), what to review before enforcing, and what comparable repos commonly adopt that this repo does not yet. Read-only.

List the architecture rules this TypeScript repo already follows, with the evidence: each rule stated in plain words, whether it is AUTO (clears the confidence gate) or SUGGEST (short of it), its adoption ("enforce": archprint init or generate writes a rule for it, which archprint wire connects to the linter, and public-API rules need dependency-cruiser; "review": held for a human to review, not enforced by default; "report-only": the code follows it but archprint writes no rule for it), how many files conform vs. break it, the files that break it, and the confidence. Read-only. `path` defaults to "." and a monorepo root scans every app.