@ctrl-spc/cs 0.7.3 → 0.7.5

package/dist/panel3/prompt.js

@@ -130,6 +130,7 @@
  * how to write it travels with `write_report`'s own description, where ux.md
  * says the how belongs.
  */
+import { FIREWALL_WRITING_RULE } from '../firewall.js';
 /**
  * ═══ WHAT EVERY LEVEL IS TOLD ABOUT THE THING IT SENDS BACK. ═══
  *
@@ -429,9 +430,12 @@ const projectCodebases = (codebases) => {
  * — which matters because the daemon writes it to `panel3_runs.brief`.
  *
  * ═══ `cardTitle` IS A NAME, NOT THE QUESTION, AND ITS LABEL SAYS SO. ═══ `say`
- * fixes it once, as the truncated first line of the FIRST message, and never
- * changes it. Labelled as what is being asked, a second turn would tell the
- * agent the current question is a stale half-sentence and then hand it the real
+ * writes it as the truncated first line of the FIRST message, and the launcher
+ * may replace it once, with `dispatch`'s `work_name`, so that it names the work
+ * rather than that sentence. Either way it names the CONVERSATION and not what
+ * is currently being asked: it is written before the first answer and nothing
+ * touches it after. Labelled as what is being asked, a second turn would tell
+ * the agent the current question is the opening line and then hand it the real
  * ones underneath — so the label names the conversation, which is all the title
  * has ever been.
  *
@@ -494,6 +498,18 @@ export function levelOnePrompt(cardTitle, messages, produced, attachments = [],
         '',
         'WHAT THIS CONVERSATION IS CALLED',
         cardTitle,
+        /* ═══ THE ONE MOMENT ANYTHING CAN NAME THE WORK. ═══ Until the owner is
+           sent, this is the truncated first line of the person's first message, and
+           sending the owner cuts the branch for the work from it and stamps that
+           branch for good. The launcher is the only thing that runs in between, and
+           it has the messages in front of it, so it is the only thing that can say
+           what the work is before both are fixed. */
+        'This is the first line of what they typed, so it names their sentence rather than the work. If',
+        'the person pointed this conversation at a work item, that item is already its name and there is',
+        'nothing to do. Otherwise pass `work_name` to `dispatch`: a few words, six at most, naming the',
+        'work itself, such as "Fix the sign-out checklist bug". The conversation is called that from',
+        'then on, and the branch the work goes on is cut from it, both as you send the owner. This is',
+        'the only moment either can be named.',
         '',
         'WHAT HAS ALREADY BEEN MADE HERE',
         'Everything this conversation has produced so far, whatever it was that made it, with the id to',
@@ -648,6 +664,22 @@ export function workBrief(level, responsibility, boundary, workItemId, attachmen
                         'first stage only, and do not start the next stage until the one before it has come',
                         'back. When you send somebody for a stage, put that stage\'s own document into what you',
                         'give them, in full: they cannot read the workflow themselves.',
+                        /* ═══ 38-panel3-steps: THE STAGES LAND ON THE WORK ITEM, WHERE THE
+                           PERSON WATCHES. ═══ Without these sentences a panel run follows a
+                           workflow and the work item's Steps section stays empty: nothing
+                           starts the workflow on the item and nothing writes a step. The
+                           owner starts it once, hands each worker the work item, and reads
+                           the record before sending the next stage, because "the stage is
+                           finished" is what `up_next` moving on means and nothing else
+                           enforces the order. */
+                        'Before you send anybody for the first stage, call `start_workflow` with the workflow and',
+                        'the work item, once: it puts the stages on the work item, where the person watches. Pass',
+                        '`work_item_id` when you send somebody for a stage. When somebody comes back, call',
+                        '`list_steps` before you send the next stage. If `up_next` still names the stage you sent',
+                        'them for, that stage is not finished: send somebody back for what is left, or ask the',
+                        'person. Send the next stage only when `up_next` has moved on. A stage you work yourself',
+                        'gets the same record: `list_steps`, then `create_step` for each unit of work, then',
+                        '`update_step` as you go.',
                     ]
                     : []),
                 'What you have already sent somebody to do is written down, and you are handed that list',
@@ -669,6 +701,25 @@ export function workBrief(level, responsibility, boundary, workItemId, attachmen
                 '',
                 'Somebody else may be working in this same copy of the codebase at the same time as you, on',
                 'a different piece. Stay inside what you were given and leave the rest of it alone.',
+                /* ═══ 38-panel3-steps: A WORKER'S STAGE IS WRITTEN DOWN AS STEPS. ═══
+                   Printed only when a workflow is on the card, like the owner's clause
+                   above. The wording is the one v2's `start_workflow` reminder already
+                   uses, which a walked agent follows: decompose before working, tick as
+                   you go, only done moves the record on. It names no sequencing rule,
+                   because a worker sends nobody. */
+                ...(hasWorkflow
+                    ? [
+                        '',
+                        'THIS WORK FOLLOWS A WORKFLOW, AND ITS STEPS ARE WRITTEN DOWN WHERE THE PERSON WATCHES.',
+                        'Your stage is the first unfinished one on the work item: call `list_steps` with the work',
+                        'item id and read `up_next`. Before you do the stage\'s work, record its steps with',
+                        '`create_step`, one per unit of work, in order. Then `update_step` each to `in_progress`',
+                        'when you pick it up and `done` when it is finished; only done lets the next one start. If',
+                        'you cannot go on without an answer, `update_step` the step you are on to `blocked` with a',
+                        '`next_action` saying what you need, then `escalate`, then stop. Never create a second step',
+                        'to report on the first.',
+                    ]
+                    : []),
             ]),
         '',
         'WHAT YOU OWN',
@@ -727,6 +778,9 @@ export function workBrief(level, responsibility, boundary, workItemId, attachmen
         'not what you were halfway through. Notes written at the end of the work are notes that were',
         'never written.',
         '',
+        'ANYTHING YOU SAVE GOES THROUGH A FIREWALL',
+        FIREWALL_WRITING_RULE,
+        '',
         ...WHILE_YOU_ARE_WORKING,
         '',
         ...(level === 2