Tale v0.4.11

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

Highlights

Review of agent work lives on the status gate. The gray Needs review banner is gone. Setting the task to Done (sheet Status or board drag) is the approve; a comment or @mention of the assignee sends work back; any other leave withdraws the request. Inbox and email copy now say that. review_policy (independent reviewer / competence) now runs on those gestures — they used to skip the checks because only the deleted card enforced them. (#3042)

Automation agent nodes run on a vendor subscription credential. The same subscription lane project agents already had. A broker-only org that already served a pinned project agent now serves the node too, instead of failing every turn with "no configured provider serves model …". A direct api-key or env credential still wins when both can serve the model. llm nodes stay direct-only — a subscription is bound to its vendor harness and never serves a raw API call. (#3040)

Chat and sandbox tools hand the model ISO dates, not epoch milliseconds. 1787124301288 became a calendar four weeks off (mid-August arrivals reported as mid-September). Those fields now emit 2026-08-19T07:25:01.288Z. Stored values, sort order, UI date cells, and REST are unchanged. (#3037)

Behaviour changes

• Approve is Status → Done, not a card button. Automation-owned subject-panel Approve / Request changes stay; Approve writes Done and can now be refused by review_policy. (#3042)
• Sending work back is a comment / @mention. Moving to any other column withdraws (bells clear; next park mints a fresh request). Dragging into In review opens the gate; leaving and re-entering remints. Agent, automation, and GitHub-sync leaves withdraw, never record a human approve. (#3042)
• A Done that used to skip review_policy can now toast and refuse — "Your organization requires an independent reviewer" or "Approving this review requires a competence you don't hold." (#3042)
• Subscription serving on agent nodes needs no reconfigure. In-flight scheduled starts from before the deploy keep the old gateway behavior. Subscription turns stay off the gateway meter, same as the task lane. (#3040)
• A non-usable timestamp is omitted from the tool result, not a failed turn. (#3037)

Upgrading

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

From 0.4.10 a default tale deploy is enough — this cut has no stop-gated image content. If you never ran tale deploy --stop for 0.4.10, private knowledge search is still empty until db (or knowledge-db) is recreated so conversation_id exists.

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

• chore: adopt the shared toolchain and reformat by @yannickmonney in #3038
• ci: adopt the shared agent contract and standard workflow set by @yannickmonney in #3039
• fix: heal main after the template-alignment merges by @yannickmonney in #3041
• feat(platform): serve agent nodes on subscription credentials by @larryro in #3040
• fix(platform): give the model dates instead of epoch numbers by @Israeltheminer in #3037
• feat(platform): retire the task review card for the status gate by @larryro in #3042

Full Changelog: v0.4.10...v0.4.11