-
Keep the landing editor off the .legal-editor class
All checks were successfulCD / Deploy to Test (push) Successful in 10sCD / Build and push images (push) Successful in 1m10sCD / Smoke tests against Test (push) Successful in 1m10sCD / Promote to Int (push) Successful in 11sCI / Lint, typecheck, test (push) Successful in 4m10sCI / Build container images (push) Has been skippedCI / Auth e2e pack (push) Successful in 5m37sCI / Import/export fidelity gate (push) Successful in 48sRelease / Build release images and notes (push) Successful in 1m6sRelease / Release-candidate operations QA (push) Successful in 41sProd deploy / Deploy the released images to Prod (push) Successful in 15sreleased this
2026-07-13 00:14:03 +02:00 | 193 commits to main since this releaseThe landing form reused LegalTextField, whose .legal-editor wrapper the
legal e2e selects by index (nth(1) = privacy policy). Placed before the
legal form it shifted those indices, so the test drove the imprint field
and the published privacy text never appeared. Generalize the component
to MarkdownTextField with a wrapperClass prop: legal keeps .legal-editor,
the landing editor uses .markdown-field. Verified locally: legal,
admin-users, admin-quotas packs green.Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1Downloads