@fro.bot/systematic 3.13.2 → 3.13.4

package/dist/cli.js

@@ -1981,6 +1981,7 @@ function cleanup(agentsRoot, configOptions) {
 // src/lib/review-artifact-schema.ts
 var MAX_REVIEWER_LENGTH = 64;
 var MAX_RUN_ID_LENGTH = 64;
+var MAX_BRANCH_LENGTH = 256;
 var MAX_INPUT_ID_LENGTH = 128;
 var MAX_REASON_LENGTH = 2048;
 var MAX_FINDINGS = 32;
@@ -2007,6 +2008,9 @@ var AdmittedDispositionSchema = DispositionSchema.exclude(["rejected"]);
 var HarnessSchema = exports_external.enum(["opencode", "pi", "claude-code"]);
 var RepoRelativePathSchema = boundedText(256).regex(/^(?!\/)(?![A-Za-z]:[\\/])(?!\\).+/);
 var ReviewerSchema = boundedText(MAX_REVIEWER_LENGTH);
+var BranchSchema = exports_external.string().max(MAX_BRANCH_LENGTH);
+var HeadShaSchema = exports_external.string().regex(/^[0-9a-f]{40}$/);
+var CompletedAtSchema = exports_external.iso.datetime({ offset: false });
 var ReasonSchema = boundedText(MAX_REASON_LENGTH);
 var FindingTitleSchema = boundedText(256);
 var SeveritySchema = exports_external.enum(["P0", "P1", "P2", "P3", "unknown"]);
@@ -2115,6 +2119,8 @@ var CoverageSchema = exports_external.object({
 var ReviewArtifactSchema = exports_external.object({
   schema_version: exports_external.literal(1),
   run_id: boundedText(MAX_RUN_ID_LENGTH),
+  branch: BranchSchema,
+  head_sha: HeadShaSchema,
   mode: exports_external.enum(["interactive", "autofix", "headless"]),
   harness: HarnessSchema,
   run_status: exports_external.enum([
@@ -2124,6 +2130,7 @@ var ReviewArtifactSchema = exports_external.object({
     "abnormal"
   ]),
   verdict: boundedText(256),
+  completed_at: CompletedAtSchema,
   dispatches: exports_external.array(DispatchSchema).max(MAX_PERSONAS),
   input_findings: exports_external.array(InputFindingSchema).max(MAX_FINDINGS * MAX_PERSONAS),
   findings: exports_external.array(SynthesizedFindingSchema).max(MAX_FINDINGS),

package/dist/lib/review-artifact-schema.d.ts

@@ -104,6 +104,8 @@ type SynthesizedFinding = Omit<SynthesizedFindingFields, 'validated' | 'validati
 export declare const ReviewArtifactSchema: z.ZodObject<{
     schema_version: z.ZodLiteral<1>;
     run_id: z.ZodString;
+    branch: z.ZodString;
+    head_sha: z.ZodString;
     mode: z.ZodEnum<{
         autofix: "autofix";
         headless: "headless";
@@ -121,6 +123,7 @@ export declare const ReviewArtifactSchema: z.ZodObject<{
         in_progress: "in_progress";
     }>;
     verdict: z.ZodString;
+    completed_at: z.ZodISODateTime;
     dispatches: z.ZodArray<z.ZodObject<{
         persona: z.ZodString;
         dispatch_outcome: z.ZodEnum<{

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fro.bot/systematic",
-  "version": "3.13.2",
+  "version": "3.13.4",
   "description": "Compound-engineering loops for OpenCode, Pi, and Claude Code",
   "type": "module",
   "homepage": "https://fro.bot/systematic",

package/skills/ce-plan/SKILL.md

@@ -443,6 +443,8 @@ For each unit, include:
 
 Every feature-bearing unit should include the test file path in `**Files:**`.
 
+When a unit creates a file in a directory that carries registration obligations — a manifest, index, codemap, module table, or generated artifact that must list it — name those surfaces in the same unit's `**Files:**`, and name the regeneration command in its `**Verification**`. Phase 1.1 already collects this from the repository's own contributor guidance; carry it into the unit rather than leaving it for a failing gate to report. An obligation that no gate enforces is the one most likely to be missed, so state it even when nothing will fail.
+
 Use `Execution note` sparingly. Good uses include:
 - `Execution note: Start with a failing integration test for the request/response contract.`
 - `Execution note: Add characterization coverage before modifying this legacy parser.`

package/skills/ce-review/SKILL.md

@@ -706,18 +706,7 @@ After presenting findings and verdict (Stage 6), route the next steps by mode. R
 - `review-summary.json` is the parent-owned synthesis artifact. Its lifecycle, dispatch outcomes, complete input ledger, synthesized and filtered findings with provenance, disposition counts, and downstream work are defined in the [canonical synthesis artifact contract](./references/synthesis-artifact-contract.md), whose vocabulary and bounds are executable in [`findings-schema.json`](./references/findings-schema.json).
 - Before finalizing, follow the [artifact validation and failure path](./references/synthesis-artifact-contract.md).
 - Initialize the artifact before dispatch and persist only validated parent-owned records. Finalize lifecycle and reconciliation after synthesis; preserve the existing degraded and abnormal-run behavior described in the canonical contract.
-- Also write `metadata.json` alongside the findings so downstream skills can verify the artifact matches the current branch and HEAD. Minimum fields:
-  ```json
-  {
-    "run_id": "<run-id>",
-    "branch": "<git branch --show-current at dispatch time>",
-    "head_sha": "<git rev-parse HEAD at dispatch time>",
-    "harness": "<opencode | pi | claude-code>",
-    "verdict": "<Ready to merge | Ready with fixes | Not ready>",
-    "completed_at": "<ISO 8601 UTC timestamp>"
-  }
-  ```
-  Capture `branch` and `head_sha` at dispatch time (before any autofixes land), and write the file after the verdict is finalized. This file is additive -- pre-existing artifacts that predate this field are still valid, and downstream skills fall back to file mtime when it is missing.
+- Capture `branch` and `head_sha` at dispatch time, before any autofixes land, and write them into `review-summary.json` with `completed_at` when the verdict is finalized; see the [canonical synthesis artifact contract](./references/synthesis-artifact-contract.md) for the provenance semantics.
 - In autofix mode, create durable todo files only for unresolved actionable findings whose final owner is `downstream-resolver`. Load the `todos` skill (Create section) for the canonical directory path, naming convention, YAML frontmatter structure, and template. Each todo should map the finding's severity to the todo priority (`P0`/`P1` -> `p1`, `P2` -> `p2`, `P3` -> `p3`) and set `status: ready` since these findings have already been triaged by synthesis.
 - Do not create todos for `advisory` findings, `owner: human`, `owner: release`, or protected-artifact cleanup suggestions.
 - If only advisory outputs remain, create no todos.

package/skills/ce-review/references/review-summary-schema.json

@@ -12,6 +12,14 @@
       "maxLength": 64,
       "pattern": "\\S"
     },
+    "branch": {
+      "type": "string",
+      "maxLength": 256
+    },
+    "head_sha": {
+      "type": "string",
+      "pattern": "^[0-9a-f]{40}$"
+    },
     "mode": {
       "type": "string",
       "enum": ["interactive", "autofix", "headless"]
@@ -30,6 +38,11 @@
       "maxLength": 256,
       "pattern": "\\S"
     },
+    "completed_at": {
+      "type": "string",
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
+    },
     "dispatches": {
       "maxItems": 64,
       "type": "array",
@@ -500,10 +513,13 @@
   "required": [
     "schema_version",
     "run_id",
+    "branch",
+    "head_sha",
     "mode",
     "harness",
     "run_status",
     "verdict",
+    "completed_at",
     "dispatches",
     "input_findings",
     "findings",

package/skills/ce-review/references/synthesis-artifact-contract.md

@@ -136,12 +136,12 @@ The artifact must preserve these distinctions:
   or higher.
 
 The artifact also includes applied fixes, residual actionable work,
-advisory-only outputs, coverage data, and the harness value. Alongside the
-findings, the parent writes `metadata.json` with the run ID, branch and HEAD
-captured at dispatch time, harness, verdict, and completion timestamp. The
-branch and HEAD are captured before autofixes land; metadata is written after
-the verdict is finalized. Existing artifacts without this additive metadata
-remain valid, with downstream consumers falling back to file mtime.
+advisory-only outputs, coverage data, and the harness value. The run artifact
+itself carries the branch and HEAD provenance alongside the run ID, harness,
+verdict, and completion timestamp. The parent captures `branch` and `head_sha`
+at dispatch, before autofixes land, and writes the artifact after the verdict
+is finalized; consumers can therefore tell whether the artifact describes the
+current checkout.
 
 Validation and persistence remain parent-side: no per-agent record or finding
 is written or merged until that finding passes schema and environment-value