Move the CMS CORE feature used by KOF22 into the canonical development line: entities and child lists, feature permissions and home rendering, schema installation, and catalog verification for a DML-only PostgreSQL runtime identity.
This reconciles the feature work in #3 plus the later PostgreSQL catalog verification while preserving the newer upstream CI configuration. The build uses the published QQQ 4.1.0-RC.21 BOM. Existing PRs are left intact until the integration is merged.
Validation: production and test sources compiled against published QQQ JARs (test-compile BUILD SUCCESS; no local test execution). Upstream repository CI is the test gate. The published artifact will replace KOF22's embedded CMS source.
Move the CMS CORE feature used by KOF22 into the canonical development line: entities and child lists, feature permissions and home rendering, schema installation, and catalog verification for a DML-only PostgreSQL runtime identity.
This reconciles the feature work in #3 plus the later PostgreSQL catalog verification while preserving the newer upstream CI configuration. The build uses the published QQQ 4.1.0-RC.21 BOM. Existing PRs are left intact until the integration is merged.
Validation: production and test sources compiled against published QQQ JARs (test-compile BUILD SUCCESS; no local test execution). Upstream repository CI is the test gate. The published artifact will replace KOF22's embedded CMS source.
Implement the CORE feature area as standard QQQ tables: site, domain,
redirect, redirect type, page, page type, page section, page section type,
snippet, menu and menu item. Add the CMS app with Sites, Pages and
Navigation homes, CmsFeature flags with dependency validation, per-table
permissions with CmsRole bundles and openReads, a startup schema check
(FAIL_FAST, DEGRADED, SKIP), a prefix-parameterized Liquibase changelog and
the Postgres DDL.
Add unit tests, Postgres-backed Testcontainers install and runtime-identity
tests, and a local demo server used to produce the docs screenshots.
Build against the published QQQ 4.1 BOM (4.1.0-RC.21), add the test-scope
Postgres, Javalin, frontend-next and Testcontainers dependencies, and
enforce checkstyle at validate.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Move the CMS CORE feature used by KOF22 into the canonical development line: entities and child lists, feature permissions and home rendering, schema installation, and catalog verification for a DML-only PostgreSQL runtime identity.
This reconciles the feature work in #3 plus the later PostgreSQL catalog verification while preserving the newer upstream CI configuration. The build uses the published QQQ 4.1.0-RC.21 BOM. Existing PRs are left intact until the integration is merged.
Validation: production and test sources compiled against published QQQ JARs (test-compile BUILD SUCCESS; no local test execution). Upstream repository CI is the test gate. The published artifact will replace KOF22's embedded CMS source.