@blxzer/pactile 0.5.0 → 0.6.0-beta.4

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

@@ -1,29 +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.
+# 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. `pactile task 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/pactile/tasks/templates/release-execution/prd.md

@@ -1,31 +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).
+# 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/pactile/tasks/templates/release-readiness/design.md

@@ -1,50 +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`).
-
-## Pactile CLI reference commands (dry-run / check only)
-
-From the Pactile 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/pactile 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.
+# 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`).
+
+## Pactile CLI reference commands (dry-run / check only)
+
+From the Pactile monorepo `packages/cli` (adjust paths for other products):
+
+```bash
+pnpm --filter @blxzer/pactile exec tsx scripts/check-manifest-continuity.ts
+pnpm release:check
+pnpm release:plan
+pnpm --filter @blxzer/pactile exec tsx scripts/release-preflight.ts verify-packed-cli
+pnpm --filter @blxzer/pactile exec npm pack --dry-run
+```
+
+Do **not** run `pnpm release`, `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/pactile/tasks/templates/release-readiness/handoff-template.md

@@ -1,39 +1,45 @@
-# 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}`
+# 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. Run `pnpm --filter @blxzer/pactile run release:check`, then use
+   `pnpm --filter @blxzer/pactile run release:beta` or
+   `pnpm --filter @blxzer/pactile run release:promote` to prepare a local plan.
+   These commands do not tag or publish. After separate approval, create
+   `pactile-vX.Y.Z-beta.N` at the exact `develop` HEAD or `pactile-vX.Y.Z` at the
+   exact `main` HEAD and follow `docs/governance/releasing.md`; stable promotion
+   uses a separate approved Publish workflow dispatch.
+
+## 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/pactile/tasks/templates/release-readiness/implement.md

@@ -1,29 +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. `.pactile/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 ./.pactile/scripts/task.py validate <this-task>` and `archive --check` when finishing.
-
-## Validation
-
-- Dry-run and `--check` commands only.
+# 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. `.pactile/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 `pactile task 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/pactile/tasks/templates/release-readiness/prd.md

@@ -1,31 +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 Pactile 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
-
+# 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 Pactile 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`.

package/dist/templates/pactile/workflow.md

@@ -1,64 +1,61 @@
-# Development Workflow
-
-> **Human overview — not runtime SSOT.** Gates, Rigor, Topology, and Task state are Kernel / `task.json` projections. Do not parse this document as the runtime program of record.
-
-## Interfaces
-
-Constraints live in artifacts and Kernel records:
-
-| Interface | Role |
-| --- | --- |
-| `prd.md` | Definition and acceptance |
-| `implement.md` | Execution / verification contract (when present) |
-| `verify.md` | Evidence (when recorded) |
-| `task.json` | Status and metadata (accounting) |
-| `kernel.json` | Audit chain |
-| `task.py archive` | Close: `status=completed`, Kernel audit, notes projection |
-
-## User commands
-
-- `pactile-continue` — resume the selected task. Details: `.pactile/framework/index.md`.
-- `pactile-finish-work` — closeout / archive path. Details: `.pactile/framework/index.md`.
-- `pactile-handoff` — session handoff (reports a temp path). Details: `.pactile/framework/index.md`.
-- `pactile-start` — only when the framework needs a refresh and no task is selected.
-
-## Gates
-
-- **Execute:** `python ./.pactile/scripts/task.py start-execution <task> --approved` (`--check` is preflight only; it does not impersonate approval).
-- **Close:** `python ./.pactile/scripts/task.py archive <task>` — writes `completed`, Kernel audit, and notes projection.
-
-## Pointers
-
-Start at `.pactile/framework/index.md`. Do not expand methodology here.
-
-- Parallel first → `.pactile/framework/parallel-first-execution.md`
-- Pool → `.pactile/pool/`
-- Full Quality / graded verify → `.pactile/framework/verification-strength-guide.md`
-- Retrieval → `.pactile/framework/retrieval-daily-guide.md`
-- Subagent dispatch → `.pactile/framework/cursor-subagent-policy.md`
-
-<!--
-  Codex/Claude UserPromptSubmit parses [workflow-state:STATUS] blocks.
-  Bodies are status facts (1–2 sentences), not process teaching.
-  STATUS charset: [A-Za-z0-9_-]+
--->
-
-[workflow-state:no_task]
-No task is selected.
-This status is an accounting fact, not a step list.
-[/workflow-state:no_task]
-
-[workflow-state:planning]
-Selected task status is `planning`.
-Constraints are `prd.md` and optional `design.md`/`implement.md`; Execute starts only after `task.py start-execution --approved`.
-[/workflow-state:planning]
-
-[workflow-state:in_progress]
-Selected task status is `in_progress`.
-Implement against the approved artifacts; Close is `task.py archive` (Kernel audit plus notes projection).
-[/workflow-state:in_progress]
-
-[workflow-state:completed]
-Task status is `completed`.
-`task.py archive` writes this status in the same call that moves the directory.
-[/workflow-state:completed]
+# Task Workflow
+
+> Human overview only, not runtime SSOT. The unified Task Kernel reader determines the stored schema. For a V2 Task, `kernel.json` is the source of lifecycle state, definition, Runs, candidate snapshots, Reviews, dependencies, and Close history.
+
+The installed guide index is `.pactile/framework/index.md`. Load only the guide
+needed for the current decision; reading a guide does not change Kernel state.
+
+## V2 Task contract
+
+A V2 Task is one reviewable deliverable. Its Kernel definition records:
+
+- the deliverable;
+- measurable acceptance criteria (ACs);
+- one delivery level: `local-result`, `pull-request`, `merged-result`, or `documentation`;
+- hard dependency Task IDs. Every dependency must close successfully before this Task may start or close.
+
+Create a Task only after the user agrees to its proposal. Kernel V2 begins at Define; do not project V1 `task.json` phases onto a V2 Task.
+
+## Runs, scheduling, and Review
+
+A Task may have multiple Runs. Each attempt preserves its authorization, write-set snapshot, estimates and measurements, outcome, and (on completion) candidate snapshot. Retrying creates a new Run; it does not overwrite earlier evidence. The latest recorded Run must be completed and is the only one eligible for Review and Close.
+
+Reviews are independent records bound to one Run and exact candidate ID/fingerprint. Close must use the latest Review for that candidate, and that verdict must pass with no blockers and evidence for every AC. If a new Run produces a new candidate, review that candidate separately.
+
+Schedule work for completion-time benefit, subject to hard dependencies, authorization, and write conflicts. There is no fixed numeric concurrency cap. Overlapping write sets are sequential by default; explicit overlap needs recorded authorization and an integration plan. A scheduler suggestion cannot override Kernel gates or write-conflict admission.
+
+For the detailed Task/Run scheduling, isolation, and optional host-dispatch rules, see [critical-path scheduling](./framework/parallel-first-execution.md). The filename is retained for compatibility with existing installations.
+
+## V2 command surface
+
+Use the current Task commands for the stored V2 Kernel: `pactile task create`, `add-dependency`, `run-start`, `run-resume`, `run-result`, `review`, and `close`. Run `pactile task --help` for current arguments. The V2 flow does not use the V1 `start-execution` or directory-archive command.
+
+At Close, the delivery evidence level must equal the definition. `pull-request` and `merged-result` require an HTTPS reference; the other levels still require a nonempty evidence reference and summary. A mismatched level, unmet hard dependency, stale candidate, incomplete AC evidence, or a non-passing latest Review keeps the Task open.
+
+## Compatibility boundary: explicit V1 legacy Tasks
+
+The unified reader preserves existing legacy state and identifies it as V1; do not migrate it by merely editing this overview. Only when the reader identifies a V1 legacy Task should its V1-specific artifacts and commands be considered. For that legacy path, `pactile task start-execution <task> --approved` records the caller's approval declaration, and `pactile task archive <task>` performs the legacy close/archive operation. These commands and the `--approved` flag are not V2 instructions. A CLI flag does not authenticate the caller; human authorization must come from the actual authorized interaction and its evidence.
+
+## Session status hints
+
+The following blocks are compatibility hints for legacy V1 `task.json` status injection. They are not V2 Kernel phase instructions. V2 session guidance comes from the selected Task's compiled Session Pack and Kernel snapshot.
+
+[workflow-state:no_task]
+No task is selected. This is a legacy status hint only; the V2 Session Pack determines whether a V2 Task is selected.
+[/workflow-state:no_task]
+
+[workflow-state:planning]
+Legacy V1 only: the task is in planning. Use its V1 artifacts and compatibility flow; do not apply this hint to a V2 Kernel Task.
+[/workflow-state:planning]
+
+[workflow-state:in_progress]
+Legacy V1 only: the task is in progress. Its V1 artifacts remain the execution boundary; do not apply this hint to a V2 Kernel Task.
+[/workflow-state:in_progress]
+
+[workflow-state:review]
+Legacy V1 only: verification is pending under that task's legacy contract. V2 Review must bind to the exact candidate recorded in its Kernel.
+[/workflow-state:review]
+
+[workflow-state:completed]
+Legacy V1 only: the task is complete under its recorded legacy lifecycle. A directory move is not a V2 Close.
+[/workflow-state:completed]

package/dist/templates/template-utils.d.ts

@@ -1,6 +1,6 @@
 /**
  * Shared utilities for platform template modules.
- * Eliminates boilerplate across qoder/, codebuddy/, droid/, cursor/, gemini/, kiro/ index.ts files.
+ * Eliminates boilerplate across the supported template modules.
  */
 export interface AgentTemplate {
     name: string;
@@ -16,7 +16,6 @@ export interface TemplateReader {
     listMdAgents: (dir?: string) => AgentTemplate[];
     listMdCommands: (dir?: string) => AgentTemplate[];
     listJsonAgents: (dir?: string) => AgentTemplate[];
-    listMdcRules: (dir?: string) => AgentTemplate[];
     getSettings: (filename?: string) => HookTemplate;
     getConfig: (filename: string) => string;
 }

package/dist/templates/template-utils.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"template-utils.d.ts","sourceRoot":"","sources":["../../src/templates/template-utils.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAMH,MAAM,WAAW,aAAa;IAC5B,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,YAAY;IAC3B,UAAU,EAAE,MAAM,CAAC;IACnB,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,cAAc;IAC7B,YAAY,EAAE,CAAC,YAAY,EAAE,MAAM,KAAK,MAAM,CAAC;IAC/C,SAAS,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,MAAM,EAAE,CAAC;IACrC,YAAY,EAAE,CAAC,GAAG,CAAC,EAAE,MAAM,KAAK,aAAa,EAAE,CAAC;IAChD,cAAc,EAAE,CAAC,GAAG,CAAC,EAAE,MAAM,KAAK,aAAa,EAAE,CAAC;IAClD,cAAc,EAAE,CAAC,GAAG,CAAC,EAAE,MAAM,KAAK,aAAa,EAAE,CAAC;IAClD,YAAY,EAAE,CAAC,GAAG,CAAC,EAAE,MAAM,KAAK,aAAa,EAAE,CAAC;IAChD,WAAW,EAAE,CAAC,QAAQ,CAAC,EAAE,MAAM,KAAK,YAAY,CAAC;IACjD,SAAS,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,MAAM,CAAC;CACzC;AAED;;;GAGG;AACH,wBAAgB,oBAAoB,CAAC,aAAa,EAAE,MAAM,GAAG,cAAc,CA8E1E"}
+{"version":3,"file":"template-utils.d.ts","sourceRoot":"","sources":["../../src/templates/template-utils.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAMH,MAAM,WAAW,aAAa;IAC5B,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,YAAY;IAC3B,UAAU,EAAE,MAAM,CAAC;IACnB,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,cAAc;IAC7B,YAAY,EAAE,CAAC,YAAY,EAAE,MAAM,KAAK,MAAM,CAAC;IAC/C,SAAS,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,MAAM,EAAE,CAAC;IACrC,YAAY,EAAE,CAAC,GAAG,CAAC,EAAE,MAAM,KAAK,aAAa,EAAE,CAAC;IAChD,cAAc,EAAE,CAAC,GAAG,CAAC,EAAE,MAAM,KAAK,aAAa,EAAE,CAAC;IAClD,cAAc,EAAE,CAAC,GAAG,CAAC,EAAE,MAAM,KAAK,aAAa,EAAE,CAAC;IAClD,WAAW,EAAE,CAAC,QAAQ,CAAC,EAAE,MAAM,KAAK,YAAY,CAAC;IACjD,SAAS,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,MAAM,CAAC;CACzC;AAED;;;GAGG;AACH,wBAAgB,oBAAoB,CAAC,aAAa,EAAE,MAAM,GAAG,cAAc,CAkE1E"}

package/dist/templates/template-utils.js

@@ -1,6 +1,6 @@
 /**
  * Shared utilities for platform template modules.
- * Eliminates boilerplate across qoder/, codebuddy/, droid/, cursor/, gemini/, kiro/ index.ts files.
+ * Eliminates boilerplate across the supported template modules.
  */
 import { readdirSync, readFileSync } from "node:fs";
 import { dirname, join } from "node:path";
@@ -31,7 +31,7 @@ export function createTemplateReader(importMetaUrl) {
             content: readTemplate(`${dir}/${f}`),
         }));
     }
-    /** Read all .md command files from a subdirectory (e.g. cursor/commands).
+    /** Read all .md command files from a subdirectory.
      * Unlike listMdAgents, the name keeps no prefix transformation — callers
      * decide the output filename (e.g. `pactile-${name}.md`). */
     function listMdCommands(dir = "commands") {
@@ -51,16 +51,6 @@ export function createTemplateReader(importMetaUrl) {
             content: readTemplate(`${dir}/${f}`),
         }));
     }
-    /** Read all .mdc rule files from a subdirectory (Cursor .cursor/rules) */
-    function listMdcRules(dir = "rules") {
-        return listFiles(dir)
-            .filter((f) => f.endsWith(".mdc"))
-            .map((f) => ({
-            // Keep the .mdc extension in the name — Cursor requires it.
-            name: f,
-            content: readTemplate(`${dir}/${f}`),
-        }));
-    }
     /** Read settings.json and return as HookTemplate */
     function getSettings(filename = "settings.json") {
         return { targetPath: filename, content: readTemplate(filename) };
@@ -75,7 +65,6 @@ export function createTemplateReader(importMetaUrl) {
         listMdAgents,
         listMdCommands,
         listJsonAgents,
-        listMdcRules,
         getSettings,
         getConfig,
     };