Update to ShipFrame

{
  "description": "Orchestrate a generic release by loading project profile rules, running checks, and collecting deploy evidence.",
  "included_files": [],
  "name": "project-release",
  "skill_md_contents": "---\nname: project-release\ndescription: Orchestrate a generic release by loading project profile rules, running checks, and collecting deploy evidence.\nallowed-tools: Read Glob Grep Bash Skill\nargument-hint: '[--target <frontend|backend|full-stack|library|docs>] [--environment <name>]'\neffort: high\n---\n\n# Project Release\n\nProject Release is the generic ShipFrame release entrypoint. It must work across projects without hardcoding a specific client or product.\n\n## Flow\n\n1. Run `project-profile` to load repo-specific rules.\n2. Run `release-checklist` to define release gates.\n3. Dispatch by target:\n   - frontend/static/UI changes → `frontend-release`\n   - backend/API/jobs/integrations → `backend-release`\n   - both → run both in dependency order from the project profile\n   - docs/library-only → run the relevant checklist and evidence steps\n4. Run `deploy-evidence` after deploy/publication.\n5. Report final status with completed checks, evidence, gaps, and rollback notes.\n\n## Completion rule\n\nDo not say \"done\", \"deployed\", or \"released\" unless the final report includes concrete evidence for the intended environment.\n\n## Final report\n\n```markdown\n## Project Release Report\n\n**Target:** <target>\n**Environment:** <environment>\n**Version/tag/commit:** <value>\n\n### Completed\n- ✅ <item>\n\n### Evidence\n- ✅ <item>\n\n### Gaps / follow-up\n- <item or \"None\">\n\n### Verdict\n<Released | Not released | Partially verified>\n```\n"
}