Adopt the two-tier (early-release) publish: insidersManifestUrl in bridge.json, early manifest first, promote on a human's words, release log

Overview Files Skills Discover Packages Releases Dependencies Issues1 Breadcrumbs Pull Requests Activity

Closed feature request

John Lauer · 1mo ago ·closed by John Lauer

Ask from John (2026-09-02): this bridge should ship on the two-tier (early-release) publish that Adom Bridge now supports, so Adom employees get every build the moment it is cut and public users only move when a human promotes one.

What ab does for you (2.0.99+). If src/bridge.json declares insidersManifestUrl next to updateManifestUrl, ab probes that manifest first with the desktop user's own login and installs what it names; any failure (no login, 403, 404) falls back to updateManifestUrl silently. A public desktop never learns the field means anything.

What to do, in order:

Add insidersManifestUrl to src/bridge.json. Adom-org bridges do NOT create a private page for this: the org has one shared early-tier page, and the insiders-tier-bridges skill in your workspace names it and gives the exact recipe (folder named after this page's slug, a version.json in the bridge-manifest shape, bytes stay as releases on THIS page). If that skill is not in ~/.claude/skills, it arrives on the next Hydrogen update check under an Adom-org login.
Make your ship script write the early-tier manifest by default. The public manifest on this page changes only through a promote step that requires and records a human's exact words (promoted_by, promoted_at, promotion_attestation in the manifest). Reference: the Bridge SDK publish skill on adom/adom-bridge, "Release tiers", and adom/pup-bridge's tools/ship.sh and tools/promote.sh, which did this first.
Every early publish appends an entry to this bridge's release log on the early-tier page (version, date, what is in it, "Not promoted"); a promote edits the entry with the date and the words. The insiders-tier-publish skill has the rule.
If this page also hosts a skills package: publish it in lockstep with every early ship, same version, until adom/wiki#170 is fixed (a release-only row otherwise outranks the package and breaks pkg install). The insiders-tier-bridges skill records that decision.
Verify with the insiders-tier-verify skill, section 3b: the two-curl split, and the one-time bootstrap for a desktop whose installed bridge predates the field (bridge_install with the early manifest URL and force: true).

Reply here with the first version that carries the field and the ship script change, and tick your box on the cascade tracker the skill points at. Questions about the pattern itself go to adom/adom-bridge#119 (tier readouts in bridge_check_updates and bridge_list are being added there).

1 Reply

John Lauer · 5d ago

Adopted in 1.3.3.

bridge.json declares insidersManifestUrl (/pages/insiders/files/grok-bridge/version.json).
tools/ship.sh <ver> "<log>" is insiders by default: lockstep bump → runtime zip → skills pkg at the same version (lockstep until adom/wiki#170) → release on this page → insiders manifest + a "Not promoted" release-log entry on the early-tier page → source push. The public manifest is never touched.
tools/promote.sh <ver> "<words>" --by "<name>" refuses without the human's exact words, re-checks the served asset's sha256, records promotion_attestation / promoted_by / promoted_at, and marks the release-log entry.
Verified with the two-curl split: insiders manifest reads 1.3.3 with a login and anonymous gets 404; the public manifest is still 1.3.2. AdomLapper was bootstrapped with bridge_install from the early manifest (force: true).
Cascade tracker box ticked.

Public stays at 1.3.2 until someone promotes 1.3.3.