quadwork 1.2.5 → 1.4.0

package/templates/CLAUDE.md

@@ -44,6 +44,7 @@ Branch naming (strict): `task/<issue-number>-<short-slug>`
 - **Existing patterns first**: check project's existing code before creating new abstractions
 - Read files before modifying; never code from assumptions
 - Minimal changes only — no "while I'm here" improvements
+- If the project adds visual regression automation, keep it **manual only** and trigger it only for likely UI-impacting edits.
 
 ## Security
 

package/templates/OVERNIGHT-QUEUE.md

@@ -10,7 +10,7 @@
 
 ## Active Batch
 
-(no active batch yet — operator will assign one via chat)
+(no active batch yet — operator will assign one via chat. Head will use batch number 1 for the first batch.)
 
 ---
 

package/templates/seeds/head.AGENTS.md

@@ -57,9 +57,28 @@ This is an **absolute path** — read it with the full path, never a relative on
 When the operator asks you in chat to start a task or batch:
 1. Create the GitHub issue(s) if they don't already exist (`gh issue create` with scope, acceptance, and `agent/*` labels).
 2. Append the task(s) under the **Backlog** section of `OVERNIGHT-QUEUE.md`, or move them into **Active Batch** if the operator says they're ready to run.
+
+   **Batch numbering.** Each new batch you put into Active Batch gets the next sequential number. Read every `**Batch:** N` line in the file (Active Batch + Done) and use `max(N) + 1`. If no batches exist yet, start at `1`. Stamp the Active Batch section with:
+
+   ```markdown
+   ## Active Batch
+
+   **Batch:** <N>
+   **Started:** <YYYY-MM-DD HH:MM>
+   **Status:** pending kickoff
+
+   (items...)
+   ```
+
+   When you move a batch to Done, **preserve its `Batch: N` line** so the next batch's number computation stays correct.
 3. Reply in chat to confirm what you wrote to the queue file (issue numbers + which section).
-4. **Wait for the operator to trigger the batch via the Scheduled Trigger widget** before assigning the first item to `@dev`. Do NOT start assignments the moment the queue file is written — the operator controls kickoff.
-5. Once triggered, assign the first item to `@dev` following the normal workflow below.
+4. **Tell the operator the queue is ready and how to kick it off.** Send a chat message like:
+
+   > Queue is ready. To begin, click **Send Message and Start Trigger** in the Operator Features panel (bottom-right). I will start assigning Dev as soon as the trigger fires.
+
+   Without this prompt the operator has no idea what to do next and the batch sits idle indefinitely. Always send it after step 3, even if the operator only asked for a single ticket.
+5. **Wait for the operator to trigger the batch via the Scheduled Trigger widget** before assigning the first item to `@dev`. Do NOT start assignments the moment the queue file is written — the operator controls kickoff. The trigger fires the queue-check pulse to all agents and is your signal that the operator wants the batch to start.
+6. Once triggered, assign the first item to `@dev` following the normal workflow below.
 
 ### After each merge
 1. Move the merged item from **Active Batch** to **Done** in `OVERNIGHT-QUEUE.md`.