Zeroshot v10.22.0

Changes since v10.21.0.

Features

Isolate adapters and add contributed harnesses (#1316)

Local builds now include contributed OpenCode and Hermes adapters with
the same execution, session, permission and Active Memory contracts as
maintained harnesses. Platform and default target images retain the
core-only registry.

One adapter registry owns descriptors, provider requirements, executable
lookup and factories. Maintained and contributed implementations live in
dedicated folders, own their native environment/path policy, and
preserve existing public module paths. Targets advertise enabled
harness/provider pairs through a separate discovery extension.

Both contributed adapters support the six existing provider families.
Native configuration, plugins, MCP, authentication and refresh remain
native; declared credentials retain precedence. Copilot gains native
BYOK provider lanes and Pi gains GitHub support. The harness guide
documents availability and contribution requirements, with short
references elsewhere.

The branch includes current main, preserving host context, caller
token-limit semantics, decision bindings, forge support and Copilot
grammar retries. Focused regressions cover fresh host context on
contributed session revisits and BYOK credentials surviving a native
grammar retry.

Fixes

Honor local Git configuration (#1315)

Local delivery honors the invoking user's effective Git configuration, including global core.autocrlf, repository overrides, and attributes. A one-line edit in a CRLF checkout is normalized by the caller's policy when staged. Staging, commits, and the shared forge reconciliation paths use the same private caller context; hosted execution retains its isolation.

Git protocol stdout is parsed before credential redaction, so collisions with credentials cannot corrupt revisions or paths. Printable diagnostics remain redacted.

Fixes #1301.

Upgrade

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