chore(deployments): permissioned posm redeploy with deliveryGasLimit (mainnet + sepolia)

[SocksNFlops]

What

Records the redeployed PermissionedPositionManager on mainnet and Sepolia in the deployment records (deployments/json/{1,11155111}.json plus the forge-chronicles generated deployments/{1,11155111}.md).

Why

The contract was redeployed to add a new constructor parameter, deliveryGasLimit = 500,000, exposed via the new DELIVERY_GAS_LIMIT() getter.

Addresses

Chain	Old	New
Mainnet (1)	0x63Bd7e5D4EcfAA74d82AE1dE98F476C935a81973	0xd7be746b6b29f6185a01013e944313e1704c971f
Sepolia (11155111)	0xf99D553912084c99F6299291b75Fe9B7119Aa1A7	0x864c37908aa5e10b100cacee1c62e3954d76f5e1

Notes

• All other constructor params are byte-identical to the previous deployments (poolManager, permit2, unsubscribeGasLimit 150k mainnet / 300k Sepolia, tokenDescriptor, WETH9, PermissionsAdapterFactory); the ABI diff shows only the added DELIVERY_GAS_LIMIT() getter.
• Both contracts are verified on Etherscan (solc 0.8.26, optimizer 500 runs, cancun).
• Markdown files were regenerated from the JSON with forge-chronicles (node lib/forge-chronicles --skip-json), matching the existing convention; history entries for the old deployments are preserved.
• Merging auto-pushes deployments/json to the briefcase repo via push-briefcase.yaml.

🤖 Generated with Claude Code