Lifecycle hooks, a queryable substrate & recurring jobs

Until now the value lived inside interactive runs. Three layers landed together that turn it into infrastructure you can build on.

• Lifecycle hooks: the core emits documented, versioned events (council recorded, run finished, persona grounded, …); subscribe in-process, via the extension seam, or with durable command/webhook hooks — a Slack push on "session finished" is one CLI line.
• The queryable substrate: paginated, filterable reads over personas, projects, councils and syntheses with stable ordering and a versioned envelope; one structured study result per project; durable multi-turn persona chat; an access-guard seam ready for multi-tenant cloud.
• Recurring jobs (Cloud): deterministic trend watches that alert on meaningful change, and scheduled councils/simulations dispatched as fully-specified assignments to a host — cron-style intervals, daily anchors, or event triggers.