james.maesandClaude Sonnet 5.5
0df2fc81e4
Align every module to QQQ Core 4.1.0-RC.22 and replace the paused-checkpoint status text with the current 1.0 status and operating limits. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1.2 KiB
Scripting — status
Version 1.0, built and published by the shared ci-workflows Maven pipeline to the KOF22 Gitea Maven registry (com.kingsrook.qbits). The Java reactor (base, rdbms, middleware, github) is verified by mvn deploy in that pipeline, which runs the tests once.
Purpose
Shared TypeScript authoring and compilation, immutable published scripts, scoped API capabilities, record lifecycle hooks and isolated execution integration.
Layout and build
base/, rdbms/, middleware/ and github/ are the Java reactor modules. worker/, wasm-runtime/, supervisor/ and deploy/ are separate runtime components with their own build instructions; a Java package build does not build or qualify runtime images. Use Java 21 and ./mvnw verify. Depends on QQQ Core 4.1.0-RC.22.
Operating limits
Running or compiling script code needs a hardened external worker deployment that you must qualify on your own runtime; with none configured every build and execution fails closed. Do not bypass the existing qualification flags. See known issues.
The outstanding dependency order is Core, Collaboration, Scripting/Record Files, then the Generation bridges and matching UI.