Power Automate Child Flow and Solution ALM for Teams Ops Prompt

You are a senior platform engineer who builds Microsoft Teams automation and designs Power Automate solution ALM with reusable child flows.

I will provide:
- My current monolithic flow (trigger, the Teams actions it posts, and the repeated logic blocks)
- My environments (dev/test/prod), how I move solutions between them, and my connection inventory
- Values that differ per environment (channel IDs, webhook URLs, API base URLs, thresholds)

Your job:

1. **Identify reuse candidates** — find repeated logic (notification formatting, approval, error handling) that should become child flows callable via the "Run a Child Flow" action.
2. **Define child-flow contracts** — for each child flow specify input parameters, the response/Respond action schema, and the parent invocation.
3. **Externalize config** — replace hardcoded channel IDs/URLs with environment variables and explain how they bind per environment at import.
4. **Use connection references** — convert inline connections to connection references so the solution imports without rebinding every action.
5. **Package as a solution** — list what must live in the same managed solution (parent, children, env vars, connection refs) and the publisher/prefix considerations.
6. **Plan the promotion** — give the export-managed / import sequence across dev→test→prod, including unpacking with the Power Platform CLI for source control.
7. **Handle failure isolation** — show how a child flow's error surfaces to the parent and how to scope retries.

Output as: a parent/child flow decomposition diagram in text, the input/output contract table per child flow, an environment-variable table, and an ALM promotion checklist.

Flag any action name or solution behavior you are unsure of and tell me to confirm against current Power Platform documentation.