wakespace 0.1.2 → 0.1.4

package/CHANGELOG.md

@@ -3,6 +3,57 @@
 All notable changes to `wakespace` are documented here. This project adheres to
 [Semantic Versioning](https://semver.org/).
 
+## 0.1.4 — 2026-06-01
+
+### Added
+
+- Wake chronicles now record `wake.progress` events for worker and commit tool
+  calls, so `inspect wait` can observe long wakes before they finish.
+- Wake chronicles now record bounded worker diagnostics for each worker and
+  forced commit pass, including state-command counts, project tool/write
+  evidence, tool-call summaries, and first-pass text previews.
+- Added `inspect wait`, a read-side command that waits for the next chronicle
+  event (optionally scoped by task) or exits on timeout.
+- AI SDK project workers now get `replaceInFile` for exact small source edits;
+  wakespace counts it as project write evidence alongside `writeFile`.
+- CLI task creation now accepts `--parent`, and `submit` accepts `transition`
+  so a lead can split broad work into child tasks and explicitly accept results.
+
+### Fixed
+
+- Forced commit fallback now coalesces duplicate block/cancel calls so a worker
+  retry does not create misleading `command.rejected` chronicle noise.
+- Wake diagnostics now label project write evidence generically as
+  `projectWrites` because either `writeFile` or `replaceInFile` can satisfy it.
+- Project write evidence now counts only successful edit tool results, and the
+  forced commit fallback also runs when the worker only records non-advancing
+  commands such as `append_note`.
+
+### Changed
+
+- `chronicle --text` now renders structured facts for diagnostics, forced
+  commits, and progress rows instead of relying only on prose summaries.
+- Default wake step budget increased from 6 to 12 so development workers have
+  enough room to inspect, edit, and commit state in one small implementation
+  wake.
+- Development implement-stage instructions now prefer `replaceInFile` for
+  localized edits and explicitly warn workers not to spend the wake only on
+  inspection after the edit target is clear.
+
+## 0.1.3 — 2026-06-01
+
+### Changed
+
+- Default CLI state now resolves to `~/.wakespace` through `WAKESPACE_HOME`.
+  Legacy `WAKESPACE_DIR` and `--dir` remain explicit store overrides.
+- Project definitions and memory now write to `projects/<id>/project.yaml` and
+  `projects/<id>/memory.md`.
+- New task timelines and projections now write under
+  `projects/<id>/state/`, while legacy flat state remains readable.
+- No-state-command fallback passes now use stage policy: planning/design-style
+  stages may commit workflow fields without project writes, while stages marked
+  `requiresProjectWrite` still block without `writeFile` evidence.
+
 ## 0.1.2 — 2026-06-01
 
 ### Added

package/README.md

@@ -34,8 +34,20 @@ After install:
 wakespace help
 ```
 
-The default workspace directory is `.wakespace`. Override it with
-`WAKESPACE_DIR` or the CLI `--dir` flag.
+The default workspace home is `~/.wakespace`. Override it with `WAKESPACE_HOME`.
+The legacy `WAKESPACE_DIR` environment variable and CLI `--dir` flag still act
+as explicit store overrides for tests, isolated smokes, and migration.
+
+The normal home layout keeps user coordination state out of source checkouts:
+
+```text
+~/.wakespace/
+  workers/<id>.yaml
+  projects/<projectId>/project.yaml
+  projects/<projectId>/memory.md
+  projects/<projectId>/state/events/<taskId>.jsonl
+  projects/<projectId>/state/projections/<taskId>.json
+```
 
 Agent-facing commands default to JSON. Use `--text` for ad-hoc human text on
 commands such as `status`, `task`, `project list`, and `worker list`.
@@ -46,6 +58,21 @@ For a human-readable snapshot of projects, workers, tasks, and recent activity:
 wakespace overview
 ```
 
+To coordinate with a concurrently running wake without streaming `run`, wait
+for the next chronicle event:
+
+```sh
+wakespace inspect wait --task <taskId> --timeout 30000
+```
+
+When a task is too broad, split a narrower child task and let the lead merge
+accepted fields back into the parent:
+
+```sh
+wakespace create "small bounded change" --parent <parentTaskId> --workflow general
+wakespace submit <taskId> transition "accepted"
+```
+
 ## Live Smoke
 
 ```sh
@@ -72,8 +99,7 @@ The platform matrix lives in `scripts/build-platforms.ts`; it stamps each
 platform package with the launcher's version and fails if
 `optionalDependencies` drift out of sync. Bump the version in both
 `package.json` (version + each `optionalDependencies` entry) when cutting a
-release. The root `bun run release:check` still runs the typecheck/test/build
-gate plus a launcher dry-run.
+release. Run `bun run release:dry` before publishing.
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wakespace",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "Durable wake-loop workspace for agent-driven project development.",
   "type": "module",
   "bin": {
@@ -42,13 +42,13 @@
   },
   "homepage": "https://github.com/lidessen/wakespace/tree/main/packages/wakespace#readme",
   "optionalDependencies": {
-    "wakespace-darwin-arm64": "0.1.2",
-    "wakespace-darwin-x64": "0.1.2",
-    "wakespace-linux-x64": "0.1.2",
-    "wakespace-linux-arm64": "0.1.2",
-    "wakespace-linux-x64-musl": "0.1.2",
-    "wakespace-linux-arm64-musl": "0.1.2",
-    "wakespace-windows-x64": "0.1.2"
+    "wakespace-darwin-arm64": "0.1.4",
+    "wakespace-darwin-x64": "0.1.4",
+    "wakespace-linux-x64": "0.1.4",
+    "wakespace-linux-arm64": "0.1.4",
+    "wakespace-linux-x64-musl": "0.1.4",
+    "wakespace-linux-arm64-musl": "0.1.4",
+    "wakespace-windows-x64": "0.1.4"
   },
   "devDependencies": {
     "@types/bun": "latest",