Can a Claim Page work alongside a custom extension that binds ERC-6551 accounts and ERC-8004 agents?

Manifold Support Questions
1

Hi Manifold team,

I have a 333-piece ERC-721 collection on a Creator Core contract with a custom registered extension. My extension’s mint() creates the NFT, deploys an ERC-6551 token-bound account, binds it to the token, and assigns a sequential seed. A second call, awakenAgent(), registers an ERC-8004 agent identity and transfers it into that token-bound account. This all works — I’ve verified it end to end.

What I don’t have is a collector-facing mint page. I’d much rather use your Claim Page than build my own. Four questions:

  1. Can a Claim Page or Editions campaign be configured to call a custom registered extension’s mint() function instead of ERC721LazyPayableClaim? My reading of the architecture says no, but I’d like to confirm before I build an alternative.

  2. If tokens are minted by ERC721LazyPayableClaim, can a separately registered extension act on those tokens afterward — specifically create an ERC-6551 account for them and write token data? Or are extensions limited to tokens they minted themselves?

  3. When ERC721LazyPayableClaim mints, it controls tokenURI through the claim’s location and storageProtocol. I have 333 unique metadata files in a single IPFS folder as 1.json through 333.json. Can a claim be configured to resolve each token to its own file in that folder, or does the identical flag mean all tokens in a claim share one URI?

  4. I noticed you ship a 6551 Display Widget. Is there a recommended pattern for combining Claim Pages with token-bound accounts? If there’s a supported path I’m missing, I’d rather follow it than invent one.

Happy to share contract addresses if that helps. Thanks — the Creator Core architecture has been a pleasure to build on says me trying to control Claude AI. Cheers Manifold Team!