@sublang/playbook 17.10.1 → 17.11.0

package/docs/configuration.md

@@ -304,6 +304,22 @@ files, so keep their locations available for resumed runs. Ordinary Captain
 routing, judging and replies receive `skills: []`; bounded recovery preparation
 can use the Captain's configured skills.
 
+Agents also find skills by themselves in their project and user skill folders,
+such as `.claude/skills` and `.agents/skills`. Captain routing, judging and
+replies turn that discovery off as far as the agent allows, so a skill
+installed there no longer steers them; what an agent keeps regardless stays,
+such as OpenCode's configuration-directory skills and plugin or extension
+skills. Kimi Code has no switch for this, so a Kimi Captain still reads those
+folders. Working players and recovery preparation keep them.
+
+A session whose Captain conversation began before Captain control turned this
+discovery off, with the Playbook release that requires Cligent 0.36.0, keeps the
+skill listings already in that conversation; start a new session for full
+isolation. A Captain whose agent offers the switch but cannot apply it where it
+runs now fails its control calls with an error, for example a Gemini CLI Captain
+under its native sandbox or run from the home directory, or a Codex Captain with
+an unreadable skill root.
+
 ## Browser capability
 
 A Captain or player agent block may set `browser: true` to make Cligent's managed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sublang/playbook",
-  "version": "17.10.1",
+  "version": "17.11.0",
   "type": "module",
   "description": "Composable XState v5 playbook runtime with compiled Captain, CODE, REVIEW, DECIDE, DEV, BRANCH, PR, and INSPECT workflows driven by GEARS specs.",
   "license": "Apache-2.0",
@@ -280,7 +280,7 @@
     "provenance": true
   },
   "dependencies": {
-    "@sublang/cligent": "^0.34.0",
+    "@sublang/cligent": "^0.36.0",
     "@sublang/spex": "^3.0.0",
     "p-queue": "^9.3.1",
     "xstate": "^5.19.4",

package/reference/sdlc/code.md

@@ -91,7 +91,6 @@ Every new-intent phase has two semantic outcomes: direct implementation and new
 Every IR-task phase, including the first phase for an existing IR, identifies the IR and the implemented task, and has two semantic outcomes: more tasks and final task.
 The first phase therefore has four semantic outcomes — direct implementation, new IR, more tasks, and final task — plus the Boss question when the continued IR is ambiguous.
 Each semantic outcome requires affirmative support in Coder's result, but no phase transition shall depend on a fixed presentation format of Coder's reply.
-The Boss-question outcome means that, at the end of this call, Coder has an unanswered clarifying question for Boss whose answer is required to complete the current coding phase. Earlier interim questions resolved or superseded by later affirmative current-phase completion, and prerequisites only for later review, acceptance or release stages, do not establish this outcome.
 A commit statement alone does not establish semantic completion, and contradictory or insufficient evidence supports no forced commit outcome.
 Captain shall use the repository-effect receipt as the authoritative identity of the phase's new commit.
 

package/reference/sdlc/code.playbook/code.fsm.js

@@ -84,7 +84,7 @@ const REVIEW_IR_TASK_PHASE_TEMPLATE = [
     '',
     '> Current IR task: <ir-task>',
 ].join('\n');
-const NEEDS_BOSS_REPLY_DESCRIPTION = "At the end of this call, Coder has an unanswered clarifying question for Boss whose answer is required to complete the current coding phase. Earlier interim questions resolved or superseded by later affirmative current-phase completion, and prerequisites only for later review, acceptance or release stages, do not establish this outcome. Output shall include `question: <verbatim question text from the acting agent's prose>`.";
+const NEEDS_BOSS_REPLY_DESCRIPTION = "The acting agent's prose surfaces a clarifying question for Boss that the agent cannot answer alone. Output shall include `question: <verbatim question text from the acting agent's prose>`.";
 const FIRST_PHASE_RESULT = {
     directCommit: "Coder completed the new coding intent as one direct implementation phase and made its one new commit; Coder's result affirmatively supports this outcome, and no fixed presentation format of the reply is required. Output shall include `coderOutput: <verbatim final text>` and `latestCommit: <commit identity>`.",
     irCommit: "Coder decomposed the new coding intent into a new IR, implemented no IR task, and made its one new commit; Coder's result affirmatively supports this outcome, and no fixed presentation format of the reply is required. Output shall include `coderOutput: <verbatim final text>`, `latestCommit: <commit identity>`, and `irNumber` identifying the created IR.",

package/reference/sdlc/code.playbook/code.fsm.ts

@@ -326,7 +326,7 @@ const REVIEW_IR_TASK_PHASE_TEMPLATE = [
 ].join('\n');
 
 const NEEDS_BOSS_REPLY_DESCRIPTION =
-  "At the end of this call, Coder has an unanswered clarifying question for Boss whose answer is required to complete the current coding phase. Earlier interim questions resolved or superseded by later affirmative current-phase completion, and prerequisites only for later review, acceptance or release stages, do not establish this outcome. Output shall include `question: <verbatim question text from the acting agent's prose>`.";
+  "The acting agent's prose surfaces a clarifying question for Boss that the agent cannot answer alone. Output shall include `question: <verbatim question text from the acting agent's prose>`.";
 
 const FIRST_PHASE_RESULT = {
   directCommit:

package/reference/sdlc/code.playbook/playbook-captain.js

@@ -5,6 +5,7 @@ import { posix, win32 } from 'node:path';
 import { isDeepStrictEqual } from 'node:util';
 import PQueue from 'p-queue';
 import { isAgentCallSettingsError, } from '@sublang/cligent/tmux-play';
+import { getNativeSkillSupport } from '@sublang/cligent';
 import { assertPlaybookFailureCause } from '@sublang/playbook/runtime';
 import { assertPlaybookRuntimeSnapshot, assertPlaybookEffectLedger, emptyPlaybookEffectLedger, hiddenControlEnvelope, isPlaybookEffectLedgerMonotonicExtension, normalizeError, parseJudgeJson, registerPlaybookAbortCleanup, snapshotJsonValue, validatePlayerResult, } from '../../../src/xstate-runtime.js';
 import createDefaultCaptainRuntime from '../captain.playbook/captain.playbook.js';
@@ -2395,7 +2396,23 @@ function callSettings(agent, tuning = agent) {
     };
 }
 function controlCallSettings(agent) {
-    return { ...callSettings(agent), browser: false, skills: [], mcpServers: {} };
+    return {
+        ...callSettings(agent),
+        browser: false,
+        skills: [],
+        mcpServers: {},
+        ...controlNativeSkills(agent.adapter),
+    };
+}
+// The native-skill half of a decision, Judge or reporting call's settings
+// (playbook-captain-88). Only an adapter Cligent reports can honor the switch
+// is asked to; tmux-play rejects `false` for any other, so a Kimi Captain
+// keeps its runtime's own skills rather than failing every control call
+// (DR-093). Working calls never carry it.
+function controlNativeSkills(adapter) {
+    return getNativeSkillSupport(adapter)?.disableSupported === true
+        ? { nativeSkills: false }
+        : {};
 }
 function promptIdentity(binding) {
     return binding.model.kind === 'value'

package/reference/sdlc/code.playbook/playbook-captain.ts

@@ -16,6 +16,7 @@ import {
   type PlayerAdapterName,
   type TuningSelection,
 } from '@sublang/cligent/tmux-play';
+import { getNativeSkillSupport } from '@sublang/cligent';
 import type { Effort, PermissionPolicy } from '@sublang/cligent';
 import type {
   JsonValue,
@@ -4173,7 +4174,24 @@ function callSettings(
 }
 
 function controlCallSettings(agent: SessionAgent): AgentCallSettings {
-  return { ...callSettings(agent), browser: false, skills: [], mcpServers: {} };
+  return {
+    ...callSettings(agent),
+    browser: false,
+    skills: [],
+    mcpServers: {},
+    ...controlNativeSkills(agent.adapter),
+  };
+}
+
+// The native-skill half of a decision, Judge or reporting call's settings
+// (playbook-captain-88). Only an adapter Cligent reports can honor the switch
+// is asked to; tmux-play rejects `false` for any other, so a Kimi Captain
+// keeps its runtime's own skills rather than failing every control call
+// (DR-093). Working calls never carry it.
+function controlNativeSkills(adapter: string): { nativeSkills?: false } {
+  return getNativeSkillSupport(adapter)?.disableSupported === true
+    ? { nativeSkills: false }
+    : {};
 }
 
 function promptIdentity(binding: EffectivePlayerBinding): string {

package/slc/text2gears.md

@@ -229,7 +229,7 @@ The annotation makes the field runtime-owned: the adjudicator selects the result
 A distinct typed field extracted from that response remains judge-authored even when a later prompt quotes its exact value; quoting a field does not turn it into the player's whole final response.
 One property name shall not be annotated as verbatim in one result contract and judge-authored in another; text2gears shall choose distinct properties or report that the Source cannot be represented by the current contract.
 
-A Source statement that qualifies an outcome's evidence — what affirmatively
+A Source statement that qualifies an authored domain outcome's evidence — what affirmatively
 supports it, what supports no outcome, such as "a progress report, status
 update, or promise of a later result supports no review outcome" — shall be
 carried in that outcome's result description, the only text the adjudicator
@@ -244,7 +244,10 @@ explicitly requires the acting agent to show that machine syntax to the user.
 It shall move Source's outcome contract into `Results:` while preserving the
 human domain instructions in the blockquote.
 It shall not emit the framework-owned `needsBossReply` result; gears2fsm adds
-that universal result for every Captain- or player-invoking state.
+that universal result with its standard description for every Captain- or player-invoking state.
+The framework-owned question is interpreted under the runtime's current-call
+adjudication rule; it is not an authored domain outcome whose description
+Source overrides.
 
 Where Source restricts an initial Captain to routing, text2gears shall preserve
 only the authored question and delegation outcomes and shall not infer a
@@ -255,7 +258,7 @@ outcome Source leaves unqualified carries no `Results:` label; downstream,
 [gears2fsm](gears2fsm.md#setup) gives its state the default single-outcome
 contract, so text2gears shall not invent a one-bullet `Results:` block for it.
 When a later item does consume its output, the produced-value rule above
-applies instead; when Source qualifies the one outcome's evidence — what
+applies instead; when Source qualifies the one authored domain outcome's evidence — what
 affirmatively supports it, what supports no outcome — the behavior carries
 exactly one `Results:` bullet naming that outcome and carrying the
 qualification, with an output property only where a consumer requires one,