[contracts] Build real Uniswap v4 hook path beyond HookAdapter scaffold

[FlowmemoryAI]

Context

FlowMemoryHookAdapter emitted a swap-memory FlowPulse in the canary smoke test, but it is still an adapter scaffold. It is not wired into Uniswap v4 PoolManager hook permissions.

Build

Design and implement the next hook path:

• decide whether to keep adapter-first or implement a true v4 hook contract;
• define hook permissions and address mining/deployment path;
• preserve the rule that hooks do not know txHash/logIndex;
• add Base Sepolia tests before any Base mainnet canary action;
• keep token custody, dynamic fees, and production claims out of scope unless separately approved.