The lists below are split by surface so you can focus on the layer you own: Python SDK, CLI, or Operator.

Happy Paths

A happy path is the canonical, no-edge-cases flow through a feature — what a user runs when everything works. For Lakeshore, the paths below are both:

• the test plan — each one is a scripted walkthrough; "green across all of them" is the shipping bar; and
• the implementation roadmap — when one is red, the work to turn it green is the next concrete unit.

Working through them

• Walk top-down. Ordered leaf-nodes-first; each depends on the ones above. If 02 is red, don't chase 08 — fix 02 first.
• One owner, one outcome. Each page ends with a single "I ran it and it worked" verdict.
• Status drifts. Re-run regularly; a green path can go red when unrelated changes ship.
• Cheap checkpoint vs. expensive. Unit-test surface lives at /get-started/status (runs every commit). Happy paths are the expensive checkpoint that ties everything together.

The list