feat(help): add init help topic and route madt_init to cli-setup #396

Merged
hexajon merged 1 commit from issue-371-init-help-topic into main 2026-08-17 08:18:06 +00:00
Owner

Summary

madt_init was undiscoverable: help topic="init" returned Unknown, and the tool surfaced only in passing under madt_remote_add.

This adds a hand-written init help topic that documents madt_init end to end (turn an existing directory into a new repo and push it), with bootstrap and new-repo aliases so an obvious guess finds it. It moves the madt_init MCP tool from the cli-workflows group to cli-setup, where a reader looks for how to bootstrap a repo, and cross-references it from the repos create action. Reference docs are regenerated.

Gate green, including mcp-conformance. A regression test guards the new aliases.

Closes #371

## Summary madt_init was undiscoverable: `help topic="init"` returned Unknown, and the tool surfaced only in passing under madt_remote_add. This adds a hand-written `init` help topic that documents madt_init end to end (turn an existing directory into a new repo and push it), with `bootstrap` and `new-repo` aliases so an obvious guess finds it. It moves the madt_init MCP tool from the cli-workflows group to cli-setup, where a reader looks for how to bootstrap a repo, and cross-references it from the repos create action. Reference docs are regenerated. Gate green, including mcp-conformance. A regression test guards the new aliases. Closes #371
feat(help): add init help topic and route madt_init to cli-setup
Some checks failed
drift / govulncheck (pull_request) Has been skipped
drift / surface-diff (pull_request) Successful in 1m19s
drift / forgejo-smoke (pull_request) Has been skipped
ci / mcp-conformance (pull_request) Successful in 2m8s
ci / mcp-conformance (push) Successful in 29s
drift / govulncheck (push) Has been skipped
drift / surface-diff (push) Successful in 14s
drift / forgejo-smoke (push) Has been skipped
ci / gate (push) Has been cancelled
ci / gate (pull_request) Successful in 25m49s
5736e90309
madt_init was undiscoverable: no `init` help topic, and it surfaced only
in passing under madt_remote_add. Add a hand-written `init` topic that
documents madt_init end to end (turn an existing directory into a new
repo and push it), plus `bootstrap` and `new-repo` aliases so an obvious
guess finds it. Move the madt_init MCP tool from the cli-workflows group
to cli-setup, and cross-reference it from the repos create action.
Regenerate the reference docs.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea!396
No description provided.