Skip to content

quad-cli gate: add a periodic live four-CLI dogfood check (smoke:quad) #15

Description

@drvoss

Follow-up to #9. Tracks the part of #9's close criterion 3 that is not satisfied by the transport fix in #14.

#14 added 19 regression tests that really spawn processes, using stub CLIs. Those cover launcher resolution
(.exe / .cmd / .ps1), synchronous EINVAL, ENAMETOOLONG transport fallback, envelope unwrapping,
process-tree termination and the failure taxonomy. They do not cover drift in the real, independently
updated CLIs — a vendor changing a flag, an output envelope, or a default mode would not fail any test.

Remaining work:

  • npm run smoke:quad — a live, non-mock preflight that runs the declared reviewer set against a tiny fixed
    diff and fails if a declared reviewer is absent, unauthenticated or non-compliant; plus a
    smoke:quad:available variant that probes whatever is installed. Not part of npm test, not in CI
    (runners have no CLIs installed).
  • Emit a machine-readable artifact per run: orchestrator commit, OS and Node version, resolved CLI paths and
    launcher kinds, CLI versions, per-tool result and duration, schema outcome.
  • A transport-integrity nonce in the production protocol, so "schema-valid" and "received the whole prompt"
    stay distinguishable outside of ad-hoc investigations.
  • Revisit --min-reviewers (currently 2) and the supported-reviewer contract now that four reviewers actually
    run.

Measurement context for all of the above is in #9 and #14.

Activity

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions