Brings every table the QBit declares to the QQQ table standard: createDate and modifyDate, date-time, not editable, set by QQQ.
What changes
Nine tables lacked a standard date. Eight had createDate only (assistant_turn_event, assistant_tool_call, assistant_feedback, assistant_usage, assistant_data_audit, assistant_budget_event, assistant_client_error, assistant_pending_action_claim) and assistant_budget_usage had neither. All nine now declare both. The other tables already had them.
Write paths: every write the QBit makes goes through QQQ's own insert and update actions (AssistantStore), so QQQ sets both on insert and moves modifyDate on update: the incremented daily usage counter, a decided pending action, a cleared tool result, a scheduled run that ends, the accounting row that follows a usage row. Tables that are only inserted (turn events, feedback, client errors, data audit, budget events, pending action claims) have modifyDate equal to createDate.
Schema: the QBit ships a reference DDL (docs/schema-postgres.sql), not changesets. An additive block is appended at its end: nullable columns defaulting to CURRENT_TIMESTAMP (no table rewrite on PostgreSQL 11 and later, safe while the previous release still runs), and an UPDATE per table that gives existing rows their own creation time. See UPGRADE.md.
Tests
TableStandardDatesTest: iterates the tables the producer declares (a table added later without the dates fails) and checks type, editability and both behaviors; exercises the store's insert and update paths (usage counter increment, pending action decision and claim, tool result clearing, budget accounting projection, scheduled run) for set-on-insert, modifyDate moves, createDate stays, and equal dates on insert-only rows.
TableStandardSchemaTest: the reference DDL creates both columns for every declared table.
No dependency, build, CI or release configuration changed.
Brings every table the QBit declares to the QQQ table standard: `createDate` and `modifyDate`, date-time, not editable, set by QQQ.
## What changes
- Nine tables lacked a standard date. Eight had `createDate` only (`assistant_turn_event`, `assistant_tool_call`, `assistant_feedback`, `assistant_usage`, `assistant_data_audit`, `assistant_budget_event`, `assistant_client_error`, `assistant_pending_action_claim`) and `assistant_budget_usage` had neither. All nine now declare both. The other tables already had them.
- Write paths: every write the QBit makes goes through QQQ's own insert and update actions (`AssistantStore`), so QQQ sets both on insert and moves `modifyDate` on update: the incremented daily usage counter, a decided pending action, a cleared tool result, a scheduled run that ends, the accounting row that follows a usage row. Tables that are only inserted (turn events, feedback, client errors, data audit, budget events, pending action claims) have `modifyDate` equal to `createDate`.
- Schema: the QBit ships a reference DDL (`docs/schema-postgres.sql`), not changesets. An additive block is appended at its end: nullable columns defaulting to `CURRENT_TIMESTAMP` (no table rewrite on PostgreSQL 11 and later, safe while the previous release still runs), and an `UPDATE` per table that gives existing rows their own creation time. See UPGRADE.md.
## Tests
- `TableStandardDatesTest`: iterates the tables the producer declares (a table added later without the dates fails) and checks type, editability and both behaviors; exercises the store's insert and update paths (usage counter increment, pending action decision and claim, tool result clearing, budget accounting projection, scheduled run) for set-on-insert, `modifyDate` moves, `createDate` stays, and equal dates on insert-only rows.
- `TableStandardSchemaTest`: the reference DDL creates both columns for every declared table.
No dependency, build, CI or release configuration changed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Nine tables lacked a standard date: eight had createDate but no modifyDate
(turn events, tool calls, feedback, model calls, data audit, budget events,
client errors, pending action claims) and the budget accounting table had
neither. All nine now declare both, date-time, not editable, set by QQQ.
Every write the QBit makes goes through QQQ's own insert and update actions,
so an insert sets both and an update (an incremented daily usage counter, a
decided pending action, a cleared tool result, a scheduled run that ends, the
accounting row that follows a usage row) moves modifyDate. A table that is
only inserted has modifyDate equal to createDate.
The reference DDL gets an additive block (nullable columns defaulting to the
time of the write, so the previous release keeps working; existing rows get
the table's own creation time). Tests iterate the declared tables, exercise
the store's insert and update paths, and check the DDL creates the columns.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
QQQ's createDate and modifyDate behaviors each read the clock, so the two
values of one insert differ by a few microseconds on a clock finer than the
machine this was first run on. The decision claim and the budget event are
written once and never change; an insert customizer on those two tables makes
modifyDate the same instant as createDate. The test of the other tables no
longer asserts equality they cannot give (they are rewritten when a
transcript is redacted).
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.
Brings every table the QBit declares to the QQQ table standard:
createDateandmodifyDate, date-time, not editable, set by QQQ.What changes
createDateonly (assistant_turn_event,assistant_tool_call,assistant_feedback,assistant_usage,assistant_data_audit,assistant_budget_event,assistant_client_error,assistant_pending_action_claim) andassistant_budget_usagehad neither. All nine now declare both. The other tables already had them.AssistantStore), so QQQ sets both on insert and movesmodifyDateon update: the incremented daily usage counter, a decided pending action, a cleared tool result, a scheduled run that ends, the accounting row that follows a usage row. Tables that are only inserted (turn events, feedback, client errors, data audit, budget events, pending action claims) havemodifyDateequal tocreateDate.docs/schema-postgres.sql), not changesets. An additive block is appended at its end: nullable columns defaulting toCURRENT_TIMESTAMP(no table rewrite on PostgreSQL 11 and later, safe while the previous release still runs), and anUPDATEper table that gives existing rows their own creation time. See UPGRADE.md.Tests
TableStandardDatesTest: iterates the tables the producer declares (a table added later without the dates fails) and checks type, editability and both behaviors; exercises the store's insert and update paths (usage counter increment, pending action decision and claim, tool result clearing, budget accounting projection, scheduled run) for set-on-insert,modifyDatemoves,createDatestays, and equal dates on insert-only rows.TableStandardSchemaTest: the reference DDL creates both columns for every declared table.No dependency, build, CI or release configuration changed.
🤖 Generated with Claude Code