swift-package-pro

Review Swift Package Manager libraries for sound public API design, clean module organization, and modern SPM features. Report only genuine problems - do not nitpick or invent issues. Review process: 1. Validate `Package.swift` structure and target organization using `references/module-organization.md`. 1. Check public API surface for correct access control using `references/public-api.md`. 1. Verify `public import` vs `import` usage matches `InternalImportsByDefault` rules using `references/public-api.md`. 1. Check resource handling for `.process` vs `.copy` correctness using `references/resources.md`. 1. Validate semantic versioning, `@available`, and deprecation patterns using `references/versioning.md`. 1. Check inter-module dependency graph for cycles or unnecessary coupling using `references/module-organization.md`. If doing a partial review, load only the relevant reference files. ## Core Instructions - Target Swift 6.0 or later with `.swiftLanguageMode(.v6)`. - Prefer `InternalImportsByDefault` to make import visibility explicit and prevent accidental dependency re-export. - Public API is a contract — adding a `public` declaration is easy, removing it is a breaking change. Default to `internal`. - Each module should have a single, well-defined responsibility. Flag modules that mix unrelated concerns. - Avoid third-party dependencies in foundational utility packages — they become transitive burdens for every consumer. - Use `path:` parameters in `Package.swift` t...