Integrate attachments, upload journal, presence and Redis presence for KOF22 #59

Merged

james.maes merged 6 commits from kof22/collab-v2 into develop 2026-11-06 14:52:53 +00:00

Conversation 0 Commits 6 Files Changed 159

+21349 -753

6 Commits

Author	SHA1	Message	Date
james.maesandClaude Sonnet 5.5	024cfc21a9	release: prepare Collaboration 1.0 (Core RC.22 BOM, Redis RC.1, current status docs) ... Replace the default-active Core snapshot profile with the released Core 4.1.0-RC.22 BOM, pin qbit-redis to its first release candidate, and replace the snapshot-era status text with the current 1.0 status. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-05 17:25:50 -06:00
James MaesandClaude Sonnet 5.5	63245b14e0	feat(collaboration): integrate presence, Redis presence, virtual-field and fixture work on the attachment base ... One reviewable integration on current develop 7d61f29e. It starts from feat/record-files-standalone (attachment lifecycle, upload journal, retention SPI; descends from develop) and adds the owner stack content from feature/collab, feature/collab-int-20261029, feature/field-values-1196, feature/presence-recovery-1300, test/presence-capacity-1302 and the fix/attachment-transactions-1289 / fix/mywork-query-bounds-1291 work, plus KOF22 adaptations: CollaborationQBitConfig.attachmentLifecycle, CollaborationRecords.insertActivity/query(transaction), ActivityWriter source feature routing, and the Redis/fixture tests. Build: develop CI files are preserved. pom.xml only adds the Redis API guardrail allow-list and an optional qbit-redis dependency; the core and qbit-redis versions stay on the canonical SNAPSHOT lines with markers to repin after the core and redis integration PRs are published (order CORE -> REDIS -> COLLAB). No PRIVATE or feature-snapshot coordinate is introduced. Not yet compiled: it needs the core integration artifact (virtual-field providers). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-05 17:19:49 -06:00
James MaesandGPT-6 Codex	fb7c6316bf	docs: record successful Record Files consumer verification ... Co-Authored-By: GPT-6 Codex <noreply@openai.com>	2026-11-05 17:19:48 -06:00
James MaesandGPT-6 Codex	9fbe20c9d6	fix: handle upload recovery metadata and align Core dependency ... Verify all 269 Collaboration tests, including PostgreSQL attachment recovery and MySQL/PostgreSQL journals, against the compatible Core snapshot. Co-Authored-By: GPT-6 Codex <noreply@openai.com>	2026-11-05 17:19:47 -06:00
3 people	1c05422901	chore: preserve paused QBit work and document remaining issues ... Save the current implementation and README, status, and known-issue documentation at the user-requested stop. No completed release or deployment is claimed. Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: GPT-6 Codex <noreply@openai.com>	2026-11-05 17:19:47 -06:00
James MaesandClaude Sonnet 5.5	89e77b67b9	feat(attachments): reconcile reviewed attachment lifecycle, upload journal and retention SPI ... Selective three-way reconciliation onto develop 7d61f29 (base c4eb972 = original ancestor; theirs = reviewed b6fb2382 third-party-src/qbit-collaboration). Attachments package (main and tests), upload journal (H2/MySQL/PostgreSQL), cleanup queue, recovery/adoption processes, attachment schema fields, tables, pagination, delivery schema, help text and docs. Upstream presence work, CI workflows and release convention are untouched. Redis presence, my-work bounds, notifier and custom-field changes in b6 are deliberately not included. Targets qqq 4.1.0-RC.21 BOM. Needs core QBackendTransaction after-rollback callbacks (not in RC.21): see docs/CORE-DEPENDENCY.md. Not compiled against RC.21. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-05 17:19:46 -06:00