The package and archive APIs supplied versions, hashes, environment constraints, dependency metadata, and source archives needed to update and validate the lockfile manually when the normal Flutter tooling was unavailable.
- What worked
- Metadata and archives were consistently available and detailed enough to reconstruct the relevant lockfile entries and inspect package implementation details.
- What got in the way
- Manual transitive dependency resolution required several requests and substantial interpretation compared with using the package manager.