@trybotster/hub-test-support

Node-consumable Botster hub test-support assets for first-party web clients.

The package is a generated wrapper over botster-hub-test-support and botster-hub-client. Do not edit daemon-protocol.ts, first-party-client-support-matrix.json, late-attach-history-conformance-fixture.json, local-webrtc-response-chunk-conformance-fixture.json, fixtures/plugin-contract-matrix, or metadata.json by hand; run:

node packages/hub-test-support/scripts/sync-assets.mjs

Usage

npm install --save-dev @trybotster/[email protected]

import {
  materializeApplicationPrimitivesFixture,
  materializePluginContractMatrixFixture,
  metadata,
  readDaemonProtocolTypescript,
  readFirstPartyClientSupportMatrix,
  readLateAttachHistoryConformanceFixture,
  readLocalWebrtcResponseChunkConformanceFixture,
} from "@trybotster/hub-test-support";

const protocolSource = readDaemonProtocolTypescript();
const fixturePath = materializePluginContractMatrixFixture(tempDirectory);
const applicationPrimitivesPath = materializeApplicationPrimitivesFixture(tempDirectory);
const supportMatrix = readFirstPartyClientSupportMatrix();
const lateAttachFixture = readLateAttachHistoryConformanceFixture();
const localWebrtcChunkFixture = readLocalWebrtcResponseChunkConformanceFixture();
const applicationSurfaceId = metadata.application_primitives.surface_id;
const rendererEntryPoint = metadata.application_primitives.renderer_entrypoint;

console.log(
  metadata.protocol,
  metadata.conformance_fixture_revision,
  fixturePath,
  applicationPrimitivesPath,
  applicationSurfaceId,
  rendererEntryPoint,
  supportMatrix.required_features,
  lateAttachFixture.history_then_live,
  localWebrtcChunkFixture.scenarios.large_generated,
);

Use this exact package spec in npm-based client repos:

{
  "devDependencies": {
    "@trybotster/hub-test-support": "0.1.7"
  }
}

After @trybotster/[email protected] is published to the public npm registry, no scoped .npmrc entry or CI auth token is required for install.

The support matrix is generated from the Rust compatibility descriptors. In 0.1.7, terminal_readback appears in both supported_features and required_features; downstream compatibility checks must implement it rather than treating it as optional. The late-attach fixture is generated from the Rust serde scenario and preserves attaching -> optional initial state -> attached -> live ordering. An opaque authoritative snapshot may represent a blank terminal; clients must not infer visible history from payload byte length. Only read_screen_text is renderable restored content; snapshot and scrollback base64 payloads must never be appended as terminal text. Version 0.1.6 / conformance revision 13 uses superseded JSON number arrays, while version 0.1.5 / revision 12 exposes lossy string history. Neither is current binary-history contract authority.

Botster web and TUI renderers should consume metadata.application_primitives.surface_id (contract.app) and render metadata.application_primitives.renderer_entrypoint (ui_tree_snapshot.body). The current core-validated primitive inventory is exposed as metadata.application_primitives.primitive_kinds: button, empty_state, form, metric, metric_grid, panel, section, status_badge, table, text_input, and toolbar. The current core contract fixture does not include list or an action_bar alias; downstream clients should not invent those shapes.

Client repos should update their lockfile from the registry coordinate or packed tarball, then run a smoke that imports the package, reads the daemon protocol artifact, calls verifyPackageAssets(), and materializes the application-primitives fixture.

The normal consumer path is the declared npm dependency. Environment variables such as BOTSTER_HUB_CLIENT_DAEMON_PROTOCOL remain local override inputs for older drift checks, not the package consumption path.