release: merge develop into release/0.1 (save_analysis, decided actions, ask before guessing) #99

Merged

james.maes merged 3 commits from rc/develop-into-release-0.1-save into release/0.1 2026-11-11 13:57:26 +00:00

Conversation 0 Commits 3 Files Changed 17

+1493 -14

3 Commits

Author	SHA1	Message	Date
james.maesandClaude Fable 5.2	07b06f2070	Merge develop into release/0.1 for the next 0.1.0 RC (save_analysis, decided actions, ask before guessing) ... Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-11 07:51:36 -06:00
james.maes	7d4014d79f	Merge pull request 'feat(tools): save and schedule an analysis with one confirmation; decided actions reach the conversation; ask before guessing' (#98) from feat/save-and-schedule-analysis into develop	2026-11-11 13:47:54 +00:00
james.maesandClaude Fable 5.2	7c54a02a87	feat(tools): save and schedule an analysis with one confirmation; decided actions reach the conversation; ask before guessing ... save_analysis proposes keeping an analyze_records question as a saved analysis the user owns and, when asked, a daily schedule emailed to them. One pending action lists everything that will be created with the numbers as they are now; nothing exists until the user confirms it (never auto-confirmed). On confirmation both records are created through the data-analysis tables' own insert operations with the confirming user's session. Offered only with the data-analysis extension and data access READ_WRITE on data_analysis_saved (a schedule also needs it on data_analysis_schedule); the user's own insert permission is read from GET /metaData first. A schedule that could never run is refused when proposed and again at confirmation, with what is missing: the instance is read (a schedule table, a scheduler on data_analysis_run_schedules) and the host is asked through AssistantQBitConfig.withScheduledDeliveryCheck. Confirming any pending action now adds a message of the assistant to the conversation (what was done, links to the records), and each earlier proposal carries what became of it in the next request (done, failed, cancelled, expired). Before, the model only ever saw 'waiting for confirmation'. Rule 14 for every model: ask one short question when a request is ambiguous in a way that changes the result (table, field, time zone); the user's browser time zone is stated in the per-user context. Golden task clarify-ambiguous-field. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-11 07:34:51 -06:00