Zeroshot v10.18.0

Changes since v10.17.0.

Features

Rebrand Zeroshot Cloud as Zeroshot Platform (#1289)

Rename Zeroshot Cloud to Zeroshot Platform across CLI help, Rust modules
and public source names, the embedded editor, SDK examples,
documentation and installed product skills.

Fresh registries receive the built-in platform target. Existing
cloud target records keep their saved identity and remain usable.
Users choosing the new name sign in with zeroshot target login platform and use --target platform. Hosted workspaces use kind: "platform", which starts fresh browser drafts and preferences without a
state-migration layer.

Review/comment delivery uses the Platform source names and target
examples. Historical delivery identities remain unchanged through
workspace restore and comment publication. Server-side identifiers,
opaque workspace IDs and service/API origins retain their stored values.

Documentation

Add user quotes, results and the Cloud issue command (#1292)

Moves what zeroshot.sh showed before the 2026-10-23 rebuild into the
README:

• One line on why a graph instead of a prompt: "A skill can ask for a
  review, but the agent decides whether to listen."
• Three more results next to ProgramBench: the design slop reviewer test
  (ten screens sent back, five accepted, eight with the standards in the
  prompt), the 21× auto-research run, and the flight game before/after.
  Each links to its demo on zeroshot.sh.
• A "What users say" section with four quotes from the old landing page
  (Mark Dingwall, Daniel Graungaard, Andrey, Fav).
• The Cloud issue command: comment @zeroshot-cloud run on a GitHub
  issue, linked to the Cloud docs page.

Left out on purpose: "we don't review the code" (an outcome promise),
the old $100 pricing (no longer stated anywhere), and team bios.

Checks run locally: Prettier, npm run lint, npm test (67 pass),
cargo fmt --check.

🤖 Generated with Claude Code

Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Add the key to the feature graph and render it at 50 fps (#1294)

• The README's feature graph now matches zeroshot.sh: it includes the
  key (writes, judges, built in, boots the stack) and the larger "all yes"
  and repair labels. The frozen desktop source dated from 2026-10-19,
  before the page added them; the animation keyframes are unchanged.
• Both GIFs render at 50 fps (800 frames, 20 ms each) instead of 15 fps,
  which made the animation stutter. Sizes: desktop 152 KB → 338 KB, mobile
  → 366 KB.
• The reduced-motion desktop PNG is re-exported with the key. The mobile
  layout has no key on the page, so its source and PNG are unchanged.

Rendered with docs/brand/render-product-graphs.cjs from the checked-in
sources. Checked frame timing (800 × 20 ms, 16 s loop), the key, flow
dots, and pass/fail marks in sample frames.

🤖 Generated with Claude Code

Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Tone down the intro and drop the Cloud issue command (#1293)

• The ProgramBench line now says "a small model in a zeroshot loop".
• The "Results so far" list is replaced by one line linking the flight
  game, landing page and research demos on zeroshot.sh.
• Removes the security reviewer example paragraph from the intro.
• Removes the @zeroshot-cloud run issue command added in #1292; the
  Cloud section is back to its one-line setup pointer.

Checks run locally: Prettier, npm test (67 pass).

🤖 Generated with Claude Code

Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Make agent-facing docs runnable and lead with the team's own enforced QA process (#1295)

• Zeroshot's agent guide (docs/llms.txt), the docs home and site
  description, the npm and PyPI descriptions and READMEs, and zeroshot --help now lead with what Zeroshot is for: a team defines its own QA
  process as a graph, the engine enforces it, and every engineer's tasks
  run through one process. The guide adds "Why teams use it" and "Make it
  yours" sections.
• docs/llms.txt and the execution concepts page said software-change
  keeps changes local by default. It opens a pull request. The guide's
  quick start now passes --delivery none like the README, says a valid
  request prints {"valid":true}, and names the harness/provider pairs
  for Claude Code, GitHub Copilot and Pi.
• The first-run guide shows a runtime.json for every harness.

Add page metadata and self-host documentation fonts (#1300)

Give every documentation page its own search description and social
metadata, add breadcrumb structured data, and serve the existing fonts
locally. Preserve the versioned canonical URL policy and point the docs
footer at the active company X account.

Generated reference descriptions are supplied by the publication hook.
Pricing and product behavior are unchanged.

Upgrade

npm install -g @the-open-engine-company/zeroshot@10.18.0