cawdev-cli 1.0.10-beta → 1.1.0

package/mcp/server.mjs

@@ -375,6 +375,41 @@ const TOOLS = [
     },
   },
 
+  {
+    name: 'sprint_list',
+    description:
+      'The sprints a project\'s cards can be filed into, with how far each has got — R489. Sprints ' +
+      'are a team\'s: written `S7` inside the team and `Core team · S7` outside it. Read this before ' +
+      'filing a card into one with roadmap_create / roadmap_update `sprint`. State narrows it ' +
+      '(ACTIVE, UPCOMING, COMPLETED; comma-separated); the default is ACTIVE and UPCOMING.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        ...PROJECT_ARGUMENT,
+        state: {
+          type: 'string',
+          description: 'ACTIVE, UPCOMING, COMPLETED — one or several, comma-separated. Default ACTIVE,UPCOMING.',
+        },
+      },
+    },
+    handler: async (config, args) => {
+      const slug = await resolveProject(config, args.project);
+      const state = args.state || 'ACTIVE,UPCOMING';
+      const sprints = await api(config, `/api/projects/${slug}/sprints?state=${encodeURIComponent(state)}`);
+      if (!sprints.length) return `${slug} has no sprints in ${state}.`;
+      return sprints
+        .map((sprint) => {
+          const counts = sprint.counts ?? {};
+          return (
+            `${sprint.label ?? sprint.ref}${sprint.name ? ` ${sprint.name}` : ''} — ` +
+            `${String(sprint.state).toLowerCase()} — ${counts.landed ?? 0} of ${counts.cards ?? 0} landed` +
+            (sprint.goal ? `\n    goal: ${sprint.goal}` : '')
+          );
+        })
+        .join('\n');
+    },
+  },
+
   {
     name: 'roadmap_statuses',
     description:
@@ -396,18 +431,17 @@ const TOOLS = [
   {
     name: 'roadmap_list',
     description:
-      'A project\'s roadmap entries, optionally filtered by status or by sprint. Use brief=true ' +
-      'to survey without pulling every entry\'s body into context.',
+      'A project\'s roadmap cards, optionally filtered by status or by sprint. Use brief=true ' +
+      'to survey without pulling every card\'s body into context.',
     inputSchema: {
       type: 'object',
       properties: {
         ...PROJECT_ARGUMENT,
         sprint: {
-          type: 'integer',
-          minimum: 1,
+          type: ['integer', 'string'],
           description:
-            'Only cards in this sprint, by number — 1 for S1. A number the project has no ' +
-            'sprint for is refused naming the ones it has.',
+            'Only cards in this sprint: `S7` (or 7), "Core team · S7" when two teams have an S7, or a ' +
+            'sprint id. A sprint the project has none for is refused naming the ones it has.',
         },
         status: {
           type: 'string',
@@ -439,7 +473,9 @@ const TOOLS = [
       if (args.status) query.set('status', args.status);
       // R257. The API refuses a number with no sprint behind it, naming the
       // sprints there are; that sentence is passed through as the tool error.
-      if (args.sprint) query.set('sprint', String(args.sprint));
+      if (args.sprint !== undefined && args.sprint !== '' && args.sprint !== 0) {
+        query.set('sprint', String(args.sprint));
+      }
       if (args.assignee) query.set('assignee', args.assignee);
       query.set('brief', String(brief));
 
@@ -454,7 +490,7 @@ const TOOLS = [
   {
     name: 'roadmap_get',
     description:
-      'One roadmap entry in full: its body, THE PLAN somebody agreed for it, and the ' +
+      'One roadmap card in full: its body, THE PLAN somebody agreed for it, and the ' +
       'discussion on it. Read the plan before doing any of the work — it is what was decided, ' +
       'and it names the files. Read the comments before proposing anything: they are where an ' +
       'objection was answered, and re-proposing what was talked out three months ago is the ' +
@@ -594,7 +630,7 @@ const TOOLS = [
   {
     name: 'roadmap_comment',
     description:
-      'Say something about an entry, beside the entry rather than inside it. Use it for the ' +
+      'Say something about a card, beside the card rather than inside it. Use it for the ' +
       'argument: an objection, a measurement, why an obvious approach was not taken. The body ' +
       'is where a settled conclusion is written down — edit that when the discussion reaches ' +
       'one. Comments cannot be deleted, by you or by anyone.',
@@ -680,12 +716,13 @@ const TOOLS = [
   {
     name: 'roadmap_create',
     description:
-      'Create a roadmap entry. The platform allocates its permanent number — written R91 on ' +
-      'a roadmap card and i91 on an issue, one sequence across both — and the ' +
+      'Create a roadmap card. The platform allocates its permanent number — written R91 on ' +
+      'a roadmap card and i91 on an issue, two sequences, one per kind — and the ' +
       'project decides where a card you file starts — the BACKLOG by default for a card an ' +
       'agent files, waiting until a person or a sprint brings it in — unless you say ' +
       'otherwise; a status that requires something must be given it. A card in the BACKLOG ' +
-      'holds no sprint: giving it one moves it to CONSIDERING.',
+      'holds no sprint: giving it one moves it to CONSIDERING. A plan run\'s card lands ' +
+      'where the console\'s do (R380).',
     inputSchema: {
       type: 'object',
       properties: {
@@ -713,12 +750,12 @@ const TOOLS = [
         reason: { type: 'string' },
         section: { type: 'string', description: 'Which part of the roadmap, e.g. "Phase 2 — …".' },
         sprint: {
-          type: 'integer',
-          minimum: 0,
+          type: ['integer', 'string'],
           description:
-            'The sprint to file this card into, by number — 1 for S1. 0 takes it out of its ' +
-            'sprint; leave it out to leave it alone. A CLOSED sprint refuses a card that is ' +
-            'not already in it, and only a person can reopen one — do not retry.',
+            'The sprint to file this card into: `S7` (or 7) when the project\'s teams have one S7, ' +
+            '"Core team · S7" when two teams do, a sprint id, or 0 / "" to take it out of its sprint; ' +
+            'leave it out to leave it alone. A COMPLETED sprint refuses a card that is not already in it, ' +
+            'and only a person can reopen one — do not retry. Sprint_list shows what there is.',
         },
         related: {
           type: 'array',
@@ -866,6 +903,12 @@ const TOOLS = [
           description:
             'How much it matters; it does not reorder the board. Leave out for MEDIUM.',
         },
+        affectedVersions: {
+          type: 'array',
+          items: { type: 'string' },
+          description:
+            'Versions the project defined or shipped in where this issue was found — R378. Any other name is refused.',
+        },
       },
       required: ['title', 'severity'],
     },
@@ -873,7 +916,7 @@ const TOOLS = [
       const slug = await resolveProject(config, args.project);
       const issue = await api(config, `/api/projects/${slug}/issues`, {
         method: 'POST',
-        body: pick(args, ['title', 'body', 'severity', 'status', 'related', 'tags', 'assignee', 'priority']),
+        body: pick(args, ['title', 'body', 'severity', 'status', 'related', 'tags', 'assignee', 'priority', 'affectedVersions']),
       });
       return `Filed ${refOf(issue)} in ${slug}.\n\n${formatEntry(issue, {})}`;
     },
@@ -922,7 +965,7 @@ const TOOLS = [
   {
     name: 'roadmap_update',
     description:
-      'Edit an entry\'s title, body, section, sprint, tags, parent, related refs or the cards it ' +
+      'Edit a card\'s title, body, section, sprint, tags, parent, related refs or the cards it ' +
       'starts after. Use roadmap_set_status to move it.',
     inputSchema: {
       type: 'object',
@@ -936,12 +979,12 @@ const TOOLS = [
         body: { type: 'string' },
         section: { type: 'string' },
         sprint: {
-          type: 'integer',
-          minimum: 0,
+          type: ['integer', 'string'],
           description:
-            'The sprint to file this card into, by number — 1 for S1. 0 takes it out of its ' +
-            'sprint; leave it out to leave it alone. A CLOSED sprint refuses a card that is ' +
-            'not already in it, and only a person can reopen one — do not retry.',
+            'The sprint to file this card into: `S7` (or 7) when the project\'s teams have one S7, ' +
+            '"Core team · S7" when two teams do, a sprint id, or 0 / "" to take it out of its sprint; ' +
+            'leave it out to leave it alone. A COMPLETED sprint refuses a card that is not already in it, ' +
+            'and only a person can reopen one — do not retry. Sprint_list shows what there is.',
         },
         related: {
           type: 'array',
@@ -993,6 +1036,13 @@ const TOOLS = [
             'The card this one sits under (an epic), e.g. "R300". "" takes the card out of its ' +
             'parent; leave out to leave it alone. Same rules as roadmap_create.',
         },
+        affectedVersions: {
+          type: 'array',
+          items: { type: 'string' },
+          description:
+            'Issues only (R378): the versions the project defined or shipped in where it was found. ' +
+            'Leave out to leave them alone; [] clears them. A roadmap card refuses a non-empty list.',
+        },
       },
       required: ['number'],
     },
@@ -1003,7 +1053,7 @@ const TOOLS = [
         // pick keeps a present 0, which is how a card leaves its sprint.
         body: pick(args, [
           'title', 'body', 'section', 'related', 'after', 'sprint', 'tags', 'assignee', 'priority',
-          'due', 'estimate', 'targetVersion', 'parent',
+          'due', 'estimate', 'targetVersion', 'parent', 'affectedVersions',
         ]),
       });
       return `Updated ${refOf(entry)}.\n\n${formatEntry(entry, {})}`;
@@ -1013,7 +1063,7 @@ const TOOLS = [
   {
     name: 'roadmap_set_status',
     description:
-      'Move an entry to a status. Any status may move to any other — the rules are about what ' +
+      'Move a card to a status. Any status may move to any other — the rules are about what ' +
       'a status must carry, not a permitted path. IN_DEVELOPMENT needs a branch, MERGED the ' +
       'merge — the PR, the merge commit or the sha — and SHIPPED a version. Move a card to ' +
       'MERGED when its pull request lands; the branch may then be deleted. ' +
@@ -1062,7 +1112,7 @@ const TOOLS = [
   {
     name: 'roadmap_decline',
     description:
-      'Decline an entry, with a reason. This is the only exit an entry has — there is no delete. ' +
+      'Decline a card, with a reason. This is the only exit a card has — there is no delete. ' +
       'The reason is the point: it stops the idea being proposed again.',
     inputSchema: {
       type: 'object',
@@ -1139,10 +1189,10 @@ const TOOLS = [
         entryNumber: {
           type: ['string', 'integer'],
           description:
-            'The roadmap card or issue this entry describes — R156 — by ref: R91, i91, or a '
+            'The roadmap card or issue this changelog entry describes — R156 — by ref: R91, i91, or a '
             + 'bare number for a roadmap card (R221). Set it. Until R156 the only link was the '
             + 'ref you type into the prose, which cannot be queried, so a release could not '
-            + 'tell whether a card already had an entry and would write a second one beside '
+            + 'tell whether a card already had a changelog entry and would write a second one beside '
             + 'the first. Put the ref in the text as well; that is what a reader sees.',
         },
       },
@@ -1175,8 +1225,8 @@ const TOOLS = [
         entryNumber: {
           type: ['string', 'integer'],
           description:
-            'The roadmap card or issue this entry describes — R156 — by ref (R91, i91; a bare '
-            + 'number is a roadmap card). Set it on an older entry that has never been linked; '
+            'The roadmap card or issue this changelog entry describes — R156 — by ref (R91, i91; a bare '
+            + 'number is a roadmap card). Set it on an older changelog entry that has never been linked; '
             + 'omitting it leaves whatever link is already there.',
         },
       },
@@ -1197,9 +1247,9 @@ const TOOLS = [
   {
     name: 'task_current',
     description:
-      'What you are working on: the roadmap entry, THE PLAN agreed for it, its branch, and ' +
+      'What you are working on: the roadmap card, THE PLAN agreed for it, its branch, and ' +
       'everything already said and asked on this run. Call it first, and again whenever you ' +
-      'are unsure where you are — a resumed or confused session re-orients from this alone.',
+      'are unsure where you are — a resumed or confused agent session re-orients from this alone.',
     inputSchema: { type: 'object', properties: {} },
     handler: async (config) => {
       const { runId, project } = await requireRun(config);
@@ -1421,20 +1471,20 @@ const TOOLS = [
   {
     name: 'propose_entry',
     description:
-      'Record something an audit found, or a card a scoping session cut, as a proposed entry. ' +
+      'Record something an audit found, or a card a scoping run cut, as a proposed card. ' +
       '`kind` is your opinion: "issue" ' +
       '(broken, unsafe, or loses data — with a severity) or "roadmap" (it should also do this, ' +
       'or do it better — no severity). A PERSON decides, and may file it the other way — you ' +
-      'are not creating an entry, you are suggesting it. Default "issue", so an audit written ' +
+      'are not creating a card, you are suggesting it. Default "issue", so an audit written ' +
       'before there was a choice files what it always did. Severity is "critical" (broken, ' +
       'unsafe, or loses data), "medium" (it will hurt, but not today) or "minor" (worth doing, ' +
-      'nobody is bleeding). `section` is where you think it belongs; a scoping session names ' +
+      'nobody is bleeding). `section` is where you think it belongs; a scoping run names ' +
       'ONE for every card of the idea. A roadmap card MUST say what it starts after — `after`: ' +
       '`[]` for a card that starts after none, `"#2"` for the second card you proposed in this ' +
       'run (the number this tool answered with), `"R12"` for a card already on the roadmap. ' +
       'You can only name what has already been proposed, so file in build order. Write each ' +
-      'one as an entry would be written, and say where in the code you saw it. Only an audit ' +
-      'or a scoping session may use this.',
+      'one as a card would be written, and say where in the code you saw it. Only an audit ' +
+      'or a scoping run may use this.',
     inputSchema: {
       type: 'object',
       properties: {
@@ -1459,7 +1509,7 @@ const TOOLS = [
           type: 'string',
           description:
             'The roadmap section this belongs under, in your opinion. Optional. The person ' +
-            'accepting sees it as the default and may file it elsewhere. A scoping session ' +
+            'accepting sees it as the default and may file it elsewhere. A scoping run ' +
             'uses the same section on every card it cuts from one idea.',
         },
         after: {
@@ -1471,7 +1521,7 @@ const TOOLS = [
             'card you proposed in THIS run, by the number this tool answered with; it must ' +
             'already have been proposed, so propose what a card depends on before the card. ' +
             '`"R12"` or `"i7"` names a card already on the roadmap. A person adds the cards ' +
-            'in this order, and a coding session on one waits until what it starts after has ' +
+            'in this order, and a coding run on one waits until what it starts after has ' +
             'landed.',
         },
       },
@@ -1551,7 +1601,7 @@ const TOOLS = [
     name: 'ask_group',
     description:
       'Ask a ROUND of questions at once, and wait for all of them. Use it when you have several ' +
-      'things to settle that belong together — they arrive in the person\'s inbox under one ' +
+      'things to settle that belong together — they arrive in the person\'s Waiting on you page under one ' +
       'title, on one form, instead of interrupting them once per question. At most 12 in a ' +
       'round; ask the rest in the next one. Blocks for up to ten minutes; if the round is ' +
       'unfinished by then it returns a group_id for await_group.',
@@ -1561,7 +1611,7 @@ const TOOLS = [
         title: {
           type: 'string',
           description:
-            'What this round is called in their inbox. A CTO Interview uses "CTO Interview".',
+            'What this round is called in Waiting on you. A CTO Interview uses "CTO Interview".',
         },
         intro: {
           type: 'string',
@@ -1691,7 +1741,7 @@ const TOOLS = [
     name: 'await_answer',
     description:
       'Resume waiting for a question ask_user handed back. Between the two you experience one ' +
-      'natural blocking ask; the person experiences an inbox item.',
+      'natural blocking ask; the person experiences a Waiting on you item.',
     inputSchema: {
       type: 'object',
       properties: { question_id: { type: 'string' } },
@@ -2051,11 +2101,23 @@ function approvalTimeoutSeconds() {
 // The same goes for comments — nothing here removes one, and nothing there
 // does either.
 //
-// Nor is there a sprint_open, sprint_close or sprint_rename — R257. Opening,
-// closing and renaming a sprint are a person's acts on the page, and the API
-// says so structurally (POST/PATCH /sprints take a session, not a token). An
-// agent's whole reach here is reading a card's sprint and filing a card into
-// one with roadmap_create / roadmap_update `sprint`.
+// Nor is there a sprint_open, sprint_start, sprint_complete or sprint_rename —
+// R257, and a team's since R474. Opening, starting, completing and renaming a
+// sprint are a person's acts on the page, and the API says so structurally
+// (the /api/teams/{id}/sprints writes take a session, not a token). An
+// agent's whole reach here is reading the sprints (sprint_list) and a card's
+// sprint, and filing a card into one with roadmap_create / roadmap_update
+// `sprint`.
+
+/**
+ * R489. A card's sprint as a line: `Core team · S7 Name (active)`. The label
+ * is the server's one spelling; `S7` alone means nothing outside its team.
+ */
+function sprintLine(sprint) {
+  const label = sprint.label ?? sprint.ref ?? `S${sprint.number}`;
+  const state = String(sprint.state ?? '').toLowerCase();
+  return `${label}${sprint.name ? ` ${sprint.name}` : ''}${state ? ` (${state})` : ''}`;
+}
 
 function pick(source, keys) {
   const out = {};
@@ -2341,11 +2403,13 @@ function formatEntry(entry, { brief, comments, plan }) {
   if (entry.estimate) lines.push(`  estimate: ${entry.estimate}`);
   // R358. Printed until the card ships; `version` says where it did.
   if (entry.targetVersion && !entry.version) lines.push(`  target: ${entry.targetVersion}`);
+  // R378. History, not plan: still printed once the issue has shipped.
+  if (entry.affectedVersions?.length) lines.push(`  affects: ${entry.affectedVersions.join(', ')}`);
   // R257. Always printed when the card has one, so a reader's shape does not
   // depend on which tool printed the card; a closed sprint says so.
   if (entry.sprint) {
     lines.push(
-      `  sprint: ${entry.sprint.ref} ${entry.sprint.name}${entry.sprint.state === 'CLOSED' ? ' (closed)' : ''}`,
+      `  sprint: ${sprintLine(entry.sprint)}`,
     );
   }
   if (entry.related?.length) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cawdev-cli",
-  "version": "1.0.10-beta",
+  "version": "1.1.0",
   "description": "cawdev's terminal client and runner daemon — zero dependencies, on purpose",
   "type": "module",
   "bin": {

package/runner/README.md

@@ -158,8 +158,9 @@ served like any added project, and the rest of the console's setup walk —
 rules, members, the CTO Interview — is linked at
 `<url>/projects/<slug>/setup`.
 
-**What takes effect when** (R294). Three settings a running daemon takes
-without a restart — `agentCommands`, `grantable`, `acceptsRulesFromConsole`,
+**What takes effect when** (R294). Four settings a running daemon takes
+without a restart — `agentCommands`, `grantable`, `acceptsRulesFromConsole`
+and `autoWorkspaces`,
 the `HOT_SWAPPABLE` list in `tools/lib/runner-config.mjs`, spelled once —
 because the daemon reads them fresh on every use. Everything else in the file
 (`projects` and their workspaces, `url`, `name`, the token, `browser`, the
@@ -197,7 +198,7 @@ and its copy all work exactly as they always have, and scrolling up reaches the
 start of the session. The only thing pinned is the footer at the bottom, and it
 never scrolls away: which cawdev, who you are signed in as, this machine's
 runner, the per-project session counts against their checkouts and the machine's
-total against `maxSessions` — plus the run you are watching and the keys that
+total — plus the run you are watching and the keys that
 work right now. Anything *stopping* a session sits above all of that, because it
 is the only thing in there waiting on a person.
 
@@ -283,7 +284,7 @@ the shape of the decision, and the whole value of asking a person is that they
 can say the thing that was not on the list — so getting there costs one key, and
 `esc` from it comes back to the list rather than abandoning the answer. A chosen
 option and a typed sentence resolve the same question the same way, through the
-same endpoint the inbox and the run page post to: one record, the same
+same endpoint the Waiting on you page and the run page post to: one record, the same
 `answeredBy`, and the badge clears at once.
 
 A permission request is the same widget — R60's lengths of yes as rows, with the
@@ -469,7 +470,7 @@ this machine serves — unless the command names it with `@project`, or
 advanced mode is narrowed to ONE project (`/projects`), which is a choice
 already made rather than a guess. Never guessed from the focused window, nor
 from a machine serving just one, since a session on the wrong project is a
-card planned or a branch cut in the wrong repository. `/new dev` alone and `d` list the planned cards of every project,
+card planned or a branch cut in the wrong repository. `/new dev` alone and `d` list the planned cards and the confirmed issues of every project,
 each with its own, so they ask nothing more. A usage window over this machine's threshold is refused in a
 sentence; `--anyway` starts it regardless, the same decision the console's
 panel asks for. All four commands need you signed in (`/login`), and they work
@@ -575,7 +576,12 @@ serves as a small board — Considering, Planned and In development side by
 side, one line per card, `●` on a card with a session running now; Merged,
 Shipped and Declined — work that is over, and only grows — are counts beside
 the project's name (`1 merged · 2 shipped`), as the console's board folds its
-own last columns. As tall as the fullest column, never more than a
+own last columns. The Backlog is a count there too, first (`3 backlog`): since
+R371 it is where a new issue lands, and it would be the first column to go. **Issues are on it too** (R85's other board, read from
+`/issues` beside `/roadmap`): a NEW issue sits in Considering and a CONFIRMED
+one in Planned — their counterparts — first in the column and most severe first,
+so a `+N more` never hides a critical defect, with the ref (`i12`) in the colour
+of its severity. As tall as the fullest column, never more than a
 third of the screen, and gone before the windows are on a short terminal.
 When the room runs out it is SAID: a column ends in `+N more`, empty columns
 go first when the width does, then whole columns (Considering, then Planned —
@@ -689,7 +695,7 @@ it ends.
 A bare path means one workspace, which is what every config meant before this
 existed — nothing changes for a machine that serves one checkout per project.
 
-How many coding runs go at once is `min(workspaces, maxSessions)`. A run that
+How many coding runs go at once is the number of workspaces. A run that
 waits now says **"no free workspace in cawdev (2 here, all busy)"** instead of
 "that project already has a run here", which was a proxy for it.
 
@@ -712,18 +718,16 @@ says about knowing it.
 
 **This number caps coding and nothing else** (R70). `ASK`, `ROADMAP`, `AUDIT`
 and `SCOPE` runs take no workspace, so a project whose checkouts are all busy
-still starts a question, an entry-writing session, an audit and a scoping
-session at once. `INTERVIEW`, `MERGE`
+still starts a question, a card-writing run, an audit and a scoping
+run at once. `INTERVIEW`, `MERGE`
 and `RELEASE` do take one — each commits something — and count against this
 number; what each may *write* in it is far narrower than a coding run's and is
 decided by the profile, not by the prompt: an interview writes `docs/brief/`,
 a merge writes the files git put conflict markers in, and a release (R187)
 writes exactly the version files the platform names on the claim, with `git`,
 `gh pr create`, `gh pr view` and `node` for the exports — no build tools, no
-permission prompt, no `gh pr merge`. What holds the rest back
-is `maxSessions`, which counts every profile — **"at 4 sessions on this machine
-(every profile counts)"** is the other thing a waiting run can say, and the log
-always says which of the two it was.
+permission prompt, no `gh pr merge`. What holds a coding run back
+is a free workspace, and the log says so (R109 removed `maxSessions`).
 
 **One thing this gate cannot express, and does not try to.** It serialises on a
 checkout, so two runs on *the same branch* in two checkouts are, to this daemon,
@@ -792,8 +796,8 @@ whether the browser is allowed. Those five answer nearly every "why did that
 not happen", and they used to be spread across a config file and a shrug.
 
 Attaching adds a second bar row: the URL, each project as **coding sessions over
-checkouts** (`cawdev 1/2`), and the machine's total against `maxSessions`.
-Both gates, on screen, counting what each actually bounds — a question is in the
+checkouts** (`cawdev 1/2`), and the machine's total.
+The gate, on screen, counting what it actually bounds — a question is in the
 total on the right and not in any project's figure, because it took no checkout.
 A run that is waiting is explained by the bar
 above it rather than by reading the source. A narrow terminal drops projects
@@ -844,11 +848,11 @@ than twenty-six. A machine that wants it unattended puts that string in its own
 ### What a person can ask of a checkout
 
 R57. The daemon polls `workspace-requests/claim` every few seconds and does one
-of **ten** things to a checkout it serves. It said six for two entries, and
+of **eleven** things to a checkout it serves. It said six for two entries, and
 `HANDOFF` had been missing from the list since R148 — a table that quietly does
 not describe one of the things a person can ask for is worse than no table. So
 count the rows below against that number before you trust either. `CUT_BRANCH`
-is the ninth, R260's; `OPEN_PR` the tenth, R261's.
+is the ninth, R260's; `OPEN_PR` the tenth, R261's, `CREATE_BRANCH` the eleventh, R379's.
 
 | | |
 |---|---|
@@ -862,6 +866,7 @@ is the ninth, R260's; `OPEN_PR` the tenth, R261's.
 | `TAG` | R156's release: `git ls-remote --tags origin refs/tags/<version>` for the version in `message`. **The remote, not this clone** — a local tag nobody pushed is exactly the state a release is trying to rule out, and `git tag --list` cannot tell the two apart. A read; it fetches nothing and moves no ref. The sha is reported on the result's first line, the way `MERGE` reports its URL, because the platform will not confirm a release on `ok: true` alone. **A tag that is not there yet is `ok: false` with a sentence, and that is a normal answer** — the release procedure pushes the tag last, so the first check correctly finds nothing. Addressed to a **release** rather than to a directory alone, which is why it is asked for from the roadmap board and refused on this channel. |
 | `CUT_BRANCH` | R260's sprint branch: `git push origin origin/<default>:refs/heads/<name>` for the branch in `message`, after a fetch — so the sprint's cards are cut from what everyone else has, not from whatever this checkout was left on. The second kind after `MERGE` whose effect is **not** in the checkout: the push names two refs and this clone's HEAD is not one of them, so any live checkout of the project will do and nothing local moves. **A branch already on origin is `ok: true`** ("already on origin at <sha>") — the sprint wanted one to exist, and one does. The sha is reported on the result's first line, the way `TAG` reports its. Addressed to a **sprint** and asked for from the sprint page by an OWNER, for `MERGE`'s reason — it reaches the remote — and refused on this channel. A `MERGE` of a card's pull request into a sprint branch still runs `--squash --delete-branch`: the card's branch goes, the sprint's stays. Landing the sprint branch itself is `OPEN_PR` then `MERGE` below. |
 | `OPEN_PR` | R261's sprint merge, first half: `gh pr create --head <branch> --base <base> --title <title>` for the branch in `message` — the sprint's — to `baseBranch ?? defaultBranch`, titled as the claim's `title` (*S1 Notifications*). **An existing pull request is `ok: true` with its URL** — the same `gh pr view` lookup the `auto_pr` rule makes, and the reason the platform can ask this every time: it holds no git-host credential and cannot know whether one exists. The URL is reported on the result's first line, and the platform queues the `MERGE` to this same checkout when it reads one. Nothing is pushed: the branch is on origin already, cut there by `CUT_BRANCH` and merged into by every card. Addressed to a **work item** — the sprint's — and asked for by Merge on the development board or *Merge sprint* on the sprint page, by an OWNER; refused on this channel for `MERGE`'s reason. |
+| `CREATE_BRANCH` | R379's New branch from the console: pushes `origin/<fromBranch>` to `refs/heads/<name>` for the name in `message`. Unlike `CUT_BRANCH` a name already on origin is a **refusal**, because the person asked for a new branch and the existing one may be somebody else's work. Touches no working tree; a daemon that knows the kind says `createBranch: true` in its hello. |
 
 **A `MERGE` that fails also says which KIND of failure it was** — R155, in one
 of five words beside `gh`'s own unchanged text:
@@ -1252,12 +1257,9 @@ rest queue.
 
 **Questions are not serialised.** An `ASK` run prepares nothing and writes
 nothing, so it runs alongside whatever else is going on — you can ask about a
-project while an agent is working in it. `maxSessions` (4 by default) bounds how
-many agent processes this machine will host at once, and it is the **only**
-thing bounding a question, a roadmap session or an audit (R70). It counts runs
-this daemon has claimed, not children it has spawned: a claim takes a second or
-two to become a process, and counting processes let one pass of the loop claim
-the whole queue.
+project while an agent is working in it. Nothing bounds a question, a roadmap session or an audit but the platform's
+own queue: `maxSessions` was removed in R109, and the workspace gate above is
+the only one.
 
 ## If the daemon dies mid-run
 
@@ -1386,7 +1388,7 @@ permission stops forever.
 
 - `--permission-mode acceptEdits` lets it write files.
 - `--allowedTools mcp__cawdev__…` lets it use the cawdev tools. **Without this
-  the entire loop is unreachable** — no reading the task, no moving the entry,
+  the entire loop is unreachable** — no reading the task, no moving the card,
   no reporting, no asking. A real session found this by being denied
   `task_current` and stopping rather than guessing, which was the right call
   and a good sign for the prompt.
@@ -1412,7 +1414,7 @@ never asks you anything — an unlisted tool is refused, not raised (i138).
 
 **Anything else stops and asks you** (R51). Rather than being denied in
 silence, a session that needs `mvn` or `npm` posts a request that appears in
-your inbox and on the run, and waits for an answer. Allow it once, or allow it
+your Waiting on you page and on the run, and waits for an answer. Allow it once, or allow it
 always here — which writes a rule on the project that every runner serving it
 inherits.
 
@@ -1543,8 +1545,8 @@ after `--mcp-config` fails with `ENAMETOOLONG`, which names neither the flag nor
 the prompt.
 
 The prompt deliberately teaches the **method**, not the task. The task is in the
-roadmap entry, which the agent reads for itself with `task_current` — putting it
-in the prompt too would be a second copy that can disagree with the entry.
+roadmap card, which the agent reads for itself with `task_current` — putting it
+in the prompt too would be a second copy that can disagree with the card.
 
 ### Codex CLI
 

package/runner/attach.mjs

@@ -61,7 +61,7 @@ import { clip, keyList, padVisible, painter, stripAnsi, visibleWidth, wrap } fro
 import { restartNeededFor } from '../lib/runner-config.mjs';
 import {
   BOARD_COLUMNS, MIN_ZONE_HEIGHT, PROMPT_ROWS, SplitScreen, readerFrame, tabsLine, visibleSessions, actionsFor, composeFrame,
-  carriesOnHere, builtNothing, cardLines, cardTitleFor, commandWords, wordsText, subtitleFor, agentModelFor, wordWrap, isAutoCheckout, isPullRequest, parseNew, roadmapStrip, sessionTag, splitLayout, titleFor, toneFor,
+  carriesOnHere, builtNothing, cardLines, columnOf, cardTitleFor, commandWords, wordsText, subtitleFor, agentModelFor, wordWrap, isAutoCheckout, isPullRequest, parseNew, roadmapStrip, sessionTag, splitLayout, titleFor, toneFor,
   windowLines,
 } from './split.mjs';
 import { KNOWN_AGENTS, agentOfCommand } from '../lib/agents.mjs';
@@ -3413,9 +3413,10 @@ export class Attached {
   }
 
   /**
-   * Every card of every project this machine serves, whatever its status —
-   * the strip draws them all, and `d` offers the PLANNED ones. One request
-   * per project, the board's own (`brief`, so no bodies). Needs a person's
+   * Every card AND ISSUE of every project this machine serves, whatever its
+   * status — the strip draws them all, and `d` offers the PLANNED cards and
+   * the CONFIRMED issues. Two requests per project, the two boards' own
+   * (`brief`, so no bodies). Needs a person's
    * session, like everything read off the roadmap here.
    *
    * A project that cannot be read keeps ITS last cards and no other's: this
@@ -3435,6 +3436,15 @@ export class Attached {
         for (const card of Array.isArray(cards) ? cards : []) {
           all.push({ ref: card.ref, title: card.title, slug, status: card.status, live: Boolean(card.activeRun) });
         }
+        // The issues are another list on the platform (R85), and were never
+        // read here: the strip drew a project's ideas and not one of its bugs.
+        const issues = await this.session.request(`/api/projects/${slug}/issues?brief=true`);
+        for (const issue of Array.isArray(issues) ? issues : []) {
+          all.push({
+            ref: issue.ref, title: issue.title, slug, status: issue.status,
+            live: Boolean(issue.activeRun), severity: issue.severity ?? 'MINOR',
+          });
+        }
         read.push(slug);
         this.gone.delete(slug);
       } catch (failure) {
@@ -3447,7 +3457,8 @@ export class Attached {
       }
     }
     this.cards = all;
-    this.planned = all.filter((card) => card.status === 'PLANNED');
+    // Ready to be developed: a planned card, or a confirmed issue.
+    this.planned = all.filter((card) => columnOf(card.status) === 'PLANNED');
     this.dirty = true;
     if (!hold) this.sayGone();
     return { signedIn: true, read, failed };
@@ -3482,7 +3493,7 @@ export class Attached {
     const counts = read.filter((slug) => shown.has(slug)).map((slug) => {
       const mine = this.cards.filter((card) => card.slug === slug);
       const tally = BOARD_COLUMNS
-        .map(([status, label]) => `${mine.filter((card) => card.status === status).length} ${label.toLowerCase()}`)
+        .map(([status, label]) => `${mine.filter((card) => columnOf(card.status) === status).length} ${label.toLowerCase()}`)
         .join(' · ');
       return `${slug}: ${tally}`;
     });
@@ -3498,8 +3509,8 @@ export class Attached {
   }
 
   /**
-   * `d`, or `/new dev` with nothing after it: the planned cards as a list, and
-   * the one picked is developed — `/new dev R3 @slug`, on this machine.
+   * `d`, or `/new dev` with nothing after it: the planned cards — and the
+   * confirmed issues — as a list, and the one picked is developed — `/new dev R3 @slug`, on this machine.
    */
   async pickPlanned(slug = null) {
     if (!this.requireSignIn('start a session')) return;