Zeroshot v10.17.0

Changes since v10.16.0.

Features

Add active memory for local and Docker runs (#1288)

Active Memory is enabled by default for local and direct Docker runs. It
recalls concise lessons from costly repository mistakes and recurring
graph procedures through deterministic hooks and instruction guidance,
using the run's configured model provider for postmortem work.

A resumable zeroshot memory init --directory DIR command and the
zeroshot-memory-init skill initialize memory from local run history,
with repository/graph exclusions and final reconciliation against
current checkouts.

Post issue and PR review reports to GitHub (#1291)

Add native comment delivery and pre-start issue/PR URL intake.
Publication records durable intent before posting and returns a
confirmed receipt; retries and workspace recovery reuse the original
comment without blind reposts. Custom graphs can use the same publisher.

Add separate issue-review and pr-review graphs. PR review
conditionally reproduces behavior through the full local stack,
including browser checks for UI, then checks lean implementation and
linked-issue coverage. Its concise comment preserves reproduction and
setup evidence. The supplied runtime assigns all three agents
gpt-6.1-sol at xhigh. Review templates default to comments;
software-change defaults to PR delivery. GitHub is the maintained forge.

Fixes

Name the checkout behind an unresolved Git worktree link (#1287)

A local run in a repository with a broken Git worktree link stopped at
its first workspace checkpoint, before any node started, with only:

Runtime failed: workspace checkpoint is unavailable: No such file or directory (os error 2)

Git still accepts these repositories, and ordinary commands produce
them. Moving a checkout that contains a nested linked worktree (for
example .claude/worktrees/<name>) leaves that worktree's .git file
naming a missing administrative directory. Moving a linked worktree with
mv leaves its administrative backpointer naming the old location; the
moved worktree can be nested in the workspace or be the workspace
itself. The error named neither the checkout nor the fix, so the only
way out was trial-and-error worktree cleanup.

Checkpoint Git discovery now names the checkout it refuses, and a broken
worktree link names Git's repair:

Runtime failed: workspace checkpoint is unavailable: Git checkout ".claude/worktrees/review": unresolved Git worktree link: No such file or directory (os error 2); run `git worktree repair` with this checkout's path from its main worktree, or remove the stale checkout (log v2:3)

Keep the graph zoom when expanding or collapsing groups (#1282)

Expanding or collapsing a workflow group preserves its screen position
and zoom. Clicking Fit while a group is laying out fits the completed
graph from its rendered positions and sizes, so stale React Flow
measurements cannot clip the expanded group.

Fixes #1281

Retain postmortem evidence and reconcile stable lessons (#1290)

Active Memory could lose the worker's costly exploration when a long run
filled its evidence budget with the last reviewer's transcript.
Postmortems now read bounded history pages and retain evidence fairly
across executions, with cooperative cancellation and diagnostics that
identify rejected admission gates without logging proposal contents.

Maintenance now removes unstable source locations and lets the host bind
each decision to the supplied lesson revision. This prevents stale
line-number guidance and model-generated revision errors while
preserving complete reconciliation and compare-and-swap protection.

Maintenance

Use five roles with persistent sessions (#1286)

Replace the built-in autoresearch workflow with the five-role loop
tested in the Luna campaign: three independent scouts propose
directions, one researcher owns the round, and one fresh reviewer checks
the retained result. A normal round uses five model executions.

• Keep separate continuing sessions for the scouts and researcher by
  default, with fresh review on every pass. Explicit runtime scopes remain
  caller-owned.
• Route requested corrections directly to the same researcher without
  repeating scouting or spending another research iteration. Carry the
  native review verdict beside feedback so advisory warnings cannot be
  mistaken for a revision. Treat minor optional archive and bookkeeping
  issues as advisory while preserving correctness, evidence and
  protected-file requirements.
• Retain archive-based exploration, reconsideration after non-adoptions
  or diminishing returns, configurable iteration counts, and reviewed
  per-round push delivery. Use one workspace-root research ledger for
  subdirectory tasks.
• Remove bootstrap, staging, multi-judge finalization, separate audit
  and delivery-manifest model passes. Saved profiles and admitted runs
  retain their stored definitions.

Upgrade

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