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.
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)
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>
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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.xmlkeeps the release branch's<revision>(0.1.0-RC.26, so the workflow publishes 0.1.0-RC.27);CHANGELOG.mdtakes develop's new section.Needed by GG Forge dev.
🤖 Generated with Claude Code
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>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>