docs: group the madtea init CLI command under Setup, matching the madt_init MCP tool #461

Merged

hexajon merged 1 commit from issue-399-init-docs-group into main 2026-08-27 04:45:04 +00:00

Conversation 0 Commits 1 Files changed 4 +19 -19

hexajon commented 2026-08-27 04:45:00 +00:00

Owner

Copy link

Summary

#371 moved the madt_init MCP tool to the Setup group (cli-setup.md) but the madtea init CLI command stayed under Workflows (cli-workflows.md), so the two surfaces of the same operation documented on different reference pages. Move the CLI init prefix into the Setup domain so both surfaces render together on cli-setup.md, where a reader looks for how to bootstrap a repo. Also correct the domain summaries: Setup now names repository initialization, and Workflows drops "branch initialization" (which described init, a repo-bootstrap command, not a branch operation). Regenerated docs/reference/ accordingly.

Closes #399

## Summary #371 moved the madt_init MCP tool to the Setup group (cli-setup.md) but the `madtea init` CLI command stayed under Workflows (cli-workflows.md), so the two surfaces of the same operation documented on different reference pages. Move the CLI `init` prefix into the Setup domain so both surfaces render together on cli-setup.md, where a reader looks for how to bootstrap a repo. Also correct the domain summaries: Setup now names repository initialization, and Workflows drops "branch initialization" (which described init, a repo-bootstrap command, not a branch operation). Regenerated docs/reference/ accordingly. Closes #399

hexajon added 1 commit 2026-08-27 04:45:00 +00:00

docs: group the madtea init CLI command under Setup, matching the madt_init MCP tool (#399) 9357db9f57

hexajon merged commit 9357db9f57 into main 2026-08-27 04:45:04 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

breaking

Breaking change - flag for release notes

  

bug

Something is not working

  

documentation

Documentation only

  

enhancement

New feature

  

epic

Tracking epic with dependency children

  

good first issue

Interested in contributing? Get started here.

  

help wanted

Maintainer would welcome outside help

  

refactoring

Code restructuring without behavior changes

  

resolution/duplicate

Closed as duplicate of another issue

  

resolution/invalid

Closed as invalid or not reproducible

  

resolution/wontfix

Closed as won't fix

  

security

Security issue or hardening

  

severity/critical

Security severity: critical

  

severity/high

Security severity: high

  

severity/low

Security severity: low

  

severity/medium

Security severity: medium

  

status/abandoned

Someone started, then walked away - up for grabs

  

status/blocked

Blocked by another issue or an external dependency

  

status/needs-decision

Waiting on a maintainer decision; workable once decided

  

status/needs-info

Waiting on reporter / more information before work can start

  

status/needs-verification

Done except verification in a live interactive session

  

testing

Test suite / CI infrastructure work

  

upstream

Related to an upstream repository, already reported there

No labels

breaking

bug

documentation

enhancement

epic

good first issue

help wanted

refactoring

resolution/duplicate

resolution/invalid

resolution/wontfix

security

severity/critical

severity/high

severity/low

severity/medium

status/abandoned

status/blocked

status/needs-decision

status/needs-info

status/needs-verification

testing

upstream

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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!461

No description provided.