[CodyCBakerPhD]

Adds docs/future-ideas.md, which records the pros and cons of keeping the packages framework-free, then three suggestions for later:

1. Give every @brain-bbqs/ui binding a teardown. bindAccountMenu, initThemeToggle and createHumanSubjectsGate have none today, unlike bindDropzone and initWhatsNew.
2. Offer the shell as light-DOM Custom Elements from a separate entry point.
3. Revisit a reactive layer (signals, Lit, or a framework) if the apps start sharing heavy stateful widgets.

This changes docs only, so no package is affected and there is no changeset.

Original prompt

Do these components follow any framework? REACT, etc.

and pros/cons to that decision?

report these as suggestions under a docs/future-ideas.md

🤖 Generated with Claude Code

https://claude.ai/code/session_01P8t3eCPAHiqRTZgRC4m6K7