ratatoskr

Files

T

vh b798068932 pin: re-pin to Worldtree's FROZEN v1 surface (OpenAPI 2.2.0 + SSE schema)

v1 coverage-audit remediation P-1: vendor the authoritative machine-
readable artifacts and pin them for drift-checking, advancing the spec
pin from v0.35.16 (f1b59f8) to v1.0.0b2 (5810a26).

- Vendor docs/conversation-api-openapi.json (OpenAPI 2.2.0, 40 path-
  groups) + docs/conversation-api-sse-events.schema.json (11 events).
- Pin all three Conversation-API artifacts in .corviduo-canonicals.toml:
  OpenAPI + SSE schema as strict drift gates (canonical_drift.py), the
  prose markdown as tolerate_drift reference. Drift check green (10/10).
- pyproject: worldtree-spec-rev -> 5810a26, worldtree-version -> v1.0.0b2
  (was stale at v0.29.0), pinned-on -> 2026-06-30.
- SPEC-PIN.md: current-pin table + history row + vendored-artifacts list.
- coverage-map.md: P-1 marked remediated; the map now audits a frozen,
  diffable target.

The prose markdown is byte-identical to v0.35.16 (last WT edit
2026-05-31); the b2 surface lives only in the OpenAPI. No client-
facing code change (the b2 409/503 + unified error envelope were
already consumed in v0.18.3/.4) -> pin-only, no version bump.

2026-06-30 15:28:52 -07:00

contracts

feat: map Worldtree b1 eager turn-launch statuses (409/503) in stream_turn

2026-06-30 13:11:33 -07:00

architecture.md

init: seed Ratatoskr from corviduo-project-template + ship v0 scaffold

2026-05-20 20:38:22 -07:00

bifrost-self-test.md

pin: bump Worldtree spec to f1b59f8 (v0.35.16) — cold recall closes end-to-end

2026-06-17 08:24:27 -07:00

canonical-sync.md

init: seed Ratatoskr from corviduo-project-template + ship v0 scaffold