TokenPak v1.5.2 — MultiPak Pro Phase 0 + Phase 1 OSS surface
Batched PATCH release covering both Phase 0 (TIP capability constants + Pak/ContextPackage data contracts) and Phase 1 (OSS surface — adapter, journal, CLI, proxy stubs).
What's new
Phase 0 — TIP capability + data contracts (PR #101 + companion registry PR #4)
- 10 new TIP capability constants under
tokenpak.tip.capabilities:tip.pak.{capture,index,recall,hydrate,promote}+tip.context.{package,handoff,resume,coverage,policy}. Pak+ContextPackagefrozen dataclasses with full JSON round-trip intokenpak.tip.pakandtokenpak.tip.context_package.- Companion
tokenpak/registry0.2.0 release: capability-catalog entries + JSON Schemas (pak-v1,context-package-v1). - 54 contract tests.
Phase 1 — OSS surface (PR #102)
tokenpak/vault/pak_adapter.py— read-only adapter wrappingVaultIndex.searchto producePakinstances withPakSubtype.VAULT.tokenpak/companion/journal/pak_aware.py— opt-in promotion-candidate marker. Auto-capture unchanged per internal policy.tokenpak pak {inspect,export,import,status}CLI subcommand with--jsonfor machine output./pak/v1/{status,inspect/<pak-id>,recall}proxy routes. Standardized 501 envelope for Pro-gated endpoints.tokenpak/licensing/daemon_probe.py— fast-path-safe presence check reading~/.tokenpak/pro/daemon.sock-infoper internal policy.pro.multipak.enabledconfig key (defaultsfalseuntil 1-week soak per internal policy).- 100 surface tests.
Pure additive
No breaking changes, no removed fields, no renamed canonical types. Existing flows unaffected.
Pro daemon work — gated
tokenpak-paid daemon code (capture pipeline, recall ranking, Handoff Paks, anchor hydration, encrypted Pak store) remains gated by internal policy.
Release-batching note
Two-step v1.5.2 → v1.5.3 was originally intended (Phase 0 → Phase 1 PATCH separation). PR #102 merged immediately after PR #101 + the registry companion PR landed, before a release-bump window opened. The two phases ship together as a single batched PATCH per the release-protocol allowance documented in the TokenPak release protocol.