Compose 0.2.0 feedback after using it as the source-of-truth for a real project

Wanted to share feedback after spending a session using Compose 0.2.0 as the projects-as-code source of truth for a real, non-flat project, in case it's useful for prioritization. Context. The project I tested with: 31 work items, 11 grouping units (modules), 5 phased time windows (cycles, with overlapping dates), ~17 dependency relations across them, 7 custom states. Probably representative of any moderately structured operational playbook -- release planning, customer onboarding, deal pipelines, marketing campaigns, etc. The kind of thing where the *structure* is the artifact and items get filled in over time. The headline I was hoping to write was: *Plane is the only modern PM tool that treats project structure as infrastructure.* After working through Compose end-to-end, here's what I found. What works well • plane clone <uuid> is fast and ergonomic. ~6 seconds for a 31-item project. Directory layout (plane.yaml, schema/, work/, .plane/remote/) is intuiti…