@piagent/platform 1.7.1 → 1.9.0

package/docs-site/content/en/quickstart.html

@@ -47,12 +47,11 @@ pi</code></pre>
 
     <article class="step">
       <div>
-        <h3 id="onboard-context">Onboard context</h3>
-        <p>Run this once in a new repository to record project context, verification matrices, and protected areas under <span class="inline-code">.pi/</span>. <span class="inline-code">/onboard</span> opens the menu and status; <span class="inline-code">run</span> launches the project-reading workflow.</p>
+        <h3 id="onboard-context">Let the agent read the project</h3>
+        <p>In a new repository, ask the agent to read the project (read-only) and record its project context under <span class="inline-code">.pi/</span>. No separate command: plain language is enough.</p>
         <div class="command-card">
-          <header><span>Onboard</span><button class="clip-btn" data-clip="/onboard&#10;/onboard run">Copy</button></header>
-          <pre><code>/onboard
-/onboard run</code></pre>
+          <header><span>Read the project</span><button class="clip-btn" data-clip="Inspect this project read-only and record its project context.">Copy</button></header>
+          <pre><code>Inspect this project read-only and record its project context.</code></pre>
         </div>
       </div>
     </article>
@@ -84,20 +83,19 @@ pi</code></pre>
     <article class="step">
       <div>
         <h3 id="run-workflow">Run a workflow</h3>
-        <p>Use the command that matches the intent so the agent does not spend context rediscovering the process. Start a fresh session for context-heavy work.</p>
+        <p>State the work and the intent (edit, read-only, plan first) in plain language. Start a new session with <span class="inline-code">/new</span> for context-heavy work.</p>
         <div class="command-card">
-          <header><span>Workflow</span><button class="clip-btn" data-clip="/workflow task Implement the requested bounded change.&#10;/workflow review current diff&#10;/fresh task Implement the requested bounded change.">Copy</button></header>
-          <pre><code>/workflow task Implement the requested bounded change.
-/workflow review current diff
-/fresh task Implement the requested bounded change.</code></pre>
+          <header><span>Assign work</span><button class="clip-btn" data-clip="Implement the requested change and run the project tests.&#10;Review the current diff. Read-only.">Copy</button></header>
+          <pre><code>Implement the requested change and run the project tests.
+Review the current diff. Read-only.</code></pre>
         </div>
       </div>
     </article>
 
     <article class="step">
       <div>
-        <h3 id="verify-before-handoff">Verify before handoff</h3>
-        <p>The final gate trusts only commands that actually ran, exited successfully, and matched the verification plan. After pinning or upgrading a version, run doctor in the project:</p>
+        <h3 id="verify-before-handoff">Check before you hand over</h3>
+        <p>Ask the agent to run the project's checks (tests, type check, build) and read the real output; in company mode the Harness asks for this itself. After pinning or upgrading a version, run doctor in the project:</p>
         <div class="command-card">
           <header><span>Doctor</span><button class="clip-btn" data-clip="piagent-doctor">Copy</button></header>
           <pre><code>piagent-doctor</code></pre>

package/docs-site/content/en/runtime.html

@@ -1,7 +1,7 @@
 <section class="section">
   <div class="command-grid">
     <article class="command-card"><header><span>Global setup</span><button class="clip-btn" data-clip="piagent-setup --mcp-preset core --subagents-preset safe">Copy</button></header><pre><code>piagent-setup --mcp-preset core --subagents-preset safe</code></pre></article>
-    <article class="command-card"><header><span>Full update</span><button class="clip-btn" data-clip="npm install -g --ignore-scripts @earendil-works/pi-coding-agent@0.86.1&#10;npm install -g --ignore-scripts @piagent/platform@X.Y.Z&#10;piagent-install --stable --dry-run&#10;piagent-install --stable">Copy</button></header><pre><code>npm install -g --ignore-scripts @earendil-works/pi-coding-agent@0.86.1
+    <article class="command-card"><header><span>Full update</span><button class="clip-btn" data-clip="npm install -g --ignore-scripts @earendil-works/pi-coding-agent@0.87.1&#10;npm install -g --ignore-scripts @piagent/platform@X.Y.Z&#10;piagent-install --stable --dry-run&#10;piagent-install --stable">Copy</button></header><pre><code>npm install -g --ignore-scripts @earendil-works/pi-coding-agent@0.87.1
 npm install -g --ignore-scripts @piagent/platform@X.Y.Z
 piagent-install --stable --dry-run
 piagent-install --stable</code></pre></article>

package/docs-site/content/en/security.html

@@ -5,7 +5,7 @@
     <article class="card"><h3 id="secret-redaction">Secret redaction</h3><p>Text tool output passes through a redactor for provider tokens, secret keyword patterns, and common sensitive values. Current benchmarks are synthetic and internal; the model continues to evolve.</p></article>
     <article class="card"><h3 id="capability-lock">Capability lock</h3><p>Capability packs have digests and tamper detection. An invalid lock fails closed and never expands permissions automatically.</p></article>
     <article class="card"><h3 id="human-action-gate">Human-action gate</h3><p>Destructive or external-provider actions require explicit operator confirmation even in full-access mode. The gate covers direct tools, decoded MCP proxy calls, GitHub CLI writes, and non-GET HTTP shell forms.</p></article>
-    <article class="card"><h3 id="verify-evidence">Verification evidence</h3><p>A completed handoff requires observed bash results, not an unsupported statement that tests passed.</p></article>
+    <article class="card"><h3 id="verify-evidence">Real checks</h3><p>In company mode the Harness only counts a check that actually ran and passed on the final code; saying “tested” is not enough.</p></article>
   </div>
 
   <div class="callout">

package/docs-site/content/en/team.html

@@ -1,10 +1,10 @@
 <section class="section">
   <div class="split">
-    <article class="card"><h3 id="do">Do</h3><p>Run <span class="inline-code">/onboard run</span>, apply <span class="inline-code">/profile auto</span>, use <span class="inline-code">/workflow</span>, execute real verification, and state blockers clearly.</p></article>
+    <article class="card"><h3 id="do">Do</h3><p>Ask the agent to read the project and record its context, apply <span class="inline-code">/profile auto</span>, assign work in plain language, run real checks, and state blockers clearly.</p></article>
     <article class="card"><h3 id="avoid">Avoid</h3><p>Do not place tokens, authentication files, caches, sessions, private examples, or project-specific business logic in the public core package.</p></article>
   </div>
   <div class="callout ok-callout">
-    <strong>Handoff standard</strong>
+    <strong>The final answer</strong>
     <p>A final response should briefly state what changed, which verification ran, whether subagents were used, and which risks or next steps require review.</p>
   </div>
   <div class="callout">

package/docs-site/content/en/whats-new.html

@@ -1,3 +1,91 @@
+<section class="section">
+  <p class="section-kicker">v1.9.0 · 2026-10-02</p>
+  <h2 id="v1-9-0">Ask in plain language; the team's Harness does the checking</h2>
+  <p class="section-lead">The task contract and the workflow commands are gone: you ask as you would ask a colleague, and the guard still checks every tool call. Company mode runs through Agent Studio and Agent Watch; its Harness asks for checks, has a subagent review the change and sends blocking findings back to the agent. See <a href="/en/ecosystem">Ecosystem</a>.</p>
+
+  <div class="benchmark-metrics" aria-label="Release 1.9.0 verification figures">
+    <div class="benchmark-metric"><span>Live scenarios</span><strong>13/13</strong><small>9 personal, 4 company, on the final install</small></div>
+    <div class="benchmark-metric"><span>Automated tests</span><strong>5,800+</strong><small>unit, integration and security; 0 failures</small></div>
+    <div class="benchmark-metric"><span>Browser tests</span><strong>27/27</strong><small>dashboard and WebUI on Chromium</small></div>
+    <div class="benchmark-metric"><span>Smaller guard</span><strong>−854 lines</strong><small>code that only served the task contract (4993 → 4139)</small></div>
+  </div>
+
+  <figure class="shot">
+    <img src="/assets/shots/company-run-done.jpg" alt="A company-mode turn: the agent changes code and runs the tests; A check passed and Review found no blocking issue are written under the answer" loading="lazy" width="1600" height="1000">
+    <figcaption>A company-mode turn: the agent changes code and runs the tests, a subagent reviews the change, and the outcome is written right under the answer.</figcaption>
+  </figure>
+
+  <div class="grid cols-3">
+    <article class="card"><h3 id="freeform">Plain-language requests</h3><p>No more <span class="inline-code">/workflow</span>, <span class="inline-code">/fresh</span>, <span class="inline-code">/onboard</span> or task contract. The guard still blocks protected files and checks permission profiles, oversized files and stale edits, and asks you before a push or publish.</p></article>
+    <article class="card"><h3 id="harness">The team's Harness</h3><p>Studio decides whether each turn suggests or requires a plan, checks and a review. A separate subagent reviews; blocking findings go back to the agent within the team's fix rounds.</p></article>
+    <article class="card"><h3 id="network">Network on approval</h3><p>Company-mode commands run without network. To install a package the agent asks to run that one command with network; the card shows the exact command and you allow it once.</p></article>
+    <article class="card"><h3 id="stop">Stop and continue</h3><p>Stop works for the whole turn, including while the review runs. A stopped turn says it was stopped, not that the model failed; Continue picks up from the steps kept.</p></article>
+    <article class="card"><h3 id="reconnect">Reconnect company mode</h3><p>If the company runtime is not running (after a restart or an update), the conversation says so and offers Reconnect in place.</p></article>
+    <article class="card"><h3 id="local-state">Out of git</h3><p><span class="inline-code">.pi/piagent-state</span> gets its own <span class="inline-code">.gitignore</span>; run state no longer shows up in the project's <span class="inline-code">git status</span>.</p></article>
+    <article class="card"><h3 id="queue">Waiting in line when the company is busy</h3><p>When every company model account is busy, a request waits its turn (up to 20 minutes) instead of failing. The running turn shows a “Wait for a free company account” step; Stop still works.</p></article>
+    <article class="card"><h3 id="many-conversations">Many conversations at once</h3><p>Creating or sending in one conversation is no longer refused because another one just changed. Two folders with the same name (two clones) also show where each one is.</p></article>
+    <article class="card"><h3 id="model-scope">Clean up models that are gone</h3><p><span class="inline-code">piagent-doctor</span> lists configured models Pi no longer knows; <span class="inline-code">piagent-model-scope --prune</span> removes only those lines.</p></article>
+  </div>
+</section>
+
+<section class="section">
+  <p class="section-kicker">From the dashboard</p>
+  <h2 id="v1-9-0-shots">What a member sees while working</h2>
+  <div class="shot-grid">
+    <figure class="shot">
+      <img src="/assets/shots/network-approval.jpg" alt="Approval card for one network command, showing the exact npm install command" loading="lazy" width="1600" height="1000">
+      <figcaption>Approving one network command: the card shows the exact command and what allow or deny does.</figcaption>
+    </figure>
+    <figure class="shot">
+      <img src="/assets/shots/new-chat-models.jpg" alt="Choosing a model for a new conversation: Company and Personal groups" loading="lazy" width="1600" height="1000">
+      <figcaption>New conversation: a company model or a personal one, in the same dashboard.</figcaption>
+    </figure>
+    <figure class="shot">
+      <img src="/assets/shots/company-review-running.jpg" alt="Review running: the header shows Subagent 1/2 and Stop is still available" loading="lazy" width="1600" height="1000">
+      <figcaption>Review running: the header shows Subagent 1/2 and Stop still works.</figcaption>
+    </figure>
+    <figure class="shot">
+      <img src="/assets/shots/personal-edit-test.jpg" alt="A personal turn that edits code, with the diff inside the Edit card" loading="lazy" width="1600" height="1000">
+      <figcaption>Personal mode: every read, edit and command is a card, with the diff right there.</figcaption>
+    </figure>
+  </div>
+</section>
+
+<section class="section">
+  <p class="section-kicker">Verification</p>
+  <h2 id="v1-9-0-verification">Run for real, the way a member works</h2>
+  <p class="section-lead">Each scenario drives a real browser against the installed release, sends messages as a member would and checks the result on disk. Every experience bug found was fixed with a test and the scenario run again.</p>
+  <div class="table-wrap"><table>
+    <thead><tr><th>Scenario</th><th>Result</th></tr></thead>
+    <tbody>
+      <tr><td>Company · strip Vietnamese accents from slugs, add tests</td><td>2 files changed, tests pass, "A check passed on the final code · Review found no blocking issue"</td></tr>
+      <tr><td>Company · press Stop while the review runs</td><td>"The turn stopped before its checks finished", no error shown</td></tr>
+      <tr><td>Company · install a package that needs network</td><td>The approval card shows the exact command; once allowed, the package is in <span class="inline-code">package.json</span></td></tr>
+      <tr><td>Company · send another message during a turn</td><td>Held, sent when the turn ends, and answered</td></tr>
+      <tr><td>Personal · edit, test, commit and push</td><td>Push waits for approval in the browser; stopping a long command leaves no process behind</td></tr>
+      <tr><td>Personal · read <span class="inline-code">.env</span></td><td>Blocked without revealing values; the agent explains how to open it yourself</td></tr>
+    </tbody>
+  </table></div>
+  <p>Benchmark and journey results of earlier releases were measured with task contracts; they are historical, and 1.9.0 has not been measured again.</p>
+</section>
+
+<div class="callout">
+  <strong>Earlier releases</strong>
+  <p>The notes below describe earlier releases as they shipped. Since 1.9.0 the task contract, trajectories, completion receipts and workflow commands mentioned below are gone.</p>
+</div>
+
+<section class="section">
+  <p class="section-kicker">v1.8.0</p>
+  <h2 id="v1-8-0">Astra, Sol, and Luna in Piagent</h2>
+  <p class="section-lead">Pi 0.87.1 exposes all three GPT-6 models through the authenticated catalog. New sessions prefer Sol High; parent routing remains opt-in.</p>
+  <div class="grid cols-3">
+    <article class="card"><h3>Luna</h3><p>Focused, verifiable tasks: the low tier at Medium effort.</p></article>
+    <article class="card"><h3>Sol</h3><p>Everyday coding: the medium and high tiers; the new-session default is High when available.</p></article>
+    <article class="card"><h3>Astra</h3><p>Broad or ambiguous work: the ultra tier at Extra High. Explicit pins and existing sessions stay intact.</p></article>
+  </div>
+  <p>The router selects only authenticated models and records a legacy 5.6 fallback. The old 108-session result does not measure GPT-6 performance or token savings.</p>
+</section>
+
 <section class="section">
   <p class="section-kicker">v1.7.1</p>
   <h2 id="v1-7-0">Long sessions with clearer context and accounting</h2>
@@ -56,7 +144,7 @@
   <p class="section-kicker">Daily flow</p>
   <h2 id="usage-flow">The daily workflow does not break</h2>
   <div class="steps">
-    <article class="step"><div><h3>Assign work as before</h3><p>Use a natural-language request or <span class="inline-code">/workflow task &lt;request&gt;</span>. Manual preflight is optional.</p></div></article>
+    <article class="step"><div><h3>Assign work as before</h3><p>Use a natural-language request (<span class="inline-code">/workflow</span> was retired in 1.9.0). Manual preflight is optional.</p></div></article>
     <article class="step"><div><h3>The runtime records truth</h3><p>Task Contracts, context, changed files, trajectories, and checkpoints are updated from hooks and tool results rather than model memory.</p></div></article>
     <article class="step"><div><h3>Verify the exact working tree</h3><p>Only observed exact commands that exit successfully and match the current-tree digest count as passing evidence.</p></div></article>
     <article class="step"><div><h3>Bounded recovery or handoff</h3><p>Source repair and transient retries have ceilings. Unsafe cases return to handoff or the operator instead of continuing by guesswork.</p></div></article>

package/docs-site/content/en/workflows.html

@@ -1,20 +1,19 @@
 <section class="section">
   <p class="section-kicker">Workflow impact</p>
   <h2 id="conclusion">No new command is mandatory in the daily flow</h2>
-  <p class="section-lead">Users still assign work with a natural-language request or <span class="inline-code">/workflow task</span>. The main change is inside the runtime: task state, trajectories, verifier evidence, recovery, and completion gates are recorded more strictly. The new commands only expose that data when needed.</p>
+  <p class="section-lead">Since 1.9.0 work is assigned with a plain-language request and nothing else. <span class="inline-code">/workflow</span>, <span class="inline-code">/task</span>, <span class="inline-code">/fresh</span> and <span class="inline-code">/onboard</span> were retired together with the task contract: a session no longer records a contract, work plan, completion gate or receipt. The guard still checks every tool call.</p>
   <div class="callout ok-callout">
     <strong>Short answer</strong>
-    <p>The interaction flow is not longer. The control flow behind it is safer and fails closed when evidence is missing. A valid task does not require all four new commands.</p>
+    <p>Say what you want, including whether the agent may edit ("read-only, do not edit", "plan first", "implement and run the tests"). The inspection commands below are optional and never start a model turn.</p>
   </div>
   <div class="table-wrap">
     <table>
-      <thead><tr><th>Moment</th><th>User action stays the same</th><th>New automatic runtime behavior</th><th>Optional inspection command</th></tr></thead>
+      <thead><tr><th>Moment</th><th>What the user does</th><th>What the runtime does</th><th>Optional inspection command</th></tr></thead>
       <tbody>
-        <tr><td>Before a task</td><td>Send a request or <span class="inline-code">/workflow task &lt;request&gt;</span>.</td><td>Loads profile and context, classifies intent and risk, captures runtime truth, and computes a solver recommendation.</td><td><span class="inline-code">/task-preflight [--json] &lt;intent&gt;</span></td></tr>
-        <tr><td>During work</td><td>Continue the task normally.</td><td>Records the work plan, phase, changed files, tool and command results, checkpoints, helpers, and recovery events. The inspector updates below the footer.</td><td><span class="inline-code">/piagent-inspector</span> or <span class="inline-code">/piagent-status</span></td></tr>
-        <tr><td>Verify and review</td><td>Use project verification; call <span class="inline-code">/workflow review</span> when a separate review is useful.</td><td>Accepts only successful exact verifiers bound to the current working-tree identity.</td><td><span class="inline-code">/piagent-status</span></td></tr>
-        <tr><td>Completion or handoff</td><td>Receive the outcome and remaining risks as before.</td><td>Approves a receipt only when trace, work plan, acceptance, changed-file integrity, and the hard gate all pass.</td><td><span class="inline-code">/piagent-status</span></td></tr>
-        <tr><td>After a task</td><td>No new required step.</td><td>Keeps sourced telemetry without inferring quality.</td><td><span class="inline-code">/usage efficiency</span></td></tr>
+        <tr><td>Before the work</td><td>Send the request in plain language.</td><td>Loads the profile and project context.</td><td><span class="inline-code">/task-preflight [--json] &lt;intent&gt;</span></td></tr>
+        <tr><td>During the work</td><td>Follow along or answer a confirmation.</td><td>Checks each tool call: protected and read-only paths, permission profile, context budget for large files, edits against a stale read, and confirmation for destructive or external actions. The inspector updates below the footer.</td><td><span class="inline-code">/piagent-inspector</span> or <span class="inline-code">/piagent-status</span></td></tr>
+        <tr><td>Verify and review</td><td>Ask for the project's checks, or for a review of the current diff.</td><td>Runs the commands like any other tool call.</td><td><span class="inline-code">/piagent-inspector commands</span></td></tr>
+        <tr><td>After the work</td><td>No required step.</td><td>Keeps sourced telemetry without inferring quality.</td><td><span class="inline-code">/usage efficiency</span></td></tr>
       </tbody>
     </table>
   </div>
@@ -22,22 +21,22 @@
 
 <section class="section">
   <p class="section-kicker">Command semantics</p>
-  <h2 id="command-effects">How far the new commands affect a workflow</h2>
+  <h2 id="command-effects">How far the inspection commands affect a workflow</h2>
   <div class="table-wrap">
     <table>
       <thead><tr><th>Command</th><th>Reads or displays</th><th>Does not perform</th></tr></thead>
       <tbody>
-        <tr><td><span class="inline-code">/task-preflight</span></td><td>Intent, risk, scope, runtime, route, phase/tool/helper policy, backend, approval, and blockers.</td><td>Does not create a task, advance a phase, call a model, or grant implementation authority.</td></tr>
-        <tr><td><span class="inline-code">/piagent-status</span></td><td>Task Contract, trajectory, checkpoint, verifier, recovery, helper, resume, and terminal receipt from persisted evidence.</td><td>Does not edit files, rerun verification, retry work, or turn missing evidence into success.</td></tr>
-        <tr><td><span class="inline-code">/piagent-inspector</span></td><td>Observed task files in the four-row footer panel, exact baseline delta in the <span class="inline-code">files</span> view, current tool, command failures and blocks, safety warnings, and context budget. No argument opens the menu.</td><td>Does not edit files, execute commands, change completion state, or estimate tokens for each built-in tool.</td></tr>
-        <tr><td><span class="inline-code">/usage efficiency</span></td><td>Sourced context telemetry and task metrics; unavailable facts remain <span class="inline-code">null</span> or unavailable.</td><td>Does not grade a person or model and does not decide the completion gate.</td></tr>
-        <tr><td><span class="inline-code">/piagent-orchestration</span></td><td>Current mode, helper mode, subagent limit, review lenses, Field Guide, and writer policy.</td><td>Does not change mode, spawn a helper, or enable parallel writers.</td></tr>
+        <tr><td><span class="inline-code">/task-preflight</span></td><td>Context and the deterministic shadow route for an intent.</td><td>Does not create anything, call a model, or grant implementation authority.</td></tr>
+        <tr><td><span class="inline-code">/piagent-status</span></td><td>Profile, guard, runtime and authenticated model state.</td><td>Does not edit files, rerun verification or retry work.</td></tr>
+        <tr><td><span class="inline-code">/piagent-inspector</span></td><td>Changed files in the four-row footer panel, current tool, command failures and blocks, safety warnings, and context budget. No argument opens the menu.</td><td>Does not edit files, execute commands, or estimate tokens for each built-in tool.</td></tr>
+        <tr><td><span class="inline-code">/usage efficiency</span></td><td>Sourced context telemetry; unavailable facts remain <span class="inline-code">null</span> or unavailable.</td><td>Does not grade a person or model.</td></tr>
+        <tr><td><span class="inline-code">/piagent-orchestration</span></td><td>Current mode, helper mode, helper limit, review lenses, Field Guide, and writer policy.</td><td>Does not change mode, spawn a helper, or enable parallel writers.</td></tr>
       </tbody>
     </table>
   </div>
   <div class="callout">
     <strong>Only explicit opt-in changes behavior.</strong>
-    <p>These five commands are read-only. Behavior changes only when an operator deliberately enables a rollout setting such as phase tools or helper mode; parent routing, automatic workers, and multiple writers do not turn on automatically.</p>
+    <p>These five commands are read-only. Behavior changes only when an operator deliberately enables a setting such as helper mode; parent routing, automatic workers, and multiple writers do not turn on automatically.</p>
   </div>
 </section>
 
@@ -46,14 +45,13 @@
   <h2 id="example-flow">A complete flow can look like this</h2>
   <div class="command-grid">
     <article class="command-card">
-      <header><span>Inspect → implement → review → receipt</span><button class="clip-btn" data-clip="/task-preflight --json Fix the failing checkout test&#10;/workflow task Fix the failing checkout test and verify.&#10;/piagent-inspector&#10;/workflow review current diff&#10;/piagent-status&#10;/usage efficiency">Copy</button></header>
+      <header><span>Inspect → implement → review</span><button class="clip-btn" data-clip="/task-preflight --json Fix the failing checkout test&#10;Fix the failing checkout test and run the project tests.&#10;/piagent-inspector&#10;Review the current diff: correctness, missing tests, scope drift. Read-only.&#10;/usage efficiency">Copy</button></header>
       <pre><code>/task-preflight --json Fix the failing checkout test
-/workflow task Fix the failing checkout test and verify.
+Fix the failing checkout test and run the project tests.
 /piagent-inspector
-/workflow review current diff
-/piagent-status
+Review the current diff: correctness, missing tests, scope drift. Read-only.
 /usage efficiency</code></pre>
-      <p>Only <span class="inline-code">/workflow task</span> starts implementation. The inspector opens a menu for files, commands, safety, and context; preflight, inspector, status, and efficiency are optional. Use a separate review when the scope or handoff policy calls for one.</p>
+      <p>Only the plain-language lines start model work. Preflight, inspector and efficiency are optional views.</p>
     </article>
   </div>
 </section>
@@ -61,21 +59,21 @@
 <section class="section">
   <div class="callout ok-callout">
     <strong>Git in Pi Agent</strong>
-    <p>There is no separate <span class="inline-code">/git</span> namespace. Use <span class="inline-code">/workflow commit</span> for a reviewed local commit and <span class="inline-code">/workflow pr</span> to prepare a pull request. Actions such as <span class="inline-code">git push</span> or broad staging with <span class="inline-code">git add -A</span> still require operator confirmation.</p>
+    <p>There is no <span class="inline-code">/git</span> namespace and no workflow command. Ask for a commit or a pull request in plain language. <span class="inline-code">git push</span>, GitHub writes and broad staging such as <span class="inline-code">git add -A</span> still require operator confirmation.</p>
   </div>
   <div class="callout">
     <strong>Parent-direct orchestration</strong>
-    <p>Use <span class="inline-code">/piagent-orchestration</span> to inspect the one-helper ceiling, dispatch/skip reason, projected token saving, review lenses, Field Guide, and writer policy. Helpers default to off. Explicit opt-in still permits only one fresh read-only helper when two independent lanes and at least 30% projected net saving are proven; workers and retries stay disabled.</p>
+    <p>Use <span class="inline-code">/piagent-orchestration</span> to inspect the helper ceiling, dispatch/skip reason, review lenses, Field Guide, and writer policy. Helpers default to off. With explicit opt-in the parent may use up to two fresh read-only helpers; token-saving estimates are telemetry, not a gate. Workers and retries stay disabled.</p>
   </div>
   <div class="command-grid">
-    <article class="command-card"><header><span>Bounded implementation</span><button class="clip-btn" data-clip="/workflow task Fix the failing checkout test and verify.">Copy</button></header><pre><code>/workflow task Fix the failing checkout test and verify.</code></pre></article>
-    <article class="command-card"><header><span>Read-only scout</span><button class="clip-btn" data-clip="/workflow scout Map the auth flow and risk areas.">Copy</button></header><pre><code>/workflow scout Map the auth flow and risk areas.</code></pre></article>
-    <article class="command-card"><header><span>Plan before coding</span><button class="clip-btn" data-clip="/workflow plan Add multi-tenant billing support.">Copy</button></header><pre><code>/workflow plan Add multi-tenant billing support.</code></pre></article>
-    <article class="command-card"><header><span>Review a diff</span><button class="clip-btn" data-clip="/workflow review current diff">Copy</button></header><pre><code>/workflow review current diff</code></pre></article>
-    <article class="command-card"><header><span>Guarded local commit</span><button class="clip-btn" data-clip="/workflow commit &quot;feat: add guarded git workflow&quot;">Copy</button></header><pre><code>/workflow commit "feat: add guarded git workflow"</code></pre></article>
-    <article class="command-card"><header><span>Prepare a pull request</span><button class="clip-btn" data-clip="/workflow pr &quot;Prepare PR for guarded git workflow&quot;">Copy</button></header><pre><code>/workflow pr "Prepare PR for guarded git workflow"</code></pre></article>
-    <article class="command-card"><header><span>Backend spec to frontend</span><button class="clip-btn" data-clip="/profile be-readonly-fe&#10;/workflow be-to-fe Implement frontend support for the new user status endpoint.">Copy</button></header><pre><code>/profile be-readonly-fe
-/workflow be-to-fe Implement frontend support for the new user status endpoint.</code></pre></article>
-    <article class="command-card"><header><span>Improve the platform</span><button class="clip-btn" data-clip="/workflow platform-improve Harden command docs and run verification.">Copy</button></header><pre><code>/workflow platform-improve Harden command docs and run verification.</code></pre></article>
+    <article class="command-card"><header><span>Implementation</span><button class="clip-btn" data-clip="Fix the failing checkout test and run the project tests.">Copy</button></header><pre><code>Fix the failing checkout test and run the project tests.</code></pre></article>
+    <article class="command-card"><header><span>Read-only scout</span><button class="clip-btn" data-clip="Map the auth flow and risk areas. Read-only, do not edit.">Copy</button></header><pre><code>Map the auth flow and risk areas. Read-only, do not edit.</code></pre></article>
+    <article class="command-card"><header><span>Plan before coding</span><button class="clip-btn" data-clip="Plan multi-tenant billing support. Do not edit code yet.">Copy</button></header><pre><code>Plan multi-tenant billing support. Do not edit code yet.</code></pre></article>
+    <article class="command-card"><header><span>Review a diff</span><button class="clip-btn" data-clip="Review the current diff: correctness, missing tests, scope drift. Read-only.">Copy</button></header><pre><code>Review the current diff: correctness, missing tests, scope drift. Read-only.</code></pre></article>
+    <article class="command-card"><header><span>Local commit</span><button class="clip-btn" data-clip="Commit the two docs files with message &quot;docs: update onboarding notes&quot;. Do not push.">Copy</button></header><pre><code>Commit the two docs files with message "docs: update onboarding notes". Do not push.</code></pre></article>
+    <article class="command-card"><header><span>Pull request</span><button class="clip-btn" data-clip="Open a draft pull request for this branch titled &quot;Harden command docs&quot;.">Copy</button></header><pre><code>Open a draft pull request for this branch titled "Harden command docs".</code></pre></article>
+    <article class="command-card"><header><span>Backend spec to frontend</span><button class="clip-btn" data-clip="/profile be-readonly-fe&#10;Implement frontend support for the new user status endpoint. Backend is read-only.">Copy</button></header><pre><code>/profile be-readonly-fe
+Implement frontend support for the new user status endpoint. Backend is read-only.</code></pre></article>
+    <article class="command-card"><header><span>Onboard a project</span><button class="clip-btn" data-clip="Inspect this project read-only and record its project context.">Copy</button></header><pre><code>Inspect this project read-only and record its project context.</code></pre></article>
   </div>
 </section>

package/docs-site/content/index.html

@@ -1,8 +1,8 @@
 <section class="hero">
-  <p class="eyebrow">Team operating docs</p>
-  <h1>Pi runtime được đóng gói như một nền tảng dùng lại cho nhiều dự án.</h1>
+  <p class="eyebrow">Piagent 1.9.0</p>
+  <h1>Coding agent cho cả team, kiểm tra từng bước.</h1>
   <p>
-    Tài liệu này gom phần cài đặt, profile, quyền chạy, MCP, bảo mật và workflow vào một nơi duy nhất. Mục tiêu là thành viên mới chỉ cần mở trang này, chọn đúng command, chạy đúng chế độ và biết ranh giới an toàn.
+    Một dashboard cho Terminal và trình duyệt. Dùng model bằng tài khoản của bạn, hoặc model của công ty qua Agent Watch và Agent Studio. Guard kiểm tra từng tool call; ở chế độ công ty, Harness của team tự yêu cầu chạy check, cho subagent review và báo kết quả ngay dưới câu trả lời.
   </p>
   <div class="owner-strip" aria-label="Thông tin dự án">
     <span class="owner-label">Project links</span>
@@ -12,14 +12,24 @@
   </div>
   <div class="hero-actions">
     <a class="button primary" href="/quickstart">Bắt đầu</a>
-    <a class="button" href="/whats-new">Có gì mới</a>
+    <a class="button" href="/ecosystem">Hệ sinh thái</a>
+    <a class="button" href="/whats-new">Có gì mới trong 1.9.0</a>
     <a class="button" href="/commands">Xem command</a>
-    <a class="button" href="/mcp">MCP</a>
   </div>
 </section>
 
 <section class="section">
-  <p class="section-kicker">Production V1 · bằng chứng public của v1.6.0</p>
+  <p class="section-kicker">Bản 1.9.0</p>
+  <h2 id="ban-1-9-0">Một lượt làm việc ở chế độ công ty</h2>
+  <p class="section-lead">Bạn nhắn việc cần làm. Agent đọc, sửa và chạy test trong sandbox; một subagent review bản sửa; dòng cuối ghi kết quả. Đã chạy thật 13/13 kịch bản trên bản cài cuối, 27/27 test trình duyệt.</p>
+  <figure class="shot">
+    <img src="/assets/shots/company-run-done.jpg" alt="Dashboard Piagent: một lượt ở chế độ công ty với các bước đọc, sửa, chạy test và dòng Check đã qua trên code cuối, Review không có lỗi chặn" width="1600" height="1000">
+    <figcaption>Dashboard Piagent ở chế độ công ty. Xem toàn cảnh ở <a href="/ecosystem">Hệ sinh thái</a> và mọi thay đổi ở <a href="/whats-new">Có gì mới</a>.</figcaption>
+  </figure>
+</section>
+
+<section class="section">
+  <p class="section-kicker">Production V1 · bằng chứng lịch sử của v1.6.0</p>
   <h2 id="bang-chung">Đo được, không phải nói suông</h2>
   <p class="section-lead">Run gắn với release <code>production-v1-20260824T040017Z-05b7cf</code> đã đo 108 session bằng GPT-5.6 Luna Medium tại tag <code>v1.6.0</code>, đúng commit <code>3bba8f0b3ff521bc2a355e1f6bef6d1bbdc09511</code>, với Piagent so với <code>codex-cli</code>.</p>
 
@@ -79,14 +89,19 @@ piagent-setup</code></pre>
   <h2 id="bat-dau-tu-dau">Bắt đầu từ đâu</h2>
   <div class="card-grid">
     <a class="doc-card" href="/whats-new">
-      <span class="card-kicker">Product update</span>
+      <span class="card-kicker">Bản 1.9.0</span>
       <h3>Có gì mới</h3>
-      <p>Runtime truth, task trajectory, recovery, helper policy và completion receipt fail-closed — phần nào tự chạy, phần nào cần opt-in.</p>
+      <p>Giao việc bằng lời thường, Harness của team, lệnh có mạng theo lần duyệt, nút Dừng suốt lượt và thẻ duyệt dễ đọc.</p>
+    </a>
+    <a class="doc-card" href="/ecosystem">
+      <span class="card-kicker">Get started</span>
+      <h3>Hệ sinh thái</h3>
+      <p>Piagent, Agent Watch và Agent Studio: phần nào chạy ở đâu, khi nào dùng chế độ cá nhân hay công ty.</p>
     </a>
     <a class="doc-card" href="/quickstart">
       <span class="card-kicker">Get started</span>
       <h3>Quickstart</h3>
-      <p>Cài, mở repo, onboard context, chọn profile và permission, chạy task đầu tiên, verify trước khi handoff.</p>
+      <p>Cài, mở repo, chọn profile và quyền, rồi giao việc đầu tiên bằng lời thường.</p>
     </a>
     <a class="doc-card" href="/scope">
       <span class="card-kicker">Get started</span>

package/docs-site/content/quickstart.html

@@ -65,12 +65,11 @@ pi</code></pre>
 
     <article class="step">
       <div>
-        <h3 id="onboard-context">Onboard context</h3>
-        <p>Chạy một lần ở repo mới để ghi context, verify matrix và protected areas vào <span class="inline-code">.pi/</span>. <span class="inline-code">/onboard</span> mở menu/status; <span class="inline-code">run</span> mới launch workflow đọc project.</p>
+        <h3 id="onboard-context">Cho agent đọc project</h3>
+        <p>Ở repo mới, nhờ agent đọc project (chỉ đọc) và ghi lại project context vào <span class="inline-code">.pi/</span>. Không cần lệnh riêng: nói bằng lời thường.</p>
         <div class="command-card">
-          <header><span>Onboard</span><button class="clip-btn" data-clip="/onboard&#10;/onboard run">Lấy lệnh</button></header>
-          <pre><code>/onboard
-/onboard run</code></pre>
+          <header><span>Đọc project</span><button class="clip-btn" data-clip="Đọc project này (chỉ đọc) và ghi lại project context.">Lấy lệnh</button></header>
+          <pre><code>Đọc project này (chỉ đọc) và ghi lại project context.</code></pre>
         </div>
       </div>
     </article>
@@ -102,20 +101,19 @@ pi</code></pre>
     <article class="step">
       <div>
         <h3 id="chay-workflow">Chạy workflow</h3>
-        <p>Dùng command đúng mục tiêu để agent không phải diễn giải quá dài. Task nào nặng context thì dùng fresh session.</p>
+        <p>Nói rõ việc và ý định (sửa, chỉ đọc, lập plan) bằng lời thường. Việc nào nặng context thì mở session mới bằng <span class="inline-code">/new</span>.</p>
         <div class="command-card">
-          <header><span>Workflow</span><button class="clip-btn" data-clip="/workflow task Implement the requested bounded change.&#10;/workflow review current diff&#10;/fresh task Implement the requested bounded change.">Lấy lệnh</button></header>
-          <pre><code>/workflow task Implement the requested bounded change.
-/workflow review current diff
-/fresh task Implement the requested bounded change.</code></pre>
+          <header><span>Giao việc</span><button class="clip-btn" data-clip="Implement thay đổi được yêu cầu rồi chạy test của project.&#10;Review diff hiện tại. Chỉ đọc.">Lấy lệnh</button></header>
+          <pre><code>Implement thay đổi được yêu cầu rồi chạy test của project.
+Review diff hiện tại. Chỉ đọc.</code></pre>
         </div>
       </div>
     </article>
 
     <article class="step">
       <div>
-        <h3 id="verify-truoc-khi-handoff">Verify trước khi handoff</h3>
-        <p>Final gate chỉ tin kết quả command đã chạy thật, exit 0, và khớp verify plan. Sau khi pin hoặc nâng version, chạy doctor trên project:</p>
+        <h3 id="verify-truoc-khi-handoff">Kiểm tra trước khi giao</h3>
+        <p>Nhờ agent chạy check của project (test, type check, build) và đọc kết quả thật; ở chế độ công ty, Harness tự yêu cầu việc này. Sau khi pin hoặc nâng version, chạy doctor trên project:</p>
         <div class="command-card">
           <header><span>Doctor</span><button class="clip-btn" data-clip="piagent-doctor">Lấy lệnh</button></header>
           <pre><code>piagent-doctor</code></pre>

package/docs-site/content/runtime.html

@@ -6,8 +6,8 @@
       <pre><code>piagent-setup --mcp-preset core --subagents-preset safe</code></pre>
     </article>
     <article class="command-card">
-      <header><span>Full update</span><button class="clip-btn" data-clip="npm install -g --ignore-scripts @earendil-works/pi-coding-agent@0.86.1&#10;npm install -g --ignore-scripts @piagent/platform@X.Y.Z&#10;piagent-install --stable --dry-run&#10;piagent-install --stable">Lấy lệnh</button></header>
-      <pre><code>npm install -g --ignore-scripts @earendil-works/pi-coding-agent@0.86.1
+      <header><span>Full update</span><button class="clip-btn" data-clip="npm install -g --ignore-scripts @earendil-works/pi-coding-agent@0.87.1&#10;npm install -g --ignore-scripts @piagent/platform@X.Y.Z&#10;piagent-install --stable --dry-run&#10;piagent-install --stable">Lấy lệnh</button></header>
+      <pre><code>npm install -g --ignore-scripts @earendil-works/pi-coding-agent@0.87.1
 npm install -g --ignore-scripts @piagent/platform@X.Y.Z
 piagent-install --stable --dry-run
 piagent-install --stable</code></pre>

package/docs-site/content/security.html

@@ -22,8 +22,8 @@
       <p>Destructive hoặc external-provider action vẫn cần operator xác nhận rõ, kể cả khi full-access đang bật. Gate áp dụng cho direct tool, MCP proxy đã decode và các shell form như GitHub CLI write hoặc HTTP non-GET.</p>
     </article>
     <article class="card">
-      <h3 id="verify-evidence">Verify evidence</h3>
-      <p>Handoff hoàn tất cần bằng chứng verify từ bash result đã quan sát, không nhận câu trả lời “đã test” suông.</p>
+      <h3 id="verify-evidence">Check thật</h3>
+      <p>Ở chế độ công ty, Harness chỉ tính một check đã chạy thật và qua trên code cuối; câu “đã test” suông không đủ.</p>
     </article>
   </div>
 

package/docs-site/content/team.html

@@ -3,7 +3,7 @@
   <div class="split">
     <article class="card">
       <h3 id="viec-nen-lam">Việc nên làm</h3>
-      <p>Chạy <span class="inline-code">/onboard run</span>, áp <span class="inline-code">/profile auto</span>, dùng <span class="inline-code">/workflow</span>, verify thật và ghi blockers rõ ràng.</p>
+      <p>Nhờ agent đọc project và ghi project context, áp <span class="inline-code">/profile auto</span>, giao việc bằng lời thường, chạy check thật và nói rõ việc còn vướng.</p>
     </article>
     <article class="card">
       <h3 id="viec-nen-tranh">Việc nên tránh</h3>
@@ -12,7 +12,7 @@
   </div>
 
   <div class="callout ok-callout">
-    <strong>Chuẩn handoff</strong>
+    <strong>Câu trả lời cuối</strong>
     <p>Final response nên nói ngắn: đã đổi gì, verify nào đã chạy, có dùng subagent không, và còn rủi ro hoặc next step nào cần người review.</p>
   </div>