Skip to content

mypi v0.7.0

Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 22 Oct 19:43
· 804 commits to main since this release
7808643

mypi v0.7.0

Prerelease; not a production-readiness claim. Implements MP-29 via PR #41; release metadata via PR #42.

Work chats

  • Unified explicit opening through CLI work-chat open-request, MCP work_chat_open_request and Pi /work-chat open-request.
  • Pi owns native history/model/auth; Herdr owns native launch and terminals; mypi keeps request/worktree/session associations and cooperative reservation.
  • Exact saved-session continuation without automatic work prompts or silent history replacement.
  • Read-only inspection, preparation before reservation, stale-result/CAS protection and conservative handling of uncertain external actions.
  • Removed duplicated auth/readiness/adoption/ack/launch-commit/watch protocol.
  • Correct Herdr exit-only versus JSON response handling, explicit shell resource-root propagation and slash CLI process-group separation.

Verification

Mandatory local and installed-layout verification: 66 fast + 30 boundary tests. Independent code/test reviews and real Pi/Herdr evidence review accepted the documented scope. Real CLI/MCP, save/exact-resume/recall, no-auth, conflict and simulated-legacy scenarios were exercised on the reviewed preceding candidate; the final scope-limited slash change has its own real same-writer/process-overlap acceptance. Earlier failed evidence and its corrected classification were preserved, not relabeled.

Final release/main CI: https://github.com/yokeloop/mypi/actions/runs/39842305235 — SUCCESS on 7808643.

Upgrade

SQLite schema 4 → 5 requires explicit migration (mypi db init). Back up the database first. Existing rows/legacy fields/indexes/relationships are preserved; new process boot ID and Herdr endpoint are nullable for legacy rows. A reserved native session ID may precede discovery of its actual history path.

Rebuild/update the installation, migrate only with authorization, then reload/reconnect old Pi/MCP clients. Old clients may reject the new schema. No automatic migration on ordinary reads and no reset/bootstrap required.

Limits

Linux direct Pi executable and stock Herdr integration are required. Opening is not an OS/credential sandbox, global native-history writer lock or exactly-once transaction. Unsaved native references are not resumability guarantees. Explicit no-auth model evidence is argv/UI only, not successful provider readiness. Process-group cleanup does not promise to catch escaped descendants or undo completed server-side effects. Shared-server/reboot/network faults and real child-agent execution were not live-tested.

Private package; no npm publication. Existing context, histories and worktrees must be preserved during upgrade.