eq-frontend-standards

Measure per-rule violation counts first with measure-rules.mjs, then set zero-violation rules to error immediately. Repos with roughly 300 or fewer remaining violations get one AI-assisted fix PR; larger debt stays on ESLint with a suppressions baseline until oxlint supports suppressions.

Run init-greenfield.mjs, which lands oxfmt formatting config, oxlint fast and strict configs, git hooks, CI gates, and agent policy files without overwriting existing files. Then install dependencies and run format, lint, typecheck, and build to verify.

Yes, but only when run with the --type-aware flag and the oxlint-tsgolint devDependency; otherwise type-aware rules are silently skipped with exit 0. The strict config pins all 23 type-aware rules by name and CI asserts on the rule count.

Without --force, the .tsbuildinfo cache goes stale and produces phantom errors and false passes. A hook that emits false failures gets bypassed with --no-verify, so correctness outweighs the few seconds --force costs.

Parking is allowed only inside a fix branch for rules whose fixes are genuinely risky to batch, recorded in a marked PARKED block with the measured count and date. Correctness rules like no-floating-promises are never parked because they close the bug class the migration exists to fix.

Yes, adapt-hosts.mjs generates each host's own hook configuration from the .claude/ source and reports what each host cannot enforce. Hosts without blocking hooks, like Zed, rely on pattern-based denials plus CI as the real gate.