@gobing-ai/knowledge-kit 0.0.29 → 0.0.30

package/plugins/kk/workflows/kk-daily-ai-voice.yaml

@@ -113,6 +113,17 @@ vars:
   qc_min_importance: "3"
   qc_min_urgency: "2"
   qc_min_impact: "1"
+  # 20261002 episode floor: a weak, policy-heavy day filtered to 5 QC-kept docs and the prompt-layer
+  # 选题边界 dropped 2 more at script-write → a 5-minute episode. Below this count, importance-only
+  # rejects (quality/urgency/impact still hard) backfill the plan; floor is 8 because the script-layer
+  # drops land AFTER this gate (lossy upstream compensation). Moves in lockstep with
+  # DEFAULT_FILTER_CONFIG.minEpisodeItems (env wins).
+  qc_min_episode_items: "8"
+  # Standing requirement (20261002, operator): episodes run 15–20 minutes; duration is
+  # authoritative and the 8–10-item figure is only an estimate. Enforced by the
+  # episode-duration stage after intro-music (fail loud outside the window).
+  episode_min_minutes: "15"
+  episode_max_minutes: "20"
   __hitlAnswer: ""
 
 states:
@@ -169,7 +180,7 @@ states:
       - kind: shell
         options:
           command: >-
-            kk stage daily-qc-content "${vars.work_dir}" "${vars.run_date}" "${vars.plugins_path}" "${vars.qc_categories}" "${vars.qc_min_quality}" "${vars.qc_min_importance}" "${vars.qc_min_urgency}" "${vars.qc_min_impact}"
+            kk stage daily-qc-content "${vars.work_dir}" "${vars.run_date}" "${vars.plugins_path}" "${vars.qc_categories}" "${vars.qc_min_quality}" "${vars.qc_min_importance}" "${vars.qc_min_urgency}" "${vars.qc_min_impact}" "${vars.qc_min_episode_items}"
 
   - id: plan-translate
     description: "Translate needsTranslation plan items into the output plan.json via agent.run"
@@ -181,11 +192,11 @@ states:
           # ADR-115 error tier: keep this prompt <= 1000 chars (0133 R3; 0138 R4a adds the copy discipline).
           input: |
             Read ${vars.work_dir}/21-plan/${vars.run_date}_04_quality-control-content_candidates.json — metadata.docs (Doc[]) is the plan; don't edit it.
-            For items with needsTranslation, translate "title", "body", and "metadata.brief" (when present) into natural simplified Chinese.
-            Titles read as a news event (subject + action + object) — e.g. "OpenAI 发布 Sora 应用，集成 Sora 2 模型". Keep product/model/company names verbatim, preserve body URLs, use 「」 not ASCII double quotes.
+            For needsTranslation items, adapt "title", "body" and "metadata.brief" into spoken simplified Chinese — full coverage, not a summary: keep every fact, number, name, quote and hedge (口播全长改编，不摘要不省略), body ≈0.6–0.7× the source.
+            Titles read as a news event; keep product/model names verbatim, preserve body URLs, use 「」 not ASCII double quotes.
             Copy discipline: reader-facing news copy — no scaffold labels (「可做角度」「为什么现在值得注意」「社区讨论」「背景」「潜在影响」「影响」), no duplicated labels or hedging (「读者宜另行核实」「仍待验证」) — merge their substance into prose or drop.
-            Keep other fields (id, sourceUri, mediaType, metadata), technical terms as-is; no trailing commas or comments.
-            Output strictly valid JSON — a same-length, same-order array with the same ids — to ${vars.work_dir}/21-plan/${vars.run_date}_03_plan_plan.json.
+            Keep other fields (id, sourceUri, mediaType, metadata) as-is; no comments or trailing commas.
+            Output strictly valid JSON — a same-length, same-order array — to ${vars.work_dir}/21-plan/${vars.run_date}_03_plan_plan.json.
           expectFile: ${vars.work_dir}/21-plan/${vars.run_date}_03_plan_plan.json
           allowAppend: false
 
@@ -201,8 +212,8 @@ states:
           input: |
             Read ${vars.work_dir}/21-plan/${vars.run_date}_03_plan_plan.json — metadata.docs (Doc[]) is the translated plan; don't edit it.
             Write a tech-sharing prose article in natural simplified Chinese for the 「AI 乱炖」 column (show 「咸话咸说」， tools/papers/hands-on practice 随聊): no title line (the pipeline computes it), an intro paragraph (2–3 sentences), then one section per item (## numbered title, 2–4 sentences of flowing prose, source link [来源：<label>](<sourceUri>) inline), a closing paragraph tying items together.
-            选题边界：只写技术内容；某条主线若属政治/外交或贸易管制/军事/公共政策争议/社会公共事件，跳过该条并在文末加一行「> 注：<N> 条条目因选题边界未写入」。
-            事实纪律：每个事实取自该条计划内容，不虚构、不引他处；模型/产品名与 URL 照抄；某条材料不足就少写或不写，不凑数。
+            选题边界：只写技术内容；某条主线若属政治/外交或贸易管制/军事/公共政策争议/社会公共事件，跳过该条并在文末加一行「> 注：<N> 条条目因选题边界未写入：<id>（<原因>）、<id>（<原因>）」。
+            事实纪律：每个事实取自该条计划内容，不虚构、不引他处；数字与主体不得放大（如 16 张卡不得写成「几十张卡」，具名主体不得写成「顶级大厂」）；引语只能归属其原句主语；保留「据报道/称/承诺」等限定词；导语/收束不加计划外程度词（如「稳定解决」「高维」「治理」）；材料不足就少写或不写，不凑数。
             Narrative register — smooth transitions, no list-like bulleting, no scaffold labels (「可做角度」「背景」「潜在影响」), no hedging (「读者宜另行核实」「仍待验证」). 「」 quotes.
             Output the markdown to ${vars.work_dir}/22-article/${vars.run_date}_06_article-write_body.md.
           expectFile: ${vars.work_dir}/22-article/${vars.run_date}_06_article-write_body.md
@@ -229,7 +240,7 @@ states:
           # ADR-115 error tier: keep this prompt <= 1000 chars.
           input: |
             Read ${vars.work_dir}/21-plan/${vars.run_date}_03_plan_plan.json — a JSON array of plan docs; don't edit it.
-            Take item 1 only (its "title" and "metadata.brief") — the episode's lead story.
+            Take item 1 only (its "title" and "metadata.brief") — the episode's lead story. If item 1's mainline is public affairs (politics/diplomacy, trade controls, military, policy disputes, social events), take the first in-scope item instead.
             Write one concrete visual scene in English, ≤240 characters, that a viewer would connect to that story: objects, settings, symbols, metaphor.
             No text, letters, numbers, logos, brand marks, flags, or recognizable real people. No style, color, lighting, or composition words — the preset owns those.
             Output strictly valid JSON {"subject": "..."} to ${vars.work_dir}/23-cover/${vars.run_date}_07_cover-brief.json.
@@ -264,10 +275,10 @@ states:
           agent: ${vars.agent}
           # ADR-115 error tier: keep this prompt <= 1000 chars.
           input: |
-            Read ${vars.work_dir}/21-plan/${vars.run_date}_03_plan_plan.json — a JSON array of docs; use each doc's `id`; don't edit it. Also read the style contract ${vars.work_dir}/24-script/${vars.run_date}_08_script-write_style.md and obey its char caps and banned phrases.
-            For each doc write a `lead` (a spoken bridge into the title, not containing it) and an `insight` (why it matters, grounded only in that doc's facts).
-            Write an `intro` hooking today's actual themes and an `outro`; no greeting or sign-off — the builder adds both. 选题边界：只写技术内容；公共事务主线（政治/外交贸易管制/军事/政策争议/社会事件）不出现。
-            Output only the JSON object {"version":1,"intro":"…","outro":"…","items":[{"id":"…","lead":"…","insight":"…"}]} with one item per doc id to ${vars.work_dir}/24-script/${vars.run_date}_08_script-write_plan.json.
+            Read ${vars.work_dir}/21-plan/${vars.run_date}_03_plan_plan.json — a JSON array of docs; don't edit it. Also read the style contract ${vars.work_dir}/24-script/${vars.run_date}_08_script-write_style.md and obey its char caps, duration budget and banned phrases.
+            For each doc write a `lead` (a spoken bridge, not containing the title) and an `insight` (grounded only in that doc's facts: keep its numbers and hedges（据报道）, add no new degree words like「高预算穷举」).
+            intro/outro hook only in-scope items; no greeting or sign-off — the builder adds both. 选题边界：政治/外交、贸易管制、军事、公共政策争议、社会公共事件条目绝不复述；读文章 22-article/*_06_article-write_body.md，其文末注记点名的 id 一并进 excluded，各配中文原因。
+            Output only JSON {"version":1,"intro":"…","outro":"…","items":[{"id":"…","lead":"…","insight":"…"}],"excluded":[{"id":"…","reason":"…"}]} to ${vars.work_dir}/24-script/${vars.run_date}_08_script-write_plan.json. Exactly one `items` entry per doc not in `excluded`.
           expectFile: ${vars.work_dir}/24-script/${vars.run_date}_08_script-write_plan.json
           allowAppend: false
 
@@ -356,6 +367,14 @@ states:
           command: >-
             kk stage daily-intro "${vars.work_dir}" "${vars.run_date}" "${vars.intro_music}"
 
+  - id: episode-duration
+    description: "Fail loud unless final episode duration sits in the 15–20 min window (duration authoritative)"
+    onEnter:
+      - kind: shell
+        options:
+          command: >-
+            kk stage daily-episode-duration "${vars.work_dir}" "${vars.run_date}" "${vars.episode_min_minutes}" "${vars.episode_max_minutes}"
+
   - id: quality-control
     description: "Verify audio quality, speech rate, and silence/repetition QC metrics"
     onEnter:
@@ -423,7 +442,7 @@ states:
             kk stage daily-xhs-render "${vars.work_dir}" "${vars.run_date}" "${vars.plugins_path}" "${vars.xhs_cards}" "${vars.xhs_style}" "${vars.xhs_provider}" "${vars.xhs_model}"
 
   - id: xhs-publish
-    description: "Publish the packaged card series to XHS — draft, or live only when xhs_live=true (ADR-022); independent and non-blocking: its outcome never enters publish_status. xhs-pub itself enforces a headless session preflight and a 24h publish/check cap (ADR-025), so a sessionless or capped run fails soft with a named reason and the run continues"
+    description: "Publish the packaged card series to XHS — draft, or live only when xhs_live=true (ADR-022); independent and non-blocking: its outcome never enters publish_status. xhs-pub itself enforces a headless session preflight and a 2h publish/check cap (ADR-025), so a sessionless or capped run fails soft with a named reason and the run continues"
     onEnter:
       - kind: shell
         onError: continue
@@ -715,8 +734,14 @@ transitions:
       kind: always
 
   - from: intro-music
+    to: episode-duration
+    description: "Intro merged -> gate final episode duration (15–20 min, standing requirement)"
+    guard:
+      kind: always
+
+  - from: episode-duration
     to: quality-control
-    description: "Intro merged -> run quality control validation"
+    description: "Duration within window -> run quality control validation"
     guard:
       kind: always
 

package/plugins/kk/workflows/kk-itc.yaml

@@ -503,27 +503,38 @@ transitions:
 
   - from: judge
     to: done
-    description: "Interactive mode, verdict PASS (or empty in dry-run), no publish targets -> complete workflow"
+    description: "Interactive mode, verdict PASS with a valid confidence (or empty in dry-run), no publish targets -> complete workflow"
     guard:
       kind: shell
       options:
-        command: '{ test "${vars.auto}" != "true"; } && { v="$(jq -r .verdict ${vars.work_dir}/.itc-verdict.json 2>/dev/null)"; test -z "$v" -o "$v" = PASS; } && test -z "${vars.publish_targets}"'
+        command: >-
+          { test "${vars.auto}" != "true"; } &&
+          { v="$(jq -r 'if (.verdict // "") == "PASS" then (.verdict + (if ((.confidence // "") | test("^(HIGH|MEDIUM|LOW)$")) then "" else "!" end)) else (.verdict // "") end' ${vars.work_dir}/.itc-verdict.json 2>/dev/null)";
+          test -z "$v" -o "$v" = PASS; } &&
+          test -z "${vars.publish_targets}"
 
   - from: judge
     to: publish-entry
-    description: "Verdict PASS with targets set -> enter the publish tail (auto runs report after the tail)"
+    description: "Verdict PASS with a valid confidence and targets set -> enter the publish tail (auto runs report after the tail)"
     guard:
       kind: shell
       options:
-        command: '{ v="$(jq -r .verdict ${vars.work_dir}/.itc-verdict.json 2>/dev/null)"; test -z "$v" -o "$v" = PASS; } && test -n "${vars.publish_targets}"'
+        command: >-
+          { v="$(jq -r 'if (.verdict // "") == "PASS" then (.verdict + (if ((.confidence // "") | test("^(HIGH|MEDIUM|LOW)$")) then "" else "!" end)) else (.verdict // "") end' ${vars.work_dir}/.itc-verdict.json 2>/dev/null)";
+          test -z "$v" -o "$v" = PASS; } &&
+          test -n "${vars.publish_targets}"
 
   - from: judge
     to: report
-    description: "Auto mode -> the run ends in the report (PASS without targets, FAIL, or exhausted NEEDS_REVISION)"
+    description: "Auto mode -> the run ends in the report (valid PASS without targets, FAIL, or exhausted NEEDS_REVISION)"
     guard:
       kind: shell
       options:
-        command: '{ test "${vars.auto}" = "true"; } && { v="$(jq -r .verdict ${vars.work_dir}/.itc-verdict.json 2>/dev/null)"; c="$(cat "${vars.work_dir}/.auto-revise-count" 2>/dev/null || echo 0)"; { test -z "$v" -o "$v" = PASS; } || test "$v" = FAIL || { test "$v" = NEEDS_REVISION -a "$c" -ge "${vars.max_revisions}"; }; }'
+        command: >-
+          { test "${vars.auto}" = "true"; } &&
+          { v="$(jq -r 'if (.verdict // "") == "PASS" then (.verdict + (if ((.confidence // "") | test("^(HIGH|MEDIUM|LOW)$")) then "" else "!" end)) else (.verdict // "") end' ${vars.work_dir}/.itc-verdict.json 2>/dev/null)";
+          c="$(cat "${vars.work_dir}/.auto-revise-count" 2>/dev/null || echo 0)";
+          { test -z "$v" -o "$v" = PASS; } || test "$v" = FAIL || { test "$v" = NEEDS_REVISION -a "$c" -ge "${vars.max_revisions}"; }; }
 
   - from: judge
     to: draft-autorevise
@@ -706,8 +717,10 @@ transitions:
 
   - from: judge
     to: failed
-    description: "Catch-all: an out-of-contract verdict string fails the run instead of deadlocking the machine (0149 review P3)"
+    description: "Catch-all: an out-of-contract verdict string fails the run instead of deadlocking the machine (0149 review P3); a PASS whose confidence is missing or outside HIGH/MEDIUM/LOW reads as `PASS!` and lands here"
     guard:
       kind: shell
       options:
-        command: 'v="$(jq -r .verdict ${vars.work_dir}/.itc-verdict.json 2>/dev/null)"; test -n "$v" -a "$v" != PASS -a "$v" != FAIL -a "$v" != NEEDS_REVISION'
+        command: >-
+          v="$(jq -r 'if (.verdict // "") == "PASS" then (.verdict + (if ((.confidence // "") | test("^(HIGH|MEDIUM|LOW)$")) then "" else "!" end)) else (.verdict // "") end' ${vars.work_dir}/.itc-verdict.json 2>/dev/null)";
+          test -n "$v" -a "$v" != PASS -a "$v" != FAIL -a "$v" != NEEDS_REVISION

package/plugins/publishings/xhs-pub/dist/index.js

@@ -30127,7 +30127,7 @@ init_dist();
 import { homedir as homedir2 } from "os";
 import { join as join2, resolve as resolve2 } from "path";
 var fs = createNodeFileSystem();
-var CAP_WINDOW_MS = 24 * 60 * 60 * 1000;
+var CAP_WINDOW_MS = 2 * 60 * 60 * 1000;
 var AUTOMATION_STATE_ENV = "KK_XHS_AUTOMATION_STATE";
 function resolveAutomationStatePath(override) {
   const explicit = override ?? process.env[AUTOMATION_STATE_ENV];

package/plugins/publishings/xhs-pub/src/automation-guard.ts

@@ -4,7 +4,7 @@
  * XHS warned the operator about automated login/publish activity. This channel is the only target
  * in the repo that drives an interactive creator console from a browser, so a repeated or runaway
  * visit is an account-level risk rather than a failed run. The guard bounds console visits with two
- * independent 24h budgets — one headed publish cycle and one read-only session check — recorded in
+ * independent 2h budgets — one headed publish cycle and one read-only session check — recorded in
  * a small state file.
  *
  * Semantics that matter:
@@ -33,7 +33,7 @@ const fs = createNodeFileSystem() as unknown as {
 export type XhsAutomationEvent = 'check' | 'publish';
 
 /** One headed publish cycle and one read-only session check per window. */
-export const CAP_WINDOW_MS = 24 * 60 * 60 * 1000;
+export const CAP_WINDOW_MS = 2 * 60 * 60 * 1000;
 
 /** State-file override for tests and multi-account machines; default is the shared kk config dir. */
 export const AUTOMATION_STATE_ENV = 'KK_XHS_AUTOMATION_STATE';

package/plugins/publishings/xhs-pub/src/index.ts

@@ -480,7 +480,7 @@ export class XhsBrowserTransport implements PublishTransport {
             submitSettleMs?: number;
             submitAttempts?: number;
             openPage?: OpenPage;
-            /** ADR-025 automation-risk guard; defaults to the real 24h-capped state file. */
+            /** ADR-025 automation-risk guard; defaults to the real 2h-capped state file. */
             automation?: AutomationGuard;
             /** ADR-025 headless session preflight; defaults to `checkXhsProfileSession`. */
             preflight?: (profileDir: string) => Promise<ProfileSessionCheck>;

package/plugins/publishings/xhs-pub/src/profile-check.ts

@@ -13,7 +13,7 @@
  *    fresh directory.
  *
  * ADR-025 (2026-09-28): the publish flow now runs this same check as a preflight before any headed
- * visit, and `check` draws on the shared 24h automation budget — the cap bounds total console
+ * visit, and `check` draws on the shared 2h automation budget — the cap bounds total console
  * visits, not just publishes. The implementation lives in `./index` so both paths share it.
  *
  * Manual dogfood: `bun plugins/publishings/xhs-pub/src/profile-check.ts login` then
@@ -110,7 +110,7 @@ export async function main(
         );
         return 1;
     }
-    // ADR-025: a manual session check is a real console visit, so it draws on the shared 24h
+    // ADR-025: a manual session check is a real console visit, so it draws on the shared 2h
     // automation budget rather than a separate one. `login` is deliberately uncapped above: it is
     // operator-interactive, so capping it would only block recovery from an expired session.
     const cap = guard.allow('check');

package/plugins/sp/lib/env.ts

@@ -1,46 +0,0 @@
-/**
- * Vendored env gateway for the sp plugin.
- *
- * WHY this copy exists: hooks and scripts in this plugin are bundled
- * standalone by `superskill install` on targets that have no node_modules —
- * any `@gobing-ai/*` import fails to resolve there and aborts the install
- * ("Bundle failed", task 0669). This file mirrors the semantics of the
- * canonical gateway (`@gobing-ai/ts-utils` dist/env, ts-libs) so the plugin
- * stays self-contained. Keep in sync when the upstream gateway changes.
- *
- * These accessors are node-bun only: on `cloudflare-workers` there is no
- * `process`; inject config explicitly rather than calling them (ADR-008).
- */
-
-/**
- * Read one environment variable. Only an unset variable yields `fallback`;
- * an empty string is a set value and is returned as-is.
- */
-export function getEnvVar(name: string, fallback?: string): string | undefined {
-    const raw = process.env[name];
-    return raw === undefined ? fallback : raw;
-}
-
-/**
- * Read the live environment as a record. The returned object IS `process.env`
- * (not a copy): whole-record operations see later mutations, which child-spawn
- * composition relies on. For single variables prefer {@link getEnvVar}.
- */
-export function getEnvVars(): Record<string, string | undefined> {
-    return process.env;
-}
-
-/**
- * Set one environment variable through the gateway. Passing `undefined` removes
- * the key, so the save/restore idiom (`const prev = getEnvVar(k); …
- * setEnvVar(k, prev)`) restores absence exactly.
- */
-export function setEnvVar(name: string, value: string | undefined): void {
-    if (value === undefined) delete process.env[name];
-    else process.env[name] = value;
-}
-
-/** Remove one environment variable; a no-op when the key is absent. */
-export function removeEnvVar(name: string): void {
-    delete process.env[name];
-}