feat!: snake_case assistant_ table and key names (0.1.0-RC.2) #3

Merged
KofTwentyTwo merged 3 commits from feature/snake-case-table-names into develop 2026-10-12 20:17:10 +00:00
3 Commits
Author SHA1 Message Date
james.maes a4f113ef61 Merge branch 'develop' into feature/snake-case-table-names 2026-10-12 15:15:12 -05:00
james.maesandClaude Opus 5.5 bf914dc76e fix: keep the assistant.hasAccess permission
QQQ core's standard permission suffix is hasAccess
(PrivatePermissionSubType.HAS_ACCESS) and the assistant base already
follows the naming rule, so the permission stays assistant.hasAccess,
matching the sql-workbench rename. Drops LEGACY_ACCESS_PERMISSION and
updates README, CHANGELOG, UPGRADE.md and NamingTest. Table, PVS and
key-type renames are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 14:12:00 -05:00
james.maesandClaude Opus 5.5 e5413d8ad0 feat!: snake_case table, permission and key names (assistant_ prefix)
Applies the QRun-IO naming rule (owner, 2026-10-12): table names are
lowercase snake_case and prefixed with the qbit's name. Metadata only;
docs/schema-postgres.sql already creates assistant_* tables.

- Tables: assistantConversation ... assistantUsageDaily become
  assistant_conversation, assistant_message, assistant_turn,
  assistant_turn_event, assistant_tool_call, assistant_feedback,
  assistant_policy, assistant_usage_daily. The conversation PVS follows.
- Permission assistant.hasAccess becomes assistant.has_access
  (assistant.admin unchanged).
- Owner key type assistantUserId becomes assistant_user_id; all-access
  key assistant_user_id_all_access.
- @Deprecated LEGACY_* constants keep the RC.1 names until 0.2.0.
- UPGRADE.md lists the stored references to update (permissions,
  saved views and reports, audit_table names) with sample SQL.
- NamingTest pins the new and legacy names.

Target: 0.1.0-RC.2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 14:04:57 -05:00