Fix AI narrative insertion formatting

Objective

• When inspectors use AI narrative to populate title and description fields in Report Writer, the inserted text should land with clean, predictable formatting—no awkward line breaks, stray bullets, or markup that fights the field’s intended style.

Background

• May 15 feature sync (Ben): Formatting / insertion is awkward after AI applies narrative into title and description—this ticket is about presentation and insertion mechanics, not judging the quality of the generated prose itself.
• Ben had specific notes in the meeting; capture any repro steps or examples in team channels if they were not pasted here.

Scope

Report Writer app (primary)

• Title vs description widgets (plain text vs rich text, character limits, newline policy)—Decision needed per-field rules when AI returns multi-sentence or markdown-ish output.
• Insert action semantics: replace vs append, cursor position, and undo—Decision needed product contract.

Backend (if any)

• If narrative is post-processed server-side before the client inserts it, verify normalization does not introduce extra escapes—Decision needed once ATT-1672 lands the authoritative schema.

Codebase audit note

• attik-frontend, attik-backend, and attik-mobile snapshots searched for obvious Report Writer authoring paths did not expose a named module—treat the Report Writer repo/branch as the implementation source of truth once linked.

References

• ATT-1672 (backend schema / API ownership).
• Related content workflows elsewhere in Attik products should be cited only if designers want consistent AI-insert UX patterns.