@ai-dossier/cli 0.93.2-next.728.1 → 0.93.2-next.729.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +10 -3
  2. package/package.json +4 -4
package/README.md CHANGED
@@ -1791,12 +1791,19 @@ per running parallel member) and stops unfinished members atomically. `abandon`
1791
1791
  State is written atomically (tmp + fsync + rename), so a process killed between writes
1792
1792
  always leaves the previous complete state, and a scheduler restart resumes identically
1793
1793
  from `state.json` (pre-#464/#468/#472/#500/#505/#504 state files — schema
1794
- 1.0.0/1.1.0/1.2.0/1.3.0/1.4.0/1.5.0/1.6.0 — migrate to 1.7.0 on load). A corrupt state file is a loud
1795
- error naming the file — never a silent queue reset — except a state file written by a
1794
+ 1.0.0/1.1.0/1.2.0/1.3.0/1.4.0/1.5.0/1.6.0 — migrate on load). Corrupt state fails closed
1795
+ with record-local repair guidance. Eligible malformed terminal batches are instead
1796
+ isolated after durable preservation in `quarantine/<sha256>.json` and a companion
1797
+ manifest; commands warn and continue with inert placeholders. Original cleanup
1798
+ obligations require operator reconciliation. See the scheduler package README's
1799
+ “Corrupt state is loud” contract for the recovery/refusal and locking boundaries.
1800
+ A state file written by a
1796
1801
  newer schema than the installed engine, which is not corruption: `load()` throws the more
1797
1802
  specific `EngineTooOldError` (#537), pointing at an engine upgrade
1798
1803
  (`npm i -g @ai-dossier/cli@latest`) rather than at deleting real queue data. Concurrency is
1799
- serialized by a `.sched-lock` directory mutex (stolen from dead holders). `config.json`
1804
+ serialized by the state mutex, including reads (directory write access required).
1805
+ Linux holds a permanent `.sched-lock.guard` kernel lock; never remove that file.
1806
+ Non-Linux stale-directory takeover requires verified manual reconciliation. `config.json`
1800
1807
  holds `max_slots` (default 3, bounds concurrently-live units), `stall_timeout_ms` (default
1801
1808
  1 800 000 — but the `implement` phase defaults to 5 400 000, overridable per phase via
1802
1809
  `dispatch.phase_stall_timeout_ms: {"<phase>": <ms>}`, #495), `reconcile_interval_ms`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ai-dossier/cli",
3
- "version": "0.93.2-next.728.1",
3
+ "version": "0.93.2-next.729.1",
4
4
  "description": "CLI for signed, versioned agent skills and model-driven orchestration: create, verify, sign, publish, and install skills for Claude Code, Codex, OpenCode, and LLM tools.",
5
5
  "main": "dist/cli.js",
6
6
  "bin": {
@@ -56,9 +56,9 @@
56
56
  "registry": "https://registry.npmjs.org"
57
57
  },
58
58
  "dependencies": {
59
- "@ai-dossier/core": "1.17.0-next.728.1",
60
- "@ai-dossier/sched": "0.70.0-next.728.1",
61
- "@ai-dossier/worktree-pool": "0.7.7-next.728.1",
59
+ "@ai-dossier/core": "1.17.0-next.729.1",
60
+ "@ai-dossier/sched": "0.70.1-next.729.1",
61
+ "@ai-dossier/worktree-pool": "0.7.7-next.729.1",
62
62
  "commander": "^12.1.0",
63
63
  "yaml": "^2.8.3"
64
64
  },