Package readiness

Inspect the project's manifest, package policy, tool versions, release scripts, and required checks. Identify the exact candidate revision and which packaging or consumer assumptions changed. Use native tools; apply Hex checks only to an Elixir package.

• Build a local candidate and inspect its file list, dependencies, metadata, license, and required generated assets. Look for missing runtime files and unintended private or development-only content.
• Exercise the affected public interface from a disposable generic consumer using the built candidate where the toolchain supports it. Record when a path checkout or Git dependency was used instead; it does not prove the archive is complete.
• Avoid sibling-only paths, private application fixtures, or untracked developer state. Check optional dependency absence and supported compatibility directions when the contract requires them.
• Align documentation and source links with the candidate. Record exact artifact identity, commands, results, consumer setup, and combinations not tested.

Integrator owns package validation with the implementation and documentation owners. A local validation task does not authorize registry publication, a release tag, deployment, or a visibility change. Follow existing user authorization and repository release policy for separate release actions; repository visibility is always user-managed in this project.