PiClaw v2.7.1 — The Ipcress File

PiClaw v2.7.1 — "The Ipcress File"

A model-auth and request-configuration patch: fewer stale private-import notes, clearer provider setup, and fewer opportunities for authentication wiring to behave like a classified memo left in the wrong filing cabinet.

Fixes

• Model auth documentation and request configuration are aligned with the Earendil 0.80.x runtime APIs, so provider setup has fewer contradictory breadcrumbs and less “ask the source code, it knows” energy.
• Request configuration paths for side prompts, context pruning, smart compaction, and streamed completions now follow the updated runtime contracts instead of leaning on stale assumptions from the previous API shape.
• E2E setup documentation and model-configuration helpers were updated around the current provider/auth setup, because test environments deserve instructions that are not historical fiction.

Under the hood

• Earendil packages were bumped to 0.80.2, keeping Piclaw on the current public runtime surface after the v2.7.0 migration.
• Stale private-import guidance was removed, because telling future maintainers not to use a private path that no longer exists is less documentation and more séance.
• Model-auth and side-prompt runner tests were updated to cover the current auth/request wiring.
• Pack hygiene, import boundaries, and public add-on compatibility were validated against the updated API surface.

Known issues

• Provider auth remains provider auth: the best documentation in the world cannot make OAuth emotionally nourishing.
• Third-party integrations should still retest against the public runtime APIs rather than poking at upstream internals with a stick labelled “compatibility”.

Upgrade

• Upgrade normally; no database migration is required.
• If model auth setup now feels less like decoding a spy dossier in a dark room, that is intentional.