ixf-docs-writerlisted

# ixf Docs Writer Use `ixf docs publish` through the local Toolbox CLI for new documents. The command is API-only and create-only for a new docx document. It does not modify existing docx content. Use `ixf docs update` for existing docx updates. The supported mode is `replace_body`: it keeps the original URL, permissions, and location, but replaces the body blocks. It rejects complex existing content by default; use `--allow-complex-replace` only after explicit destructive approval. ## Runtime Boundary Go `ixf` only. Do not call `ixfdoc` or `ixfwrite`. Do not use Python fallback, Python-compatible readers, or Python-compatible writers. ## Workflow 1. For new docx publishing, confirm the Markdown file and destination URL or parent location. 2. Run a publish dry run first: `ixf docs publish <file.md> --base-url https://tenant.example.test --dry-run` 3. Review the planned title, create-only target, and required text checks with the user. 4. Apply only after explicit approval: `ixf docs publish <file.md> --base-url https://tenant.example.test --apply` 5. For existing docx update requests, run update dry-run first: `ixf docs update <file.md> --url https://tenant.example.test/docx/example --dry-run` 6. Apply existing docx updates only after explicit approval: `ixf docs update <file.md> --url https://tenant.example.test/docx/example --apply` 7. If dry-run reports complex blocks, do not apply unless the user explicitly approves losing those blocks: `ixf docs upda