breakaway 1.2.1-main.27 → 1.2.1-main.29

package/README.md

@@ -175,7 +175,7 @@ breakaway publishes releases and never deploys an install. Every install, the ow
 - **A stable release** `vX.Y.Z` is the owner's: they run the **Release** workflow with the pre-release to promote. The bundle is that pre-release's, unchanged, and the notes cover everything since the last stable.
 - **The CLI** is on npm as [`breakaway`](https://www.npmjs.com/package/breakaway), staged on npm by the same workflow, with provenance, and live once the owner approves it there with 2FA. npm's trusted publishing can't yet read the OIDC identity of a repository as new as this one ([npm/cli#9969](https://github.com/npm/cli/issues/9969)), so until it can, a token that can stage but never publish by itself stands in, in an environment only `main` can use. Every pre-release goes out under the `next` dist-tag, and a stable release as `latest`. `npx breakaway <command>` is `node scripts/tasks.mjs <command>`.
 - **A major release** is one where an install has to do something by hand: a config or binding change, a Durable Object class or migration, a route or cron. Its notes have a **Manual steps** section and its manifest says `manual: true`, which an install's deploy stops on. A change that needs it sets `manual` and `manualSteps` in `release.json`, and the pull request that ships the steps clears them. When the only step is `wrangler deploy` (a new Durable Object class, a cron, a route), it also sets `wranglerDeploy: true`, and an install whose Deploy may run `wrangler deploy` does it itself (the install template's README says when). Data the Durable Object stores changes forward-only and additively, so an install can always go back one release, except across a new Durable Object class, which Cloudflare doesn't roll back.
-- **The version** is `package.json`'s; the release workflow sets it to the pre-release's before it builds. `GET /api/ping` and `GET /api/health` report it as `release`. An install that deploys a stable passes it as the `BREAKAWAY_VERSION` variable, since the bundle was built as the pre-release.
+- **The version** is `package.json`'s; the release workflow sets it to the pre-release's before it builds. Patches count by themselves; for the next minor or major, **Prepare** on the board's GitHub view starts an agent that opens the pull request setting it. `GET /api/ping` and `GET /api/health` report it as `release`. An install that deploys a stable passes it as the `BREAKAWAY_VERSION` variable, since the bundle was built as the pre-release.
 
 </details>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "breakaway",
-  "version": "1.2.1-main.27",
+  "version": "1.2.1-main.29",
   "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/scripts/tasks/cli.js

@@ -145,16 +145,21 @@ export function forceFields(force, by) {
  * `agents new`: the request that makes a task from a prompt and starts an agent on it. It's the checkout's repository
  * unless `--repo` names another. It always says who asks, so the board refuses an agent's name: only the owner starts one.
  * With `decision` (`agents new --decision <ID> ["<note>"]`, BRK-110) the board writes the prompt from that answered
- * decision, in the decision's repository, and the text is the owner's note under it.
+ * decision, in the decision's repository, and the text is the owner's note under it. With `next`
+ * (`agents new --next minor|major ["<note>"]`, BRK-100) it writes the prompt that sets the repository's next version.
  * @param {string} prompt
- * @param {{ repo?: string | null, force?: boolean, by?: string, decision?: string | null }} [options]
+ * @param {{ repo?: string | null, force?: boolean, by?: string, decision?: string | null, next?: string | null }} [options]
  */
-export function generalAgentRequest(prompt, { repo = null, force = false, by, decision = null } = {}) {
+export function generalAgentRequest(prompt, { repo = null, force = false, by, decision = null, next = null } = {}) {
   const text = String(prompt ?? '').trim();
-  if (!text && !decision)
+  if (decision && next) return { error: 'start one from --decision or --next, not both' };
+  if (next && !['minor', 'major'].includes(next))
+    return { error: 'patches count by themselves: --next minor or --next major' };
+  if (!text && !decision && !next)
     return { error: 'say what the agent should do: npx breakaway agents new "Tidy the docs" [--image <file>]' };
+  const board = decision ? { decision } : next ? { next } : null;
   const body = {
-    ...(decision ? { decision, ...(text ? { note: text } : {}) } : { prompt: text }),
+    ...(board ? { ...board, ...(text ? { note: text } : {}) } : { prompt: text }),
     ...(repo ? { repo } : {}),
     ...(force ? { force: true } : {}),
     ...(by ? { by } : {}),
@@ -164,12 +169,14 @@ export function generalAgentRequest(prompt, { repo = null, force = false, by, de
 
 /**
  * What the CLI says about a general agent's answer: the task and that it started, or why it waits (and whether Force
- * start could skip that), or, from a decision, the open one that already has it.
+ * start could skip that), or, from a decision or for the next version (`next`), the open one that already has it.
  * @param {{ task: { wid?: string, short?: string }, run?: { url?: string, agent?: string } | null, waiting?: string | null, forceable?: boolean, already?: string | null }} answer
+ * @param {{ next?: string | null }} [options]
  */
-export function generalAgentSummary({ task, run, waiting, forceable, already }) {
+export function generalAgentSummary({ task, run, waiting, forceable, already }, { next = null } = {}) {
   const id = task.wid ?? task.short;
-  if (!run && already) return `${id} already refines from these answers: ${already}.`;
+  if (!run && already)
+    return `${id} already ${next ? 'prepares the next version' : 'refines from these answers'}: ${already}.`;
   if (run) return `Started ${run.agent ? `${run.agent} ` : 'an agent '}on ${id}${run.url ? `: ${run.url}` : ''}`;
   return `Saved ${id}, waiting to start: ${waiting ?? 'no room yet'}.${forceable ? ` Start it now past the board's limits: npx breakaway agents start ${id} --force` : ''}`;
 }

package/scripts/tasks.mjs

@@ -145,6 +145,7 @@ Reading                (list, next, claim, and add work in this checkout's repos
   agents                 cloud agents: what's running, what's waiting to start
   agents new "<prompt>"  start an agent from a prompt: it makes its own task  [--image <file>]… [--repo <slug>] [--force] (owner)
   agents new --decision <ref> ["<note>"]   start an agent that brings the work waiting for an answered decision in line with its answers; the board writes its prompt  [--force] (owner)
+  agents new --next minor|major ["<note>"]   start an agent that sets package.json to the next minor or major release; the board writes its prompt  [--repo <slug>] [--force] (owner)
   agents start <ref>     start a Claude cloud agent on a task  [--note <text>] [--force]
   agents refine <ref>    start an agent that improves a task, not builds it  --note <what to look at or change> [--force]
   agents plan [<plan>]   your Claude plan and what it allows; pro, max5, or max20 picks one (owner) and sets the limits to its defaults
@@ -230,6 +231,8 @@ Working
                          --pipeline <file.json|none> sets its deploy pipeline ({"workers": {"staging", "production"}, "workflows": {...}, "deployPaths"}) or clears it
   features add <slug>    new feature: its tasks join by carrying <slug> as a tag  [--title <text>]
                          [--brief <text> | --brief-file <path>] [--release <x.y.z>] (agents add one without a release)
+                         --from <ref> (owner): made from the group <ref> is in on the Dependencies view: its open tasks
+                         join, and tasks already in another feature stay there
   features modify <slug> change one (owner): --title, --brief, --brief-file, --release <x.y.z|none>, --state open|shipped
   routines add <slug>    new routine (owner)  --name <text> --prompt <text> | --prompt-file <path>  [--done-when <text>] [--horizon now|next|later] [--gap <minutes>] [--daily <n>]
                          [--repo <slug>] the repository it runs in (default: the checkout's)
@@ -780,10 +783,12 @@ const commands = {
     }
     if (sub === 'new') {
       const decision = typeof opts.decision === 'string' ? opts.decision : null;
+      const next = typeof opts.next === 'string' ? opts.next : null;
       const built = generalAgentRequest(args.slice(1).join(' '), {
         // From a decision, the board runs it in the decision's repository unless --repo says otherwise.
         repo: opts.repo ?? (decision ? null : (await checkoutRepo()).slug),
         decision,
+        next,
         force: Boolean(opts.force),
         by: opts.as ?? setting('AGENT'),
       });
@@ -796,7 +801,7 @@ const commands = {
         const image = await upload(ref(answer.task), file);
         if (!opts.json) console.log(`Attached ${image.name} (${Math.ceil(image.size / 1024)} KB).`);
       }
-      print(answer, generalAgentSummary);
+      print(answer, (d) => generalAgentSummary(d, { next }));
       return;
     }
     if (sub === 'start') {
@@ -1080,11 +1085,18 @@ const commands = {
     const by = opts.as ?? setting('AGENT');
     if (sub === 'add') {
       const slug = need(args[1], 'slug').toLowerCase();
-      const { feature } = await call('POST', 'features', { slug, ...body(), ...(by ? { by } : {}) });
-      print({ feature }, (d) =>
+      const from = opts.from === undefined ? {} : { from: opts.from };
+      const added = await call('POST', 'features', { slug, ...body(), ...from, ...(by ? { by } : {}) });
+      print(added, (d) =>
         [
           `Added the feature ${d.feature.slug}${d.feature.release ? `, aimed at ${d.feature.release}` : ''}: ${progressLine(d.feature.progress)}.`,
-          `Tasks join it by the tag: npx breakaway modify <ref> --tag ${d.feature.slug}`,
+          ...(d.joined
+            ? [
+                `Joined by its tag: ${d.joined.join(', ')}.`,
+                ...d.kept.map((k) => `${k.wid} stays in ${k.feature}: a task is in one feature.`),
+                `Chase it: npx breakaway chase ${d.feature.slug}`,
+              ]
+            : [`Tasks join it by the tag: npx breakaway modify <ref> --tag ${d.feature.slug}`]),
         ].join('\n'),
       );
       return;

package/src/cli-version.js

@@ -4,5 +4,5 @@
  * and how to update it. scripts/tasks/version.test.js fails when the copied files change and this doesn't:
  * so it lives in the board's package (CLD-135) and the CLI imports it from here.
  */
-export const CLI_VERSION = 58;
-export const CLI_FINGERPRINT = '602ca4bf1b6cfe8b';
+export const CLI_VERSION = 60;
+export const CLI_FINGERPRINT = 'faef5017c4405443';

package/src/decision.js

@@ -241,7 +241,7 @@ export function summarize(questions, answers) {
 }
 
 /** Tags that aren't a feature's (IDEA-28 section 1): the board's own, horizons, and release tags. */
-const NOT_FEATURES = new Set(['agent', 'owner', 'decide', 'idea', 'general']);
+const NOT_FEATURES = new Set(['agent', 'owner', 'decide', 'idea', 'general', 'version']);
 export const featureTags = (tags) =>
   (tags ?? []).filter((t) => !NOT_FEATURES.has(t) && !t.startsWith('horizon-') && !/^v\d/u.test(t));