Skip to content

Preflight check registry #562

Description

@flyingrobots

Migrated from a local Wesley Method backlog card after adopting METHOD v2.1.0 tracker doctrine.

  • Source path: docs/method/backlog/bad-code/RUNTIME_preflight-check-registry.md
  • Original filesystem lane: bad-code
  • Canonical Method lane label: lane:bad-code
  • Legend: RUNTIME
  • Migration issue: Migrate Wesley Method backlog to GitHub Issues #548
  • Migrated on: 2026-06-04

Original Local Backlog Card

Preflight check registry

  • Lane: bad-code
  • Legend: RUNTIME

Why now

scripts/preflight.mjs uses global mutable ok and failures state plus a
long numbered list of inline checks. The current behavior works, but the shape
makes checks harder to test independently and easier to edit inconsistently.

Hill

Repository preflight is a registry of named checks that return failure messages,
while pnpm run preflight preserves its existing user-facing behavior.

Done looks like

  • checks are represented as named functions or objects
  • each check returns an array of failure messages instead of mutating global
    state
  • process-running checks share one helper
  • smoke tests cover at least one passing and one failing check
  • current checks remain intact: docs links, docs truth, forbidden literals, docs
    CLI commands, pnpm version, dependency-cruiser, core purity, package hygiene,
    license, progress weights, and docs whitespace

Repo Evidence

  • scripts/preflight.mjs
  • package.json
  • docs/audit/2026-05-05_ship-readiness.md

Activity

  1. added
    triage:bad-codeDebt intake that still needs scheduling, closure, or a repo move
    legend:RUNTIMERuntime/tooling/host/operator flow work
    on Jun 4, 2026
  2. coderabbitai commented on Jun 4, 2026

    @coderabbitai
    🔗 Related PRs

    #270 - feat(host-browser): browser host + browser/deno/bun smokes [merged]
    #504 - Compile runtime optic artifacts [merged]
    #521 - Add Rust IR performance baseline [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    legend:RUNTIMERuntime/tooling/host/operator flow worktriage:bad-codeDebt intake that still needs scheduling, closure, or a repo move

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions