@olhapi/maestro-darwin-x64 0.1.0-rc.2 → 0.1.0-rc.4

package/README.md

@@ -2,6 +2,9 @@
 
 Maestro is a local-first orchestration runtime for agent-driven software work.
 
+Website: [maestro.olhapi.com](https://maestro.olhapi.com/)
+Repository: [github.com/olhapi/maestro](https://github.com/olhapi/maestro)
+
 It combines a SQLite-backed tracker, an orchestrator that reads `WORKFLOW.md`, a private MCP daemon bridged by `maestro mcp`, and an HTTP server that serves the embedded dashboard plus JSON/WebSocket APIs.
 
 Maestro stays local-first even when a project syncs issues from Linear. Provider-backed issues are synchronized into the local store, then supervised through the same local queue, runtime state, MCP tools, and dashboard surfaces as local kanban issues.
@@ -85,7 +88,7 @@ This writes a repo-local `WORKFLOW.md` with the default orchestration settings a
 ### 2. Create a project and queue some work
 
 ```bash
-maestro project create "My App" --repo /absolute/path/to/my-app --desc "Example project"
+maestro project create "My App" --repo /absolute/path/to/my-app --desc "Repo-wide Codex guidance: use pnpm, keep changes scoped, and run focused validation for touched packages."
 maestro issue create "Add login page" --project <project_id> --labels feature,ui
 maestro issue create "Fix auth bug" --project <project_id> --priority 1 --labels bug
 maestro issue move ISS-1 ready
@@ -93,6 +96,8 @@ maestro issue move ISS-1 ready
 
 Projects default to the local `kanban` provider. You can also register a project with limited Linear-backed sync by passing `--provider linear --provider-project-ref <slug>` and, if needed, `--provider-endpoint` or `--provider-assignee`.
 
+Project descriptions are not just dashboard notes. Maestro passes `project.description` into every implementation, review, and done prompt by default, so use it for standing requirements, conventions, and validation expectations Codex should keep in mind for every issue.
+
 ### 3. Start the daemon
 
 ```bash
@@ -107,22 +112,39 @@ Issue images are stored next to the active database under `assets/images`. With
 
 The preview warning on `run` is intentional. Pass `--i-understand-that-this-will-be-running-without-the-usual-guardrails` only when unattended Codex execution is actually what you want.
 
-### 4. Expose the tracker to MCP clients
+### 4. Add the Maestro MCP server to your coding agent
+
+Use the setup path that matches your coding agent:
+
+Codex:
+
+```bash
+codex mcp add maestro -- maestro mcp
+```
 
-Add the built or installed binary to your MCP client config:
+Claude Code:
+
+```bash
+claude mcp add maestro -- maestro mcp
+claude mcp add --scope project maestro -- maestro mcp
+```
+
+Other MCP-capable agents:
 
 ```json
 {
   "mcpServers": {
     "maestro": {
-      "command": "/absolute/path/to/maestro",
+      "command": "maestro",
       "args": ["mcp"]
     }
   }
 }
 ```
 
-`maestro mcp` is a stdio bridge into the live `maestro run` daemon for the same database. Start `maestro run` first, then let your MCP client invoke `maestro mcp`.
+If you built Maestro from source and did not add it to your `PATH`, replace `maestro` with the absolute path to the binary.
+
+`maestro mcp` is a stdio bridge into the live `maestro run` daemon for the same database. Start `maestro run` first, then let your coding agent invoke `maestro mcp`.
 
 ### 5. Open the dashboard or use live CLI helpers
 
@@ -250,9 +272,14 @@ Supported prompt-template variables are:
 - `{{ issue.title }}`
 - `{{ issue.description }}`
 - `{{ issue.state }}`
+- `{{ project.id }}`
+- `{{ project.name }}`
+- `{{ project.description }}`
 - `{{ phase }}`
 - `{{ 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 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:

package/package.json

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