Repository navigation
The saved contract becomes a two-way artifact. A spec now records its own state — verification_status (asked / routed / verified / superseded) plus an optional verification object holding the check that runs after a hand-off, both optional so every spec 1.2.0 wrote still validates. A session looks for <workspace>/.intent/<intent>.intent.yaml before probing anything and follows that state: a question already answered is not asked again, a settled contract is carried out as written, one already carried out is not reopened unless you ask. Inheritance is by source and never wholesale — an asked constraint carries over, a probed one is re-checked at its evidence pointer and drops back to unknown when it no longer holds, an inferred one is never inherited, so an old inference cannot be laundered into a fact. The hand-off names the spec file and asks for every constraint to be checked before the work is called done, writing that result back into the same file. Replies now lead with 3–6 lines of prose before the fenced spec.
存下来的契约从此是双向的。spec 会记录自己的状态——verification_status（asked / routed / verified / superseded），外加一个可选对象 verification 用来装交接之后那次核对的结果；两者都可选，因此 1.2.0 写出的每份 spec 依然通过校验。session 会在探测任何东西之前先找 <workspace>/.intent/<intent>.intent.yaml，按该状态分流：已答过的问题不再问，已定的契约照写实施，已做过的不重开（除非你明确要求重做）。继承按来源、绝不整体照搬——asked 约束直接继承，probed 约束回到它的 evidence 指针重新核实、不再成立就退回未知项，inferred 约束一律不继承，于是一次旧推断不会被洗成事实。交接会点名 spec 文件路径，并要求在宣布完成前逐条约束核对；核对结果写回同一份文件。回复改为先用 3–6 行散文，再给围栏 spec。
Repository / 仓库运维: main is protected with offline-gate as a required status check, linear history, and force-pushes and deletions refused; GitHub Pages serves docs/, and Discussions is enabled. / main 受保护：offline-gate 是必需状态检查，历史必须线性，拒绝强推与删除；GitHub Pages 从 docs/ 发布站点，Discussions 已开启。
Documentation / 文档: two bilingual write-ups land under docs/articles/, built entirely out of the numbers already committed in evals/reports/. / docs/articles/ 下新增两篇中英文章，全部素材取自 evals/reports/ 里已提交的数字。
Verification / 核验: incomplete for this release, and that is stated rather than implied. The delivery run on opencode reached ASK and then ROUTE with a schema-valid spec carrying the new verification_status: routed, but its implement turn hit the runner's 480-second ceiling and was killed, so no diff was produced. The same turn took 354 s on 2026-09-28 and passed, so this is a timing edge rather than a behaviour verdict — but no verification run of the final skill text exists, and this release claims nothing about the 2026-09-28 changes beyond what those two reports already carry. / 本版核验未完成，这一点如实写明而非含糊带过。opencode 上的交付运行走到了 ASK、再到 ROUTE，spec 通过 schema 校验并带上新的 verification_status: routed；但实施轮撞上 runner 的 480 秒上限被杀，没有产出 diff。同一轮在 2026-09-28 用时 354 秒并通过，因此这是时序临界而非行为判定——但没有针对最终 skill 文本的核验运行，本版对 2026-09-28 那批改动不作任何超出上述两份报告已有内容的声称。
Full changelog: v1.2.0...v1.3.0