@polymorphism-tech/morph-spec 8.44.0 → 8.46.0

package/framework/phases.json

@@ -42,13 +42,12 @@
       "displayName": "Plan",
       "goals": [
         "Write spec.md (technical spec)",
-        "Write mandate.md (implementation contract with stack defaults + forbidden patterns)",
         "Write tasks.json (ordered task breakdown)"
       ],
-      "requiredOutputs": ["spec", "mandate", "tasks"],
+      "requiredOutputs": ["spec", "tasks"],
       "optionalOutputs": ["decisions"],
       "pausePoints": [
-        { "id": "plan", "label": "Gate 2 — Approve spec + mandate + tasks" }
+        { "id": "plan", "label": "Gate 2 — Approve spec + tasks" }
       ],
       "skill": "morph-plan"
     },
@@ -59,7 +58,7 @@
       "displayName": "Implementation",
       "goals": [
         "Execute tasks in order with auto-advance between tasks",
-        "Apply morph-eval after each task",
+        "Advance a task only on verify green and its doneCriteria met",
         "Maintain recap.md and execution trace"
       ],
       "requiredOutputs": ["recap"],
@@ -73,8 +72,7 @@
       "folder": "4-review",
       "displayName": "Review",
       "goals": [
-        "Verify implementation against mandate",
-        "Apply morph-eval at phase scope to produce dimension scores",
+        "Independent evaluator verdict (SHIP/FIX) with evidence-typed blockers",
         "Produce review-report.md and present Gate 3"
       ],
       "requiredOutputs": ["reviewReport"],

package/framework/rubrics/backend.json

@@ -1,7 +1,7 @@
 {
   "id": "backend",
   "version": "1.1.0",
-  "description": "Backend-focused rubric. Higher weight on architecture, security, and package health. Deterministic-validator rubric — approve threshold aligned to the single bar 9 from MORPH.md §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,

package/framework/rubrics/default.json

@@ -1,7 +1,7 @@
 {
   "id": "default",
   "version": "1.1.0",
-  "description": "Default rubric for general-purpose projects. Balanced weights across all categories. Deterministic-validator rubric — approve threshold aligned to the single bar 9 from MORPH.md §0 (the LLM eval rubrics live in framework/evals/rubrics/*.md).",
+  "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,

package/framework/rubrics/frontend.json

@@ -1,7 +1,7 @@
 {
   "id": "frontend",
   "version": "1.1.0",
-  "description": "Frontend-focused rubric. Higher weight on design system compliance and UI quality. Deterministic-validator rubric — approve threshold aligned to the single bar 9 from MORPH.md §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,

package/framework/rules/morph-workflow.md

@@ -15,7 +15,7 @@ stacks:
 
 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 + mandate + tasks (`2-plan/usecases/UC-{nn}-{slug}.md`, `spec.md`, `mandate.md`, `tasks.json`). Each use case post-condition must be observable in a test and reaches the task's `doneCriteria` verbatim.
+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`)
 
@@ -72,7 +72,7 @@ All outputs go in `.morph/features/{feature}/`:
 |-------|------|
 | Proposal | `0-proposal/proposal.md`, `stack-scan.md` |
 | Design (optional) | `1-design/design-system.md`, `mockups.md`, `components.md`, `flows.md` |
-| Plan | `2-plan/spec.md`, `mandate.md`, `tasks.json`, `decisions.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` |
 
@@ -206,8 +206,8 @@ here would put a second, staler copy in permanent context:
 
 | Concern | Where it actually lives |
 |---------|-------------------------|
-| How many tests to write | The test budget copied into the feature's `mandate.md`: 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), then the `morph-eval` skill for the 0-10 score |
+| 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` |
 
@@ -215,7 +215,7 @@ here would put a second, staler copy in permanent context:
 
 ## Scope Escalation
 
-The plan contract frozen at Gate 2 — `spec.md`, `mandate.md`, and the immutable `tasks.json`
+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:
 
@@ -225,7 +225,7 @@ task turns out to be bigger than estimated, three different situations resolve t
 | **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 `mandate.md` does not cover is **not** an escalation: record it in
+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).
 

package/framework/schemas/config.schema.json

@@ -9,6 +9,10 @@
       "type": "object",
       "additionalProperties": true,
       "properties": {
+        "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."
+        },
         "tests": {
           "type": "array",
           "description": "One entry per test suite. Absent (not empty) means the four-step fallback of resolveTestPlan() decides — every project created before this key existed keeps working. An empty array is an explicit declaration of 'no test suites'.",

package/framework/schemas/feature.schema.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "MORPH-SPEC feature.json",
-  "description": "Canonical shape of the authoritative, committed per-feature state at .morph/features/{feature}/feature.json (v5 per-feature state model). Born via `morph-spec create` (explicit) or the state-sync hook (implicit fallback). Server-side writers: `morph-spec approve/advance` (approvalGates), `morph-spec score` (taskScores), `morph-spec gate-decision` (gateDecisions), `morph-spec archive`/`finish` (status/archivedAt — `finish` archives internally before integrating). Never hand-edit the CLI-owned fields — manual Edits collide with the state-sync hook. This schema is documentational: additionalProperties stays true so older/newer CLIs interoperate.",
+  "description": "Canonical shape of the authoritative, committed per-feature state at .morph/features/{feature}/feature.json (v5 per-feature state model). Born via `morph-spec create` (explicit) or the state-sync hook (implicit fallback). Server-side writers: `morph-spec approve/advance` (approvalGates), `morph-spec gate-decision` (gateDecisions), `morph-spec archive`/`finish` (status/archivedAt — `finish` archives internally before integrating). Never hand-edit the CLI-owned fields — manual Edits collide with the state-sync hook. This schema is documentational: additionalProperties stays true so older/newer CLIs interoperate.",
   "type": "object",
   "required": ["status", "approvalGates"],
   "properties": {
@@ -57,7 +57,7 @@
           "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, evalScore, standardsViolations, designSystemDivergence..."
+            "description": "Risk signals evaluated (free-form): taskCount, evaluatorVerdict, standardsViolations, designSystemDivergence..."
           },
           "trust": { "type": "string", "enum": ["auto", "manual"] },
           "decidedAt": { "type": "string", "format": "date-time" },
@@ -69,32 +69,6 @@
         "additionalProperties": false
       }
     },
-    "taskScores": {
-      "type": "object",
-      "description": "Per-task eval scores, written ONLY by `morph-spec score` (updatedAt is server-side; attempts auto-increment; bestScore is kept).",
-      "propertyNames": { "pattern": "^T\\d+$" },
-      "additionalProperties": {
-        "type": "object",
-        "required": ["lastScore", "bestScore", "attempts", "updatedAt"],
-        "properties": {
-          "lastScore": { "type": "number", "minimum": 0, "maximum": 10 },
-          "bestScore": { "type": "number", "minimum": 0, "maximum": 10 },
-          "attempts": { "type": "integer", "minimum": 1 },
-          "dimensions": {
-            "type": "object",
-            "properties": {
-              "architecture": { "type": "number", "minimum": 0, "maximum": 10 },
-              "contracts": { "type": "number", "minimum": 0, "maximum": 10 },
-              "codeQuality": { "type": "number", "minimum": 0, "maximum": 10 },
-              "testCoverage": { "type": "number", "minimum": 0, "maximum": 10 }
-            },
-            "additionalProperties": false
-          },
-          "updatedAt": { "type": "string", "format": "date-time" }
-        },
-        "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().",
@@ -178,7 +152,9 @@
         "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." }
+        "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." },
+        "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
     },

package/framework/schemas/tasks.schema.json

@@ -38,7 +38,7 @@
           },
           "reuse": {
             "type": "array",
-            "description": "Veredito de reuso por conceito que ESTA task introduz, carimbado por morph-plan a partir do 2-plan/reuse-map.md. Optional. Part of the plan contract: frozen after Gate 2. A justificativa de um CRIAR mora no reuse-map.md, nunca aqui — duas verdades do mesmo fato divergem.",
+            "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"],
@@ -51,11 +51,15 @@
                 "verdict": {
                   "type": "string",
                   "enum": ["REUSAR", "ESTENDER", "CRIAR"],
-                  "description": "REUSAR: usar o que existe. ESTENDER: partir do que existe. CRIAR: nada cobre o caso — exige justificativa de uma linha no reuse-map.md."
+                  "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

package/framework/skills/README.md

@@ -14,9 +14,8 @@ These are the only skills the harness needs. MORPH.md references them by path.
 |----------------------|----------------------------------------------------------------------|----------------|
 | `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 spec.md + mandate.md + tasks.json (Gate 2)                   | 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-eval`          | Score work 0-10 across 4 dimensions, silence on score >= 9           | no             |
 | `morph-review`        | Final review report with scores + recommendation (Gate 3)            | yes            |
 | `morph-standards`     | Locate and load a specific standard on demand                        | no             |
 

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.44.0"
+cliVersion: "8.46.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.44.0"
+cliVersion: "8.46.0"
 stacks:
   - umbraco
 ---