release: prepare Record Files 1.0 (Core RC.22, Collaboration 1.0.0, current docs)

Pin QQQ Core 4.1.0-RC.22 and the released Collaboration 1.0.0 in place of the snapshot placeholders, and replace the paused-checkpoint text. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-06 09:31:26 -06:00
3 changed files with 6 additions and 13 deletions
@@ -1,6 +1,6 @@
 # QBit Record Files

-> **Paused, unreleased work in progress — 2026-11-04.** Implementation has stopped. This is a source checkpoint, not a production-ready release or a complete installable package set.
+> **Version 1.0.** Published to the KOF22 Gitea Maven registry (`com.kingsrook.qbits`). Requires QQQ Core `4.1.0-RC.22` and QBit Collaboration `1.0.0`.

 Start with [current status and build prerequisites](docs/RELEASE-STATUS.md) and [known issues](docs/KNOWN-ISSUES.md). These documents supersede older release-readiness statements below.

@@ -1,9 +1,4 @@
 # Known issues and unfinished work

-Updated: 2026-11-04. These are unresolved items, not a plan currently being executed.
-
- Public Collaboration 0.1.0-RC.6 does not provide the attachment lifecycle, upload journal, recovery and download APIs this module requires.
- The corresponding canonical Collaboration integration is preserved on a separate work-in-progress branch. It requires confirmed rollback callbacks in QQQ Core/RDBMS; public QQQ 4.1.0-RC.21 is insufficient for that dependency chain.
- Current snapshot dependency versions are placeholders for source integration, not published installation coordinates. No clean consumer installation of the complete public cohort has been demonstrated.
- Full Record Files verification, database integration, retained-file recovery and final standard-UI acceptance remain incomplete for this reconciled source.
+- Final standard-UI acceptance needs the matching Next UI release and the host configuration.
 - Permanent access depends on the host's durable object storage, backups, retention and permission configuration. A source-level interface or unit test alone does not prove operational permanence.
@@ -22,12 +22,10 @@
      <maven.compiler.source>21</maven.compiler.source>
      <maven.compiler.target>21</maven.compiler.target>
      <jacoco.version>0.8.15</jacoco.version>
-      <!-- Released qqq (Maven Central); one core for the whole module, imported through qqq-bom-pom (see the qqq-snapshot profile). -->
-      <qqq.version>4.1.0-RC.21</qqq.version>
-      <!-- NOTE: collaboration's lifecycle code also needs core after-rollback callbacks (CORE-DEPENDENCY.md); raise this to the core release that has them. -->
-      <!-- Candidate collaboration carrying the attachment lifecycle SPI (feat/record-files-standalone, not yet released).
-           Not in public 0.1.0-RC.6. Qualify with a locally installed 0.1.0-SNAPSHOT; see COLLABORATION-HANDOFF.md. -->
-      <qbit-collaboration.version>0.1.0-SNAPSHOT</qbit-collaboration.version>
+      <!-- QQQ Core 4.1.0-RC.22 from the Gitea registry, imported through qqq-bom-pom. It includes the after-rollback callbacks Collaboration needs. -->
+      <qqq.version>4.1.0-RC.22</qqq.version>
+      <!-- Released Collaboration carrying the attachment lifecycle SPI. -->
+      <qbit-collaboration.version>1.0.0</qbit-collaboration.version>
   </properties>

   <parent>