@hagicode/cli 0.1.0-dev.54.1.372ef38 → 0.1.0-dev.55.1.790ae59

package/dist/cli.js

@@ -1,3 +1,3 @@
 #!/usr/bin/env node
-Object.defineProperty(exports,Symbol.toStringTag,{value:"Module"});const s=require("./chunks/main-BrAlo52u.js");s.runCli().then(e=>{e!==0&&(process.exitCode=e)}).catch(e=>{const n=e instanceof Error?e.stack??e.message:String(e);process.stderr.write(`${n}
+Object.defineProperty(exports,Symbol.toStringTag,{value:"Module"});const s=require("./chunks/main-B-hAwHb9.js");s.runCli().then(e=>{e!==0&&(process.exitCode=e)}).catch(e=>{const n=e instanceof Error?e.stack??e.message:String(e);process.stderr.write(`${n}
 `),process.exitCode=s.EXIT_CODES.UNKNOWN});

package/dist/main.js

@@ -1 +1 @@
-Object.defineProperty(exports,Symbol.toStringTag,{value:"Module"});const e=require("./chunks/main-BrAlo52u.js");exports.createCliApp=e.createCliApp;exports.runCli=e.runCli;
+Object.defineProperty(exports,Symbol.toStringTag,{value:"Module"});const e=require("./chunks/main-B-hAwHb9.js");exports.createCliApp=e.createCliApp;exports.runCli=e.runCli;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hagicode/cli",
-  "version": "0.1.0-dev.54.1.372ef38",
+  "version": "0.1.0-dev.55.1.790ae59",
   "description": "HagiCode CLI for project, proposal, vault, chat, and AutoTask management.",
   "homepage": "https://github.com/HagiCode-org/cli#readme",
   "bugs": {

package/skills/hagi/references/saga.md

@@ -108,9 +108,19 @@ and `updatedAt`. `items <saga-id> --json` returns `{ "sagaId": "...", "items": [
 canonical `id`, `title`, `state`, `cmd`, and `note`.
 
 `status <saga-id> --json` returns the `saga-status/2` projection directly, with `schema`, `sagaId`, `revision`, `state`,
-`updatedAt`, `note`, `artifacts`, `nextArtifact`, `counts`, `openAmendments`, and `items`. It derives this view from the
-Saga files; `updatedAt` is the time of this observation, not the execution heartbeat in `runtime/status.json`. The query
-does not refresh or rewrite that stored status, and its default `note` is empty rather than a cached execution note.
+`updatedAt`, `note`, `artifacts`, `nextArtifact`, `counts`, `openAmendments`, and `items`. Counts, artifacts, `nextArtifact`,
+`openAmendments`, and `items` are derived from the Saga files at read time.
+
+`state` and `note` come from the stored snapshot in `runtime/status.json` when it is valid: a `state` of `draft`,
+`planned`, `running`, `paused`, or `done`. The reported `state` and `note` are the stored values as written, so a stored
+`paused` or `done` is reported even when the files derive another state. A stored `running` is the one exception: it is
+honored, with its note, only when the derived state (from the contract revision, artifacts, and item counts) is also
+`running`. Otherwise the derived state applies with an empty `note`, because `running` is the state that goes stale when
+an orchestrator exits. A missing file, unparsable JSON, a non-object document, or any other `state` value falls back to
+the derived state with an empty `note`.
+
+`updatedAt` is the time of this observation, not the execution heartbeat in `runtime/status.json`. The query
+does not refresh or rewrite that stored status, never repairs it, and creates no `runtime/` file or directory.
 
 All three queries are strictly read-only: they do not initialize or repair resources, create runtime files, run the Saga
 tool, or execute acceptance commands. Missing optional draft files use canonical empty-data behavior; malformed or

package/skills/hagi/references/session-data.md

@@ -107,8 +107,9 @@ hagi saga items <saga-id> --project-id <project-id> --json
 ```
 
 These queries read the selected project's Saga files without initializing or repairing them, refreshing runtime status,
-or executing acceptance commands. Status is a fresh `saga-status/2` observation; its `updatedAt` is not the stored
-execution heartbeat in `runtime/status.json`. `init` installs resources and `new` creates a Saga, so run either only
+or executing acceptance commands. Status is a fresh `saga-status/2` observation: its counts and items come from the Saga
+files, and its `state` and `note` may come from a valid stored state in `runtime/status.json` (a stored `running` only
+when the files also derive `running`). Its `updatedAt` is not the stored execution heartbeat in `runtime/status.json`. `init` installs resources and `new` creates a Saga, so run either only
 when the user explicitly asks for that change. Contract and lifecycle operations run through `hagi saga` with the execution token rules in `references/saga.md`.
 
 ### Skills