shapeup-sdlc 1.6.3 → 3.0.0

package/skills/tech-lead/schemas/gate-answers.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://github.com/nguyenvanphituoc/shapeup-sdlc-plugin/schemas/gate-answers.schema.json",
   "title": "GateAnswerSet",
-  "description": "A pre-recorded set of PO decisions, one per gate, that lets a run cross its gates without a human in the loop. This is NOT 'gates off' — every gate still emits its block and still records a decision in the ledger; the decision's SOURCE becomes this file instead of a live human. That distinction is the whole design: an unattended run with no answer set stalls at the first ⏸ and burns its wall-clock budget (measured: shapeup-sdlc DNF at 1800s on benchmark F3), while an unattended run with one produces the same audit trail an interactive run does.",
+  "description": "A pre-recorded set of PO decisions, one per gate, that lets a run cross its gates without a human in the loop. This is NOT 'gates off' — every gate still emits its block and still records a decision in the ledger; the decision's SOURCE becomes this file instead of a live human. That distinction is the whole design: an unattended run with no answer set stalls at the first ⏸ and burns its whole wall-clock budget having built nothing, while an unattended run with one produces the same audit trail an interactive run does.",
   "type": "object",
   "required": ["version", "preset", "answers"],
   "additionalProperties": false,
@@ -26,7 +26,7 @@
     "escalation": {
       "type": "object",
       "additionalProperties": false,
-      "description": "Policy for a worker's structured ESCALATE (advisor-protocol), which is a gate in all but name.",
+      "description": "RESERVED. Policy for a worker-raised question, which would be a gate in all but name. Inert today: WorkResult carries no escalates field, so no worker can raise one. Kept as a declared key because the answer-set schema forbids additional properties, and removing it would invalidate every gate-answers.json already on disk.",
       "properties": {
         "default": {
           "type": "string",

package/skills/tech-lead/schemas/work-order.schema.json

@@ -1,16 +1,25 @@
 {
   "$id": "work-order.schema.json",
   "title": "WorkOrder",
-  "description": "The orchestrator → worker envelope (pure-skill architecture v1.0). Compiled by skills/tech-lead/scripts/compile-order.mjs, validated by validate-envelope.mjs before any worker dispatch. A worker depends only on this envelope — never on filesystem topology, run-state format, board schema, or another worker. Path: .shapeup/<slug>/orders/r<N>-a<M>.json (or <slug>/orders/<operation>.json for non-attempt work). Every record type and payload field is DEFINED CENTRALLY in domain.schema.json ($defs + x-payload-by-worker) — this file only shapes the envelope; it never re-defines a domain entity.",
+  "description": "The orchestrator → worker envelope (pure-skill architecture v1.0). Compiled by kernel/compile.mjs, validated by harness verify envelope before any worker dispatch. A worker depends only on this envelope — never on filesystem topology, run-state format, board schema, or another worker. Path: .shapeup/<slug>/orders/r<N>-a<M>.json (or <slug>/orders/<operation>.json for non-attempt work). Every record type and payload field is DEFINED CENTRALLY in domain.schema.json ($defs + x-payload-by-worker) — this file only shapes the envelope; it never re-defines a domain entity.",
   "type": "object",
   "required": ["schema_version", "order_id", "worker", "mode", "payload"],
   "properties": {
     "schema_version": { "type": "integer", "enum": [1] },
     "order_id": {
       "type": "string",
-      "description": "\"<slug>/r<N>-a<M>\" for build attempts, \"<slug>/<operation>[-r<N>]\" otherwise",
+      "description": "\"<slug>/r<N>-a<M>\" for build attempts, \"<slug>/<operation>[-r<N>]\" otherwise. Identifies a dispatch WITHIN a run — it repeats across runs of the same slug, which is why run_id exists.",
       "pattern": "^[a-z0-9][a-z0-9-]*/[a-z0-9][A-Za-z0-9.-]*$"
     },
+    "run_id": {
+      "type": "string",
+      "description": "OPTIONAL (v1.8) — the run this dispatch belongs to, stamped by harness compile from the receipt (kernel/lib/paths.mjs). The join key the analysis plane groups on: order_id alone collides across runs of the same slug, so without this no record the pipeline writes can be attributed to a run. Absent when no readable receipt exists (a standalone dispatch in a workspace with no open run) — never invented, and never required, because an analytic field must not be able to block a build.",
+      "pattern": "^[a-z0-9][a-z0-9-]*-[0-9]{8}T[0-9]{6}Z-[0-9a-f]{8}$"
+    },
+    "compiled_at": {
+      "type": "string",
+      "description": "OPTIONAL (v1.8) — ISO timestamp of compilation. The dispatch record's own time dimension: WorkResult carries none, and the journal's timings exist only on the workflow lane, so without this a dispatch on the prose lane is timeless."
+    },
     "worker": { "$ref": "domain.schema.json#/$defs/WorkerName" },
     "mode": { "type": "string", "enum": ["orchestrated", "standalone"] },
     "operation": { "$ref": "domain.schema.json#/$defs/Operation" },

package/skills/tech-lead/schemas/work-result.schema.json

@@ -1,40 +1,78 @@
 {
   "$id": "work-result.schema.json",
   "title": "WorkResult",
-  "description": "The worker → orchestrator envelope (pure-skill architecture v1.0). Everything a worker used to write into shared files it now RETURNS as data; skills/tech-lead/scripts/ingest-result.mjs performs the writes (tick AC boxes, flip board status, append execution log, propagate unblocks, append discoveries) deterministically, in one place. Path: .shapeup/<slug>/results/r<N>-a<M>.json. Every record type is DEFINED CENTRALLY in domain.schema.json — this file only shapes the envelope.",
+  "description": "The worker → orchestrator envelope (pure-skill architecture v1.0). Everything a worker used to write into shared files it now RETURNS as data; kernel/reduce/ingest.mjs performs the writes (tick AC boxes, flip board status, append execution log, propagate unblocks, append discoveries) deterministically, in one place. Path: .shapeup/<slug>/results/r<N>-a<M>.json. Every record type is DEFINED CENTRALLY in domain.schema.json — this file only shapes the envelope.",
   "type": "object",
-  "required": ["schema_version", "order_id", "status"],
+  "required": [
+    "schema_version",
+    "order_id",
+    "status"
+  ],
   "properties": {
-    "schema_version": { "type": "integer", "enum": [1] },
-    "order_id": { "type": "string", "description": "Copied verbatim from the answered WorkOrder — the 1:1 join key." },
-    "worker": { "type": "string" },
-    "status": { "type": "string", "enum": ["done", "partial", "escalated", "failed"] },
+    "schema_version": {
+      "type": "integer",
+      "enum": [
+        1
+      ]
+    },
+    "order_id": {
+      "type": "string",
+      "description": "Copied verbatim from the answered WorkOrder — the 1:1 join key."
+    },
+    "worker": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string",
+      "enum": [
+        "done",
+        "partial",
+        "escalated",
+        "failed"
+      ]
+    },
     "task_results": {
       "type": "array",
       "description": "Per-task outcome. ingest-result flips the board row, ticks GATE-verified AC boxes, and appends the Execution Log from these entries.",
-      "items": { "$ref": "domain.schema.json#/$defs/TaskResult" }
+      "items": {
+        "$ref": "domain.schema.json#/$defs/TaskResult"
+      }
     },
     "files_touched": {
       "type": "array",
-      "items": { "$ref": "domain.schema.json#/$defs/FileTouched" }
-    },
-    "escalates": {
-      "type": "array",
-      "description": "advisor-protocol ESCALATE blocks — the worker's one outward port.",
-      "items": { "$ref": "domain.schema.json#/$defs/Escalate" }
+      "items": {
+        "$ref": "domain.schema.json#/$defs/FileTouched"
+      }
     },
     "discoveries": {
       "type": "array",
       "description": "Raw discovered lines. ingest-result appends them to the discovery ledger — the worker never touches the ledger itself.",
-      "items": { "$ref": "domain.schema.json#/$defs/Discovery" }
+      "items": {
+        "$ref": "domain.schema.json#/$defs/Discovery"
+      }
+    },
+    "verdict": {
+      "$ref": "domain.schema.json#/$defs/Verdict"
     },
-    "verdict": { "$ref": "domain.schema.json#/$defs/Verdict" },
     "artifacts": {
       "type": "array",
       "description": "Domain artifacts the worker wrote inside its substrate (spec docs, orient/ files, reports).",
-      "items": { "type": "string" }
+      "items": {
+        "type": "string"
+      }
     },
-    "assumptions": { "type": "array", "items": { "type": "string" } },
-    "deviations": { "type": "array", "items": { "type": "string" } }
+    "assumptions": {
+      "type": "array",
+      "items": {
+        "type": "string"
+      }
+    },
+    "deviations": {
+      "type": "array",
+      "items": {
+        "type": "string"
+      },
+      "description": "When status is \"escalated\", the FIRST entry is the blocker: one specific, answerable question with the context needed to answer it. There is no escalates[] field, so this is the only channel a blocked worker has."
+    }
   }
 }