Ashlrverse 3.23.0 — Automatic chat and outcome-driven Fleet

Ashlrverse 3.23 brings Automatic chat and outcome-driven Fleet work into one workbench: work with agents interactively, or give the Fleet a desired result to pursue.

• Automatic chat: describe the task and let routing choose an eligible account and model. Advanced retains explicit choices. Failed routing preserves your draft; local-only projects keep their privacy boundary.
• Work for me: save an outcome, repositories and acceptance criteria. The Leader refines dependency-ready tasks into the resident queue. Edit, Pause and Resume preserve revisions, runs and selected proposals, with current-scope checks before provider, review and merge actions.
• Automatic scheduling: remove operator count ceilings without allocating a fabricated worker count. Actual ready work, serving capacity and account admission determine dispatch. Manual count ceilings remain available; financial settings and signed authority remain separate.
• More reliable execution: preserve the original task and correlated tool calls during context compaction, record claims and run identities atomically, retry terminal-record contention without rerunning the producer, and retain cumulative producer duration across proposal capture.
• Complete operator guides: npm now includes the Automatic, Verse, resident setup and related operational guides with checked local links.

Validation for source 047cd263d402174ed882240e43b3d3561d2084d2: all seven prepublish stages passed, including three exhaustive backend shards, seven isolated files, two campaign cases and the complete web suite. All 13 hosted checks passed. Every one of the 10,463 archive files matched the frozen source/build; three isolated Hub/Plugin consumer combinations passed. Native packaging matched all 711 public assets, the compiled outcome-worker metadata smoke passed 32 checks, and independent DMG verification passed.

The Apple Silicon DMG is signed with Ashlr Local and is not Developer ID notarized. Installing or publishing this release does not activate resident autonomy: connected accounts, an effective signed grant and a running resident are required. The compiled smoke validates metadata and authority boundaries without contacting live providers.