Never commit secrets.
Credentials, cookies, access tokens, API keys, HAR files, private screenshots, and connected-account exports stay out of Git.
This edition is specifically written around Muse by Meta. It does not claim to expose private Meta telemetry; it gives you a disciplined prompt and reporting layer around the Muse work you can observe. Everything important is reachable as a page: what FedPromptly is, how to open it, how to deploy it, how to contribute, and where privacy boundaries live.
The standalone edition is intentionally dependency-free. Double-click the HTML files, or serve the folder if you want to test navigation through a local HTTP origin.
Then visit http://localhost:8080. No npm, framework, local JSON, server-side include, or bundler is required for the HTML edition.
For a root-level static site, leave the build command blank and deploy the repository contents as assets.
This applies to a plain HTML repository with index.html at the root. A Worker-code or framework project needs its own build and deploy configuration.
The privacy-safe folders are placeholders for local runtime material, not an invitation to commit sensitive exports.
Credentials, cookies, access tokens, API keys, HAR files, private screenshots, and connected-account exports stay out of Git.
When usage data is measured or estimated, record the evidence or rationale. This is more useful than a high-precision guess.
Check payment-provider rules, local age requirements, privacy obligations, accessibility, and any external links before launch.
Go from project structure to a concrete measurement spec.
Open the audit guide