From 0be49e87a93d506d43832f1f3799150333729173 Mon Sep 17 00:00:00 2001 From: Nikolai Emil Damm Date: Mon, 16 Nov 2026 03:01:39 +0100 Subject: [PATCH 1/2] feat(legal): show the portal's privacy section in production The maintainer chose to switch the portal on, invite-only (business-site#302). The production-template packager now sets FEATURE_PORTAL_PRIVACY=true, so the release that starts the portal also publishes the privacy notice's portal section: accounts, optional GitHub sign-in, SES mail, the sign-in cookies and retention. Other builds keep it off. scripts/vat-activation.test.mjs now pins the production value to true, and its mutation controls cover removing, withdrawing or garbling that pin. Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 6 +++--- scripts/package-runtime.sh | 2 +- scripts/vat-activation.test.mjs | 7 ++++--- 3 files changed, 8 insertions(+), 7 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 66e26855..161e6318 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -154,9 +154,9 @@ production-template packager explicitly enables the footer, email route and requ whose address the runtime reads from its private projected file. The same release enables the EN/DA privacy notice and customer terms (`/privacy/`, `/terms/`), whose copy lives in `src/components/business/legal-copy.ts`. The privacy notice's portal -section stays behind the default-off `FEATURE_PORTAL_PRIVACY` until the portal is activated; -the activation flips its `false` pin in `scripts/package-runtime.sh` and -`scripts/vat-activation.test.mjs`. They link to the address rather +section is behind `FEATURE_PORTAL_PRIVACY`, off by default and on in the production-template +packager since the portal's invite-only activation (#302); `scripts/vat-activation.test.mjs` +pins it there. They link to the address rather than repeat it. Change them with any change to hosting, providers, retention, prices or terms (#19); never call the business compliant. Publish the maintainer's fixed VAT-inclusive prices (15 November 2026): DKK 6,000 plus optional diff --git a/scripts/package-runtime.sh b/scripts/package-runtime.sh index d0dac74f..5382c1f0 100644 --- a/scripts/package-runtime.sh +++ b/scripts/package-runtime.sh @@ -29,7 +29,7 @@ build_env+=("PUBLIC_CONTENT_PROFILE=$profile" "FEATURE_COMPANY_IDENTITY=false" " if [[ "$profile" == production-template ]]; then inputs="$(mktemp -d "$output/public-inputs.XXXXXX")" bash scripts/refresh-public-stars.sh "$inputs/stars.json" - build_env+=("PUBLIC_CONTENT_PROFILE=production-template" "FEATURE_COMPANY_IDENTITY=true" "PUBLIC_STARS_SNAPSHOT=$PWD/$inputs/stars.json") + build_env+=("PUBLIC_CONTENT_PROFILE=production-template" "FEATURE_COMPANY_IDENTITY=true" "FEATURE_PORTAL_PRIVACY=true" "PUBLIC_STARS_SNAPSHOT=$PWD/$inputs/stars.json") fi "${build_env[@]}" npm run build bash scripts/check-portal-artifacts.sh dist diff --git a/scripts/vat-activation.test.mjs b/scripts/vat-activation.test.mjs index 49a86db7..ba6f6c68 100644 --- a/scripts/vat-activation.test.mjs +++ b/scripts/vat-activation.test.mjs @@ -17,7 +17,7 @@ const currentRuntimeCI = workflow => { return packages.length === 1 && [workflow.env, runtimeJob(workflow)?.env, packages[0].env] .every(env => presentation.every(flag => !Object.hasOwn(env ?? {}, flag))); }; -const current = state => state.FEATURE_COMPANY_IDENTITY === 'true' && state.FEATURE_OFFER_COPY === 'false' && state.FEATURE_PORTAL_PRIVACY === 'false' && +const current = state => state.FEATURE_COMPANY_IDENTITY === 'true' && state.FEATURE_OFFER_COPY === 'false' && state.FEATURE_PORTAL_PRIVACY === 'true' && !Object.hasOwn(state, 'FEATURE_VAT_PRICES') && !Object.hasOwn(state, 'FEATURE_CUSTOMER_SCOPE'); const packagerSource = readFileSync('scripts/package-runtime.sh', 'utf8'); /** Run the actual (or a changed) packager; the build double records every FEATURE_ setting it receives. */ @@ -150,8 +150,9 @@ for (const [mode, from, to] of [ ['offer removed', ' "FEATURE_OFFER_COPY=false"', ''], ['revised offer', '"FEATURE_OFFER_COPY=false"', '"FEATURE_OFFER_COPY=true"'], ['ambiguous offer', '"FEATURE_OFFER_COPY=false"', '"FEATURE_OFFER_COPY=ambiguous"'], - ['portal privacy unpinned', ' "FEATURE_PORTAL_PRIVACY=false"', ''], - ['portal privacy released', '"FEATURE_PORTAL_PRIVACY=false"', '"FEATURE_PORTAL_PRIVACY=true"'], + ['portal privacy unpinned', ' "FEATURE_PORTAL_PRIVACY=true"', ''], + ['portal privacy withdrawn', '"FEATURE_PORTAL_PRIVACY=true"', '"FEATURE_PORTAL_PRIVACY=false"'], + ['ambiguous portal privacy', '"FEATURE_PORTAL_PRIVACY=true"', '"FEATURE_PORTAL_PRIVACY=ambiguous"'], ['legacy VAT', production, `${production} "FEATURE_VAT_PRICES=false"`], ['stale audience', production, `${production} "FEATURE_CUSTOMER_SCOPE=false"`], ]) { From 9c42e72168511428c77a7ee8577983ff5538a936 Mon Sep 17 00:00:00 2001 From: Nikolai Emil Damm Date: Mon, 16 Nov 2026 03:13:53 +0100 Subject: [PATCH 2/2] docs(agents): state the portal's invite-only sign-in consistently CodeRabbit: AGENTS.md said both that production authentication and social logins stay off and that the portal section is on since activation. It now says what this release does. Sign-in is switched on, invite-only, by the platform's portal settings (platform#6389), while intake and payments stay off. Customers sign in with password plus MFA or, optionally, GitHub through ZITADEL. The privacy section ships together with that switch-on. Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 161e6318..2882e682 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -43,10 +43,12 @@ review/CI/user-path evidence. Never use an admin merge bypass or request Copilot - `docs/README.md` contains the editorial, localization, catalogue and feature-flag standards. - `server/` contains the default-off Go/PostgreSQL browser identity boundary. Read `server/AGENTS.md` before changing it. The platform runtime ships its handlers default-off; - production authentication, customer intake and payments remain disabled. - Customer identity source preparation uses dedicated customer Dex and self-hosted + production sign-in is switched on, invite-only, by the platform's `business-site-runtime` + portal settings (#302, devantler-tech/platform#6389), while customer intake and payments + remain disabled. Customer identity uses dedicated customer Dex and self-hosted ZITADEL; read `server/CUSTOMER-IDENTITY.md`. The explicit offline preparer has no - deployment, user-provisioning or portal-activation authority. Social logins are deferred. + deployment, user-provisioning or portal-activation authority. Customers sign in with a + ZITADEL password plus MFA or, optionally, GitHub through ZITADEL; other social logins are deferred. - ZITADEL is never built, patched or redistributed here. When the portal is activated, #305 runs the official upstream image unmodified, pinned by digest and branded only through its native Label Policy. Upstream does not sign its images, so no signature is verified. Read ADR 0031. @@ -155,8 +157,9 @@ whose address the runtime reads from its private projected file. The same release enables the EN/DA privacy notice and customer terms (`/privacy/`, `/terms/`), whose copy lives in `src/components/business/legal-copy.ts`. The privacy notice's portal section is behind `FEATURE_PORTAL_PRIVACY`, off by default and on in the production-template -packager since the portal's invite-only activation (#302); `scripts/vat-activation.test.mjs` -pins it there. They link to the address rather +packager. That release goes out together with the platform switching portal sign-in on, +invite-only (#302, devantler-tech/platform#6389), so the notice and the processing it describes +start together; `scripts/vat-activation.test.mjs` pins it there. They link to the address rather than repeat it. Change them with any change to hosting, providers, retention, prices or terms (#19); never call the business compliant. Publish the maintainer's fixed VAT-inclusive prices (15 November 2026): DKK 6,000 plus optional