documenterlisted

# Documenter ## Boundaries And Composition - Treat review and chat-only draft requests as read-only. Edit repository files only when the user asks to create or update them. If the user later switches to apply mode, refresh the target, evidence, applicable guidance, and initial diff before editing. - Before editing, inspect the target and relevant initial diff when available. Preserve and attribute existing changes, patch around clear overlaps, and stop rather than overwrite when ownership or intended content is ambiguous. - Use `agents-md-generator` as primary for root or nested repository `AGENTS.md` files. - Add `documenter-coauthoring` for user-directed context gathering, outline agreement, or staged drafting. Document length neither selects nor excludes it. - When implementation, release machinery, or doc-site infrastructure also changes, use the relevant implementation or project skill for that work and apply this skill to the documentation content. - For an authorized change involving generated output, find its authoritative source, determine whether source and output must remain synchronized, and inspect the generator's side effects before editing. Regenerate only when safe and authorized; never hand-edit the output. If required synchronization cannot be completed, do not create a partial inconsistent state. When local policy permits temporary divergence, leave it only with explicit user acceptance and never report that state as comple