Pin messcript and define the production TypeScript gate

[jonbaldie]

Parent

#27 — Bring production TypeScript to messcript's idiomatic ruleset

What to build

A maintainer can run the same deterministic messcript idiomatic TypeScript policy against any named production unit or the complete production surface, with meaningful failure status and no runtime coupling to the Deno service.

Acceptance criteria

• A pinned messcript revision or released artifact has an explicit, reproducible acquisition, build, and execution path.
• The production scope covers configuration, router, middleware, rate limiter, Queue Manager, Persist Engine, HTTP handler, and the executable entrypoint, while excluding tests, mutation infrastructure, documentation, CI configuration, generated output, and development tooling.
• Documented per-unit and aggregate commands use the recommended typescript policy, retain CyclomaticComplexity and NPathComplexity, and use messcript's default thresholds.
• Findings and processing errors produce the normal non-zero exit status; suppressions, ignored violations, and broad exclusions are not used.

Blocked by

• None — can start immediately.