Fix the concrete Sepolia admission failure of UNLOCK job 672489ef-8304-403f-855c-b9dce583bc31 and parked launch 55d5370e-7256-465c-808f-09ba4cc8ccee (launch 1534). Continue the published source https://github.com/identity-md-launches/launch-1534-unlock at f77cf377f6eb58f05ef9b9c61f36407933d5053a, reconciling any newer accepted work. No old bundle recovery or rewrite from scratch is needed.

Exact failure: HookDeployer runtime is 26264 bytes, exceeding 24576. UnlkHook itself is 24328 bytes. src/HookDeployer.sol embeds type(UnlkHook).creationCode. scripts/release_artifacts.py incorrectly exempts HookDeployer from its size assertion, although the actual service rejects it.

Make HookDeployer a small pure encoder: remove its UnlkHook import; initCode must accept bytes memory hookCreationCode plus Config calldata and concatenate the provided code with the same four ABI-encoded constructor arguments. initCodeHash must accept the same arguments and hash initCode's result. This helper must not gain deployment authority or become a production factory. Update callers in test/fixtures/SystemFixture.sol and test/FailurePaths.t.sol to supply type(UnlkHook).creationCode. Preserve the official factory launch, manifest placeholders, hook flags and all token/trading/oracle/claim/setup behavior.

Remove the HookDeployer exception from release_artifacts.py; every release artifact must pass actual EIP-170 runtime and initcode limits. Do not increase limits, weaken protected checks or merely hide an oversized artifact. Add a regression test that deploys the helper, asserts runtime <=24576, compares its output/hash to the reviewed hook creation code plus four encoded addresses, and detects a changed setup authority. Run the complete existing suite and confirm creation/runtime bytes for token, hook, router, oracle and claim evidence are unchanged. Refresh the helper ABI, artifact/source digests and outdated size documentation.

Deliver the actual published fix commit, reproducible commands/results and all artifact sizes. Rerun the real IMD admission check if a supported operation is available. Do not claim a local test is service admission, or that job.continue redeploys. Identify the supported way to retry the parked launch against the reviewed fixed commit; do not invent a retry endpoint or silently deploy another token.

Sepolia activation remains a separate release prerequisite: confirm the concrete authorized actor and transactions for deployCompanions, actual round-0 certification and configureAndActivate before any broadcast. Keep unresolved protocol-fee halt, treasury reward-round powers and manipulation risks disclosed; this size fix does not authorize acceptance of new risks. No mainnet transactions. If continuation can only publish code, report that explicitly along with the remaining release operation.