| name | recover-and-release-project |
| description | Use when context was compacted or forgotten, settled questions repeat, canonical sources disagree, production readiness is requested, or an exact release candidate needs validation. |
Recover and Release Project
Recover from canonical evidence before mutation, and release only the exact candidate that both technical checks and the user validated.
- Run
stackcord status --json. If questions repeat, context was compacted, or sources disagree, stop mutation and run stackcord context audit --json.
- Reconstruct approved product meaning, service contracts, external UI source authority, the exact UI baseline and source fingerprints, actual root and child Git state, exact submodule pointers, selected provider state, Git semantic reservations, evidence, and candidate identity. After clone, recover reservation owner and branch but require the selected external connector to re-read live status. Report confirmed facts, stale derivations, unknown external state, local-only work, blockers, and one safe next action. Chat memory and generated summaries are navigation hints only.
- For production readiness, verify role/journey/UI coverage, service guarantees and failure behavior, fresh product-authority approval for protected meaning, clean published root and workspace commits, exact UI/frontend/backend pointers, frontend evidence bound to the current UI baseline, TDD and integration evidence, security, privacy, accessibility, observability, operations, support, backup/restore, and applicable migration/rollback evidence.
- Refresh and reconcile the selected task provider before integration or release. Run
stackcord release prepare --json with the selected work and release version. The candidate binds commits, remotes, pointers, the combined provider and Git-reservation revisions, contract fingerprints, evidence, migrations, tool versions, and profile; any identity change creates a different candidate.
- Store user validation evidence outside tracked product files or under ignored local state. Run
stackcord release validate --evidence <file> --confirm --apply, then stackcord release verify --json. Block validation from a different digest, build, commit, or stale screen.
- Use the default
core profile for ordinary services. Enable strict-release only when the organization explicitly needs stronger SBOM, provenance, signatures, approval records, and publication controls. Strict adds gates without replacing core checks.
- Treat publication, marketplace submission, package-manager release, signing, and production mutation as explicit external actions after verification. Never infer them from “완료” or “release 해줘.”
Read context recovery, workflow, safety, and tool selection. If the Plugin is absent, use the repo-local Skill; if the CLI is absent, follow its Markdown fallback and name the checks that remain unverified.
