From 45db9e2e8735c3228cf2e1676c8477343024a2ab Mon Sep 17 00:00:00 2001 From: James Maes Date: Mon, 12 Oct 2026 16:14:09 -0500 Subject: [PATCH] docs: note that 0.1.0-RC.2 is a burned republish of RC.1 A tag build of v0.1.0-RC.1 published 0.1.0-RC.2 with the RC.1 code (QRun-IO/qqq-orb#20). Add a dated do-not-use entry for RC.2 and label the snake_case change as 0.1.0-RC.3, the next real candidate. Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c281906..b1fe7d5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,7 +8,7 @@ Phase 0/1 of the QQQ Assistant: read-only Q&A and navigation. Requires QQQ 4.1 w - the AI tool kernel (`qqq-backend-core` `actions.ai`, QRun-IO/qqq#1078) - the developer-panel contract (QRun-IO/qqq#1076). -### Changed (0.1.0-RC.2) +### Changed (0.1.0-RC.3) - **Snake_case names** (QRun-IO naming rule, 2026-10-12). Metadata only; the physical tables were already `assistant_*`: - tables `assistantConversation` ... `assistantUsageDaily` are now `assistant_conversation`, `assistant_message`, `assistant_turn`, `assistant_turn_event`, `assistant_tool_call`, `assistant_feedback`, `assistant_policy` and `assistant_usage_daily`; the conversation possible-value source follows the table name - permissions are unchanged: `assistant.hasAccess` keeps QQQ's standard `hasAccess` suffix, and `assistant.admin` stays as is @@ -60,3 +60,7 @@ Phase 0/1 of the QQQ Assistant: read-only Q&A and navigation. Requires QQQ 4.1 w - **Limits.** Page-context scalars are capped (strings up to 512 characters, at most 100 selected ids). Conversation lists are limited to 200, running turns to 50, and replay is paged at 500 events. - **Ordering.** Terminal events (`usage`, `error`, `message.end`) are persisted before the turn's status becomes final. - **Supplemental meta-data.** The `assistant` supplemental instance meta-data is registered when the QBit is enabled. + +## [0.1.0-RC.2] - 2026-10-12 + +**Do not use.** 0.1.0-RC.2 on Maven Central is an accidental republish of the RC.1 code by a tag build; do not use it. The next real candidate is 0.1.0-RC.3. (Cause: QRun-IO/qqq-orb#20; the `publish_release` workflow now runs on GA tags only.) -- 2.54.0