skill-family-engineering-kit 0.5.0 → 0.7.0

package/docs/en/migration/index.html

@@ -1194,22 +1194,22 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#Ten-Field-Hand-off-Draft" class="md-nav__link">
+  <a href="#Profile-Draft" class="md-nav__link">
     <span class="md-ellipsis">
 
-        Ten-Field Hand-off Draft
+        Profile Draft
 
     </span>
   </a>
 
-    <nav class="md-nav" aria-label="Ten-Field Hand-off Draft">
+    <nav class="md-nav" aria-label="Profile Draft">
       <ul class="md-nav__list">
 
           <li class="md-nav__item">
-  <a href="#INCOMPLETE-Blocking-Rules" class="md-nav__link">
+  <a href="#Incompleteness-Blocking-Rules" class="md-nav__link">
     <span class="md-ellipsis">
 
-        INCOMPLETE Blocking Rules
+        Incompleteness Blocking Rules
 
     </span>
   </a>
@@ -1228,10 +1228,10 @@
 </li>
 
           <li class="md-nav__item">
-  <a href="#Rendering-Boundary" class="md-nav__link">
+  <a href="#Boundary" class="md-nav__link">
     <span class="md-ellipsis">
 
-        Rendering Boundary
+        Boundary
 
     </span>
   </a>
@@ -1923,22 +1923,22 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#Ten-Field-Hand-off-Draft" class="md-nav__link">
+  <a href="#Profile-Draft" class="md-nav__link">
     <span class="md-ellipsis">
 
-        Ten-Field Hand-off Draft
+        Profile Draft
 
     </span>
   </a>
 
-    <nav class="md-nav" aria-label="Ten-Field Hand-off Draft">
+    <nav class="md-nav" aria-label="Profile Draft">
       <ul class="md-nav__list">
 
           <li class="md-nav__item">
-  <a href="#INCOMPLETE-Blocking-Rules" class="md-nav__link">
+  <a href="#Incompleteness-Blocking-Rules" class="md-nav__link">
     <span class="md-ellipsis">
 
-        INCOMPLETE Blocking Rules
+        Incompleteness Blocking Rules
 
     </span>
   </a>
@@ -1957,10 +1957,10 @@
 </li>
 
           <li class="md-nav__item">
-  <a href="#Rendering-Boundary" class="md-nav__link">
+  <a href="#Boundary" class="md-nav__link">
     <span class="md-ellipsis">
 
-        Rendering Boundary
+        Boundary
 
     </span>
   </a>
@@ -2196,83 +2196,28 @@
 <li><strong>Rollback relies on evidence</strong>: before adoption writes to disk, a dual-digest binding of <code>adoptionProof</code> and <code>foundationPlanDigest</code> must exist first; on rollback, the plan write set's <code>expect.sha256</code> pre-state is used to restore; an overwrite action that does not declare its pre-state is refused at the <code>projection</code> stage.</li>
 <li><strong>fail-closed default</strong>: any unparseable, out-of-bounds, identity-mismatched, or evidence-missing input makes the corresponding judgment unproven; success is not assumed.</li>
 </ul>
-<h2 id="Ten-Field-Hand-off-Draft">Ten-Field Hand-off Draft<a class="headerlink" href="#Ten-Field-Hand-off-Draft" title="Permanent link">&para;</a></h2>
-<p><code>adopt-plan</code> output carries a <code>handoffDraft</code> sub-block (kind=<code>skill-family.handoff-draft</code>, schemaVersion=1), providing structured data draft for the planner-side ten-field hand-off. Field sources are only two kinds: <code>derived</code> (mechanically derivable from read-only evidence) and <code>INCOMPLETE</code> (not mechanically derivable, never guessed). The ten fields correspond one-to-one with the source constant <code>HANDOFF_FIELDS</code>:</p>
-<table>
-<thead>
-<tr>
-<th>id</th>
-<th>Field name</th>
-<th>Source</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>1</td>
-<td><code>project-identity</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>2</td>
-<td><code>repository-state</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>3</td>
-<td><code>foundation-binding</code></td>
-<td>derived (manifest declared binding) / INCOMPLETE (no manifest declared)</td>
-</tr>
-<tr>
-<td>4</td>
-<td><code>write-set-policy</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>5</td>
-<td><code>legacy-exits</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>6</td>
-<td><code>business-logic-to-keep</code></td>
-<td>always INCOMPLETE</td>
-</tr>
-<tr>
-<td>7</td>
-<td><code>plan-summary</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>8</td>
-<td><code>verification-entries</code></td>
-<td>derived (all four classes of evidence proven) / INCOMPLETE (any unproven)</td>
-</tr>
-<tr>
-<td>9</td>
-<td><code>legacy-removal-recovery</code></td>
-<td>always INCOMPLETE</td>
-</tr>
-<tr>
-<td>10</td>
-<td><code>authorization-status</code></td>
-<td>derived (commit/push/tag/publish always false)</td>
-</tr>
-</tbody>
-</table>
-<h3 id="INCOMPLETE-Blocking-Rules">INCOMPLETE Blocking Rules<a class="headerlink" href="#INCOMPLETE-Blocking-Rules" title="Permanent link">&para;</a></h3>
+<h2 id="Profile-Draft">Profile Draft<a class="headerlink" href="#Profile-Draft" title="Permanent link">&para;</a></h2>
+<p><code>adopt-plan</code> output carries a <code>profileDraft</code> sub-block (kind=<code>skill-family.profile-draft</code>, schemaVersion=1): a pre-filled profile.json descriptor draft (<code>descriptorRelPath</code>=<code>profile.json</code>). The adoption-lock concept and its artifact form are deprecated (remediation handoff D-8): the lightweight adoption proof is the descriptor's own adoption declaration, machine-verified by <code>verifyProfile</code> (Profile SPI v2) — field completeness and pin format are schema-checked at the descriptor step (SPE1001), pin digests are compared against the real artifact bytes inside the write set per GK-4 discipline (SPE1006), and the tightening-only overrides policy is adjudicated separately (SPE1007).</p>
+<p>The draft pre-fills everything mechanically derivable from read-only facts:</p>
+<ul>
+<li>Descriptor identity and base: <code>profile.id</code>/<code>profile.name</code> come from the plan inputs, <code>base.contractsVersion</code> is the loaded frozen contracts version; <code>differences</code>/<code>spi</code> start as empty arrays.</li>
+<li>The adoption declaration (D-8 minimal field set, authoritative definition in <code>adoptionDeclaration</code> of <code>profiles/spi/extension-spi.json</code>):</li>
+<li><code>foundation_profile.id</code> is the adopted foundation profile id from the plan inputs; <code>version</code>/<code>stability</code> are human decisions and stay null.</li>
+<li><code>foundation_pin.algorithm</code> is always <code>sha256</code>; the three foundation packages' <code>version</code> values are pre-filled manifest-declaration-first, then from loaded constants; <code>path</code>/<code>sha256</code> stay null until real artifacts are placed in the profile write set (a digest comes only from real bytes, never guessed).</li>
+<li><code>adopted_at</code> is fixed at adoption time, never at planning time, and stays null.</li>
+<li><code>overrides</code> is an empty array (the empty example): overrides are opt-in self-tightening declarations, and the kit never enumerates rule examples (the core never imports the profile layer); the draft carries <code>overridesGuidance</code> explaining the tightening-only semantics.</li>
+</ul>
+<h3 id="Incompleteness-Blocking-Rules">Incompleteness Blocking Rules<a class="headerlink" href="#Incompleteness-Blocking-Rules" title="Permanent link">&para;</a></h3>
 <ul>
-<li>Any INCOMPLETE field makes <code>ready=false</code>: a draft with gaps must not enter the hand-off.</li>
-<li>The tool never guesses mechanically-undeterminable fields:</li>
-<li><code>business-logic-to-keep</code> and <code>legacy-removal-recovery</code> are <strong>always INCOMPLETE</strong> and must be provided by a human owner; the tool has no basis to derive them;</li>
-<li><code>foundation-binding</code> is INCOMPLETE when no migration manifest declares (<code>foundationPackages</code>) it, counting only the manifest-declared binding;</li>
-<li><code>verification-entries</code> is INCOMPLETE when any of the four classes of evidence (unit/integration/consumer/independentAudit) is not proven.</li>
+<li>Any non-derivable field stays null and is listed in <code>incompleteFields</code>; as long as <code>incompleteFields</code> is non-empty, <code>ready=false</code>: a draft with gaps must not be written as an adoption declaration as-is.</li>
+<li>The tool never guesses: a human completes <code>foundation_profile.version</code>/<code>stability</code>, each package artifact's <code>path</code>/<code>sha256</code>, <code>adopted_at</code>, and <code>profile.version</code>.</li>
 </ul>
 <h3 id="Binding">Binding<a class="headerlink" href="#Binding" title="Permanent link">&para;</a></h3>
-<p>The draft carries a dual sha256 digest (the <code>binding</code> block): <code>targetSetDigest</code> summarizes the target repository's file set, and <code>foundationPlanDigest</code> summarizes the Foundation plan write set. Two plans for the same target yield the same digest, precisely binding the draft and the target state at plan time.</p>
-<h3 id="Rendering-Boundary">Rendering Boundary<a class="headerlink" href="#Rendering-Boundary" title="Permanent link">&para;</a></h3>
+<p>The draft carries a dual sha256 digest (the <code>binding</code> block): <code>targetSetDigest</code> summarizes the target repository's file set, and <code>foundationPlanDigest</code> summarizes the Foundation plan write set. Two plans for the same target yield the same digest, precisely binding the draft to the target state at plan time.</p>
+<h3 id="Boundary">Boundary<a class="headerlink" href="#Boundary" title="Permanent link">&para;</a></h3>
 <ul>
-<li>The renderer writes only the planner-side hand-off draft, <strong>never the consumer repository</strong>;</li>
-<li>No fifth Kit top-level command is added: Kit top-level commands are permanently the four — scaffold, adopt-plan, projection, check — and <code>handoffDraft</code> is only a sub-block of <code>adopt-plan</code> output.</li>
+<li><code>adopt-plan</code> is strictly read-only: the draft is only printed with the plan to stdout, <strong>never written into the consumer repository</strong>;</li>
+<li>No fifth Kit top-level command is added: Kit top-level commands are permanently the four — scaffold, adopt-plan, projection, check — and <code>profileDraft</code> is only a sub-block of <code>adopt-plan</code> output.</li>
 </ul>
 <h2 id="Hazard-Class-Fixtures">Hazard-Class Fixtures<a class="headerlink" href="#Hazard-Class-Fixtures" title="Permanent link">&para;</a></h2>
 <p><code>fixtures/adoption/cases/</code> covers seven hazard classes: dirty repository, nested repository, tracked-but-ignored, symlink placeholder, generated-artifact drift, legacy-implementation exit gate, and temporary-exception fields. Each case proves the plan is read-only via byte-level before/after snapshots; see the in-repo <code>fixtures/adoption/README.md</code> for case descriptions.</p>

package/docs/en/reference/failure-and-side-effect-matrix/index.html

@@ -2050,7 +2050,7 @@
 <td><code>SFC2004</code> (<code>target-not-empty</code>)</td>
 </tr>
 <tr>
-<td><code>planAdoption</code> / <code>buildHandoffDraft</code></td>
+<td><code>planAdoption</code> / <code>buildProfileDraft</code></td>
 <td>yes</td>
 <td>no</td>
 <td>no</td>

package/docs/integration/audit/index.html

@@ -1796,7 +1796,8 @@
   isolation-and-lockfile.md     隔离安装与包锁验证设计
   independence.md               独立性声明与机械证明
   schemas/audit-evidence.schema.json   证据文档的 JSON Schema（审计自有）
-  baseline/contracts-1.5.0.pin.json    Contracts 1.5.0 现行基线 pin（摘要+事实）
+  baseline/contracts-1.6.0.pin.json    Contracts 1.6.0 现行基线 pin（摘要+事实）
+  baseline/contracts-1.5.0.pin.json    Contracts 1.5.0 只读兼容存档 pin
   baseline/contracts-1.1.1.pin.json    Contracts 1.1.1 只读兼容存档 pin
   baseline/contracts-1.1.0.pin.json    Contracts 1.1.0 只读兼容存档 pin
   baseline/contracts-1.0.0.pin.json    Contracts 1.0.0 只读兼容存档 pin

package/docs/integration/audit/version-compatibility/index.html

@@ -1643,6 +1643,17 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#profile-行为变更纪律2026-08-19D6" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        profile 行为变更纪律（2026-08-19，D6）
+
+    </span>
+  </a>
+
 </li>
 
     </ul>
@@ -1737,6 +1748,17 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#profile-行为变更纪律2026-08-19D6" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        profile 行为变更纪律（2026-08-19，D6）
+
+    </span>
+  </a>
+
 </li>
 
     </ul>
@@ -1769,7 +1791,7 @@
 <tbody>
 <tr>
 <td><code>contractsVersion</code></td>
-<td>Contracts 冻结版本（当前 <code>1.5.0</code>）</td>
+<td>Contracts 冻结版本（当前 <code>1.6.0</code>）</td>
 <td>机器契约内容的版本</td>
 </tr>
 <tr>
@@ -1784,7 +1806,7 @@
 </tr>
 </tbody>
 </table>
-<p>三者都由 <code>describeAuditSurface()</code> 一次性给出，审计侧把它们与基线 pin（当前为 <code>baseline/contracts-1.5.0.pin.json</code>）比对。</p>
+<p>三者都由 <code>describeAuditSurface()</code> 一次性给出，审计侧把它们与基线 pin（当前为 <code>baseline/contracts-1.6.0.pin.json</code>）比对。</p>
 <h2 id="兼容规则">兼容规则<a class="headerlink" href="#兼容规则" title="Permanent link">&para;</a></h2>
 <p>一个被消费的 Contracts 包与某个基线 pin <strong>兼容</strong>，当且仅当同时满足：</p>
 <ol>
@@ -1840,9 +1862,50 @@
 <li><strong>Contracts 1.2.0（2026-08-09）</strong>：报告能力线增量，不是描述补丁：新增 <code>report-model</code>、<code>report-binding</code> 两个顶层契约和 SFC3001～SFC3003 报告错误码，改变了公开机器合同与审计事实。</li>
 <li><strong>Contracts 1.3.0（2026-08-09）</strong>：宿主接入能力线增量，不是描述补丁：新增 <code>host-descriptor</code>、<code>host-capability-fact</code>、<code>adapter-build-manifest</code>、<code>host-operation-plan</code>、<code>host-operation-receipt</code> 五个顶层契约，改变了公开机器合同与审计事实。</li>
 <li><strong>Contracts 1.4.0（2026-08-09）</strong>：持久状态能力线增量，不是描述补丁：新增 <code>state-event-envelope</code>、<code>state-snapshot-metadata</code> 两个顶层契约，改变了公开机器合同与审计事实。</li>
-<li><strong>Contracts 1.5.0（2026-08-16）</strong>：FND-ADR-010/011 能力线增量，不是描述补丁：新增 <code>declared-read-surface-result</code>、<code>structured-scan-policy</code> 两个顶层契约（顶层对象集合 20 → 22），改变了公开机器合同与审计事实。<code>contracts-1.5.0.pin.json</code> 是当前现行基线；1.4.0 及更早 pin 保留为只读兼容存档。该 pin 的摘要与事实均从当前 <code>describeAuditSurface()/digestAuditSurface()</code> 机械投影，provenance 仍为 <code>product-compatibility-fixture</code>。</li>
+<li><strong>Contracts 1.5.0（2026-08-16）</strong>：FND-ADR-010/011 能力线增量，不是描述补丁：新增 <code>declared-read-surface-result</code>、<code>structured-scan-policy</code> 两个顶层契约（顶层对象集合 20 → 22），改变了公开机器合同与审计事实。该 pin 的摘要与事实均从当前 <code>describeAuditSurface()/digestAuditSurface()</code> 机械投影，provenance 仍为 <code>product-compatibility-fixture</code>。</li>
+<li><strong>Contracts 1.6.0（2026-08-18）</strong>：审计整改 C5 能力线增量，不是描述补丁：新增 <code>public-boundary-declaration</code>、<code>platform-difference-registry</code>、<code>observation-scope</code>、<code>profile-adoption-declaration</code>、<code>audit-baseline-pin</code>、<code>token-estimate-record</code> 六个顶层契约（顶层对象集合 24 → 30），改变了公开机器合同与审计事实；未新增 SFC 错误码，规则与 kernel 协议仅随 <code>contractsVersion</code> 字段更新。<code>contracts-1.6.0.pin.json</code> 是当前现行基线（经 <code>scripts/baseline-pin-gen.mjs --update</code> 由 <code>describeAuditSurface()/describeBaselinePin()</code> 机械生成，落盘前经 audit-baseline-pin 合同校验与 <code>verifyBaselinePin()</code> 自校验）；1.5.0 及更早 pin 保留为只读兼容存档。pin 合同本身（<code>audit-baseline-pin</code>）与消费面校验函数 <code>verifyBaselinePin()</code>（AUD-BASE-001 / AUD-LOCK-001 编码）在本版本落地（GAP-5 / SG-28）。</li>
 <li>审计运行时先做包锁验证（见 isolation-and-lockfile.md），再做变异重放；pin 不匹配时，变异重放结果不得被采信。</li>
 </ul>
+<h2 id="profile-行为变更纪律2026-08-19D6">profile 行为变更纪律（2026-08-19，D6）<a class="headerlink" href="#profile-行为变更纪律2026-08-19D6" title="Permanent link">&para;</a></h2>
+<p>Foundation 对外暴露的 profile 机制面是消费方 pin 的行为契约，包括 <code>FOUNDATION_MECHANISM_OPERATIONS</code> 8 个 operations 与 <code>runner.mjs</code> 直接导出（含 <code>publishFileExclusive</code> 等函数的选项面）。<strong>profile 行为变更 = profile 版本变更</strong>：行为语义漂移不得在不升版本的前提下发生。stability 维持 candidate-only（D6）期间同样适用——candidate profile 的字节一致性由 pin digest 约束，行为语义变更必须走版本坐标，不因 candidate 状态而豁免。</p>
+<table>
+<thead>
+<tr>
+<th>变更</th>
+<th>分级</th>
+<th>需要的动作</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>8 个 operations 之一的分派语义变化（参数、结果、错误 kind）</td>
+<td>profile 行为变更</td>
+<td>包版本递增（candidate 阶段为 candidate 版本递增）+ 本文件更新</td>
+</tr>
+<tr>
+<td>runner 直接导出面变化（新增/删除/改变导出，含 publish 函数族）</td>
+<td>profile 行为变更</td>
+<td>包版本递增 + 本文件更新</td>
+</tr>
+<tr>
+<td>publish 选项面变化（2026-08-19 D5 为 <code>publishFileExclusive</code> 新增 <code>createParents</code> 选项即此类；选项是 Foundation 侧契约，消费面只传参）</td>
+<td>profile 行为变更</td>
+<td>包版本递增 + 本文件更新</td>
+</tr>
+<tr>
+<td>不改变行为的字节变更（注释、格式化）</td>
+<td>无影响</td>
+<td>无需版本动作（pin digest 仍按既有机制变化）</td>
+</tr>
+</tbody>
+</table>
+<p>消费方响应动作：</p>
+<ol>
+<li><strong>pin 升级</strong>：消费方把 foundation-pin（或等价钉扎）升级到含该行为变更的版本；禁止在旧 pin 上假设新行为。</li>
+<li><strong>adoption-lock 重生成</strong>：受影响消费方重新生成 adoption-lock（或等价声明载体），使 <code>declared_foundation_surface</code> 与 <code>foundation_versions</code> 反映新 pin 字节。</li>
+<li><strong>先建后删</strong>：行为变更以 Foundation 侧行为测试（含 bundle 字节对象测试）落地为先，消费方删除自身重验测试在后（D2 顺序）。</li>
+</ol>
+<p><strong>行为归属记录（2026-08-19）</strong>：「宿主运行时（node）不可用 → 无回退、fail-closed」的触发面（node 解析/env 检查）属于消费方调用边界（SFA 侧为 D3 已裁决接受的残余风险，仅保留调用点声明检查）；Foundation 侧等价语义 = 写入环节失败时 fail-closed（无部分产物、错误码正确、无本地回退），由 atomic 行为测试承接，不在 Foundation 建宿主 spawn 测试。</p>
 
 
 

package/docs/migration/index.html

@@ -573,22 +573,22 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#十字段-hand-off-草案" class="md-nav__link">
+  <a href="#Profile-草稿" class="md-nav__link">
     <span class="md-ellipsis">
 
-        十字段 hand-off 草案
+        Profile 草稿
 
     </span>
   </a>
 
-    <nav class="md-nav" aria-label="十字段 hand-off 草案">
+    <nav class="md-nav" aria-label="Profile 草稿">
       <ul class="md-nav__list">
 
           <li class="md-nav__item">
-  <a href="#INCOMPLETE-阻断规则" class="md-nav__link">
+  <a href="#不完整阻断规则" class="md-nav__link">
     <span class="md-ellipsis">
 
-        INCOMPLETE 阻断规则
+        不完整阻断规则
 
     </span>
   </a>
@@ -607,10 +607,10 @@
 </li>
 
           <li class="md-nav__item">
-  <a href="#渲染边界" class="md-nav__link">
+  <a href="#边界" class="md-nav__link">
     <span class="md-ellipsis">
 
-        渲染边界
+        边界
 
     </span>
   </a>
@@ -1923,22 +1923,22 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#十字段-hand-off-草案" class="md-nav__link">
+  <a href="#Profile-草稿" class="md-nav__link">
     <span class="md-ellipsis">
 
-        十字段 hand-off 草案
+        Profile 草稿
 
     </span>
   </a>
 
-    <nav class="md-nav" aria-label="十字段 hand-off 草案">
+    <nav class="md-nav" aria-label="Profile 草稿">
       <ul class="md-nav__list">
 
           <li class="md-nav__item">
-  <a href="#INCOMPLETE-阻断规则" class="md-nav__link">
+  <a href="#不完整阻断规则" class="md-nav__link">
     <span class="md-ellipsis">
 
-        INCOMPLETE 阻断规则
+        不完整阻断规则
 
     </span>
   </a>
@@ -1957,10 +1957,10 @@
 </li>
 
           <li class="md-nav__item">
-  <a href="#渲染边界" class="md-nav__link">
+  <a href="#边界" class="md-nav__link">
     <span class="md-ellipsis">
 
-        渲染边界
+        边界
 
     </span>
   </a>
@@ -2196,83 +2196,28 @@
 <li><strong>回滚以证据为准</strong>：采用落盘前必须先有 <code>adoptionProof</code> 与 <code>foundationPlanDigest</code> 双摘要绑定；回滚时以计划写集的 <code>expect.sha256</code> 前置状态还原，未声明前置状态的覆盖动作在 <code>projection</code> 阶段即拒绝。</li>
 <li><strong>fail-closed 默认</strong>：任何不可解析、越界、身份不符或证据缺失的输入，都使对应判定为未证明，不假设成功。</li>
 </ul>
-<h2 id="十字段-hand-off-草案">十字段 hand-off 草案<a class="headerlink" href="#十字段-hand-off-草案" title="Permanent link">&para;</a></h2>
-<p><code>adopt-plan</code> 输出携带 <code>handoffDraft</code> 子块（kind=<code>skill-family.handoff-draft</code>，schemaVersion=1），为 planner 侧的十字段 hand-off 提供结构化数据草案。字段来源只有两种：<code>derived</code>（可由只读证据机械推导）与 <code>INCOMPLETE</code>（不可机械推导，绝不猜测）。十字段与源码常量 <code>HANDOFF_FIELDS</code> 逐一对应：</p>
-<table>
-<thead>
-<tr>
-<th>id</th>
-<th>字段名</th>
-<th>来源</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>1</td>
-<td><code>project-identity</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>2</td>
-<td><code>repository-state</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>3</td>
-<td><code>foundation-binding</code></td>
-<td>derived（清单已声明绑定）／INCOMPLETE（无清单声明）</td>
-</tr>
-<tr>
-<td>4</td>
-<td><code>write-set-policy</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>5</td>
-<td><code>legacy-exits</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>6</td>
-<td><code>business-logic-to-keep</code></td>
-<td>恒 INCOMPLETE</td>
-</tr>
-<tr>
-<td>7</td>
-<td><code>plan-summary</code></td>
-<td>derived</td>
-</tr>
-<tr>
-<td>8</td>
-<td><code>verification-entries</code></td>
-<td>derived（四类证据全部 proven）／INCOMPLETE（任一未证明）</td>
-</tr>
-<tr>
-<td>9</td>
-<td><code>legacy-removal-recovery</code></td>
-<td>恒 INCOMPLETE</td>
-</tr>
-<tr>
-<td>10</td>
-<td><code>authorization-status</code></td>
-<td>derived（commit/push/tag/publish 恒为 false）</td>
-</tr>
-</tbody>
-</table>
-<h3 id="INCOMPLETE-阻断规则">INCOMPLETE 阻断规则<a class="headerlink" href="#INCOMPLETE-阻断规则" title="Permanent link">&para;</a></h3>
+<h2 id="Profile-草稿">Profile 草稿<a class="headerlink" href="#Profile-草稿" title="Permanent link">&para;</a></h2>
+<p><code>adopt-plan</code> 输出携带 <code>profileDraft</code> 子块（kind=<code>skill-family.profile-draft</code>，schemaVersion=1）：一份预填的 profile.json 描述符草稿（<code>descriptorRelPath</code>=<code>profile.json</code>）。adoption-lock 概念与其工件形态已废弃（整改交接 D-8）：轻量采用证明就是描述符自身的采用声明，由 <code>verifyProfile</code>（Profile SPI v2）机械核验——字段完整性与 pin 形态在描述符 Schema 步把关（SPE1001），pin 摘要按 GK-4 纪律对写集内真实工件字节逐一比对（SPE1006），overrides 只收紧策略独立裁决（SPE1007）。</p>
+<p>草稿预填一切可由只读事实机械推导的内容：</p>
+<ul>
+<li>描述符身份与基线：<code>profile.id</code>/<code>profile.name</code> 来自计划输入，<code>base.contractsVersion</code> 为已加载的冻结 Contracts 版本；<code>differences</code>/<code>spi</code> 为空数组起点。</li>
+<li>采用声明（D-8 最小字段集，权威定义在 <code>profiles/spi/extension-spi.json</code> 的 <code>adoptionDeclaration</code>）：</li>
+<li><code>foundation_profile.id</code> 为计划采用的 Foundation Profile id；<code>version</code>/<code>stability</code> 属人类决策，保持 null。</li>
+<li><code>foundation_pin.algorithm</code> 恒为 <code>sha256</code>；三个 Foundation 包的 <code>version</code> 按「迁移清单声明优先，其次加载常量」预填；<code>path</code>/<code>sha256</code> 在真实工件放入 Profile 写集之前保持 null（摘要只能来自真实字节，绝不猜测）。</li>
+<li><code>adopted_at</code> 在采用时刻才产生，规划期保持 null。</li>
+<li><code>overrides</code> 为空数组（空示例）：覆盖是可选的自收紧声明，Kit 不枚举规则示例（核心不导入 Profile 层）；草稿附带 <code>overridesGuidance</code> 说明只收紧语义。</li>
+</ul>
+<h3 id="不完整阻断规则">不完整阻断规则<a class="headerlink" href="#不完整阻断规则" title="Permanent link">&para;</a></h3>
 <ul>
-<li>任何 INCOMPLETE 字段都使 <code>ready=false</code>：草案带缺口就不得进入 hand-off。</li>
-<li>工具绝不猜测不可机械推导的字段：</li>
-<li><code>business-logic-to-keep</code> 与 <code>legacy-removal-recovery</code> <strong>恒 INCOMPLETE</strong>，必须由人类负责人给出，工具无推导依据；</li>
-<li><code>foundation-binding</code> 在无迁移清单声明（<code>foundationPackages</code>）时 INCOMPLETE，只计清单声明的绑定；</li>
-<li><code>verification-entries</code> 在四类证据（unit/integration/consumer/independentAudit）任一未达 proven 时 INCOMPLETE。</li>
+<li>任何不可机械推导的字段保持 null 并列入 <code>incompleteFields</code>；只要 <code>incompleteFields</code> 非空即 <code>ready=false</code>：带缺口的草稿不得直接落盘为采用声明。</li>
+<li>工具绝不猜测：人工需补齐 <code>foundation_profile.version</code>/<code>stability</code>、各包工件的 <code>path</code>/<code>sha256</code>、<code>adopted_at</code> 与 <code>profile.version</code>。</li>
 </ul>
 <h3 id="绑定">绑定<a class="headerlink" href="#绑定" title="Permanent link">&para;</a></h3>
-<p>草案携带双 sha256 摘要（<code>binding</code> 块）：<code>targetSetDigest</code> 汇总目标仓文件集合，<code>foundationPlanDigest</code> 汇总 Foundation 计划写集。同一目标两次计划得到相同摘要，草案与计划时刻的目标状态精确绑定。</p>
-<h3 id="渲染边界">渲染边界<a class="headerlink" href="#渲染边界" title="Permanent link">&para;</a></h3>
+<p>草稿携带双 sha256 摘要（<code>binding</code> 块）：<code>targetSetDigest</code> 汇总目标仓文件集合，<code>foundationPlanDigest</code> 汇总 Foundation 计划写集。同一目标两次计划得到相同摘要，草稿与计划时刻的目标状态精确绑定。</p>
+<h3 id="边界">边界<a class="headerlink" href="#边界" title="Permanent link">&para;</a></h3>
 <ul>
-<li>渲染器只写 planner 侧的 hand-off 草案，<strong>绝不写消费者仓</strong>；</li>
-<li>不新增第五个 Kit 顶层命令：Kit 顶层命令恒为 scaffold、adopt-plan、projection、check 四个，<code>handoffDraft</code> 只是 <code>adopt-plan</code> 输出的子块。</li>
+<li><code>adopt-plan</code> 严格只读：草稿只随计划输出到 stdout，<strong>绝不写消费者仓</strong>；</li>
+<li>不新增第五个 Kit 顶层命令：Kit 顶层命令恒为 scaffold、adopt-plan、projection、check 四个，<code>profileDraft</code> 只是 <code>adopt-plan</code> 输出的子块。</li>
 </ul>
 <h2 id="危害类-fixture">危害类 fixture<a class="headerlink" href="#危害类-fixture" title="Permanent link">&para;</a></h2>
 <p><code>fixtures/adoption/cases/</code> 覆盖七个危害类：dirty 仓、嵌套仓、tracked-but-ignored、符号链接占位、生成物漂移、旧实现退出门禁、临时例外字段。每个案例以字节级前后快照证明计划只读；案例说明见仓内 <code>fixtures/adoption/README.md</code>。</p>

package/docs/public/status/index.html

@@ -1792,17 +1792,17 @@
 <tbody>
 <tr>
 <td><code>skill-family-contracts</code></td>
-<td>0.5.0</td>
+<td>0.7.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.5.0</td>
+<td>0.7.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.5.0</td>
+<td>0.7.0</td>
 <td><a href="https://github.com/ifoohoo/skill-family-engineering-kit">ifoohoo/skill-family-engineering-kit</a></td>
 </tr>
 </tbody>