v0.6.0

• You can now assemble and set up your team by chatting. Alfred asks setup questions, proposes fixed, allowlisted actions, previews team names, and routes every write through the same approval gates as the form-based setup. You can also build a full roster theme just by describing the team you want.
• Agents have a stable identity that themes sit on top of. Every runner is now addressed by a fixed role such as architect, senior-dev, reviewer, or test-engineer, and the Batman cast (Batman, Lucius, Ra's al Ghul, Bane) is the default display theme layered over those roles. Renaming your team never changes how the runtime, scheduler, or GitHub labels work.
• Alfred remembers what your repositories have taught it, with nothing extra to run. The default memory store is now a single embedded SQLite file that gives semantic-quality recall using only the Python standard library. There is no Redis, no separate embedder, and no daemon to keep alive for the common case. Redis Agent Memory stays fully supported for operators who already use it.
• The fleet spends fewer tokens on the same work. Verbose tool output is compacted before it reaches the model, large source files are read as a structure-first skeleton with targeted follow-up reads, and only the lessons that matter to the current task are injected, ranked and trimmed to a budget. None of this changes the result of a run.
• Optional "batteries" are now a first-class, opt-in idea. A shared manifest, an alfred batteries command, and a picker in the desktop onboarding let you turn extras such as Redis memory, a stronger compression engine, the code-structure memory server, dense embeddings, and a Postgres scale tier on or off. Alfred runs fully with zero batteries; the built-ins are always on.
• The public story is rewritten for a non-technical reader. The README, the landing hero, and the docs now lead with plain-language positioning: a local coding-agent team that plans, builds, reviews, and ships, and remembers what it learns.

Full changelog: CHANGELOG.md