bug: E2E tests failing — editor contenteditable element not found on production

[zacharias-ona]

Description

15 of 27 E2E tests fail when run against the live site (https://memo.software-factory.dev). All failures share the same root cause: the [contenteditable="true"] editor element is not found on page routes.

Detected during post-merge verification of PR #83, but PR #83 changed only automation YAML, documentation, and issue templates — no application code. These are pre-existing failures.

Affected test suites

• e2e/editor-drag.spec.ts — 2 of 3 tests fail (drag handle, reorder blocks)
• e2e/editor-link.spec.ts — 3 of 3 tests fail (link creation, link editor, link removal)
• e2e/editor-slash-commands.spec.ts — 4 of 4 tests fail (slash menu, filtering, heading insert, keyboard nav)
• e2e/editor-toolbar.spec.ts — 4 of 4 tests fail (toolbar appearance, bold toggle, collapse, Cmd+B)
• e2e/page-crud.spec.ts — 2 of 4 tests fail (create page, delete page)

Common error pattern

Error: expect(locator).toBeVisible() failed
Locator: locator('[contenteditable="true"]')
Expected: visible
Timeout: 10000ms
Error: element(s) not found

Acceptance Criteria

• All 15 currently failing E2E tests pass against the live site
• Editor contenteditable element renders on page routes after authentication
• Page CRUD operations (create, delete) work in the sidebar
• pnpm lint && pnpm typecheck && pnpm test pass

Technical Notes

• The ad-hoc smoke tests (landing page, sign-in, health endpoint, authenticated workspace load) all pass — the app is functional for basic flows
• The editor element specifically is not rendering, suggesting a client-side component issue on page routes
• Tests that don't require the editor (auth, workspace switcher) pass fine (8 of 27)
• 4 tests were skipped (dependent on earlier failing tests in the same suite)