Zeroshot v10.25.0

Changes since v10.24.1.

Features

Add Microsoft Foundry provider for Codex and Claude (#1328)

Codex and Claude runtimes can now use provider: "foundry" to reach
models deployed in a Microsoft Foundry resource. One foundry
connection carries AZURE_FOUNDRY_API_KEY with either
AZURE_FOUNDRY_RESOURCE or AZURE_FOUNDRY_BASE_URL, so a run that
mixes Codex and Claude nodes on the same resource needs one stored
connection. The model is the Foundry deployment name.

Expose node execution metadata (#1329)

Expose seven public ZEROSHOT_* execution labels across all six harness
adapters, including reducer attempts and the innermost loop iteration.
Preserve labels through corrections, replay, capsule requests and
auxiliary launches, with documented inheritance rules.

Closes #1326.

Add per-node native harness configuration (#1330)

Add per-node native harness configuration across all six adapters,
including Claude verifier tool selection. Preserve overrides through
profiles, corrections and session reuse while protecting runtime-owned
controls and plugins.

Documentation

Lead with the team's own graph (#1323)

The README now leads with the team's own graph instead of the built-in
review loop.

• "Build your own graph" moves up under the intro. It shows an example
  team graph as text, a prompt for the zeroshot-graph-design skill to
  design a graph for your repo, and how to export the built-in graph, edit
  it and run it with --graph.
• The intro is shorter: your team's QA process as a graph, enforced by
  the engine, saved as a profile so everyone runs the same process.
• The animated example graph is no longer at the top of the README; its
  exports stay in docs/assets.
• The banners carry the README headline and a "graphs are enforced" note
  instead of the old tagline and the fixed write → review → deliver loop.
  The mobile banner is now rendered from HTML like the desktop ones.

The text graph is 34 characters wide so it fits a 360px phone without
horizontal scrolling, and stays readable for agents that fetch the
README as plain text.

Replace the banner with a plain header (#1324)

The README opens with a plain header instead of a banner.

• The banner is gone. It repeated the text under it and filled a phone's
  first screen. Its sources stay in docs/brand.
• The header is the title and one line: "Write your QA process down as a
  graph. zeroshot makes every agent run follow it."
• Only the Discord and zeroshot.sh buttons remain. The Discord button
  now reads "Talk to the team and power users on Discord".
• The README asks for Discord feedback where people get stuck: after the
  first run and after "Build your own graph".

Show an example team graph and the graph-design skill (#1325)

The agent guide (docs/llms.txt) now sells building your own graph, not
just the built-in one.

• "Make it yours" becomes "Build your own graph" and moves up under the
  summary. It shows an example team graph as text, the same one as the
  README.
• Its first step is the zeroshot-graph-design skill, installed with
  the CLI, which drafts a graph from the repository's build, test and CI
  setup. Exporting the built-in graph and running it with --graph stays
  as the second option.
• The "Independent review" bullet no longer describes only the built-in
  graph.
• The installer paragraph lists all four installed skills.
• A failed setup or run points to https://theopenengine.com/discord.

Upgrade

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