@polymorphism-tech/morph-spec 8.47.0 → 9.1.0

package/framework/standards/frontend/design-system/premium-finish.md

@@ -3,9 +3,9 @@
 > **Scope:** frontend-design-system
 > **Layer:** 3
 > **Keywords:** premium, polish, typography, film grain, atmosphere, load-in, scrim, legibility over video, accent
-> **Load When:** ui-designer active, or the brief asks for a premium or high-end feel
+> **Load When:** ui-designer active (every surface), or the brief asks for a premium or high-end feel
 
-**Verified against:** Production landing pages, CSS-only techniques, no runtime dependency. Last-verified: 2026-08-21.
+**Verified against:** Production landing pages, CSS-only techniques, no runtime dependency; app patterns from an approved login prototype (2026-10-06). Last-verified: 2026-10-06.
 
 ---
 
@@ -148,6 +148,78 @@ Finish with fresh eyes: open the page as if you were the client. Whatever looks
 
 ---
 
+## Section 8: Patterns For App Screens
+
+The finish is not only for marketing pages. Login, onboarding, the first screen after sign-up, an empty state and a success moment are brand moments inside the product, and a data screen also has to look designed: elegant density, illustrated empty states, skeletons with shimmer, transitions between states. These patterns come from an app login that was approved on first sight after a plain one was rejected.
+
+### Bottom sheet on mobile
+
+On a phone the form lives in a sheet anchored to the bottom, inside the thumb zone, with the brand scene above it. Never the desktop card centered and shrunk.
+
+```css
+.sheet {
+  position: fixed; inset: auto 0 0 0;
+  padding: 12px 20px calc(20px + env(safe-area-inset-bottom));
+  border-radius: 24px 24px 0 0;
+  background: var(--surface);
+  box-shadow: 0 -12px 40px color-mix(in oklab, var(--brand) 18%, transparent);
+}
+.sheet::before {
+  content: ''; display: block; width: 36px; height: 4px; margin: 0 auto 16px;
+  border-radius: 2px; background: var(--border);
+}
+.sheet button, .sheet input { min-height: 44px; }
+```
+
+### Stories-style progress
+
+A sequence of scenes reads like stories: thin segmented bars at the top, each filling while its scene is on. One keyframe, the delay per segment, and the scene swap keyed to the same delays.
+
+```css
+.stories { display: flex; gap: 4px; }
+.stories span { flex: 1; height: 3px; border-radius: 2px; background: color-mix(in oklab, var(--fg) 20%, transparent); overflow: hidden; }
+.stories span::after {
+  content: ''; display: block; height: 100%; background: var(--fg);
+  transform: scaleX(0); transform-origin: left;
+  animation: fill var(--beat) linear forwards;
+  animation-delay: calc(var(--i) * var(--beat));
+}
+@keyframes fill { to { transform: scaleX(1); } }
+```
+
+### Synchronized highlight by `animation-delay`
+
+When a scene card lights up while its story bar runs, both share `--i` and `--beat`. No JavaScript timer: the browser keeps them in step, and pausing is one `animation-play-state: paused` on the parent.
+
+### Scene cards without real data
+
+A card that illustrates the product cycle shows shapes, icons and labels, never a metric. A made-up number on a real screen reads as a real number ("R$ 12.430 recovered") and becomes a claim nobody can back. Use bars without values, avatars without names, a check without a count.
+
+### Dot grid faded with `mask-image`
+
+Texture for a hero or a sheet backdrop, cheaper than an image and on brand:
+
+```css
+.dots {
+  background-image: radial-gradient(color-mix(in oklab, var(--fg) 22%, transparent) 1px, transparent 1px);
+  background-size: 16px 16px;
+  mask-image: radial-gradient(ellipse at 50% 30%, #000 30%, transparent 75%);
+}
+```
+
+### Static version for reduced motion
+
+`prefers-reduced-motion: reduce` gets a composed still frame (the best scene, every bar full, the highlight on), not the first frame of a stopped animation.
+
+```css
+@media (prefers-reduced-motion: reduce) {
+  .stories span::after { animation: none; transform: scaleX(1); }
+  .scene { animation: none; opacity: 1; }
+}
+```
+
+---
+
 ## Checklist
 
 - [ ] Display font chosen from the brand, not from stack defaults or the AI-tell list
@@ -157,4 +229,7 @@ Finish with fresh eyes: open the page as if you were the client. Whatever looks
 - [ ] Directional scrim plus text-shadow on every text-over-media block
 - [ ] Accent used in three places or fewer
 - [ ] Details swept: scrollbar, selection, hairlines, hover micro-transitions
+- [ ] App screen: mobile designed on its own (bottom sheet, thumb zone, 44px targets), never the desktop stacked
+- [ ] No invented number or data on a real screen
+- [ ] Reduced motion gets a composed static frame
 - [ ] Fresh-eyes pass done, and it does not read as a template

package/framework/standards/infrastructure/neon/neon-pgvector.md

@@ -19,7 +19,7 @@ Stack: .NET VSA + Neon Serverless Postgres. For the end-to-end RAG pipeline (ing
 - ALWAYS call `UseVector()` on the `UseNpgsql(...)` options builder (EF Core); `NpgsqlDataSourceBuilder.UseVector()` is only for raw Npgsql
 - ALWAYS register the `vector` extension in `OnModelCreating` (`HasPostgresExtension("vector")`)
 - Map vector properties as `Pgvector.Vector` -- EF Core does not map `float[]` or `ReadOnlyMemory<float>` to the `vector` column
-- Query through the `ApplicationDbContext` in the slice handler with the `CosineDistance`/`L2Distance`/`MaxInnerProduct` LINQ translations -- no repository class, no raw SQL from C# without a `decisions.md` justification
+- Query through the `ApplicationDbContext` in the slice handler with the `CosineDistance`/`L2Distance`/`MaxInnerProduct` LINQ translations -- no repository class, no raw SQL from C# without a `plan.md` (`## Decisões`) justification
 - IDs come from the app (`Guid.CreateVersion7()`), never from a `gen_random_uuid()` column default
 
 ## Enable pgvector
@@ -39,7 +39,7 @@ CREATE EXTENSION IF NOT EXISTS vector;
 <PackageReference Include="Pgvector.EntityFrameworkCore" Version="0.3.0" />
 ```
 
-`Pgvector.EntityFrameworkCore` 0.3.0 requires `Npgsql.EntityFrameworkCore.PostgreSQL` >= 9.0.1 and brings `Pgvector` (the `Vector` type and the raw-Npgsql plugin) transitively. The configuration below maps each column to the snake_case names of `backend/database/postgresql/database.md` (`embedding`, `created_at`) with `HasColumnName`; without it EF creates `"Embedding"`, `"CreatedAt"` and every SQL snippet below would have to quote PascalCase names. (A project that wants this for every entity can add `EFCore.NamingConventions` and `UseSnakeCaseNamingConvention()` once, instead of per column -- a project-wide decision for `decisions.md`.)
+`Pgvector.EntityFrameworkCore` 0.3.0 requires `Npgsql.EntityFrameworkCore.PostgreSQL` >= 9.0.1 and brings `Pgvector` (the `Vector` type and the raw-Npgsql plugin) transitively. The configuration below maps each column to the snake_case names of `backend/database/postgresql/database.md` (`embedding`, `created_at`) with `HasColumnName`; without it EF creates `"Embedding"`, `"CreatedAt"` and every SQL snippet below would have to quote PascalCase names. (A project that wants this for every entity can add `EFCore.NamingConventions` and `UseSnakeCaseNamingConvention()` once, instead of per column -- a project-wide decision for `plan.md` (`## Decisões`).)
 
 ### Entity Definition
 
@@ -196,9 +196,9 @@ public sealed class SearchDocumentsHandler(
 
 Storing an embedding is an ordinary EF write in the handler that owns the document: `document.Embedding = new Vector(await embeddings.GenerateVectorAsync(text, cancellationToken: ct));` followed by `SaveChangesAsync`. No `UPDATE ... SET embedding` from C#.
 
-### SQL Functions (only with a `decisions.md` justification)
+### SQL Functions (only with a `plan.md` (`## Decisões`) justification)
 
-When the query must live in the database (called from several apps, or a hybrid score the LINQ translation cannot express), a SQL function is acceptable -- record why in `decisions.md`, call it through EF Core with interpolated parameters, and keep the same distance rules:
+When the query must live in the database (called from several apps, or a hybrid score the LINQ translation cannot express), a SQL function is acceptable -- record why in `plan.md` (`## Decisões`), call it through EF Core with interpolated parameters, and keep the same distance rules:
 
 ```sql
 CREATE OR REPLACE FUNCTION match_documents(
@@ -218,7 +218,7 @@ $$;
 
 ## Hybrid Search (Vector + Full-Text)
 
-Blends the vector score with `ts_rank`. Same rule as above: a SQL function, justified in `decisions.md`.
+Blends the vector score with `ts_rank`. Same rule as above: a SQL function, justified in `plan.md` (`## Decisões`).
 
 ```sql
 CREATE OR REPLACE FUNCTION hybrid_search(

package/framework/standards/integration/mcp/mcp-tools.md

@@ -195,14 +195,14 @@ Fallback: WebSearch for library capabilities.
 
 | Tool | Use Case | Example |
 |------|----------|---------|
-| **GitHub CLI (`gh`)** | Create issues from tasks, link to milestone | `gh issue create` (Bash) |
+| **GitHub CLI (`gh`)** | Create issues from slices, link to milestone | `gh issue create` (Bash) |
 | **Context7** | Estimate complexity based on library docs | `mcp__context7__query-docs()` |
 
 ```bash
-# Create GitHub issues from tasks.json (if team uses GitHub Projects)
-# — one `gh issue create` per task, iterating tasks.json:
-gh issue create --title "T001: Create Entity Lead" \
-  --body "description + doneCriteria da task" \
+# Create GitHub issues from the plan's slices (if team uses GitHub Projects)
+# — one `gh issue create` per slice of .morph/features/{f}/2-plan/checks.json:
+gh issue create --title "F1: Create Entity Lead" \
+  --body "fatia F1 do plan.md + cenários que ela cobre" \
   --label "backend" --milestone "feature-x"
 ```
 
@@ -234,7 +234,7 @@ psql $(neonctl connection-string) -c "SELECT column_name, data_type FROM informa
 psql $(neonctl connection-string) -c "SELECT policyname, cmd, qual FROM pg_policies WHERE tablename = 'leads'"
 ```
 
-Look up the API while coding, then smoke test the deployed feature: the snapshot shows whether the page renders, the console messages catch JavaScript errors and failed API calls, and the screenshot goes to `recap.md`. Vercel covers deployment status, logs and environment variables.
+Look up the API while coding, then smoke test the deployed feature: the snapshot shows whether the page renders, the console messages catch JavaScript errors and failed API calls, and the screenshot goes to the slice report (`3-implement/reports/F{n}.md`). Vercel covers deployment status, logs and environment variables.
 
 ```javascript
 const docs = await mcp__context7__query-docs({
@@ -329,7 +329,7 @@ await mcp__playwright__browser_file_upload({ ref: "s1e20", paths: ["/path/to/fil
 | Implement (7) | Smoke test deployed features | `browser_navigate` + `browser_click` + `browser_snapshot` |
 | Implement (7) | Verify form flows end-to-end | `browser_fill_form` + `browser_click` + `browser_snapshot` |
 | Implement (7) | Check console errors after deploy | `browser_navigate` + `browser_console_messages` |
-| Implement (7) | Screenshot for recap.md | `browser_take_screenshot` |
+| Implement (7) | Screenshot for the slice report | `browser_take_screenshot` |
 
 ---
 

package/framework/templates/CLAUDE.md.core.template

@@ -6,7 +6,7 @@
 
 VSA + .NET 10 + EF Core + Neon (Postgres) + Microsoft Agent Framework + Next.js (App Router) + Tailwind + Framer Motion + Shadcn + Hangfire (quando necessário).
 
-Padrões proibidos por padrão: `Guid.NewGuid()` (use `Guid.CreateVersion7()`), classes não-sealed sem justificativa, exceptions como fluxo de controle, camada de Service/Manager entre handler e dados, repository genérico (`IRepository<T>`/`IUnitOfWork`), SQL cru sem justificativa. Acesso a dados: `ApplicationDbContext` direto no slice (`DbSet<T>` já é repository, `DbContext` já é unit of work); para concorrência ou SQL específico, store dedicado hand-written com justificativa em `decisions.md`.
+Padrões proibidos por padrão: `Guid.NewGuid()` (use `Guid.CreateVersion7()`), classes não-sealed sem justificativa, exceptions como fluxo de controle, camada de Service/Manager entre handler e dados, repository genérico (`IRepository<T>`/`IUnitOfWork`), SQL cru sem justificativa. Acesso a dados: `ApplicationDbContext` direto no slice (`DbSet<T>` já é repository, `DbContext` já é unit of work); para concorrência ou SQL específico, store dedicado hand-written com justificativa em `plan.md` (`## Decisões`).
 
 ## Harness
 
@@ -18,5 +18,5 @@ morph-spec NLH — leia `.morph/framework/MORPH.md` ao iniciar cada sessão. Em
 
 ## Slash commands
 
-- `/morph-proposal {feature}` — entendimento de negócio + use cases, spec e tasks (Gates 1 e 2)
-- `/morph-apply {feature}` — execução autônoma das tarefas + review (Gate 3)
+- `/morph-plan {feature}` — entrevista, `plan.md`, `plan-check` e gate do plano
+- `/morph-apply {feature}` — fatias do plano, `verify` e review (Gate 3)

package/framework/templates/README.md

@@ -18,8 +18,7 @@ through the registry, and this README never repeats a path the registry already
 
 ```
 framework/templates/
-├── docs/              # Phase documents (proposal, spec, ui-*)
-├── feature/           # decisions.md, recap.md
+├── docs/              # plan.md (the plan's single source) and ui-mockups.md
 ├── context/           # ARCHITECTURE.md, design-system.md
 │
 ├── code/              # Code templates, by technology
@@ -38,7 +37,7 @@ framework/templates/
 ├── integrations/      # asaas-client, asaas-webhook, neon-auth-config
 ├── ui/                # design-system.css
 ├── meta-prompts/      # fusion, squad-leaders, validators
-├── examples/          # spec-examples.md, design-system-examples.md
+├── examples/          # design-system-examples.md
 └── REGISTRY.json      # template metadata — the index every consumer reads
 ```
 

package/framework/templates/REGISTRY.json

@@ -29,84 +29,18 @@
   ],
   "templates": [
     {
-      "id": "proposal",
+      "id": "plan",
       "kind": "template",
-      "name": "Feature Proposal",
-      "path": "docs/proposal.md",
-      "location": "framework",
-      "category": "documentation",
-      "phase": "proposal",
-      "required": true,
-      "description": "Feature proposal with overview, problem statement, solution approach, and cost estimates",
-      "outputName": "proposal.md",
-      "placeholders": [
-        "AUTHOR",
-        "DATE",
-        "STACK"
-      ],
-      "stackSpecific": false,
-      "engine": "handlebars",
-      "deprecated": false,
-      "technology": "handlebars",
-      "validatePlaceholders": true
-    },
-    {
-      "id": "spec",
-      "kind": "template",
-      "name": "Technical Specification",
-      "path": "docs/spec.md",
+      "name": "Feature Plan",
+      "path": "docs/plan.md",
       "location": "framework",
       "category": "documentation",
       "phase": "plan",
       "required": true,
-      "description": "Detailed technical spec with architecture, data model, API contracts",
-      "outputName": "spec.md",
+      "description": "Single source of a feature: problem, scenarios (Cn with proof), decisions (ADRs), reuse, slices (Fn) and errata — parsed by morph-spec plan-check into checks.json",
+      "outputName": "plan.md",
       "placeholders": [
-        "DATE",
-        "FEATURE_NAME",
-        "STACK"
-      ],
-      "stackSpecific": false,
-      "engine": "handlebars",
-      "deprecated": false,
-      "technology": "handlebars",
-      "validatePlaceholders": true
-    },
-    {
-      "id": "decisions",
-      "kind": "template",
-      "name": "Architecture Decision Records",
-      "path": "feature/decisions.md",
-      "location": "framework",
-      "category": "documentation",
-      "phase": "plan",
-      "required": true,
-      "description": "ADR format for documenting architectural decisions with context, alternatives, consequences",
-      "outputName": "decisions.md",
-      "placeholders": [
-        "DATE"
-      ],
-      "stackSpecific": false,
-      "engine": "handlebars",
-      "deprecated": false,
-      "technology": "handlebars",
-      "validatePlaceholders": true
-    },
-    {
-      "id": "recap",
-      "kind": "template",
-      "name": "Feature Recap",
-      "path": "feature/recap.md",
-      "location": "framework",
-      "category": "documentation",
-      "phase": "implement",
-      "required": true,
-      "description": "Post-implementation summary with deliverables, metrics, lessons learned",
-      "outputName": "recap.md",
-      "placeholders": [
-        "DATE",
-        "FEATURE_NAME",
-        "STACK"
+        "FEATURE_NAME"
       ],
       "stackSpecific": false,
       "engine": "handlebars",
@@ -121,7 +55,7 @@
       "path": "context/ARCHITECTURE.md",
       "location": "framework",
       "category": "context",
-      "phase": "proposal",
+      "phase": "plan",
       "required": false,
       "description": "Auto-scanned architecture context with entities, endpoints, pages, components, integrations, database tables, and package versions",
       "outputName": "ARCHITECTURE.md",
@@ -132,24 +66,6 @@
       "technology": "handlebars",
       "validatePlaceholders": true
     },
-    {
-      "id": "spec-examples",
-      "kind": "template",
-      "name": "Spec Examples",
-      "path": "examples/spec-examples.md",
-      "location": "framework",
-      "category": "examples",
-      "phase": null,
-      "required": false,
-      "description": "Example technical specs for reference",
-      "outputName": null,
-      "placeholders": [],
-      "stackSpecific": false,
-      "engine": null,
-      "deprecated": false,
-      "technology": null,
-      "validatePlaceholders": true
-    },
     {
       "id": "design-system-examples",
       "kind": "template",
@@ -263,7 +179,7 @@
       "path": "code/dotnet/contracts/README.md",
       "location": "framework",
       "category": "documentation",
-      "phase": "design",
+      "phase": "implement",
       "required": false,
       "description": "Documentation for contract patterns and usage",
       "outputName": "README.md",
@@ -284,7 +200,7 @@
       "path": "code/dotnet/contracts/contracts-vsa.cs",
       "location": "framework",
       "category": "code",
-      "phase": "design",
+      "phase": "implement",
       "required": false,
       "description": "Feature slice completo: Abstractions, Entity, Errors, e um slice de operação (Request, Response, Validator, Handler, Endpoint). Padrão KanaiyaKatarmal (.NET 10, Minimal APIs, EF Core 10, FluentValidation 12, Scrutor 7).",
       "outputName": "contracts.cs",
@@ -306,7 +222,7 @@
       "path": "code/typescript/contracts.ts",
       "location": "framework",
       "category": "code",
-      "phase": "design",
+      "phase": "implement",
       "required": false,
       "description": "TypeScript type definitions and interfaces",
       "outputName": "contracts.ts",
@@ -614,71 +530,6 @@
       "technology": "handlebars",
       "validatePlaceholders": true
     },
-    {
-      "id": "ui-flows",
-      "kind": "template",
-      "name": "UI Flows",
-      "path": "docs/ui-flows.md",
-      "location": "framework",
-      "category": "documentation",
-      "phase": "uiux",
-      "required": false,
-      "description": "User flows and interaction patterns with state diagrams and edge cases",
-      "outputName": "flows.md",
-      "placeholders": [
-        "DATE",
-        "FEATURE_NAME"
-      ],
-      "stackSpecific": false,
-      "engine": "handlebars",
-      "deprecated": false,
-      "technology": "handlebars",
-      "validatePlaceholders": true
-    },
-    {
-      "id": "ui-components",
-      "kind": "template",
-      "name": "UI Components",
-      "path": "docs/ui-components.md",
-      "location": "framework",
-      "category": "documentation",
-      "phase": "uiux",
-      "required": false,
-      "description": "Component specifications mapping UI elements to shadcn/ui components with props and events",
-      "outputName": "components.md",
-      "placeholders": [
-        "DATE",
-        "FEATURE_NAME",
-        "STACK"
-      ],
-      "stackSpecific": false,
-      "engine": "handlebars",
-      "deprecated": false,
-      "technology": "handlebars",
-      "validatePlaceholders": true
-    },
-    {
-      "id": "ui-design-system",
-      "kind": "template",
-      "name": "UI Design System",
-      "path": "docs/ui-design-system.md",
-      "location": "framework",
-      "category": "documentation",
-      "phase": "uiux",
-      "required": false,
-      "description": "Design system documentation with color palette, typography, spacing, and semantic tokens",
-      "outputName": "design-system.md",
-      "placeholders": [
-        "DATE",
-        "FEATURE_NAME",
-        "PROJECT_NAME"
-      ],
-      "stackSpecific": false,
-      "engine": "handlebars",
-      "deprecated": false,
-      "technology": "handlebars",
-      "validatePlaceholders": true
-    },
     {
       "id": "github-workflow-dotnet-build",
       "kind": "template",
@@ -687,7 +538,7 @@
       "location": "framework",
       "category": "infrastructure",
       "technology": "github-actions",
-      "phase": "build",
+      "phase": "implement",
       "required": false,
       "description": "Reusable workflow for building .NET applications with restore, build, test, coverage",
       "outputName": "dotnet-build.yml",
@@ -711,7 +562,7 @@
       "location": "framework",
       "category": "infrastructure",
       "technology": "github-actions",
-      "phase": "build",
+      "phase": "implement",
       "required": false,
       "description": "Reusable workflow for building and pushing Docker images to registry",
       "outputName": "docker-build-push.yml",
@@ -733,7 +584,7 @@
       "location": "framework",
       "category": "infrastructure",
       "technology": "github-actions",
-      "phase": "deploy",
+      "phase": "implement",
       "required": false,
       "description": "Reusable workflow for deploying to Coolify via SSH (API is not publicly exposed)",
       "outputName": "deploy-coolify.yml",
@@ -755,7 +606,7 @@
       "location": "framework",
       "category": "infrastructure",
       "technology": "github-actions",
-      "phase": "build",
+      "phase": "implement",
       "required": false,
       "description": "Composite action for building and pushing Docker images",
       "outputName": "action.yml",
@@ -777,7 +628,7 @@
       "location": "framework",
       "category": "infrastructure",
       "technology": "github-actions",
-      "phase": "deploy",
+      "phase": "implement",
       "required": false,
       "description": "Composite action for polling health endpoint until ready",
       "outputName": "action.yml",
@@ -1460,21 +1311,6 @@
         "TIMESTAMP"
       ],
       "validatePlaceholders": true
-    },
-    {
-      "id": "tasks-template",
-      "kind": "template",
-      "consumption": "reference",
-      "name": "tasks.json",
-      "path": "tasks.template.json",
-      "category": "context",
-      "phase": null,
-      "outputName": null,
-      "description": "Initial tasks.json scaffold",
-      "engine": "handlebars",
-      "deprecated": false,
-      "placeholders": [],
-      "validatePlaceholders": true
     }
   ]
 }

package/framework/templates/docs/plan.md

@@ -0,0 +1,72 @@
+# Plano — {{FEATURE_NAME}}
+
+<!-- Fonte única da feature. `morph-spec plan-check {{FEATURE_NAME}}` lê este arquivo e grava 2-plan/checks.json.
+     Depois do gate plan, o corpo congela: fato errado sobre o código vai em ## Errata (append-only). -->
+
+## Problema
+
+<O que dói hoje, para quem, e como se percebe. Duas a cinco frases.>
+
+## Fora de escopo
+
+- <o que esta feature deliberadamente não faz>
+
+## Suposições não confirmadas
+
+- <o que foi assumido sem prova; "nenhuma" vale>
+
+## Cenários
+
+<!-- Um cenário por comportamento observável. `prova:` é teste | e2e | eval | manual.
+     Cenário que fala de arquivo, grep ou texto exige a linha "> Por que artefato:" logo abaixo. -->
+
+- **C1** — Dado <estado>, quando <ação>, então <resultado observável>.
+  prova: teste
+
+## Decisões
+
+### ADR-001 — <título>
+**Alcance:** feature
+
+<Contexto, decisão e consequência. `projeto` quando a decisão vale além desta feature.>
+
+### Conflitos com o acervo
+
+<!-- ADR do índice (.morph/specs/adrs/) que este plano contradiz: "nenhum", ou a tabela abaixo fora do bloco.
+     O finish aplica cada linha: total retira o ADR do índice; parcial o mantém com o escopo onde ainda vale.
+```
+| ADR | Mudança | Escopo em que o antigo ainda vale |
+|---|---|---|
+| {feature}/ADR-{nnn} | parcial | <onde o antigo ainda vale> |
+| {feature}/ADR-{nnn} | total | — |
+```
+-->
+
+nenhum
+
+## Arquitetura
+
+<Onde o código entra, o que conversa com o quê. Diagrama só se ajudar.>
+
+## Reuso
+
+| conceito | veredito | alvo | why |
+|---|---|---|---|
+| <conceito> | REUSAR | <arquivo ou símbolo existente> | |
+
+## Fatias
+
+<!-- Uma fatia = uma unidade de entrega (com ou sem dispatch), relatório em 3-implement/reports/Fn.md.
+     arquivos ≤ 8; superfície e depende são opcionais; toda Cn é coberta por alguma fatia. -->
+
+### F1 — <título>
+- persona: dotnet-senior
+- standards: <id>
+- arquivos: <caminho/a.cs>, <caminho/b.cs>
+- cobre: C1
+
+## Contrato de implementação
+
+<Assinaturas, records, enums e rotas que as fatias precisam honrar.>
+
+## Errata

package/framework/templates/docs/ui-mockups.md

@@ -18,6 +18,10 @@
 
 ## Tela: {Primary Screen}
 
+**Protótipo:** 1-design/prototipos/{tela}.html
+
+O protótipo renderizado é a fonte visual da tela; os prints `{tela}-1280.png` e `{tela}-390.png` ficam ao lado dele, e sem os três arquivos o Gate uiux pausa. O layout em texto abaixo é opcional.
+
 ### Desktop Layout
 
 ```

package/framework/templates/dotnet/ai-kit/README.md

@@ -58,15 +58,7 @@ dotnet test  --solution Morph.AiKit.sln -c Release --no-build
 > do `morph-spec verify`); por isso nenhum chamador repassa a flag. Ao adicionar
 > testes, suba o piso — `test/framework/ai-kit-ci-packaging.test.js` reprova um
 > piso que ficou para trás da contagem de `[Fact]`/`[Theory]`.
-> **Consequência para o recorte por task:** `--minimum-expected-tests 1` na
-> linha de comando não sobrescreve o valor do projeto (medido: o recorte verde
-> sai 9 do mesmo jeito), mas a propriedade global do MSBuild sim. Por isso
-> `morph-spec verify {f} {task}` estreita este projeto repassando
-> `"-p:TestingPlatformCommandLineArguments=…"` com o valor do `.csproj` e o piso
-> em 1 — verde sai 0, zero testes segue saindo 8, nada recompila (issue #114).
-> Mantenha o piso **nesse** elemento, literal (sem `Condition`, sem `$(…)`, sem
-> outra declaração da propriedade em `Directory.Build.*`): em qualquer outra
-> forma o recorte volta a rodar o nó inteiro.
+
 
 > **`dotnet test` precisa rodar COM O CWD DENTRO deste diretório.** O opt-in do
 > Microsoft.Testing.Platform (que `xunit.v3` 4.x usa) vive em `global.json`, e o

package/framework/templates/dotnet/ai-kit/tests/Morph.AiKit.Tests/Morph.AiKit.Tests.csproj

@@ -30,16 +30,6 @@
       de workflow. Uma unica verdade: nenhum chamador repassa a flag na linha de
       comando, porque repassa-la duplicaria a opcao.
 
-      Consequencia para o recorte por task (`morph-spec verify {f} {task}`): a
-      mesma opcao com valor 1 na linha de comando NAO sobrescreve o valor do
-      projeto (medido: o recorte verde sai 9 do mesmo jeito), mas a propriedade
-      global do MSBuild sim. O recorte estreita este projeto repassando
-      "-p:TestingPlatformCommandLineArguments=" com ESTE valor e o piso em 1
-      (issue #114: verde sai 0, zero testes segue saindo 8, nada recompila). Por
-      isso o piso fica NESTE elemento, literal: sem Condition, sem $(...), sem
-      outra declaracao da propriedade em Directory.Build.* — em qualquer outra
-      forma o recorte volta a rodar o no inteiro.
-
       O numero e o total de CASOS EXECUTADOS (275), nao de atributos nem de casos
       DESCOBERTOS (276): os [Theory] expandem, e um caso IGNORADO nao conta para o piso — a
       suite descobre 276 e executa 275, porque o semeador da cache exemplar de eval

package/framework/templates/meta-prompts/squad-leaders/backend-squad.md

@@ -78,7 +78,7 @@ Backend deliverables typically include:
 2. Create migrations before writing service logic
 3. Implement services with proper unit-testable interfaces
 4. Wire up API endpoints last (depends on services)
-5. After every 3 tasks, persist completed tasks to `tasks.json` (`status`/`outputs`/`notes` only) and run the checkpoint
+5. After every 3 slices, write each finished slice's report (`3-implement/reports/F{n}.md`) and run the checkpoint
 6. If blocked (compilation error, migration conflict), document and continue with next unblocked task
 
 ## Report Back When Done

package/framework/templates/meta-prompts/squad-leaders/frontend-squad.md

@@ -72,7 +72,7 @@ Frontend deliverables typically include:
 2. Build reusable sub-components before composing pages
 3. Wire up API calls/services last (after UI is structured)
 4. Test each component with loading + error + empty states
-5. After every 3 tasks, persist completed tasks to `tasks.json` (`status`/`outputs`/`notes` only) and run the checkpoint
+5. After every 3 slices, write each finished slice's report (`3-implement/reports/F{n}.md`) and run the checkpoint
 
 ## Report Back When Done
 Provide a summary of:

package/framework/templates/meta-prompts/squad-leaders/squad-leader.md

@@ -32,7 +32,7 @@ You are a **Squad Leader** in the MORPH-SPEC agent hierarchy.
 ## How to Work
 1. Read your standards carefully before starting
 2. Implement each task in order (respecting dependencies)
-3. After every 3 tasks, persist completed tasks to `tasks.json` (`status`/`outputs`/`notes` only) and run the checkpoint
+3. After every 3 slices, write each finished slice's report (`3-implement/reports/F{n}.md`) and run the checkpoint
 4. If blocked, document the blocker and continue with the next unblocked task
 5. Report completion with: files created, any blockers, checkpoint results