ShipGuard 2.17.0

Changes since 2.16.1,
covering main through 70f0a58937d81434dcd98edffa6501c5f1e9ee90.
This minor version includes new recording/replay and tool-copy capabilities alongside fixes.

Added

• Record and replay native browser back/forward actions, including the recorder toolbar controls;
  distinguish manual history navigation from navigation triggered by recorded page actions (#138).
• Detect stale project copies of ShipGuard tools and support explicit refresh with rollback;
  preserve copy permissions during refresh and rollback (#115).
• Prepare complex or unfamiliar tasks conditionally in mission-lock and grill-goal: reuse prior
  preparation, consider relevant methods, data and authorized tools, and choose evidence that can
  expose an insufficient result. Simple tasks remain direct (72755d2).

Fixed

• Audit evidence: reject inconsistent verifier results, bound source reads, retain ignored zone
  artifacts before completion, and reject foreign run events in the monitor (#120, #113, #138).
• E2E assertions: reject incomplete agent evidence rather than treating it as verified (#99).
• CLI: avoid duplicate findings for linked HTTP errors; preserve execution, capture, lifecycle and
  exit outcomes, including native back/forward replay (#117, #138).
• Recorder: expose integration-generator errors; preserve absolute URLs outside the configured
  base, body clicks that dismiss content, captured actions, document navigation and replay scope;
  avoid duplicating history traversal caused by recorded page actions (#114, #122, #121, #138).
• Review dashboard: distinguish static audit results from runtime verification, show exact run
  evidence, and clear completed review intent (#124, #138).
• Dialogue checks: keep equality unverified when question evidence is truncated (#106).
• Model scope probes: require an explicit user request; never select them implicitly (#116).
• Correct the prompt-audit documentation's stated behavior and limits (#91).

Distribution

• Claude Code and Codex plugin manifests now identify this content as 2.17.0. Both marketplace
  catalogs continue to resolve ./plugins/shipguard, where those manifests carry the version;
  neither catalog has a separate version field. There is no npm package or package manifest.
• This release preparation changes only version metadata and documentation. It does not install
  or update plugins on machines, change hook trust, or reload running sessions.