Zeroshot v11.1.0

Changes since v11.0.0.

Features

Add an opt-out for automatic skill installation (#1350)

Add documented ZEROSHOT_SKIP_SKILLS=1 support for npm installation and
self-update while preserving default managed-skill protections. Isolate
updater tests from the exported setting.

Allow disabling workspace checkpoints (#1344)

Add workspaceCheckpoints to runtime plans, defaulting to enabled.
Local runs can set it to false to skip Restic setup, workspace
snapshots and snapshot cleanup while retaining durable run history,
outputs, logs and usage.

Normal restart preserves the saved policy and retained workspace.
Selected checkpoint restore is rejected before credential resolution
when snapshots were disabled. Named targets and contained hosting
explicitly reject the opt-out until they support it. Decision bindings
are excluded from workspace writers.

The setting works in exact and uniform runtime plans, saved profiles and
Python UniformRuntime. The SDK change also normalizes an existing type
union to satisfy its pinned Ruff check.

Add local script bindings (#1343)

Add a local script runtime binding to typed graph steps. The runtime
supplies an executable and literal arguments. Each invocation exchanges
bounded JSON over stdin and stdout, validates the result against the
step's output schema, and checks the serialized completion against the
existing ledger event limit. Invalid or oversized results follow the
graph's normal error handling.

The adapter reuses process containment, cancellation, declared
connections and credential redaction before diagnostic truncation. Agent
instructions remain required for agent bindings, while script steps omit
them. Scripts work inside existing maps and record execution timings and
zero native model tokens. Decision HTTP timing uses the same small
timing helper. Named targets and contained placements explicitly reject
this initial local binding.

Add the code-review built-in template (#1348)

Adds code-review, an alternative to pr-review that inspects code and
existing tests without installing dependencies or starting applications,
services or browsers. It shares the existing PR input, source pinning
and native comment delivery: --task-from <PR URL> or prepared {url, context, instructions?} input produces the same comment receipt.

Triage partitions the change into units. Four reviewers inspect each
unit beside five whole-change specialists; finalizers merge duplicates
and try to disprove findings before the report agent writes one comment.
Agent errors and map overflow stop publication; a crashed agent gets one
retry. Prompt fragments concatenate at compile time, and the report
budget leaves room for the publisher header. Models remain in the
runtime plan.

The supplied local runtime sets workspaceCheckpoints: false, skipping
workspace snapshots and Restic while retaining durable history, outputs,
usage, logs and comment receipts. Uniform runtimes can use the same
setting. Named targets currently reject opt-out, so hosted users enable
or omit the field as documented. This uses the checkpoint control from
main; it adds no template-specific runtime override.

Let hosts choose the author of delivered commits (#1359)

• Hosted runs can choose the author and committer of the commits
  delivery creates: TargetRunRequest.commitIdentity ({name, email}) on
  submission, and RunResumeParams.commitIdentity for a resumed
  successor.
• When present, it is used for every commit that attempt's delivery
  creates: prepared revisions, reconcile merges, target-integration
  merges, and the repository-local user.name/user.email set before
  conflict-repair handoff.
• When absent, delivery keeps Zeroshot <delivery@zeroshot.invalid>.
  Local CLI runs never set it, and local resume rejects one.
• CommitIdentity is valid by construction. It rejects values that are
  longer than 256 bytes, contain a control character, < or >, or that
  Git would trim to nothing. The target answers an invalid run request
  with 400 request.invalid before submission, and the JSON Schema states
  the same limits.
• Requests without the field serialize byte-for-byte as before.
  schema.json, openrpc.json and docs/reference/cluster/api.md were
  regenerated through the Rust testkit.
• NativeV2CandidateDelivery::new builds the forge authority from the
  delivery config, so one value feeds both workspace commits and the
  shared transport's merges. The identity travels only with per-run source
  credentials, never in run state or agent environments.

Let hosts save environment snapshots (#1367)

Let an embedded host save an environment through one generic snapshot
and acknowledge it with only its identity, name, definition, and
revision. Keep host-owned settings out of Zeroshot state while allowing
host dirty state to protect navigation.

The host contract contains no provider, credential, egress, deployment,
or other cloud behavior. Settings edits made while a save is in flight
remain dirty after the captured save is acknowledged.

Fixes

Reject unreadable store writes (#1333)

Reject writes that fail read-back so existing profiles stay usable; add
depth-61/62 regressions. Fixes #1332.

Include observed evidence in postmortem discovery (#1345)

Postmortem discovery missed review repairs in maps, nested loops, and
incomplete visits.
Collect observed agent completions and tool receipts across those
shapes, and let
specialists judge whether they support a useful lesson, including in
historical
initialization. Preserve node provenance,
current-source validation, scope, and bounded context; retain
representative citations
when long histories need trimming.

Condense the four specialist prompts by 44–57% while preserving their
authority and
publication contracts.

Isolate incompatible local entries (#1351)

Keep one incompatible local profile from blocking access to other saved
profiles. The CLI and standalone UI report individual metadata problems
while healthy profiles stay usable and affected entries remain removable
by name. This works independently of Platform updates.

Recover missing README summaries (#1366)

Recover missing release summaries for eight historical README commits so
release notes can be generated from immutable Git history again. Keep
recovery bound to their exact commit hashes and preserve explicit
summary precedence and strict validation for other commits.

Documentation

Lead with using zeroshot through your agent (#1334)

Rewrite the README around installing Zeroshot and using its graph-design, planning and run skills through a coding agent.

Add the blog link, the starred-by strip, the problem and where work goes (#1335)

Add the README blog link and starred-by banner, and explain local, branch, PR and merge delivery.

Read as a dev tool, not a team pitch (#1336)

Address individual developers in the README introduction and keep shared Platform workflows in a separate team section.

Open with why reviews must be independent and enforced (#1337)

Explain independent reviews in the README, including fresh reviewer sessions and enforced repair cycles.

Say the graph is customizable down to the model per step (#1338)

Clarify in the README that graphs customize workflow steps and select each step's tool and model.

Open with why single-agent sessions fail (#1339)

Explain why independent reviewers check single-agent work and return failed checks through the graph's repair loop.

Add the skills, an architecture diagram and a command reference (#1340)

Document the four installed skills, add an architecture diagram, and list common CLI commands in the README.

Use a compact architecture diagram (#1341)

Replace the README's boxed architecture diagram with a compact flow through admission, execution, adapters, durable state and delivery.

Make quickstart commands portable across shells (#1342)

Make the quickstart's validation and run commands copyable in Bash,
PowerShell, and Command Prompt. Clarify native CLI setup, choosing a
task that fits the project, and what validation checks.

Show the site's example graph as an animation (#1346)

The README now shows zeroshot.sh's example graph from issue to merge as
a looping animation. It sits under "Get started", right after the
paragraph on where finished work goes, and links to the drawing on
zeroshot.sh. The page's headline is left out. The README's opening graph
stays a text block, so agents reading it as plain text can still read
it.

• Light and dark versions, and the page's tall layout below 641px
  viewport width.
• Readers who turn motion off get the page's reduced-motion still.
• The GIFs are 1,590 frames at 50 fps (the page's 31.8-second run),
  rendered at 2x: 1760px wide (about 1.1 MB) and 800px tall (about 0.9
  MB).

docs/brand/freeze-example-graph.py freezes the drawing from a
zeroshot-landing-page checkout (846a4bd) with its run unchanged.
docs/brand/render-example-graph.cjs pauses the CSS animations and
seeks every frame. docs/brand/README.md documents both.

Position zeroshot as a software production engine (#1347)

Position zeroshot as an open-source engine for autonomous software
production. The README now leads with the team's executable development
and QA process, explains CI starting at the issue, and presents the
review loop as one configurable graph. A concrete CSV-export example
shows rejection, repair, and delivery, with completion scoped to
required approvals and configured bounds.

Present zeroshot as an agent workflow framework (#1353)

Present zeroshot as a framework for building agent workflows, with an
opening that speaks directly to individual developers. Keep the existing
custom graph example and add a CLI walkthrough to export a template,
customize it, validate the configuration, and run it locally, with links
to per-node models and reusable profiles.

Introduce autonomous software production across product surfaces (#1352)

Lead docs, npm and Python SDK introductions with zeroshot as the engine
for autonomous software production. Keep workflow engine, coding agents,
multi-agent graphs, code review, testing, repair and QA automation in
supporting copy and package keywords.

Update the docs contract to verify discoverable descriptions and avoid
reducing the engine to its default graph without freezing a marketing
slogan into a test. Registry metadata ships with the next package
release; this PR does not publish a new engine version.

Clarify multi-agent framework wording (#1354)

Describe zeroshot as a multi-agent framework and lead with defining the
graph topology. Go straight to the security-review graph example, and
remove the repeated claim about model output adding edges or raising
bounds.

Trim README to framework example and quick start (#1356)

Shorten the README from 311 to 117 lines around the multi-agent
framework, custom graph example, and quick start. Replace repeated
workflow explanations, diagrams, CLI instructions, and hosting setup
with links to the existing guides. Keep the direct graph export command,
user quotes, delivery default, and contributor links. Update the Docker
documentation test to require the README's guide link while retaining
the guide's volume check.

Lead README with independent adversarial review (#1358)

Lead the README with the limits of single-agent workflows and the value
of independent, adversarial review cycles. Place the approved
explanation before the custom graph example and remove repeated
review-context wording below it.

Make README explanations more direct (#1361)

Use the revised single-agent and independent-review explanation in the
README opening. Make the graph example, reusable profiles, and setup
instructions more direct while keeping the existing commands and links.

Sharpen README tagline and remove star graphic (#1362)

Replace the README tagline with “Independent, adversarial review with
mechanically enforced execution.” Remove the “Starred by” graphic and
its spacer so the opening argument follows the header directly.

Illustrate the full development graph with boxed nodes (#1363)

Replace the README security-review example with the first workflow from
zeroshot.sh: goal, worker, parallel acceptance and code reviews,
end-to-end test, PR, CI, and merge. Use static boxed ASCII inspired by
the January README, with explicit rejection and failure paths through
repair back to implementation.

Identify the framework in the README tagline (#1364)

Use “A multi-agent orchestration framework for autonomous software
development.” as the README tagline. The opening paragraphs and graph
explain the review mechanism below it.

Compact the README delivery graph (#1365)

Reduce the README graph from 33 to 25 lines by placing PR, CI, and merge
on one horizontal row. Preserve plain-text boxed nodes, parallel
reviews, and every repair path so people and agents can still read the
workflow directly.

Maintenance

Add a lightweight path for README-only changes (#1357)

Root-README-only changes now run formatting, local link/image checks,
and documentation contracts instead of Rust protocol generation,
distribution checks, and the full source scan. CI and Opcore use the
same history selector; mixed changes retain their existing lanes, while
missing history, unknown paths, and manual dispatches select full
checks.

The README lane participates in the required aggregate, so missing,
skipped, or failed selected checks block merging. It retains the
existing self-hosting-guide requirement and checks inline,
reference-style, and HTML links/images. Existing PR policy and Greptile
gates remain in place.

Upgrade

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