wakespace 0.1.3 → 0.1.5

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.5 — 2026-06-01
+
+### Changed
+
+- Implementation stages that require project writes now cap pre-write project
+  exploration. After the budget is exhausted, project tools reject the rest of
+  the worker pass, cancel the run, and route to commit fallback instead of
+  allowing repeated read retries or late writes.
+- Coding-stage project writes now refuse `writeFile` overwrites of existing
+  files, steering workers toward structured `replaceInFile` edits for existing
+  source.
+- Forced commit tools now expose workflow-field JSON schema and reject invalid
+  field payload types before reducer application.
+
+## 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

package/README.md

@@ -58,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
@@ -77,7 +92,15 @@ dependencies already resolve). From `packages/wakespace`:
 
 ```sh
 bun run release:dry   # build all platforms + npm publish --dry-run everywhere
-bun run release       # build all platforms + publish for real (needs npm auth)
+NPM_TOKEN=... bun run release
+```
+
+The script performs `npm whoami` with the same auth config before any real
+publish. If `NPM_TOKEN` is loaded only when your shell starts at the repository
+root, run the release from the root with an explicit environment override:
+
+```sh
+NPM_TOKEN="$NPM_TOKEN" bun --cwd packages/wakespace scripts/release.ts
 ```
 
 The platform matrix lives in `scripts/build-platforms.ts`; it stamps each
@@ -86,6 +109,13 @@ platform package with the launcher's version and fails if
 `package.json` (version + each `optionalDependencies` entry) when cutting a
 release. Run `bun run release:dry` before publishing.
 
+When publishing from this monorepo, do not rely on npm discovering a local
+`.npmrc` from generated package directories. The release script maps `NPM_TOKEN`
+to a temporary `NPM_CONFIG_USERCONFIG` file and passes that config explicitly to
+each `npm publish` child process, then removes it. This avoids the recurring
+case where `npm whoami` succeeds in one directory but platform-package publish
+fails with auth/404 errors.
+
 ## License
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wakespace",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "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.3",
-    "wakespace-darwin-x64": "0.1.3",
-    "wakespace-linux-x64": "0.1.3",
-    "wakespace-linux-arm64": "0.1.3",
-    "wakespace-linux-x64-musl": "0.1.3",
-    "wakespace-linux-arm64-musl": "0.1.3",
-    "wakespace-windows-x64": "0.1.3"
+    "wakespace-darwin-arm64": "0.1.5",
+    "wakespace-darwin-x64": "0.1.5",
+    "wakespace-linux-x64": "0.1.5",
+    "wakespace-linux-arm64": "0.1.5",
+    "wakespace-linux-x64-musl": "0.1.5",
+    "wakespace-linux-arm64-musl": "0.1.5",
+    "wakespace-windows-x64": "0.1.5"
   },
   "devDependencies": {
     "@types/bun": "latest",