Confirmation Cards and Safe Writes

When a request would modify prose, titles, outlines, settings, or chapters, the Agent should present a structured candidate and a relevant action such as write, append, replace selection, save outline, create record, accept, skip, rewrite, or comment.

The card should identify the target, before/after difference, affected scope, write conditions, sources, review state, and undo path. If a request could mean either discussion or writing, clarify the intent first.

If the action is missing, verify that the prompt names both target and operation, wait for the run, reload the saved conversation, retry, then send a short explicit instruction. Keep the screenshot, task time, and model name if it still fails. Avoid manually replacing a whole chapter, which loses the diff and audit trail.