Skip to content

Thinkroom v0.2.6

Choose a tag to compare

View all tags
@phenomenoner phenomenoner released this 03 Sep 07:36
· 3 commits to main since this release
v0.2.6
e65c05b

Thinkroom v0.2.6

This release makes Prime RPC transport accounting resilient to cumulative telemetry amplification while keeping hard resource ceilings and the existing provider-failover policy intact.

What changed

  • Separates exact raw-wire observation from an amplification-aware accounted transport budget.
  • Discounts only the repeated message_update.message and assistantMessageEvent.partial payloads; unknown and control fields remain charged, every event has a minimum cost, and projection depth is bounded.
  • Keeps a 64 MB per-line ceiling, a 64 MB accounted ceiling, and a 512 MB absolute raw ceiling.
  • Preserves transport metrics when otherwise valid backend results fail response-schema validation.
  • Makes the v0.2.4 to v0.2.6 SQLite migration chain and final schema attestation atomic.
  • Recognizes the exact released v0.2.5 managed-Skills receipt so production Skills can migrate directly to v0.2.6 while unknown or modified receipts still fail closed.
  • Aligns English and Traditional-Chinese guidance for the legacy and Prime 0.8.1 lifecycle custody paths.

Verification

  • All required clean-export gates passed on commit e65c05b311ad1b46e3d641977eff4583decbeecb, including 352 tests.
  • A locked candidate runtime passed package, native-process, and 44-distribution manifest verification.
  • The installed candidate read the production v0.2.5 Skills receipt without mutation and classified three Skills as UPDATE and their three agent descriptors as EXACT.
  • One isolated Terra/high three-branch run on the released transport implementation completed all three branches. Two provider calls transported more than the previous 64 MB raw threshold while remaining below the new accounted ceiling, and neither ended with OUTPUT_LIMIT_EXCEEDED.

The isolated provider run finished succeeded/partial: the 900-second soft deadline did not admit critique or synthesis. Two rollout attempts initially returned malformed provider output and required the existing route-preserving schema repair. This validates the transport repair and branch path; it does not claim complete synthesis, provider-wide reliability, or research correctness.

Installation

Verify SHA256SUMS, install the hash-locked dependencies from requirements-production.txt, then install the wheel with --no-deps. See docs/OPERATIONS.md for the native production procedure and rollback boundary.

Assets 8
Loading