syntaur 0.47.0 → 0.49.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "syntaur",
-  "version": "0.47.0",
+  "version": "0.49.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.47.0",
+  "version": "0.49.0",
   "skills": [
     "./skills/syntaur-protocol",
     "./skills/grab-assignment",

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

@@ -66,6 +66,13 @@ After every mutating subcommand, run `syntaur status list` (or `--json` for mach
 
 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.
 
+**Two ways to declare them**, kept in sync because both write the same `statuses.facts` block:
+
+- **Dashboard** — the Settings page has a **Facts** section that lists every declared fact and lets the user add/edit/delete declarations (name + kind, plus `binds` for attestations) with the same validation the CLI/doctor enforce. Deleting a fact that a derive rule still references prompts for confirmation before saving, and a Facts save preserves the existing statuses, ordering, and derive rules.
+- **Config / CLI** — hand-edit the `statuses.facts` block in `~/.syntaur/config.md` directly (the shapes below).
+
+Declaring a fact (either way) only defines the vocabulary; asserting per-assignment values is always `syntaur fact set` / `syntaur attest`.
+
 **1. Custom asserted facts** — config-declared `bool` / `number` values, asserted via `syntaur fact set` and stored in a `facts:` frontmatter map:
 
 ```yaml

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

@@ -1,6 +1,6 @@
 {
   "name": "syntaur",
-  "version": "0.47.0",
+  "version": "0.49.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

@@ -66,6 +66,13 @@ After every mutating subcommand, run `syntaur status list` (or `--json` for mach
 
 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.
 
+**Two ways to declare them**, kept in sync because both write the same `statuses.facts` block:
+
+- **Dashboard** — the Settings page has a **Facts** section that lists every declared fact and lets the user add/edit/delete declarations (name + kind, plus `binds` for attestations) with the same validation the CLI/doctor enforce. Deleting a fact that a derive rule still references prompts for confirmation before saving, and a Facts save preserves the existing statuses, ordering, and derive rules.
+- **Config / CLI** — hand-edit the `statuses.facts` block in `~/.syntaur/config.md` directly (the shapes below).
+
+Declaring a fact (either way) only defines the vocabulary; asserting per-assignment values is always `syntaur fact set` / `syntaur attest`.
+
 **1. Custom asserted facts** — config-declared `bool` / `number` values, asserted via `syntaur fact set` and stored in a `facts:` frontmatter map:
 
 ```yaml

package/skills/manage-statuses/SKILL.md

@@ -66,6 +66,13 @@ After every mutating subcommand, run `syntaur status list` (or `--json` for mach
 
 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.
 
+**Two ways to declare them**, kept in sync because both write the same `statuses.facts` block:
+
+- **Dashboard** — the Settings page has a **Facts** section that lists every declared fact and lets the user add/edit/delete declarations (name + kind, plus `binds` for attestations) with the same validation the CLI/doctor enforce. Deleting a fact that a derive rule still references prompts for confirmation before saving, and a Facts save preserves the existing statuses, ordering, and derive rules.
+- **Config / CLI** — hand-edit the `statuses.facts` block in `~/.syntaur/config.md` directly (the shapes below).
+
+Declaring a fact (either way) only defines the vocabulary; asserting per-assignment values is always `syntaur fact set` / `syntaur attest`.
+
 **1. Custom asserted facts** — config-declared `bool` / `number` values, asserted via `syntaur fact set` and stored in a `facts:` frontmatter map:
 
 ```yaml

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

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

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

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-WL4C6EOR-Dqvl_14m.js";import{_ as i}from"./mermaid.core-C0KQpDyW.js";import"./chunk-FMBD7UC4-D3siQyQ4.js";import"./chunk-JSJVCQXG-DKGuxEMf.js";import"./chunk-55IACEB6-BJOEnwNN.js";import"./chunk-KX2RTZJC-CNIWWO2F.js";import"./index-C3kYxhbQ.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-Bkoc7orC.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-WL4C6EOR-Dqvl_14m.js";import{_ as i}from"./mermaid.core-C0KQpDyW.js";import"./chunk-FMBD7UC4-D3siQyQ4.js";import"./chunk-JSJVCQXG-DKGuxEMf.js";import"./chunk-55IACEB6-BJOEnwNN.js";import"./chunk-KX2RTZJC-CNIWWO2F.js";import"./index-C3kYxhbQ.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-CltBg7cH.js

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