@polymorphism-tech/morph-spec 8.46.0 → 9.0.0

package/framework/hooks/shared/tasks-validator.js

@@ -1,111 +0,0 @@
-/**
- * tasks-validator.js — minimal hook-side schema validation for tasks.json.
- *
- * Mirrors VALID_STATUS / VALID_EFFORT from src/lib/tasks/tasks-json-parser.js.
- * Hooks are installed standalone into target projects (.morph/framework/hooks/),
- * so they cannot import from src/ — the enum lives here, duplicated on purpose
- * and covered by tests on both sides.
- */
-
-export const VALID_TASK_STATUS = ['pending', 'in_progress', 'done', 'skipped', 'blocked'];
-export const VALID_TASK_EFFORT = ['S', 'M', 'L', 'XL'];
-
-/**
- * Validate the parts of a tasks.json document that hooks care about:
- * a tasks[] array whose entries carry a valid status (and effort, when set).
- * The production failure this guards: a leaf agent writing status "completed"
- * (not in the enum) without any validation.
- *
- * @param {object} doc - parsed tasks.json
- * @returns {{ valid: boolean, errors: string[] }}
- */
-/** Human-readable type name for error messages ('array', not 'object'). */
-function typeName(value) {
-  return Array.isArray(value) ? 'array' : typeof value;
-}
-
-export function validateTasksDoc(doc) {
-  if (!doc || typeof doc !== 'object' || !Array.isArray(doc.tasks)) {
-    return { valid: false, errors: ['tasks.json must be an object with a tasks[] array'] };
-  }
-
-  const errors = [];
-  for (const task of doc.tasks) {
-    const id = task?.id ?? '?';
-    if (!VALID_TASK_STATUS.includes(task?.status)) {
-      errors.push(`task '${id}': invalid status '${task?.status}' (valid: ${VALID_TASK_STATUS.join(', ')})`);
-    }
-    if (task?.effort !== undefined && !VALID_TASK_EFFORT.includes(task.effort)) {
-      errors.push(`task '${id}': invalid effort '${task.effort}' (valid: ${VALID_TASK_EFFORT.join(', ')})`);
-    }
-    // Mutable-field type checks with the exact field/value in the message —
-    // a malformed notes/outputs used to surface as the misleading generic
-    // "notes is empty" downstream (MORPH_GHLBrain 2026-07-11).
-    if (task?.notes !== undefined && typeof task.notes !== 'string') {
-      errors.push(`task '${id}': 'notes' must be a string (got ${typeName(task.notes)})`);
-    }
-    if (task?.outputs !== undefined) {
-      if (!Array.isArray(task.outputs)) {
-        errors.push(`task '${id}': 'outputs' must be an array of path strings (got ${typeName(task.outputs)})`);
-      } else {
-        task.outputs.forEach((entry, i) => {
-          if (typeof entry !== 'string') {
-            errors.push(`task '${id}': outputs[${i}] must be a string path (got ${typeName(entry)})`);
-          }
-        });
-      }
-    }
-  }
-  return { valid: errors.length === 0, errors };
-}
-
-/**
- * Planned-vs-real outputs divergence: tasks whose `outputs` changed relative
- * to the previous document but whose `notes` is still empty. The divergence
- * itself is legitimate (outputs is a mutable progress field) — shipping it
- * without an explanatory note is what gets flagged.
- *
- * @param {object} oldDoc - parsed previous tasks.json
- * @param {object} newDoc - parsed proposed tasks.json
- * @returns {string[]} human-readable violation messages (empty = OK)
- */
-/** Compact outputs rendering for messages, capped so huge arrays stay readable. */
-function fmtOutputs(outputs) {
-  const s = JSON.stringify(outputs ?? []);
-  return s.length > 120 ? s.slice(0, 117) + '...' : s;
-}
-
-export function outputsDivergenceViolations(oldDoc, newDoc) {
-  const violations = [];
-  const oldById = new Map((oldDoc?.tasks ?? []).map(t => [t.id, t]));
-
-  for (const task of newDoc?.tasks ?? []) {
-    const old = oldById.get(task.id);
-    if (!old) continue;
-    const outputsChanged =
-      JSON.stringify(old.outputs ?? []) !== JSON.stringify(task.outputs ?? []);
-    if (!outputsChanged) continue;
-
-    // A filled string note explains the divergence — done.
-    if (typeof task.notes === 'string' && task.notes.trim().length > 0) continue;
-
-    // Root-cause specific messages: a malformed notes value is a DIFFERENT
-    // failure than a missing one — claiming "notes is empty" when the agent
-    // just wrote an array reads as a false positive and burns a retry cycle.
-    if (task.notes !== undefined && typeof task.notes !== 'string') {
-      violations.push(
-        `task '${task.id}': outputs diverged from the plan and 'notes' is not a string ` +
-        `(got ${typeName(task.notes)}) — write the explanation as a single string in 'notes'`
-      );
-      continue;
-    }
-
-    violations.push(
-      `task '${task.id}': outputs diverged from the plan ` +
-      `(${fmtOutputs(old.outputs)} → ${fmtOutputs(task.outputs)}) but 'notes' is empty — ` +
-      `record why in 'notes' in the same edit. ` +
-      `Deletions and annotations belong in 'notes', not in 'outputs' (outputs = produced paths only).`
-    );
-  }
-  return violations;
-}

package/framework/rubrics/backend.json

@@ -1,41 +0,0 @@
-{
-  "id": "backend",
-  "version": "1.1.0",
-  "description": "Backend-focused rubric. Higher weight on architecture, security, and package health. Deterministic-validator weights for the verify validators node; the score is informational — the node fails on validator errors.",
-  "categories": {
-    "functionality": {
-      "weight": 0.25,
-      "validators": ["contract-compliance"],
-      "description": "Core feature correctness and contract compliance"
-    },
-    "code_quality": {
-      "weight": 0.25,
-      "validators": ["architecture", "reuse", "code-budget"],
-      "description": "Architecture patterns, dependency direction, code structure, reuse of what the codebase already has, and comment and test budget"
-    },
-    "design_ui": {
-      "weight": 0.05,
-      "validators": ["design-system", "css", "contrast", "nextjs-component"],
-      "description": "Design system compliance (minimal weight for backend projects)"
-    },
-    "security": {
-      "weight": 0.15,
-      "validators": [],
-      "description": "Security posture (agent-evaluated, no automated validator)"
-    },
-    "packages": {
-      "weight": 0.20,
-      "validators": ["packages"],
-      "description": "Dependency health, version compatibility, and deprecated packages"
-    },
-    "maf_compliance": {
-      "weight": 0.10,
-      "validators": [],
-      "description": "MAF agent compliance (agent-evaluated, applies only when the feature touches AI agents): Microsoft.Agents.AI GA packages used; Model Registry alias referenced not hardcoded models; structured output for pipelined agents; prompts from DB not hardcoded; no Semantic Kernel; no hosted agent services."
-    }
-  },
-  "thresholds": {
-    "approve": 9.0,
-    "retry": 6.0
-  }
-}

package/framework/rubrics/default.json

@@ -1,36 +0,0 @@
-{
-  "id": "default",
-  "version": "1.1.0",
-  "description": "Default rubric for general-purpose projects. Balanced weights across all categories. Deterministic-validator weights for the verify validators node; the score is informational — the node fails on validator errors.",
-  "categories": {
-    "functionality": {
-      "weight": 0.30,
-      "validators": ["contract-compliance"],
-      "description": "Core feature correctness and contract compliance"
-    },
-    "code_quality": {
-      "weight": 0.25,
-      "validators": ["architecture", "reuse", "code-budget"],
-      "description": "Architecture patterns, code structure, reuse of what the codebase already has, and comment and test budget"
-    },
-    "design_ui": {
-      "weight": 0.15,
-      "validators": ["design-system", "css", "contrast", "nextjs-component"],
-      "description": "Design system compliance, CSS quality, and UI correctness"
-    },
-    "security": {
-      "weight": 0.15,
-      "validators": [],
-      "description": "Security posture (agent-evaluated, no automated validator)"
-    },
-    "packages": {
-      "weight": 0.15,
-      "validators": ["packages"],
-      "description": "Dependency health and compatibility"
-    }
-  },
-  "thresholds": {
-    "approve": 9.0,
-    "retry": 6.0
-  }
-}

package/framework/rubrics/frontend.json

@@ -1,36 +0,0 @@
-{
-  "id": "frontend",
-  "version": "1.1.0",
-  "description": "Frontend-focused rubric. Higher weight on design system compliance and UI quality. Deterministic-validator weights for the verify validators node; the score is informational — the node fails on validator errors.",
-  "categories": {
-    "functionality": {
-      "weight": 0.25,
-      "validators": ["contract-compliance"],
-      "description": "Core feature correctness and contract compliance"
-    },
-    "code_quality": {
-      "weight": 0.15,
-      "validators": ["architecture", "reuse", "code-budget"],
-      "description": "Architecture patterns, code structure, reuse of what the codebase already has, and comment and test budget"
-    },
-    "design_ui": {
-      "weight": 0.35,
-      "validators": ["design-system", "css", "contrast", "nextjs-component"],
-      "description": "Design system compliance, CSS quality, contrast ratios, and component correctness"
-    },
-    "security": {
-      "weight": 0.10,
-      "validators": [],
-      "description": "Security posture (agent-evaluated, no automated validator)"
-    },
-    "packages": {
-      "weight": 0.15,
-      "validators": ["packages"],
-      "description": "Dependency health and compatibility"
-    }
-  },
-  "thresholds": {
-    "approve": 9.0,
-    "retry": 6.0
-  }
-}

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

@@ -1,54 +0,0 @@
----
-stacks:
-  - "*"
----
-
-# MORPH-SPEC Task Tracking
-
-> 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`
-
-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)
-and `standards` (paths pinned by morph-plan) are optional — legacy plans without
-them remain valid.
-
-Use the `Write` tool (whole-file rewrite) OR the `Edit` tool — `Edit` is allowed
-as long as it touches only `status`, `outputs`, and `notes`. State is then synced
-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
-task's `notes` field. `notes` is **uma única string** (o schema declara
-`"notes": { "type": "string" }`) — para registrar mais de um desvio, separe-os com
-`;` ou `\n` dentro da mesma string. Um array é **rejeitado** pelo validador, com a
-mensagem `'notes' must be a string`.
-
-```json
-{
-  "id": "T3",
-  "status": "done",
-  "outputs": ["Features/User/Update/Handler.cs"],
-  "notes": "deviation: split validation into a separate validator for testability; blocker-resolved: EF migration conflict fixed by regenerating the snapshot"
-}
-```

package/framework/rules/morph-workflow.md

@@ -1,244 +0,0 @@
----
-stacks:
-  - "*"
----
-
-# MORPH-SPEC Workflow Rules
-
-> Always-active rules for all MORPH-SPEC managed projects.
-
----
-
-## Spec-First Mandate
-
-**NEVER skip to code without a specification.** Every feature must progress through phases:
-
-1. **Proposal** — Problem statement + scope + risks (`0-proposal/proposal.md`). No acceptance criteria: verifiable behaviour lives in the use cases.
-2. **UI/UX Design** (optional, UI-heavy) — Design system + mockups + flows. The phase id is `uiux` (that is the gate name); the folder is `1-design/`
-3. **Plan** — Use cases first, then technical spec + tasks (`2-plan/usecases/UC-{nn}-{slug}.md`, `spec.md`, `tasks.json`). Each use case post-condition must be observable in a test and reaches the task's `doneCriteria` verbatim.
-4. **Implement** — Code + recap (`3-implement/recap.md`)
-5. **Review** — Review report + Gate 3 (`4-review/review-report.md`)
-
----
-
-## Phase Sequence
-
-```
-proposal → [uiux] → plan → implement → review
-```
-
-Use `morph-spec status {feature}` to see current phase and pending approval gates.
-
----
-
-## Phase Commands
-
-| Command | Purpose |
-|---------|---------|
-| `/morph-proposal {feature}` | Business understanding + plan — pauses at Gate 1 and Gate 2 |
-| `/morph-apply {feature}` | Autonomous execution + review — pauses at Gate 3 |
-| `/morph-status` | Feature dashboard |
-
-The full slash-command and CLI surface lives in the resident `.claude/CLAUDE.md` and in
-`.morph/framework/CLI.md` — this table only carries the three phase entry points.
-
----
-
-## State & Outputs
-
-| Path | Notes |
-|------|-------|
-| `.morph/features/{feature}/feature.json` | **Authoritative + committed** feature state. Write it through the CLI (`create`, `score`, `gate-check`, `approve`) — a hand Edit collides with the `state-sync` hook |
-| `.morph/state.json` | **READ-ONLY** — thin, gitignored index rebuilt from `feature.json` on load; kept in sync by the `state-sync` hook |
-| `.morph/features/{feature}/{phase}/` | Feature outputs organized by phase |
-| `.morph/framework/` | **READ-ONLY** — framework files managed by morph-spec |
-| `.morph/config/config.json` | Project configuration (editable) |
-
-### output types
-
-The canonical filename and phase folder of every output type are fixed by
-morph-spec itself — the concrete paths are in the table below. State sync is
-handled automatically by the `state-sync.js` PostToolUse hook: write the file
-at the right path and it is recorded; the agent does not call any CLI to
-register an output.
-
----
-
-## Output Paths
-
-All outputs go in `.morph/features/{feature}/`:
-
-| Phase | Path |
-|-------|------|
-| Proposal | `0-proposal/proposal.md`, `stack-scan.md` |
-| Design (optional) | `1-design/design-system.md`, `mockups.md`, `components.md`, `flows.md` |
-| Plan | `2-plan/usecases/`, `spec.md`, `tasks.json`, `decisions.md` |
-| Implement | `3-implement/recap.md` + source code; `3-implement/evidencias/{taskId}.md` (condicional — task cujo `doneCriteria` julga saída de LLM) |
-| Review | `4-review/review-report.md` |
-
----
-
-## Formato obrigatório do `3-implement/recap.md`
-
-> Esta exigência é **cobrada por hook** (`validate-completion`, no Stop). Ela está aqui, na regra
-> sempre-ativa, e não só na skill `morph-implement`: descobrir o formato quando o hook dispara
-> significa reescrever o recap depois de a fase já estar dada por encerrada.
-
-**Para CADA task com `status: "done"` em `tasks.json`**, o recap precisa de um bloco próprio:
-
-1. um heading `## T{N}` (o hook casa `^## T\d+` — uma linha de tabela `| T1 | … | done |` conta
-   como menção, **não** como bloco);
-2. uma linha `**Standard:** {standard-id}` **dentro de 12 linhas** do heading. Sem standard que
-   cubra o caso, registre a decisão em `decisions.md` e cite
-   `**Standard:** ad-hoc (see decisions.md ADR-{N})`.
-
-```markdown
-## T{N} — {title}
-
-**Standard:** {standard-id} (`.morph/framework/standards/{path}.md`)
-**Persona:** {mecanismo real usado}
-**Files:**
-- `{path}`
-
-{2-3 frases sobre o que foi feito}
-
-**Issues encontrados:** {breve descrição ou "nenhum"}
-```
-
-O `validate-completion` também acusa **drift**: uma task que aparece como concluída no recap mas
-ainda está `pending`/`in_progress` no `tasks.json`. Template completo e regras de exceção em
-`morph-implement` §6.
-
----
-
-## Checkpoints
-
-Run a checkpoint every 3 completed tasks:
-- Validate architecture compliance
-- Check package versions
-- Scan for security issues
-- Verify design system adherence (UI features)
-
----
-
-## Approval Gates
-
-Before completing any phase, verify pending approval gates:
-- `morph-spec approval-status <feature>` — check which gates are pending
-- `morph-spec approve <feature> <gate>` — approve a gate (`proposal`, `plan`, `review`; `uiux` if applicable)
-- `morph-spec advance <feature>` — approve the current gate AND scaffold the next phase folder in one step
-- Gates must be approved before advancing to the next phase
-
----
-
-## Protected Files
-
-**NEVER directly edit:**
-- `.morph/state.json` — Managed by CLI only
-- `.morph/framework/**` — Read-only framework content
-
----
-
-## Test File Policy
-
-When a test fails, always follow this order:
-
-1. **Analyze first** — determine if the IMPLEMENTATION is wrong or the TEST SPEC is wrong
-2. **Fix implementation first** — the test is the spec; trust it by default
-3. **Only modify a test file if the test expectation itself is incorrect** — wrong expected value, wrong behavior modeled
-4. **Before modifying any test file, explain WHY the test spec is wrong** — what the correct behavior is and why the test doesn't model it
-
-Do not modify test files to make a failing test pass when the implementation is the actual problem.
-
----
-
-## Context Maintenance
-
-After making structural changes (new packages, dependencies, project config changes), update the project context:
-- Edit `.morph/context/README.md` — update Tech Stack, Architecture, Key Integrations sections
-- Any `.morph/context/*.md`: **rewrite the body, never stack** — the section that described the old fact now describes the new one (a value that still holds somewhere says where); a changelog keeps only date and reason
-- Update `.morph/config/config.json` — update stack, architecture, integrations, paths
-- Structural changes include: package.json, .csproj, next.config.*, tsconfig.json, docker-compose.yml
-
----
-
-## Spec-Driven Task Execution (implement phase)
-
-BEFORE implementing ANY task during the implement phase:
-
-1. **Read tasks.json** → identify the current task object (`id`, `description`, `doneCriteria`, `dependencies`)
-2. **Read spec.md** → the FR sections that the task `description` references
-3. **Read the contracts** → the DTOs/interfaces are defined inside `spec.md` (v5 keeps contracts in the spec, not separate files)
-4. Only then begin implementation
-
-This is **NON-NEGOTIABLE**. The spec is the source of truth. Code that doesn't match the spec is a bug.
-
-Every task in `tasks.json` MUST reference its FR(s) in the `description` field so the link to the spec is explicit:
-```json
-{
-  "id": "T1",
-  "title": "Create user endpoint",
-  "description": "Implement user CRUD (FR001) and input validation (FR003). Contracts: CreateUserRequest, CreateUserResponse, UserErrors.",
-  "dependencies": [],
-  "effort": "M",
-  "doneCriteria": "POST /users creates a user and rejects invalid input",
-  "status": "pending",
-  "outputs": ["Features/UserFeature/Create/Handler.cs", "Validator.cs", "Endpoint.cs"],
-  "group": "backend"
-}
-```
-
----
-
-## Debugging
-
-When a bug or unexpected behavior shows up mid-task, find the **root cause before proposing a
-fix** — never a patch on the symptom. This is MANDATORY:
-
-1. Reproduce it and read the full error, not the first line.
-2. For a known .NET/Next.js error, run `/morph-troubleshoot <keywords>` first.
-3. One hypothesis at a time, each tested by the smallest check that could refute it.
-4. After three failed fixes, stop and question the design instead of trying a fourth.
-5. Confirm the fix with the same check that reproduced the bug; add a test only when no existing one covers that behavior.
-
-Everything else that a rule like this might list is owned by the flow itself, and duplicating it
-here would put a second, staler copy in permanent context:
-
-| Concern | Where it actually lives |
-|---------|-------------------------|
-| How many tests to write | The test budget in `morph-plan` §5: one test per postcondition, same-behavior cases in one table, no test that only pins text |
-| Verifying a task before `status: "done"` | `morph-spec verify {feature} [task]` (build + tests + validators + e2e) green, and each `doneCriteria` with the test or `file:line` that proves it |
-| Parallel dispatch | `morph-spec dag {feature}` decides sequential vs parallel; execution and isolation rules are in `morph-apply` §2/§3b |
-| Closing the phase / opening the PR | `morph-review` for Gate 3, then `morph-spec finish {feature} --pr\|--merge` |
-
----
-
-## Scope Escalation
-
-The plan contract frozen at Gate 2 — `spec.md` and the immutable `tasks.json`
-fields listed in `morph-task-tracking.md` — is enforced by the `protect-spec-files` hook. When a
-task turns out to be bigger than estimated, three different situations resolve three different ways:
-
-| Situation | Path |
-|-----------|------|
-| **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 |
-
-Scope ambiguity the plan does not cover is **not** an escalation: record it in
-`decisions.md`, resolve it the conservative way, and keep going — only pause if it is genuinely
-blocking (`morph-implement` §5).
-
-**Never** implement extra functionality within a task without registering it — `notes` for small
-additions, gate revocation for anything that changes the plan contract.
-
----
-
-## Context Window Tip
-
-When using 3+ MCPs, add `"experimental": { "mcpCliMode": true }` to `.claude/settings.json`.
-MCP tools load on-demand instead of all at startup — keeps context clean for actual work.
-
----
-
-*MORPH-SPEC by Polymorphism Tech*

package/framework/schemas/tasks.schema.json

@@ -1,79 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "MORPH-SPEC tasks.json",
-  "description": "Structured task list for a morph-spec feature. Replaces tasks.md.",
-  "type": "object",
-  "required": ["version", "feature", "tasks"],
-  "properties": {
-    "version": { "type": "string", "const": "1.0" },
-    "feature": { "type": "string", "minLength": 1 },
-    "tasks": {
-      "type": "array",
-      "items": {
-        "type": "object",
-        "required": ["id", "title", "description", "dependencies", "effort", "doneCriteria", "status"],
-        "properties": {
-          "id": { "type": "string", "pattern": "^T\\d+$" },
-          "title": { "type": "string", "minLength": 1 },
-          "description": { "type": "string", "minLength": 1 },
-          "dependencies": {
-            "type": "array",
-            "items": { "type": "string", "pattern": "^T\\d+$" }
-          },
-          "effort": { "type": "string", "enum": ["S", "M", "L", "XL"] },
-          "doneCriteria": { "type": "string", "minLength": 1 },
-          "status": { "type": "string", "enum": ["pending", "in_progress", "done", "skipped", "blocked"] },
-          "outputs": { "type": "array", "items": { "type": "string" } },
-          "notes": { "type": "string" },
-          "group": { "type": "string", "enum": ["backend", "frontend", "tests", "infra", "docs"] },
-          "usecase": {
-            "type": "string",
-            "pattern": "^UC-\\d+$",
-            "description": "ID of the use case this task realizes (2-plan/usecases/UC-{nn}-{slug}.md). Optional: technical tasks with no observable behaviour have none."
-          },
-          "agent": {
-            "type": "string",
-            "minLength": 1,
-            "description": "Persona id assigned by morph-plan for this task — the bare framework/agents.json id, no 'morph-' prefix (e.g. \"dotnet-senior\"). Optional. Part of the plan contract: frozen after Gate 2."
-          },
-          "reuse": {
-            "type": "array",
-            "description": "Veredito de reuso por conceito que ESTA task introduz, carimbado por morph-plan. Optional. Part of the plan contract: frozen after Gate 2.",
-            "items": {
-              "type": "object",
-              "required": ["concept", "verdict"],
-              "properties": {
-                "concept": {
-                  "type": "string",
-                  "minLength": 1,
-                  "description": "Nome do conceito/símbolo, como ele aparecerá no código (ex.: \"SimpleBuilding\")."
-                },
-                "verdict": {
-                  "type": "string",
-                  "enum": ["REUSAR", "ESTENDER", "CRIAR"],
-                  "description": "REUSAR: usar o que existe. ESTENDER: partir do que existe. CRIAR: nada cobre o caso — exige `why`."
-                },
-                "target": {
-                  "type": "string",
-                  "description": "Path (ou path:símbolo) do que será reusado/estendido. Vazio ou ausente em CRIAR."
-                },
-                "why": {
-                  "type": "string",
-                  "description": "Uma linha: por que nada existente cobre o caso. Exigido em CRIAR."
-                }
-              },
-              "additionalProperties": false
-            }
-          },
-          "standards": {
-            "type": "array",
-            "items": { "type": "string", "minLength": 1 },
-            "description": "Standards pinned by morph-plan for this task, as PATHS relative to the framework root (e.g. \"standards/backend/dotnet/vsa-handler-patterns.md\"). Optional. Part of the plan contract: frozen after Gate 2. NOT the same vocabulary as agents.json's top-level `standards` field, which lists IDs (e.g. \"backend-dotnet-vsa-handler-patterns\", no slashes/extension) — same field name, different shape; do not treat one as the other."
-          }
-        },
-        "additionalProperties": false
-      }
-    }
-  },
-  "additionalProperties": false
-}