Our vendored Worldtree Conversation API spec pin is at v0.19.0 (commit 55101e909abcd2219833266b6f905c5bc956e0f0). Worldtree shipped v0.20.0, v0.21.0, and v0.22.x since (current is v0.22.1) per worldtree-dev's 2026-05-23 reply (althing thread 01KSBARG2B8M8C82H6AJGJWX1B).
What changed between v0.19.0 and v0.22.1 (consumer-relevant)
v0.20.0 (#185): end_user_id became the partition key for long-term memory + persona/valence state.
v0.21.0 (#189): Phase 2.1 added optional memory_context: list[dict] field to POST /sessions/{id}/messages; appended to per-turn system prompt as [MEMORY:DATA ...] blocks.
v0.22.0 (#197): ContextPromotion + STM tier removal; the [MEMORY:DATA] envelope was strengthened.
v0.22.1: current head (point-fix on top of v0.22.0).
None of these break ratatoskr's existing surface — POST /sessions, POST /sessions/{id}/messages SSE, and POST /sessions/.../turns/{tid}/cancel are stable.
What's needed
Re-vendor docs/conversation-api-spec.md from ~/development/Worldtree/docs/conversation-api-spec.md at the v0.22.1 SHA.
Update docs/SPEC-PIN.md (and any pyproject.toml-pinned reference) to the new SHA + version label.
Audit contract texts that reference the old pin — update version string + SHA in all assumptions: blocks.
Decide whether to opt into memory_context (Phase 2.1) — separate follow-up.
Out of scope
Pre-implementing the subject:{type,id} migration (Worldtree #196) — separate ratatoskr issue.
Adopting memory_context — separate follow-up if we want it.
Why now
The pin lies about what surface we're committed to. Worldtree-dev flagged the delta on 2026-05-23.
## Context
Our vendored Worldtree Conversation API spec pin is at v0.19.0 (commit `55101e909abcd2219833266b6f905c5bc956e0f0`). Worldtree shipped v0.20.0, v0.21.0, and v0.22.x since (current is v0.22.1) per worldtree-dev's 2026-05-23 reply (althing thread `01KSBARG2B8M8C82H6AJGJWX1B`).
## What changed between v0.19.0 and v0.22.1 (consumer-relevant)
- **v0.20.0** (#185): `end_user_id` became the partition key for long-term memory + persona/valence state.
- **v0.21.0** (#189): Phase 2.1 added optional `memory_context: list[dict]` field to `POST /sessions/{id}/messages`; appended to per-turn system prompt as `[MEMORY:DATA ...]` blocks.
- **v0.22.0** (#197): ContextPromotion + STM tier removal; the `[MEMORY:DATA]` envelope was strengthened.
- **v0.22.1**: current head (point-fix on top of v0.22.0).
None of these break ratatoskr's existing surface — `POST /sessions`, `POST /sessions/{id}/messages` SSE, and `POST /sessions/.../turns/{tid}/cancel` are stable.
## What's needed
1. Re-vendor `docs/conversation-api-spec.md` from `~/development/Worldtree/docs/conversation-api-spec.md` at the v0.22.1 SHA.
2. Update `docs/SPEC-PIN.md` (and any `pyproject.toml`-pinned reference) to the new SHA + version label.
3. Audit contract texts that reference the old pin — update version string + SHA in all `assumptions:` blocks.
4. Decide whether to opt into `memory_context` (Phase 2.1) — separate follow-up.
## Out of scope
- Pre-implementing the `subject:{type,id}` migration (Worldtree #196) — separate ratatoskr issue.
- Adopting `memory_context` — separate follow-up if we want it.
## Why now
The pin lies about what surface we're committed to. Worldtree-dev flagged the delta on 2026-05-23.
Closed — superseded. Target was v0.19.0 → v0.22.1; the spec pin has since advanced to v0.29.0 (commit 562001a, pinned 2026-05-26) via the v0.11.0/v0.13.0/v0.14.0 integration arcs. The v0.22.1 intermediate refresh is moot — we're seven minors past it and all consumer surfaces (POST /sessions, messages SSE, cancel) remain stable. memory_context (Phase 2.1) opt-in remains a separate untracked follow-up if ever wanted.
Closed — superseded. Target was v0.19.0 → v0.22.1; the spec pin has since advanced to v0.29.0 (commit 562001a, pinned 2026-05-26) via the v0.11.0/v0.13.0/v0.14.0 integration arcs. The v0.22.1 intermediate refresh is moot — we're seven minors past it and all consumer surfaces (POST /sessions, messages SSE, cancel) remain stable. memory_context (Phase 2.1) opt-in remains a separate untracked follow-up if ever wanted.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
Our vendored Worldtree Conversation API spec pin is at v0.19.0 (commit
55101e909abcd2219833266b6f905c5bc956e0f0). Worldtree shipped v0.20.0, v0.21.0, and v0.22.x since (current is v0.22.1) per worldtree-dev's 2026-05-23 reply (althing thread01KSBARG2B8M8C82H6AJGJWX1B).What changed between v0.19.0 and v0.22.1 (consumer-relevant)
end_user_idbecame the partition key for long-term memory + persona/valence state.memory_context: list[dict]field toPOST /sessions/{id}/messages; appended to per-turn system prompt as[MEMORY:DATA ...]blocks.[MEMORY:DATA]envelope was strengthened.None of these break ratatoskr's existing surface —
POST /sessions,POST /sessions/{id}/messagesSSE, andPOST /sessions/.../turns/{tid}/cancelare stable.What's needed
docs/conversation-api-spec.mdfrom~/development/Worldtree/docs/conversation-api-spec.mdat the v0.22.1 SHA.docs/SPEC-PIN.md(and anypyproject.toml-pinned reference) to the new SHA + version label.assumptions:blocks.memory_context(Phase 2.1) — separate follow-up.Out of scope
subject:{type,id}migration (Worldtree #196) — separate ratatoskr issue.memory_context— separate follow-up if we want it.Why now
The pin lies about what surface we're committed to. Worldtree-dev flagged the delta on 2026-05-23.
Closed — superseded. Target was v0.19.0 → v0.22.1; the spec pin has since advanced to v0.29.0 (commit 562001a, pinned 2026-05-26) via the v0.11.0/v0.13.0/v0.14.0 integration arcs. The v0.22.1 intermediate refresh is moot — we're seven minors past it and all consumer surfaces (POST /sessions, messages SSE, cancel) remain stable. memory_context (Phase 2.1) opt-in remains a separate untracked follow-up if ever wanted.