peaks-loop 4.0.0-beta → 4.0.0-beta.2

package/dist/src/services/workflow/workflow-autonomous-service.d.ts

@@ -1,7 +1,7 @@
 import type { CapabilityItemType } from '../recommendations/recommendation-types.js';
 import type { ModelProviderConfig, WorkspaceConfig } from '../config/config-types.js';
 import { type RdPlanResult } from '../rd/rd-service.js';
-import { type SoloMode, type WorkflowMode, type WorkflowRouterPlan } from './workflow-router-service.js';
+import { type CodeMode, type WorkflowMode, type WorkflowRouterPlan } from './workflow-router-service.js';
 export { getResumeRequiredArtifacts, getResumeArtifactsStatus, createResumePlan } from './workflow-autonomous-resume-helpers.js';
 export type CapabilitySurface = 'skill' | 'mcp' | 'plugin' | 'expert';
 export type CapabilityPurpose = 'code-review' | 'security-review' | 'coding-standards' | 'docs-lookup' | 'browser-validation' | 'browser-debug' | 'design-context' | 'design-source' | 'code-search' | 'database-inspection' | 'browser-agent' | 'worker-guidance' | 'memory' | 'context-management' | 'ui-components' | 'spec-workflow' | 'repo-intelligence' | 'openspec' | 'workflow-methodology' | 'workflow-reference' | 'workflow-guidance' | 'product-guidance' | 'design-reference' | 'ui-reference' | 'engineering-guidance' | 'typescript-guidance' | 'quality-guidance' | 'skill-pack' | 'external-skill' | 'design-critique' | 'design-guidance' | 'cloud-skill-pack';
@@ -20,7 +20,7 @@ export type CapabilityCandidate = {
 };
 export type AutonomousWorkflowRequest = {
     readonly mode: WorkflowMode;
-    readonly soloMode?: SoloMode;
+    readonly codeMode?: CodeMode;
     readonly sessionId: string;
     readonly goal: string;
     readonly maxWorkers?: number;
@@ -68,7 +68,7 @@ export type AutonomousStoragePlan = {
 };
 export type AutonomousMvpPackage = {
     readonly mode: WorkflowMode;
-    readonly soloMode: SoloMode | undefined;
+    readonly codeMode: CodeMode | undefined;
     readonly executionMode: 'preview';
     readonly dryRun: true;
     readonly routePolicy: WorkflowRouterPlan['routePolicy'];

package/dist/src/services/workflow/workflow-autonomous-service.js

@@ -205,7 +205,7 @@ function createCapabilityPlan(request) {
 function createMvpPackage(request, routePlan, rdPlan, capabilityPlan, ready) {
     return {
         mode: request.mode,
-        soloMode: routePlan.soloMode,
+        codeMode: routePlan.codeMode,
         executionMode: 'preview',
         dryRun: true,
         routePolicy: routePlan.routePolicy,
@@ -240,7 +240,7 @@ export function createAutonomousWorkflowPlan(request) {
     const available = hasArtifactWorkspace(request, artifactWorkspacePath);
     const routePlan = createWorkflowRouterPlan({
         mode: request.mode,
-        ...(request.soloMode !== undefined ? { soloMode: request.soloMode } : {}),
+        ...(request.codeMode !== undefined ? { codeMode: request.codeMode } : {}),
         sessionId: request.sessionId,
         goal,
         maxWorkers,

package/dist/src/services/workflow/workflow-router-service.d.ts

@@ -1,18 +1,18 @@
 import { type ModelProviderConfig, type WorkspaceConfig } from '../config/config-types.js';
 import { type RdPlanResult } from '../rd/rd-service.js';
 import { type TechPlanResult, type TechStatus } from '../tech/tech-service.js';
-export type WorkflowMode = 'solo' | 'team';
-export type SoloMode = 'full-auto' | 'guided' | 'rnd';
+export type WorkflowMode = 'code' | 'team';
+export type CodeMode = 'full-auto' | 'guided' | 'rnd';
 export type ModelTier = 'top-tier' | 'mid-tier';
 export type ModelRole = 'strongest' | 'execution';
-export type WorkflowRoutePolicy = 'solo-broad-multi-model' | 'team-rd-limited-multi-model';
+export type WorkflowRoutePolicy = 'code-broad-multi-model' | 'team-rd-limited-multi-model';
 export type WorkflowStepStage = 'product-direction' | 'design-direction' | 'tech-direction' | 'tech-review' | 'rd-planning' | 'coding-execution' | 'unit-test-execution' | 'quality-review';
 export type WorkflowStepOwner = 'peaks-code' | 'peaks-rd' | 'peaks-tech' | 'human';
 export type WorkflowRouterRequest = {
     sessionId: string;
     goal: string;
     mode: WorkflowMode;
-    soloMode?: SoloMode;
+    codeMode?: CodeMode;
     maxWorkers?: number;
     dryRun: true;
     artifactWorkspacePath?: string;
@@ -64,7 +64,7 @@ export type WorkflowRouterPlan = {
     readonly sessionId: string;
     readonly goal: string;
     readonly mode: WorkflowMode;
-    readonly soloMode?: SoloMode;
+    readonly codeMode?: CodeMode;
     readonly executionMode: 'autonomous';
     readonly decisionProfile: string;
     readonly dryRun: true;
@@ -81,5 +81,5 @@ export type WorkflowRouterPlan = {
     readonly constraints: readonly string[];
 };
 export declare function isWorkflowMode(mode: string): mode is WorkflowMode;
-export declare function isSoloMode(value: string): value is SoloMode;
+export declare function isCodeMode(value: string): value is CodeMode;
 export declare function createWorkflowRouterPlan(request: WorkflowRouterRequest): WorkflowRouterPlan;

package/dist/src/services/workflow/workflow-router-service.js

@@ -18,7 +18,7 @@ const EXECUTION_STAGES = ['coding-execution', 'unit-test-execution'];
 const GUIDED_DECISION_STAGES = ['product-direction', 'design-direction'];
 const GOVERNED_DECISION_STAGES = ['product-direction', 'design-direction', 'tech-direction', 'tech-review'];
 export function isWorkflowMode(mode) {
-    return mode === 'solo' || mode === 'team';
+    return mode === 'code' || mode === 'team';
 }
 function assertSupportedMode(mode) {
     if (!isWorkflowMode(mode)) {
@@ -32,9 +32,9 @@ function normalizeGoal(goal) {
     }
     return normalized;
 }
-function assertSoloModeAllowed(mode, soloMode) {
-    if (mode !== 'solo' && soloMode !== undefined) {
-        throw new Error('soloMode requires solo workflow mode');
+function assertCodeModeAllowed(mode, codeMode) {
+    if (mode !== 'code' && codeMode !== undefined) {
+        throw new Error('codeMode requires code workflow mode');
     }
 }
 function step(input, executionModelId) {
@@ -48,29 +48,29 @@ function step(input, executionModelId) {
         writesArtifacts: false
     };
 }
-export function isSoloMode(value) {
+export function isCodeMode(value) {
     return value === 'full-auto' || value === 'guided' || value === 'rnd';
 }
-function getDecisionProfileSummary(mode, soloMode) {
+function getDecisionProfileSummary(mode, codeMode) {
     if (mode === 'team') {
         return 'Team mode keeps product and design governance on a human-controlled path while RD execution follows recommended defaults.';
     }
-    if (soloMode === 'guided') {
+    if (codeMode === 'guided') {
         return 'Guided mode keeps the user in the decision loop for the early recommended defaults, while later execution remains bounded by the routing plan.';
     }
-    if (soloMode === 'rnd') {
+    if (codeMode === 'rnd') {
         return 'R&D mode asks for technical confirmation up front, then applies recommended defaults for implementation, testing, review, and safety checks.';
     }
     return 'Full-auto mode applies recommended defaults for product, design, and tech decisions, then runs the engineering pipeline end to end under routing gates.';
 }
-function annotateSteps(steps, soloMode) {
-    const decisionStages = soloMode === 'guided'
+function annotateSteps(steps, codeMode) {
+    const decisionStages = codeMode === 'guided'
         ? GUIDED_DECISION_STAGES
         : GOVERNED_DECISION_STAGES;
     return steps.map((currentStep) => {
         const isDecisionStage = decisionStages.includes(currentStep.stage);
         const reasonPrefix = isDecisionStage
-            ? `[${soloMode}] decision stage`
+            ? `[${codeMode}] decision stage`
             : '[routed] execution stage';
         return {
             ...currentStep,
@@ -80,18 +80,18 @@ function annotateSteps(steps, soloMode) {
 }
 function createSoloSteps(executionModelId) {
     return [
-        step({ id: 'solo-product-direction', stage: 'product-direction', owner: 'peaks-code', modelTier: 'top-tier', reason: 'Product direction needs strong judgment before execution work is delegated.', dependsOn: [] }, executionModelId),
-        step({ id: 'solo-design-direction', stage: 'design-direction', owner: 'peaks-code', modelTier: 'top-tier', reason: 'Design direction uses the recommended default before cheaper implementation work.', dependsOn: ['solo-product-direction'] }, executionModelId),
-        step({ id: 'solo-tech-direction', stage: 'tech-direction', owner: 'peaks-tech', modelTier: 'top-tier', reason: 'Technical boundaries and approval gates use the recommended default with high-confidence planning.', dependsOn: ['solo-design-direction'] }, executionModelId),
-        step({ id: 'solo-tech-review', stage: 'tech-review', owner: 'peaks-tech', modelTier: 'top-tier', reason: 'Tech artifacts and gate decisions require strong review and a recommended default path.', dependsOn: ['solo-tech-direction'] }, executionModelId),
-        step({ id: 'solo-rd-planning', stage: 'rd-planning', owner: 'peaks-rd', modelTier: 'top-tier', reason: 'RD task decomposition and acceptance criteria use the recommended default before execution delegation.', dependsOn: ['solo-tech-review'] }, executionModelId),
-        step({ id: 'solo-coding-execution', stage: 'coding-execution', owner: 'peaks-rd', modelTier: executionModelId === STRONGEST_MODEL_ID ? 'top-tier' : 'mid-tier', reason: `Coding and routine refactoring must use the configured execution worker model ${executionModelId}.`, dependsOn: ['solo-rd-planning'] }, executionModelId),
-        step({ id: 'solo-unit-test-execution', stage: 'unit-test-execution', owner: 'peaks-rd', modelTier: executionModelId === STRONGEST_MODEL_ID ? 'top-tier' : 'mid-tier', reason: `Unit test authoring and focused test runs must use the configured execution worker model ${executionModelId}.`, dependsOn: ['solo-coding-execution'] }, executionModelId),
-        step({ id: 'solo-quality-review', stage: 'quality-review', owner: 'peaks-code', modelTier: 'top-tier', reason: 'Reducer and final quality gates need strong synthesis and risk review.', dependsOn: ['solo-unit-test-execution'] }, executionModelId)
+        step({ id: 'code-product-direction', stage: 'product-direction', owner: 'peaks-code', modelTier: 'top-tier', reason: 'Product direction needs strong judgment before execution work is delegated.', dependsOn: [] }, executionModelId),
+        step({ id: 'code-design-direction', stage: 'design-direction', owner: 'peaks-code', modelTier: 'top-tier', reason: 'Design direction uses the recommended default before cheaper implementation work.', dependsOn: ['code-product-direction'] }, executionModelId),
+        step({ id: 'code-tech-direction', stage: 'tech-direction', owner: 'peaks-tech', modelTier: 'top-tier', reason: 'Technical boundaries and approval gates use the recommended default with high-confidence planning.', dependsOn: ['code-design-direction'] }, executionModelId),
+        step({ id: 'code-tech-review', stage: 'tech-review', owner: 'peaks-tech', modelTier: 'top-tier', reason: 'Tech artifacts and gate decisions require strong review and a recommended default path.', dependsOn: ['code-tech-direction'] }, executionModelId),
+        step({ id: 'code-rd-planning', stage: 'rd-planning', owner: 'peaks-rd', modelTier: 'top-tier', reason: 'RD task decomposition and acceptance criteria use the recommended default before execution delegation.', dependsOn: ['code-tech-review'] }, executionModelId),
+        step({ id: 'code-coding-execution', stage: 'coding-execution', owner: 'peaks-rd', modelTier: executionModelId === STRONGEST_MODEL_ID ? 'top-tier' : 'mid-tier', reason: `Coding and routine refactoring must use the configured execution worker model ${executionModelId}.`, dependsOn: ['code-rd-planning'] }, executionModelId),
+        step({ id: 'code-unit-test-execution', stage: 'unit-test-execution', owner: 'peaks-rd', modelTier: executionModelId === STRONGEST_MODEL_ID ? 'top-tier' : 'mid-tier', reason: `Unit test authoring and focused test runs must use the configured execution worker model ${executionModelId}.`, dependsOn: ['code-coding-execution'] }, executionModelId),
+        step({ id: 'code-quality-review', stage: 'quality-review', owner: 'peaks-code', modelTier: 'top-tier', reason: 'Reducer and final quality gates need strong synthesis and risk review.', dependsOn: ['code-unit-test-execution'] }, executionModelId)
     ];
 }
-function createSoloStepsForMode(soloMode, executionModelId) {
-    return annotateSteps(createSoloSteps(executionModelId), soloMode);
+function createSoloStepsForMode(codeMode, executionModelId) {
+    return annotateSteps(createSoloSteps(executionModelId), codeMode);
 }
 function createTeamSteps(executionModelId) {
     return [
@@ -150,21 +150,21 @@ function createModeStatus(economyMode, swarmMode, executionModelId, executionMod
         summary: `${economySummary} ${swarmSummary}`
     };
 }
-function getSoloMode(mode, soloMode) {
-    if (mode !== 'solo') {
+function getCodeMode(mode, codeMode) {
+    if (mode !== 'code') {
         return undefined;
     }
-    if (soloMode === undefined) {
+    if (codeMode === undefined) {
         return 'full-auto';
     }
-    if (!isSoloMode(soloMode)) {
-        throw new Error('Unsupported solo mode');
+    if (!isCodeMode(codeMode)) {
+        throw new Error('Unsupported code mode');
     }
-    return soloMode;
+    return codeMode;
 }
 export function createWorkflowRouterPlan(request) {
     assertSupportedMode(request.mode);
-    assertSoloModeAllowed(request.mode, request.soloMode);
+    assertCodeModeAllowed(request.mode, request.codeMode);
     // Slice 2026-06-29-change-id-root-removal: change-id is metadata-only;
     // no structural validation gate fires here.
     const goal = normalizeGoal(request.goal);
@@ -185,8 +185,8 @@ export function createWorkflowRouterPlan(request) {
     const effectiveProviders = request.config?.providers ?? { minimax: { model: 'minimax-2.7' } };
     const executionModelId = economyMode !== false ? getConfiguredExecutionModelId(effectiveProviders) : STRONGEST_MODEL_ID;
     const modeStatus = createModeStatus(economyMode, swarmMode, executionModelId, economyMode ? 'config.providers' : 'planner-reviewer-strongest-model');
-    const soloMode = getSoloMode(request.mode, request.soloMode);
-    const decisionProfile = getDecisionProfileSummary(request.mode, soloMode);
+    const codeMode = getCodeMode(request.mode, request.codeMode);
+    const decisionProfile = getDecisionProfileSummary(request.mode, codeMode);
     const artifactWorkspacePath = request.artifactWorkspacePath ?? (request.workspace ? getLocalArtifactPath(request.workspace) : undefined);
     const sharedWorkspaceOptions = {
         ...(artifactWorkspacePath ? { artifactWorkspacePath } : {}),
@@ -195,7 +195,7 @@ export function createWorkflowRouterPlan(request) {
     const techStatus = getTechStatus({ sessionId: request.sessionId, ...sharedWorkspaceOptions });
     const techPlan = createTechPlan({ sessionId: request.sessionId, goal, swarm: swarmMode, dryRun: true, ...sharedWorkspaceOptions });
     const rdPlan = createRdSwarmPlan({ skill: 'rd', sessionId: request.sessionId, goal, maxWorkers, swarmMode, executionModelId, dryRun: true, ...sharedWorkspaceOptions });
-    const steps = soloMode ? createSoloStepsForMode(soloMode, executionModelId) : createTeamSteps(executionModelId);
+    const steps = codeMode ? createSoloStepsForMode(codeMode, executionModelId) : createTeamSteps(executionModelId);
     const blockedReasons = uniqueStrings([
         ...techStatus.blockedReasons,
         ...getTechPlanBlockedReasons(techPlan),
@@ -208,11 +208,11 @@ export function createWorkflowRouterPlan(request) {
         sessionId: request.sessionId,
         goal,
         mode: request.mode,
-        ...(soloMode ? { soloMode } : {}),
+        ...(codeMode ? { codeMode } : {}),
         executionMode: 'autonomous',
         decisionProfile,
         dryRun: true,
-        routePolicy: request.mode === 'solo' ? 'solo-broad-multi-model' : 'team-rd-limited-multi-model',
+        routePolicy: request.mode === 'code' ? 'code-broad-multi-model' : 'team-rd-limited-multi-model',
         modelRouting: createModelRouting(steps, executionModelId),
         modelAssignments: createModelAssignments(steps),
         modeStatus,

package/dist/src/services/workspace/claude-settings-template.d.ts

@@ -51,7 +51,7 @@ export declare const CLAUDE_SETTINGS_LOCAL_FILENAME = ".claude/settings.local.js
  *           bypass is the only emit. Bash enforcement is owned by
  *           `peaks gate enforce` in `settings.json`.
  *   1.3.0 — added the v3.1.2 `Bash` PreToolUse matcher that runs
- *           `peaks solo gate-step-08 --project .` (Step 0.8 mechanical
+ *           `peaks code gate-step-08 --project .` (Step 0.8 mechanical
  *           gate). The existing Write|Edit|MultiEdit matcher is
  *           preserved. The new matcher's exit code is the load-bearing
  *           signal: 0 = allow, 2 = block (with stderr BLOCKED reason).

package/dist/src/services/workspace/claude-settings-template.js

@@ -51,7 +51,7 @@ export const CLAUDE_SETTINGS_LOCAL_FILENAME = '.claude/settings.local.json';
  *           bypass is the only emit. Bash enforcement is owned by
  *           `peaks gate enforce` in `settings.json`.
  *   1.3.0 — added the v3.1.2 `Bash` PreToolUse matcher that runs
- *           `peaks solo gate-step-08 --project .` (Step 0.8 mechanical
+ *           `peaks code gate-step-08 --project .` (Step 0.8 mechanical
  *           gate). The existing Write|Edit|MultiEdit matcher is
  *           preserved. The new matcher's exit code is the load-bearing
  *           signal: 0 = allow, 2 = block (with stderr BLOCKED reason).
@@ -216,7 +216,7 @@ export function buildClaudeSettingsLocalJson() {
                 },
                 {
                     // v3.1.2 Step 0.8 — Mechanical PreToolUse gate. Runs
-                    // `peaks solo gate-step-08 --project .` before every Bash
+                    // `peaks code gate-step-08 --project .` before every Bash
                     // tool call. Exit 0 = allow (with structured stdout
                     // describing the decision + optional `Next: slice #N+1 of
                     // M (<currentSlice>)` line when progress.json exists). Exit
@@ -235,7 +235,7 @@ export function buildClaudeSettingsLocalJson() {
     };
 }
 /**
- * v3.1.2: build the Bash matcher command that runs `peaks solo
+ * v3.1.2: build the Bash matcher command that runs `peaks code
  * gate-step-08`. We invoke the CLI directly (not via `node -e "..."`)
  * because the CLI is the only legitimate source of the structured
  * decision + Next: slice context. Exit code is the load-bearing
@@ -246,9 +246,9 @@ export function buildClaudeSettingsLocalJson() {
  */
 function buildBashGateStep08Command() {
     // The hook receives the tool call on stdin. We ignore stdin and
-    // delegate entirely to `peaks solo gate-step-08`, which reads
+    // delegate entirely to `peaks code gate-step-08`, which reads
     // .peaks/_runtime/<sessionId>/job-shape.json and last-prompt.txt.
     // `${CLAUDE_PROJECT_DIR}` resolves to the consumer project's root
     // (Claude Code's standard convention).
-    return 'peaks solo gate-step-08 --project "${CLAUDE_PROJECT_DIR}"';
+    return 'peaks code gate-step-08 --project "${CLAUDE_PROJECT_DIR}"';
 }

package/dist/src/shared/version.d.ts

@@ -1 +1 @@
-export declare const CLI_VERSION = "4.0.0-beta";
+export declare const CLI_VERSION = "4.0.0-beta.2";

package/dist/src/shared/version.js

@@ -1 +1 @@
-export const CLI_VERSION = "4.0.0-beta";
+export const CLI_VERSION = "4.0.0-beta.2";

package/output-styles/peaks-skill-swarm.md

@@ -4,7 +4,7 @@ description: Peaks 专用输出风格：仅在 peaks skills 工作流中用东
 keep-coding-instructions: true
 ---
 
-This output style is self-gated. Apply the sections below only when the current task explicitly invokes or continues a Peaks-Loop skill workflow, including `/peaks-*`, `skills/peaks-*`, Peaks-Loop PRD/RD/QA/UI/SC/TXT/Solo work, or edits to this repository's `skills/` directory. For unrelated tasks, preserve the default Claude Code behavior and keep responses concise.
+This output style is self-gated. Apply the sections below only when the current task explicitly invokes or continues a Peaks-Loop skill workflow, including `/peaks-*`, `skills/peaks-*`, Peaks-Loop PRD/RD/QA/UI/SC/TXT/Code work, or edits to this repository's `skills/` directory. For unrelated tasks, preserve the default Claude Code behavior and keep responses concise.
 
 ## Peaks-Loop response contract
 
@@ -14,7 +14,7 @@ When active, make the skill transition visually obvious with a light Northeaster
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Peaks-Loop Skill Active: <skill-name> — 整活开工，但不整虚的
 Peaks-Loop Role Chain: <PRD → RD → QA → SC, or single role>
-Peaks-Loop Mode: <Solo | Assisted | Swarm | Strict | Economy>
+Peaks-Loop Mode: <Code | Assisted | Swarm | Strict | Economy>
 Peaks-Loop Current Gate: <confirmation | dry-run | coverage | QA | commit boundary | handoff>
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
@@ -54,7 +54,7 @@ Peaks-Loop Skill: <skill-name> | Peaks-Loop Gate: <current gate> | Next: <one sh
 Structure active Peaks-Loop responses around:
 
 1. **Peaks-Loop Role** — name the active Peaks-Loop role or role chain, for example PRD → RD → QA → SC.
-2. **Peaks-Loop Mode** — state whether the workflow is Solo, Assisted, Swarm, Strict, or Economy.
+2. **Peaks-Loop Mode** — state whether the workflow is Code, Assisted, Swarm, Strict, or Economy.
 3. **Peaks-Loop Current Gate** — show the current required gate: product confirmation, RD dry-run, coverage, QA acceptance, commit boundary, or handoff.
 4. **Action** — describe the immediate next action in one short sentence before tool use.
 5. **Peaks-Loop Evidence** — end with only the evidence that matters: commands, artifacts, changed files, blockers, and next action.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "peaks-loop",
-  "version": "4.0.0-beta",
+  "version": "4.0.0-beta.2",
   "description": "Loop Engineering CLI — workflow primitive / loop guards / evaluators / slice orchestration",
   "author": "SquabbyZ",
   "license": "MIT",

package/skills/bee/peaks-qa/SKILL.md

@@ -56,7 +56,7 @@ The canonical scope dir for this request is provided as `envelope.data.scopeDir`
 
 ## Sub-agent dispatch (when launched by peaks-code swarm)
 
-When this skill is launched as a sub-agent via `peaks sub-agent dispatch <role>` (then the LLM executes the returned toolCall) from `peaks-code`, the following sections of THIS skill are **suspended** for the sub-agent run: Session id, Skill presence, Workspace initialization, Mode selection, Statusline install. The sub-agent must NOT call `peaks request init` (Solo already initialised the slot), and must write `.peaks/_runtime/<sessionId>/qa/test-cases/<rid>.md` with test cases that link to PRD acceptance items. Return only a compact JSON envelope.
+When this skill is launched as a sub-agent via `peaks sub-agent dispatch <role>` (then the LLM executes the returned toolCall) from `peaks-code`, the following sections of THIS skill are **suspended** for the sub-agent run: Session id, Skill presence, Workspace initialization, Mode selection, Statusline install. The sub-agent must NOT call `peaks request init` (Code already initialised the slot), and must write `.peaks/_runtime/<sessionId>/qa/test-cases/<rid>.md` with test cases that link to PRD acceptance items. Return only a compact JSON envelope.
 
 > **v2.15.0+ 校准:** 每个 slice 完成,user 必介入做**业务审阅**(4-5 项业务/产品清单:业务流程 / 需求覆盖 / 边界 case / UI 装配 / 能合入下版吗),**不是技术审阅**。业务审过 → 进 final;业务不通过 → 返工。详见 `.peaks/memory/peaks-loop-slice-review-and-qa-perspective.md`。
 

package/skills/bee/peaks-qa/references/artifact-per-request.md

@@ -9,12 +9,12 @@ The three files for any QA invocation land under the active session's `qa/` work
 | # | File | Path | Reader | Content |
 |---|------|------|--------|---------|
 | 1 | Test cases | `.peaks/_runtime/<session-id>/qa/test-cases/<request-id>.md` | RD (before impl), QA | Generated test scenarios with status |
-| 2 | Test report | `.peaks/_runtime/<session-id>/qa/test-reports/<request-id>.md` | QA, SC, Solo | Summary, coverage%, security, perf, risks |
-| 3 | Request artifact | `.peaks/_runtime/<session-id>/qa/requests/<request-id>.md` | Solo, RD↔QA loop | Verdict, boundary check, links to #1 and #2 |
+| 2 | Test report | `.peaks/_runtime/<session-id>/qa/test-reports/<request-id>.md` | QA, SC, Code | Summary, coverage%, security, perf, risks |
+| 3 | Request artifact | `.peaks/_runtime/<session-id>/qa/requests/<request-id>.md` | Code, RD↔QA loop | Verdict, boundary check, links to #1 and #2 |
 
 ## Required content
 
-The request artifact is the **verdict carrier** — it must include: QA verdict (`pass` / `return-to-rd` / `blocked`), the red-line audit outcome, links to the test-cases and test-report, the boundary check (acceptance items covered, gaps), and any cross-skill handoff notes for Solo. The test cases file enumerates every scenario with status; the test report summarises execution and links the security / performance / regression companion files.
+The request artifact is the **verdict carrier** — it must include: QA verdict (`pass` / `return-to-rd` / `blocked`), the red-line audit outcome, links to the test-cases and test-report, the boundary check (acceptance items covered, gaps), and any cross-skill handoff notes for Code. The test cases file enumerates every scenario with status; the test report summarises execution and links the security / performance / regression companion files.
 
 ## Rules
 

package/skills/bee/peaks-qa/references/qa-sub-agent-dispatch.md

@@ -3,14 +3,14 @@
 > Body of `## Sub-agent dispatch`. When this skill is launched as a sub-agent via `peaks sub-agent dispatch <role>` (then the LLM executes the returned toolCall) from `peaks-code`, the following sections of THIS skill are **suspended** for the sub-agent run:
 
 - **Session id** — use the parent's sid (read `.peaks/_runtime/session.json` or pass `--session-id <parent-sid>` to any session-creating CLI). Do NOT spawn your own session. The new `peaks session info --active` reads the canonical binding for you.
-- **Skill presence (MANDATORY first action)** — do NOT call `peaks skill presence:set peaks-qa`. The sub-agent must not overwrite `.peaks/.active-skill.json`; the main Solo loop owns that file. If you need to mark your own state, write a marker file at `.peaks/_runtime/<sessionId>/system/sub-agent-qa.json` and only that.
-- **Workspace initialization** — Solo has already run `peaks workspace init` before fan-out. Do not re-run it.
-- **Mode selection** — Solo has already chosen the mode.
-- **Statusline install** — already done by Solo at session startup.
+- **Skill presence (MANDATORY first action)** — do NOT call `peaks skill presence:set peaks-qa`. The sub-agent must not overwrite `.peaks/.active-skill.json`; the main Code loop owns that file. If you need to mark your own state, write a marker file at `.peaks/_runtime/<sessionId>/system/sub-agent-qa.json` and only that.
+- **Workspace initialization** — Code has already run `peaks workspace init` before fan-out. Do not re-run it.
+- **Mode selection** — Code has already chosen the mode.
+- **Statusline install** — already done by Code at session startup.
 
 What the sub-agent **MUST** still do:
 
-0. **Do NOT call `peaks request init`** — Solo has already initialised the request artefact slot in the main loop before fan-out. The sub-agent reads it via `peaks request show <rid> --role qa --project <repo> --json` if it needs to.
+0. **Do NOT call `peaks request init`** — Code has already initialised the request artefact slot in the main loop before fan-out. The sub-agent reads it via `peaks request show <rid> --role qa --project <repo> --json` if it needs to.
 2. `peaks request show <rid> --role prd --project <repo> --json` (and `--role rd`, `--role ui` if UI is in the swarm plan).
 3. Standards preflight (dry-run only).
 4. Write `.peaks/_runtime/<sessionId>/qa/test-cases/<rid>.md` with test cases that link to PRD acceptance items.
@@ -30,7 +30,7 @@ What the sub-agent **MUST** still do:
 **Hard prohibitions** (sub-agent context):
 
 - Do NOT call `Skill(skill="...")`.
-- Do NOT call `peaks skill presence:set` — Solo owns the active-skill file.
+- Do NOT call `peaks skill presence:set` — Code owns the active-skill file.
 - Do NOT run the actual test suite, do NOT execute security/perf tools, do NOT open a browser — those are the **QA validation** phase, not the Swarm planning phase.
 - Do NOT commit, push, install hooks, or apply settings.json mutations.
 - Do NOT ask the user interactive questions. If you need clarification, return `{"status":"blocked","blockedReason":"<text>"}`.

package/skills/bee/peaks-rd/references/rd-fanout-contracts.md

@@ -73,7 +73,7 @@ end of implementation, RD fires 3 sub-agents in parallel via
   conversation context. They MUST NOT mutate parent settings
   (`peaks skill presence:set`, hooks install, `.claude/settings.json`).
 - Sub-agents MUST NOT call `peaks workflow verify-pipeline` — that is
-  Solo's responsibility.
+  Code's responsibility.
 - Sub-agents MUST NOT modify the request artifact body — they only
   write their respective review artifact.
 - Sub-agents MUST NOT install or persist external material (no

package/skills/bee/peaks-rd/references/rd-runbook.md

@@ -28,7 +28,7 @@ peaks understand show   --project <repo> --json                # when UA artifac
 peaks codegraph context --project <repo> "<task>"
 peaks codegraph affected --project <repo> <changed-files...> --json
 
-# 4.1 read project-scan from Solo's pre-RD scan — BLOCKING if missing
+# 4.1 read project-scan from Code's pre-RD scan — BLOCKING if missing
 # **STOP if .peaks/_runtime/<sessionId>/rd/project-scan.md does not exist.**
 # **Do not write any code, do not plan any implementation, do not pass go.**
 # **Create the project-scan first, then proceed.**

package/skills/bee/peaks-rd/references/rd-sub-agent-dispatch.md

@@ -37,21 +37,21 @@
 > design — if either changes, update the other.
 
 - **Session id** — use the parent's sid (read `.peaks/_runtime/session.json` or pass `--session-id <parent-sid>` to any session-creating CLI). Do NOT spawn your own session. The new `peaks session info --active` reads the canonical binding for you.
-- **Skill presence (MANDATORY first action)** — do NOT call `peaks skill presence:set peaks-rd`. The sub-agent must not overwrite `.peaks/.active-skill.json`; the main Solo loop owns that file. If you need to mark your own state, write a marker file at `.peaks/_runtime/<sessionId>/system/sub-agent-rd.json` and only that.
-- **Workspace initialization** — Solo has already run `peaks workspace init` before fan-out. Do not re-run it.
-- **Mode selection** — Solo has already chosen the mode. Read it from the prompt arguments (or from `.peaks/.active-skill.json` if you can, but do not write it).
-- **Statusline install** — already done by Solo at session startup; do not re-run.
+- **Skill presence (MANDATORY first action)** — do NOT call `peaks skill presence:set peaks-rd`. The sub-agent must not overwrite `.peaks/.active-skill.json`; the main Code loop owns that file. If you need to mark your own state, write a marker file at `.peaks/_runtime/<sessionId>/system/sub-agent-rd.json` and only that.
+- **Workspace initialization** — Code has already run `peaks workspace init` before fan-out. Do not re-run it.
+- **Mode selection** — Code has already chosen the mode. Read it from the prompt arguments (or from `.peaks/.active-skill.json` if you can, but do not write it).
+- **Statusline install** — already done by Code at session startup; do not re-run.
 
 What the sub-agent **MUST** still do, from this skill's contract:
 
-0. **Do NOT call `peaks request init`** — Solo has already initialised the request artefact slot in the main loop before fan-out (the runbook has the exact `peaks request init --role rd --id <rid> --project <repo> --apply --type <type> --json` call). The sub-agent reads the slot via `peaks request show <rid> --role rd --project <repo> --json` if it needs to. Note: `peaks request init` is **dry-run by default**. Pass `--apply` to actually create the artifact.
+0. **Do NOT call `peaks request init`** — Code has already initialised the request artefact slot in the main loop before fan-out (the runbook has the exact `peaks request init --role rd --id <rid> --project <repo> --apply --type <type> --json` call). The sub-agent reads the slot via `peaks request show <rid> --role rd --project <repo> --json` if it needs to. Note: `peaks request init` is **dry-run by default**. Pass `--apply` to actually create the artifact.
 2. `peaks request show <rid> --role prd --project <repo> --json` (and `--role ui` if UI is in the swarm plan).
-3. Standards preflight (dry-run only; Solo owns the apply step).
-4. Project-scan read; create `rd/project-scan.md` only if Solo flagged it missing in the dispatch prompt.
+3. Standards preflight (dry-run only; Code owns the apply step).
+4. Project-scan read; create `rd/project-scan.md` only if Code flagged it missing in the dispatch prompt.
 5. Write the planning artefact: `rd/requests/<rid>.md` (feature/refactor, per the `artifact-per-request.md` contract) or `rd/bug-analysis.md` (bugfix). If `--type` is `config|docs|chore`, **no planning artefact is required** — return immediately with `{"role":"rd-planning","status":"skipped","reason":"type=<type>"}`.
 
    > **v2.11.0 change (Group A):** `rd/tech-doc.md` is removed. The per-slice planning record is the per-request artefact at `rd/requests/<rid>.md`; the slice's source-of-truth architecture is the immutable peaks-prd handoff at `prd/handoff.md` (verify handoff hash = `<dispatched value>` before reading).
-6. Return only a compact JSON envelope — Solo will run the convergence gate (`ls` checks):
+6. Return only a compact JSON envelope — Code will run the convergence gate (`ls` checks):
 
 ```json
 {
@@ -67,12 +67,12 @@ What the sub-agent **MUST** still do, from this skill's contract:
 **Hard prohibitions** (sub-agent context, in addition to general red lines):
 
 - Do NOT call `Skill(skill="...")` from inside the sub-agent — that defeats the fan-out.
-- Do NOT call `peaks skill presence:set` — Solo owns the active-skill file.
+- Do NOT call `peaks skill presence:set` — Code owns the active-skill file.
 - Do NOT commit, push, install hooks, or apply settings.json mutations.
-- Do NOT ask the user interactive questions. If you need clarification, return `{"status":"blocked","blockedReason":"<text>"}` and let Solo handle the user message.
+- Do NOT ask the user interactive questions. If you need clarification, return `{"status":"blocked","blockedReason":"<text>"}` and let Code handle the user message.
 - Do NOT modify code (the Swarm phase is planning only; code edits happen in the RD implementation phase, which is a separate sub-agent or inline run after Gate B).
 
-After returning, Solo re-checks Gate B (`ls .peaks/_runtime/<sessionId>/rd/requests/<rid>.md` etc.) and proceeds to RD implementation, which is a different sub-agent or inline run.
+After returning, Code re-checks Gate B (`ls .peaks/_runtime/<sessionId>/rd/requests/<rid>.md` etc.) and proceeds to RD implementation, which is a different sub-agent or inline run.
 
 ## Test Tool Detection (mandatory)
 

package/skills/bee/peaks-rd/references/rd-transition-gates.md

@@ -104,7 +104,7 @@ peaks scan request-type-sanity --project <repo> --type <type> --json
 peaks request repair-status <rid> --project <repo> --session-id <session-id> --json
 # Expected: atCap=false. exit 0.
 # atCap=true → BLOCKED. Three repair cycles already attempted; emit a blocked TXT
-# handoff via Solo rather than entering a fourth cycle.
+# handoff via Code rather than entering a fourth cycle.
 ```
 
 **Peaks-Loop Gate B8 — Diff stays inside the declared red-line scope:**

package/skills/bee/peaks-sc/SKILL.md

@@ -61,7 +61,7 @@ Every SC invocation must write a change-control record at `.peaks/_runtime/<sess
 - validation result (`peaks sc validate` output);
 - boundary record (`peaks sc boundary` output).
 
-Solo reads this record before declaring the workflow complete.
+Code reads this record before declaring the workflow complete.
 
 ## Refactor role
 

package/skills/bee/peaks-txt/SKILL.md

@@ -21,7 +21,7 @@ Before any analysis or tool call, immediately run:
 peaks skill presence:set peaks-txt --project <repo> --mode <mode> --gate startup
 ```
 
-**When invoked as a sub-agent (peaks-code swarm):** do NOT call `peaks skill presence:set` (Solo owns the active-skill marker) and do NOT spawn your own session. Use the parent's sid — read `.peaks/_runtime/session.json` or pass `--session-id <parent-sid>` to any session-creating CLI. The new `peaks session info --active` reads the canonical binding for you.
+**When invoked as a sub-agent (peaks-code swarm):** do NOT call `peaks skill presence:set` (Code owns the active-skill marker) and do NOT spawn your own session. Use the parent's sid — read `.peaks/_runtime/session.json` or pass `--session-id <parent-sid>` to any session-creating CLI. The new `peaks session info --active` reads the canonical binding for you.
 
 On the first presence:set in a project, ensure the out-of-band status bar is installed so the user can see at a glance that Peaks is orchestrating — it renders the active skill in Claude Code's terminal status line, independent of model output:
 
@@ -68,7 +68,7 @@ When used alone or when a workflow needs portable artifacts that must survive se
 
 ```markdown
 ## Handoff: <request-id>
-- **Mode:** solo | assisted | swarm | strict
+- **Mode:** code | assisted | swarm | strict
 - **Status:** complete | blocked | return-to-rd
 - **Artifacts:**
   - PRD: .peaks/_runtime/<sessionId>/prd/requests/<rid>.md
@@ -114,7 +114,7 @@ Each entry should include:
 - lesson or rule;
 - why it exists;
 - affected skills;
-- how future PRD/RD/UI/QA/SC/Solo workflows should apply it;
+- how future PRD/RD/UI/QA/SC/Code workflows should apply it;
 - whether it is stable enough for `.peaks/memory` extraction.
 
 ## Project memory guidance

package/skills/bee/peaks-ui/SKILL.md

@@ -37,14 +37,14 @@ UI inherits `peaks-qa`'s hard-block contract: `AskUserQuestion` with three optio
 When this skill is launched as a sub-agent via `peaks sub-agent dispatch <role>` from `peaks-code`, these sections are **suspended** for the sub-agent run:
 
 - **Session id** — use parent's sid (`.peaks/_runtime/session.json` or `--session-id <parent-sid>`). Do NOT spawn your own session; `peaks session info --active` reads the canonical binding.
-- **Skill presence** — do NOT call `peaks skill presence:set peaks-ui`; Solo owns `.peaks/.active-skill.json`. Marker file at `.peaks/_runtime/<session-id>/system/sub-agent-ui.json` only.
-- **Workspace initialization** — Solo ran `peaks workspace init` before fan-out; do not re-run.
-- **Mode selection** — Solo chose the mode.
-- **Statusline install** — done by Solo at startup.
+- **Skill presence** — do NOT call `peaks skill presence:set peaks-ui`; Code owns `.peaks/.active-skill.json`. Marker file at `.peaks/_runtime/<session-id>/system/sub-agent-ui.json` only.
+- **Workspace initialization** — Code ran `peaks workspace init` before fan-out; do not re-run.
+- **Mode selection** — Code chose the mode.
+- **Statusline install** — done by Code at startup.
 
 What the sub-agent **MUST** still do:
 
-1. **Do NOT call `peaks request init`** — Solo already initialised the slot. Read via `peaks request show <rid> --role ui --project <repo> --json` if needed.
+1. **Do NOT call `peaks request init`** — Code already initialised the slot. Read via `peaks request show <rid> --role ui --project <repo> --json` if needed.
 2. Read PRD scope via `peaks request show <rid> --role prd --project <repo> --json`.
 3. Read `rd/project-scan.md` for component library / CSS framework / design-system context.
 4. Run the prototype fidelity check (Figma / PRD visuals / headed browser).
@@ -65,13 +65,13 @@ What the sub-agent **MUST** still do:
 **Hard prohibitions** (sub-agent context):
 
 - Do NOT call `Skill(skill="...")`.
-- Do NOT call `peaks skill presence:set` — Solo owns active-skill.
+- Do NOT call `peaks skill presence:set` — Code owns active-skill.
 - Do NOT modify application code. UI is design-direction only.
-- Do NOT install MCP servers. If Playwright MCP is missing and headed browser is required, return `{"status":"blocked","blockedReason":"playwright-mcp-unavailable"}` for Solo escalation. (peaks-loop no longer manages MCP install — user runs `claude mcp add playwright -- npx @playwright/mcp@latest` in Claude Code.)
+- Do NOT install MCP servers. If Playwright MCP is missing and headed browser is required, return `{"status":"blocked","blockedReason":"playwright-mcp-unavailable"}` for Code escalation. (peaks-loop no longer manages MCP install — user runs `claude mcp add playwright -- npx @playwright/mcp@latest` in Claude Code.)
 - Do NOT commit, push, install hooks, or apply settings.json mutations.
 - Do NOT ask user questions; return `{"status":"blocked","blockedReason":"<text>"}` if blocked.
 
-If the request does not affect user-visible behavior (no frontend keyword hit, `frontendOnly=false`), the swarm plan should not include UI at all — Solo will not launch this sub-agent. But if it does launch you and you determine the work is non-visual, return `{"status":"skipped","reason":"non-frontend-request"}` so Solo can record the misfire.
+If the request does not affect user-visible behavior (no frontend keyword hit, `frontendOnly=false`), the swarm plan should not include UI at all — Code will not launch this sub-agent. But if it does launch you and you determine the work is non-visual, return `{"status":"skipped","reason":"non-frontend-request"}` so Code can record the misfire.
 
 ## Skill presence (MANDATORY first action — main-loop context only)