description: "Scope-grouped read-only plugin inventory tab in Web Plugins settings for the xlaunch web client: agent-preset compositions first, the global plane behind a disclosure, search across both." kind: "package-reference"

@xlaunch/client-ui-settings-plugin-inventory

Summary

xlaunch-client-ui-settings-plugin-inventory contributes the read-only Plugin list tab to the Web Settings Plugins section. The tab lazily calls ctx.remote.pluginInventory.list() the first time it is selected and renders the inventory in two collapsible groups. The agent-preset group comes first, open by default: a display-only switcher pill over the roster opens on the default preset, and each composition row is a compact disclosure card carrying its enablement — including conditional for a disabled gate the Host could not evaluate — with provenance facts behind the disclosure. The global group follows collapsed, its header carrying the entry count and a failure count; expanded, failures float first, and an entry disabled globally but enabled by at least one preset is marked as preset-provided in place — its details name the enabling presets — instead of reading as plainly disabled. Search filters both groups, forces the collapsed groups open, and points at matches sitting in unselected presets. Loading, empty, no-match, and generic failure states stay local to the mounted component, and a failed read can be retried without exposing transport details; without a roster the tab renders the global plane alone, expanded.

Table of Contents

• Use this package
• Understand the implementation
• Further Exploration
• Model Experience
• Known Limitations and Deferred Work
• Dev Note

Use this package

Open the Plugins section in Settings and select the Plugin list tab to inspect the Host's plugin inventory. The tab reads no Remote during plugin activation — selecting it for the first time mounts the component and lazily calls ctx.remote.pluginInventory.list() through api-remotes.

Reading a card

Each collapsed card uses the short module name as its title and a small enablement tag; enabled entries also show a colored root-fiber status dot. Expanding one card reveals the declared entry id, the full module specifier, and the state facts: a preset row names the preset it comes from, its runtime status when the composition is live, and its disable condition when it carries one; a preset-provided global row explains that agent presets provide it per session, names the presets that enable it, and offers a jump into the preset group. Preset names resolve through the shared presetDisplayText fold (xlaunch-agent-presets/display) over ui-agent-preset's dictionaries: shipped presets follow the active locale while user-authored ones keep their own metadata, so an English surface never echoes the preset files' Chinese names. Search filters both groups by module name and entry id.

The preset switcher

The switcher is the same selector-pill-plus-menu control the General settings rows use. It lists every roster preset — the default suffixed as such, broken ones marked — and changes only what the list shows: it writes no settings, and selecting a broken preset shows the discovery-reported reason in place of rows. Choosing the default preset or a session's preset stays where it was: the Agent presets section and the new-session screen.

Retrying a failed read

A failed read renders a generic failure state inside the tab; retrying re-runs the lazy list() call without exposing transport details.

Understand the implementation

The tab is a read-only projection of a Host-owned snapshot; it performs no Remote read during plugin activation and takes the snapshot on first selection.

Registration

The browser plugin registers one localized settings.plugins.tab contribution with id all; the Plugins section owns the navigation entry and tab chrome. Registration uses ctx.slots.inject(), so it follows late tab declaration, redeclaration, locale changes, and teardown without importing the section owner.

Rendering

Row keys are scope-qualified (global:, preset:<id>:<index>), so one module appearing in both scopes keeps distinct disclosure state; an entry id is shown as detail only when the row declares one and is never classified by string shape. The preset-provided marking is derived client-side: a global entry carries it when it is disabled there while at least one preset row for the same module specifier is actually enabled, so a module every preset gates off (or declares only conditionally) stays plainly disabled rather than over-claiming provision.

Further Exploration

These pages cover the settings section, the remote call, and the Host-side projection.

• ui-settings-plugins — the Plugins section this tab registers into.
• ui-settings — the domain base declaring settings.plugins.tab.
• api-remotes — the Remote BFF surface behind pluginInventory.list().
• plugin-inventory — the Host-side read-only Loader projection this tab renders.

Model Experience

None, as the package is a browser-side inventory projection that registers nothing model-facing.

KV Cache effect

None; this package neither assembles nor sends a provider request.

Known Limitations and Deferred Work

These limits define the freshness and reach of the inventory view; they are current package constraints.

• One snapshot per Settings mount or retry — the tab does not subscribe to Loader changes or automatically refetch after reconnect; switching tabs preserves the current snapshot, while reopening Settings obtains a new one.
• Read-only in both planes — the tab shows global and preset enablement but mutates neither; enable/disable controls that write a custom preset's own composition file are deliberate follow-up work.

Dev Note

None.

Runtime invariant: No companion is published. This package owns a read-only Settings contribution.