Fix run-together title and summary text on the Docs surface

[alexeygrigorev]

Follow-up from PM acceptance of #190. Pre-existing defect, unrelated to that
diff (#190 touched no frontend/ or CSS file); it was simply made visible by
the first screenshot of the Docs surface with a populated corpus.

Observed

Screenshot: .tmp/screenshots/issue-190/worktree-processes.png (identical copy
at clean-worktree-processes.png), captured at #/processes.

Bold labels and their following text render with no separator, producing
run-together strings:

• Processes support workUse internal Process Docs from Task or Card context first.
• No findings match filtersChange filters to inspect other process quality findings.
• Synthetic Characterization ScheduleSynthetic reference used only by browser characterization tests. (the document tile: title + summary)
• DataOps V1 GoalPlanning referenceProject PlanPlanning referencePortal AnalysisPlanning referenceMerge PlanPlanning reference (the four static
  planning-reference links run together into one wrapped paragraph)

Likely cause

renderOperationsReference() in
frontend/src/surfaces/operations-overview.js (~line 499) builds each tile as:

const title = document.createElement("strong");
const summary = document.createElement("span");
el.append(title, summary);

.ops-reference-link has no CSS rule anywhere in frontend/ (grep for
ops-reference-link returns only that one JS line), so strong and span are
adjacent inline boxes with no whitespace, gap, or line break between them. The
honest-state and quality-panel strings above look like the same
label-plus-description pattern.

Why it matters

This is a real operator-facing readability defect on a canonical surface, not a
test artifact: the same rendering applies to real process documents, where every
tile will read <Doc Title><Doc summary…> with no break. Document titles are
the primary scan target on this surface.

Things to settle during grooming

• Whether the fix is CSS (make .ops-reference-link a block/flex stack with the
  title on its own line) or markup, and whether it belongs inside the design
  system convergence work in Converge canonical DataOps surfaces on one operator design system #162 or as an independent bug fix first.
• Whether the same missing-rule problem affects other ops-* classes on the
  surface (the honest-state and quality-empty strings suggest yes).
• Confirm the four static "Planning reference" links should remain a link list
  rather than tiles.

Verification hints

• Screenshot #/processes before and after under .tmp/screenshots/, with a
  populated content root, and read them for run-together text, overlap, and
  horizontal overflow.
• backend/e2e/frontend-module-characterization.spec.js already renders a
  synthetic fixture document on this surface and already asserts no horizontal
  overflow, so it is a convenient place to prove the tile layout.

Out of scope

• Backend route behavior and the Fix deterministic /docs 404 failures in frontend module characterization #190 content-root contract.
• Restoring or checking out the real content/ corpus; keep using synthetic
  fixtures.

[alexeygrigorev]

Additional evidence from PM acceptance of #192, confirming this is the renderHonestState() strong + span pattern and not only renderOperationsReference().

Screenshot: .tmp/screenshots/issue-192/processes-outage.png (#/processes against a missing docs content root, 1440x900). It shows two more run-together strings on the same surface:

• Processes support workUse internal Process Docs from Task or Card context first. (as already listed here)
• Process quality report unavailableDocs content root is unavailable: /home/alexey/.../content (set DTC_CACHE_ROOT to …) — the honest state for a failed quality snapshot, where the run-together break lands in the middle of an operator-facing error message.
• The four Planning reference links again run together into one wrapped paragraph.

Note for whoever fixes this: the new .ops-docs-state component added by #192 renders the same strong + span pair correctly, because it sets display: grid on the container. Compare the two states in that screenshot — the new outage box stacks title / message / guidance on separate lines, the older honest states directly below it do not. That is a working reference for the fix and suggests the missing rule is per-class rather than in renderHonestState() itself. #192 changed no copy here and is not the cause.