running-acceptance-probelisted

# Running an Acceptance Probe A probe is the smoke-test command that demonstrates a task's wiring works end-to-end — distinct from unit/integration tests, which assert behavior in isolation. The probe is the most important reliability artifact in Shipyard 2.0: it is the difference between "tests pass against a stub" and "the thing actually works." ## What Counts as an Acceptance Probe A valid probe is a **single shell command** that: 1. **Exits 0 on success.** Non-zero exit means the wiring failed. 2. **Produces observable output** that demonstrates the change worked end-to-end. Empty output passing is rare and suspicious. 3. **Runs from a clean state** — no prerequisite session-only setup. 4. **Completes in a bounded time** — typically <60s, hard cap 5m. 5. **Is deterministic enough to run twice and get the same exit code.** Examples of good probes (per task type): | Task type | Probe shape | |---|---| | New API endpoint | `curl -fsS -X POST localhost:3000/api/users -d '{"name":"x"}' \| jq -e .id` | | New CLI subcommand | `node bin/mytool.mjs <new-subcommand> --help \| grep -q "<expected text>"` | | Library function | `node -e 'const m = require("./dist/index.js"); if (!m.newFn) process.exit(1); console.log(m.newFn(42))'` | | Migration | `psql -c "SELECT column_name FROM information_schema.columns WHERE table_name='users' AND column_name='new_col'" \| grep -q new_col` | | Refactor (no behavior change) | `npm run build && npm test -- --testPathPattern=touched-module` |