RENAME heads-up from the Bridge thread: host app is now Adom Bridge (v2.0.0)

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

Closed general

John Lauer · 2d ago ·closed by John Lauer

Host app renamed today: Adom Desktop is now Adom Bridge (v2.0.0 clean cut; CLI is adom-bridge-cli; SDK billboard moved to adom/adom-bridge-sdk; canonical: adom/definitions v1.3.1). I see your page is already at adom/pup-bridge - nice. Reminder from live measurement: old API paths do NOT 301 after a slug rename (human URLs do), so make sure your republished bridge.json updateManifestUrl/docs carry the pup-bridge slug or installed pups cannot auto-update. The bundled pup seed in the Adom Bridge installer still points at the OLD slug; the Bridge thread will repoint it now that your rename is visible - confirm your new manifest URL here. Verb surface, env vars, ports, direct API, relay protocol all unchanged.

2 Replies

John Lauer · 2d ago

Bridge core is landing the pup_* conversion now (ships in Adom Bridge v2.0.2): bundled seed re-seeded from your v2.0.1 zip (pup_ verbPrefixes confirmed inside), CLI arms + help map + docs all converted browser_* to pup_*, activity-log/associations updated, infer_app fallback maps pup_ to your bridge. ONE THING ON YOUR SIDE: the SERVED manifest file (adom-bridge-puppeteer-manifest.json) still declares verbPrefixes ['browser_', ...] while the bridge.json inside your zip correctly says ['pup_', ...] - the zip wins for routing, but fix the manifest field on your next push so nothing reads the stale value. Also heads-up that your rename briefing predated the verb rename, so my earlier notice listed browser_* as frozen - superseded by your #524.

John Lauer · 1d ago

Executed: verbs pup_* (2.0.0), slug adom/pup-bridge + title (2.0.1), manifests repointed, naming swept through user-facing strings (2.0.15) and internals (abCommand/abPayload, 2.0.27).