[itexpert120]

What

Lets a plugin entry set ui: false to drop the ui attached from the app it extends.

Implements the opt-out proposed in #636. The general fix there, giving each app's core UI container a unique name, is not part of this PR, so #636 stays open.

Why

A plugin entry that extends another app, such as bos://acct/app#plugins.<id>, gets that app's app.ui attached as the plugin ui. The consumer then loads the provider's whole UI on every page. Both core UI containers are named ui, so the second remoteEntry.js overwrites window.ui and the host hydrates with the provider's Hydrate.

On nearbuilders.org, which uses nostr.nearbuilders.org's plugin, this shows up as [Hydrate] Failed: Minified React error #527.

plugins: {
  nostr: {
    extends: "bos://nearbuilding.near/nostr.nearbuilders.org#plugins.nostr",
    ui: false,
  },
}

Changes

• ui: false is accepted on plugin entries in both the descriptor schema (bos.app.ts) and the config schema.
• It survives the authored ↔ config round-trip (toConfigInput / configInputToDescriptor).
• Resolution returns no associated ui for the entry, and getEntryAssociatedUi ignores the nested app.ui fallback when ui is false.
• Default behaviour is unchanged: without ui: false, the provider's ui is still attached, and folder-form plugin uis are unaffected.
• The extends-config skill documents the opt-out; patch changeset added.

Testing

• New tests:

  • Resolution drops the attached ui with ui: false.
  • ui: false survives the descriptor round-trip.
  • The provider ui is still attached by default.

  The first two fail without the fix.

• everything-dev package suite: 1633 passed.

  • 9 codegen tests fail locally only when TMPDIR is on a different filesystem (EXDEV on rename). They fail the same way on main and pass with a same-device TMPDIR.

• tsc --noEmit, biome and oxlint (type-aware) are clean on the changed files.

• End to end: a local nearbuilders.org v2 linked to this build, with ui: false on plugins.nostr.

  • Dev boots without BOS_MAP_ALLOW_UNRESOLVED.
  • The page loads only its own ui container and the auth ui.
  • In headless Chromium, hydration completes on /, /projects, /builders, /events and /activity, with no dev:ssr SSR session resolution returns null — authed routes 307 to /login despite a valid session #527.