@polymorphism-tech/morph-spec 8.26.0 → 8.27.0

package/README.md

@@ -3,7 +3,7 @@
 > Spec-driven development framework for multi-stack projects. Turns feature requests into implementation-ready code through structured, AI-orchestrated phases.
 
 **Package:** `@polymorphism-tech/morph-spec`
-**Version:** 8.26.0  
+**Version:** 8.27.0  
 **Requires:** Node.js 22+, Claude Code
 
 ---
@@ -173,7 +173,7 @@ morph-spec archive {feature}                   # Archive WITHOUT integrating (le
 
 `finish` is the normal close for both flows: it archives (committing the move inside `morph/{feature}`), then integrates — `--merge` merges `--no-ff` into the default branch locally; `--pr` pushes the branch and runs `gh pr create` (needs `origin` + authenticated `gh`) — and tears down the worktree if there is one. Plain `archive` is reserved for legacy features (born before every feature had a `morph/{feature}` branch) and cleanup.
 
-Task progress within a feature is tracked with the native `TaskCreate`/`TaskUpdate` tools, persisted to `tasks.json` — there is no separate CLI command for starting or completing a task.
+Task progress within a feature is recorded in `tasks.json` — Claude writes the mutable `status`/`outputs`/`notes` fields as it goes, and there is no separate CLI command for starting or finishing a task.
 
 ### Validation
 
@@ -368,4 +368,4 @@ Code generated by morph-spec (contracts, templates, implementation output) belon
 
 ---
 
-*morph-spec v8.26.0 by [Polymorphism Tech](https://polymorphism.tech)*
+*morph-spec v8.27.0 by [Polymorphism Tech](https://polymorphism.tech)*

package/claude-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "morph-spec",
-  "version": "8.26.0",
+  "version": "8.27.0",
   "displayName": "MORPH-SPEC Framework",
   "description": "Spec-driven development with 38 agents and 8-phase workflow for .NET/Blazor/Next.js/Azure",
   "publisher": "polymorphism-tech",

package/docs/CHEATSHEET.md

@@ -185,4 +185,4 @@ Never edited directly — go through CLI commands or `morph-spec update` instead
 
 ---
 
-*morph-spec v8.26.0 by Polymorphism Tech*
+*morph-spec v8.27.0 by Polymorphism Tech*

package/docs/QUICKSTART.md

@@ -85,7 +85,7 @@ At this point, planning is complete:
 ```
 
 Claude reads `spec.md`, `mandate.md`, and `tasks.json`, then implements task by task with auto-advance (no pause between tasks unless there's a blocking ambiguity):
-- Tracks task progress with the native `TaskCreate`/`TaskUpdate` tools, persisted to `tasks.json`
+- Records task progress in `tasks.json`, writing the mutable `status`/`outputs`/`notes` fields
 - Runs the validators relevant to your stack after each task (e.g. `architecture`/`packages`/`contract-compliance` for .NET, `nextjs-component`/`css`/`design-system` for Next.js) via `morph-spec verify`
 - Applies `morph-eval` after each task — a score below 9 triggers an autonomous correction loop, not a pause
 - Generates `3-implement/recap.md` on completion, then Gate 3 review (`4-review/`)
@@ -106,7 +106,7 @@ Approve the current gate and scaffold the next phase folder in one step:
 morph-spec advance my-feature
 ```
 
-Task progress is tracked with the native `TaskCreate`/`TaskUpdate` tools and persisted to `tasks.json` — there is no separate CLI command for marking a task done.
+Task progress is recorded in `tasks.json` — Claude writes the mutable `status`/`outputs`/`notes` fields directly, and there is no separate CLI command for marking a task done.
 
 Run validators at any time:
 
@@ -249,4 +249,4 @@ morph-spec doctor
 
 ---
 
-*morph-spec v8.26.0 by Polymorphism Tech*
+*morph-spec v8.27.0 by Polymorphism Tech*

package/framework/rules/morph-task-tracking.md

@@ -5,49 +5,22 @@ stacks:
 
 # MORPH-SPEC Task Tracking
 
-> Session tasks are MANDATORY in every MORPH-SPEC phase. They track real progress and must be
-> created BEFORE any phase work begins.
-
-## Rules
-
-1. **Every phase skill MUST create session tasks** using `TaskCreate` before reading files or generating outputs
-2. **Tasks are dynamic** — analyze the phase workflow and create tasks that reflect YOUR actual planned actions for this session
-3. **Every task MUST be updated**: `in_progress` before starting, `completed` after finishing
-4. **Pipeline orchestrators** (`/morph-proposal`, `/morph-apply`) MUST create master tasks for each phase
-5. **Never skip task creation** — even if resuming mid-phase, create tasks for remaining steps
-6. **Granularity**: minimum 2, typically 3-7 tasks per phase — adjust to complexity
-7. **For iterative work** (clarification rounds, quality loops): update task `subject` with round/score progress
-
-## Task Update Pattern
-
-```
-TaskUpdate(taskId, status="in_progress")   // before starting the step
-// ... do the work ...
-TaskUpdate(taskId, status="completed")     // after step finishes
-```
-
-For iterative tasks:
-```
-TaskUpdate(taskId, subject="Round 3 — score 82/100")
-```
+> Progress lives in `tasks.json` — nowhere else. There is no CLI command to mark a task done and
+> no session-level checklist to keep in sync: this file IS the record of what happened.
 
 ## Persisting Progress to `tasks.json`
 
-> **Dois sistemas, dois vocabulários.** Tudo acima desta linha é sobre as *session
-> tasks* nativas do Claude Code (`TaskCreate`/`TaskUpdate`), cujo status terminal é
-> `completed`. Tudo abaixo é sobre o `tasks.json` do morph-spec, governado por
-> `.morph/framework/schemas/tasks.schema.json`, cujo status terminal é `done` —
-> **`completed` não existe nesse enum** e o hook `protect-spec-files` rejeita a
-> gravação. Não misture os dois.
-
-Native session tasks (`TaskCreate`/`TaskUpdate`) track your live work. To persist
-task progress for the feature, write `.morph/features/{feature}/2-plan/tasks.json`,
+To record task progress for the feature, write `.morph/features/{feature}/2-plan/tasks.json`,
 touching ONLY the mutable fields:
 
 - `status` — `pending` → `in_progress` → `done` (também: `skipped`, `blocked`)
 - `outputs` — the files the task produced
 - `notes` — free-text record (deviations, context, resolved blockers)
 
+> **O status terminal é `done`.** `completed` **não existe** no enum de
+> `.morph/framework/schemas/tasks.schema.json` — é vocabulário de outro sistema, e o hook
+> `protect-spec-files` rejeita a gravação.
+
 The plan contract — `title`, `description`, `dependencies`, `effort`, `doneCriteria`,
 `group`, `agent`, `standards` — is frozen after Gate 2. Any attempt to change it is
 blocked by the `protect-spec-files` hook. `agent` (persona id, no `morph-` prefix)
@@ -59,6 +32,10 @@ as long as it touches only `status`, `outputs`, and `notes`. State is then synce
 automatically by the `state-sync` PostToolUse hook; you do not call a CLI to mark
 output.
 
+Update each task as you go — `in_progress` when you pick it up, `done` when it is finished —
+rather than batching every write to the end of the phase. `morph-spec status`, `dag`, `verify`
+and the dashboard all read this file, so a stale `tasks.json` is a blind orchestrator.
+
 ## Deviation Tracking
 
 When completing a task differently than originally planned, record the reason in the

package/framework/rules/morph-workflow.md

@@ -215,7 +215,7 @@ task turns out to be bigger than estimated, three different situations resolve t
 
 | Situation | Path |
 |-----------|------|
-| **Small addition**, still inside the task's scope | Record it in the task's `notes` (a mutable field) and track the sub-steps with native `TaskCreate`/`TaskUpdate` for this session |
+| **Small addition**, still inside the task's scope | Record it in the task's `notes` (a mutable field) — no gate to revoke, no contract to amend |
 | **Error of fact**: the spec asserts something about the code that the code contradicts, with no scope change | Append an `## Errata` block at the END of the file. Body untouched, append-only, accepted by `protect-spec-files` **without revoking the gate** — freezing the CONTRACT is not freezing an ERROR OF FACT (MORPH.md §3) |
 | **The scope itself changed**: the contract no longer describes the work | `morph-spec unapprove {feature} plan --reason "..."`, amend the plan, then re-approve. There is no shortcut around the gate for this one |
 

package/framework/skills/core/create-umbraco-lp/SKILL.md

@@ -4,7 +4,7 @@ description: Guia a criação de uma landing page nova ponta-a-ponta a partir do
 version: core
 when-to-invoke: ao iniciar um novo projeto de LP com o template Umbraco genérico
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 stacks:
   - umbraco
 ---

package/framework/skills/core/migrate-lp-to-umbraco/SKILL.md

@@ -4,7 +4,7 @@ description: Migra uma landing page existente (React/Vite, Next.js estático ou
 version: core
 when-to-invoke: ao receber instrução "use /migrate-lp-to-umbraco {projeto}" do usuário, ou quando o usuário descrever necessidade de migrar uma LP para Umbraco
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 stacks:
   - umbraco
 ---

package/framework/skills/core/morph-apply/SKILL.md

@@ -4,7 +4,7 @@ description: Orquestra a execução autônoma de tasks de uma feature morph-spec
 version: core
 when-to-invoke: após Gate 2 aprovado, ao receber instrução "use /morph-apply" ou "implementar feature"
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-apply
@@ -158,8 +158,8 @@ dispatch Agent (subagent_type: "morph-{id}") with prompt:
        (que é cortesia best-effort e pode não chegar inteira). NÃO chame
        SendMessage.
     2. NÃO toque em tasks.json, feature.json, state.json nem no board de
-       sessão (TaskCreate/TaskUpdate) — todo estado (status de task, scores,
-       gates) é gravado exclusivamente pelo orquestrador.
+       sessão — todo estado (status de task, scores, gates) é gravado
+       exclusivamente pelo orquestrador.
     3. Verificação condicional ao isolamento:
        - Batch SEM isolamento (working tree compartilhada): NÃO rode build/test da
          suíte compartilhada — edições concorrentes quebram o build umas das outras;

package/framework/skills/core/morph-brainstorming/SKILL.md

@@ -4,7 +4,7 @@ description: Entende o negócio, os usuários e a arquitetura antes de qualquer
 version: core
 when-to-invoke: ao receber um novo request de feature, antes de morph-plan
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-brainstorming

package/framework/skills/core/morph-eval/SKILL.md

@@ -4,7 +4,7 @@ description: Avalia a qualidade de uma tarefa ou fase com rubricas graduadas 0-1
 version: core
 when-to-invoke: ao completar uma tarefa ou ao finalizar uma fase de implementação
 user-invokable: false
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-eval

package/framework/skills/core/morph-hotfix/SKILL.md

@@ -4,7 +4,7 @@ description: ADW cirúrgico de hotfix — resolve uma queda/bug crítico de prod
 version: core
 when-to-invoke: ao receber "/morph-hotfix {feature}", quando a morph-proposal classifica o pedido como workType hotfix (Passo 0), ou o usuário diz "produção caiu / hotfix / urgente"
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-hotfix

package/framework/skills/core/morph-implement/SKILL.md

@@ -4,7 +4,7 @@ description: Guia a execução de cada tarefa de implementação com standard e
 version: core
 when-to-invoke: ao iniciar cada task de implementação listada em tasks.json
 user-invokable: false
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-implement

package/framework/skills/core/morph-plan/SKILL.md

@@ -4,7 +4,7 @@ description: Guia a produção dos artefatos de planejamento de uma feature (use
 version: core
 when-to-invoke: ao iniciar a fase plan de uma feature, após o Gate 1 (proposal aprovado)
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-plan

package/framework/skills/core/morph-proposal/SKILL.md

@@ -4,7 +4,7 @@ description: Orquestra a fase de proposta+plano de uma feature morph-spec. Encad
 version: core
 when-to-invoke: ao receber instrução "use /morph-proposal" do usuário, ou ao iniciar uma nova feature
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-proposal

package/framework/skills/core/morph-review/SKILL.md

@@ -4,7 +4,7 @@ description: Conduz a fase de revisão e produz o review-report.md para o Gate 3
 version: core
 when-to-invoke: ao iniciar a fase review, após todas as tasks de tasks.json estarem com status `done`
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-review

package/framework/skills/core/morph-stack-scan/SKILL.md

@@ -4,7 +4,7 @@ description: Varre o codebase existente, detecta stack atual, compara com o stac
 version: core
 when-to-invoke: ao iniciar uma feature em projeto brownfield (codebase já existente)
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-stack-scan

package/framework/skills/core/morph-standards/SKILL.md

@@ -4,7 +4,7 @@ description: Localiza um standard específico via busca server-side (morph-spec
 version: core
 when-to-invoke: quando precisar consultar um standard específico durante a implementação
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-standards

package/framework/skills/core/morph-uiux/SKILL.md

@@ -4,7 +4,7 @@ description: Conduz a fase opcional de UI/UX — design system, mockups, compone
 version: core
 when-to-invoke: ao tomar o ramo uiux (morph-spec advance --design), depois do Gate 1 e antes do morph-plan
 user-invokable: true
-cliVersion: "8.26.0"
+cliVersion: "8.27.0"
 ---
 
 # morph-uiux

package/framework/templates/docs/onboarding.md

@@ -76,10 +76,10 @@ morph-spec archive <feature>
 morph-spec doctor
 ```
 
-> **Task tracking is native.** During the implement phase Claude tracks its own
-> work with the `TaskCreate`/`TaskUpdate` tools and persists progress by writing
-> `tasks.json` (only the `status`, `outputs`, and `notes` fields). State is synced
-> automatically by the `state-sync` hook — task tracking is native, not a CLI command.
+> **Task tracking lives in `tasks.json`.** During the implement phase Claude records
+> progress by writing `tasks.json` directly (only the `status`, `outputs`, and `notes`
+> fields). State is synced automatically by the `state-sync` hook — there is no CLI
+> command to mark a task done.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polymorphism-tech/morph-spec",
-  "version": "8.26.0",
+  "version": "8.27.0",
   "description": "MORPH-SPEC: NLH (Natural Language Harness) for spec-driven development with Claude Code",
   "keywords": [
     "claude-code",