valent-pipeline 0.1.8 → 0.1.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "valent-pipeline",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "v3 multi-agent AI pipeline for software development lifecycle",
   "type": "module",
   "bin": {

package/pipeline/prompts/lead.md

@@ -451,12 +451,16 @@ Tear down all per-story teammates. Send `shutdown_request` to each individually.
 - Update `pipeline-state.json`
 - **Update `{backlog_path}`:**
   1. Set the current item's `status` to `shipped` and add `shipped_at` date
-  2. If JUDGE G2 issued a conditional ship with bugs, add each bug as a new `bug` type entry in the backlog with:
+  2. If JUDGE G2 issued a conditional ship with bugs (P2-P3), add each bug as a new `bug` type entry in the backlog with:
      - `status: pending`
      - `priority`: one above the next pending story (bugs get worked before new stories by default)
      - `severity`, `source_story`, `affects`, `description`, `file_ref` from the G2 decision and QA-B bug report
-  3. Add the bug IDs to the shipped story's `conditional_bugs` list
-  4. For any pending stories whose `blocked_by_bugs` referenced bugs that are now `shipped`, those blockers are resolved — the story becomes unblocked if all other dependencies are also met
+  3. Add P4 bugs from `{story_output_dir}/bugs.md` to the backlog at the **lowest priority** (highest priority number). These are worked only when no other stories or bugs are unblocked — the pipeline always has something to do.
+     - `status: pending`
+     - `priority`: max existing priority + 1 (per bug, incrementing)
+     - `severity: P4`, `source_story`, `description`, `file_ref` from QA-B bug report
+  4. Add the conditional bug IDs (P2-P3) to the shipped story's `conditional_bugs` list. P4 bugs are not conditional — they don't block anything.
+  5. For any pending stories whose `blocked_by_bugs` referenced bugs that are now `shipped`, those blockers are resolved — the story becomes unblocked if all other dependencies are also met
 
 ### Step 5b: Write Epic Progress Checkpoint
 

package/skills/valent-run-project/SKILL.md

@@ -120,7 +120,7 @@ After the story ships (or is cancelled/blocked), update `{epic_progress_path}`:
 - Move the story from `stories_remaining` to `stories_completed`
 - Add a compact outcome line: `{STORY-ID} ({epic}): SHIPPED {date}. {one-line summary}. {test counts}. {bug count}.`
 - Update `total_completed`, `stories_since_retro`, `last_updated`
-- **Keep the file under 80 lines total** (larger than epic runs since it covers all epics)
+- **FIFO at 80 lines:** When the outcomes section exceeds 80 lines, remove the oldest outcome at the top to make room for the new one at the bottom. Recent context is most valuable after compression; older outcomes live in individual story reports.
 
 #### 4h. Update Backlog
 
@@ -203,7 +203,7 @@ If the loop finds no unblocked stories but pending stories remain:
 - You are the Lead for each story. The lead prompt (`.valent-pipeline/prompts/lead.md`) is YOUR operating manual.
 - **Do NOT read agent output files.** Quality is JUDGE gates' and CRITIC's job.
 - **Always read from disk, never from memory** at the top of each loop iteration.
-- **Progress file is the crash recovery substrate.** Keep it under 80 lines.
+- **Progress file is the crash recovery substrate.** FIFO queue — cap outcomes at 80 lines, evict oldest.
 - **Retrospectives run BLOCKING.**
 - **Shutdown must be sent individually, not broadcast.**
 - Correction directives may not exist yet for new pipelines — proceed without them.