Cargento 0.24.0

Cargento tells you which of your agents need you, which are fine, and when it is safe to walk away. Everything it answered before this release was about status. This one is about intent: it is the first release where the board can tell you a session is working, healthy, and doing the wrong thing.

What you can do now

Hold a session to what you asked for. P2 and P3, extend. Type a goal and an expected output against any session, in your own words, when it starts or later, and read them beside what the record shows it has been doing. Backed by a store of its own that survives a restart, keeps every revision, and says which session your words are bound to when the binding is ambiguous.

Ask for a reading of how the two compare. P3, extend. A reading says which version of your words it read, how far its evidence goes, and where the evidence is too thin to tell. It never says the work is done. Four rulings govern what it may claim, and three of them are built into the producer rather than checked afterwards.

Have Cargento check a session while you are away. P3, new. Off by default, behind --unasked-readings, bounded per session and per day. It raises only a departure, never a reassurance, and what became of every notification it raises is written down, so a signal you never saw is not recorded as one you ignored.

Review what was raised, and what came after. P3, extend. One place showing every departure, whether it reached you, and what later evidence showed, with unknown as a first-class answer and the common one.

What Cargento saw end stays ended. P5, sharpen. A session that finished no longer reads as merely quiet after a restart, so a final reading is still takeable on it.

Upgrading

Nothing to do. No flag changed meaning, no route disappeared, no payload key stopped being published, and the Python floor is still 3.11. The ten supported harnesses are unchanged. Six new flags and six new routes arrive, all additive, and the two features that spend model capacity ship switched off.

What this release does not add

The Ask for a reading control is disabled until an abstention check has been run against hand-written marks, and that check has not been run. The away-checking lane is off by default. Neither is a coming-soon: both are gates that exist because a reading is a model's judgement about your intent, and the rulings behind them are recorded on the issues rather than implied here.

Nothing here changes P1, P4, or what Cargento promises about quota. The full map of what is promised and where each promise stops is in docs/promise-map.md.

---

What's Changed

• fix(skills): burndown reads a design reference, and eleven defects it could not survive by @gcko in #316
• feat(cockpit): import operator prototype and sync with main by @gcko in #312
• feat(annotations): hold a session to what you asked for by @gcko in #317
• docs(sync): reconcile the docs against #312 and #317, and advance the marker by @gcko in #318
• fix(reading): the board stops saying no reading exists when one does by @gcko in #319
• feat(deliveries): record what became of every raise, so an unseen signal is not read as an ignored one by @gcko in #320
• feat(unasked): check a session against what you asked while you are away, and raise a departure by @gcko in #321
• feat(ends): keep an observed session end across a restart of the board by @gcko in #322
• feat(scripts): score a reading against the abstention marks, before anything may ask for one by @gcko in #323
• feat(reading): a stored reading says why a row is unverifiable, and the save path says what the store did by @gcko in #324
• feat(departures): review what was raised while you were away, and what came next by @gcko in #325
• docs(sync): reconcile the docs against the Hold it to what I asked merges, and advance the marker by @gcko in #326
• docs(agents): three invariants a green suite does not enforce by @gcko in #327
• fix(departures): the record stands when the lane stops, and the act the board offers is the act it describes by @gcko in #328
• feat(cockpit): a raise says its baseline moved, and the cues reach a reader who cannot see them by @gcko in #329
• feat(annotations): a discard leaves a record that says when, and it never reads as nothing typed by @gcko in #330

Full Changelog: v0.23.0...v0.24.0