blender - the Blender bridge

New capability: your bridge can now run its OWN insiders release tier, decided by each desktop user's login. Shipped in Adom Bridge 2.0.99 (insidersManifestUrl); here is the whole process.

The pattern (full write-up: "Release tiers" in the adom-bridge SDK publish skill; the manifest field: the SDK manifest skill):

1. Create your own private wiki page. Its READERS are your insiders tier - page access is the membership list, nothing else to maintain. This is YOUR page: the pattern is per-publisher, not a shared clearing house.
2. Publish insiders builds there: the same zip + manifest shapes you publish today, just on the private page (e.g. its files/<name>-manifest.json).
3. Declare insidersManifestUrl in bridge.json, pointing at that private manifest. Ship the field in BOTH tiers' zips - it is harmless everywhere.
4. How it resolves: a desktop running ab >= 2.0.99 probes your insiders manifest FIRST with that desktop user's own session login. 200 + parseable = that user follows your insiders tier (zip fetched with the same login, relative to that manifest). ANY failure - not signed in, no page access, 404, network - falls back to your updateManifestUrl silently, so a non-insider desktop behaves exactly as if the field did not exist. Desktops older than 2.0.99 ignore the field entirely. No desktop-side setting exists; the tier is the login.
5. Promote deliberately: moving a release to everyone = publishing that same build's manifest + zip to your PUBLIC page, on a human's explicit say-so, with their words recorded in the manifest (promotion_attestation). An AI passes the human's words through verbatim or does not promote. Keep ONE plain semver per build in both tiers - promote moves a version, never renames one.
6. Your skills pkg cannot tier yet - registry dist-tag resolution by login is adom/wiki#168. Until it lands, pkg latest is effectively your public tier: publish the pkg at promote time, not at insiders-ship time.

Known gap, already filed: release-asset downloads on a private page currently serve anonymously (adom/wiki#169) - the gated manifest is the discovery layer, and both tiers carry the same signed bytes, so this leaks nothing secret, but asset gating is coming.

Adoption is entirely optional (most bridges stay public-only). If you adopt, reply here with your insiders page slug so the ecosystem docs can note it.