AgentFlow SDLC v1 is publish-grade only when tests, executable evals, npm packaging, native harness manifests, and structural harness settings merge all validate. This document defines the maintained release gate. Passing it validates the package payload but does not publish the npm package; npm publication remains a separate explicit action.
Required package fields:
private: falsefilesrepositoryhomepagebugsbin.agentflow-sdlclicense
Run:
node scripts/validate-npm-package.mjs
npm pack --dry-runvalidate-npm-package checks npm pack --dry-run --json against manifests/npm-package.json.
Run:
agentflow-sdlc plugins validate --harness all --json
agentflow-sdlc plugins build --harness all --dry-runCanonical manifests live in:
adapters/claude-code/manifest.jsonadapters/agy/manifest.jsonadapters/codex/manifest.jsonadapters/pi/manifest.json
Generated plugin files belong in harness folders only and are not canonical source.
Run:
agentflow-sdlc settings merge --harness all --dry-run
agentflow-sdlc settings status --harness all --jsonThe merge engine preserves project-owned keys and only injects the agentflowSdlc managed object from manifests/harness-settings.json.
Cockpit is optional at runtime and first-class in the product artifact. It must be packaged, documented, and smoke-tested, but default install must not start a server, require OAuth, or enable write actions.
Run:
AGENTFLOW_REPOSITORIES=owner/repo agentflow-sdlc cockpit doctor --json
node scripts/cockpit-smoke.mjspnpm test
pnpm test:evals
node scripts/sdlc-sandbox-smoke.mjs
node scripts/cockpit-smoke.mjs
node scripts/validate-npm-package.mjs
agentflow-sdlc plugins validate --harness all --json
agentflow-sdlc settings merge --harness all --dry-runThe canonical package script runs the same core gate:
pnpm validate:release