release: merge develop into release/0.1 (analyze_records) #97

Merged
james.maes merged 12 commits from rc/develop-into-release-0.1-analyze into release/0.1 2026-11-11 13:45:10 +00:00
Owner

Release merge for the next 0.1.0 RC. Brings #96 (analyze_records: grouped questions through the data-analysis pivot, as the signed-in user) to the release line. Conflicts resolved: pom.xml keeps the release branch's <revision> (0.1.0-RC.26, so the workflow publishes 0.1.0-RC.27); CHANGELOG.md takes develop's new section.

Needed by GG Forge dev.

🤖 Generated with Claude Code

Release merge for the next 0.1.0 RC. Brings #96 (`analyze_records`: grouped questions through the data-analysis pivot, as the signed-in user) to the release line. Conflicts resolved: `pom.xml` keeps the release branch's `<revision>` (0.1.0-RC.26, so the workflow publishes 0.1.0-RC.27); `CHANGELOG.md` takes develop's new section. Needed by GG Forge dev. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
james.maes added 12 commits 2026-11-11 13:34:35 +00:00
test(assistant): pin the live thread to real title, question, answer and tool steps at message.end
maven / build (push) Successful in 4m29s
build / maven (push) Successful in 4m29s
a588aafe2e
The panel reloads the conversation at message.end. A tool-using turn must
already have stored the real title, the question and answer parts and the
tool-call rows then, not the transcript redactor's placeholders
(changed:v1, [], {}). The redactor is always attached to a turn, so this is
independent of Secured Data. Fails without the flush-before-message.end
ordering (RC.24), passes on develop and RC.25.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
fix(engine): a stalled database can no longer hang a turn on 'Thinking'
maven / build (push) Successful in 5m23s
build / maven (push) Successful in 5m23s
0c32c43f8c
The watchdog ran the deadline logic after two database reads and heartbeat() was synchronized on the monitor that finish() needs, so one blocked database call stopped the deadline, the force-finalize and the final message.end. The deadline now runs first with no database access, housekeeping runs on a bounded abandonable worker, finish() has a guard that ends the stream with an error event, and every phase logs at INFO.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A new read tool: group a table by one or two fields (a date field optionally by a calendar
unit) and compute a count, sum, average, minimum, maximum or distinct count per group, with
the usual filter. It is one call of the data-analysis qbit's pivot operation
(POST /qbit/data-analysis/tables/{table}/pivot) through the same gateway and with the
signed-in user's session, so table read, the table's analyze permission, field access and
record locks decide as on the Analyses screens. The assistant only narrows it: data access
READ on the table, fields whose values it may see, the policy's row cap. Offered only where
the data-analysis extension is registered; no production dependency on that qbit.

Tests run against the released data-analysis qbit served by the real UI API.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
OPERATIONS stays the list of core /qqq/v1 operations (every one is invocable on any
instance); analyze_records moves to EXTENSION_OPERATIONS, offered and invocable only where
the data-analysis extension is registered. A test pins that it is neither offered nor
invocable without the extension.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
test(tools): run the analysis tests against data-analysis 0.3.0-RC.2 (relative dates in filters)
maven / build (push) Successful in 5m17s
build / maven (push) Successful in 5m17s
10d80f6bcf
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Merge develop into release/0.1 for the next 0.1.0 RC (analyze_records)
maven / build (push) Successful in 6m27s
build / maven (push) Successful in 6m27s
f1634b0911
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

# Conflicts:
#	CHANGELOG.md
#	pom.xml
james.maes merged commit d761bd4a7d into release/0.1 2026-11-11 13:45:10 +00:00
Sign in to join this conversation.