mandrel 2.36.0 → 2.38.0

package/.agents/scripts/lib/feedback-loop/graduator-core.js

@@ -60,7 +60,7 @@ import { upsertStructuredComment } from '../orchestration/ticketing.js';
  * finalize indefinitely; the walk now caps every spawn at this bound unless
  * a caller overrides it.
  */
-export const DEFAULT_RUN_CHILD_TIMEOUT_MS = 30000;
+const DEFAULT_RUN_CHILD_TIMEOUT_MS = 30000;
 
 /**
  * Default per-run filing cap. `graduate()` files at most this many follow-up
@@ -72,7 +72,7 @@ export const DEFAULT_MAX_FILINGS_PER_RUN = 20;
  * Structured-comment type used to durably persist cross-repo-deferred
  * findings on the Epic. Registered in `STRUCTURED_COMMENT_TYPES`.
  */
-export const CROSS_REPO_DEFERRED_COMMENT_TYPE = 'cross-repo-deferred';
+const CROSS_REPO_DEFERRED_COMMENT_TYPE = 'cross-repo-deferred';
 
 /**
  * Explicit, greppable opt-back-in to live issue filing from a context the

package/.agents/scripts/lib/feedback-loop/prior-feedback-fetcher.js

@@ -1,6 +1,6 @@
 /**
  * prior-feedback-fetcher.js — gh-CLI-backed fetcher for open meta feedback
- * issues that feed the `/plan` Phase 0 planner context.
+ * issues that feed the `/mandrel-plan` Phase 0 planner context.
  *
  * Story #2554 / Epic #2547. Tech Spec #2550 specifies that the fetcher MUST
  * return open issues carrying the `meta::framework-gap` and
@@ -17,8 +17,8 @@
  * `recurringDefectClasses[]` array derived from the `friction::<class>`
  * labels the retro routed-proposals composer stamps onto the meta issues it
  * proposes. That closes the retro→planner loop: a recurring defect class
- * caught by review/deliver is filed as a `meta::*` + `friction::<class>`
- * issue, and the next `/plan` Phase 0 surfaces the class (with a recurrence
+ * caught by review/mandrel-deliver is filed as a `meta::*` + `friction::<class>`
+ * issue, and the next `/mandrel-plan` Phase 0 surfaces the class (with a recurrence
  * count across the open feedback issues) to the decompose-author guidance so
  * the planning floor ratchets up. The derivation is no-op-safe: issues with
  * no `friction::*` label contribute nothing and the array is empty.
@@ -52,7 +52,7 @@ const FRICTION_LABEL_PREFIX = 'friction::';
  * @param {Array<{ number: number, labels?: string[] }>} issues
  * @returns {Array<{ class: string, count: number, issues: number[] }>}
  */
-export function extractRecurringDefectClasses(issues) {
+function extractRecurringDefectClasses(issues) {
   if (!Array.isArray(issues)) return [];
   /** @type {Map<string, Set<number>>} */
   const byClass = new Map();
@@ -297,7 +297,7 @@ export async function fetchPriorFeedback({
 
   // Story #4135 (Epic #4131, F11) — close the retro→planner loop: derive the
   // recurring defect classes from the `friction::<class>` labels carried by
-  // the deduped feedback issues, so the next /plan Phase 0 surfaces them to
+  // the deduped feedback issues, so the next /mandrel-plan Phase 0 surfaces them to
   // the decompose-author guidance. No-op-safe when no issue carries a
   // `friction::*` label (empty array, no behavioural change).
   envelope.recurringDefectClasses = extractRecurringDefectClasses([

package/.agents/scripts/lib/feedback-loop/retro-proposals-graduator.js

@@ -6,7 +6,7 @@
  * (`retro-proposals.js`) already split the Epic's source-tagged friction
  * into `framework` / `consumer` actionable items, each carrying a
  * pre-drafted `gh issue create` command stanza. Historically an operator
- * had to copy-paste those stanzas by hand, so `/plan` Phase 0's
+ * had to copy-paste those stanzas by hand, so `/mandrel-plan` Phase 0's
  * `recurringDefectClasses` stayed empty unless someone remembered to run
  * the commands. This module files them mechanically instead — the retro
  * body then lists the real filed issue numbers rather than paste-ready
@@ -387,7 +387,7 @@ export function enrichRoutedProposalsWithFilings(routedProposals, filed) {
  * @param {string|null|undefined} slug
  * @returns {{ owner: string, repo: string } | null}
  */
-export function parseRepoSlug(slug) {
+function parseRepoSlug(slug) {
   if (typeof slug !== 'string') return null;
   const parts = slug.split('/');
   if (parts.length !== 2) return null;

package/.agents/scripts/lib/findings/classify-finding.js

@@ -51,7 +51,7 @@ export const FINDING_CLASSES = Object.freeze([
 /**
  * Class → label-set routing table. Each class maps to exactly one label set.
  * `tooling-dx` is the framework-gap path: it carries `meta::framework-gap` so
- * the `/plan` Phase 0 feedback fetcher surfaces it to the planner.
+ * the `/mandrel-plan` Phase 0 feedback fetcher surfaces it to the planner.
  */
 const CLASS_TO_LABELS = Object.freeze({
   'product-bug': [FOCUS_LABELS.PRODUCT],

package/.agents/scripts/lib/findings/promote-finding.js

@@ -5,8 +5,8 @@
  * tail of the exploratory-QA Triage path: once an operator has dispositioned a
  * session's ledger items (see `.agents/schemas/qa-ledger.schema.json` and
  * `lib/qa/qa-session.js`), the still-untriaged backlog is clustered and each
- * cluster is promoted to a follow-up ticket — a single Story (via `/plan`)
- * for a tight, one-deliverable cluster, or a multi-Story plan-seed (via `/plan --seed`) for
+ * cluster is promoted to a follow-up ticket — a single Story (via `/mandrel-plan`)
+ * for a tight, one-deliverable cluster, or a multi-Story plan-seed (via `/mandrel-plan --seed`) for
  * a broad cluster that spans multiple coverage surfaces. Each contributing
  * ledger item then has the resulting `routedTo` issue link written back onto it
  * so a resume run sees the item as filed rather than re-promoting it.
@@ -23,7 +23,7 @@
  * Pure orchestration: **no network I/O lives here.** Every GitHub side-effect
  * (issue search, ticket creation) flows through INJECTED PORTS so the unit test
  * runs with no network. Production wires the ports to the GitHub provider /
- * `/plan` / `/plan` surfaces; tests pass in-memory stubs.
+ * `/mandrel-plan` / `/mandrel-plan` surfaces; tests pass in-memory stubs.
  */
 
 import { fingerprintFinding, routeFinding } from './route-finding.js';
@@ -35,8 +35,8 @@ const TRIAGED_DISPOSITIONS = Object.freeze(['file', 'defer', 'dismiss']);
 /**
  * The two promotion targets a cluster routes to.
  *
- * `PLAN_SEED` promotes a broad cluster by seeding a multi-Story `/plan`
- * run (`/plan --seed`). Its persisted wire token is the legacy string
+ * `PLAN_SEED` promotes a broad cluster by seeding a multi-Story `/mandrel-plan`
+ * run (`/mandrel-plan --seed`). Its persisted wire token is the legacy string
  * `'epic'`: archived qa-ledger records (and the distributed
  * `qa-ledger.schema.json` `routedTo.kind` enum) still carry `'epic'`, so
  * the value is kept read-compatible while the write-side constant name is
@@ -49,8 +49,8 @@ export const PROMOTION_TARGETS = Object.freeze({
 
 /**
  * A cluster of more than this many distinct coverage surfaces is broad enough
- * to warrant a plan-seed (`/plan --seed`) rather than a single Story
- * (`/plan`). One or two surfaces is a tight, single-deliverable cluster.
+ * to warrant a plan-seed (`/mandrel-plan --seed`) rather than a single Story
+ * (`/mandrel-plan`). One or two surfaces is a tight, single-deliverable cluster.
  */
 const EPIC_COVERAGE_THRESHOLD = 2;
 
@@ -168,8 +168,8 @@ export function clusterLedgerItems(items) {
 /**
  * Decide a cluster's promotion target. A cluster that spans more than
  * {@link EPIC_COVERAGE_THRESHOLD} distinct coverage surfaces is broad enough to
- * warrant a plan-seed (`/plan --seed`); otherwise it is a single-deliverable
- * Story (`/plan`).
+ * warrant a plan-seed (`/mandrel-plan --seed`); otherwise it is a single-deliverable
+ * Story (`/mandrel-plan`).
  *
  * @param {{ coverages: string[] }} cluster
  * @returns {'story'|'epic'}
@@ -242,7 +242,7 @@ function routedToLink(issue, kind) {
  *      shared `routeFinding` against existing Issues (via the injected search
  *      port). This dedups against work already filed.
  *   2. On a `new` decision, open the follow-up ticket through the injected
- *      `createStory` (`/plan`) or `createPlanSeed` (`/plan --seed`) port,
+ *      `createStory` (`/mandrel-plan`) or `createPlanSeed` (`/mandrel-plan --seed`) port,
  *      chosen by {@link targetForCluster}. On any other decision, link back to
  *      the matched Issue rather than creating a duplicate.
  *   3. Stamp the resolved `routedTo` link onto every contributing ledger item
@@ -259,9 +259,9 @@ function routedToLink(issue, kind) {
  * @param {(finding: object) => Promise<Array<{ number: number, state: string, title?: string, body?: string }>>} [ports.searchCandidates]
  *   Optional semantic candidate search, forwarded to `routeFinding`.
  * @param {(cluster: object) => Promise<{ number: number, url?: string }>} ports.createStory
- *   Opens a single Story (`/plan`) for a tight cluster.
+ *   Opens a single Story (`/mandrel-plan`) for a tight cluster.
  * @param {(cluster: object) => Promise<{ number: number, url?: string }>} ports.createPlanSeed
- *   Opens a plan-seed (`/plan --seed`) run for a broad cluster.
+ *   Opens a plan-seed (`/mandrel-plan --seed`) run for a broad cluster.
  * @returns {Promise<{
  *   promotions: Array<{
  *     clusterKey: string,

package/.agents/scripts/lib/findings/route-finding.js

@@ -249,9 +249,9 @@ function parseAllFooterValues(text, pattern, isValid) {
  * Carry audit dedup provenance from a source document into a target body
  * (Story #4877).
  *
- * The audit sweep's Single-plan path emits a `/plan` seed whose MVP Scope
+ * The audit sweep's Single-plan path emits a `/mandrel-plan` seed whose MVP Scope
  * bullets already carry the `audit-fingerprints` / `audit-semantic-keys`
- * footers (Story #4626). Nothing then copied them into the Story `/plan`
+ * footers (Story #4626). Nothing then copied them into the Story `/mandrel-plan`
  * actually persisted, so the recommended path filed Stories that the next
  * sweep could not recognise and re-filed as new. It was left to the authoring
  * agent to notice HTML comments in a one-pager and hand-carry them — a