[OKAN-SOFTWARE]

Whitespace-heavy text within the 50,000-character limit could cause excessive regex backtracking. A pending draft request could also restore old results after the source or mode changed, and topic deduplication dropped provider responsibilities when client responsibilities were already present.

This change:

• Checks the question ending separately and matches only the supported prefix, avoiding overlapping whitespace/question captures.
• Discards draft responses and errors after source edits, mode changes, example loading, or successful text imports, including edits that restore the original source.
• Tracks client and provider responsibility topics separately while preserving duplicate filtering for the same party.
• Adds regression tests and an Unreleased changelog entry.

Validation:

• mvn -B -ntp verify: 38 Java tests passed.
• node --test src/test/js/*.test.cjs: 12 JavaScript tests passed.
• The new tests reproduced four Java failures and four JavaScript failures against the original code before the fixes.
• Additional DOM checks passed for draft editing, reordering, search, imports, exports, HTML escaping, and stale-result handling.
• Packaged-app HTTP checks returned both client and provider FAQs. The whitespace-heavy probe took approximately 14–15 ms on both endpoints after the fix; the original preview request took 7.8 seconds in the same local review environment. These are individual local measurements, not a load benchmark.

Public-hosting controls such as overall JSON body limits, rate limiting, response security headers, and isolated document parsing remain follow-up work.