Replace the undeclared `mbake` validation command

[coderabbitai]

Summary

Replace the undeclared mbake validation command in templated repository documentation and parent repository documentation.

Rationale

Documentation validation must use reproducible, project-provisioned commands. The repository layout identifies Makefile as the public validation entrypoint, but the supplied Makefile exposes no mbake target or installation/provisioning path.

Required changes

• Replace mbake invocations with an appropriate declared make target; or
• Document and provision mbake as a supported project command, including its installation path and expected validation entrypoint.
• Keep validation guidance reproducible from a clean contributor environment.
• Update related documentation and validation coverage as needed.

Affected areas

• Documentation or scripts that invoke mbake
• Makefile validation entrypoints and any associated contributor guidance

Acceptance criteria

• No documentation validation workflow invokes an undeclared or unprovisioned mbake command.
• The documented command is available through a declared make target, or mbake is explicitly documented and provisioned.
• Repository validation instructions remain reproducible using the documented project entrypoints.

Triage

[type:docstyle]

Requested by @leynos.

Backlinks:

• Originating PR: (adr-0001) Parse one GNU Makefile into versioned JSON facts makeutil#6
• Originating comment: (adr-0001) Parse one GNU Makefile into versioned JSON facts makeutil#6 (comment)

[coderabbitai]

🔗 Related PRs

leynos/theoremc#44 - Run Rust tests with cargo-nextest [closed]
leynos/beatcue#16 - Refresh repository documentation guidance [closed]
leynos/lading#125 - Pin lockfile discovery and validation I/O decisions (#83) [merged]
leynos/lading#176 - Adopt plaintext fences for prose output (#161) [merged]
leynos/wildside#433 - Require installed Nixie and Merman tools [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!