@atolis-hq/wake 0.3.0 → 0.3.2

package/README.md

@@ -108,8 +108,8 @@ For more detail, see [docs/vision.md](docs/vision.md) and
   provider.
 - **Human resumption.** A human can pick up the exact local agent session when a
   direct terminal intervention is the best way forward.
-- **Operator correlation escape hatch.** `wake correlate <workItemKey>
-<resourceUri>` lets an operator hand-declare that a resource (a PR, a Slack
+- **Operator correlation escape hatch.** `wake correlate <resourceUri>
+<workItemId>` lets an operator hand-declare that a resource (a PR, a Slack
   thread, etc.) belongs to an existing work item when nothing detected the
   link automatically. See [docs/configuration.md](docs/configuration.md).
 
@@ -138,10 +138,10 @@ adapters currently exist for:
 - **[Codex](https://openai.com/codex/)**
 - **[Cursor](https://cursor.com/cli)**
 
-Each runner sits behind the same `AgentRunner` contract, so Wake's routing,
+Each runner sits behind the same execution contract, so Wake's routing,
 lifecycle, and sandbox behavior stay the same regardless of which CLI executes
-a given step. A fake runner adapter also exists for zero-token testing of the
-control plane itself. See [docs/runner-comparison.md](docs/runner-comparison.md)
+a given activity. A fake runner adapter also exists for zero-token testing of
+the control plane itself. See [docs/runner-comparison.md](docs/runner-comparison.md)
 for capability differences between runners.
 
 ## Getting Started

package/dist/src/bootstrap/initialise.js

@@ -228,26 +228,28 @@ and either:
 
 ## 2. External integrations
 
-Ask the user which external source(s) should feed Wake work items (an issue
-tracker, for example), and whether it should start polling immediately or
-stay off until they're ready.
+Ask the user:
 
-Add an entry under \`integrations\` in \`config.yaml\`, for example:
+- Which external source or sources should feed Wake work items?
+- Which provider-specific rule should opt work in?
+- Should polling start immediately, or stay disabled until they are ready?
+
+Configure each provider under \`integrations\` in \`config.yaml\`:
 
 \`\`\`yaml
 integrations:
   <name>:
     provider: <provider-id>
     enabled: true # or leave false to configure now, enable later
-    # the remaining fields are specific to that provider — ask the user, or
-    # check that provider's own configuration reference, for the exact
-    # fields it needs (which repositories/projects to watch, credentials,
-    # which events opt an item in).
+    # Provider-specific fields select resources, configure credentials,
+    # and define which observed work is admitted.
 \`\`\`
 
-This file intentionally does not hardcode any one provider's field shape —
-Wake's integration providers are pluggable, and each owns its own
-configuration schema.
+The fields beneath an integration entry are provider-owned and validated by
+that provider. Consult
+https://github.com/atolis-hq/wake/blob/main/docs/configuration.md for each
+supported provider's current schema, credential guidance, polling controls,
+and intake rules.
 
 ## 3. Credential mounts (check before asking)
 

package/dist/src/bootstrap/version.js

@@ -108,4 +108,4 @@ export function resolveWakeVersion(options = {}) {
         return `g${headHash.slice(0, 7)}`;
     return '0.1.0-dev';
 }
-export const wakeVersion = "g31cb844";
+export const wakeVersion = "gfcc686b";

package/dist/src/main.js

@@ -1,3 +1,4 @@
+#!/usr/bin/env node
 import { spawn } from 'node:child_process';
 import { access } from 'node:fs/promises';
 import { join } from 'node:path';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atolis-hq/wake",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Local autonomous agent control plane for software development",
   "license": "Apache-2.0",
   "repository": {
@@ -32,7 +32,7 @@
     "access": "public"
   },
   "scripts": {
-    "build": "tsc -p tsconfig.json && node scripts/embed-version.mjs",
+    "build": "tsc -p tsconfig.json && node scripts/embed-version.mjs && node scripts/check-cli-entrypoint.mjs",
     "prepack": "npm run build && npm run build:web",
     "test": "vitest run",
     "test:fast": "npm run test:unit",

package/templates/SETUP.md

@@ -1,115 +0,0 @@
-?# Wake Setup Guide (for the assisting agent)
-
-You are reading this because a human just ran `wake init` and asked you to
-help finish configuring this Wake home. This file is written as instructions
-to you, the assisting agent — not as prose for a human to read top to bottom.
-
-Read `config.yaml` and `config.workflows.yaml` in this directory now — both
-already exist with working defaults from `wake init`. Everything below tells
-you which fields in those two files to change. Edit them directly; don't
-create a new `config.<label>.yaml` split unless the user asks for one.
-
-Work through the three sections below in order, asking the user only what's
-asked in each section. Each section links the relevant part of the hosted
-`docs/configuration.md` for full field-by-field reference beyond what's
-summarized here.
-
-## 1. GitHub source
-
-Ask the user:
-
-- Which GitHub repo(s) should Wake monitor for issues? (`owner/repo` format)
-- Should polling start immediately, or stay off until they're ready?
-
-Edit in `config.yaml`:
-
-```yaml
-sources:
-  github:
-    enabled: true # or leave false to configure now, enable later
-    repos: [owner/repo] # one or more, owner/repo format
-```
-
-Tell the user: once enabled, Wake adds/removes a
-`wake:status.pending|working|failed|completed` label on issues it works, and
-preserves any other labels already on the issue.
-
-Full reference:
-https://github.com/atolis-hq/wake/blob/main/docs/configuration.md#sourcesgithub
-
-## 2. Runner and runnerPool
-
-Ask the user which agent CLI(s) they have authenticated on this host:
-Claude, Codex, and/or Cursor.
-
-`config.workflows.yaml` already has example `runners` entries for
-`claude-haiku`, `claude-opus`, `codex-mini`, `codex-flagship`, and
-`cursor-composer`, but every runnerPool (`light`/`standard`/`deep`, with
-`defaultRunnerPool: standard`) still points at the placeholder `fake` runner — none
-of them route to a real runner yet. Don't rewrite this from scratch — pick
-which runner(s) the user actually has access to, and either:
-
-- repoint `runnerPools` so each runnerPool lists the real named runner(s) the user can
-  actually use instead of `fake`, or
-- if the user has a runner not already listed (a different model, a
-  different CLI), add a new named entry under `runners` following the
-  existing pattern, then reference it from `runnerPools`.
-- remove entries which are not needed.
-
-Full reference:
-https://github.com/atolis-hq/wake/blob/main/docs/configuration.md#runners
-and
-https://github.com/atolis-hq/wake/blob/main/docs/configuration.md#runnerPools
-
-## 3. Credential mounts (check before asking)
-
-Do not start by asking the user where their credentials are. First check the
-host filesystem yourself for the files below, matching whichever runner(s)
-were chosen in step 2:
-
-- Claude: `~/.claude/.credentials.json` and `~/.claude/settings.json`
-- Codex: `~/.codex/config.toml` and `~/.codex/auth.json`
-- Cursor: `~/.config/cursor/auth.json`
-
-For each file that exists, propose adding it to `sandbox.extraMounts` in
-`config.yaml`, for example:
-
-```yaml
-sandbox:
-  extraMounts:
-    - source: /home/alice/.claude/.credentials.json
-      target: /home/wake/.claude/.credentials.json
-      readOnly: true
-    - source: /home/alice/.claude/settings.json
-      target: /home/wake/.claude/settings.json
-      readOnly: false
-```
-
-`.credentials.json`/`auth.json` should be `readOnly: true` unless the user
-wants the sandbox able to refresh tokens on the host's behalf. `settings.json`
-must stay `readOnly: false` — Claude plugin commands write to it. Use the
-actual host home directory path (resolve `~` yourself; don't write a literal
-tilde into YAML).
-
-Never mount the whole `~/.claude`, `~/.codex`, or `~/.cursor` directory —
-only the specific files listed above. Mounting the whole directory leaks
-OS-specific absolute paths (e.g. Windows plugin cache paths) into the Linux
-sandbox and can cause the sandbox to overwrite the host's plugin bookkeeping.
-
-Only if none of the expected files exist for the runner the user chose, ask
-them directly where their credentials live (e.g. a custom `CODEX_HOME`).
-
-Full reference:
-https://github.com/atolis-hq/wake/blob/main/docs/configuration.md#sandbox
-
-## After config looks right
-
-Don't try to explain the sandbox lifecycle yourself — point the user at (or
-fetch, if you have web access):
-
-- https://github.com/atolis-hq/wake/blob/main/docs/getting-started.md —
-  `wake sandbox build` / `up` / `setup` / `exec` / `down`
-- https://github.com/atolis-hq/wake/blob/main/docs/runner-comparison.md —
-  deeper comparison of runner tradeoffs if the user asks which to pick
-- https://github.com/atolis-hq/wake/blob/main/docs/configuration.md — every
-  config field, if something here doesn't cover their situation