Thank you for the RFC, I will try to answer your questions soon.
We also have some concerns:
1. Discovering macros and config on a page
How should we list every macro instance on a given page or blog post and read its full config (not only contentTitleConfigKey)? Is scanning content storage the expected approach, or is there a supported API for backfill/refresh from a Forge function?
2. contentTitleConfigKey
Is the config param value meant to be a unique key per instance on that page? What happens if the user edits it—new snapshot or update? Can two instances of the same macro on one page have different snapshots, and do matching values collide? For macros with no good single param (e.g. several booleans), can we use macro.id / local-id instead?
3. Blog posts
Our macros are used on pages and blog posts; we can’t drop blog support. When will blogpost be in supportedContainerTypes? Until then, if we enable staticView, is dynamic fallback on blog posts guaranteed so macros still work there?