Conversation management: table access, archive/restore/delete actions, UI API 1.6.0 #65

2026-10-16T20:46:13Z

KofTwentyTwo commented

2026-10-16 20:46:13 +00:00

(Migrated from github.com)

Assistant users can manage their own conversations through the standard table UI: rename, pin, archive, restore and delete, including bulk record actions. Owner locks remain enforced; the Assistant app and other assistant tables remain admin-only. Deletion refuses active answers and removes child records.

UI API extension 1.6.0 adds running to conversation list items, read: true to conversation updates, and permission-gated conversationsTable to config. Hosts must apply AssistantSecurity.applySessionKeys for every signed-in assistant user. No schema migration is required for these changes.

User-supplied titles are encrypted in HIPAA mode even when they begin with enc:v1:. An unchanged encrypted title is preserved only when it exactly matches that same record's stored title; internal SYSTEM writes retain their existing storage path. Regression coverage exercises normal renames, prefix-looking plaintext, unchanged ciphertext and ciphertext copied from another record.

Integrated develop 63afe0b, preserving attachment support, owner-scoped scheduled notifications and fresh authorization checks for starter prompts with the combined three-prompt limit.

Validation:

Focused compatibility/security suite: 79 tests passed.
Full Maven wrapper verify: 509 tests, zero failures/errors/skips; all eight reactor modules succeeded and seven JaCoCo checks passed. Includes the pgvector container test.
Live provider evaluations remain excluded by the repository's default live group setting; they were not run.
git diff --check passed.

Full verify completed 2026-10-19 at 09:46 CDT in 4m26s. A subsequent docs-only changelog correction restored historical encoding and documented the encryption fix; source stayed unchanged. This is local verification; remote CI results follow publication.

Assistant users can manage their own conversations through the standard table UI: rename, pin, archive, restore and delete, including bulk record actions. Owner locks remain enforced; the Assistant app and other assistant tables remain admin-only. Deletion refuses active answers and removes child records. UI API extension 1.6.0 adds `running` to conversation list items, `read: true` to conversation updates, and permission-gated `conversationsTable` to config. Hosts must apply `AssistantSecurity.applySessionKeys` for every signed-in assistant user. No schema migration is required for these changes. User-supplied titles are encrypted in HIPAA mode even when they begin with `enc:v1:`. An unchanged encrypted title is preserved only when it exactly matches that same record's stored title; internal SYSTEM writes retain their existing storage path. Regression coverage exercises normal renames, prefix-looking plaintext, unchanged ciphertext and ciphertext copied from another record. Integrated develop `63afe0b`, preserving attachment support, owner-scoped scheduled notifications and fresh authorization checks for starter prompts with the combined three-prompt limit. Validation: - Focused compatibility/security suite: 79 tests passed. - Full Maven wrapper verify: 509 tests, zero failures/errors/skips; all eight reactor modules succeeded and seven JaCoCo checks passed. Includes the pgvector container test. - Live provider evaluations remain excluded by the repository's default `live` group setting; they were not run. - `git diff --check` passed. Full verify completed 2026-10-19 at 09:46 CDT in 4m26s. A subsequent docs-only changelog correction restored historical encoding and documented the encryption fix; source stayed unchanged. This is local verification; remote CI results follow publication.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-assistant#65