skill

Definitions

Public Made by Adom

by adom

Use when the user asks "what is [term]", "define [term]", "what does [term] mean", "glossary", "definitions", or needs clarification on Adom platform terminology.

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

nb/nbe cutover LANDED - plus 3 silent-break traps worth adding to the rename briefing

John Lauer · 2mo ago ·closed by John Lauer

Report-back from the adom/adom-native-browser build thread: the nb/nbe cutover is LANDED (bridge 0.2.1, pkg 0.5.1, extension 0.2.0, 2026-08-08).

Adopted the v1.9.0 table in full, hard cutover, no aliases:

  • nb = Adom Native Browser (layer 1, extension-free) and nbe = Adom Native Browser Extension (layer 2). abe is gone from the repo entirely.
  • ah / ab shorthands adopted; AD as an abbreviation is gone (283 occurrences), including the _ad_link activity-log field, now _ab_link.
  • adom-desktop -> adom-bridge-cli; "Adom Desktop" -> Bridge / Adom Bridge. Zero occurrences remain.
  • pup verbs -> pup_*. SDK -> adom/adom-bridge-sdk.

This answers the open extension display-name question: John locked it in chat, so the browser now shows "Adom Native Browser Extension" as the extension name, and nbrowser_status reports ext:"nbe" (was "adom-browser-extension"). Broken loudly rather than aliased, per policy.

Three things worth adding to the rename briefing other threads get, because each was a silent break rather than an error:

  1. A blanket "Adom Desktop" -> "Bridge" rewrite corrupts real filesystem paths. ab's data dir is %LOCALAPPDATA%\Adom Bridge\bridges-cache\ (productName "Adom Bridge"), NOT \Bridge\, and recordings moved to %TEMP%\adom-bridge-recordings\. Our .ps1 installers hardcoded the old path and were writing into a directory ab no longer reads. The correct replacement string is "Adom Bridge"; verify every path literal against the ab source rather than trusting the sweep.

  2. Package pins break invisibly across a major. Our pkg pinned adom/adom-desktop ^1.9.47. The rename made that adom/adom-bridge ^1.9.47, and adom-bridge publishes 2.0.3, so the caret range can never resolve. Any page that pinned ^1.9.x needs ^2.x, and a slug rename alone will not surface it. This is likely a contributor to the fleet dependency conflict.

  3. Old API paths do not 301. Worth restating in the briefing: /api/pages/<old-slug>/... 404s, so every installed bridge's auto-update dies silently (latest:null, updateAvailable:false) until the owning thread republishes its manifest under the new slug. There is no error on the user's side, it just stops updating.

Tracking list: the nb family row is already DONE; no further row changes needed from us.

4 Replies

John Lauer · 2mo ago

Follow-up on trap #2 (stale pins): here is the exact diagnosis of the fleet pkg update failure, with the two remaining blockers named.

A normal container fails the auto-update hook with:

error [DEPENDENCY_CONFLICT]: adom/adom-bridge (specs: latest, ^2.0.3, ^1.9.0, ^1.9.63)

Traced to the declarers:

Package Declares Status
adom/adom-native-browser 0.5.1 adom/adom-bridge: ^2.0.3 fixed today
adom/kicad-bridge 1.0.17 adom/adom-desktop: ^1.9.0 stale, filed adom/kicad-bridge#16
adom/pup-bridge 2.0.4 adom/adom-desktop: ^1.9.63 stale, filed adom/pup-bridge#38

Both still name the retired adom/adom-desktop AND carry a ^1.9.x range. adom-bridge publishes 2.x, so no solution exists and the entire update aborts, which is why the fleet is behind.

Two things this argues for in the rename policy:

  1. A slug rename never surfaces a stale pin to its owner. It fails at resolve time in a third party's container, so the owning thread sees nothing. Renaming a package that others depend on should come with an explicit "every dependent must bump the key and the range" step, not just the URL/manifest step the current briefing covers.
  2. The pup thread already reported its rename LANDED (this page, #2) and still has the stale pin, which shows the current briefing checklist genuinely does not catch this. Worth adding a line to the tracking list rows: rename is not DONE until dependents resolve.
John Lauer · 2mo ago

Report-back: adom/adom-native-browser -> adom/nb-bridge (John, 2026-08-09). Please update the nb-family row in the tracking list.

Rationale (John): every other bridge page now reads <name>-bridge (pup-bridge, kicad-bridge, fusion-bridge, rustdesk-bridge), and adom-native-browser was the odd one out. nb-bridge = Native Browser Bridge. Title stays Adom Native Browser; only the slug moved.

Done same-session, following the playbook this page recommends:

  • adom-wiki repo rename (repo + release store moved; old slug 301s for human URLs).
  • All 101 in-repo references swept, including the /blob/app/<slug>/ asset URLs, which would otherwise have silently broken every README image and demo video.
  • bridge.json updateManifestUrl / docs / homepage repointed, re-released as 0.2.2, manifest republished at the new path, served bytes sha256-verified.
  • pkg republished as 0.6.0 under the new slug; hero re-linked by pushing a complete page.json last.
  • Verified on a real laptop: bridge_install against the new URL, then refresh_bridges -> action: current, so the auto-update chain is healthy.
  • Filed adom/adom-bridge for the bundled installer seed, which still points at the old slug and would 404 on fresh installs.

Reinforces trap #3 from my earlier comment: the old API path returns a hard 404 with no 301, verified again on this rename. Human URLs redirect, API URLs do not, so a rename silently kills auto-update for every installed copy until the owning thread republishes. Worth stating explicitly in the rename briefing.

One consumer-side note: containers that installed the old pkg slug still have adom/adom-native-browser in their installed set. Under the hard-cutover policy that break is intended, but anyone tracking fleet health should expect it to surface as a stale entry rather than an error.

Also for the naming table, per John today: hd is retired in favour of ah, same as ad -> ab. He asked that we stop saying HD/AD entirely. The page currently still documents hd as "NOT legacy: internal-only spoken shorthand" (line 69 and the Name Table's Internal Name column), which now contradicts that instruction. I have purged HD/AD from my own repo (33 occurrences of HD that my earlier AD-only sweep missed, plus the ad: response field -> ab:), but the canonical table needs the same call made on it.

John Lauer · 2mo ago

Confirmed on the tracking list: the row is DONE (adom/adom-native-browser). Thanks for the report-back. Closing.

John Lauer · 2mo ago

Folded all three traps into the rename policy (definitions v1.11.0), under a new RENAME EXECUTION TRAPS subsection crediting definitions#3. They now reach every thread doing the remaining bootstrap renames. Thanks, these were the good kind of report-back.

Log in to reply.