Tale v0.4.6

0.4.6 is a fix release on the 0.4 line — an in-place update: tale update, then tale deploy. No data migrations ship with it.

Highlights

Chat Auto no longer picks a draft model for a document. A short prompt plus a PDF used to score as draft because attachments were invisible to the band heuristic — a 491-page statute was summarized from one 20k-character window. A document attachment now floors the band at standard. The rag_fetch tool description now says: never present a partial read as a summary of the whole source — keep fetching until nextOffset is absent, or say exactly which part was read. (#2979)

Behaviour changes

• Messages with a document attachment (not image, audio, or video) never land below the standard band on Auto. The floor applies on every path (bare file send, trivial greeting), outranks the light-work discount, and never lowers what the text already earned. Follow-ups without re-attaching re-score on text. (#2979)
• rag_fetch is steered to keep fetching until nextOffset is absent, or to name exactly which part was read. (#2979)

Migration notes

No new data migrations in 0.4.6 — tale deploy is an image update only. Updating straight from 0.4.0 applies the four 0.4.1 migrations automatically on the way.

Upgrading

tale update    # a 0.4.x CLI stays on the 0.4 line and picks up 0.4.6
tale deploy    # pulls the 0.4.6 images

On 0.3.x? The 0.3 → 0.4 cutover is a fresh deployment, not an upgrade — read the v0.4.0 release notes and Upgrades → 0.3 → 0.4: breaking cutover before moving.

What's Changed

• fix(platform): chat Auto — document attachments floor the band at standard by @larryro in #2979

Full Changelog: v0.4.5...v0.4.6