Chainvoice x StablePay: Secure Invoicing and Multi-Variant Djed Payments

Chainvoice's privacy path is completely broken Lit Protocol is defunct, which means invoice creation and rendering fail for real users. Meanwhile, StablePay hardcodes its payment logic per Djed variant, so every new variant is a mini rewrite. And even though these two products live in the same ecosystem, a merchant still has to manually match invoices to on-chain transactions because nothing connects them. I'm fixing all three. First, I'll replace the broken Lit dependency with a mentor-confirmed alternative (ECIES with an on-chain key registry is my primary proposal, but the final call gets made during bonding). Second, I'll introduce a DjedVariantRouter in StablePay so supporting Classic, Wren, or any future variant is a config change, not a code change. Third, I'll bridge Chainvoice and StablePay using invoiceId as the shared anchor when a payment settles in StablePay, the invoice in Chainvoice flips to paid automatically. On top of that I'll ship lightweight merchant analytics derived from on-chain events (no backend needed), a module refactor that cleans up the encryption/payments/analytics boundaries, and a Dockerized dev environment. If core work finishes early, I'll build a typed Chainvoice SDK so any Web3 app can embed invoice flows without forking the frontend.