Task · SKT-0104

Add a one-shot validate mode for blueprint sets

Description

Validation and cardinality preview currently only run inside a live instance (POST /control/blueprints/validate builds a throwaway dry runner in-process, unbounded). Add a one-shot validate mode (flag name to match the existing -preflight style): load the selected set (BLUEPRINT_NAMES plus sources), run ValidateSet and the cardinality projection, print a machine-readable result and exit non-zero on failure. The credentials preflight mode already exists.

Acceptance Criteria

Definition of Done

Implementation Plan

Isolated candidate with frozen ownership; acceptance reproduction, focused checks and just check; independent review before root landing. HA seam design is independently challenged and frozen first.

Implementation Notes

loop1: implementation attempts 1, review-repair rounds 0 (identity objection resolved by native edit replay, no candidate change). Landd61ea18359738eddc93993fdb7be4faa94acdf60; composed gate green exactSHA. Final integrated CI run37696196429 atf3d701a1a4500eb2944a0a354c53a9c641fed371 green; earlierd61 run37693078591 cancelled, not pass. Real CLI shipped set JSON3537series, collision/schema errors nonzero, no network/state writes, independent review ACCEPT. Generation not applicable; no live renderer changes; composed inventory/fidelity green. Routine aggregate review scheduled after last routine land.

Final Summary

Offline -validate loads selected sets and reports JSON diagnostics/per-blueprint single-cycle cardinality including native OTLP metrics. Real CLI and read-only staged-source tests proved behavior. Evidence /tmp/C104-evidence/acceptance-report.json and /tmp/C104-composed-d61ea18/gate.log; contemporaneous native tool chronology binds exact candidate hashes.

View the source file on GitHub