breakaway 1.0.1-main.1 → 1.0.1-main.3

package/README.md

@@ -14,7 +14,7 @@
   <a href="#run-your-own"><b>Run your own</b></a> ·
   <a href="#how-it-works">How it works</a> ·
   <a href="#docs">Docs</a> ·
-  <a href="https://breakaway.samewave.dev">Website</a> ·
+  <a href="https://leavethepack.dev">Website</a> ·
   <a href="#licence">Licence</a>
 </p>
 
@@ -29,7 +29,7 @@
 Paste this into [Claude Code](https://claude.com/claude-code), in an empty folder:
 
 ```text
-Set up a breakaway board for me. Read https://breakaway.samewave.dev/install.md and follow it.
+Set up a breakaway board for me. Read https://leavethepack.dev/install.md and follow it.
 ```
 
 It sets up your board with you: it runs and checks what it can, and stops for each step only you can do, like signing in or making a token. It never asks for a secret in the chat.
@@ -122,22 +122,22 @@ npx breakaway list --ready
   <img alt="How breakaway is built. Three ways in: the web board, the CLI, and Taskwarrior. They reach one Worker and its Durable Object on your own Cloudflare account, which holds every task. The board talks to GitHub through its own GitHub App, and starts Claude Code cloud agents through your routine; agents work the board through the CLI." src="https://raw.githubusercontent.com/TheAnarchoX/breakaway/main/docs/media/built-dark.png" width="100%">
 </picture>
 
-One Cloudflare Worker serves the API, the web app (Preact), and Taskwarrior sync, and one SQLite Durable Object holds every task, claim, comment, and change. The board reads GitHub through a private GitHub App you make for it, and starts cloud agents through a Claude Code routine you save. [Architecture](https://breakaway.samewave.dev/docs/architecture/) has the rest.
+One Cloudflare Worker serves the API, the web app (Preact), and Taskwarrior sync, and one SQLite Durable Object holds every task, claim, comment, and change. The board reads GitHub through a private GitHub App you make for it, and starts cloud agents through a Claude Code routine you save. [Architecture](https://leavethepack.dev/docs/architecture/) has the rest.
 
 ## Docs
 
 | Read | For |
 | --- | --- |
-| [Run your own board](https://breakaway.samewave.dev/docs/quickstart/) | From nothing to a board that starts agents and updates itself |
-| [Concepts](https://breakaway.samewave.dev/docs/concepts/) | Tasks and work IDs, areas, horizons, claims, dependencies, and how a pull request closes a task |
-| [Playbook](https://breakaway.samewave.dev/docs/playbook/) | Write tasks agents finish, run many agents without collisions, and keep the review load to one person |
-| [Agents](https://breakaway.samewave.dev/docs/agents/) | Cloud agents from the board, local agents, limits, live output, and messaging a running agent |
-| [Ideas, decisions, and pings](https://breakaway.samewave.dev/docs/ideas-decisions-pings/) | Let an agent shape an idea, answer its questions in a form, and get a ping when only you can help |
-| [The CLI](https://breakaway.samewave.dev/docs/cli/) | Every command of `npx breakaway` |
-| [GitHub](https://breakaway.samewave.dev/docs/github/) | Your own private App, how pull requests link to tasks, and merging, promoting, and rolling back |
-| [Taskwarrior](https://breakaway.samewave.dev/docs/taskwarrior/) | Sync, reports, and contexts with Taskwarrior 3 |
-| [Deploying](https://breakaway.samewave.dev/docs/deploying/) | Releases, channels, the Deploy and Update workflows, and rollbacks |
-| [FAQ](https://breakaway.samewave.dev/docs/faq/) | The licence, your data, what it works with, and what it won't do |
+| [Run your own board](https://leavethepack.dev/docs/quickstart/) | From nothing to a board that starts agents and updates itself |
+| [Concepts](https://leavethepack.dev/docs/concepts/) | Tasks and work IDs, areas, horizons, claims, dependencies, and how a pull request closes a task |
+| [Playbook](https://leavethepack.dev/docs/playbook/) | Write tasks agents finish, run many agents without collisions, and keep the review load to one person |
+| [Agents](https://leavethepack.dev/docs/agents/) | Cloud agents from the board, local agents, limits, live output, and messaging a running agent |
+| [Ideas, decisions, and pings](https://leavethepack.dev/docs/ideas-decisions-pings/) | Let an agent shape an idea, answer its questions in a form, and get a ping when only you can help |
+| [The CLI](https://leavethepack.dev/docs/cli/) | Every command of `npx breakaway` |
+| [GitHub](https://leavethepack.dev/docs/github/) | Your own private App, how pull requests link to tasks, and merging, promoting, and rolling back |
+| [Taskwarrior](https://leavethepack.dev/docs/taskwarrior/) | Sync, reports, and contexts with Taskwarrior 3 |
+| [Deploying](https://leavethepack.dev/docs/deploying/) | Releases, channels, the Deploy and Update workflows, and rollbacks |
+| [FAQ](https://leavethepack.dev/docs/faq/) | The licence, your data, what it works with, and what it won't do |
 
 <details>
 <summary><b>Run it locally</b></summary>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "breakaway",
-  "version": "1.0.1-main.1",
+  "version": "1.0.1-main.3",
   "description": "The task board for you and your coding agents: a Cloudflare Worker, its web app, Taskwarrior sync, and the CLI (npx breakaway).",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/prompts/install.md

@@ -2,7 +2,7 @@
 
 You're helping someone set up their own breakaway board: a task board for them and their coding agents, on their own Cloudflare account. It's theirs: they own it, run it, and decide. You do the typing. This file is the whole job. Read it to the end before you start, then work through it one step at a time.
 
-The owner started you with something like: "Set up a breakaway board for me. Read https://breakaway.samewave.dev/install.md and follow it." The full guide behind these steps is at https://breakaway.samewave.dev/docs/quickstart/, if a step needs more detail.
+The owner started you with something like: "Set up a breakaway board for me. Read https://leavethepack.dev/install.md and follow it." The full guide behind these steps is at https://leavethepack.dev/docs/quickstart/, if a step needs more detail.
 
 ## How you work
 
@@ -125,4 +125,4 @@ Only with a Claude plan that has routines. Otherwise skip to step 7.
 
 Run `npx breakaway connections` and go through anything that still needs attention, with the fix each row gives. Taskwarrior is optional: if they use it, `npx breakaway setup` connects it.
 
-Then add a first task together, in a checkout of the repository: `npx breakaway add "<something small that needs doing>" --project <area> --tag agent --horizon now`. Show them the board. Tell them where things are: the board in their browser, `npx breakaway help` for the CLI, and the docs at https://breakaway.samewave.dev/docs/. Then stop. From here on, the board is theirs.
+Then add a first task together, in a checkout of the repository: `npx breakaway add "<something small that needs doing>" --project <area> --tag agent --horizon now`. Show them the board. Tell them where things are: the board in their browser, `npx breakaway help` for the CLI, and the docs at https://leavethepack.dev/docs/. Then stop. From here on, the board is theirs.

package/scripts/tasks/init.js

@@ -24,12 +24,11 @@ export const CLI_PACKAGE = 'breakaway@next';
  */
 export const CLI_ENTRIES = ['scripts/tasks.mjs', 'scripts/tasks/session-hook.mjs', 'scripts/tasks/message-wait.mjs'];
 /**
- * While breakaway is private, nothing reaches npm (BRK-57), so `npx breakaway@next hook …` fails silently in another
- * repository and a started agent's live output never reaches the board (BRK-64). Until it is public, repos init copies
- * the two hooks and what they import under HOOKS_DIR and settings.json runs them from there. Once breakaway is
- * public, set this to false: the hooks run through npx again, and `repos init --update` removes the copy.
+ * While breakaway was private, nothing reached npm (BRK-57), so repos init copied the two hooks and what they import
+ * under HOOKS_DIR and settings.json ran them from there (BRK-64). breakaway is public and on npm now, so the hooks run
+ * through npx again (BRK-69), and `repos init --update` removes a copy an older repos init left.
  */
-export const HOOKS_FROM_COPY = true;
+export const HOOKS_FROM_COPY = false;
 /** The session hooks' entry files, and where their copy goes: its own folder, so it never touches the repository's src/. */
 export const HOOK_ENTRIES = ['scripts/tasks/session-hook.mjs', 'scripts/tasks/message-wait.mjs'];
 export const HOOKS_DIR = 'tools/tasks/cli/';

package/src/cli-version.js

@@ -5,5 +5,5 @@
  * bump CLI_VERSION and set CLI_FINGERPRINT to the value it prints. Constants only: the board's Worker imports it,
  * so it lives in the board's package (CLD-135) and the CLI imports it from here.
  */
-export const CLI_VERSION = 35;
-export const CLI_FINGERPRINT = '38b6844e896df3f7';
+export const CLI_VERSION = 36;
+export const CLI_FINGERPRINT = '252bee7de1e280f7';