wiki_submit

For every coordinated full-rebuild review action, read [`REVIEW_CONTRACT.md`](REVIEW_CONTRACT.md) completely first. It defines the required handoffs, phase states, outputs, and completion criteria for both Writer and Reviewer. # Wiki Submit Skill This skill provides a simple command-line tool to submit wiki documentation pages to the Wegent backend. ## Page paths A page is identified by its `--path`: `index`, `architecture/backend`, `modules/indexing`. Lowercase, `/`-separated, no file extension, at most 4 folders deep. Two paths may not differ only by case — the projection matches them case-insensitively, so they would collapse into one page. **Keep a path stable across runs.** It is what lets an unchanged page keep its place, its links and its search index. Changing it republishes the page as a deletion plus an insertion, so reword titles freely and move paths rarely. Send a page's **complete content** every time. There is no patch format; what you send replaces the page. A section that holds pages needs a substantive page of its own. If you submit `architecture/backend`, also submit `architecture` with an overview of that section; for `architecture/backend/api`, submit both `architecture` and `architecture/backend`. This is a publish requirement: `complete` refuses a version with any ancestor path that is not a page. Submit overview pages first where practical, and always before running `complete`. Write `index` as the wiki overview. Create a slash-separated sectio...