docs(site): main-status drift — #1698 model_usage fix, #1701 traverse-mcp packaging

public/llms.txt

@@ -42,7 +42,7 @@ Current packages: crates.io Traverse at 0.15.0; npm `traverse-embedder-web@0.15.
 
 - **Direction (same as Required reading above):** [agent MCP exact-ref](https://traverse-framework.com/blog/agent-mcp-exact-ref.html) · [signed exact-ref digits](https://traverse-framework.com/blog/signed-exact-ref-digits.html) · [same-wasm multi-host](https://traverse-framework.com/blog/same-wasm-multi-host.html) · [deny demo blog](https://traverse-framework.com/blog/agent-freestyle-blocked.html) · [what-is-real-today](https://traverse-framework.com/what-is-real-today.html) · [run the deny demo (blog-first; weekly-demos not public yet)](https://traverse-framework.com/questions/how-do-i-run-the-agent-blocked-weekly-demo.html).
 - [For AI Agents](https://traverse-framework.com/agents.html): the real MCP tool list (ten commands: describe_server, list_content_groups, describe_content_group, list_entrypoints, search_capabilities, describe_entrypoint, validate_entrypoint, execute_entrypoint, render_execution_report, shutdown), the discover-inspect-execute-trace flow, and the honest limits (stdio is the packaged bootstrap today; in-process library functions exist on traverse-mcp, but there is no separate HTTP MCP listener as a packaged product).
-- [Is the agent MCP exact-ref demo the same as traverse-mcp?](https://traverse-framework.com/questions/is-the-agent-mcp-demo-the-same-as-traverse-mcp.html): no. The Oct 9 weekly demo is an in-process MCP-shaped JSON-RPC façade over `ExactModelBrowserHost` under Node, not the checksum-pinned Mode A `traverse-mcp` binary. Mode A `traverse-mcp` is the published stdio MCP server for discover/inspect/execute of registry capabilities. Pinning a packaged Mode A binary is longer-term (#1653). Write-up: [Agent speaks MCP](https://traverse-framework.com/blog/agent-mcp-exact-ref.html).
+- [Is the agent MCP exact-ref demo the same as traverse-mcp?](https://traverse-framework.com/questions/is-the-agent-mcp-demo-the-same-as-traverse-mcp.html): no. The Oct 9 weekly demo is an in-process MCP-shaped JSON-RPC façade over `ExactModelBrowserHost` under Node, not the checksum-pinned Mode A `traverse-mcp` binary. Mode A `traverse-mcp` is the published stdio MCP server for discover/inspect/execute of registry capabilities. Checksum-pinned Mode A binaries (#1653): packaging workflow merged on main (#1701); first non-Latest `traverse-mcp-v*` release with `SHA256SUMS` comes with the next product tag, none published yet. Write-up: [Agent speaks MCP](https://traverse-framework.com/blog/agent-mcp-exact-ref.html).
 - [traverse-framework/claude-skills](https://github.com/traverse-framework/claude-skills): Claude Skills for building apps with Traverse — starting with `traverse-capability-author` (plus extractor and workflow-planner), which checks the registry before authoring, produces contract + WASM, and validates against the real traverse-cli — including this platform's current execution limitations.
 - [How do I author a capability in plain English?](https://traverse-framework.com/questions/how-do-i-author-a-capability-in-plain-english.html): Claude skill `traverse-capability-author` — interview → registry check → contract → WASM → human-reviewed PR; under the hood still Rust→WASM; manual Rust is secondary.
 - [How do I go from a skill draft to a published capability?](https://traverse-framework.com/questions/how-do-i-go-from-skill-draft-to-published-capability.html): after the skill opens the registry PR — review, CI, human merge, next catalog release; no side-door upload.
@@ -79,8 +79,8 @@ Current packages: crates.io Traverse at 0.15.0; npm `traverse-embedder-web@0.15.
 - [How do hosts trust signed models?](https://traverse-framework.com/questions/how-do-hosts-trust-signed-models.html): discover → execute → trace; one shared `runtime.wasm`; host-owned trust roots gate `register_package`; pin by digest + `model.sig.json`; `model_usage` required in v0.15.0; test-only digits-mlp key (custody #1567 still open); published exact-ref execute is native + web + Swift `swift-host-v0.15.0` + Kotlin and .NET 0.15.0; third-party ONNX can be packaged and signed with `traverse-cli model`.
 - [Which hosts run signed exact-ref models?](https://traverse-framework.com/questions/which-hosts-run-signed-exact-ref-models.html) · [Is production model signing ready?](https://traverse-framework.com/questions/is-production-model-signing-ready.html) · [Can Kotlin or .NET run exact-ref yet?](https://traverse-framework.com/questions/can-kotlin-or-dotnet-embedders-run-exact-ref-yet.html): discover → execute → trace; one shared `runtime.wasm`; published exact-ref is native + web 0.15.0 + Swift `swift-host-v0.15.0` + Kotlin and .NET 0.15.0 (#1651 closed); production signing custody is not finished (#1567 still open; v0.15.0 shipped key-generation tooling).
 - [What is ExactModelHost?](https://traverse-framework.com/questions/what-is-exact-model-host.html): host-side connector for governed exact-ref model packages (Spec 138). Register a signed package under host-owned trust roots, then execute under discover → execute → trace. Not a second runtime. Published in 0.15.0: native connector, web `ExactModelBrowserHost`, Swift `ExactModelHost` on `swift-host-v0.15.0`, Kotlin and .NET `ExactModelHost` in Maven/NuGet 0.15.0 (#1651 closed). Test-only digits-mlp key; custody #1567 still open. Not catalog `model.execute`. Not Hugging Face.
-- [Signed models on every host. The rights travel with them.](https://traverse-framework.com/blog/signed-models-on-every-host.html): Oct 15 v0.15.0 narrative — discover → execute → trace; signed exact-ref on native Rust, web, Swift `swift-host-v0.15.0`, Kotlin and .NET 0.15.0 via small audited native boundaries sharing `traverse-model-host-frame`, byte-identical conformance vectors, one 21-case rights suite; **breaking** `model_usage`; `traverse-cli model` + `package-onnx` (install `traverse-cli-rs`, runner from `onnx-runner-v0.15.0`); ABI v3 prepare-once; Core ML opt-in on Apple (iPhone governed evidence traverse#1630 open). Caveats: web `modelUsage` not validated (traverse#1685), CLI verify usage (traverse#1686, main only), test-only key (custody #1567), registry capability revocation #1598 not shipped. No host Certified.
-- [What is model_usage?](https://traverse-framework.com/questions/what-is-model-usage-in-traverse.html): since v0.15.0 apps with `exact_model_dependencies` must declare `model_usage: commercial | non_commercial` or fail closed with `usage_undeclared`; `commercial` rejects `prohibited` packages (`rights_policy_denied`); results carry `model_evidence`; Rust `ExactModelHostConnector::model_usage`, web `modelUsage`, Swift `modelUsage:` (no default), Kotlin/.NET `modelUsage`. Gaps: published web 0.15.0 accepts any string (traverse#1685); `traverse-cli-rs` 0.15.0 `model verify` has no usage flag (traverse#1686, fixed on main after release).
+- [Signed models on every host. The rights travel with them.](https://traverse-framework.com/blog/signed-models-on-every-host.html): Oct 15 v0.15.0 narrative — discover → execute → trace; signed exact-ref on native Rust, web, Swift `swift-host-v0.15.0`, Kotlin and .NET 0.15.0 via small audited native boundaries sharing `traverse-model-host-frame`, byte-identical conformance vectors, one 21-case rights suite; **breaking** `model_usage`; `traverse-cli model` + `package-onnx` (install `traverse-cli-rs`, runner from `onnx-runner-v0.15.0`); ABI v3 prepare-once; Core ML opt-in on Apple (iPhone governed evidence traverse#1630 open). Caveats: web `modelUsage` not validated in 0.15.0 (traverse#1685; fix #1698 on main, unreleased), CLI verify usage (traverse#1686, main only), test-only key (custody #1567), registry capability revocation #1598 not shipped. No host Certified.
+- [What is model_usage?](https://traverse-framework.com/questions/what-is-model-usage-in-traverse.html): since v0.15.0 apps with `exact_model_dependencies` must declare `model_usage: commercial | non_commercial` or fail closed with `usage_undeclared`; `commercial` rejects `prohibited` packages (`rights_policy_denied`); results carry `model_evidence`; Rust `ExactModelHostConnector::model_usage`, web `modelUsage`, Swift `modelUsage:` (no default), Kotlin/.NET `modelUsage`. Gaps: published web 0.15.0 accepts any string (traverse#1685; fix #1698 merged on main, rejects with `usage_invalid`, unreleased); `traverse-cli-rs` 0.15.0 `model verify` has no usage flag (traverse#1686, fixed on main after release).
 - [How do I package my own ONNX model?](https://traverse-framework.com/questions/how-do-i-package-an-onnx-model-for-traverse.html): `cargo install traverse-cli-rs --version =0.15.0 --locked` (Rust ≥ 1.94; crates.io `traverse-cli` is unrelated); `runner.wasm` from GitHub release `onnx-runner-v0.15.0` (sha256 `f3902703fe79cc161c13b87cf507dcb25cb53ea3c2a68bed6cc753f9df100966`); `model package-onnx` → sign → verify → conformance → pin; one input + one output tensor only (traverse#1661); post-processing belongs in capabilities, hosts stay UI + I/O. Not catalog `model.execute`, not Hugging Face.
 - [What happens when a host marks a model package revoked?](https://traverse-framework.com/questions/what-happens-when-a-host-marks-a-model-package-revoked.html): v0.15.0 hosts own a package-status map for signed model packages — `revoked` blocks (`package_revoked`), `deprecated` runs and is flagged; `model_evidence` on every result. Not registry capability revocation (runtime refusal is traverse#1598, not shipped).
 - [Can Traverse run models on a GPU or the Apple Neural Engine?](https://traverse-framework.com/questions/can-traverse-run-models-on-a-gpu-or-neural-engine.html): Core ML is an opt-in Apple placement in v0.15.0. Default stays `wasm-cpu`. Ordered placements, on-device self-check, fail-closed `placement_unavailable`, placement evidence (Decision 112). Evidence so far is macOS cargo test plus the Decision 113 iPhone spike. Governed-path iPhone evidence is traverse#1630, still open. No web, Android, or desktop GPU adapter. No host is Certified.

src/pages/agents.astro

@@ -144,7 +144,7 @@ const _body = `<section class="page-hero">
             </div>
             <div class="checklist-item">
               <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><circle cx="12" cy="12" r="10"/><line x1="12" y1="8" x2="12" y2="12"/><line x1="12" y1="16" x2="12.01" y2="16"/></svg>
-              <span><strong style="color:var(--fg)">The Oct 9 exact-ref demo is not this server.</strong> That write-up is an in-process MCP-shaped JSON-RPC façade over <code>ExactModelBrowserHost</code> under Node. Mode A <code>traverse-mcp</code> is the stdio server on this page. <a href="/questions/is-the-agent-mcp-demo-the-same-as-traverse-mcp.html">They are not the same.</a> Pinning a packaged Mode A binary is <a href="https://github.com/traverse-framework/traverse/issues/1653" target="_blank" rel="noopener">#1653</a>.</span>
+              <span><strong style="color:var(--fg)">The Oct 9 exact-ref demo is not this server.</strong> That write-up is an in-process MCP-shaped JSON-RPC façade over <code>ExactModelBrowserHost</code> under Node. Mode A <code>traverse-mcp</code> is the stdio server on this page. <a href="/questions/is-the-agent-mcp-demo-the-same-as-traverse-mcp.html">They are not the same.</a> Checksum-pinned Mode A binaries are <a href="https://github.com/traverse-framework/traverse/issues/1653" target="_blank" rel="noopener">#1653</a>: the packaging workflow merged on main, and the first <code>traverse-mcp-v*</code> artifact release (Linux x86_64 and macOS arm64, with <code>SHA256SUMS</code>) comes with the next product tag. None is published yet.</span>
             </div>
             <div class="checklist-item">
               <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><circle cx="12" cy="12" r="10"/><line x1="12" y1="8" x2="12" y2="12"/><line x1="12" y1="16" x2="12.01" y2="16"/></svg>

src/pages/blog/signed-models-on-every-host.astro

@@ -44,7 +44,7 @@ const _body = `
 
       <p>A <code>commercial</code> usage, declared by the app or forced by the host, rejects any package whose rights say <code>commercial_use: prohibited</code>, with <code>rights_policy_denied</code>. Hosts also own a package-status map: a <code>revoked</code> package is blocked and a <code>deprecated</code> one is flagged. Every result carries <code>model_evidence</code>, the verified rights record, so the trace shows which rights the answer ran under. Earlier this month I wrote that <a href="/blog/model-rights-are-data.html">model rights are data, not a README</a>. v0.15.0 is the release where every host acts on that data.</p>
 
-      <p>One caveat, and it is a real one. The published web host does not validate the value yet. <code>traverse-embedder-web@0.15.0</code> accepts strings other than <code>commercial</code> and <code>non_commercial</code>, so a typo such as <code>"Commercial"</code> quietly skips the commercial check. That is <a href="https://github.com/traverse-framework/traverse/issues/1685" target="_blank" rel="noopener">#1685</a>. A fix is in review (<a href="https://github.com/traverse-framework/traverse/pull/1698" target="_blank" rel="noopener">#1698</a>) and is not in a release. Native Rust uses an enum and cannot express a bad value. Until a release fixes the web host, pass exactly <code>commercial</code> or <code>non_commercial</code>, and test the commercial path once on purpose. The short page is <a href="/questions/what-is-model-usage-in-traverse.html">what is model_usage?</a></p>
+      <p>One caveat, and it is a real one. The published web host does not validate the value yet. <code>traverse-embedder-web@0.15.0</code> accepts strings other than <code>commercial</code> and <code>non_commercial</code>, so a typo such as <code>"Commercial"</code> quietly skips the commercial check. That is <a href="https://github.com/traverse-framework/traverse/issues/1685" target="_blank" rel="noopener">#1685</a>. A fix merged on main on October 15 (<a href="https://github.com/traverse-framework/traverse/pull/1698" target="_blank" rel="noopener">#1698</a>): string-typed hosts now reject any other value with <code>usage_invalid</code>. It is not in a release yet. Native Rust uses an enum and cannot express a bad value. Until a release fixes the web host, pass exactly <code>commercial</code> or <code>non_commercial</code>, and test the commercial path once on purpose. The short page is <a href="/questions/what-is-model-usage-in-traverse.html">what is model_usage?</a></p>
 
       <h2 id="onnx">Package your own ONNX model</h2>
 

src/pages/questions/is-the-agent-mcp-demo-the-same-as-traverse-mcp.astro

@@ -9,7 +9,7 @@ const jsonLd = JSON.stringify({
     name: 'Is the agent MCP exact-ref demo the same as traverse-mcp?',
     acceptedAnswer: {
       '@type': 'Answer',
-      text: 'No. The October 9 weekly demo (agent-mcp-exact-ref) uses an in-process MCP-shaped JSON-RPC façade over ExactModelBrowserHost under Node. It is not the checksum-pinned Mode A traverse-mcp binary. Mode A traverse-mcp is the published stdio MCP server for discover, inspect, and execute of registry capabilities. Pinning a packaged Mode A binary is longer-term work tracked as #1653.',
+      text: 'No. The October 9 weekly demo (agent-mcp-exact-ref) uses an in-process MCP-shaped JSON-RPC façade over ExactModelBrowserHost under Node. It is not the checksum-pinned Mode A traverse-mcp binary. Mode A traverse-mcp is the published stdio MCP server for discover, inspect, and execute of registry capabilities. Checksum-pinned Mode A binaries are #1653: the packaging workflow merged on main and the first traverse-mcp-v* artifact release comes with the next product tag. None is published yet.',
     },
   }],
 });
@@ -24,7 +24,7 @@ const relatedLinks = [
 ---
 <QuestionLayout
   title="Is the agent MCP exact-ref demo the same as traverse-mcp?"
-  description="No. The Oct 9 demo is an in-process MCP-shaped façade over ExactModelBrowserHost under Node. Mode A traverse-mcp is the published stdio server for registry capabilities. Pinning that binary is #1653."
+  description="No. The Oct 9 demo is an in-process MCP-shaped façade over ExactModelBrowserHost under Node. Mode A traverse-mcp is the published stdio server for registry capabilities. Pinned binaries (#1653) ship with the next product tag."
   canonical="https://traverse-framework.com/questions/is-the-agent-mcp-demo-the-same-as-traverse-mcp.html"
   category="AI and MCP"
   relatedLinks={relatedLinks}
@@ -39,5 +39,5 @@ const relatedLinks = [
   <p>Mode A <code>traverse-mcp</code> is the published stdio MCP server. An agent uses it to discover, inspect, and execute registry capabilities: <code>list_entrypoints</code>, <code>describe_entrypoint</code>, <code>execute_entrypoint</code>, and the rest of the ten-command set on <a href="/agents.html">For AI agents</a>. Setup is the <a href="/docs/guides/mcp-setup.html">MCP setup guide</a>. Stdio is the packaged bootstrap. That server is a client of the shared runtime contract. It is not the demo façade, and it is not a second runtime.</p>
 
   <h2>What is still open</h2>
-  <p>Pinning and checksum-verifying a packaged Mode A binary, the way you would pin any other release artifact, is longer-term work: <a href="https://github.com/traverse-framework/traverse/issues/1653">#1653</a>. Until that lands, do not describe the October 9 column as "the checksum-pinned <code>traverse-mcp</code>." Quote the blog for what the façade did. Quote this page, or <a href="/agents.html">agents</a>, for what the server is.</p>
+  <p>Pinning and checksum-verifying a packaged Mode A binary, the way you would pin any other release artifact, is <a href="https://github.com/traverse-framework/traverse/issues/1653">#1653</a>. The packaging workflow merged on main on October 15 (<a href="https://github.com/traverse-framework/traverse/pull/1701">#1701</a>). It builds Linux x86_64 and macOS arm64 binaries on the next product tag and publishes them as a non-Latest <code>traverse-mcp-v*</code> release with <code>SHA256SUMS</code> and build provenance. No such release exists yet. Until one does, do not describe the October 9 column as "the checksum-pinned <code>traverse-mcp</code>." Quote the blog for what the façade did. Quote this page, or <a href="/agents.html">agents</a>, for what the server is.</p>
 </QuestionLayout>

src/pages/questions/what-is-model-usage-in-traverse.astro

@@ -46,7 +46,7 @@ const relatedLinks = [
 
   <h2>Known gaps in 0.15.0</h2>
   <ul>
-    <li><strong>Web accepts any string.</strong> Published <code>traverse-embedder-web@0.15.0</code> does not check that the value is exactly <code>commercial</code> or <code>non_commercial</code>. A typo like <code>"Commercial"</code> skips the commercial check without an error. Tracked in <a href="https://github.com/traverse-framework/traverse/issues/1685">traverse#1685</a>, with a fix in review and not in a release. Native Rust uses an enum and cannot express a bad value.</li>
+    <li><strong>Web accepts any string.</strong> Published <code>traverse-embedder-web@0.15.0</code> does not check that the value is exactly <code>commercial</code> or <code>non_commercial</code>. A typo like <code>"Commercial"</code> skips the commercial check without an error. Tracked in <a href="https://github.com/traverse-framework/traverse/issues/1685">traverse#1685</a>. The fix (<a href="https://github.com/traverse-framework/traverse/pull/1698">#1698</a>) merged on main on October 15 and rejects any other value with <code>usage_invalid</code>, but it is not in a release yet. Native Rust uses an enum and cannot express a bad value.</li>
     <li><strong>CLI verify has no usage flag.</strong> <code>traverse-cli model verify</code> in <code>traverse-cli-rs</code> 0.15.0 always verifies as <code>non_commercial</code>. <code>--model-usage</code> landed on main after the release (<a href="https://github.com/traverse-framework/traverse/issues/1686">traverse#1686</a>) and is not in 0.15.0.</li>
   </ul>
   <p>Until those ship, pass the exact value and test the commercial path once on purpose. No host is Certified under Spec 529. The upgrade notes are in <a href="https://github.com/traverse-framework/traverse/blob/v0.15.0/docs/upgrade-to-v0.15.0.md">docs/upgrade-to-v0.15.0.md</a>.</p>