TDK doctor

Use the CLI's environment and project checks as the starting point for TDK setup and diagnosis.

Workflow

1. Run tdk doctor from the TDK project root.
2. Read the full output and distinguish host prerequisites from project configuration findings.
3. Fix the source configuration or environment item named by the diagnostic. Do not hand-edit generated .autogenerated/ output.
4. Run tdk doctor again to confirm the finding is resolved.
5. Before starting services, use tdk networks to inspect the routed URLs; start only the needed stack with tdk up <stack> when appropriate.

Guardrails

• Do not claim the project is ready when tdk doctor reports unresolved errors.
• Ask before starting a large landscape or a task likely to build or launch many containers; it can take several minutes and use substantial resources.
• Avoid stopping containers by broad name patterns. Identify the target project and stack first.
• Treat diagnostic output as evidence. If it does not identify a cause, report what was observed and gather the next relevant check instead of guessing.