@v587d/capital-generation 2.7.12 → 2.8.1

package/lib/time/tools.js

@@ -67,6 +67,30 @@ const DATA_TIME_CONTRACTS = {
         maxDays: TEN_YEAR_DAYS,
         warning: '分钟档（m1/m5/m15/m30）区间上限 10 天，超出会在参数层被拒；adjust=qfq 时 end_date 不得晚于当日（afdate 由本能力锁成当日）',
     },
+    // FTShare 免费档那三条日度资金流：实测窗口只有最近约 45 个交易日（按真实交易日二分，T-45 有数、T-46 起 total=0）。
+    // ⛔ 这里刻意**不设 maxDays**：maxDays 会在参数层抛错，而这个窗口是每天都在往前滚的观测值，
+    // 写成天数常量等于造一个会腐烂的闸门（窗口变宽就误拒合法请求）。只给 warning 提示模型别循环重试。
+    ftshare_stock_daily_flow: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: '上游只保留最近约 45 个交易日：早于窗口的日期返回 total=0，是合法空结果、不是取数失败，不要换日期循环重试' },
+    ftshare_industry_daily_flow: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: '上游只保留最近约 45 个交易日：早于窗口的日期返回 total=0，是合法空结果、不是取数失败' },
+    ftshare_concept_daily_flow: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: '上游只保留最近约 45 个交易日：早于窗口的日期返回 total=0，是合法空结果、不是取数失败' },
+    ftshare_main_capital_flow: { kind: 'date', fields: ['date'], warning: 'date 必须是交易日；省略时取上游最新切片（实测为当日 15:30 那一次）' },
+    ftshare_daily_kline_snapshot: { kind: 'date', fields: ['trade_date'], warning: 'trade_date 必须是**交易日**：非交易日会在参数层响亮失败（实测上游 400「trade_date 不是交易日」），未来交易日返回 total=0；当日截面收盘后即可取（实测 2026-10-15 15:51 打 20261015 已回 5565 行）' },
+    ftshare_prev_close: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: '历史窗口起点实测在 2022-04（2016 / 2018 / 2020 / 2021 全年区间都回空数组、不报错）；早年请用 history 或 tencent_kline' },
+    ftshare_trading_calendar: { kind: 'date_range', fields: ['start_date', 'end_date'] },
+    ftshare_block_trades: { kind: 'date', fields: ['date'], warning: 'date 必须是交易日；省略 = 上游最新有数的一天，**当日入库时刻不固定**（实测 2026-10-15 19:32 打 date=当天 total=0，同一晚 20:03 重打已有 80 行）——傍晚拿到当天为空先按「还没入库」理解，不是取数失败、不要循环重试。历史不连续：实测 2016-01-04（交易日历确认是交易日）整天为 0' },
+    ftshare_sw_industry_overview: { kind: 'date', fields: ['date'], warning: 'date 必填且必须是交易日（非交易日与未来日期回 total=0，合法空）。⛔ 窗口实测只到最近约 94 个交易日：2026-10-15 实测最早有数的是 2026-05-28，更早的交易日全部 total=0——那是窗口外，不要换日期重试；更早序列请用 ftshare_sw_industry_metrics' },
+    ftshare_sw_industry_metrics: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: '最早一天实测 2021-05-31（更早区间回 total=0、不报错）；start_date 晚于 end_date 也是静默空，本层已在参数层拒。⛔ 聚合列有断供：amount / total_mv / constituent_count / close_price / below_net_asset_count 与多数 *_quantile 实测自 2026-08-26 起为 null（2026-10-14 仍为 null，但 PE/PB/股息率有值），三级行业的 amount / index_close / 拥挤度恒为 null——null 不是 0，别补值也别循环重试' },
+    // 批次 D（2026-10-16 真报文）。⛔ `fields` 的顺序是有主的：resolve_data_time_range 把 period 写成
+    // fields[0] / fields[1]，所以 date_range 必须是 [start, end]，多出来的日期参数只能排在后面。
+    ftshare_limit_price: { kind: 'date_range', fields: ['start_date', 'end_date', 'date'], warning: '单票区间模式：start_date / end_date 必须与 code 一起给（实测只给区间不给标的 → 400「start_date/end_date 需配合 symbol 使用」），跨度不超过 3 年（实测 2020..2026 → 400）。全市场模式用 date（单日）。⛔ 混用 date 与区间上游 400；非交易日、未来日期与早于窗口的日期都只回 total=0、不报错（实测 600519.SH 2009 全年空、2010-01-04 起有数）' },
+    ftshare_dragon_tiger_seats: { kind: 'date', fields: ['date'], warning: 'date 必填且必须是交易日：上游本来允许省略（回"最新快照"），但响应行里**没有日期列**，所以这颗能力要求显式日期来写时间轴。实测非交易日 / 未来日期 / 早于窗口都回 data:null（合法空、不是失败）；窗口起点实测在 2022-01-04（2021-12-31 及更早为空），分不清是滚动还是固定起点' },
+    ftshare_index_weight: { kind: 'date', fields: ['date'], warning: 'date 是**权重采集期**且必须精确命中：实测 2026-06-15 / 2026-09-30 各回该期，而 2026-10-01 / 2026-01-01 这种没有采集的日期 total=0（**不会**回退到最近一期）；省略时取最新一期。请按数据里出现过的 collect_date 挑期，别按自然日猜' },
+    ftshare_convertible_bond_kline: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: '⛔ 跨度上限是 12 个自然月，本层不换算成天数闸门（换算规则未核出）：实测 364 天的区间正常、365 天被上游 400「日 K 及以上周期查询范围不能超过 12 个自然月」。start_date 晚于 end_date 在参数层拒（上游同样 400）。要更长序列请分段取，注意周/月/年档是按请求区间内日 K 聚合的，窗口没盖满周期那根不完整' },
+    // 批次 E（2026-10-16 真报文）：利率族与财经日历。⛔ LPR 那颗**没有日期参数**（上游会静默忽略多发参数），所以不挂契约。
+    ftshare_chinabond_yield: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: 'start_date / end_date 必填。⛔ 三条曲线各自起点不同（实测同一 2002-2010 窗口内：国债 2006-03-01、中短期票据 2006-12-25、商业银行普通债 2009-12-24），早于某条曲线起点只是那一行缺席，是合法空、不是失败、不要按年份重试；起点是滚动还是固定未核出' },
+    ftshare_shibor: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: 'start_date / end_date 必填。历史起点实测在 2006-10-08（2006 全年 63 行、首行就是它；2006-01-01..06-30、07-01..09-30、1999 与 2004 全年都 0 行）；周末、节假日与未发布日没有行，上游不插值也不前值填充，所以序列天然不连续' },
+    ftshare_hibor: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: 'start_date / end_date 必填。实测 2010 全年 249 行（首行 2010-01-04）、2000-01-01..2001-12-31 两年 0 行，起点是否滚动未核出；香港假日与未发布日没有行。⛔ m4 / m5 / m7..m11 七档实测整列为 null（HIBOR 只公布部分期限），null 不是 0，别补值' },
+    ftshare_financial_calendar: { kind: 'date_range', fields: ['start_date', 'end_date'], warning: '⛔ 单次窗上限是 3 天差（实测 4 天就 400「时间范围不能超过3天」，本层在参数层拒）——要更长区间请分段请求，本层不循环取。覆盖是**滚动窗**：实测 2026-08-03 / 09-01 / 09-15 / 10-05 / 10-12 / 10-19 / 10-26 各日都有事件（40 / 59 / 45 / 37 / 21 / 25 / 10 行），2026-11-02 与 11-16 / 12-01 / 2026-01-05 回空数组（total=0），2020 / 2023 / 2024 / 2025 里的整天直接回 data:null——边界随日期前移；两种空都是合法空，不要换日期重试' },
 };
 export function getDataTimeContract(capability) {
     const contract = DATA_TIME_CONTRACTS[capability];

package/lib/web-retriever/local-fetch.d.ts

@@ -6,7 +6,7 @@
  * between validation and connect. Closing that window would require a custom
  * dispatcher; this module keeps the same explicit trade-off as dsh-search-first.
  */
-export declare const LOCAL_FETCH_CLIENT_VERSION = "2.7.12";
+export declare const LOCAL_FETCH_CLIENT_VERSION = "2.8.1";
 export declare const LOCAL_FETCH_MAX_URL_LENGTH = 2048;
 export type LocalFetchErrorCode = 'ABORTED' | 'TIMEOUT' | 'INVALID_URL' | 'BLOCKED_URL' | 'DNS' | 'REDIRECT' | 'HTTP' | 'TOO_LARGE' | 'UNSUPPORTED_CONTENT_TYPE';
 export declare class LocalFetchError extends Error {

package/lib/web-retriever/local-fetch.js

@@ -7,7 +7,7 @@
  * dispatcher; this module keeps the same explicit trade-off as dsh-search-first.
  */
 import { htmlToMarkdown, stripInvisibleText } from './html-markdown.js';
-export const LOCAL_FETCH_CLIENT_VERSION = '2.7.12';
+export const LOCAL_FETCH_CLIENT_VERSION = '2.8.1';
 export const LOCAL_FETCH_MAX_URL_LENGTH = 2048;
 export class LocalFetchError extends Error {
     code;

package/lib/web-retriever/wind-client.d.ts

@@ -52,7 +52,7 @@ export interface WindCallResult {
  * `test/chart-composition.test.mjs` 守着（会因漂移而失败），这里原本是写死的第二处，
  * 一次发版就得记得改两遍。所以本常量由测试一并核对（见 `test/wind-client.test.mjs`）。
  */
-export declare const WIND_CLIENT_VERSION = "2.7.12";
+export declare const WIND_CLIENT_VERSION = "2.8.1";
 export interface WindClient {
     callTool(toolName: string, args: Record<string, unknown>, signal?: AbortSignal): Promise<WindCallResult>;
 }

package/lib/web-retriever/wind-client.js

@@ -35,7 +35,7 @@ export const WIND_SERVER_ENDPOINTS = {
  * `test/chart-composition.test.mjs` 守着（会因漂移而失败），这里原本是写死的第二处，
  * 一次发版就得记得改两遍。所以本常量由测试一并核对（见 `test/wind-client.test.mjs`）。
  */
-export const WIND_CLIENT_VERSION = '2.7.12';
+export const WIND_CLIENT_VERSION = '2.8.1';
 function errorText(error) {
     return error instanceof Error ? error.message : String(error);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@v587d/capital-generation",
-  "version": "2.7.12",
+  "version": "2.8.1",
   "description": "Capital Generation：面向中国散户的 AI 投资助手插件(Capital mode Agent Preset）",
   "icon": "assets/cg-icon.png",
   "author": "v587d",

package/preset/capital-generation/README.md

@@ -120,33 +120,40 @@
   coding 工具；插件注册 `read_profile`（allow 里的名字必须先真实存在）；更新 `AGENTS.md` 与 `docs/dev/data-roles.md`
   的角色边界与 `test/persona.test.mjs` 的预留期断言。
 
-## 5.1 bash：为什么只给 data_junior，以及它到底能做什么
+## 5.1 shell 与文件口：开 read、保留 bash、不给写（2026-10-15 用户决策）
 
 - **动机**：`query_dataset` 只有 `count/min/max/avg/sum`，变化量 / 增幅 / CAGR / 比值这类派生
   指标没有宿主工具；模型只能拿 `time_facts.first/last` 心算——那正是 §1.3 那次 41,961 字符
   时间戳心算的同型浪费。所以给 data_junior 一个纯计算兜底。**不是**给它开取数通道。
-- **为什么主 Agent 不给**：主 Agent 今天没有任何通用执行 / 文件 / 网络工具（Web 平面把 host 层
-  的 `tool-bash` / `tool-fs` / `tool-web` 都 `disabled` 了，本 preset 也不挂回来）。这是一条
-  结构性事实，不是 persona 约定：主 Agent 唯一对用户说话、又会读到子 Agent 回传（含网页材料），
-  一旦拥有 bash 就等于拿到"注入 → 执行 → 读凭据 → 出网"的完整链路。收敛靠
-  `ROOT_AGENT_DENIED_TOOLS`（含 `bash` / `pwsh`）。
+- **2026-10-15 起主 Agent 也持有 shell 与 `read`**（用户决策「开 read、同时保留 bash」，推翻
+  2026-09-30 的"主 Agent 不给 shell"）：主 Agent 需要 `read` 读 skill 分册与工作区文件
+  （此前只能 `bash cat`，能力等价但绕远），shell 保留纯计算兜底。`ROOT_AGENT_DENIED_TOOLS`
+  里的 `bash` / `pwsh` 随之移出，名单改为出图三件套 + 十三个出网工具 + `write` / `edit`。
+- **文件写口不开**：`write` / `edit` 被两层拦住——根侧逐名收敛（主 Agent 视图层）+ 全局
+  `tools.guard()`（`registerFsWriteGuard`，调用期按 `composedPreset` 认领，fail-open，细节见
+  `docs/dev/bash-gate.md` §1.6）。理由：主 Agent 唯一对用户说话、又会读到子 Agent 回传（含网页
+  材料），写文件等于给"注入 → 落盘 → 被别的环节读回"开口；业务落盘本来就有正路
+  （`store.writeContext` 等工具实现），模型手里的写口没有正当用途。通用 `subagent` 行的
+  `toolFilter.deny` 同步含 `read` / `write` / `edit`（通用 child 不得读 raw.json，原始 rows
+  永不出工具层）。
 - **平台成对挂载**：Windows 上 host 层挂的是 `pwsh-sandbox`，没有 `bash-sandbox`；只挂
   `tool-bash` 会让名为 bash 的工具实际执行 PowerShell。所以两行互补 `disabled`，allow / deny
   里的名字用 `!!js` 三元表达式按平台选。`tools.restrict()` 对未注册名字报错，所以表达式与行必须
   同进同退（回归：`test/persona.test.mjs`「shell 行：平台成对挂载……」）。
 - **不给后台执行**：`enableRunInBackground: false`。本 preset 不挂 `tool-jobs`，开着后台只会让
   模型拿到一个永远读不回来的 jobId（`job_output` / `job_kill` 不在任何 allow 里）。
-- **闸门只有两层，且都不是安全边界**（`src/agents/bash-guard.ts`）：
-  ① 只对**被委派**子会话开放（镜像 `tool-exec.ts` 的 `delegatedSession`，执行层兜住可见性被改坏）；
-  ② 拦掉 `sandbox_permissions`——委派会话的审批策略由框架固定为 `never`，升级必然失败，而且模型
-  会收到「the user rejected…」这种把系统拒绝说成用户拒绝的文案。
-  **刻意不解析 `command`**：本仓实测沙箱只拦写、不拦读（`~/.dsh/.credentials.yaml` 与
-  `sessions/**` 整机可读）、不拦网络（`curl` 直连 200），而正则挡不住 `node -e` / `python3 -c`
-  ——那正是引入 bash 的目的。禁区与出网纪律是 data_junior persona 的 `# BASH DISCIPLINE` 软约束。
-- **写边界收不窄**：`store.writeContext()` 用**调用方 session** 的 policy 且要求
+- **shell 闸门只剩一层，且不是安全边界**（`src/agents/bash-guard.ts`）：拦掉
+  `sandbox_permissions` / `justification`——被委派会话的审批策略由框架固定为 `never`，升级必然
+  失败，而且模型会收到「the user rejected…」这种把系统拒绝说成用户拒绝的文案；被委派或身份
+  不可考的调用方 fail closed。主 Agent 的升级走正常 ask 审批（2026-10-15 前的"只对被委派子会话
+  开放"一层随决策移除，断言迁移见 `test/bash-guard.test.mjs`）。**刻意不解析 `command`**：本仓
+  实测沙箱只拦写、不拦读（`~/.dsh/.credentials.yaml` 与 `sessions/**` 整机可读）、不拦网络
+  （`curl` 直连 200），而正则挡不住 `node -e` / `python3 -c`——那正是引入 bash 的目的。禁区与
+  出网纪律是 data_junior persona 的 `# BASH DISCIPLINE` 软约束。
+- **写边界收不窄到会话**：`store.writeContext()` 用**调用方 session** 的 policy 且要求
   `mode ∈ {workspace-write, danger-full-access}`，而 `describe_dataset` 会用 data_junior 的会话写
   `profile.json`；把它的会话钉成 `read-only` 会直接打断 describe_dataset。bash 与 Dataset 管线
-  共用同一把尺子（session policy）。
+  共用同一把尺子（session policy），所以模型侧写口只能靠上一条的调用期闸门收。
 - **要真正收紧**只有两条路：换掉 `ctx.shell`（容器 / 微 VM / 远端执行器），或给 dsh 进程做出网
   限制。两者都不是 `ctx.sandbox` 能提供的。
 

package/preset/capital-generation/agent.patch.yml

@@ -45,6 +45,8 @@
                 最终答：工具完成后再答，必须含结论、关键证据与来源标注、局限与风险；归因准确，给出观察 / 验证 / 防守选项；勿只报“已交付/已完成”。
 
                 # RULES & DISCIPLINE
+                读文件只用 read：只读 skill 分册与工作区文件；不读 capital-data/ 落盘（原始行走回传），不读 ~/.dsh/；
+                   分册整册读完才算读过。
                 用户倾向与外界观点皆为待检验假设；发现造假、质押、现金流或流动性风险时如实说明并给边界，不制造恐慌。
                 仅在有可复现模型或回测时报告胜率 / 盈亏比 / 概率，并披露区间、样本、费用、方法与失效条件；否则明确「无法可靠测算」。
                 不索取凭据与不必要仓位信息；不保证收益或准确率；极端行情与数据延迟如实说明局限。
@@ -130,7 +132,7 @@
                    不得冒充行情证据或补位缺失能力。不支持的频率如实披露，用已有粒度降级，不编造。
 
 
-          # ── shell：只给 data_junior（主 Agent 由 root-tool-policy 在自己 scope 上 deny）──────
+          # ── shell：主 Agent 与 data_junior 共用（2026-10-15「开 read、同时保留 bash」）────
           # 边界、为什么不按命令内容 deny、平台门控：见同目录 README.md 的「bash」一节。
           - id: tool-bash
             name: '@deepseek-ai/dsh-tool-bash'
@@ -145,6 +147,12 @@
             config:
               enableRunInBackground: false
 
+          # ── 文件口：read 开给主 Agent 读 skill 分册 / 工作区文件（2026-10-15 用户决策）────
+          # `tool-fs` 一颗挂 read / write / edit：write / edit 由根侧收敛 + 全局写口闸门拦
+          # （src/agents/root-tool-policy.ts），落盘只走工具实现；tool-fs-search 本轮不挂。
+          - id: tool-fs
+            name: '@deepseek-ai/dsh-tool-fs'
+
           - id: tool-subagent-data-collector
             name: '@deepseek-ai/dsh-tool-subagent'
             config:
@@ -418,6 +426,11 @@
               toolFilter:
                 deny:
                   - !!js "process.platform === 'win32' ? 'pwsh' : 'bash'"
+                  # 文件口全关：通用 child 不得读 raw.json（原始 rows 永不出工具层）也不得写；
+                  # read_image 刻意不点名（条件注册，名字不在 = 创建子 Agent 失败，且它只读）。
+                  - read
+                  - write
+                  - edit
                   - render_chart
                   - prepare_chart_source
                   - describe_dataset

package/preset/capital-generation/skills/capital-data-protocol/SKILL.md

@@ -59,7 +59,7 @@ description: Use when composing or reading a Capital data message — data_reque
 | 步 | 工具 | 得到什么 | 调用纪律 |
 |----|------|----------|----------|
 | ① | `list_capabilities()` | 纯文本能力目录：**一行一条** `capability\|summary\|paginated`（1=分页、0=不分页） | **一个任务只调一次**；目录已在本 session 历史里，重复调用只会白占上下文 |
-| ② | `describe_capability({ capability })` | 该能力的完整 `description` / `input_schema` / `output_fields`（逐行字段字典） | 一次只传**一个**名字、**不传逗号**；同一个能力描述一次即可；要几个能力就分别调用几次 |
+| ② | `describe_capability({ capability })` | 该能力的完整 `description` / `input_schema` / `output_fields`（逐行字段字典） | 一次只传**一个**名字、**不传逗号**；同一个能力描述一次即可；要几个能力就在**同一条消息里一次发出多个调用**（纯读、可并发），不要一份一份等 |
 
 - 读目录时**按行切**：一行就是一条能力，取第一个 `|` 前面的部分当 `capability` 原样复制；摘要里出现的
   `\|`、`\n` 是转义字符，不是分隔符。
@@ -69,6 +69,9 @@ description: Use when composing or reading a Capital data message — data_reque
 - 目录刻意不含参数与输出结构：全量 schema 约 23KB，会被工具结果剪枝器（阈值 8192）截断中间
   部分，导致排在中间的能力在发现阶段不可见。目录只负责"选哪个"，详情负责"怎么填"。
 - **一个任务只调一次 `list_capabilities`**；**同一个能力只描述一次**，重复调用只会白占上下文。
+- `list_capabilities` 与 `describe_capability` 都是**纯读**：本轮要看几个能力，就在**同一条消息里一次发出
+  这几个 `describe_capability` 调用**，它们在框架并发池里并行执行、在同一个下一步一起返回；一份一份等
+  等于把一次往返付成 N 次。这不改变上一条"每个能力只描述一次"，也不改变"一次只传一个名字"。
 - 不查 `input_schema` 就填 `params` 属于违规；`params` 的取值与约束一律以 `describe_capability` 为准。
 
 `describe_capability` 的错误按 code 处置，不要盲目重试：

package/selected-skills/InvestSkill/UPSTREAM.md

@@ -60,6 +60,23 @@
 - Maintenance snapshot（checked 2026-10-10）：251 次提交；近 90 天 47 次非机器人提交、近 180 天 111 次；
   最新 release `v1.12.0`（2026-09-25）。维护活跃，因此标 `experimental`。
   See [GitHub commit history](https://github.com/yennanliu/InvestSkill/commits/main/).
+- Visibility layering, second batch (2026-10-15, same §8.6 reason): the remaining **25** catalogued entries in this
+  snapshot were single-file bodies of 15,437–31,754 characters — every one of them arrived as a truncated excerpt
+  (head 4,096 + tail 1,024) once a user ticked it. All 25 are now entry file plus parts under `skills/<name>/references/`:
+  the entry keeps only what holds on every round (`⚠️ Data Verification`, `📋 Data & Sources Header`, and
+  `⚠️ Read This First` where upstream wrote one), gains an index of the part filenames, and states that loading the
+  entry is not reading the skill. Everything else moves **in section order** into `references/10…`, splitting a
+  section that still overflows at `###`, then `####`, then blank-line paragraphs — and a section cut across two parts
+  gets a one-line pointer at the cut (`This section is not finished here: … continues in references/NN-….md`), which
+  is why prose like "the following sections" still lands: across the whole batch exactly **one** real dangling pointer
+  had to be rewritten (`learning-coach`: "the quiz block from §4" → the part that now holds §4). Nothing was deleted —
+  a line-set check per entry found zero lost lines apart from that rewrite, and each directory's `.md` total grew
+  (e.g. `stock-eval` 31,754 → 34,135, `earnings-call-analysis` 15,437 → 16,873; 98 new parts in total). Sizes are judged
+  on the **rendered** `read` receipt, with the part header itself reserved inside the envelope. Two upstream quirks are
+  deliberately left alone: `institutional-ownership` mentions "the smart-money list above" that upstream never defines,
+  and `fact-check`'s example table cites `§1…§5` of **the report being verified**, not of this skill — neither is a
+  layering artefact. `test/selected-skills-content.test.mjs` (LAYERED, now 32 entries) and the ratchet in
+  `test/persona.test.mjs` (baseline emptied, so any future oversized entry fails outright) hold the result.
 - Visibility layering (2026-10-14, third allowed reason in `docs/dev/selected-skills.md` §8.6): `bear-case` and `stock-screener` had a single `SKILL.md` over the host load cap (8,192 code points; the middle of a longer tool result comes back as `[... tool result middle pruned ...]`). Each is now an entry file plus parts under `skills/<name>/references/`: `bear-case` 13,816 → 15,218 characters with `10-analysis-framework.md`, `11-output-and-signal.md`, `12-thesis-invalidation.md`; `stock-screener` 11,588 → 12,961 with `10-scoring-framework.md`, `11-output-format.md`, `12-invalidation-and-signal.md`. The entry keeps its per-round discipline sections (Data Verification, the Data & Sources header, Read This First / Accepted Inputs) and gains an index of the parts plus a line saying that loading the entry is not reading the skill. No line of upstream text was deleted: a line-set check against this commit found only the rewritten pointer lines, plus two cross-file pointers fixed (`pillars 1–7 above` → the file that now holds them, and the same for `The Score above`). MIT, so no per-file licence notice is required. Sizes are judged on the **rendered** `read` receipt (each line gains an `N: ` prefix), not on file characters — see `test/selected-skills-content.test.mjs`.
 - Runtime status: `experimental` / 显式实验。默认全关，只在使用者于「插件」→ Capital Generation →「配置」
   逐格打开后，对**之后新建**的 Capital 根 Agent 可见；子 Agent 不继承。

package/selected-skills/InvestSkill/plugins/us-stock-analysis/skills/10k-digest/SKILL.md

@@ -37,302 +37,16 @@ Data & Sources
 
 Produce a clean, structured markdown document that distills a company's 10-K annual report into an abstract, per-section summaries, a digest of key metrics, and full source references. Designed for quick comprehension — not trading signals. Output language is selectable: English or Traditional Chinese (繁體中文).
 
-## 🔎 Retrieving the Filing — the Keyless EDGAR Path
+## Read the Parts
 
-This skill fetches nothing by itself. When the user gives only a ticker, obtain the 10-K in one of three ways and record which one in the `Data & Sources` header:
+Everything below the surface of this file lives in `references/`. **whole, with no line window** — quoting a rule or a template out of a slice of one is how a
+file gets reported as read when it was only skimmed. The file names below are the only
+addressing this entry has.
 
-**A. Retrieval through the host (the normal path)** → `Retrieval: delegated retrieval`. In a role-split host, delegate the fetch to the agent that owns web retrieval — this step never searches from the analysis role itself. Every step is free and needs no API key:
+- `references/10-retrieving-the-filing.md` — 🔎 Retrieving the Filing — the Keyless EDGAR Path; How to Use; Output Document Structure
+- `references/11-key-metrics-table.md` — (continued) Output Document Structure; References
+- `references/12-language-mode.md` — Language Mode; File Output; Thesis Invalidation
 
-1. **Ticker → CIK** — `https://www.sec.gov/files/company_tickers.json`: find the entry whose `ticker` matches (write `BRK-B` for `BRK.B`) and zero-pad its `cik_str` to 10 digits.
-2. **Filings index** — `https://data.sec.gov/submissions/CIK##########.json`: inside `filings.recent` the arrays `form`, `filingDate`, `reportDate`, `accessionNumber` and `primaryDocument` are aligned by index. Take the newest row whose `form` is `10-K` (foreign private issuers file `20-F` instead; a `10-K/A` is an amendment). The top-level `fiscalYearEnd` is `MMDD`.
-3. **The document** — `https://www.sec.gov/Archives/edgar/data/<CIK without leading zeros>/<accessionNumber without dashes>/<primaryDocument>`: the complete filing as HTML (inline XBRL). The filing's index page is the same folder plus `<accessionNumber>-index.htm`; cite that URL and the accession number in the References.
-4. **Structured statement data (optional)** — `https://data.sec.gov/api/xbrl/companyfacts/CIK##########.json`: every US-GAAP fact the company has tagged, by concept and period. Use it to confirm the figures read from Item 8.
-5. **Full-text search (optional)** — `https://www.sec.gov/edgar/search/#/q=%22<phrase>%22&forms=10-K` when a filing has to be located by phrase rather than ticker.
-
-Send a `User-Agent` header that identifies the requester (the SEC requires it, e.g. `Name email@example.com`) and stay under 10 requests per second. Never substitute a summary site for the filing itself.
-
-**B. Only if the host has no retrieval path at all** → `Retrieval: pasted by user`. Ask the user for the sections needed. The repository's own fetch helpers are optional, keyless, and live outside this plugin — they are never run from here.
-
-**C. Neither** → show the ⚠️ *Source unavailable* warning and digest only what the user provided. What is absent stays absent: no accession number, figure or date is filled in from memory.
-
----
-
-## How to Use
-
-```
-# Analyze by ticker (retrieves the latest 10-K via the EDGAR path above, or asks you to paste it)
-/10k-digest AAPL
-
-# Paste 10-K text directly
-/10k-digest [paste 10-K sections here]
-
-# Specify fiscal year
-/10k-digest MSFT FY2024
-
-# Output in Traditional Chinese
-/10k-digest NVDA --lang zh-TW
-
-# Save output to file
-/10k-digest GOOGL --output googl-10k-digest.md
-```
-
----
-
-## Output Document Structure
-
-The skill produces a single markdown document with the following sections in order.
-
----
-
-### 1. Cover Block
-
-```
-# [Company Name] ([TICKER]) — 10-K Digest
-**Fiscal Year:** [FY20XX ending MM/DD/YYYY]
-**Filed:** [Filing date]
-**Source:** SEC EDGAR — [Direct URL to filing]
-**Prepared:** [Today's date]
-**Language:** English | 繁體中文
-```
-
----
-
-### 2. Abstract
-
-A 3–5 sentence executive summary of the entire 10-K. Cover:
-- What the company does (core business in one sentence)
-- Year-over-year financial performance headline (revenue, profit, FCF)
-- The single most important strategic development disclosed in this filing
-- The most material risk disclosed
-- Overall filing tone (transparent / cautious / optimistic)
-
----
-
-### 3. Section Summaries
-
-Summarize each major 10-K section. For each section, write 2–4 sentences capturing the substance — not just restating headings.
-
-#### 3.1 Business Overview (Item 1)
-- Core products/services and revenue model
-- Key markets and customer segments
-- Significant changes to business described in this filing (new products, acquisitions, divestitures)
-
-#### 3.2 Risk Factors (Item 1A)
-- Total number of risk factors disclosed
-- Top 3 risks by disclosure prominence (listed first, given most space, or new this year)
-- Any risks added or removed vs. prior filing (state "N/A if prior not available")
-- One-line assessment: are risks standard boilerplate or specific and material?
-
-#### 3.3 Selected Financial Data / Properties (Items 1B–2)
-- Key quantitative highlights from Selected Financial Data if present
-- Material properties or facilities disclosed
-
-#### 3.4 Management's Discussion & Analysis — MD&A (Item 7)
-- Revenue: total and YoY growth; organic vs. inorganic split if stated
-- Gross margin and operating margin trend
-- Management's stated explanation for performance changes
-- Forward-looking statements: what management guided or projected
-- Liquidity summary: cash position, debt level, upcoming maturities
-
-#### 3.5 Financial Statements (Items 8)
-- Revenue, net income, EPS (GAAP) — current year vs. prior year
-- Operating cash flow and free cash flow (OCF minus capex)
-- Total assets, total debt, shareholders' equity
-- Auditor name and opinion type (unqualified / qualified / adverse)
-- Any restatements or material changes in accounting policy noted
-
-#### 3.6 Quantitative Disclosures about Market Risk (Item 7A)
-- Primary market risks disclosed (interest rate, FX, commodity)
-- Sensitivity disclosures if provided (e.g., "1% rate rise = $X impact")
-
-#### 3.7 Controls and Procedures (Item 9A)
-- Management's conclusion on effectiveness of internal controls
-- Any material weaknesses or significant deficiencies disclosed
-
-#### 3.8 Legal Proceedings (Item 3)
-- Active material litigation or regulatory matters
-- Estimated financial exposure if disclosed
-
-#### 3.9 Executive Compensation & Governance (Items 10–13, from Proxy if incorporated)
-- CEO/CFO compensation summary
-- Board composition notes (independence, tenure)
-- Any significant governance changes
-
----
-
-### 4. Key Metrics Table
-
-Provide a concise metrics table drawn directly from the financial statements. Use exact figures from the filing; do not estimate.
-
-```
-| Metric                    | Current FY      | Prior FY        | YoY Change |
-|---------------------------|-----------------|-----------------|------------|
-| Revenue                   | $X.XX B         | $X.XX B         | +X.X%      |
-| Gross Profit              | $X.XX B         | $X.XX B         | +X.X%      |
-| Gross Margin %            | XX.X%           | XX.X%           | +X bps     |
-| Operating Income          | $X.XX B         | $X.XX B         |            |
-| Operating Margin %        | XX.X%           | XX.X%           |            |
-| Net Income (GAAP)         | $X.XX B         | $X.XX B         |            |
-| EPS Diluted (GAAP)        | $X.XX           | $X.XX           |            |
-| Operating Cash Flow       | $X.XX B         | $X.XX B         |            |
-| Capital Expenditures      | $X.XX B         | $X.XX B         |            |
-| Free Cash Flow            | $X.XX B         | $X.XX B         |            |
-| Cash & Equivalents        | $X.XX B         | $X.XX B         |            |
-| Total Debt                | $X.XX B         | $X.XX B         |            |
-| Net Debt / (Net Cash)     | $X.XX B         | $X.XX B         |            |
-| Shares Outstanding (dil.) | X.XX B          | X.XX B          |            |
-```
-
-Note below the table: data source (filing section and page number if available).
-
----
-
-### 5. Highlights & Concerns
-
-Two short lists that give the reader the "so what" without leaving the digest. Draw every item directly from the filing and cite the source Item.
-
-**Highlights** — up to 5 of the strongest positives disclosed this year (e.g., record revenue, margin expansion, new products/segments, strong FCF conversion, new buyback authorization, market-share gains). Format: `- **[Headline]** — [one sentence] *(Item X)*`
-
-**Concerns** — up to 5 of the most material negatives or warning signs (e.g., decelerating growth, margin compression, rising leverage, customer/supplier concentration, new risk factors, active litigation, going-concern language). Format: `- **[Headline]** — [one sentence] *(Item X)*`
-
----
-
-### 6. Management Outlook & Forward Guidance
-
-Capture every forward-looking commitment made in the filing. Present as a table.
-
-```
-| Guidance Item              | What Management Said                | Time Horizon | Source     |
-|----------------------------|-------------------------------------|--------------|------------|
-| Revenue growth             | [target / range / directional]      | [FY / multi] | Item 7     |
-| Margin target              | [gross / operating target]          | [horizon]    | Item 7     |
-| Capex / capacity           | [planned spend or expansion]        | [horizon]    | Item 7     |
-| Capital allocation         | [dividend / buyback / debt / M&A]   | [horizon]    | Item 7/8   |
-| Strategic priorities       | [product roadmap, new markets]      | [horizon]    | Item 1/7   |
-```
-
-Only include rows the filing actually addresses. If the 10-K gives no explicit guidance (common — 10-Ks are backward-looking), state that and summarize any qualitative forward statements instead.
-
----
-
-### 7. Prior-Year Promise Tracker
-
-An accountability audit: take the forward-looking statements, targets, and stated priorities from **last year's** 10-K (Item 7 MD&A) and score whether they materialized in this year's results. This is the single most differentiating part of the digest — it measures management credibility over time.
-
-```
-| Prior-Year Commitment (FY[N-1] 10-K)   | FY[N] Actual Result          | Verdict     | Notes            |
-|-----------------------------------------|------------------------------|-------------|------------------|
-| [what management said they would do]    | [what actually happened]     | ✅ Delivered | [brief context]  |
-| [e.g., "expand operating margin"]       | [e.g., "margin +120 bps"]    | 🟡 Partial  | [brief context]  |
-| [e.g., "launch product X in H2"]        | [e.g., "slipped to next FY"] | ❌ Missed    | [brief context]  |
-```
-
-Verdict legend: ✅ Delivered · 🟡 Partial · ❌ Missed · ⏳ Too early to judge.
-
-Close with a one-line **Management Credibility read**: e.g., "4/5 prior commitments delivered — high follow-through." If the prior-year 10-K is unavailable, state `N/A — prior filing not retrieved` and skip the table.
-
----
-
-### 8. Bull vs. Bear Synthesis
-
-A lightweight face-off built strictly from evidence in this filing — not a full valuation call (defer to `bear-case`, `stock-eval`, and `stock-valuation` for that).
-
-**Bull case** — 3–4 strongest points from this filing supporting the stock.
-
-**Bear case** — 3–4 strongest points from this filing arguing against it.
-
-**Net read** — one sentence weighing the two, consistent with the Investment Signal below.
-
----
-
-### 9. Notable Disclosures
-
-Bullet list of up to 8 items that are worth investor attention but don't fit neatly into section summaries:
-- New segment or business unit disclosures
-- Changes in accounting estimates or policies
-- Related party transactions
-- Auditor changes
-- Going concern language (if any)
-- New share repurchase authorizations or dividend changes
-- Material acquisitions or divestitures announced
-- Specific named customers or suppliers with concentration risk
-
----
-
-### 10. Source References
-
-List all sources cited in this digest. Format:
-
-```
-## References
-
-1. **SEC EDGAR Filing** — [Company] 10-K, FY[XXXX]
-   URL: https://www.sec.gov/cgi-bin/browse-edgar?...
-   Filed: [Date] | Accession No.: [XXXXXXXXXX-XX-XXXXXX]
-
-2. **Item 1 — Business** (pp. X–X of filing)
-3. **Item 1A — Risk Factors** (pp. X–X of filing)
-4. **Item 7 — MD&A** (pp. X–X of filing)
-5. **Item 8 — Financial Statements** (pp. X–X of filing)
-6. **Item 9A — Controls and Procedures** (pp. X–X of filing)
-7. **Exhibit 13 / Annual Report to Shareholders** (if incorporated by reference)
-8. [Any additional sources used, e.g. earnings press release, investor presentation]
-```
-
-If page numbers are unavailable (e.g., pasted text), reference by Item number and section heading.
-
----
-
-## Language Mode
-
-When `--lang zh-TW` is specified, output the **entire document** in Traditional Chinese (繁體中文), including:
-- All section headings translated
-- All narrative summaries written in Traditional Chinese
-- All tables with Chinese column headers
-- Cover block language field: `語言：繁體中文`
-- Keep ticker symbols, financial figures, and SEC item numbers in their original form
-
-Suggested Traditional Chinese headings for the interpretation sections: 亮點與隱憂 (Highlights & Concerns), 管理層展望 (Management Outlook & Forward Guidance), 上年度承諾兌現 (Prior-Year Promise Tracker), 多空對決 (Bull vs. Bear Synthesis).
-
-English mode is the default when no `--lang` flag is given.
-
----
-
-## File Output
-
-When `--output <filename>` is specified:
-- Save the digest as a markdown file at the specified path
-- If no path separator is present, save in the current directory
-- Confirm the file path after saving: `✓ Digest saved to: <path>`
-- Default filename if `--output` flag is present without a name: `<TICKER>-10k-digest.md`
-
----
-
-## Thesis Invalidation
-
-After delivering the digest, note what would make this document stale:
-
-**Re-run this digest when:**
-- [ ] Company files next 10-K or 10-K/A amendment
-- [ ] Material 8-K filed disclosing a restatement or auditor change
-- [ ] 12 months have elapsed since the filing date
-
-```
-╔══════════════════════════════════════════════╗
-║              INVESTMENT SIGNAL               ║
-╠══════════════════════════════════════════════╣
-║ Signal:      BULLISH / NEUTRAL / BEARISH     ║
-║ Confidence:  HIGH / MEDIUM / LOW             ║
-║ Horizon:     SHORT / MEDIUM / LONG-TERM      ║
-║ Score:       X.X / 10                        ║
-╠══════════════════════════════════════════════╣
-║ Action:      BUY / HOLD / SELL               ║
-║ Conviction:  STRONG / MODERATE / WEAK        ║
-╚══════════════════════════════════════════════╝
-```
-
-Score Guide: 8.0–10.0 Strongly Bullish | 6.0–7.9 Moderately Bullish | 4.0–5.9 Neutral | 2.0–3.9 Moderately Bearish | 0.0–1.9 Strongly Bearish
-Confidence: HIGH (strong data, clear signals) | MEDIUM (mixed signals) | LOW (limited data, conflicting signals)
-Horizon: SHORT-TERM (1 week–3 months) | MEDIUM-TERM (3 months–1 year) | LONG-TERM (1+ years)
-
-**Disclaimer:** Educational analysis only. Not financial advice.
+Loading this file is not reading the skill: the steps, templates, and thresholds exist only
+in the parts above. Say which parts you opened, name the ones you did not, and never report a
+step or a template you have not read in this session.