@olhapi/maestro-darwin-x64 0.1.4 → 0.1.5-rc.10

package/README.md

@@ -83,6 +83,9 @@ For local development or unsupported platforms:
 go build -o maestro ./cmd/maestro
 ```
 
+This build path is pure Go. You do not need a C compiler or a system SQLite
+development package for the standard `make build` / `make test` flow.
+
 Local contributor Docker build:
 
 ```bash
@@ -291,13 +294,17 @@ Fresh `maestro workflow init --defaults` output currently defaults to:
 - `agent.mode: app_server`
 - `agent.dispatch_mode: parallel`
 - `codex.command: codex app-server`
-- `codex.expected_version: 0.114.0`
+- `codex.expected_version: 0.116.0`
 - `codex.approval_policy: never`
 - `codex.initial_collaboration_mode: default` for fresh `app_server` threads
+- `phases.review.enabled: true`
+- `phases.done.enabled: true`
 - runtime permission profiles now live in the DB per project/issue instead of `WORKFLOW.md`
 
 `initial_collaboration_mode: default` keeps unattended runs execution-first for a fresh `app_server` thread. Use `plan` only when you explicitly want a plan-gated startup mode. Interactive approvals and `requestUserInput` prompts still depend on using a non-`never` approval policy, and those prompts are queued through the dashboard's global interrupt panel. Resumed threads and `stdio` runs do not use that startup-mode path.
 
+Interactive `maestro workflow init` now walks through `workspace.root`, `codex.command`, `agent.mode`, `agent.dispatch_mode`, `agent.max_concurrent_agents`, `agent.max_turns`, and `agent.max_automatic_retries`, then asks for `codex.approval_policy` and `codex.initial_collaboration_mode` only for `app_server`. Those extra tuning knobs remain interactive-only; `--defaults` stays the stable scripted path, and the existing flags still override only the workspace root, Codex command, and agent mode.
+
 Supported prompt-template variables are:
 
 - `{{ issue.identifier }}`
@@ -311,13 +318,13 @@ Supported prompt-template variables are:
 - `{{ attempt }}`
 
 When a project has a description, Maestro's default implementation, review, and done prompts include it automatically under a `Project context:` section. Custom workflows can place `{{ project.description }}` wherever they want.
-The default done prompt now focuses on merge-back, PR readiness, and blocker reporting instead of asking for a preview artifact.
+The default done prompt now focuses on merge-back, worktree cleanup, PR readiness, and blocker reporting instead of asking for a preview artifact.
 
 The checked-in [`WORKFLOW.md`](WORKFLOW.md) is this repository's own workflow example. It is not guaranteed to match fresh `workflow init` defaults exactly.
 
 Missing-file behavior differs by command:
 
-- `maestro workflow init` creates `WORKFLOW.md` explicitly
+- `maestro workflow init` creates `WORKFLOW.md` explicitly; `maestro init` is a root-level alias for the same command
 - `maestro run` bootstraps a missing file automatically
 - `maestro verify` checks readiness and returns remediation guidance
 - `maestro doctor` runs the same readiness checks with different presentation
@@ -361,6 +368,9 @@ pnpm run website:dev
 pnpm run website:check
 ```
 
+The standard Go build/test path is now toolchain-light. The remaining
+`sqlite3` CLI usage lives in a few optional shell scripts under `scripts/`.
+
 Repo-managed Git hooks stay targeted:
 
 - staged Go changes run package-scoped Go tests

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@olhapi/maestro-darwin-x64",
-  "version": "0.1.4",
+  "version": "0.1.5-rc.10",
   "description": "Maestro CLI binary for macOS x64",
   "license": "MIT",
   "files": [