skill-family-engineering-kit 0.2.1 → 0.3.0

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.3.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.3.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.3.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>

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

@@ -972,6 +972,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">
@@ -2416,7 +2438,7 @@
 <li>纯函数：是（无时钟、无环境、无网络、无模型调用）。</li>
 <li>副作用：无文件/Git/网络。</li>
 <li>稳定错误码与 <code>details.kind</code>：<code>SFC3001</code>（<code>REPORT_DIGEST_MISMATCH</code>，绑定摘要不符或报告非模型规范渲染）、<code>SFC3002</code>（<code>REPORT_ELEMENT_MISSING</code>，强制元素缺失）、<code>SFC3003</code>（<code>REPORT_FACT_DRIFT</code>，报告改写绑定结果事实或字节与确定性再渲染不一致）。风格告警由 <code>collectStyleWarnings</code> 产出，仅建议、不编码、不阻断。</li>
-<li>前置条件与信任锚：<code>REPORT_RENDERER_NAME</code> / <code>VERSION</code> 取自各自 package（当前 <code>0.2.1</code>）；双输出成组写入并拒绝路径别名与输入覆盖。</li>
+<li>前置条件与信任锚：<code>REPORT_RENDERER_NAME</code> / <code>VERSION</code> 取自各自 package（当前 <code>0.3.0</code>）；双输出成组写入并拒绝路径别名与输入覆盖。</li>
 <li><code>since</code> / <code>stability</code>：<code>0.2.0</code> / <code>stable</code>。</li>
 <li>源文件：<code>packages/skill-family-harness-node/src/report.mjs</code>。</li>
 <li>正例/负例测试：<code>packages/skill-family-harness-node/test/report.test.mjs</code>。</li>
@@ -2544,6 +2566,10 @@
 </tbody>
 </table>
 <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-harness-node/candidate/quickstart-profile</code> 负责创建 observation Resource、Task 与终态 Result，并复验真实文件字节、Resource id 全局唯一性、Task digest、operation 身份、逐字段 <code>run/stage/attempt</code> 以及 evidence 精确回指。<code>verifyQuickstartExchange</code> 把机制拒绝转换成结构化结果，抛出式入口继续使用已登记的 <code>SFC2004</code> 与稳定 <code>details.kind</code>。</p>
+<p>该入口不选择 method，不解释 domainResult，也不拥有重试、调度或生命周期。0.3.0 的 v2 与 0.2.1 的 v1 不兼容；接入必须精确锁定所选版本。</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.harness.*</code>）。</li>

package/docs/reference/api/index.html

@@ -671,6 +671,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>
 
     </ul>
@@ -1737,6 +1748,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>
 
     </ul>
@@ -1796,8 +1818,10 @@
 <ul>
 <li>机制失败统一 <code>SFC2004</code>（<code>EXECUTION_FAILED</code>），由 <code>details.kind</code> 区分（<code>HARNESS_ERROR_KINDS</code> 冻结枚举）；Contracts 校验失败（<code>SFC1001</code> / <code>SFC1002</code>）经 <code>validateDocument</code> 返回值表达、不抛异常。</li>
 <li>Kit 顶层命令集合固定为 4 个（<code>scaffold</code> / <code>adopt-plan</code> / <code>projection</code> / <code>check</code>），不扩张；<code>host apply</code> / <code>install</code> / <code>update</code> / <code>uninstall</code>、Qoder 完整 driver、二进制 adapter source、远端发布、业务状态机、模型编排、领域审计语义均明确 unsupported。</li>
-<li>所有版本字段从 <code>package.json</code> 与 Contracts 真源生成或由 fact-check 校验；<code>CONTRACTS_VERSION=1.4.0</code> 与 npm 包版本 <code>0.2.1</code> 并行。</li>
+<li>所有版本字段从 <code>package.json</code> 与 Contracts 真源生成或由 fact-check 校验；<code>CONTRACTS_VERSION=1.4.0</code> 与 npm 包版本 <code>0.3.0</code> 并行。</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>三个包都通过既有 candidate 子路径公开 Quickstart Profile v2。Contracts 定义 <code>execute-method</code> 交换结构，Harness 复验字节和绑定，Kit 从显式消费者 Schema 生成离线 Bundle。该能力仍标记为 <code>candidate</code>，0.3.0 的 v2 与 0.2.1 的 v1 不兼容；消费者必须精确锁定所选包版本。</p>