@yemi33/minions 0.1.2392 → 0.1.2393

package/dashboard/js/qa.js

@@ -554,6 +554,8 @@ const QA_SESSION_TERMINAL_STATES = new Set(['done', 'failed', 'killed']);
 let _qaSessionsPollInterval = null;
 let _qaSessionsCache = [];
 let _qaRunnersCache = [];
+// Polling replaces the cards every three seconds, so disclosure state lives outside the DOM.
+const _qaExpandedFlows = new Set();
 
 function _stopQaSessionsPoll() {
   if (_qaSessionsPollInterval) {
@@ -706,6 +708,17 @@ function _qaAfterSessionsRender() {
   if (allTerminal) _stopQaSessionsPoll();
 }
 
+function qaSessionFlowsToggle(details) {
+  if (!details) return;
+  const isOpen = details.open;
+  const summary = details.querySelector('.qa-session-flows-summary');
+  if (summary) summary.setAttribute('aria-expanded', isOpen ? 'true' : 'false');
+  const id = details.getAttribute('data-session-id');
+  if (!id) return;
+  if (isOpen) _qaExpandedFlows.add(id);
+  else _qaExpandedFlows.delete(id);
+}
+
 function _qaRenderSessionCard(s) {
   const id = s && s.id || '';
   const state = (s && s.state) || 'unknown';
@@ -749,7 +762,19 @@ function _qaRenderSessionCard(s) {
 
   let body = '';
   if (flowsShort) {
-    body += '<div class="qa-session-flows"><strong>Flows:</strong> ' + escHtml(flowsShort) + '</div>';
+    const flowsOpen = _qaExpandedFlows.has(id);
+    body += '<details class="qa-session-flows"' + (flowsOpen ? ' open' : '') +
+      ' data-session-id="' + escHtml(id) + '" ontoggle="qaSessionFlowsToggle(this)">' +
+        '<summary class="qa-session-flows-summary" aria-expanded="' + (flowsOpen ? 'true' : 'false') + '">' +
+          '<strong class="qa-session-flows-label">Flows:</strong>' +
+          '<span class="qa-session-flows-preview">' + escHtml(flowsShort) + '</span>' +
+          '<span class="qa-session-flows-affordance">' +
+            '<span class="qa-session-flows-expand-label">Show full prompt</span>' +
+            '<span class="qa-session-flows-collapse-label">Hide full prompt</span>' +
+          '</span>' +
+        '</summary>' +
+        '<div class="qa-session-flows-full">' + escHtml(flowsRaw) + '</div>' +
+      '</details>';
   }
   if (state === 'failed' && (failureClass || error)) {
     body += '<div class="qa-session-error"><strong>' + escHtml(failureClass || 'failed') + ':</strong> ' + escHtml(error || summary || 'no details') + '</div>';

package/dashboard/styles.css

@@ -1597,6 +1597,31 @@
     background: var(--surface); padding: var(--space-3);
     border-radius: var(--radius-sm); border: 1px solid var(--border);
   }
+  .qa-session-flows-summary {
+    display: grid; grid-template-columns: auto minmax(0, 1fr) auto;
+    align-items: start; gap: var(--space-2); cursor: pointer; list-style: none;
+  }
+  .qa-session-flows-summary::-webkit-details-marker { display: none; }
+  .qa-session-flows-summary::marker { content: ''; }
+  .qa-session-flows-summary:focus-visible {
+    outline: 2px solid var(--blue); outline-offset: 3px;
+    border-radius: var(--radius-sm);
+  }
+  .qa-session-flows-preview,
+  .qa-session-flows-full { overflow-wrap: anywhere; }
+  .qa-session-flows-affordance {
+    color: var(--blue); font-size: var(--text-xs); white-space: nowrap;
+  }
+  .qa-session-flows-affordance::before { content: '+ '; }
+  .qa-session-flows-collapse-label { display: none; }
+  .qa-session-flows[open] .qa-session-flows-preview { display: none; }
+  .qa-session-flows[open] .qa-session-flows-affordance::before { content: '- '; }
+  .qa-session-flows[open] .qa-session-flows-expand-label { display: none; }
+  .qa-session-flows[open] .qa-session-flows-collapse-label { display: inline; }
+  .qa-session-flows-full {
+    margin-top: var(--space-3); padding-top: var(--space-3);
+    border-top: 1px solid var(--border); white-space: pre-wrap;
+  }
   .qa-session-error {
     font-size: var(--text-base); color: var(--red);
     background: rgba(248, 81, 73, 0.08); padding: var(--space-3);

package/docs/pr-auto-fix-dispatch.md

@@ -51,7 +51,7 @@ Independent of the master kill-switches, each PR tracks repeated no-op fix outco
 2. Click the red chip → `POST /api/pull-requests/clear-paused-cause` with `{ prId, cause }`.
 3. Direct API call to the same endpoint.
 
-This per-PR per-cause pause is unrelated to `autoFixPaused`. Cause keys are validated against `shared.PR_FIX_CAUSE` (e.g. `BUILD_FAILURE`, `REVIEW_FEEDBACK`, `HUMAN_FEEDBACK`, `MERGE_CONFLICT`, `PR_FIX`). Full mechanics in [`docs/pr-review-fix-loop.md`](pr-review-fix-loop.md) §4E.
+This per-PR per-cause pause is unrelated to `autoFixPaused`. Cause values are validated against `Object.values(shared.PR_FIX_CAUSE)` (`human-feedback`, `review-feedback`, `build-failure`, `merge-conflict`, or `pr-fix`). Full mechanics in [`docs/pr-review-fix-loop.md`](pr-review-fix-loop.md) §4E.
 
 ## Key files
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.2392",
+  "version": "0.1.2393",
   "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
   "bin": {
     "minions": "bin/minions.js"

package/playbooks/plan-to-prd.md

@@ -135,7 +135,7 @@ Rules for items:
       { "id": "P-bbb2", "name": "UI client",    "project": "web-dashboard",   ... }
     ]
     ```
-    The engine routes each item to that project's SQL work-item scope. The verify task at plan completion picks the project with the most completed items and runs cross-repo verification from there. See the **Cross-repo plans** section below for the full output contract when `{{target_projects}}` is set.
+    The engine routes each item to that project's SQL work-item scope. At plan completion, the engine creates one project-scoped verify work item per touched project (each project with an active PR linked to a completed plan item). If no linked PRs surface, it falls back to one verify work item on the primary project. See the **Cross-repo plans** section below for the full output contract when `{{target_projects}}` is set.
 - `depends_on` lists IDs of items that must be done first
 - Keep descriptions actionable — name the files, functions, patterns, or integration points the implementing agent should touch whenever the plan makes them clear
 - Include `acceptance_criteria` so reviewers know when it's done
@@ -161,7 +161,7 @@ Apply these rules on top of (and where they conflict, instead of) the single-pro
    - `parallel`: omit `feature_branch` entirely (the engine derives per-item branches as `user/<loginname>/<wi-id>-<slug>` in each project).
    - `shared-branch` (only with explicit justification): use the canonical `user/<loginname>/PL-<short-kebab-slug>` form. The engine will pre-create a matching branch in every project listed in `{{target_projects}}` (P-1c0f5e84) so each item can push to the same branch name in its own repo.
 
-The verify task at plan completion picks the project with the most completed items and runs cross-repo verification from there; items with no PRs (e.g. docs-only changes that landed via direct commit) are still counted via their `done` status.
+At plan completion, the engine creates one verify work item per touched project, where a touched project has at least one active PR linked to a completed plan item. Those project-scoped verify tasks run independently in parallel. If no linked PRs surface (for example, items completed without PR records or legacy state), the fan-out collapses to one verify work item on the primary project — the project with the most completed items — as a fallback.
 
 {{/target_projects}}
 ## Reusing an Existing PRD