moxie.propose_doc_update
Propose a documentation file to add or update as part of YOUR current change. Records a new proposal each call (not idempotent) and does NOT modify your repository or open a PR - Moxie Docs resolves the target path and returns the path + Markdown for YOU to write into your working branch, so the docs land in the SAME PR as the code. Returns the resolved target path and the content to write. Provide either targetPath or baseSlug.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Short human title for the documentation update. | |
| reason | No | Why this doc is being added or changed. | |
| baseSlug | No | Slug of an existing generated doc to update instead of supplying targetPath. | |
| markdown | Yes | The documentation content (Markdown) to write to the target file. | |
| repository | No | The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer. | |
| targetPath | No | Repository-relative path to write the doc to (e.g., docs/billing.md). Omit to resolve from baseSlug. | |
| sourcePaths | No | Code paths this doc documents, for provenance. |