Skip to content

v1.9.0

Choose a tag to compare

@alsevilla alsevilla released this 19 Oct 12:34
efe2773

v1.9.0

  • Correct model provenance across foreground, background, monitor and retained handoffs: keep requested identity separate from child-reported route/request and response model. Preserve unknown completed messages and earlier-attempt uncertainty; include only actually launched children in fallback attempt history.
  • Add opt-in Pi modelSlot: "fallback" with explicit modelTier, using the first usable configured fallback in the same tier without replaying back to its primary.
  • Strengthen content-fingerprint and independent-review guidance and routing regression fixtures.
  • Remove the external compaction integration while preserving Pi's normal compaction behavior.
  • Align Pi package and Copilot CLI preview source versions to 1.9.0.

Verification and scope

Independent verification passed and review approved the exact integrated candidate, closing all three provenance findings. Reused byte-matched worker results: Bun 676 passed / 4 skipped, Python 105 passed and configuration scan zero errors. Independent focused verification and review passed; release smoke added 16 Copilot packaging/bootstrap tests and Pi manifest/export checks. Merged tree is identical to the checked PR head; source archive integrity, versions and contents passed.

Child-reported identity is not provider attestation. Absent responseModel remains served UNVERIFIED; an unknown marker means at least one unknown message, not its count. No upstream-provider inference, live provider independence, token savings, Linux/macOS or Windows/Linux runtime parity is claimed. Existing platform/ACL/symlink skips and Copilot preview limitations remain.

Distribution and activation

Source-only GitHub release, following v1.8.0: no uploaded binary/package assets and no npm publication. GitHub supplies its normal source archives. Pi uses the repository's native package; Copilot remains a separately installed limited preview. No install, deployment or live configuration change was performed.

Reload/restart Pi at a safe point after active workers finish to activate the updated extension schema and behavior. No automatic reload. No database migration or new configuration requirement; recovery is selecting the prior source release/reverting the scoped change, not moving this release tag.

Source: squash-merged PR #8, commit efe2773.