@blxzer/cursor-trellis 0.1.0

package/dist/templates/trellis/tasks/templates/release-execution/design.md

@@ -0,0 +1,61 @@
+# Design — Release execution
+
+## Boundary
+
+This task **may** mutate remotes **only** after explicit user approval captured in `verify.md` (quote or paraphrase the approval request/response).
+
+## Release status model (this task)
+
+| Status | When to use |
+| --- | --- |
+| **published** | npm and/or git remote actions completed for the approved version |
+| **not published** | Execution aborted or only dry-run/preflight completed |
+| **blocked** | Preflight failed; do not publish until fixed |
+| **waived** | User approved proceeding despite a listed risk |
+| **deferred** | User postponed publish after readiness |
+
+Do not mark **ready to publish** here — that remains the readiness task outcome.
+
+## Approval gate (mandatory)
+
+Before any of the following, stop and obtain explicit user approval:
+
+- `node scripts/release.js …` (bundles bump, commit, tag, push)
+- `npm publish` / CI publish workflow dispatch
+- `git tag` / `git push` (including `--tags`)
+- GitHub **Create release** or promotion workflows
+
+Document in `verify.md`:
+
+```markdown
+## Publish approval evidence
+
+User explicitly approved: yes/no
+Approved version: …
+Approved dist-tag: …
+Approved remote actions: tag / push / npm publish / …
+```
+
+## Evidence contract (`verify.md`)
+
+1. **Readiness link** — path to readiness `handoff.md`.
+2. **Publish approval evidence** — as above.
+3. **Preflight results** — `check-versions`, `publish-plan`, `verify-packed-cli`.
+4. **Execution log** — commands run (redact tokens); pass/fail.
+5. **Post-publish smoke** — registry check, `trellis --version`, dogfood smoke commands.
+6. **Validation evidence** — tests run after publish if applicable.
+
+## Trellis CLI reference sequence (after approval)
+
+Typical human/CI sequence (do not automate without approval):
+
+```bash
+cd packages/cli
+node scripts/release-preflight.js check-versions
+node scripts/release-preflight.js publish-plan
+# After approval:
+pnpm --filter @blxzer/cursor-trellis release:beta   # or patch/minor/major per policy
+node scripts/release-preflight.js verify-npm --package all
+```
+
+`release.js` performs commit, tag, and push — treat it as a single approved bundle or decompose manually per policy.

package/dist/templates/trellis/tasks/templates/release-execution/handoff-template.md

@@ -0,0 +1,29 @@
+# Handoff — Release execution — `{task-id}`
+
+## Published
+
+| Action | Evidence |
+| --- | --- |
+| Version bumped | `{yes/no}` — `{version}` |
+| Git tag | `{tag or none}` |
+| Git push | `{ref or none}` |
+| npm publish | `{package@version + dist-tag or none}` |
+| Post-publish smoke | `{summary}` |
+
+## Not published
+
+- `{Describe aborted or dry-run-only session}`
+
+## Ready to publish
+
+_Refer to readiness task:_ `{path to readiness handoff.md}`
+
+## Blockers
+
+| Blocker | Severity | Disposition | Notes |
+| --- | --- | --- | --- |
+| `{if any}` | | | |
+
+## Residual risks
+
+- `{registry lag, global CLI hygiene, consumer dist-tag confusion, etc.}`

package/dist/templates/trellis/tasks/templates/release-execution/implement.md

@@ -0,0 +1,29 @@
+# Implementation Plan — Release execution
+
+## Development Strategy Contract
+
+execution_mode: lite-task
+isolation: none
+verification_profile: standard
+retrieval_profile: structure
+optional_capabilities: []
+quality_gates:
+  mode: profile
+  profile: standard
+  enabled: []
+  disabled: []
+
+## Steps
+
+1. Read linked readiness `handoff.md` and confirm **ready to publish**.
+2. Ask user for explicit approval; record in `verify.md` **Publish approval evidence**.
+3. Run preflight checks (no publish yet).
+4. On approval only, run approved release commands.
+5. Run post-publish smoke and registry verification.
+6. Write `handoff.md` (**Published** / **Not published** / residual risks).
+7. `task.py validate` and archive when complete.
+
+## Validation
+
+- Preflight must pass or be explicitly waived before publish.
+- If user denies approval, end with **not published** and no remote mutations.

package/dist/templates/trellis/tasks/templates/release-execution/prd.md

@@ -0,0 +1,31 @@
+# Release execution — {package_or_product}
+
+## Goal
+
+Execute an **already prepared** release after explicit user approval, with auditable evidence for each remote mutation.
+
+## Preconditions
+
+- A completed **release-readiness** task (or equivalent evidence) with **ready to publish** status.
+- Explicit user approval in this session for **each** of: version bump (if not done), git tag, git push, npm publish (and GitHub release if used).
+- No execution without naming the approved version and dist-tag.
+
+## Requirements
+
+- Link readiness task path and restate approved version/channel in `verify.md`.
+- Run project release preflight (`check-versions`, `publish-plan`, `verify-packed-cli`) immediately before publish.
+- Execute only approved steps; record exact commands, timestamps, and outcomes.
+- Capture post-publish smoke (registry visibility, installed CLI version, or project-specific smoke).
+- Write `handoff.md` with **Published** evidence separate from readiness artifacts.
+
+## Acceptance Criteria
+
+- [ ] `handoff.md` documents what was published/tagged/pushed vs skipped.
+- [ ] `verify.md` lists validation and post-publish smoke results.
+- [ ] No publish/tag/push occurred before documented user approval.
+- [ ] Readiness task remains **not published** if execution was aborted.
+
+## Out Of Scope
+
+- Re-doing full readiness research (fix blockers in readiness or a new readiness task).
+- Publishing without user approval “because checks passed”.

package/dist/templates/trellis/tasks/templates/release-readiness/design.md

@@ -0,0 +1,50 @@
+# Design — Release readiness
+
+## Boundary
+
+This task is **readiness only**. It produces evidence and recommendations; it does not change registry or remote git state.
+
+## Release status model (this task)
+
+Use these labels in `handoff.md` and `verify.md` (not `task.json.status` — see workflow release guidance).
+
+| Status | Meaning |
+| --- | --- |
+| **ready to publish** | Evidence complete; operator may proceed after explicit approval |
+| **not published** | No remote release actions were performed in this task |
+| **blocked** | A required gate failed; publish must not proceed until fixed or waived |
+| **waived** | User explicitly accepted a known blocker; document approver + rationale |
+| **deferred** | Publish intentionally postponed (e.g. wait for another child / dogfood) |
+
+**published** belongs only in a **release-execution** task after verified remote actions.
+
+## Evidence contract (`verify.md`)
+
+Include grep-friendly sections (archive checks may reference these families):
+
+1. **Version recommendation** — current vs proposed; channel; dist-tag expectation.
+2. **Changelog / release notes** — draft text or path to notes file.
+3. **Migration manifest** — new/updated manifest id or “no manifest change”.
+4. **Build evidence** — commands + pass/fail summary.
+5. **Test evidence** — focused suite scope; note full-suite gaps if publish pipeline would fail.
+6. **Pack dry-run evidence** — `npm pack --dry-run` / `publish-plan` / `verify-packed-cli` as applicable.
+7. **Prepublish blockers** — table with severity and disposition (`blocking` / `fixed` / `waived` / `deferred`).
+
+## Trellis CLI reference commands (dry-run / check only)
+
+From the Trellis monorepo `packages/cli` (adjust paths for other products):
+
+```bash
+node scripts/check-manifest-continuity.js
+node scripts/release-preflight.js check-versions
+node scripts/release-preflight.js publish-plan
+node scripts/release-preflight.js verify-packed-cli
+pnpm --filter @blxzer/cursor-trellis exec npm pack --dry-run
+```
+
+Do **not** run `scripts/release.js`, `npm publish`, or `git push` in readiness.
+
+## Safety
+
+- Agents must not run publish/tag/push even if checks are green.
+- Waiving a blocker requires explicit user words in chat or `handoff.md`, not agent assumption.

package/dist/templates/trellis/tasks/templates/release-readiness/handoff-template.md

@@ -0,0 +1,39 @@
+# Handoff — Release readiness — `{task-id}`
+
+## Ready to publish
+
+**Materials are prepared; explicit user approval still required before any remote release.**
+
+| Area | Status |
+| --- | --- |
+| Version recommendation | `{proposed-version}` via `{channel}` |
+| Changelog / release notes | Draft in `verify.md` |
+| Migration manifest | `{manifest-id or none}` |
+| Build / test / pack dry-run | `{summary}` |
+
+**Operator checklist before publish (not executed in readiness task):**
+
+1. Resolve or waive each **blocking** row in Blockers below.
+2. Create or select a **release-execution** task; obtain explicit publish approval.
+3. Only then run release scripts (`release.js` / CI publish) per project policy.
+
+## Not published
+
+- No npm publish, git tag, git push, or GitHub release in this task session.
+- Workspace `package.json` versions unchanged unless a separate task already bumped them.
+
+## Blockers
+
+| Blocker | Severity | Disposition | Notes |
+| --- | --- | --- | --- |
+| Explicit user approval for publish | **Required gate** | blocking | Out of scope for readiness by design |
+| `{example}` | blocking / fixed / waived / deferred | `{disposition}` | `{notes}` |
+
+## Published
+
+_Not applicable in a readiness task. Record publish evidence only in release-execution `handoff.md`._
+
+## Integration notes
+
+- Link execution task: `{path or pending}`
+- Parent / dogfood notes: `{optional}`

package/dist/templates/trellis/tasks/templates/release-readiness/implement.md

@@ -0,0 +1,29 @@
+# Implementation Plan — Release readiness
+
+## Development Strategy Contract
+
+execution_mode: lite-task
+isolation: none
+verification_profile: standard
+retrieval_profile: structure
+optional_capabilities: []
+quality_gates:
+  mode: profile
+  profile: standard
+  enabled: []
+  disabled: []
+
+## Steps
+
+1. Read product release spec (e.g. `.trellis/spec/**/release*.md`) and recent integrated task handoffs.
+2. Record current versions from `package.json` (and lockstep packages).
+3. Draft version recommendation and changelog.
+4. Run non-mutating guards and validation (manifest, build, focused tests, typecheck, pack dry-run).
+5. Fill `verify.md` using the evidence contract in `design.md`.
+6. Write `handoff.md` with **Ready to publish**, **Not published**, and **Blockers** tables.
+7. Run `python ./.trellis/scripts/task.py validate <this-task>` and `archive --check` when finishing.
+
+## Validation
+
+- Dry-run and `--check` commands only.
+- No version bump, tag, push, or publish.

package/dist/templates/trellis/tasks/templates/release-readiness/prd.md

@@ -0,0 +1,31 @@
+# Release readiness — {package_or_product}
+
+## Goal
+
+Prepare a **ready-to-publish** release recommendation and evidence **without** publishing, tagging, pushing, or bumping versions in this task.
+
+## Requirements
+
+- Record current workspace versions (CLI, core, or product packages as applicable).
+- Recommend next version and release channel (`patch` / `minor` / `major` / `beta` / `rc` / `promote`) with rationale.
+- Draft changelog / release notes for the scoped changes.
+- Document migration manifest expectations when the Trellis CLI ships template or script changes.
+- Run **non-mutating** validation: build, focused tests, typecheck, pack dry-run, manifest/docs guards (dry-run only).
+- Structure prepublish blockers as `blocking` / `fixed` / `waived` / `deferred`.
+- Write `verify.md` and `handoff.md` that clearly separate **ready to publish** from **published**.
+
+## Acceptance Criteria
+
+- [ ] `handoff.md` includes **Ready to publish**, **Not published**, and **Blockers** sections.
+- [ ] `verify.md` includes validation commands/results and standardized release evidence headings.
+- [ ] No `npm publish`, `git tag`, `git push`, version bump commits, or GitHub release created in this task.
+- [ ] Any waived blocker names the approver and rationale in `handoff.md`.
+
+## Out Of Scope
+
+- Release execution (publish / tag / push / bump).
+- Fixing unrelated full-suite failures unless required to document a publish blocker.
+
+## Operator handoff
+
+When readiness is complete, open a separate **release-execution** task (or explicit user approval in-session) before any remote mutation. Link the readiness task directory in execution `prd.md`.