Make everyday workflows discoverable within Use Mecatl #2393

Reader need

"I know what I want to do, but I do not know which Mecatl feature or documentation page I need."

Proposed direction

Create an outcome-oriented Workflows entry within Use Mecatl. Decide whether an index linking current owners, a sidebar subsection, or both gives the smallest useful improvement. A new peer top-level section is not the starting direction: these scenarios serve the existing Use Mecatl audience.

Scope

Cover model choices/routing, planning and implementation, delegation, memory maintenance, long-task continuity, recurring tasks, and reusable guidance/specialists. Keep install/connect orientation easy to find. Existing pages can participate through links; do not move or duplicate content just to fill a directory.

Acceptance criteria

• Readers can find tasks by outcome from the Use Mecatl landing page and the autogenerated sidebar.
• The entry distinguishes first-run/setup tasks, everyday workflows, and customization/reference sufficiently to avoid one growing undifferentiated list.
• Each task links to one owning page or section, including improved existing capability pages when appropriate.
• Shared behavior remains canonical in Capabilities and service administration remains in Deploy and operate.
• Any new directory has the required entry page and category metadata; no manual sidebar is introduced.
• Published URLs are preserved. Necessary moves follow website/AGENTS.md, including redirects and live verification where required.
• Introduce navigation incrementally as content becomes available; avoid broken links or placeholder pages for unimplemented guides.
• Record the rationale for the chosen grouping in the PR so a later separate top-level journey is based on audience need rather than page count.

Tracking

Part of #2386. Follow the parent issue's shared ownership and validation criteria.