@mindrian_os/cli 2.0.0-beta.29 → 2.0.0-beta.31

package/data/research-sources.json

@@ -0,0 +1,58 @@
+{
+  "generated_note": "Phase 130.5 Plan 01 Task 1 -- single source-of-truth for the research-corpus source enum + per-source gating. Consumed by lib/core/research-corpus.cjs. Default-eligible sources (the four shipped-on) are openalex/arxiv/pubmed/tavily; brain-cypher is enabled but availability-gated; sci-bot ships enabled:false behind three opt-in gates per the 130.5 CONTEXT decision (Sci-Hub provenance + legal-review required). No em-dashes anywhere in this file (hyphens only).",
+  "schema_version": "1.0",
+  "default_sources": ["openalex", "arxiv", "pubmed", "tavily"],
+  "sources": [
+    {
+      "id": "openalex",
+      "enabled": true,
+      "kind": "academic",
+      "gates": [],
+      "note": "No API key. OpenAlex polite pool via OPENALEX_EMAIL. Delegated to lib/core/rs-fetcher-academic.cjs fetchOpenAlex."
+    },
+    {
+      "id": "arxiv",
+      "enabled": true,
+      "kind": "academic",
+      "gates": [],
+      "note": "No API key. Atom XML. Delegated to lib/core/rs-fetcher-academic.cjs fetchArxiv."
+    },
+    {
+      "id": "pubmed",
+      "enabled": true,
+      "kind": "academic",
+      "gates": [],
+      "note": "No API key. eutils JSON. Delegated to lib/core/rs-fetcher-academic.cjs fetchPubMed."
+    },
+    {
+      "id": "tavily",
+      "enabled": true,
+      "kind": "web",
+      "gates": ["env:TAVILY_API_KEY"],
+      "note": "Gated only by the existing TAVILY_API_KEY env var, not opt-in. Snippet-only web results. Missing key degrades to an empty envelope (no throw)."
+    },
+    {
+      "id": "tavily-extract",
+      "enabled": true,
+      "kind": "web",
+      "gates": ["env:TAVILY_API_KEY"],
+      "note": "URL -> full-page markdown via Tavily POST /extract (extract_depth advanced). Phase 220 url-ingest rung 1. NOT in default_sources - explicit-invocation only, never part of the default research fan-out. Missing key degrades to a typed provider_unavailable envelope (no throw)."
+    },
+    {
+      "id": "brain-cypher",
+      "enabled": true,
+      "kind": "graph",
+      "gates": ["brain:isAvailable"],
+      "note": "Generic framework/topic handles ONLY, bound via brain-client.sanitizeCypherInput. NEVER user content (Canon Part 8). Honors the Phase 110 packet contract: handles + enums only. Unavailable Brain degrades to an empty envelope (no throw)."
+    },
+    {
+      "id": "sci-bot",
+      "enabled": false,
+      "kind": "web",
+      "gates": ["opt_in:user", "token:user_supplied", "legal_review:signed_off"],
+      "endpoint": "https://sci-bot.ru",
+      "tier_on_enable": "practitioner",
+      "provenance_note": "Sci-Bot (https://sci-bot.ru) is an AI research assistant POWERED BY Sci-Hub (Alexandra Elbakyan). Sci-Hub bypasses paywalls and is legally contested in many jurisdictions. The plugin is a commercial product shipping to academic testers (pre-publication-priority + grant personas, Canon Part 8 protections). Routing research through a Sci-Hub-powered service MUST clear separate legal review before it can be enabled by default. No documented public API exists: it is a login + token + queue web UI (alpha). An adapter would need a user-supplied credential/token and must respect the queue + token budget. NO headless browser. When ever enabled, Sci-Bot output is a Practitioner/None-tier lead that MUST be re-grounded against an Academic-tier primary source (Canon Part 5) before it can inform a confirmed claim."
+    }
+  ]
+}

package/data/roadmap-type-chains.json

@@ -0,0 +1,28 @@
+{
+  "_note": "Phase 264 R2 roadmap-type to framework-name chain table - values are framework NAMES validated against command-resolver.cjs's framework_index via commandsForFramework, never slugs and never commands (D-05) - the file is hand-authored, NOT generated, because there is no frontmatter source of truth to generate from (D-04), contrast data/command-registry.json which IS generated - it is drift-tested by tests/test-264-roadmap-type-chains-drift.cjs, which is wired explicitly into tests/run-all-264.sh - agenda-setting-manifesto deliberately ships as a 2-step chain because /mos:present has an empty frameworks array in the registry and therefore cannot appear in a framework-name chain at all (RESEARCH Open Question 3; adding a framework to it would mean editing command frontmatter and regenerating the registry, which is outside this phase's boundaries) - Futures Wheel and Six Thinking Hats are the two framework_index names that are NOT autonomous-safe and must never be added to a chain here, because they would flip validateChainAutonomy(...).runnable to false.",
+  "landscape-analysis": [
+    "Usher's Model of Cumulative Synthesis",
+    "HSI Semantic Surprise Analysis Assistant"
+  ],
+  "technical-roadmap": [
+    "Problem Definition Transformation Framework",
+    "Reverse Salient Analysis",
+    "Knowns and Unknowns Matrix Framework"
+  ],
+  "pipeline-analysis": [
+    "Systems Thinking",
+    "Reverse Salient Analysis",
+    "S-Curve Analysis"
+  ],
+  "opportunity-analysis": [
+    "PWS Value Proposition"
+  ],
+  "agenda-setting-manifesto": [
+    "Beautiful Question Framework",
+    "MECE (Mutually Exclusive, Collectively Exhaustive)"
+  ],
+  "vision-paper": [
+    "Scenario Planning",
+    "Four Lenses of Innovation"
+  ]
+}

package/data/room-blueprints.json

@@ -0,0 +1,156 @@
+{
+  "_comment": "GENERATED by Phase 155-05. Blueprint families drive persona-conditional scaffolding. All section slugs MUST appear in the SECTION_NAMES frozen table in lib/core/room-skeleton-scaffold.cjs. run: node scripts/check-room-blueprints.cjs --check. Phase 275 grew SECTION_NAMES 8 -> 11; assumptions remains the only non-frozen slug still in use (hypothesis family).",
+  "_schema_version": "1",
+  "exploration": {
+    "description": "Blank-slate or CV-passer persona: map a domain or interest before committing to a problem statement.",
+    "arrival_assets": ["domain-or-interest", "cv-upload"],
+    "sections": [
+      "problem-definition",
+      "opportunity-bank",
+      "market-analysis",
+      "competitive-analysis"
+    ],
+    "_sections_note": "domain-decomposition is not a frozen slug; substituted problem-definition (houses domain analysis + diagnosis). opportunity-bank substituted for the domain-decomposition sub-sections per BIRTH-FLOW-BRIEF.md Section 3.",
+    "default_methodologies": [
+      "explore-domains",
+      "beautiful-question",
+      "map-unknowns"
+    ]
+  },
+  "solution-first": {
+    "description": "Solution-seeking-problem: the navigator arrives with a working solution and needs to find the right problem and user.",
+    "arrival_assets": ["solution-looking-for-problem"],
+    "sections": [
+      "solution-design",
+      "market-analysis",
+      "problem-definition",
+      "competitive-analysis"
+    ],
+    "_sections_note": "analogies/ is not a frozen slug; substituted competitive-analysis (competitive landscape analysis includes analogy mapping). BIRTH-FLOW-BRIEF.md Section 3: solution-design seeded first.",
+    "default_methodologies": [
+      "find-analogies",
+      "user-needs",
+      "validate"
+    ]
+  },
+  "problem-first": {
+    "description": "Problem-seeking-business: the navigator has observed a real problem and needs to find the business model and solution.",
+    "arrival_assets": ["problem-seeking-business"],
+    "sections": [
+      "problem-definition",
+      "market-analysis",
+      "opportunity-bank"
+    ],
+    "_sections_note": "mullins/ and validation sub-section are not frozen slugs; opportunity-bank substitutes for the mullins pipeline staging area per BIRTH-FLOW-BRIEF.md Section 3.",
+    "default_methodologies": [
+      "validate",
+      "mullins",
+      "explore-domains"
+    ]
+  },
+  "business-first": {
+    "description": "Business-case-seeking-problem: the navigator has a revenue logic or business case and needs to validate the underlying problem.",
+    "arrival_assets": ["business-case"],
+    "sections": [
+      "business-model",
+      "competitive-analysis",
+      "problem-definition",
+      "market-analysis"
+    ],
+    "_sections_note": "BIRTH-FLOW-BRIEF.md Section 3: business-model seeded first. All 4 slugs are in the frozen SECTION_NAMES table.",
+    "default_methodologies": [
+      "lean-canvas",
+      "challenge-assumptions",
+      "diagnose"
+    ]
+  },
+  "portfolio": {
+    "description": "Portfolio steward persona class: TTO / VC / PE / venture studio / accelerator / CVC / family office. The steward room is a room factory; unit-of-account varies by sub-type.",
+    "arrival_assets": ["portfolio-steward"],
+    "_arrival_assets_note": "Decision 7 (BIRTH-FLOW-BRIEF.md): portfolio steward is a persona CLASS not TTO alone. Part 8 P1 LPA confidentiality covers the full class.",
+    "sections": [
+      "opportunity-bank",
+      "market-analysis",
+      "competitive-analysis",
+      "problem-definition"
+    ],
+    "_sections_note": "portfolio/, assets/, connections/ are not frozen slugs. Substituted: opportunity-bank (the primary steward work surface), market-analysis, competitive-analysis, problem-definition. financial-model and legal-ip are intentionally omitted day-1 per BIRTH-FLOW-BRIEF.md Section 3.",
+    "default_methodologies": [
+      "find-connections",
+      "whitespace",
+      "explore-domains"
+    ]
+  },
+  "venture": {
+    "description": "Sole entrepreneur or defined venture: the navigator arrives with a venture in hand. Reproduces the SECTION_NAMES frozen 11 for backwards compatibility.",
+    "arrival_assets": ["defined-venture", "mva-brief"],
+    "sections": [
+      "problem-definition",
+      "market-analysis",
+      "solution-design",
+      "business-model",
+      "competitive-analysis",
+      "team-execution",
+      "legal-ip",
+      "financial-model",
+      "opportunity-bank",
+      "funding",
+      "strategy"
+    ],
+    "_sections_note": "Exact reproduction of the SECTION_NAMES frozen table in room-skeleton-scaffold.cjs. Backwards-compat guarantee: callers that pass blueprintFamily='venture' get the same sections as callers that pass no blueprintFamily. Phase 275 (D-01): grew 8 -> 11 alongside SECTION_NAMES; the exact-reproduction contract above is what forces this.",
+    "default_methodologies": [
+      "mva-brief",
+      "diagnose",
+      "lean-canvas"
+    ]
+  },
+  "program": {
+    "description": "Program or initiative: the navigator is launching a program, grant initiative, or institutional project rather than a commercial venture.",
+    "arrival_assets": ["program-initiative"],
+    "sections": [
+      "problem-definition",
+      "market-analysis",
+      "opportunity-bank",
+      "team-execution",
+      "funding"
+    ],
+    "_sections_note": "BIRTH-FLOW-BRIEF.md Section 3: program persona shares exploration + team execution focus without financial-model / legal-ip day 1. Phase 275 (D-01): funding added; this family's own description names grant initiatives, and the funding-as-empty-shell audit finding that promoted the section came from a room of this shape.",
+    "default_methodologies": [
+      "explore-domains",
+      "mullins",
+      "validate"
+    ]
+  },
+  "case-study": {
+    "description": "Case-study persona: the navigator is analyzing an existing venture or situation to extract lessons and apply them.",
+    "arrival_assets": ["case-study"],
+    "sections": [
+      "problem-definition",
+      "solution-design",
+      "market-analysis",
+      "financial-model"
+    ],
+    "_sections_note": "BIRTH-FLOW-BRIEF.md Section 3: case-study pattern = problem + solution + market + financial outcomes. All 4 slugs are in the frozen SECTION_NAMES table.",
+    "default_methodologies": [
+      "diagnose",
+      "lean-canvas",
+      "find-analogies"
+    ]
+  },
+  "hypothesis": {
+    "description": "Hypothesis-driven persona (Door 3): the navigator arrives with a falsifiable belief ('I believe ___') and needs to structure, challenge, and test it before committing.",
+    "arrival_assets": ["hypothesis-arrival"],
+    "sections": [
+      "problem-definition",
+      "assumptions",
+      "opportunity-bank"
+    ],
+    "_sections_note": "Phase 179-04 LOCKED set (CONTEXT decision 3). problem-definition is seeded with the captured hypothesis. assumptions + opportunity-bank are non-frozen slugs (not in the SECTION_NAMES frozen table); the scaffold skips them gracefully and the check-room-blueprints CI gate accepts them via EXTENDED_VALID_SLUGS_FOR_CHECK. No dedicated hypotheses section this phase.",
+    "default_methodologies": [
+      "structure-argument",
+      "challenge-assumptions",
+      "validate",
+      "research"
+    ]
+  }
+}

package/data/subagent-dispatch-grants.json

@@ -0,0 +1,150 @@
+{
+  "schema": "subagent-dispatch-grants/v1",
+  "purpose": "Reviewed pre-approvals for the Agent or Task dispatch token in commands/*.md frontmatter; a command may not carry the token without a matching row here.",
+  "tokens": ["Task", "Agent"],
+  "grants": [
+    {
+      "command": "commands/act.md",
+      "token": "Task",
+      "status": "granted",
+      "dispatch_shape": "one framework-runner subagent per framework selected for the --swarm run, spawned in a single turn",
+      "fan_bound": "planDispatch",
+      "reason": "act's --swarm mode dispatches multiple framework-runner subagents at once; without the grant each spawn triggers the normal Claude Code permission prompt, producing a per-agent approval storm on a command meant to run unattended.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "265-03-PLAN.md Task 2 (navigator decision, Open Question 4, SETTLED Add Task); 265-RESEARCH.md section 2d and its Security Domain ASVS V4 row"
+    },
+    {
+      "command": "commands/persona.md",
+      "token": "Task",
+      "status": "granted",
+      "dispatch_shape": "one persona-analyst subagent per De Bono Six Thinking Hat lens, run in parallel under --parallel",
+      "fan_bound": "6, one per De Bono hat",
+      "reason": "persona --parallel dispatches all six hat lenses at once; up to 6 permission prompts per invocation is the friction the grant is meant to remove on a routine, frequently-run command.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "265-03-PLAN.md Task 2 (navigator decision, Open Question 4, SETTLED Add Task); 265-RESEARCH.md section 2d and its Security Domain ASVS V4 row"
+    },
+    {
+      "command": "commands/grade.md",
+      "token": "Task",
+      "status": "granted",
+      "dispatch_shape": "one grading subagent per canonical room section, run in parallel under --full",
+      "fan_bound": "8 canonical room sections",
+      "reason": "grade --full dispatches a subagent per room section; up to 8 permission prompts per run was the measured friction, and the sections are independent grading work with no shared mutable state.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "265-03-PLAN.md Task 2 (navigator decision, Open Question 4, SETTLED Add Task); 265-RESEARCH.md section 2d and its Security Domain ASVS V4 row"
+    },
+    {
+      "command": "commands/deep-grade.md",
+      "token": "Agent",
+      "status": "granted",
+      "dispatch_shape": "one grading subagent per rubric-category batch, mirroring grade-grant's reviewer-panel fan-out over one shared source",
+      "fan_bound": "resolveFanoutCap / FUTURES_FANOUT_CAP default 5",
+      "reason": "deep-grade already declared the Agent dispatch token before Phase 265 began; this row is the retroactive review the grant never received. The token spells Agent rather than Task, and the 265-03 tripwire greps for Task only, so this pre-existing grant was invisible to the exact control meant to catch a fourth command acquiring dispatch privilege.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "commands/deep-grade.md frontmatter (Agent already present, Phase 265 finding, not newly added); the token differs from the other three commands here, which all declare Task, and the 265-03 Task-only tripwire (tests/test-265-swarm-task-grant.cjs, grep on the literal Task) could not see this grant; 265-RESEARCH-generative-redesign.md 'house pattern any redesign must mirror' section (resolveFanoutCap / FUTURES_FANOUT_CAP default 5, grade-grant's two-batch idiom)"
+    },
+    {
+      "command": "commands/opportunities.md",
+      "token": "Agent",
+      "status": "granted",
+      "dispatch_shape": "undocumented: the command frontmatter declares the Agent dispatch token, but no prose in the command body names a subagent dispatch instruction, a subagent_type, or a fan-out shape anywhere in the file",
+      "fan_bound": "not established; no fan-out instruction exists to bound",
+      "reason": "opportunities.md already declared Agent before Phase 265 began, exactly like deep-grade, but unlike deep-grade there is no corresponding dispatch prose anywhere in the file to explain why. Found while rewriting the Task 2 tripwire (arm 1 flagged it as an undeclared row), not by the Task 1 read_first, which stated only deep-grade carried Agent -- that inventory was incomplete. Recorded here as a reviewed-but-vestigial grant rather than silently widened or silently dropped; a follow-on plan should either wire a real dispatch instruction and update this row, or remove the unused Agent token from the command file.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "commands/opportunities.md frontmatter line 16 (Agent already present, Phase 265 finding, not newly added, and NOT part of the Task 1 nine-row inventory); grep for agent/spawn/dispatch/fan-out prose in the command body returns zero hits beyond the frontmatter token itself"
+    },
+    {
+      "command": "commands/research.md",
+      "token": "Agent",
+      "status": "granted",
+      "dispatch_shape": "one subagent per research subquestion, fanning out independently and verified back as an any-order basket (the existing deep_research fan-out, per the command's own hitl_why)",
+      "fan_bound": "not established in the command body beyond the existing deep_research fan-out; no explicit numeric or resolver cap named",
+      "reason": "research.md already declared Agent before Phase 265 began, exactly like deep-grade. Its hitl_why states subquestions fan out independently and are verified as an any-order basket, and the URL-mode section names the existing deep_research fan-out as byte-unchanged, so a real dispatch shape exists here, unlike opportunities.md. Found while rewriting the Task 2 tripwire (arm 1 flagged it), not by the Task 1 read_first, which stated only deep-grade carried Agent -- that inventory was incomplete.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "commands/research.md frontmatter line 24 (Agent already present, Phase 265 finding, not newly added, and NOT part of the Task 1 nine-row inventory); commands/research.md hitl_why ('Research subquestions fan out independently and are verified as an any-order basket') and its URL-mode section ('keeps the existing deep_research fan-out below byte-unchanged')"
+    },
+    {
+      "command": "commands/mos-reason.md",
+      "token": "Task",
+      "status": "granted",
+      "dispatch_shape": "one reasoning subagent per populated room section, each reading its own artifacts and running the 4-stage Feynman pass independently before results are merged",
+      "fan_bound": "planDispatch",
+      "reason": "mos-reason currently loops 8-11 sections sequentially into one context, each requiring a full artifact read plus a 4-stage reasoning pass; the sections are disjoint in and out, so parallelizing needs the dispatch grant before plan 265-14 can ship it.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "265-RESEARCH-generative-redesign.md section 1 'mos-reason - REDESIGN CANDIDATE (highest confidence)', lines 116-215; verified shipped shape against 265-14-SUMMARY.md: PHASE 1 dispatches one framework-runner subagent per populated section, sized via planDispatch, matching this row's dispatch_shape and fan_bound as reviewed -- no correction needed"
+    },
+    {
+      "command": "commands/scout.md",
+      "token": "Task",
+      "status": "granted",
+      "dispatch_shape": "one subagent per tracked competitor, each running its own web-evidence pass",
+      "fan_bound": "the existing max 5",
+      "reason": "scout's per-competitor research is independent work already bounded at 5; plan 265-15 needs the reviewed grant before it can move that work from sequential to parallel dispatch.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "265-RESEARCH-generative-redesign.md section 2 (commands/scout.md, 298 lines) and the phase's dispatch-optimizer cost bound already governing scout's existing max; verified shipped shape against 265-15-SUMMARY.md: subagent_type research, one per tracked competitor, max 5 unchanged, matching this row's dispatch_shape and fan_bound as reviewed -- no correction needed"
+    },
+    {
+      "command": "commands/file-meeting.md",
+      "token": "Task",
+      "status": "granted",
+      "dispatch_shape": "one extraction subagent per perspective in the perspective set, each reading the full meeting transcript independently",
+      "fan_bound": "the perspective-set size",
+      "reason": "file-meeting's extraction currently runs one perspective at a time over the full transcript; plan 265-19 needs the reviewed grant to fan the perspective set out in parallel instead.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "265-RESEARCH-file-meeting-deep-dive.md (perspective-set extraction shape) cross-referenced with 265-RESEARCH-generative-redesign.md's fan-out house pattern; verified shipped shape against 265-19-SUMMARY.md: five subagent_type meeting-perspective-extractor workers, each reading the full transcript, perspective-set size 5, matching this row's dispatch_shape and fan_bound as reviewed -- no correction needed"
+    },
+    {
+      "command": "commands/vault.md",
+      "token": "Task",
+      "status": "granted",
+      "dispatch_shape": "one subagent per guessed-section group, sized and gated by a cost threshold before dispatch",
+      "fan_bound": "planDispatch, threshold-gated",
+      "reason": "vault's section-guessing work groups naturally by section; plan 265-21 needs the reviewed grant to dispatch one subagent per group once the guess count clears the threshold that makes parallel dispatch worth its cost.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "265-RESEARCH-generative-redesign.md section 4 (commands/vault.md, 204 lines) and the house pattern's planDispatch sizing idiom; verified shipped shape against 265-21-SUMMARY.md: VAULT_REVIEW_FANOUT_THRESHOLD (default 40) gates a single-pass path below threshold and a section-group fan-out via planDispatch/resolveFanoutCap at or above it, matching this row's dispatch_shape and fan_bound as reviewed -- no correction needed"
+    },
+    {
+      "command": "commands/find-analogies.md",
+      "token": "Task",
+      "status": "granted",
+      "dispatch_shape": "one subagent per navigator-approved audited query, each running its own external fetch, SAPPhIRE encoding and structural mapping pass",
+      "fan_bound": "resolveFanoutCap / FUTURES_FANOUT_CAP default 5",
+      "reason": "find-analogies' --external mode does real per-query analytical work (fetch, SAPPhIRE encoding, structural mapping), but dedup risk across query families is high, so the navigator scoped the parallel grant to an audited query list rather than an open query set; plan 265-21 ships it once that audit exists.",
+      "reviewed_by": "navigator",
+      "reviewed_date": "2026-08-27",
+      "ratified_date": "2026-08-27",
+      "ratified_in": "265-23",
+      "evidence": "265-RESEARCH-generative-redesign.md section 5 'find-analogies (--external only) - REDESIGN CANDIDATE, scoped, lower priority', lines 523-551 and 907-921 (dedup risk, Part 8 boundary note); verified shipped shape against 265-21-SUMMARY.md: one analogy-query-fetcher subagent per navigator-approved audited query, each doing its own fetch + SAPPhIRE encoding + structural mapping, clamped through resolveFanoutCap (FUTURES_FANOUT_CAP default 5), matching this row's dispatch_shape and fan_bound as reviewed -- no correction needed"
+    }
+  ]
+}