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

2026-11-11T13:51:53Z

james.maes commented

2026-11-11 13:51:53 +00:00

Release merge for the next 0.1.0 RC. Brings #98 to the release line: save_analysis (a saved analysis and its daily emailed schedule as ONE confirmed proposal), the outcome of a decided action told to the conversation, a schedule refused with the reason while it could not run (withScheduledDeliveryCheck), and rule 14 (ask one short question instead of guessing). The merge is clean; <revision> stays the release branch's (0.1.0-RC.27), so the workflow publishes 0.1.0-RC.28.

Needed by GG Forge dev.

🤖 Generated with Claude Code

Release merge for the next 0.1.0 RC. Brings #98 to the release line: `save_analysis` (a saved analysis and its daily emailed schedule as ONE confirmed proposal), the outcome of a decided action told to the conversation, a schedule refused with the reason while it could not run (`withScheduledDeliveryCheck`), and rule 14 (ask one short question instead of guessing). The merge is clean; `<revision>` stays the release branch's (0.1.0-RC.27), so the workflow publishes 0.1.0-RC.28. Needed by GG Forge dev. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

james.maes added 3 commits 2026-11-11 13:51:53 +00:00

feat(tools): save and schedule an analysis with one confirmation; decided actions reach the conversation; ask before guessing

maven / build (push) Successful in 6m31s

Details

build / maven (push) Successful in 6m31s

Details

7c54a02a87

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>

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

maven / build (push) Successful in 6m43s

Details

build / maven (push) Successful in 6m43s

Details

7d4014d79f

Merge develop into release/0.1 for the next 0.1.0 RC (save_analysis, decided actions, ask before guessing)

maven / build (push) Successful in 5m13s

Details

build / maven (push) Successful in 5m13s

Details

07b06f2070

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

james.maes merged commit 08c8264f23 into release/0.1

2026-11-11 13:57:26 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-assistant#99