9 Commits

Include renames

Author	SHA1	Message	Date
james.maesandClaude Fable 5.2	c6aa0bf6b0	feat(foundation): preview, diagnostic and render target ports with registration hooks (P6a) ... The contracts the preview, bridge and render target packages plug into. No label prints differently and no existing host adapter changes. GenerationPorts: - Diagnostic (with Severity): a code from a closed vocabulary, an author element id, a box and named integers. It has no field that holds free text. - PreviewRequest, PreviewPage and Preview, and IsolatedRenderer.preview as a default that refuses, so an adapter written before it compiles unchanged. - 15 version 2 FailureCode values after the 13 released ones, and RenderException(FailureCode, Diagnostic) beside the existing constructor. - Integer targetDpi on RenderRequest (absent, 203, 300 or 600); the seven-argument constructor is kept and nothing reads the value yet. Registration points, each an empty class that is already called: GenerationPreviewProcesses, GenerationAssetProcesses, GenerationUpgradeProcesses and GenerationAssetTables from the producer, and GenerationPreviewWidget.section(table) from GenerationTables. Bridge: IsolatedRendererBridge maps any FailureCode name from a 0.1.0 worker to a typed refusal, so growing the enum alone would have widened what such a worker can name. The 13 released codes are now the set a 0.1.0 worker may name; BridgeTest asserts the other 15 stay generic. Tests: record validation, default refusals, source compatibility of the existing constructors, and that the producer registers exactly the tables, processes, choices, widgets and template sections it did before (the lists were captured from the untouched v1.1.0-RC.2 tag). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-11 17:28:43 -06:00
james.maesandClaude Fable 5.2	3ba676106f	build(coverage): gate renderer and bridge coverage at baseline; seeded mutation campaigns (P13) ... Coverage gates: - renderer and bridges/renderer gain JaCoCo (prepare-agent, report, check at verify) with a bundle rule at the measured baseline, rounded down: renderer 94% instructions and 91% lines, bridge 85% instructions and 82% lines. - New code is held to 100% line coverage from its first commit: packages com.kingsrook.qbits.renderer.scene2 and below, AssetInspector, ZplRaster, and the new foundation classes the label layout design names. The rules match nothing until those exist, so later packages do not edit these poms. - The foundation's 85% instruction and 90% class rule is unchanged. Fuzz scaffolding: - MutationCampaign in each module's test tree: a seeded, bounded mutation harness with no clock and no unseeded randomness; a finding replays from its seed and iteration. - One campaign per module in the normal test phase: what the version 1 scene parser accepts is a version 1 scene (checked by a second parser), and what the host printer gate accepts holds only the renderer's command set. - docs/security/fuzzing.md: targets, properties, limits, seeds and replay. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-11 17:28:42 -06:00
james.maesandClaude Fable 5.2	cfbf0744f9	fix(postgres): accept full_page_writes off on Amazon Aurora PostgreSQL only ... Generation qualification refused every Amazon Aurora PostgreSQL server: Aurora always reports full_page_writes = off and has no parameter to change it, because its storage layer does not write torn pages. The settings query now also returns to_regprocedure('aurora_version()') IS NOT NULL (true on Aurora, false on stock PostgreSQL, never an error). full_page_writes = off is accepted only when that is true. Stock PostgreSQL must still report it on, and fsync on, synchronous_commit on or remote_apply and every other check are unchanged on both. The refusal text now says full-page writes are not required on Aurora. Tests run on a real postgres:17 engine whose settings are really changed; only Aurora is simulated, by creating a function named aurora_version() in the test database. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-09 20:25:55 -06:00
james.maesandClaude Opus 5.5	4f850c2cf3	build(deps): align with Gitea registry (parent 2.2.1, QQQ 4.1.0-RC.26) ... bridges/printing/pom.xml: qqq.version: 4.1.0-RC.22 -> 4.1.0-RC.26 bridges/printing/pom.xml: qbit-record-files.version: 0.1.0-RC.1 -> 0.4.0-RC.1 bridges/printing/pom.xml: qbit-printing.version: 1.0.0 -> 1.2.0-RC.1 bridges/record-files/pom.xml: qqq.version: 4.1.0-RC.22 -> 4.1.0-RC.26 bridges/record-files/pom.xml: qbit-record-files.version: 0.1.0-RC.1 -> 0.4.0-RC.1 bridges/scripting/pom.xml: qqq.version: 4.1.0-RC.22 -> 4.1.0-RC.26 bridges/scripting/pom.xml: qbit-scripting.version: 1.0.0 -> 1.1.0-RC.3 foundation/pom.xml: qqq.version: 4.1.0-RC.22 -> 4.1.0-RC.26 pom.xml: parent -> 2.2.1 pom.xml: added qqq.version=4.1.0-RC.26 (parent BOM import) pom.xml: revision -> 1.1.0-SNAPSHOT Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-07 18:59:01 +00:00
james.maesandClaude Sonnet 5.5	cb420158ba	release: prepare Document Generation 1.0 (released Record Files, Scripting, Core RC.22) ... Pin QQQ Core 4.1.0-RC.22, Record Files 0.1.0-RC.1 and Scripting 1.0.0 in place of the SNAPSHOT placeholders, and replace the unreleased-checkpoint text. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-06 13:11:27 -06:00
james.maes	72de6f87e5	Merge pull request 'Make the reactor root the single version source; publish vendored OpenHTML at the family version' (#1) from kof22/single-revision into develop	2026-11-06 15:35:27 +00:00
james.maesandClaude Fable 5.1	313f081026	feat(authoring): rename document types, stock and templates natively ... Add DocumentDefinitionService.rename and the native authoring actions document_generation_{type,stock,template}_author_rename. The form loads the current name and saves only the trimmed name; names must be nonblank, at most 200 characters and free of control characters. The configure permission is checked at discovery and again at save, and the native UpdateAction keeps the host's field-level audit. GenerationStore.update now admits an id+name-only write for type and stock rows, so geometry, bindings, drafts, published revisions and queued pins stay immutable. No schema change. Carried locally by GG Forge as definition-rename.patch (pin 0.1.0-forge.ee782b7d6ea8-rename1); upstreamed so a published release can replace that pin. The prepare-step selection message is generalised to cover type and stock rows. Docs: AUTHORING.md describes the action, README and RELEASE-STATUS record the addition and its verification (./mvnw -pl foundation -am verify: 232 tests, Checkstyle and coverage gates met, including the Docker MySQL and PostgreSQL suites). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-06 08:59:39 -06:00
james.maesandClaude Sonnet 5.5	8351fd7fb4	build: make the reactor root the single version source of every module ... The release pipeline rewrites <revision> only in the ROOT pom.xml (the pinned legacy calculate_version.sh) and nothing passes -Drevision (java-verify runs plain `mvn verify`), but every module declared its own <revision>0.1.0-SNAPSHOT</revision> and did not inherit the root. After an RC rewrite the root would say the RC while the modules still built as the SNAPSHOT, so capture (target/<artifact>-<root version>.jar) would find no JAR and the publisher (one version per reactor) would reject the reactor. The root now inherits qbit-build-parent 2.1.1 (foundation's existing parent) and every module inherits the root with the per-module <revision> removed (relativePath ../pom.xml, ../../pom.xml, ../../../pom.xml; remote-renderer transport and adapter keep inheriting remote-renderer-parent). GAVs, module list, dependencies, sources and tests are unchanged. Audited with `help:effective-pom` (Maven 3.9.11, before/after for all 11 projects): - licenses: root, foundation (Apache-2.0) unchanged; bridges/scripting previously inherited AGPL-3.0 from build-parent 2.0.0 and now states it explicitly (build parent 2.0.0 -> 2.1.1 for this module); the vendored OpenHTML module keeps its explicit LGPL-2.1+ entry (a child's <licenses> replaces the parent's); the seven modules that had no license (renderer, bridges/renderer, record-files, printing, remote-renderer parent/transport/adapter) now inherit the root's Apache-2.0, matching the repository LICENSE. - compiler: build-parent adds <source>21</source><target>21</target> to the compiler plugin; identical to the modules' maven.compiler.release 21; the Java 8 vendor module pins <source>8</source><target>8</target> explicitly next to maven.compiler.release 8 (testRelease 21 unchanged). - dependency management: build-parent imports qqq-bom-pom 4.0.0 (jackson 2.21.5, qqq 4.0.0, ...) which the parentless modules never had. record-files and printing now import qqq-bom-pom ${qqq.version} (as foundation and bridges/scripting already do), so their managed versions equal what qqq-backend-core RC.21 declares; renderer, bridges/renderer and remote-renderer-parent import jackson-bom 2.22.4 so jackson-core/annotations stay aligned with their explicit jackson-databind 2.22.4. - guardrails: build-parent 2.1.1 adds the qbit-guardrails test dependency, surefire dependenciesToScan and enforcer executions. foundation keeps them (enforcer.skip false); the other modules keep the previous behavior (enforcer.skip true, dependenciesToScan reset); the extra test-scope qbit-guardrails dependency and the snapshots-only central-portal-snapshots repository are inherited metadata. - url/scm: the root states build-parent's url/scm so the modules' derived metadata stays the same. The vendor's complete-source ZIP now ships parent/pom.xml (a copy of the reactor POM; module/pom.xml differs from the repository POM only in its relativePath, ../parent/pom.xml inside the archive), inputs.sha256 and the verify/build scripts follow, the README documents it, and renderer/Dockerfile copies the reactor POM from a named BuildKit context. Not built or tested: model introspection only. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-05 17:10:19 -06:00
3 people	ee782b7d6e	chore: preserve unfinished document generation source and status ... Checkpoint implementation at user-requested stop; document known failures and incomplete release qualification. Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: GPT-6 Codex <noreply@openai.com>	2026-11-04 10:45:09 -06:00