Add --bitgate-* theme tokens and a build-injected VERSION.

Widget styles now prefer --bitgate-* custom properties, falling back to the
deprecated --gov-* names and then the existing defaults so current pages and
overrides keep working. Browser bundles and ESM entry points expose VERSION
(and window.bitgate.version) from package.json. Document allowlist on the
widget policy preset list. Sync the lockfile so npm ci sees @bitgate/standalone.

Co-authored-by: thePR0M3TH3AN <[email protected]>
This commit is contained in:
Cursor AgentandthePR0M3TH3AN committed 2026-10-08 19:14:44 +00:00
1 parent 90d4290989
commit 9e6f6c659e
24 files changed
+369 -22

No files matched your search

+3 -1
View File
@@ -175,7 +175,9 @@ unchanged.
authority or leaking private application context.
- [ ] Decide whether standalone output is generated from the canonical engine
directly or from a separately maintained browser entry point.
- [ ] Decide how browser builds expose version and integrity metadata.
- [x] Decide how browser builds expose version and integrity metadata.
`VERSION` + `window.bitgate.version` equal `package.json`, injected at
build time. Integrity manifests remain open (distribution / D7).
## BitBlocks App Kit compatibility layer