fix(canvas): render base.text tag:none as bare text to match published DOM

[DavidBabinec]

What

In the visual editor canvas, a base.text node with tag: none was wrapped in a <span>. The publisher renders tag: none as bare text with no element (src/modules/base/text/index.ts → { html: text }). That divergence let descendant selectors match the phantom span in the builder while leaving the published page untouched.

Concretely, on the 404 template the number is one .ist-404__num container with three base.text children — two tag: none 4s and a tag: span 0 — plus an ambient rule .ist-404__num span { color: var(--ist-accent) }. In the canvas all three were spans, so the rule painted the 4s orange; on the published page the 4s are bare text, so they stayed black. The builder lied about the result.

Fix

The canvas now renders tag: none as bare text + <br> breaks (a fragment, no host element), exactly like the publisher — so the canvas DOM equals the published DOM. This is the same canvas-equals-published principle that drove removing the per-node wrapper <div>.

• TextEditor.tsx: tag: none display path renders a BareText fragment instead of a <span> wrapper. The inline-edit branch still hosts a <span> for an active session (unreachable from the canvas for tag: none — there is no element to double-click).

Trade-off (intentional, agreed with author)

A tag: none node owns no element, so it has no in-canvas selection ring / hover / inline-edit — it is selected via the Layers panel and edited via the Properties → Text field. This is the honest reflection of "no element": that text has no box on the published page either. A future, separate PR could add Range-based selection to restore direct manipulation without a phantom element.

User/developer impact

• Users: the builder now shows the same text colors (and any other descendant-selector styling) as the published site for tag: none text.
• Developers: canvas/publish DOM parity holds for tag: none.

Verification

• bun run build ✓
• bun run lint ✓
• bun test ✓ — 5437 pass, 0 fail (added 3 canvas-render tests in base-modules.test.ts)
• Live in the editor (isolated dev server against a DB containing the 404 template): the 4s render black and the 0 orange, matching the front end. .ist-404__num DOM is 4<span data-node-id=…>0</span>4 (childNodes ["#text:4","SPAN","#text:4"]), no console errors.

Note: the pre-push hook flags a react-doctor/no-danger warning on the non-none display path's dangerouslySetInnerHTML — that is the pre-existing escaped-text + <br> pattern already on main (only relocated by this diff), not a new regression.

🤖 Generated with Claude Code