@polymorphism-tech/morph-spec 8.46.0 → 9.0.0

package/framework/rules/nextjs-standards.md

@@ -8,14 +8,16 @@ stacks:
 
 # Next.js Standards
 
-@.morph/framework/standards/frontend/nextjs/naming-conventions.md
-@.morph/framework/standards/frontend/nextjs/project-structure.md
-@.morph/framework/standards/frontend/nextjs/app-router.md
-@.morph/framework/standards/frontend/nextjs/components.md
-@.morph/framework/standards/frontend/nextjs/data-fetching.md
-@.morph/framework/standards/frontend/nextjs/forms.md
-@.morph/framework/standards/frontend/nextjs/state-management.md
-@.morph/framework/standards/frontend/nextjs/testing.md
-@.morph/framework/standards/frontend/nextjs/nextjs-patterns.md
-@.morph/framework/standards/frontend/nextjs/motion-patterns.md
-@.morph/framework/standards/architecture/code-comments.md
+- **frontend-nextjs-naming-conventions** (`frontend/nextjs/naming-conventions.md`) — Arquivo SEMPRE kebab-case (`user-card.tsx`); export PascalCase para componente e `useX` para hook. Zod em `.schemas.ts`, tipos em `.types.ts` via `z.infer`. Named export (só `page.tsx` usa `default`). Nunca misture casos na mesma categoria.
+- **frontend-nextjs-project-structure** (`frontend/nextjs/project-structure.md`) — `src/app/` só roteia e importa de `features/`. Cada `src/features/{f}/` tem `components/`, `hooks/`, `types/` e `index.ts` como API pública (import de `@/features/users`, nunca deep path). NUNCA uma feature importa outra; `components/ui/` é shadcn e não se edita.
+- **frontend-nextjs-app-router** (`frontend/nextjs/app-router.md`) — Server Component por padrão; `'use client'` só para interação, browser API ou TanStack Query. Nunca fetch em `useEffect`. `loading.tsx`/`error.tsx` ao lado do `page.tsx` (`error.tsx` é client). Server Component chama o .NET com `BACKEND_API_PREFIX`; evite `route.ts`.
+- **frontend-nextjs-components** (`frontend/nextjs/components.md`) — `components/ui/` é saída do shadcn CLI (nunca editar; envolva em `components/`); `components/` sem regra de negócio e sem importar `features/`; `features/*/components/` conhece o domínio. Props tipadas e validadas com Zod, sempre com `className` opcional.
+- **frontend-nextjs-data-fetching** (`frontend/nextjs/data-fetching.md`) — Server Component com `BACKEND_API_PREFIX`; Client Component só pelo proxy same-origin com `PROXY_API_PREFIX`. TanStack Query 5 com key factory por feature e `invalidateQueries({ queryKey })`; toda resposta passa por Zod. PROIBIDO: `useEffect(() => fetch…)` e paginar/filtrar a coleção inteira no browser.
+- **frontend-nextjs-forms** (`frontend/nextjs/forms.md`) — react-hook-form + Zod (`zodResolver`) + Field do shadcn via `Controller`; tipo por `z.infer`; nunca `useState` por campo. Submit por `useMutation`, erro em `root`. Edição reusa o schema de criação (`.partial()`). Zod 4: `z.email()`.
+- **frontend-nextjs-state-management** (`frontend/nextjs/state-management.md`) — Estado de servidor no TanStack Query, nunca copiado para `useState`. Página, ordenação, filtros e aba ativa na URL (`searchParams`). Context só para tema, usuário ou locale. NUNCA Zustand/Redux antes de esgotar Server Components + TanStack Query.
+- **frontend-nextjs-testing** (`frontend/nextjs/testing.md`) — Vitest + Testing Library; MSW para API; Playwright para e2e. Teste comportamento, não implementação. Orçamento: um teste por pós-condição + um de regressão por bug; cenários do mesmo comportamento em `it.each`; nada de teste que só confere string de copy.
+- **frontend-nextjs-nextjs-patterns** (`frontend/nextjs/nextjs-patterns.md`) — Route Handler é BFF: `auth.getSession()` (401 sem sessão) e delega ao .NET; banco NUNCA em route handler. Zod no client e no server (`safeParse`, 400). `strict: true` + `noUncheckedIndexedAccess`; sem `any` em resposta de API. shadcn via `npx shadcn@latest add`.
+- **frontend-nextjs-motion-patterns** (`frontend/nextjs/motion-patterns.md`) — Motion via `motion/react` (nunca `framer-motion` junto). Variants em `motion/variants.ts` com durations/easings de `@/lib/design-tokens`. `useReducedMotion()` obrigatório; o `layout.tsx` raiz segue Server Component. 3–5 momentos de motion por página; cena guiada por scroll é do GSAP, nunca no mesmo elemento.
+- **architecture-code-comments** (`architecture/code-comments.md`) — Padrão é nenhum comentário: renomeie, extraia, tipe ou teste antes. Só o porquê que o código não mostra (invariante, ordem, quirk externo com link), até ~3 linhas. PROIBIDO: história de processo (task, UC, ADR, Gate), repetir o código, XML doc/JSDoc que repete a assinatura, banner, `#region`, código comentado, TODO solto. O hook `comment-guard` bloqueia.
+
+> Resumo injetado quando você lê ou edita um arquivo casado por `paths:`. Texto completo: `morph-spec standards --find "<id>"` e leia só a seção necessária de `.morph/framework/standards/<path>`.

package/framework/rules/nextjs-templates.md

@@ -27,7 +27,7 @@ morph-spec scaffold nextjs user-profile
 
 Generates 4 files: page (Server Component), list component, form component, TanStack Query hook.
 
-**Only use `template render` for individual files when modifying an existing feature.**
+**Adding a single file to an existing feature:** read its `.hbs` template (table below) and write the file following it — `scaffold` generates whole features only, and there is no single-file render command.
 
 | Template | Path | Purpose |
 |----------|------|---------|

package/framework/rules/resend-standards.md

@@ -9,4 +9,6 @@ stacks:
 
 # Resend Email Standards
 
-@.morph/framework/standards/backend/integrations/resend/resend-email.md
+- **backend-integrations-resend-resend-email** (`backend/integrations/resend/resend-email.md`) — REST API, não SMTP. Next: `resend` + React Email, um cliente em `lib/resend.ts`; .NET: pacote `Resend` com `AddHttpClient<ResendClient>()`. Envio sempre assíncrono (Hangfire), retry com Polly. Webhook Svix: verifique o corpo CRU com `resend.webhooks.verify()`, nunca HMAC na mão. Domínio verificado (SPF, DKIM, DMARC) antes do primeiro envio.
+
+> Resumo injetado quando você lê ou edita um arquivo casado por `paths:`. Texto completo: `morph-spec standards --find "<id>"` e leia só a seção necessária de `.morph/framework/standards/<path>`.

package/framework/schemas/config.schema.json

@@ -9,6 +9,18 @@
       "type": "object",
       "additionalProperties": true,
       "properties": {
+        "stack": {
+          "type": "string",
+          "description": "Stack tags joined by `+` (e.g. `dotnet+nextjs`). Decides the build node's commands, which assets install, and that bin/ and obj/ go into .gitignore."
+        },
+        "frontendPath": {
+          "type": "string",
+          "description": "Folder of the frontend, relative to the project root: where the build node runs `tsc`. Absent: the root."
+        },
+        "backendPath": {
+          "type": "string",
+          "description": "Folder of the .NET solution, relative to the project root: where the build node runs `dotnet build`. Absent: the root, or the repository's single .sln/.slnx (else single .csproj) when the root has none."
+        },
         "ci": {
           "type": "boolean",
           "description": "false turns `verify {f} --ci` into the local verify (with the reason printed). Absent or true: the Gate 3 proof comes from the GitHub Actions workflow that runs `morph-spec verify` (created on first use), whenever origin is GitHub and gh is authenticated."
@@ -60,20 +72,13 @@
               "e2e": {
                 "type": "boolean",
                 "default": false,
-                "description": "Requires the application stack to be up. Runs at feature scope only, never in the per-task loop."
+                "description": "Requires the application stack to be up."
               },
               "linuxImage": {
                 "type": "string",
                 "minLength": 1,
                 "description": "Overrides the container image used by `verify --linux` for this node."
               },
-              "groups": {
-                "type": "array",
-                "minItems": 1,
-                "uniqueItems": true,
-                "items": { "type": "string", "enum": ["backend", "frontend", "tests", "infra", "docs"] },
-                "description": "Which task group(s) (tasks.json `group`) this node verifies. Absent means the runner's own default applies (RUNNER_DEFAULT_GROUPS in src/lib/tasks/test-nodes.js) — `none`/`evals` have no default and are unscoped unless declared here."
-              },
               "evals": {
                 "type": "object",
                 "additionalProperties": false,
@@ -191,7 +196,7 @@
         "shutdownBuildServer": {
           "type": "boolean",
           "default": true,
-          "description": "Run `dotnet build-server shutdown` at the end of a feature-scope `verify` and of `e2e down`, only when no slot is held and no dotnet build/test is alive. Never at the end of a task-scope verify: every task would pay a cold compiler."
+          "description": "Run `dotnet build-server shutdown` at the end of a `verify` and of `e2e down`, only when no slot is held and no dotnet build/test is alive."
         },
         "disableNodeReuse": {
           "type": "boolean",

package/framework/schemas/feature.schema.json

@@ -38,17 +38,16 @@
       "type": "object",
       "description": "One entry per gate. Written ONLY by `morph-spec approve`/`advance` (approvedBy: \"auto\") or the state-sync hook on a human \"aprovado\" answer (approvedBy: \"manual\").",
       "properties": {
-        "proposal": { "$ref": "#/definitions/gate" },
-        "uiux": { "$ref": "#/definitions/gate" },
         "plan": { "$ref": "#/definitions/gate" },
+        "uiux": { "$ref": "#/definitions/gate" },
         "review": { "$ref": "#/definitions/gate" }
       },
       "additionalProperties": false
     },
     "gateDecisions": {
       "type": "object",
-      "description": "Trust decision persisted BEFORE acting on a gate, written ONLY by `morph-spec gate-decision` (decidedAt is server-side). Read by the gate-guard hook to verify the observed action matched the recorded decision.",
-      "propertyNames": { "enum": ["proposal", "uiux", "plan", "review"] },
+      "description": "Trust decision persisted BEFORE acting on a gate, written ONLY by `morph-spec gate-decision` and `morph-spec gate-check` (decidedAt is server-side). Read by the gate-guard hook to verify the observed action matched the recorded decision.",
+      "propertyNames": { "enum": ["plan", "uiux", "review"] },
       "additionalProperties": {
         "type": "object",
         "required": ["pause", "reason", "signals", "trust", "decidedAt"],
@@ -57,49 +56,26 @@
           "reason": { "type": "string", "description": "The signal that drove the decision (or 'nenhum sinal de risco')." },
           "signals": {
             "type": "object",
-            "description": "Risk signals evaluated (free-form): taskCount, evaluatorVerdict, standardsViolations, designSystemDivergence..."
+            "description": "Risk signals evaluated (free-form): sliceCount, planChecks, reviewReports, standardsViolations, designSystemDivergence..."
           },
           "trust": { "type": "string", "enum": ["auto", "manual"] },
           "decidedAt": { "type": "string", "format": "date-time" },
           "mockupsHash": {
             "type": ["string", "null"],
             "description": "uiux only: hash of the 1-design/mockups.md the decision saw (null = no mockup). A pause:false unlocks the auto signature only while the mockup is still this one."
-          }
-        },
-        "additionalProperties": false
-      }
-    },
-    "taskVerifications": {
-      "type": "object",
-      "description": "Deterministic verify results per task, written ONLY by `morph-spec verify` (task scope). updatedAt is server-side; attempts auto-increment. Persisted only from the primary root or the feature's own registered worktree — see verify.js decidePersistence().",
-      "propertyNames": { "pattern": "^T\\d+$" },
-      "additionalProperties": {
-        "type": "object",
-        "required": ["status", "nodes", "attempts", "updatedAt"],
-        "properties": {
-          "status": { "type": "string", "enum": ["pass", "fail"] },
-          "nodes": {
-            "type": "object",
-            "required": ["build", "tests", "validators"],
-            "properties": {
-              "build": { "type": "string", "enum": ["pass", "fail", "skip"] },
-              "tests": { "type": "string", "enum": ["pass", "fail", "skip"] },
-              "validators": { "type": "string", "enum": ["pass", "fail", "skip"] },
-              "e2e": { "type": "string", "enum": ["pass", "fail", "skip"], "description": "Docker bring-up + Playwright specs against the running stack. Absent on entries written before the node existed — which is why it is NOT in `required`." },
-              "evals": { "type": ["string", "null"], "enum": ["pass", "fail", "skip", null], "description": "Eval suites, pulled out of the tests rollup. Written by the SAME function that writes the singular stamp (nodeStatuses in verify.js): the two shapes must stay identical, or a stamp would omit what the history records. null means the project declares no eval node at all — distinct from skip, which means it declares one and this run did not execute it. Absent on entries written before the field existed, which is why it is NOT in required." }
-            },
-            "additionalProperties": false
           },
-          "score": { "type": ["number", "null"], "minimum": 0, "maximum": 10 },
-          "attempts": { "type": "integer", "minimum": 1 },
-          "updatedAt": { "type": "string", "format": "date-time" }
+          "source": {
+            "type": "string",
+            "enum": ["manual", "gate-check"],
+            "description": "Which command decided: `gate-decision` writes manual, `gate-check` writes gate-check. A manual pause:true is sticky: `gate-check` keeps it paused (manual reason, fresh signals); only a new `gate-decision --pause false` clears it."
+          }
         },
         "additionalProperties": false
       }
     },
     "verifications": {
       "type": "object",
-      "description": "Deterministic verify results at feature scope, written ONLY by `morph-spec verify` (feature scope, no task id).",
+      "description": "Deterministic verify results at feature scope, written ONLY by `morph-spec verify`.",
       "properties": {
         "feature": {
           "type": "object",
@@ -118,7 +94,6 @@
               },
               "additionalProperties": false
             },
-            "score": { "type": ["number", "null"], "minimum": 0, "maximum": 10 },
             "attempts": { "type": "integer", "minimum": 1 },
             "updatedAt": { "type": "string", "format": "date-time" }
           },
@@ -129,8 +104,8 @@
     },
     "verification": {
       "type": "object",
-      "description": "The single latest deterministic verify stamp (any scope), written ONLY by `morph-spec verify`. Distinct from `verifications`/`taskVerifications` above (per-scope history with attempts/nodes): this is overwritten by every verify call regardless of scope, carrying just enough to correlate a pass/fail with the exact commit it covers. Primary consumer: `morph-spec gate-check`, which feeds `status` to shouldPauseGate as `verificationStatus` — a red verify pauses the gate (risk-detector.js) — and `nodes.e2e`/`e2eReason` as `e2eStatus`/`e2eReason`, the pair that decides whether an e2e SKIP is a recorded dispensation or an absence of proof (a skip never reddens `status`, so the rollup alone is blind to it). `scope` is the third pause input: a dispensation only counts from a feature-scoped stamp (see the field below). The rest (sha/ts, and the derived `verificationStale`) is audit context.",
-      "required": ["status", "sha", "ts", "scope"],
+      "description": "The single latest deterministic verify stamp, written ONLY by `morph-spec verify`. Distinct from `verifications` above (history with attempts/nodes): this is overwritten by every persisted verify, carrying just enough to correlate a pass/fail with the exact commit it covers. Primary consumer: `morph-spec gate-check`, which feeds `status` to shouldPauseGate as `verificationStatus` — a red verify pauses the gate (risk-detector.js) — and `nodes.e2e`/`e2eReason` as `e2eStatus`/`e2eReason`, the pair that decides whether an e2e SKIP is a recorded dispensation or an absence of proof (a skip never reddens `status`, so the rollup alone is blind to it). The rest (sha/ts, and the derived `verificationStale`) is audit context.",
+      "required": ["status", "sha", "ts"],
       "properties": {
         "status": { "type": "string", "enum": ["pass", "fail"] },
         "nodes": {
@@ -144,31 +119,19 @@
             "evals": {
               "type": ["string", "null"],
               "enum": ["pass", "fail", "skip", null],
-              "description": "Status of the `runner: \"evals\"` entries of nodes.tests.runs[], pulled out of the rollup. The rollup cannot answer what Gate 3 asks: a red eval and a red unit test both read as tests:fail, and an eval SKIPPED at task scope leaves the rollup green. null means this project declares NO eval node - distinct from 'skip', which means it declares one and this run did not execute it; risk-detector.js pauses on the two for different reasons because they call for different actions. Absent on stamps written before this field existed."
+              "description": "Status of the `runner: \"evals\"` entries of nodes.tests.runs[], pulled out of the rollup. The rollup cannot answer what Gate 3 asks: a red eval and a red unit test both read as tests:fail. null means this project declares NO eval node - distinct from 'skip', which means it declares one and this run did not execute it; risk-detector.js pauses on the two for different reasons because they call for different actions. Absent on stamps written before this field existed."
             }
           },
           "additionalProperties": false
         },
         "e2eReason": { "type": ["string", "null"], "description": "The LITERAL reason the e2e node skipped (e2e-check.js's own wording), or null when it did not skip. risk-detector.js's classifyE2eSkip() reads it: 'project does not containerize' / 'does not touch runtime' are legitimate dispensations and pass; 'docker is not available' / 'requested' (--skip-e2e) / anything unclassifiable — null included — are an absence of proof and pause Gate 3. A skip recorded WITHOUT a reason is refused on purpose: a nameless dispensation is a silent no-op." },
         "sha": { "type": ["string", "null"], "description": "HEAD commit SHA at verify time (git rev-parse HEAD); null when not in a git repo or no commits yet." },
-        "ts": { "type": "string", "format": "date-time", "description": "Server-side timestamp, same instant as the corresponding verifications/taskVerifications entry's updatedAt." },
-        "scope": { "type": "string", "description": "'feature', or 'task:<id>' for a task-scoped verify. READ BY THE GATE, not just audit: this stamp is singular and any verify overwrites it, so a 'task:<id>' value at ship time means the last verify was NOT the feature's. risk-detector.js therefore accepts an e2e dispensation ('project'/'scope' in e2eReason) only from scope === 'feature' — a `morph-spec verify {f} {task}` of a task whose group does not touch runtime stamps exactly the legitimate-sounding reason that would otherwise buy Gate 3 for the whole feature (the last task of a feature is typically group: docs). Absent/unknown falls on the safe side, like an unclassifiable reason." },
+        "ts": { "type": "string", "format": "date-time", "description": "Server-side timestamp, same instant as the corresponding verifications entry's updatedAt." },
         "source": { "type": "string", "enum": ["ci"], "description": "Present only when the stamp came from `verify --ci`: the verify --json the project CI uploaded for the pushed commit, judged by the same rules as a local run. Absent = local run." },
         "ciRun": { "type": "string", "description": "URL of the CI run whose artifact wrote this stamp (with source: ci). `sha` is that run's headSha, so verificationStale compares the code CI saw with HEAD." }
       },
       "additionalProperties": false
     },
-    "tasks": {
-      "type": "object",
-      "description": "Aggregate task counters (informational — the source of truth is 2-plan/tasks.json).",
-      "properties": {
-        "total": { "type": "integer", "minimum": 0 },
-        "completed": { "type": "integer", "minimum": 0 },
-        "inProgress": { "type": "integer", "minimum": 0 },
-        "pending": { "type": "integer", "minimum": 0 }
-      },
-      "additionalProperties": true
-    },
     "outputs": {
       "type": "object",
       "description": "Outputs tracked by the state-sync hook: filename → { created, path }.",
@@ -236,7 +199,7 @@
         "approved": { "type": "boolean" },
         "timestamp": { "type": ["string", "null"], "description": "ISO timestamp of the approval/revocation, null while never evaluated." },
         "approvedBy": { "type": ["string", "null"], "description": "\"auto\" (approve/advance --mode auto), \"manual\" (human in the loop), \"policy:{workType}\" (gate stamped at birth by `morph-spec create` per the work type's skippedGates — see src/core/work-types.js; the gate-guard hook only special-cases \"auto\", so policy-stamped gates stay silent to it), a --approver name, or null while never evaluated." },
-        "selfAssessed": { "type": "boolean", "description": "Gate `review` SOMENTE. `true` quando o Gate 3 foi aprovado sem `4-review/evaluator-report.md`, via `morph-spec approve <f> review --self-assessed`. O score composto deveria vir do avaliador independente; esta flag registra a degradação em vez de deixá-la silenciosa, e aparece no `morph-spec list`." }
+        "selfAssessed": { "type": "boolean", "description": "Gate `review` SOMENTE. `true` quando o Gate 3 foi aprovado sem os relatórios de review exigidos (`4-review/verifier.md`, `reviewer.md`, `security.md`), via `morph-spec approve <f> review --self-assessed` ou um \"aprovado\" humano sem eles. O veredito deveria vir dos agentes independentes; esta flag registra a degradação em vez de deixá-la silenciosa, e aparece no `morph-spec list`." }
       },
       "additionalProperties": true
     }

package/framework/skills/README.md

@@ -12,11 +12,10 @@ These are the only skills the harness needs. MORPH.md references them by path.
 
 | Skill                | Purpose                                                              | User-invocable |
 |----------------------|----------------------------------------------------------------------|----------------|
-| `morph-brainstorming` | Business understanding + brownfield scan → proposal.md (Gate 1)     | yes            |
-| `morph-stack-scan`    | Detect stack drift in existing projects, report in stack-scan.md     | yes            |
-| `morph-plan`          | Produce use cases + spec.md + tasks.json (Gate 2)                   | yes            |
-| `morph-implement`     | Execute each task with standard + persona, auto-advance between tasks| no             |
-| `morph-review`        | Final review report with scores + recommendation (Gate 3)            | yes            |
+| `morph-plan`          | Route, scan, interview, write plan.md, plan-check and the plan gate  | yes            |
+| `morph-uiux`          | Optional design branch after the plan gate (mockups + screen checklist) | yes          |
+| `morph-apply`         | Run the plan slices (dispatch, report-check, verify) into the review | yes            |
+| `morph-review`        | Final review report with SHIP/FIX verdict (Gate 3)                   | yes            |
 | `morph-standards`     | Locate and load a specific standard on demand                        | no             |
 
 The legacy `level-0-meta/` and `level-1-workflows/` skill trees were removed

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

@@ -2,9 +2,9 @@
 name: create-umbraco-lp
 description: Guia a criação de uma landing page nova ponta-a-ponta a partir do template MORPH_Umbraco_LP_Template (Umbraco 17 + Next.js): coleta decisões, scaffolda, sobe e valida, customiza branding e módulos, e entrega checklist final.
 version: core
-when-to-invoke: ao iniciar um novo projeto de LP com o template Umbraco genérico
-user-invokable: true
-cliVersion: "8.46.0"
+when_to_use: Use quando for iniciar um novo projeto de LP com o template Umbraco genérico
+user-invocable: true
+cliVersion: "9.0.0"
 stacks:
   - umbraco
 ---

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

@@ -2,9 +2,9 @@
 name: migrate-lp-to-umbraco
 description: Migra uma landing page existente (React/Vite, Next.js estático ou HTML) para o template Umbraco-headless MORPH_Umbraco_LP_Template entregando a LP EXATAMENTE igual à origem (mesmo CSS, imagens, fontes e comportamento) + Umbraco por cima — obtenção automática do template, inventário de seções, lift-and-rewire verbatim de cada seção para módulo editável, conexão do formulário ao backend de leads e gate de paridade determinístico. Repo-agnóstica: roda em qualquer lugar, sem template nem origem pré-baixados.
 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.46.0"
+when_to_use: Use quando o usuário pedir "use /migrate-lp-to-umbraco {projeto}" ou descrever a necessidade de migrar uma LP para Umbraco
+user-invocable: true
+cliVersion: "9.0.0"
 stacks:
   - umbraco
 ---