skill-family-engineering-kit 0.2.1 → 0.4.0

package/docs/architecture/index.html

@@ -1972,7 +1972,7 @@ Contracts（结构、协议、错误码、协议名登记）
 <tbody>
 <tr>
 <td>Contracts</td>
-<td>结构、协议、错误码、协议名登记；18 类顶层对象；9 条 mandatory rule</td>
+<td>结构、协议、错误码、协议名登记；20 类顶层对象；9 条 mandatory rule</td>
 <td>业务字段语义、领域审计、远端写入、模型生成</td>
 </tr>
 <tr>
@@ -2024,7 +2024,7 @@ Contracts（结构、协议、错误码、协议名登记）
 <li>涉及制品关系/版本锁 → artifact-graph。</li>
 <li>只有一个消费者或尚未证明跨两个真实消费者重复 → 留在消费者，不扩张 Foundation。</li>
 </ol>
-<p>第 8 步是扩张闸门：新增组件必须说明删除它会让两个以上真实消费者重复实现，并经独立 fixture 验证。机器可读版见 <code>docs/agents/architecture-routing.md</code>。</p>
+<p>第 8 步是扩张闸门：新增组件必须说明删除它会让两个以上真实消费者重复实现，并经独立 fixture 验证；进入门 1 另要求至少一个现有真实消费者加一个结构同型的可预见消费者（第二消费者不要求已上线，但需求必须能用同一结构表达，调整记录见 FND-ADR-009）。第 9 步是有限封闭语义闸门（对应 FND-ADR-001 门 8）：能力若携带少量领域语义，必须满足语义能被少数稳定封闭枚举覆盖，或为确定性估算原语——算法、适用范围与偏差方向已在契约中声明；本闸门不取消门 2「语义无关」一票否决。机器可读版见 <code>docs/agents/architecture-routing.md</code>。</p>
 <h2 id="信任与副作用边界">信任与副作用边界<a class="headerlink" href="#信任与副作用边界" title="Permanent link">&para;</a></h2>
 <p>Foundation 的信任前提与副作用约定按层固化，调用方据此判断风险：</p>
 <ul>
@@ -2050,6 +2050,12 @@ Contracts（结构、协议、错误码、协议名登记）
 涉及制品关系/版本锁? ──是──▶ artifact-graph
         │否
 只有一个消费者/未证明跨两个真实消费者? ──是──▶ 留在消费者，不扩张
+        │否
+携带少量领域语义? ──是──▶ 有限封闭语义：稳定闭枚举可覆盖，或为确定性
+         │               估算原语（算法/适用范围/偏差方向已契约声明）→ 可纳入；
+         │               否则留在消费者（FND-ADR-001 门 8，不取消门 2 一票否决）
+         │否
+        ──▶ 可纳入
 </code></pre>
 <h2 id="与外部项目的路由关系">与外部项目的路由关系<a class="headerlink" href="#与外部项目的路由关系" title="Permanent link">&para;</a></h2>
 <p>Foundation 不是全能底座。下列职责明确在 Foundation 之外：</p>
@@ -2066,11 +2072,12 @@ Contracts（结构、协议、错误码、协议名登记）
 <li><strong>宿主接入线</strong>（FND-FR-001/FND-FR-002，FND-ADR-003）：Contracts 登记 descriptor/source/manifest/probe/plan/receipt；Harness 实现通用 source closure、原子 build/materialize 和 probe 分类；Kit 注入具体 Profile 与受信 driver。当前只支持 describe/build/probe/plan，<code>apply</code> 稳定拒绝，安装/卸载/更新均未实现。</li>
 <li><strong>持久状态底座线</strong>（FND-FR-003，FND-ADR-004）：append-only 事件、hash chain、快照与校验恢复；只提供状态底座，状态机、任务节点、重试、终态、记忆等业务语义不纳入 Foundation。</li>
 <li><strong>人类报告线</strong>（FND-FR-004，FND-ADR-005）：双层合同——机器结果是唯一真源，人类报告由机器结果确定性渲染（Markdown + digest 绑定 + 分级检查），不自由撰写。</li>
+<li><strong>有限封闭语义工具线</strong>（FND-ADR-009）：基线物化 + contentGuard（摘要不符、物化中途变化、守卫检出均失败关闭）、通用只读 chokepoint（允许根集合 + 可选身份谓词）、策略化表面扫描（策略契约 + 注入式自测）、token 上界估算（确定性领域估算原语，无模型/网络/tokenizer 依赖）、通用上限守卫（复用 state-store 事件账与 token-lock，上限与超限策略由消费者配置）。</li>
 </ul>
 <p>三包结构保持、不拆第四包（FND-ADR-007）；制品治理采用 artifact-graph CLI 与版本锁（FND-ADR-006）。</p>
 <h2 id="首版预算">首版预算<a class="headerlink" href="#首版预算" title="Permanent link">&para;</a></h2>
 <ul>
-<li>顶层 Contracts 对象：18 类（完整清单以 <code>packages/skill-family-contracts/src/registry.json</code> 为唯一真源）：project-manifest、profile-descriptor、managed-file-lock、operation-request、operation-result、migration-manifest、adapter-source、report-model、report-binding、host-descriptor、host-registry、host-capability-fact、host-probe-result、adapter-build-manifest、host-operation-plan、host-operation-receipt、state-event-envelope、state-snapshot-metadata；</li>
+<li>顶层 Contracts 对象：20 类（完整清单以 <code>packages/skill-family-contracts/src/registry.json</code> 为唯一真源）：project-manifest、profile-descriptor、managed-file-lock、operation-request、operation-result、migration-manifest、adapter-source、report-model、report-binding、host-descriptor、host-registry、host-capability-fact、host-probe-result、adapter-build-manifest、host-operation-plan、host-operation-receipt、state-event-envelope、state-snapshot-metadata、token-estimate-result、surface-scan-policy；</li>
 <li>Kit 顶层命令：4 个（scaffold、adopt-plan、projection、check）；</li>
 <li>强制机械规则：当前 9 条，预算不超过 20 条，绝对上限 30 条；CR-001 对登记表内全部 Schema 做统一编译；</li>
 <li>叶子包：3 个（skill-family-contracts、skill-family-harness-node、skill-family-engineering-kit）；</li>

package/docs/en/architecture/index.html

@@ -1972,7 +1972,7 @@ Horizontal (attachment surfaces, no new vertical layers):
 <tbody>
 <tr>
 <td>Contracts</td>
-<td>Structure, protocols, error codes, protocol-name registry; 18 top-level object kinds; 9 mandatory rules</td>
+<td>Structure, protocols, error codes, protocol-name registry; 20 top-level object kinds; 9 mandatory rules</td>
 <td>Business-field semantics, domain auditing, remote writes, model generation</td>
 </tr>
 <tr>
@@ -2024,7 +2024,7 @@ Horizontal (attachment surfaces, no new vertical layers):
 <li>Involves artifact relationships / version-lock → artifact-graph.</li>
 <li>Has only one consumer, or has not been proven to repeat across two real consumers → keep it with the consumer; do not expand Foundation.</li>
 </ol>
-<p>Step 8 is the expansion gate: a new component must justify that deleting it would force two or more real consumers to re-implement it, and this must be verified by an independent fixture. The machine-readable version is in <code>docs/agents/architecture-routing.md</code>.</p>
+<p>Step 8 is the expansion gate: a new component must justify that deleting it would force two or more real consumers to re-implement it, and this must be verified by an independent fixture; admission gate 1 additionally requires at least one existing real consumer plus one structurally isomorphic foreseeable consumer (the second consumer need not be live, but its need must be expressible with the same structure; adjustment record in FND-ADR-009). Step 9 is the finite-closed-semantics gate (FND-ADR-001 gate 8): a capability carrying limited domain semantics must satisfy either — its semantics are covered by a small stable closed enumeration, or it is a deterministic estimation primitive whose algorithm, scope, and bias direction are declared in the contract; this gate does not cancel gate 2's "semantics-free" veto. The machine-readable version is in <code>docs/agents/architecture-routing.md</code>.</p>
 <h2 id="Trust-and-Side-Effect-Boundaries">Trust and Side-Effect Boundaries<a class="headerlink" href="#Trust-and-Side-Effect-Boundaries" title="Permanent link">&para;</a></h2>
 <p>Foundation's trust assumptions and side-effect conventions are solidified per layer; callers judge risk accordingly:</p>
 <ul>
@@ -2050,6 +2050,14 @@ Involves tasks/retries/rework/acceptance? ──yes──▶ loop-agent
 Involves artifact relationships/version-lock? ──yes──▶ artifact-graph
         │no
 Only one consumer / not proven across two real consumers? ──yes──▶ keep with consumer, do not expand
+        │no
+Carries limited domain semantics? ──yes──▶ finite closed semantics: covered by a
+         │                stable closed enumeration, or a deterministic estimation
+         │                primitive (algorithm/scope/bias declared in the contract)
+         │                → admissible; otherwise keep with consumer
+         │                (FND-ADR-001 gate 8; does not cancel gate 2's veto)
+         │no
+        ──▶ admissible
 </code></pre>
 <h2 id="Routing-Relationships-with-External-Projects">Routing Relationships with External Projects<a class="headerlink" href="#Routing-Relationships-with-External-Projects" title="Permanent link">&para;</a></h2>
 <p>Foundation is not an all-powerful base. The following responsibilities are explicitly outside Foundation:</p>
@@ -2066,11 +2074,12 @@ Only one consumer / not proven across two real consumers? ──yes──▶ kee
 <li><strong>Host-access line</strong> (FND-FR-001/FND-FR-002, FND-ADR-003): Contracts registers descriptor/source/manifest/probe/plan/receipt; Harness implements generic source closure, atomic build/materialize, and probe classification; Kit injects the concrete Profile and trusted driver. Currently only describe/build/probe/plan are supported; <code>apply</code> is stably refused; install/uninstall/update are unimplemented.</li>
 <li><strong>Durable state-substrate line</strong> (FND-FR-003, FND-ADR-004): append-only events, hash chain, snapshots, and verification recovery; provides only the state substrate, not business semantics such as state machines, task nodes, retries, terminal states, or memory.</li>
 <li><strong>Human-report line</strong> (FND-FR-004, FND-ADR-005): a two-layer contract — machine results are the sole source of truth, and the human report is deterministically rendered from machine results (Markdown + digest binding + graded checks), not freely authored.</li>
+<li><strong>Finite-closed-semantics tools line</strong> (FND-ADR-009): baseline materialization + contentGuard (digest mismatch, mid-materialization change, and guard rejection all fail closed), generic read chokepoint (allowed-root set + optional identity predicate), strategy-driven surface scan (policy contract + injection self-test), token upper-bound estimation (deterministic estimation primitive with no model/network/tokenizer dependency), and a generic upper-bound guard (reusing the state-store event ledger and token-lock; the bound and over-limit policy are consumer-configured).</li>
 </ul>
 <p>The three-package structure is preserved and a fourth package is not split out (FND-ADR-007); artifact governance uses the artifact-graph CLI and version-lock (FND-ADR-006).</p>
 <h2 id="First-Version-Budget">First-Version Budget<a class="headerlink" href="#First-Version-Budget" title="Permanent link">&para;</a></h2>
 <ul>
-<li>Top-level Contracts objects: 18 kinds (the complete list uses <code>packages/skill-family-contracts/src/registry.json</code> as the sole source of truth): project-manifest, profile-descriptor, managed-file-lock, operation-request, operation-result, migration-manifest, adapter-source, report-model, report-binding, host-descriptor, host-registry, host-capability-fact, host-probe-result, adapter-build-manifest, host-operation-plan, host-operation-receipt, state-event-envelope, state-snapshot-metadata;</li>
+<li>Top-level Contracts objects: 20 kinds (the complete list uses <code>packages/skill-family-contracts/src/registry.json</code> as the sole source of truth): project-manifest, profile-descriptor, managed-file-lock, operation-request, operation-result, migration-manifest, adapter-source, report-model, report-binding, host-descriptor, host-registry, host-capability-fact, host-probe-result, adapter-build-manifest, host-operation-plan, host-operation-receipt, state-event-envelope, state-snapshot-metadata, token-estimate-result, surface-scan-policy;</li>
 <li>Kit top-level commands: 4 (scaffold, adopt-plan, projection, check);</li>
 <li>Mandatory mechanical rules: currently 9, budget not exceeding 20, absolute ceiling 30; CR-001 uniformly compiles all Schemas within the registry;</li>
 <li>Leaf packages: 3 (skill-family-contracts, skill-family-harness-node, skill-family-engineering-kit);</li>

package/docs/en/migration/index.html

@@ -2113,9 +2113,9 @@
   ],
   "targetProfile": "generic",
   "foundationPackages": [
-    { "name": "skill-family-contracts", "version": "0.2.1", "digest": "sha256:<64 hex digits>" },
-    { "name": "skill-family-harness-node", "version": "0.2.1", "digest": "sha256:<64 hex digits>" },
-    { "name": "skill-family-engineering-kit", "version": "0.2.1", "digest": "sha256:<64 hex digits>" }
+    { "name": "skill-family-contracts", "version": "0.3.0", "digest": "sha256:<64 hex digits>" },
+    { "name": "skill-family-harness-node", "version": "0.3.0", "digest": "sha256:<64 hex digits>" },
+    { "name": "skill-family-engineering-kit", "version": "0.3.0", "digest": "sha256:<64 hex digits>" }
   ],
   "verification": {
     "unit": "docs/evidence/unit.json",
@@ -2126,6 +2126,7 @@
 }
 </code></pre>
 <p>The structure above shows the core fields of the migration manifest; each <code>legacyInfra</code> entry gives the legacy-implementation path and its replacement; the tool only read-only evaluates existence and never deletes on its behalf.</p>
+<p>The Quickstart Profile candidate moves to v2 in 0.3.0. A migration manifest that binds candidate capabilities must pin all three Foundation packages to exactly 0.3.0; an existing integration that still requires v1 must keep all three packages pinned to exactly 0.2.1 and must not mix the two sets.</p>
 <ul>
 <li><code>legacyInfra</code>: each entry gives the legacy-implementation path and its replacement; the tool only read-only evaluates existence and never deletes on its behalf.</li>
 <li><code>exceptions</code> are <strong>temporary exceptions</strong>: must simultaneously contain all four fields — owner, reason, deadline, and migrationTarget — and missing any field counts as a conflict (plan failure); expired exceptions are not auto-renewed and persistently block the completion judgment.</li>

package/docs/en/recipes/adopt-existing-repository/index.html

@@ -1903,7 +1903,7 @@
 <li>Trust boundary: <code>adopt-plan</code> makes zero byte changes to the input repository; legacy-implementation deletion is the caller's responsibility, and the tool never deletes on its behalf.</li>
 </ul>
 <h2 id="4-Minimal-Command">4. Minimal Command<a class="headerlink" href="#4-Minimal-Command" title="Permanent link">&para;</a></h2>
-<pre><code class="language-sh">npm install --save-dev skill-family-engineering-kit@0.2.1
+<pre><code class="language-sh">npm install --save-dev skill-family-engineering-kit@0.3.0
 npm exec -- skill-family-kit adopt-plan --root &lt;repo&gt;
 </code></pre>
 <h2 id="5-Expected-Output-and-Evidence">5. Expected Output and Evidence<a class="headerlink" href="#5-Expected-Output-and-Evidence" title="Permanent link">&para;</a></h2>
@@ -1926,6 +1926,7 @@ npm exec -- skill-family-kit check --root fixtures/m0-consumer
 <ul>
 <li><code>adopt-plan</code> is read-only, has no write risk, and needs no rollback.</li>
 <li>Actual disk writes are performed by <code>scaffold</code>/<code>projection</code>; rollback relies on the dual-digest binding of <code>adoptionProof</code> and <code>foundationPlanDigest</code>; an overwrite action that does not declare the <code>expect.sha256</code> pre-state is refused at the <code>projection</code> stage.</li>
+<li>When adopting the Quickstart Profile candidate, pin all three packages to one profile: 0.3.0 for v2 or 0.2.1 for v1. Do not mix them.</li>
 </ul>
 
 

package/docs/en/recipes/domain-schema-validation/index.html

@@ -1895,6 +1895,7 @@
 <h2 id="1-Scenario-and-Non-Scenario">1. Scenario and Non-Scenario<a class="headerlink" href="#1-Scenario-and-Non-Scenario" title="Permanent link">&para;</a></h2>
 <p>Applicable: you need to validate whether a document conforms to a Foundation-registered contract object (e.g., project-manifest), choosing a validation strategy by dialect.</p>
 <p>Not applicable: needs to validate the consumer's own business Schema (the consumer should hold it itself; Foundation does not replace it); needs to mix domain-semantic validation into the generic contract.</p>
+<p>Quickstart Profile v2 is a separate candidate path. The consumer still owns its business schemas; Engineering Kit only compiles an explicit schema collection into offline validators selected by <code>$id</code>, and does not own the method-to-schema choice.</p>
 <h2 id="2-Architecture-Choice-and-Capability-ID">2. Architecture Choice and Capability ID<a class="headerlink" href="#2-Architecture-Choice-and-Capability-ID" title="Permanent link">&para;</a></h2>
 <p>Preferred capability: <code>foundation.contracts.object-validation</code> (<code>validateDocument</code> / <code>compileSchema</code> / <code>detectDialect</code>). A pure Ajv implementation, supporting draft-07 and 2020-12.</p>
 <h2 id="3-Preconditions-and-Trust-Boundary">3. Preconditions and Trust Boundary<a class="headerlink" href="#3-Preconditions-and-Trust-Boundary" title="Permanent link">&para;</a></h2>
@@ -1945,8 +1946,9 @@ if (!bad.valid) console.error(bad.errorCode); // SFC1002
 </ul>
 <h2 id="9-Upgrade-and-Rollback-Notes">9. Upgrade and Rollback Notes<a class="headerlink" href="#9-Upgrade-and-Rollback-Notes" title="Permanent link">&para;</a></h2>
 <ul>
-<li>The contract authority version <code>CONTRACTS_VERSION = 1.4.0</code>, and the npm package version <code>0.2.1</code> run in parallel and are not mixed.</li>
+<li>The contract authority version <code>CONTRACTS_VERSION = 1.4.0</code>, and the npm package version <code>0.3.0</code> run in parallel and are not mixed.</li>
 <li>Error codes are frozen and do not drift; Schema changes are handled as a new contract-version task, not by modifying frozen content in place.</li>
+<li>Candidate v2 must be pinned to exactly 0.3.0; integrations that still require v1 must remain pinned to exactly 0.2.1.</li>
 </ul>
 
 

package/docs/en/recipes/index.html

@@ -1770,13 +1770,14 @@
 <li>Need durable events and derived snapshots → see <code>durable-local-state</code>.</li>
 <li>Need an existing-repository adoption inventory → see <code>adopt-existing-repository</code>.</li>
 <li>Need a text-resource closure or host access → see <code>adapter-text-closure</code> / <code>host-profile-integration</code>.</li>
+<li>Need to trial Quickstart Profile v2 → pin the 0.3.0 candidate subpaths of all three packages exactly; remain on exactly 0.2.1 when v1 is still required.</li>
 </ul>
 <h2 id="Common-Verification-Conventions">Common Verification Conventions<a class="headerlink" href="#Common-Verification-Conventions" title="Permanent link">&para;</a></h2>
 <ul>
 <li>All examples run in a <strong>new system temp directory</strong>, leaving no personal paths or credentials.</li>
 <li>Examples contain no enterprise identifiers, private Profiles, real business data, or personal paths.</li>
 <li>Each recipe gives at least one positive case and one negative case; the negative case must produce a stable failure code or refusal.</li>
-<li>Verification commands can be copied and run directly; when a package is needed, first <code>npm install</code> the corresponding <code>@0.2.1</code>.</li>
+<li>Verification commands can be copied and run directly; when a package is needed, first <code>npm install</code> the corresponding <code>@0.3.0</code>.</li>
 </ul>
 <h2 id="Capability-ID-Overview">Capability ID Overview<a class="headerlink" href="#Capability-ID-Overview" title="Permanent link">&para;</a></h2>
 <table>

package/docs/en/reference/api/index.html

@@ -1292,6 +1292,17 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#Quickstart-Profile-v2-Candidate" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        Quickstart Profile v2 Candidate
+
+    </span>
+  </a>
+
 </li>
 
         <li class="md-nav__item">
@@ -1759,6 +1770,17 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#Quickstart-Profile-v2-Candidate" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        Quickstart Profile v2 Candidate
+
+    </span>
+  </a>
+
 </li>
 
         <li class="md-nav__item">
@@ -1848,6 +1870,8 @@
 <li>Engineering Kit keeps exactly four top-level commands: <code>scaffold</code>, <code>adopt-plan</code>, <code>projection</code>, and <code>check</code>. Each command retains its documented read-only or controlled-write boundary.</li>
 <li>Candidate capabilities are marked <code>stability: candidate</code> in the catalog. Their presence in the public package does not promote them to the stable surface.</li>
 </ul>
+<h2 id="Quickstart-Profile-v2-Candidate">Quickstart Profile v2 Candidate<a class="headerlink" href="#Quickstart-Profile-v2-Candidate" title="Permanent link">&para;</a></h2>
+<p>All three packages expose v2 through their existing candidate subpaths. Contracts defines the business-neutral <code>execute-method</code> exchange, Harness verifies bytes and bindings, and Kit turns explicit consumer schemas into an offline Bundle with standalone validators selected by schema <code>$id</code>. Version 0.3.0 candidate v2 is incompatible with the 0.2.1 candidate v1; consumers must pin the selected package versions exactly.</p>
 <h2 id="Detailed-Package-Pages">Detailed Package Pages<a class="headerlink" href="#Detailed-Package-Pages" title="Permanent link">&para;</a></h2>
 <p>The current signature-level package pages are maintained in Chinese because they enumerate every verified export and test reference:</p>
 <ul>

package/docs/en/reference/compatibility/index.html

@@ -1216,6 +1216,17 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#Quickstart-Profile-Candidate-Compatibility" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        Quickstart Profile Candidate Compatibility
+
+    </span>
+  </a>
+
 </li>
 
         <li class="md-nav__item">
@@ -1748,6 +1759,17 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#Quickstart-Profile-Candidate-Compatibility" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        Quickstart Profile Candidate Compatibility
+
+    </span>
+  </a>
+
 </li>
 
         <li class="md-nav__item">
@@ -1840,33 +1862,56 @@
 <tbody>
 <tr>
 <td><code>skill-family-contracts</code></td>
-<td>0.2.1</td>
+<td>0.3.0</td>
 <td>Contracts 1.4.0 machine contracts</td>
 <td>Public release target (private: false)</td>
 </tr>
 <tr>
 <td><code>skill-family-harness-node</code></td>
-<td>0.2.1</td>
+<td>0.3.0</td>
 <td>Node thin-mechanism runtime of Contracts</td>
 <td>Public release target</td>
 </tr>
 <tr>
 <td><code>skill-family-engineering-kit</code></td>
-<td>0.2.1</td>
+<td>0.3.0</td>
 <td>Four engineering commands (CLI <code>skill-family-kit</code>)</td>
 <td>Public release target</td>
 </tr>
 <tr>
 <td>Workspace repository</td>
-<td>0.2.1</td>
+<td>0.3.0</td>
 <td>Private parent workspace (private: true)</td>
 <td>Development source of truth only</td>
 </tr>
 </tbody>
 </table>
 <blockquote>
-<p>The contract authority version (<code>CONTRACTS_VERSION</code>) is <code>1.4.0</code>, and the npm package version is <code>0.2.1</code>; the two version lines run in parallel and are not mixed.</p>
+<p>The contract authority version (<code>CONTRACTS_VERSION</code>) is <code>1.4.0</code>, and the npm package version is <code>0.3.0</code>; the two version lines run in parallel and are not mixed.</p>
 </blockquote>
+<h2 id="Quickstart-Profile-Candidate-Compatibility">Quickstart Profile Candidate Compatibility<a class="headerlink" href="#Quickstart-Profile-Candidate-Compatibility" title="Permanent link">&para;</a></h2>
+<table>
+<thead>
+<tr>
+<th>Package version</th>
+<th>Candidate profile</th>
+<th>Compatibility rule</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>0.2.1</td>
+<td>v1</td>
+<td>Existing integrations may remain pinned to exactly 0.2.1</td>
+</tr>
+<tr>
+<td>0.3.0</td>
+<td>v2</td>
+<td>Uses <code>execute-method</code>, real <code>$id</code> schema resolution, and the offline Bundle; pin exactly 0.3.0</td>
+</tr>
+</tbody>
+</table>
+<p>Version 2 replaces v1 and provides no dual-track compatibility layer. Stable Contracts 1.4.0, the 18 object classes, the kernel protocol, and the error-code registry do not change with the candidate profile.</p>
 <h2 id="Node-Support-Matrix">Node Support Matrix<a class="headerlink" href="#Node-Support-Matrix" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Engine requirement: <code>&gt;=22.22.2 &lt;23</code> (major 22 locked).</li>
@@ -1922,6 +1967,7 @@
 <li><strong>Kit commands</strong>: top-level commands are fixed at 4 (scaffold/adopt-plan/projection/check), not expanded; <code>REFUSED_MUTATION_FLAGS</code> are refused at the CLI entry point.</li>
 <li><strong>Node/pnpm/projen</strong>: follow the exact locks in <code>.foundation/version-lock.json</code> and <code>package.json</code>; upgrades require re-generating the managed projection via <code>pnpm synth</code>.</li>
 <li><strong>Host</strong>: adding a supported host requires registering a descriptor and binding a trusted driver; unsupported hosts (e.g., qoder) are only referenced structurally and not claimed to have been run on.</li>
+<li><strong>Candidate</strong>: a later minor version may change or remove a candidate subpath; do not mix the 0.2.1 v1 packages with the 0.3.0 v2 packages, and pin all three package versions exactly.</li>
 </ul>
 <h2 id="Anti-Compatibility-Boundaries-Explicitly-Unsupported">Anti-Compatibility Boundaries (Explicitly Unsupported)<a class="headerlink" href="#Anti-Compatibility-Boundaries-Explicitly-Unsupported" title="Permanent link">&para;</a></h2>
 <ul>

package/docs/migration/index.html

@@ -2113,9 +2113,9 @@
   ],
   "targetProfile": "generic",
   "foundationPackages": [
-    { "name": "skill-family-contracts", "version": "0.2.1", "digest": "sha256:<64 位十六进制>" },
-    { "name": "skill-family-harness-node", "version": "0.2.1", "digest": "sha256:<64 位十六进制>" },
-    { "name": "skill-family-engineering-kit", "version": "0.2.1", "digest": "sha256:<64 位十六进制>" }
+    { "name": "skill-family-contracts", "version": "0.3.0", "digest": "sha256:<64 位十六进制>" },
+    { "name": "skill-family-harness-node", "version": "0.3.0", "digest": "sha256:<64 位十六进制>" },
+    { "name": "skill-family-engineering-kit", "version": "0.3.0", "digest": "sha256:<64 位十六进制>" }
   ],
   "verification": {
     "unit": "docs/evidence/unit.json",
@@ -2126,6 +2126,7 @@
 }
 </code></pre>
 <p>以上结构展示了迁移清单的核心字段；<code>legacyInfra</code> 每项给出旧实现路径与替代物，工具只读评估存在性，绝不代为删除。</p>
+<p>0.3.0 中的 Quickstart Profile candidate 已升级到 v2。迁移清单若绑定 candidate 能力，三个 Foundation 包必须统一精确锁定为 0.3.0；仍需 v1 的存量接入继续统一锁定 0.2.1，不混装两组版本。</p>
 <ul>
 <li><code>legacyInfra</code> 每项给出旧实现路径与替代物；工具只读评估存在性，绝不代为删除。</li>
 <li><code>exceptions</code> 是<strong>临时例外</strong>：必须同时含负责人（owner）、原因（reason）、截止时间（deadline）、迁移目标（migrationTarget）四项，缺任一字段即计为冲突（计划失败）；到期例外不自动续期，持续阻断完成判定。</li>

package/docs/public/status/index.html

@@ -1792,17 +1792,17 @@
 <tbody>
 <tr>
 <td><code>skill-family-contracts</code></td>
-<td>0.2.1</td>
+<td>0.4.0</td>
 <td><a href="https://github.com/ifoohoo/skill-family-contracts">ifoohoo/skill-family-contracts</a></td>
 </tr>
 <tr>
 <td><code>skill-family-harness-node</code></td>
-<td>0.2.1</td>
+<td>0.4.0</td>
 <td><a href="https://github.com/ifoohoo/skill-family-harness-node">ifoohoo/skill-family-harness-node</a></td>
 </tr>
 <tr>
 <td><code>skill-family-engineering-kit</code></td>
-<td>0.2.1</td>
+<td>0.4.0</td>
 <td><a href="https://github.com/ifoohoo/skill-family-engineering-kit">ifoohoo/skill-family-engineering-kit</a></td>
 </tr>
 </tbody>

package/docs/recipes/adopt-existing-repository/index.html

@@ -1903,7 +1903,7 @@
 <li>信任边界：<code>adopt-plan</code> 对输入仓字节零变化；旧实现删除由调用方负责，工具绝不代为删除。</li>
 </ul>
 <h2 id="4-最小命令">4. 最小命令<a class="headerlink" href="#4-最小命令" title="Permanent link">&para;</a></h2>
-<pre><code class="language-sh">npm install --save-dev skill-family-engineering-kit@0.2.1
+<pre><code class="language-sh">npm install --save-dev skill-family-engineering-kit@0.3.0
 npm exec -- skill-family-kit adopt-plan --root &lt;repo&gt;
 </code></pre>
 <h2 id="5-预期输出与证据">5. 预期输出与证据<a class="headerlink" href="#5-预期输出与证据" title="Permanent link">&para;</a></h2>
@@ -1926,6 +1926,7 @@ npm exec -- skill-family-kit check --root fixtures/m0-consumer
 <ul>
 <li><code>adopt-plan</code> 只读，无写风险，无需回滚。</li>
 <li>真正落盘由 <code>scaffold</code>/<code>projection</code> 执行，回滚以 <code>adoptionProof</code> 与 <code>foundationPlanDigest</code> 双摘要绑定为准；未声明 <code>expect.sha256</code> 前置状态的覆盖动作在 <code>projection</code> 阶段即拒绝。</li>
+<li>若采用 Quickstart Profile candidate，三个包按同一 profile 精确锁定：v2 使用 0.3.0，v1 继续使用 0.2.1，不混装。</li>
 </ul>
 
 

package/docs/recipes/domain-schema-validation/index.html

@@ -1895,6 +1895,7 @@
 <h2 id="1-场景与非场景">1. 场景与非场景<a class="headerlink" href="#1-场景与非场景" title="Permanent link">&para;</a></h2>
 <p>适用：需要校验一份文档是否符合 Foundation 已登记的契约对象（如 project-manifest），按方言选择校验策略。</p>
 <p>不适用：需要校验消费者自有业务 Schema（消费者应自行持有，Foundation 不取代）；需要把领域语义校验混入通用契约。</p>
+<p>Quickstart Profile v2 是单独的 candidate 路径。消费者仍拥有业务 Schema；Engineering Kit 只在构建阶段把显式 Schema 集合编译成按 <code>$id</code> 查询的离线 validator，不接管 method 到 Schema 的选择。</p>
 <h2 id="2-架构选择及能力-ID">2. 架构选择及能力 ID<a class="headerlink" href="#2-架构选择及能力-ID" title="Permanent link">&para;</a></h2>
 <p>首选能力：<code>foundation.contracts.object-validation</code>（<code>validateDocument</code> / <code>compileSchema</code> / <code>detectDialect</code>）。纯 Ajv 实现，支持 draft-07 与 2020-12。</p>
 <h2 id="3-前置条件与信任边界">3. 前置条件与信任边界<a class="headerlink" href="#3-前置条件与信任边界" title="Permanent link">&para;</a></h2>
@@ -1945,8 +1946,9 @@ if (!bad.valid) console.error(bad.errorCode); // SFC1002
 </ul>
 <h2 id="9-升级与回滚注意事项">9. 升级与回滚注意事项<a class="headerlink" href="#9-升级与回滚注意事项" title="Permanent link">&para;</a></h2>
 <ul>
-<li>契约权威版本 <code>CONTRACTS_VERSION = 1.4.0</code>，npm 包版本 <code>0.2.1</code> 并行，不混用。</li>
+<li>契约权威版本 <code>CONTRACTS_VERSION = 1.4.0</code>，npm 包版本 <code>0.3.0</code> 并行，不混用。</li>
 <li>错误码冻结不漂移；Schema 变更作为新的合同版本任务进行，不就地改冻结内容。</li>
+<li>candidate v2 必须精确锁定 0.3.0；仍需 v1 的接入继续精确锁定 0.2.1。</li>
 </ul>
 
 

package/docs/recipes/index.html

@@ -1770,13 +1770,14 @@
 <li>需要持久事件与派生快照 → 看 <code>durable-local-state</code>。</li>
 <li>需要存量采用盘点 → 看 <code>adopt-existing-repository</code>。</li>
 <li>需要文本资源闭包或宿主接入 → 看 <code>adapter-text-closure</code> / <code>host-profile-integration</code>。</li>
+<li>需要试用 Quickstart Profile v2 → 精确锁定三个包的 0.3.0 candidate 子路径；需要 v1 时继续锁定 0.2.1。</li>
 </ul>
 <h2 id="共同验证约定">共同验证约定<a class="headerlink" href="#共同验证约定" title="Permanent link">&para;</a></h2>
 <ul>
 <li>所有示例在<strong>新的系统临时目录</strong>执行，不留个人路径或凭据。</li>
 <li>示例不含企业标识、私有 Profile、真实业务数据或个人路径。</li>
 <li>每个 recipe 至少给出一个正例与一个负例；负例必须产生稳定失败码或拒绝。</li>
-<li>验证命令可直接复制运行；需要包时先 <code>npm install</code> 对应 <code>@0.2.1</code>。</li>
+<li>验证命令可直接复制运行；需要包时先 <code>npm install</code> 对应 <code>@0.3.0</code>。</li>
 </ul>
 <h2 id="能力-ID-总览">能力 ID 总览<a class="headerlink" href="#能力-ID-总览" title="Permanent link">&para;</a></h2>
 <table>

package/docs/reference/api/contracts/index.html

@@ -894,6 +894,17 @@
       </ul>
     </nav>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#Quickstart-Profile-v2-candidate" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        Quickstart Profile v2 candidate
+
+    </span>
+  </a>
+
 </li>
 
         <li class="md-nav__item">
@@ -2140,6 +2151,17 @@
       </ul>
     </nav>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#Quickstart-Profile-v2-candidate" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        Quickstart Profile v2 candidate
+
+    </span>
+  </a>
+
 </li>
 
         <li class="md-nav__item">
@@ -2468,6 +2490,10 @@
 <li>调用方仍拥有的业务语义：审计语义结论（接受/拒绝属外部独立审阅）。</li>
 </ul>
 <hr />
+<h2 id="Quickstart-Profile-v2-candidate">Quickstart Profile v2 candidate<a class="headerlink" href="#Quickstart-Profile-v2-candidate" title="Permanent link">&para;</a></h2>
+<p><code>skill-family-contracts/candidate/quickstart-profile</code> 导出 v2 协议、按真实 <code>$id</code> 索引的 Resource/Task/Result Schema 集合，以及 <code>validateQuickstartProfileDocument</code>。唯一操作名是业务中立的 <code>execute-method</code>；Foundation 不登记 method 词表，也不解释 parameters、evidence 或 domainResult 的领域含义。</p>
+<p>该入口从 <code>0.2.1</code> 起公开，但稳定性仍为 <code>candidate</code>。0.3.0 已用 v2 替换 v1，两者不兼容：新接入需精确锁定 <code>0.3.0</code>，仍需 v1 的接入继续精确锁定 <code>0.2.1</code>。candidate Schema 不进入稳定 <code>src/registry.json</code>。</p>
+<hr />
 <h2 id="与机器事实层的互链">与机器事实层的互链<a class="headerlink" href="#与机器事实层的互链" title="Permanent link">&para;</a></h2>
 <ul>
 <li>能力稳定 ID 见 <code>docs/agents/capability-catalog.json</code>（<code>foundation.contracts.*</code>）。</li>

package/docs/reference/api/engineering-kit/index.html

@@ -999,6 +999,17 @@
       </ul>
     </nav>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#Quickstart-Profile-v2-candidate" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        Quickstart Profile v2 candidate
+
+    </span>
+  </a>
+
 </li>
 
         <li class="md-nav__item">
@@ -2242,6 +2253,17 @@
       </ul>
     </nav>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#Quickstart-Profile-v2-candidate" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        Quickstart Profile v2 candidate
+
+    </span>
+  </a>
+
 </li>
 
         <li class="md-nav__item">
@@ -2487,6 +2509,10 @@
 </ul>
 <p>Kit 错误类型：<code>KitError extends ContractsError</code>（构造未登记码立即抛 <code>TypeError</code>）；<code>KIT_ERROR_KINDS</code> 为稳定 kind 枚举；<code>kitError</code> / <code>invalidParamsError</code> / <code>unknownCommandError</code> / <code>mutationModeError</code> / <code>refusalError</code> 为构造辅助。<code>REFUSED_MUTATION_FLAGS</code> 列出入口即拒的变更旗标（如 <code>--apply</code>）。</p>
 <hr />
+<h2 id="Quickstart-Profile-v2-candidate">Quickstart Profile v2 candidate<a class="headerlink" href="#Quickstart-Profile-v2-candidate" title="Permanent link">&para;</a></h2>
+<p><code>skill-family-engineering-kit/candidate/quickstart-profile</code> 导出 <code>buildQuickstartProfileProjection</code> 与 <code>QUICKSTART_PROFILE_TARGET_PREFIX</code>。builder 接收显式消费者 Schema 路径与冻结来源身份，生成按 Schema <code>$id</code> 查询的 standalone validator、机械投影的 Contracts/Harness runtime、许可证和完整 provenance。</p>
+<p>Bundle 离线运行时不需要 Foundation 包、<code>node_modules</code> 或 Ajv。builder 只返回稳定 projection manifest，不写目标文件，也不增加第五个 Kit 顶层命令；调用方仍需把 manifest 交给 <code>runProjection</code> 完成授权写入。0.3.0 的 v2 与 0.2.1 的依赖闭包 Bundle 不兼容，必须精确锁定版本。</p>
+<hr />
 <h2 id="与机器事实层的互链">与机器事实层的互链<a class="headerlink" href="#与机器事实层的互链" title="Permanent link">&para;</a></h2>
 <ul>
 <li>能力稳定 ID 见 <code>docs/agents/capability-catalog.json</code>（<code>foundation.kit.*</code>、<code>foundation.unsupported.*</code>）。</li>