Регекс:
/<details>\s*<summary>(?:|Summary)<\/summary>\s*<chapter>(?:月之序曲|Moonlit Prelude)\s*Ch\.\s*(\d+)\s*(.*?)<\/chapter>\s*<time>([^<]*?)<\/time>\s*<scene>([^<]*?)<\/scene>\s*<recap>\s*([\s\S]*?)\s*<\/recap>\s*<\/details>/gi;

Промт для лобомита:
<summary_instruction>
When you have finished writing the narrative part of your answer, YOU MUST summarize it at the end.
Wrap the summary using <details><summary>Summary</summary></details>.

[System Instruction: Generate an instant scene recap]
Strictly produce an immediate scene profile in the XML format below, following these principles:

1. Narrative tone:
Write like a sharp observer keeping a log—warm, natural, and human.
Avoid cold, mechanical “report” language (no numeric measurement-style phrasing).
2. Decentralized power description:
- Do NOT deliver definitive conclusions or labels.
- Keep power dynamics dynamic and neutral. Even in Dom/Sub scenes, record actions, not fixed “statuses”.
3. NSFW handling:
If sexual content occurs, simplify it. You do NOT need to restate explicit sexual organ actions or sensitive terms.
4. No forced “elevation”:
Do not end with a moral or concluding statement. Only record that events pause here.

[Output Format]
<details><summary>Summary</summary>
  <chapter>Moonlit Prelude Ch.{{index starting from 1}} {{short custom title}}</chapter>
  <time>yyyy-mm-dd hh:mm</time>
  <scene>{{current scene}}</scene>
  <recap>
    {{Naturally recap what just happened in plain, novel-outline style.
    - Normal scenes: ~80 words.
    - NSFW scenes: ~40 words.
    Keep it concise and fluent—like a fiction outline, not an experiment report.
    Avoid decisive wording such as "completely...", "ultimately...", "represents...", or any final judgments.}}
  </recap>
</details>
</summary_instruction>