5 Commits

Include renames

Author	SHA1	Message	Date
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 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.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
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