Enforce the aggregate production quality gate in CI

[jonbaldie]

Parent

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

What to build

Every applicable CI run enforces a clean messcript report for the complete production surface, with the Queue Service's existing Deno tests, mutation checks, and real server behavior still green.

Acceptance criteria

• The aggregate command covers all eight named production units, including the executable entrypoint, reports both CyclomaticComplexity and NPathComplexity rule identities, and returns zero findings.
• A Node-compatible CI job runs the pinned aggregate command and fails on findings or processing errors; no suppressions, ignored violations, or report-only success path is used.
• The existing Deno 2.7.6 test and mutation jobs remain unchanged in runtime and continue to pass.
• The complete Deno test suite, existing mutation checks, and a real startup/enqueue/FIFO-dequeue/shutdown smoke test pass after the aggregate gate is enabled.

Blocked by

• Pin messcript and define the production TypeScript gate #28 — Pin messcript and define the production TypeScript gate.
• Clear the configuration quality gate #29 — Clear the configuration quality gate.
• Clear the router quality gate #30 — Clear the router quality gate.
• Clear the Queue Manager quality gate #31 — Clear the Queue Manager quality gate.
• Clear the rate limiter quality gate #32 — Clear the rate limiter quality gate.
• Clear the authentication and middleware quality gate #33 — Clear the authentication and middleware quality gate.
• Clear the Persist Engine quality gate #34 — Clear the Persist Engine quality gate.
• Clear the HTTP handler quality gate #35 — Clear the HTTP handler quality gate.
• Clear the executable startup and shutdown quality gate #36 — Clear the executable startup and shutdown quality gate.