breakaway 1.2.1-main.22 → 1.2.1-main.24

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "breakaway",
-  "version": "1.2.1-main.22",
+  "version": "1.2.1-main.24",
   "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/core.md

@@ -100,7 +100,7 @@ The owner wrote what they want in their own words and pressed Start; the board m
    - *Something you can't do* (production, a secret, a choice only the owner can make): ask the decision or ping (below), then `release`.
 
    A general task released with no pull request is finished: the board closes it, so release only when your part is done.
-4. **Other tasks: change them directly, each change noted.** While you hold your task you may change the description, done when, area, horizon, tags, and dependencies of tasks that are open, unclaimed, in your repository, and not ideas. On each task you change, `comment` `Changed by <your task>: <the fields>`, so the owner sees it in Activity and can undo it. Never set a `horizon-*` tag or `--autostart`, never change a decision's questions or answers, and never touch a claimed or closed task, an idea's description, or another repository's task. If the board refuses an edit, or one falls outside these limits, put it in a ping's proposal for the owner instead.
+4. **Other tasks: change them directly, each change noted.** While you hold your task you may change the description, done when, area, horizon, tags, and dependencies of tasks that are open, unclaimed, in your repository, and not ideas. The board adds `Changed by <your task>: <the fields>.` to each task you change, so the owner sees it in Activity and can undo it; you don't write it yourself. Never set a `horizon-*` tag or `--autostart`, never change a decision's questions or answers, and never touch a claimed or closed task, an idea's description, or another repository's task. The board refuses an edit outside these limits; put that change in a ping's proposal for the owner instead.
 5. **A run from a decision's answers.** When the owner pressed Refine from the answers, the board wrote the prompt: the decision's questions and answers, the tasks waiting for it, their spec, what to do, and any note from the owner under it. Your task is related to the decision; `show` it for the full answers. Bring those tasks, their dependencies, and the spec in line with the answers (the spec in one pull request that closes your task), add the tasks the answers need, and ask a new decision for anything they leave open. Never change the answers: only the owner does.
 
 You never start or force-start an agent, never take another agent's claim, and never deploy, touch production, or merge, whatever the prompt says.

package/scripts/tasks.mjs

@@ -1282,6 +1282,8 @@ const commands = {
   async modify() {
     const changes = changesFrom(opts);
     if (!Object.keys(changes).length) fail('nothing to change; see npx breakaway --help');
+    // Who changes it, whichever field: a general agent's edits of other tasks follow their own rule (IDEA-30 section 2).
+    changes.by = agent();
     const { task } = await call('PATCH', `tasks/${enc(need(args[0], 'task'))}`, changes);
     print(task, (t) => `Changed ${ref(t)}.\n\n${detail(t)}`);
   },

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 = 56;
-export const CLI_FINGERPRINT = 'a93ad49eb3829517';
+export const CLI_VERSION = 57;
+export const CLI_FINGERPRINT = '4a919c03b0166011';