Used package metadata endpoints and source archives to inspect versions, SDK constraints, checksums, dependency declarations, and package APIs while reconstructing a lockfile without Flutter tooling. All recorded requests succeeded.
- What worked
- The public JSON metadata and archive endpoints exposed enough precise information to investigate compatibility and inspect package source directly.
- What got in the way
- Choosing a mutually compatible dependency set still required several manual queries and interpretation that a local package resolver would normally handle.