Current Test Command Inventory

Status: Current. This inventory implements roadmap slice 0, "Inventory and naming". It maps existing CI-relevant test-like package scripts to package or surface, lane, scope, owner, artifact name, and pipeline placement. Proposed future bundles remain in Pipeline Integration and are not treated as current commands here.

**Pipeline placement is reconciled against actual workflow invocation data** (.github/workflows/ci.yml and .github/workflows/publish.yml read in full, plus the reusable workflows they call: release-artifact-verifier.yml and live-stack-published.yml). Where a script exists but no workflow invokes it, the placement column says so explicitly rather than naming an aspirational lane — an uninvoked gate is a gap, and the remediation program was caused by exactly that kind of paper coverage.

Root release and package-integrity gates (added by the remediation program)

These root scripts are the guardrails FIX-011/FIX-012 added. Their placement is stated exactly as the workflows invoke them.

Naming Rules

• **Check labels** use testing / <lane> <scope> for future reusable jobs and keep existing workflow job names until behavior changes.
• **Artifacts** use stable, lowercase paths: test-logs/<package>-<script>.log, coverage/<package>-<script>, e2e/<package>-<script>, docs-qa/<package>-<script>.log, or release-logs/<package>-<script>.log.
• **Current commands** are package scripts that already exist in package.json files under the repo root or packages/**; dev-only *:watch commands are intentionally excluded from CI artifact naming.
• **No-model** means the command must not require provider credentials. Release-gate commands can still be no-model when they verify packaging, metadata, or static release contracts.
• **Model-backed** is reserved for commands that require real provider credentials or installed live harnesses; no current package script in this inventory is promoted as model-backed.

Inventory Summary

Current Command Map

Workflow Touchpoints

Current workflows already call many of these commands. Slice 0 does not change workflow behavior; it gives follow-up slices a stable naming target for comments, reusable workflows, and uploaded artifacts.

Gaps For Follow-Up Slices

Scripts that exist but no workflow invokes

Reconciling this inventory against actual workflow invocation data surfaced gates that exist as package scripts but are not wired into ci.yml or publish.yml. Each is a real coverage gap, not a naming gap:

• guard:packages — the composed fast package-integrity gate. Local/manual only.
• test:binary-renames — the check that proves a compatibility bin points at an emitted path (the FIX-004 failure mode). Local/manual only.
• test:package-renames — same class, local/manual only.
• test:packaged-surface-parity --workspace=@a5c-ai/extensions-adapter — the tasks-adapter equivalent is wired into both workflows; the extensions-adapter one is not.

Wiring these is follow-up work; this document records the current true state rather than the intended one.

Closed coverage gaps

These were listed above as unwired; they are now wired, and the row for each command in the tables reflects the current lanes.

• test:babysitter-metapackage — was ci.yml only. It now also runs in publish.yml's validate_core (step Metapackage shim tests (packed exit-code propagation), log core-logs/babysitter-metapackage-tests.log), so the publication path re-checks FIX-007 exit-code propagation against the packed metapackage.
• verify_release_artifacts — was in no publish job's needs, so it reported rather than gated. publish.yml's prepare_staging_publish now needs it (in both needs: and its if:, which uses !cancelled()), and every publish_staging_* job hangs off that job. The tag-recovery workflow publish-packages-from-tag.yml did not call the verifier at all; it now has its own verify_release_artifacts job, gated on should_publish, passing allow_known_failures: 'false' and the release tag as ref, with publish_non_plugin_packages depending on it.
• The FIX-009 PTY suites (packages/adapters/core/tests/pty.test.ts and tests/pty-consumer.packaged.test.ts) ran only inside publish.yml's validate_mux. ci.yml now runs the same suite at PR time under the greppable step name adapters-core PTY contract (@a5c-ai/comm-adapter suite) (log test-logs/adapters-core-pty-contract.log).

Other gaps

• Current package scripts are mostly no-model package checks; the implemented model-backed live-stack lane is selected by .github/workflows/publish.yml and exercised through test:e2e:live-stack:pipeline.
• Artifact naming is partially enforced in publish.yml for validation logs and live-stack artifacts; remaining package-local logs should converge on the inventory names when touched.
• Some root scripts aggregate package-local scripts. Follow-up workflow comments should name both the aggregate and package-local owner when they upload one shared log.
• The no-model stack matrix now covers transport-adapter-backed agent launches; the next missing slice is broadening runtime-hook assertions from hook bridge evidence into native agent lifecycle hook emission where each harness supports it.