syntaur 0.43.1 → 0.44.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "syntaur",
-  "version": "0.43.1",
+  "version": "0.44.0",
   "description": "Project workflow CLI with dashboard, Claude Code plugin, and Codex plugin",
   "homepage": "https://github.com/prong-horn/syntaur#readme",
   "repository": {

package/platforms/claude-code/.claude-plugin/plugin.json

@@ -5,7 +5,7 @@
     "name": "Brennen",
     "email": ""
   },
-  "version": "0.43.1",
+  "version": "0.44.0",
   "skills": [
     "./skills/syntaur-protocol",
     "./skills/grab-assignment",

package/platforms/claude-code/skills/manage-statuses/SKILL.md

@@ -62,11 +62,59 @@ After every mutating subcommand, run `syntaur status list` (or `--json` for mach
 - **After a `remove --force`,** the affected assignments now reference an undefined status. `syntaur doctor` will flag them as invalid. Suggest the user run `syntaur doctor` and either re-add the status (`syntaur status add ...`) or edit each frontmatter to a valid id.
 - **After `transition add`,** the dashboard's transition buttons reflect the new transition only after the cache invalidation above.
 
+## Custom facts and attestations
+
+Beyond the 14 built-in derived-status facts, users can declare their **own** facts under `statuses.facts` and reference them in `phaseLadder` / `disposition` conditions. There are two kinds.
+
+**1. Custom asserted facts** — config-declared `bool` / `number` values, asserted via `syntaur fact set` and stored in a `facts:` frontmatter map:
+
+```yaml
+statuses:
+  facts:
+    - name: qaPassed
+      type: bool
+    - name: storyPoints
+      type: number
+```
+
+```bash
+syntaur fact set <assignment> qaPassed true --project <p>
+syntaur fact set <assignment> storyPoints 5 --project <p>
+```
+
+`bool` accepts case-insensitive `true`/`false`; `number` accepts any finite number. The declared `name` exports a single derive field of the same name (`qaPassed:true`, `storyPoints > 3`). Stored in frontmatter as `facts:\n  qaPassed: "true"`.
+
+**2. Attestation facts** — model "agent X reviewed revision Y with verdict Z". Declared with `type: attestation` and a `binds:` mode:
+
+```yaml
+statuses:
+  facts:
+    - name: codeReview
+      type: attestation
+      binds: plan      # plan | commit | none
+```
+
+```bash
+syntaur attest <assignment> codeReview --agent codex --verdict approved --project <p>
+syntaur attest <assignment> codeReview --agent pi --verdict changes-requested --note "fix the lock" --project <p>
+```
+
+`--verdict` defaults to `approved` (the other value is `changes-requested`). One record per actor — re-attesting **replaces** that actor's record. Stored in an `attestations:` frontmatter list (`{fact, actor, verdict, at, note?}` + binding snapshot).
+
+Each attestation fact exports **five** derive fields (for `codeReview`): `codeReview` (any valid record), `codeReviewApproved`, `codeReviewChangesRequested` (bools), and `codeReviewBy`, `codeReviewApprovedBy` (actor **sets** — use `:` for contains / `IN`-lists, e.g. `codeReviewApprovedBy:"agent:codex"`; quote actor values that contain a `:`). This makes review loops self-modeling — a rung `when: "codeReviewApproved:true"` fires on approval, and `when: "codeReviewChangesRequested:true"` expresses "reviewed but not signed off".
+
+**Revision binding** is what makes attestations self-invalidate:
+- `binds: plan` — bound to the latest plan file + its digest (same semantics as plan approval). A replan or a post-attest plan edit makes the record **stale**; stale records contribute nothing (the fact flips false, the actor drops out of the `*By` sets).
+- `binds: commit` — bound to the workspace branch HEAD sha at attest time. A new commit makes it stale. **Lazy convergence:** dashboard payloads and `ls --query` compute facts fresh per request (always honest), but the *persisted* phase regression lands on the next recompute trigger (any CLI verb, watcher event, config change, or boot sweep) — there is no git watcher.
+- `binds: none` — never stale (a standing sign-off).
+
+**Validation & teeth.** Declared names are validated by `syntaur doctor` (the `derive-config.valid` check): bad name/type/binds and any collision of an exported field with a built-in or another declaration is reported as an error and the offending declaration is dropped (built-ins always win). A derive condition that references an **undeclared** fact still fails at recompute time (`CompileError`), exactly as before. `syntaur fact set` / `syntaur attest` reject undeclared names, wrong types, and invalid verdicts. Every `fact set` / `attest` is recorded in `statusHistory` with its actor and cause, even when no dimension moves.
+
 ## Safety notes
 
 - **`remove` is destructive.** Without `--force` it refuses if any assignment references the id. Don't suggest `--force` without first running `syntaur status remove <id>` (no force) so the user sees the affected list.
 - **`rename` rewrites many files.** It edits `config.md` AND every affected `assignment.md` in a single atomic transaction (with rollback if any write fails partway). Always run `--dry-run` first on a non-trivial codebase so the user sees the per-file diff.
 - **`terminal: true` is load-bearing.** Terminal statuses affect dashboard progress bars and dependency-satisfaction logic — an assignment with a terminal status counts as "done" for downstream `dependsOn` checks and project-rollup status. Don't toggle this on `pending`-style states without thinking.
-- **`init --force` overwrites a custom block.** Use `reset` first if the user wants a clean slate, OR confirm before passing `--force` if they have unsaved customizations.
+- **`init --force` overwrites a custom block.** Use `reset` first if the user wants a clean slate, OR confirm before passing `--force` if they have unsaved customizations. It resets to the built-in defaults and therefore **drops any `statuses.facts` declarations and `derive` rules** along with the custom statuses — every other `status` subcommand (`set`/`add`/`remove`/`rename`/`reorder`/`transition`) preserves them.
 - **Concurrency.** `rename`'s buffer-write-rollback strategy assumes no concurrent writers. Tell the user to close the dashboard / pause other agents during a rename.
 - **`SYNTAUR_HOME` precedence.** If the user has `SYNTAUR_HOME` set, the CLI writes there instead of `~/.syntaur`. Mirror their environment.

package/platforms/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "syntaur",
-  "version": "0.43.1",
+  "version": "0.44.0",
   "description": "Run Syntaur project and assignment workflows from Codex, including claiming work, planning, completing handoffs, session/server tracking, save-session-summary continuity, and write-boundary enforcement.",
   "author": {
     "name": "Brennen"

package/platforms/codex/skills/manage-statuses/SKILL.md

@@ -62,11 +62,59 @@ After every mutating subcommand, run `syntaur status list` (or `--json` for mach
 - **After a `remove --force`,** the affected assignments now reference an undefined status. `syntaur doctor` will flag them as invalid. Suggest the user run `syntaur doctor` and either re-add the status (`syntaur status add ...`) or edit each frontmatter to a valid id.
 - **After `transition add`,** the dashboard's transition buttons reflect the new transition only after the cache invalidation above.
 
+## Custom facts and attestations
+
+Beyond the 14 built-in derived-status facts, users can declare their **own** facts under `statuses.facts` and reference them in `phaseLadder` / `disposition` conditions. There are two kinds.
+
+**1. Custom asserted facts** — config-declared `bool` / `number` values, asserted via `syntaur fact set` and stored in a `facts:` frontmatter map:
+
+```yaml
+statuses:
+  facts:
+    - name: qaPassed
+      type: bool
+    - name: storyPoints
+      type: number
+```
+
+```bash
+syntaur fact set <assignment> qaPassed true --project <p>
+syntaur fact set <assignment> storyPoints 5 --project <p>
+```
+
+`bool` accepts case-insensitive `true`/`false`; `number` accepts any finite number. The declared `name` exports a single derive field of the same name (`qaPassed:true`, `storyPoints > 3`). Stored in frontmatter as `facts:\n  qaPassed: "true"`.
+
+**2. Attestation facts** — model "agent X reviewed revision Y with verdict Z". Declared with `type: attestation` and a `binds:` mode:
+
+```yaml
+statuses:
+  facts:
+    - name: codeReview
+      type: attestation
+      binds: plan      # plan | commit | none
+```
+
+```bash
+syntaur attest <assignment> codeReview --agent codex --verdict approved --project <p>
+syntaur attest <assignment> codeReview --agent pi --verdict changes-requested --note "fix the lock" --project <p>
+```
+
+`--verdict` defaults to `approved` (the other value is `changes-requested`). One record per actor — re-attesting **replaces** that actor's record. Stored in an `attestations:` frontmatter list (`{fact, actor, verdict, at, note?}` + binding snapshot).
+
+Each attestation fact exports **five** derive fields (for `codeReview`): `codeReview` (any valid record), `codeReviewApproved`, `codeReviewChangesRequested` (bools), and `codeReviewBy`, `codeReviewApprovedBy` (actor **sets** — use `:` for contains / `IN`-lists, e.g. `codeReviewApprovedBy:"agent:codex"`; quote actor values that contain a `:`). This makes review loops self-modeling — a rung `when: "codeReviewApproved:true"` fires on approval, and `when: "codeReviewChangesRequested:true"` expresses "reviewed but not signed off".
+
+**Revision binding** is what makes attestations self-invalidate:
+- `binds: plan` — bound to the latest plan file + its digest (same semantics as plan approval). A replan or a post-attest plan edit makes the record **stale**; stale records contribute nothing (the fact flips false, the actor drops out of the `*By` sets).
+- `binds: commit` — bound to the workspace branch HEAD sha at attest time. A new commit makes it stale. **Lazy convergence:** dashboard payloads and `ls --query` compute facts fresh per request (always honest), but the *persisted* phase regression lands on the next recompute trigger (any CLI verb, watcher event, config change, or boot sweep) — there is no git watcher.
+- `binds: none` — never stale (a standing sign-off).
+
+**Validation & teeth.** Declared names are validated by `syntaur doctor` (the `derive-config.valid` check): bad name/type/binds and any collision of an exported field with a built-in or another declaration is reported as an error and the offending declaration is dropped (built-ins always win). A derive condition that references an **undeclared** fact still fails at recompute time (`CompileError`), exactly as before. `syntaur fact set` / `syntaur attest` reject undeclared names, wrong types, and invalid verdicts. Every `fact set` / `attest` is recorded in `statusHistory` with its actor and cause, even when no dimension moves.
+
 ## Safety notes
 
 - **`remove` is destructive.** Without `--force` it refuses if any assignment references the id. Don't suggest `--force` without first running `syntaur status remove <id>` (no force) so the user sees the affected list.
 - **`rename` rewrites many files.** It edits `config.md` AND every affected `assignment.md` in a single atomic transaction (with rollback if any write fails partway). Always run `--dry-run` first on a non-trivial codebase so the user sees the per-file diff.
 - **`terminal: true` is load-bearing.** Terminal statuses affect dashboard progress bars and dependency-satisfaction logic — an assignment with a terminal status counts as "done" for downstream `dependsOn` checks and project-rollup status. Don't toggle this on `pending`-style states without thinking.
-- **`init --force` overwrites a custom block.** Use `reset` first if the user wants a clean slate, OR confirm before passing `--force` if they have unsaved customizations.
+- **`init --force` overwrites a custom block.** Use `reset` first if the user wants a clean slate, OR confirm before passing `--force` if they have unsaved customizations. It resets to the built-in defaults and therefore **drops any `statuses.facts` declarations and `derive` rules** along with the custom statuses — every other `status` subcommand (`set`/`add`/`remove`/`rename`/`reorder`/`transition`) preserves them.
 - **Concurrency.** `rename`'s buffer-write-rollback strategy assumes no concurrent writers. Tell the user to close the dashboard / pause other agents during a rename.
 - **`SYNTAUR_HOME` precedence.** If the user has `SYNTAUR_HOME` set, the CLI writes there instead of `~/.syntaur`. Mirror their environment.

package/skills/manage-statuses/SKILL.md

@@ -62,11 +62,59 @@ After every mutating subcommand, run `syntaur status list` (or `--json` for mach
 - **After a `remove --force`,** the affected assignments now reference an undefined status. `syntaur doctor` will flag them as invalid. Suggest the user run `syntaur doctor` and either re-add the status (`syntaur status add ...`) or edit each frontmatter to a valid id.
 - **After `transition add`,** the dashboard's transition buttons reflect the new transition only after the cache invalidation above.
 
+## Custom facts and attestations
+
+Beyond the 14 built-in derived-status facts, users can declare their **own** facts under `statuses.facts` and reference them in `phaseLadder` / `disposition` conditions. There are two kinds.
+
+**1. Custom asserted facts** — config-declared `bool` / `number` values, asserted via `syntaur fact set` and stored in a `facts:` frontmatter map:
+
+```yaml
+statuses:
+  facts:
+    - name: qaPassed
+      type: bool
+    - name: storyPoints
+      type: number
+```
+
+```bash
+syntaur fact set <assignment> qaPassed true --project <p>
+syntaur fact set <assignment> storyPoints 5 --project <p>
+```
+
+`bool` accepts case-insensitive `true`/`false`; `number` accepts any finite number. The declared `name` exports a single derive field of the same name (`qaPassed:true`, `storyPoints > 3`). Stored in frontmatter as `facts:\n  qaPassed: "true"`.
+
+**2. Attestation facts** — model "agent X reviewed revision Y with verdict Z". Declared with `type: attestation` and a `binds:` mode:
+
+```yaml
+statuses:
+  facts:
+    - name: codeReview
+      type: attestation
+      binds: plan      # plan | commit | none
+```
+
+```bash
+syntaur attest <assignment> codeReview --agent codex --verdict approved --project <p>
+syntaur attest <assignment> codeReview --agent pi --verdict changes-requested --note "fix the lock" --project <p>
+```
+
+`--verdict` defaults to `approved` (the other value is `changes-requested`). One record per actor — re-attesting **replaces** that actor's record. Stored in an `attestations:` frontmatter list (`{fact, actor, verdict, at, note?}` + binding snapshot).
+
+Each attestation fact exports **five** derive fields (for `codeReview`): `codeReview` (any valid record), `codeReviewApproved`, `codeReviewChangesRequested` (bools), and `codeReviewBy`, `codeReviewApprovedBy` (actor **sets** — use `:` for contains / `IN`-lists, e.g. `codeReviewApprovedBy:"agent:codex"`; quote actor values that contain a `:`). This makes review loops self-modeling — a rung `when: "codeReviewApproved:true"` fires on approval, and `when: "codeReviewChangesRequested:true"` expresses "reviewed but not signed off".
+
+**Revision binding** is what makes attestations self-invalidate:
+- `binds: plan` — bound to the latest plan file + its digest (same semantics as plan approval). A replan or a post-attest plan edit makes the record **stale**; stale records contribute nothing (the fact flips false, the actor drops out of the `*By` sets).
+- `binds: commit` — bound to the workspace branch HEAD sha at attest time. A new commit makes it stale. **Lazy convergence:** dashboard payloads and `ls --query` compute facts fresh per request (always honest), but the *persisted* phase regression lands on the next recompute trigger (any CLI verb, watcher event, config change, or boot sweep) — there is no git watcher.
+- `binds: none` — never stale (a standing sign-off).
+
+**Validation & teeth.** Declared names are validated by `syntaur doctor` (the `derive-config.valid` check): bad name/type/binds and any collision of an exported field with a built-in or another declaration is reported as an error and the offending declaration is dropped (built-ins always win). A derive condition that references an **undeclared** fact still fails at recompute time (`CompileError`), exactly as before. `syntaur fact set` / `syntaur attest` reject undeclared names, wrong types, and invalid verdicts. Every `fact set` / `attest` is recorded in `statusHistory` with its actor and cause, even when no dimension moves.
+
 ## Safety notes
 
 - **`remove` is destructive.** Without `--force` it refuses if any assignment references the id. Don't suggest `--force` without first running `syntaur status remove <id>` (no force) so the user sees the affected list.
 - **`rename` rewrites many files.** It edits `config.md` AND every affected `assignment.md` in a single atomic transaction (with rollback if any write fails partway). Always run `--dry-run` first on a non-trivial codebase so the user sees the per-file diff.
 - **`terminal: true` is load-bearing.** Terminal statuses affect dashboard progress bars and dependency-satisfaction logic — an assignment with a terminal status counts as "done" for downstream `dependsOn` checks and project-rollup status. Don't toggle this on `pending`-style states without thinking.
-- **`init --force` overwrites a custom block.** Use `reset` first if the user wants a clean slate, OR confirm before passing `--force` if they have unsaved customizations.
+- **`init --force` overwrites a custom block.** Use `reset` first if the user wants a clean slate, OR confirm before passing `--force` if they have unsaved customizations. It resets to the built-in defaults and therefore **drops any `statuses.facts` declarations and `derive` rules** along with the custom statuses — every other `status` subcommand (`set`/`add`/`remove`/`rename`/`reorder`/`transition`) preserves them.
 - **Concurrency.** `rename`'s buffer-write-rollback strategy assumes no concurrent writers. Tell the user to close the dashboard / pause other agents during a rename.
 - **`SYNTAUR_HOME` precedence.** If the user has `SYNTAUR_HOME` set, the CLI writes there instead of `~/.syntaur`. Mirror their environment.

package/dashboard/dist/assets/channel-gkqjyV0r.js

@@ -1 +0,0 @@
-import{aq as o,ar as n}from"./mermaid.core-eqq1_dL_.js";const t=(r,a)=>o.lang.round(n.parse(r)[a]);export{t as c};

package/dashboard/dist/assets/classDiagram-VBA2DB6C-D1CF55uI.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-WL4C6EOR-DV11wZKH.js";import{_ as i}from"./mermaid.core-eqq1_dL_.js";import"./chunk-FMBD7UC4-CWHswGwW.js";import"./chunk-JSJVCQXG-DnsqdfIB.js";import"./chunk-55IACEB6-DE34igmQ.js";import"./chunk-KX2RTZJC-FbqVE08c.js";import"./index-Dzh96P4Z.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dashboard/dist/assets/classDiagram-v2-RAHNMMFH-D1CF55uI.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-WL4C6EOR-DV11wZKH.js";import{_ as i}from"./mermaid.core-eqq1_dL_.js";import"./chunk-FMBD7UC4-CWHswGwW.js";import"./chunk-JSJVCQXG-DnsqdfIB.js";import"./chunk-55IACEB6-DE34igmQ.js";import"./chunk-KX2RTZJC-FbqVE08c.js";import"./index-Dzh96P4Z.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dashboard/dist/assets/clone-Cx1NBdWo.js

@@ -1 +0,0 @@
-import{b as r}from"./_baseUniq-DGO4Y46J.js";var e=4;function a(o){return r(o,e)}export{a as c};

package/dashboard/dist/assets/stateDiagram-v2-FVOUBMTO-kKo_Asao.js

@@ -1 +0,0 @@
-import{s as e,b as r,a,S as s}from"./chunk-NQ4KR5QH-DcsdDqWQ.js";import{_ as i}from"./mermaid.core-eqq1_dL_.js";import"./chunk-55IACEB6-DE34igmQ.js";import"./chunk-KX2RTZJC-FbqVE08c.js";import"./index-Dzh96P4Z.js";var p={parser:a,get db(){return new s(2)},renderer:r,styles:e,init:i(t=>{t.state||(t.state={}),t.state.arrowMarkerAbsolute=t.arrowMarkerAbsolute},"init")};export{p as diagram};