dos-kernel 0.23.4__tar.gz → 0.25.0__tar.gz

{dos_kernel-0.23.4/src/dos_kernel.egg-info → dos_kernel-0.25.0}/PKG-INFO

@@ -1,15 +1,18 @@
 Metadata-Version: 2.4
 Name: dos-kernel
-Version: 0.23.4
+Version: 0.25.0
 Summary: Dispatch Operating System — the domain-free trust substrate for fleets of autonomous agents (verdict spine, ship oracle, structured refusal, lane arbiter, correlation spine).
 Author: Anthony Chaudhary
 License: MIT
 Project-URL: Homepage, https://github.com/anthony-chaudhary/dos-kernel
+Project-URL: Website, https://anthony-chaudhary.github.io/dos-kernel/
 Project-URL: Documentation, https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/QUICKSTART.md
+Project-URL: FAQ, https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/FAQ.md
+Project-URL: llms.txt, https://raw.githubusercontent.com/anthony-chaudhary/dos-kernel/master/llms.txt
 Project-URL: Repository, https://github.com/anthony-chaudhary/dos-kernel
 Project-URL: Issues, https://github.com/anthony-chaudhary/dos-kernel/issues
 Project-URL: Changelog, https://github.com/anthony-chaudhary/dos-kernel/tree/master/docs/releases
-Keywords: agents,ai-agents,llm,multi-agent,agent-orchestration,orchestration,dispatch,scheduler,oracle,leases,verification,trust,mcp
+Keywords: agents,ai-agents,llm,multi-agent,agent-orchestration,orchestration,dispatch,scheduler,oracle,leases,verification,trust,mcp,claude,claude-code,mcp-server,model-context-protocol,agent-verification,autonomous-agents,agent-monitoring
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: MIT License
@@ -96,7 +99,23 @@ zero config, and the only thing you ever install is one small Python package.
 > ⏱️ **Want to try it right now?** Jump to **[Try it in 60 seconds](#try-it-in-60-seconds)**
 > — one command, real output, then come back for the why.
 
-<sub>**v0.23.4** · 3900+ tests · CI: Python 3.11–3.13 on Linux + a Windows 3.13
+> ⚡ **Or just add it — two commands, zero decisions.** From the repo where your
+> agent works:
+>
+> ```bash
+> pip install dos-kernel
+> dos init --hooks auto   # finds the agent runtime(s) you already use, wires in the checks
+> ```
+>
+> From then on: your agent can't tell you **"done"** unless the work actually
+> landed, two agents can't silently overwrite each other's files, and a run
+> that stalls gets flagged instead of quietly spinning. Nothing about your
+> workflow changes, and you don't need to learn any of the vocabulary below to
+> be covered. It prints the one config file it wrote; deleting the `dos hook`
+> entries there undoes it. (No runtime detected? It says so and lists the
+> names to pick from — it never guesses.)
+
+<sub>**v0.25.0** · 3900+ tests · CI: Python 3.11–3.13 on Linux + a Windows 3.13
 smoke run · the only runtime dependency is **PyYAML** · **MIT**.</sub>
 
 > 🧭 **Want it in plain words first?** What DOS is, what it catches, and what
@@ -111,6 +130,13 @@ smoke run · the only runtime dependency is **PyYAML** · **MIT**.</sub>
 > your work, the ~5 files actually worth reading, and the architecture rules a
 > change must satisfy.
 
+> 🔤 **Five words the rest of this page leans on.** A **plan** is a named goal
+> (`AUTH`); a **phase** is one shippable step of it (`AUTH1`); a **lane** is the
+> slice of the file tree one agent may touch; the **oracle** is the part of DOS
+> that reads the evidence and rules; a **stamp** is the mark a shipped phase
+> leaves in a commit subject (`AUTH1: …`) — the thing the oracle greps for.
+> That's the whole vocabulary.
+
 <a id="who-this-is-for"></a>
 
 ## Who this is for
@@ -209,8 +235,8 @@ echo 'def login(): ...' > login.py
 git add -A
 git commit -m "AUTH1: ship the login endpoint"   # stamp AUTH1 shipped: <PHASE-ID>: <message>
 
-dos verify --workspace . AUTH AUTH1   # → SHIPPED     AUTH AUTH1 e389e8b (via grep-subject)   exit 0
-dos verify --workspace . AUTH AUTH2   # → NOT_SHIPPED  AUTH AUTH2          (via none)          exit 1
+dos verify --workspace . AUTH AUTH1   # → SHIPPED     AUTH AUTH1 <your-sha> (via grep-subject)  exit 0
+dos verify --workspace . AUTH AUTH2   # → NOT_SHIPPED  AUTH AUTH2            (via none)          exit 1
 ```
 
 An agent can claim `AUTH2` is done all day long; `verify` just reports what the
@@ -542,9 +568,11 @@ first (`dos_verify` "did it ship?", `dos_commit_audit` "does this commit's claim
 match its diff?", `dos_status` one folded fact about a run), then
 `dos_arbitrate` (may two workers run without colliding?), the structured-refusal
 pair (`dos_refuse_reasons` / `dos_check_reason`), `dos_recall` (is this recalled
-memory still true?), and `dos_doctor` (the workspace report) — so any
-MCP-speaking host — Claude Desktop, Cursor, Cline, Trae, an Agent-SDK app — can
-call the referee over JSON-on-stdio with zero Python coupling. Each verdict comes
+memory still true?), `dos_citation_resolve` (does this cited legal case exist in
+a third-party reporter? — the *Mata v. Avianca* witness), and `dos_doctor` (the
+workspace report) — so any
+MCP-speaking host — Claude Desktop, Claude Cowork, Cursor, Cline, Trae, an
+Agent-SDK app — can call the referee over JSON-on-stdio with zero Python coupling. Each verdict comes
 back with a one-line interpretation of what it means for the agent's next move.
 (See **[the MCP server surface](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/80_mcp-server-surface.md)**.)
 
@@ -566,22 +594,37 @@ DOS's hooks into the runtime you actually run. One command per host — it write
 that host's own hook-config file, merged into anything already there:
 
 ```bash
+dos init --hooks auto .          # don't know the names below? this detects the
+                                 # runtime(s) this repo already uses and wires them all
 dos init --hooks claude-code .   # .claude/settings.json
 dos init --hooks cursor .        # .cursor/hooks.json
 dos init --hooks codex .         # .codex/config.toml
 dos init --hooks gemini .        # .gemini/settings.json
 dos init --hooks antigravity .   # .agents/hooks.json
+dos init --hooks claude-cowork . # the SAME .claude/settings.json Claude Code reads
 ```
 
 That binds three shipped hooks: `pretool` denies a structurally-refused call
 before it runs, `stop` refuses a stop on an unverified "done," `posttool`
 re-surfaces a stalled stream. This is the **enforcement** path (the *host*
 denies on a DOS verdict) — the complement to MCP's advisory path. Until
-recently this spoke only Claude Code; it now installs across five hosts —
-Claude Code, Cursor, Codex, Gemini, and Antigravity
+recently this spoke only Claude Code; it now installs across six hosts —
+Claude Code, Cursor, Codex, Gemini, Antigravity, and Claude Cowork
 ([docs/221](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/221_the-cross-vendor-hook-installer.md),
-[docs/269](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/269_antigravity-the-fifth-host.md)).
-`--with-hooks` is the back-compat alias for `--hooks claude-code`.
+[docs/269](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/269_antigravity-the-fifth-host.md),
+[docs/298](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/298_claude-cowork-the-sixth-host-shared-surface.md)).
+`--with-hooks` is the back-compat alias for `--hooks claude-code`. `auto`
+([docs/303](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/303_hooks-auto-detection-plan.md))
+names the host *for* you: it probes which of those config dirs already exist in
+the repo — plus the shell's own environment, so a fresh repo opened inside
+Claude Code still detects — wires every runtime it finds (a shared config file
+is wired once), and fails loud with the list above when nothing is detectable,
+never guessing. Claude
+Cowork is the *shared-surface* host: it runs the same agent harness as Claude
+Code, so wiring either name binds both — one file, one set of hooks. (One
+honest caveat, carried on the install note itself: the Cowork app doesn't
+*fire* hooks yet — anthropics/claude-code#63360 — so until that closes,
+Cowork's working DOS surface is the advisory one above.)
 
 Under the installer sits a pluggable dialect seam: the verdict is decided
 once, then rendered into whatever JSON shape the host parses
@@ -593,12 +636,15 @@ reads (wire it in `cli-config.yaml`). A new host's dialect is a driver, never a
 kernel edit.
 
 The flip side of that honesty: a host with **no** hook seam gets **no** dialect.
-ByteDance's **Trae** was proved out and has no hook system at all (no lifecycle
-events, no deny/allow stdout contract), so DOS binds to it advisory-only — the
-MCP server in `.trae/mcp.json`, a verify-before-"done" rule in
-`.trae/rules/project_rules.md`, the generic skills in `.trae/skills/` — and
-`dos init --hooks trae` fails loud rather than writing config Trae would never
-read ([docs/294](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/294_trae-advisory-only-the-host-with-no-hook-seam.md)).
+ByteDance's **Trae** was proved out and ships no user-scriptable hook system in
+its personal/international editions (no lifecycle events, no deny/allow stdout
+contract; its CN-enterprise edition announced one on 2026-06-09 with no
+published grammar yet), so DOS binds to it advisory-only — the MCP server in
+`.trae/mcp.json` (read alike by IDE-mode Agent, SOLO mode, and TRAE CLI), a
+verify-before-"done" rule in `.trae/rules/project_rules.md`, the generic
+skills in `.trae/skills/` — and `dos init --hooks trae` fails loud rather than
+writing config Trae would never read
+([docs/294](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/294_trae-advisory-only-the-host-with-no-hook-seam.md)).
 An invented envelope would be fake enforcement, which is the exact failure the
 dialect seam exists to prevent.
 
@@ -688,14 +734,14 @@ channel, upgrade/uninstall, WSL, troubleshooting) is in
 **[docs/INSTALL.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/INSTALL.md)**:
 
 ```bash
-# uv — the modern, fast, isolated CLI install (recommended):
-uv tool install dos-kernel        # `dos` + `dos-mcp` on PATH
-uvx --from dos-kernel dos doctor  # or run it once, ephemerally
-
-# pip — the library-consumer path (a host pins dos-kernel in its own venv):
+# pip — the default (the line the 60-second demo ran; also how a host pins it):
 pip install dos-kernel            # core kernel (PyYAML only)
 pip install "dos-kernel[mcp]"     # + the MCP server (dos-mcp)
 
+# uv — the isolated CLI install (keeps `dos` + `dos-mcp` off your project venv):
+uv tool install dos-kernel        # `dos` + `dos-mcp` on PATH
+uvx --from dos-kernel dos doctor  # or run it once, ephemerally
+
 # from a clone — editable, the contributor path (tracking unreleased master:
 # pip install "dos-kernel @ git+https://github.com/anthony-chaudhary/dos-kernel", no clone needed):
 git clone https://github.com/anthony-chaudhary/dos-kernel.git && cd dos-kernel
@@ -709,10 +755,12 @@ pip install -e .                  # editable: your edits are live in the install
 > `[mcp]` extra adds the MCP framework; `[tui]` adds the live `dos top` screens).
 > See [SECURITY.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/SECURITY.md), "Supply chain."
 
-Prefer a package manager? **uv** is the 2026 default — faster than `pipx`,
-isolates the tool, and manages Python versions; `pipx install dos-kernel` works
-the same way if your team already uses it. Homebrew / WinGet / Scoop one-liners
-are next on the release runway (see [docs/INSTALL.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/INSTALL.md)).
+`pip install dos-kernel` is the whole install — if it worked in the demo,
+you're done here. The other rows exist for how *your* team works: **uv** if you
+want the CLI isolated from your project venv (faster than `pipx`, manages
+Python versions; `pipx install dos-kernel` works the same way), the clone if
+you're contributing. Homebrew / WinGet / Scoop one-liners are next on the
+release runway (see [docs/INSTALL.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/INSTALL.md)).
 
 A host repo adds DOS as a pinned dependency and points it at its own tree — never
 by vendoring the code in. DOS is stateless about which repo it serves: it
@@ -758,9 +806,9 @@ pip install "dos-kernel[mcp]"
 
 After installing, run **`/dos-kernel:dos-setup`** once — it confirms the package
 is importable, reports what the plugin wired, and points at the next skill. The
-same three hooks are available à la carte via `dos init --hooks claude-code`
-(and for Cursor / Codex / Gemini); the plugin is just the pre-packaged Claude
-Code form. The bundle's design + the build that keeps its skills in lockstep
+same three hooks are available à la carte via `dos init --hooks auto` (detects
+your runtime; or name one — claude-code, cursor, codex, gemini, antigravity,
+claude-cowork); the plugin is just the pre-packaged Claude Code form. The bundle's design + the build that keeps its skills in lockstep
 with the source are in **[claude-plugin/README.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/claude-plugin/README.md)**.
 
 ## CLI
@@ -978,12 +1026,17 @@ for a copy-me skeleton.
 ## Documentation
 
 - **[docs/QUICKSTART.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/QUICKSTART.md)** — runnable 5-minute hello-world. Start here.
+- **[docs/FAQ.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/FAQ.md)** — the arriving questions ("how do I
+  verify an agent's claim?", "does it need an LLM?"), each answered in one
+  self-contained block.
 - **[docs/README.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/README.md)** — the docs index (guides vs. design notes
   vs. the dated build-journal; the numbers are chronology, not a reading order).
 - **[docs/HACKING.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/HACKING.md)** — extend DOS without forking it.
 - **[CLAUDE.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/CLAUDE.md)** / **[CONTRIBUTING.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/CONTRIBUTING.md)** — the
   architecture contract and how to send a change.
 - **[docs/releases/](https://github.com/anthony-chaudhary/dos-kernel/tree/master/docs/releases)** — per-version release notes (the changelog).
+- **[The website](https://anthony-chaudhary.github.io/dos-kernel/)** — this page,
+  condensed to one screen (good for sending to someone).
 
 ## Playbooks & examples
 
@@ -1095,3 +1148,8 @@ preparation. Until the arXiv ID lands, cite the repository:
 ## License
 
 MIT — see [LICENSE](https://github.com/anthony-chaudhary/dos-kernel/blob/master/LICENSE).
+
+<!-- The marker below is the official MCP Registry's PyPI ownership proof: the
+     registry only accepts a server.json naming the `dos-kernel` PyPI package if
+     this exact token appears in the published package README. Keep it intact. -->
+<!-- mcp-name: io.github.anthony-chaudhary/dos-kernel -->

dos_kernel-0.23.4/PKG-INFO → dos_kernel-0.25.0/README.md

@@ -1,52 +1,3 @@
-Metadata-Version: 2.4
-Name: dos-kernel
-Version: 0.23.4
-Summary: Dispatch Operating System — the domain-free trust substrate for fleets of autonomous agents (verdict spine, ship oracle, structured refusal, lane arbiter, correlation spine).
-Author: Anthony Chaudhary
-License: MIT
-Project-URL: Homepage, https://github.com/anthony-chaudhary/dos-kernel
-Project-URL: Documentation, https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/QUICKSTART.md
-Project-URL: Repository, https://github.com/anthony-chaudhary/dos-kernel
-Project-URL: Issues, https://github.com/anthony-chaudhary/dos-kernel/issues
-Project-URL: Changelog, https://github.com/anthony-chaudhary/dos-kernel/tree/master/docs/releases
-Keywords: agents,ai-agents,llm,multi-agent,agent-orchestration,orchestration,dispatch,scheduler,oracle,leases,verification,trust,mcp
-Classifier: Development Status :: 4 - Beta
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Operating System :: OS Independent
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Topic :: Software Development :: Quality Assurance
-Classifier: Topic :: Software Development :: Version Control :: Git
-Classifier: Topic :: System :: Distributed Computing
-Classifier: Typing :: Typed
-Requires-Python: >=3.11
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: pyyaml>=6.0
-Provides-Extra: dev
-Requires-Dist: pytest>=8.0; extra == "dev"
-Requires-Dist: build>=1.0; extra == "dev"
-Requires-Dist: wheel>=0.43; extra == "dev"
-Requires-Dist: ruff>=0.13; extra == "dev"
-Requires-Dist: mypy>=1.17; extra == "dev"
-Requires-Dist: hypothesis>=6.100; extra == "dev"
-Provides-Extra: mcp
-Requires-Dist: mcp>=1.2; extra == "mcp"
-Provides-Extra: tui
-Requires-Dist: rich>=13; extra == "tui"
-Requires-Dist: windows-curses>=2.3; sys_platform == "win32" and extra == "tui"
-Provides-Extra: notify-slack
-Requires-Dist: slack-helpers>=0.2; extra == "notify-slack"
-Provides-Extra: export-otlp
-Requires-Dist: opentelemetry-sdk>=1.20; extra == "export-otlp"
-Requires-Dist: opentelemetry-exporter-otlp-proto-http>=1.20; extra == "export-otlp"
-Provides-Extra: paper
-Requires-Dist: arxiv-latex-cleaner>=1.0; extra == "paper"
-Dynamic: license-file
-
 <!-- GENERATED FILE — do not edit README.md directly.
      The source of truth is docs/readme/ (one file per section, assembled
      in filename order). Edit the part, then run:
@@ -96,7 +47,23 @@ zero config, and the only thing you ever install is one small Python package.
 > ⏱️ **Want to try it right now?** Jump to **[Try it in 60 seconds](#try-it-in-60-seconds)**
 > — one command, real output, then come back for the why.
 
-<sub>**v0.23.4** · 3900+ tests · CI: Python 3.11–3.13 on Linux + a Windows 3.13
+> ⚡ **Or just add it — two commands, zero decisions.** From the repo where your
+> agent works:
+>
+> ```bash
+> pip install dos-kernel
+> dos init --hooks auto   # finds the agent runtime(s) you already use, wires in the checks
+> ```
+>
+> From then on: your agent can't tell you **"done"** unless the work actually
+> landed, two agents can't silently overwrite each other's files, and a run
+> that stalls gets flagged instead of quietly spinning. Nothing about your
+> workflow changes, and you don't need to learn any of the vocabulary below to
+> be covered. It prints the one config file it wrote; deleting the `dos hook`
+> entries there undoes it. (No runtime detected? It says so and lists the
+> names to pick from — it never guesses.)
+
+<sub>**v0.25.0** · 3900+ tests · CI: Python 3.11–3.13 on Linux + a Windows 3.13
 smoke run · the only runtime dependency is **PyYAML** · **MIT**.</sub>
 
 > 🧭 **Want it in plain words first?** What DOS is, what it catches, and what
@@ -111,6 +78,13 @@ smoke run · the only runtime dependency is **PyYAML** · **MIT**.</sub>
 > your work, the ~5 files actually worth reading, and the architecture rules a
 > change must satisfy.
 
+> 🔤 **Five words the rest of this page leans on.** A **plan** is a named goal
+> (`AUTH`); a **phase** is one shippable step of it (`AUTH1`); a **lane** is the
+> slice of the file tree one agent may touch; the **oracle** is the part of DOS
+> that reads the evidence and rules; a **stamp** is the mark a shipped phase
+> leaves in a commit subject (`AUTH1: …`) — the thing the oracle greps for.
+> That's the whole vocabulary.
+
 <a id="who-this-is-for"></a>
 
 ## Who this is for
@@ -209,8 +183,8 @@ echo 'def login(): ...' > login.py
 git add -A
 git commit -m "AUTH1: ship the login endpoint"   # stamp AUTH1 shipped: <PHASE-ID>: <message>
 
-dos verify --workspace . AUTH AUTH1   # → SHIPPED     AUTH AUTH1 e389e8b (via grep-subject)   exit 0
-dos verify --workspace . AUTH AUTH2   # → NOT_SHIPPED  AUTH AUTH2          (via none)          exit 1
+dos verify --workspace . AUTH AUTH1   # → SHIPPED     AUTH AUTH1 <your-sha> (via grep-subject)  exit 0
+dos verify --workspace . AUTH AUTH2   # → NOT_SHIPPED  AUTH AUTH2            (via none)          exit 1
 ```
 
 An agent can claim `AUTH2` is done all day long; `verify` just reports what the
@@ -542,9 +516,11 @@ first (`dos_verify` "did it ship?", `dos_commit_audit` "does this commit's claim
 match its diff?", `dos_status` one folded fact about a run), then
 `dos_arbitrate` (may two workers run without colliding?), the structured-refusal
 pair (`dos_refuse_reasons` / `dos_check_reason`), `dos_recall` (is this recalled
-memory still true?), and `dos_doctor` (the workspace report) — so any
-MCP-speaking host — Claude Desktop, Cursor, Cline, Trae, an Agent-SDK app — can
-call the referee over JSON-on-stdio with zero Python coupling. Each verdict comes
+memory still true?), `dos_citation_resolve` (does this cited legal case exist in
+a third-party reporter? — the *Mata v. Avianca* witness), and `dos_doctor` (the
+workspace report) — so any
+MCP-speaking host — Claude Desktop, Claude Cowork, Cursor, Cline, Trae, an
+Agent-SDK app — can call the referee over JSON-on-stdio with zero Python coupling. Each verdict comes
 back with a one-line interpretation of what it means for the agent's next move.
 (See **[the MCP server surface](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/80_mcp-server-surface.md)**.)
 
@@ -566,22 +542,37 @@ DOS's hooks into the runtime you actually run. One command per host — it write
 that host's own hook-config file, merged into anything already there:
 
 ```bash
+dos init --hooks auto .          # don't know the names below? this detects the
+                                 # runtime(s) this repo already uses and wires them all
 dos init --hooks claude-code .   # .claude/settings.json
 dos init --hooks cursor .        # .cursor/hooks.json
 dos init --hooks codex .         # .codex/config.toml
 dos init --hooks gemini .        # .gemini/settings.json
 dos init --hooks antigravity .   # .agents/hooks.json
+dos init --hooks claude-cowork . # the SAME .claude/settings.json Claude Code reads
 ```
 
 That binds three shipped hooks: `pretool` denies a structurally-refused call
 before it runs, `stop` refuses a stop on an unverified "done," `posttool`
 re-surfaces a stalled stream. This is the **enforcement** path (the *host*
 denies on a DOS verdict) — the complement to MCP's advisory path. Until
-recently this spoke only Claude Code; it now installs across five hosts —
-Claude Code, Cursor, Codex, Gemini, and Antigravity
+recently this spoke only Claude Code; it now installs across six hosts —
+Claude Code, Cursor, Codex, Gemini, Antigravity, and Claude Cowork
 ([docs/221](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/221_the-cross-vendor-hook-installer.md),
-[docs/269](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/269_antigravity-the-fifth-host.md)).
-`--with-hooks` is the back-compat alias for `--hooks claude-code`.
+[docs/269](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/269_antigravity-the-fifth-host.md),
+[docs/298](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/298_claude-cowork-the-sixth-host-shared-surface.md)).
+`--with-hooks` is the back-compat alias for `--hooks claude-code`. `auto`
+([docs/303](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/303_hooks-auto-detection-plan.md))
+names the host *for* you: it probes which of those config dirs already exist in
+the repo — plus the shell's own environment, so a fresh repo opened inside
+Claude Code still detects — wires every runtime it finds (a shared config file
+is wired once), and fails loud with the list above when nothing is detectable,
+never guessing. Claude
+Cowork is the *shared-surface* host: it runs the same agent harness as Claude
+Code, so wiring either name binds both — one file, one set of hooks. (One
+honest caveat, carried on the install note itself: the Cowork app doesn't
+*fire* hooks yet — anthropics/claude-code#63360 — so until that closes,
+Cowork's working DOS surface is the advisory one above.)
 
 Under the installer sits a pluggable dialect seam: the verdict is decided
 once, then rendered into whatever JSON shape the host parses
@@ -593,12 +584,15 @@ reads (wire it in `cli-config.yaml`). A new host's dialect is a driver, never a
 kernel edit.
 
 The flip side of that honesty: a host with **no** hook seam gets **no** dialect.
-ByteDance's **Trae** was proved out and has no hook system at all (no lifecycle
-events, no deny/allow stdout contract), so DOS binds to it advisory-only — the
-MCP server in `.trae/mcp.json`, a verify-before-"done" rule in
-`.trae/rules/project_rules.md`, the generic skills in `.trae/skills/` — and
-`dos init --hooks trae` fails loud rather than writing config Trae would never
-read ([docs/294](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/294_trae-advisory-only-the-host-with-no-hook-seam.md)).
+ByteDance's **Trae** was proved out and ships no user-scriptable hook system in
+its personal/international editions (no lifecycle events, no deny/allow stdout
+contract; its CN-enterprise edition announced one on 2026-06-09 with no
+published grammar yet), so DOS binds to it advisory-only — the MCP server in
+`.trae/mcp.json` (read alike by IDE-mode Agent, SOLO mode, and TRAE CLI), a
+verify-before-"done" rule in `.trae/rules/project_rules.md`, the generic
+skills in `.trae/skills/` — and `dos init --hooks trae` fails loud rather than
+writing config Trae would never read
+([docs/294](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/294_trae-advisory-only-the-host-with-no-hook-seam.md)).
 An invented envelope would be fake enforcement, which is the exact failure the
 dialect seam exists to prevent.
 
@@ -688,14 +682,14 @@ channel, upgrade/uninstall, WSL, troubleshooting) is in
 **[docs/INSTALL.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/INSTALL.md)**:
 
 ```bash
-# uv — the modern, fast, isolated CLI install (recommended):
-uv tool install dos-kernel        # `dos` + `dos-mcp` on PATH
-uvx --from dos-kernel dos doctor  # or run it once, ephemerally
-
-# pip — the library-consumer path (a host pins dos-kernel in its own venv):
+# pip — the default (the line the 60-second demo ran; also how a host pins it):
 pip install dos-kernel            # core kernel (PyYAML only)
 pip install "dos-kernel[mcp]"     # + the MCP server (dos-mcp)
 
+# uv — the isolated CLI install (keeps `dos` + `dos-mcp` off your project venv):
+uv tool install dos-kernel        # `dos` + `dos-mcp` on PATH
+uvx --from dos-kernel dos doctor  # or run it once, ephemerally
+
 # from a clone — editable, the contributor path (tracking unreleased master:
 # pip install "dos-kernel @ git+https://github.com/anthony-chaudhary/dos-kernel", no clone needed):
 git clone https://github.com/anthony-chaudhary/dos-kernel.git && cd dos-kernel
@@ -709,10 +703,12 @@ pip install -e .                  # editable: your edits are live in the install
 > `[mcp]` extra adds the MCP framework; `[tui]` adds the live `dos top` screens).
 > See [SECURITY.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/SECURITY.md), "Supply chain."
 
-Prefer a package manager? **uv** is the 2026 default — faster than `pipx`,
-isolates the tool, and manages Python versions; `pipx install dos-kernel` works
-the same way if your team already uses it. Homebrew / WinGet / Scoop one-liners
-are next on the release runway (see [docs/INSTALL.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/INSTALL.md)).
+`pip install dos-kernel` is the whole install — if it worked in the demo,
+you're done here. The other rows exist for how *your* team works: **uv** if you
+want the CLI isolated from your project venv (faster than `pipx`, manages
+Python versions; `pipx install dos-kernel` works the same way), the clone if
+you're contributing. Homebrew / WinGet / Scoop one-liners are next on the
+release runway (see [docs/INSTALL.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/INSTALL.md)).
 
 A host repo adds DOS as a pinned dependency and points it at its own tree — never
 by vendoring the code in. DOS is stateless about which repo it serves: it
@@ -758,9 +754,9 @@ pip install "dos-kernel[mcp]"
 
 After installing, run **`/dos-kernel:dos-setup`** once — it confirms the package
 is importable, reports what the plugin wired, and points at the next skill. The
-same three hooks are available à la carte via `dos init --hooks claude-code`
-(and for Cursor / Codex / Gemini); the plugin is just the pre-packaged Claude
-Code form. The bundle's design + the build that keeps its skills in lockstep
+same three hooks are available à la carte via `dos init --hooks auto` (detects
+your runtime; or name one — claude-code, cursor, codex, gemini, antigravity,
+claude-cowork); the plugin is just the pre-packaged Claude Code form. The bundle's design + the build that keeps its skills in lockstep
 with the source are in **[claude-plugin/README.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/claude-plugin/README.md)**.
 
 ## CLI
@@ -978,12 +974,17 @@ for a copy-me skeleton.
 ## Documentation
 
 - **[docs/QUICKSTART.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/QUICKSTART.md)** — runnable 5-minute hello-world. Start here.
+- **[docs/FAQ.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/FAQ.md)** — the arriving questions ("how do I
+  verify an agent's claim?", "does it need an LLM?"), each answered in one
+  self-contained block.
 - **[docs/README.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/README.md)** — the docs index (guides vs. design notes
   vs. the dated build-journal; the numbers are chronology, not a reading order).
 - **[docs/HACKING.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/HACKING.md)** — extend DOS without forking it.
 - **[CLAUDE.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/CLAUDE.md)** / **[CONTRIBUTING.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/CONTRIBUTING.md)** — the
   architecture contract and how to send a change.
 - **[docs/releases/](https://github.com/anthony-chaudhary/dos-kernel/tree/master/docs/releases)** — per-version release notes (the changelog).
+- **[The website](https://anthony-chaudhary.github.io/dos-kernel/)** — this page,
+  condensed to one screen (good for sending to someone).
 
 ## Playbooks & examples
 
@@ -1095,3 +1096,8 @@ preparation. Until the arXiv ID lands, cite the repository:
 ## License
 
 MIT — see [LICENSE](https://github.com/anthony-chaudhary/dos-kernel/blob/master/LICENSE).
+
+<!-- The marker below is the official MCP Registry's PyPI ownership proof: the
+     registry only accepts a server.json naming the `dos-kernel` PyPI package if
+     this exact token appears in the published package README. Keep it intact. -->
+<!-- mcp-name: io.github.anthony-chaudhary/dos-kernel -->

{dos_kernel-0.23.4 → dos_kernel-0.25.0}/pyproject.toml

@@ -9,7 +9,7 @@ build-backend = "setuptools.build_meta"
 # src/), and the console scripts stay `dos` / `dos-mcp` — only the pip-install /
 # dependency-pin name is `dos-kernel`. See SECURITY.md "Supply chain".
 name = "dos-kernel"
-version = "0.23.4"
+version = "0.25.0"
 description = "Dispatch Operating System — the domain-free trust substrate for fleets of autonomous agents (verdict spine, ship oracle, structured refusal, lane arbiter, correlation spine)."
 # The PyPI project page renders this. Point it at the README so the page isn't
 # blank below the metadata (twine warns when it's missing). PyPI resolves
@@ -24,6 +24,11 @@ keywords = [
     "agents", "ai-agents", "llm", "multi-agent", "agent-orchestration",
     "orchestration", "dispatch", "scheduler", "oracle", "leases",
     "verification", "trust", "mcp",
+    # The arrival terms an agent or answer engine actually types (docs/299 P3).
+    # Honesty rule: every keyword must be true of the package — no aspirational
+    # or adjacent-product terms.
+    "claude", "claude-code", "mcp-server", "model-context-protocol",
+    "agent-verification", "autonomous-agents", "agent-monitoring",
 ]
 classifiers = [
     "Development Status :: 4 - Beta",
@@ -136,6 +141,12 @@ dos = "dos.cli:main"
 # launches. Requires the `mcp` extra (`pip install dos-kernel[mcp]`); the import
 # of `mcp.server.fastmcp` fails loudly with an install hint if the extra is absent.
 dos-mcp = "dos_mcp.server:main"
+# A dist-name alias for the SAME server, so the uvx convention works: `uvx
+# "dos-kernel[mcp]"` runs the script named after the package (and the MCP
+# Registry's `uvx --from "dos-kernel[mcp]==X.Y.Z" dos-kernel` launch composes to
+# a real command — see server.json). Without the [mcp] extra it fails loudly
+# with the same install hint as `dos-mcp`. The umbrella CLI stays `dos`.
+dos-kernel = "dos_mcp.server:main"
 
 # The shipped LLM judge — the reference occupant of the JUDGE rung (`dos.judges`,
 # Axis 6). Registered as a discoverable judge (NOT a built-in: only `abstain` is
@@ -182,6 +193,10 @@ codex = "dos.drivers.hook_dialects:CodexDialect"
 gemini = "dos.drivers.hook_dialects:GeminiDialect"
 cursor = "dos.drivers.hook_dialects:CursorDialect"
 antigravity = "dos.drivers.hook_dialects:AntigravityDialect"
+# Claude Cowork runs the Claude Code agent harness in a desktop VM, so its envelope
+# IS CC's — the renderer delegates (the Codex precedent), kept as a named entry so
+# `--dialect claude-cowork` resolves and a future divergence has a home (docs/298).
+claude-cowork = "dos.drivers.hook_dialects:ClaudeCoworkDialect"
 # Hermes Agent (Nous Research) — its `pre_tool_call` SHELL hook is a real
 # stdout-JSON deny surface (`{"decision":"block","reason":…}`), docs/278. (OpenClaw's
 # real hook is an in-process TS return, not stdout — no renderer consumer; SwarmClaw
@@ -276,10 +291,20 @@ codex = "dos.drivers.hook_dialects:codex_install_spec"
 gemini = "dos.drivers.hook_dialects:gemini_install_spec"
 cursor = "dos.drivers.hook_dialects:cursor_install_spec"
 antigravity = "dos.drivers.hook_dialects:antigravity_install_spec"
+# Claude Cowork — the SHARED surface: the same .claude/settings.json Claude Code
+# reads (same harness, same file; the wired command carries NO --dialect because the
+# shared file must serve both runtimes and the default IS the envelope). The spec's
+# note carries the one Cowork-specific fact: the product does not fire hooks yet
+# (anthropics/claude-code#63360, docs/298).
+claude-cowork = "dos.drivers.hook_dialects:claude_cowork_install_spec"
 
 [project.urls]
 Homepage = "https://github.com/anthony-chaudhary/dos-kernel"
+Website = "https://anthony-chaudhary.github.io/dos-kernel/"
 Documentation = "https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/QUICKSTART.md"
+FAQ = "https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/FAQ.md"
+# The agent-facing index (docs/299): the raw URL is the fetchable spelling.
+"llms.txt" = "https://raw.githubusercontent.com/anthony-chaudhary/dos-kernel/master/llms.txt"
 Repository = "https://github.com/anthony-chaudhary/dos-kernel"
 Issues = "https://github.com/anthony-chaudhary/dos-kernel/issues"
 Changelog = "https://github.com/anthony-chaudhary/dos-kernel/tree/master/docs/releases"

{dos_kernel-0.23.4 → dos_kernel-0.25.0}/src/dos/__init__.py

@@ -46,7 +46,7 @@ try:
 
     __version__ = _pkg_version("dos-kernel")
 except Exception:  # pragma: no cover - source-tree / not-installed fallback
-    __version__ = "0.23.4"
+    __version__ = "0.25.0"
 
 from dos import config  # noqa: F401  (re-export the seam as the package entry)
 from dos.config import (  # noqa: F401