CODE, TESTS AND GITHUB DELIVERY ONLY; no public-network deployment or website in this task. Start from the project's delivered repository and preserve its history. The inspected delivery is https://github.com/identity-md-launches/launch-1309-unlk at 7c02c96b3d6cd07c8df9ed8a7811c95ac2ca1976; reconcile any newer project head before editing. Preserve the individual-wallet quotas, milestone thresholds, unrestricted native reward claims and permanent $5M unlock requirements.

First repair and verify the published handoff. On a clean clone of that commit, python3 scripts/check_dependencies.py fails: all 407 vendored files exist, but 177 SHA-256 values differ from dependencies.files.json. Determine the cause using the pinned upstream commits in dependencies.lock.json and the published Git blobs. Do not merely rewrite the expected hashes to accept unknown modifications. Restore or justify each difference, preserve licenses, and verify the final published commit, not only the pre-publication workspace. Correct the token display name to UNLOCK, retaining symbol UNLK; src/UnlkToken.sol and test/Launch.t.sol currently specify UNLK for both.

Resolve the documented IMD integration gaps INT-01 and INT-02 against authoritative factory, reward-distributor, fee and manifest interfaces. A previously inspected mainnet LaunchFactory at 0x12c63b581d07093f6126bc02263c58f7eadaa96f requires the full fixed supply to be minted to the factory, which then deploys the distributor and splits the tokens. The current three-recipient UnlkToken constructor does not implement that launch flow. Reverify source and policy before adapting it; never guess a Sepolia address or alter the required 10/87/3 final allocation. Reconcile companion-contract setup, CREATE2 hook flags, tuple constructor encoding, initial allocation evidence and authenticated router integration with the actual supported release interface. Provide a compatibility matrix and exact unresolved interface requirements.

Implement immutable claim and fee adapters only where verified official interfaces support them. IClaimEvidence and IFeeDistribution are currently project-defined boundaries, not verified IMD ABIs. Prove actual native claims can be credited once to the rightful recipient without restricting the native claim operation. Test fee recipients and principal withdrawal rights. Mocks must remain clearly labeled and cannot count as official integration evidence.

Reproduce the build, formatting, ABI/artifact checks and complete test suite using the pinned toolchain, then add regression tests for the corrections. Where network access and verified dependencies are available, run fork integration at a recorded chain/block and distinguish it from local PoolManager tests. Report unavailable checks accurately. Independently assess the open ORC-01 irreversible-unlock manipulation risk; quantify assumptions and attack costs rather than claiming a TWAP makes manipulation impossible. Do not silently change immutable economic parameters. If no independent reviewer runs, explicitly keep that review pending.

Deliver the updated repository commit, exact commands/results, final dependency verification, implementation changes, integration evidence, unresolved findings and a Sepolia readiness checklist. Mainnet release is out of scope. Do not claim deployment readiness while required integration or high-severity findings remain unresolved.

Upgrades and pausing: Not upgradeable and not pausable. No proxy upgrades, admin rule changes, counter resets or trader exemptions. Permit authenticated one-time initialization only; no administrative changes afterward.