@lssm-tech/module.builder-workbench
Reusable React surfaces for the Builder control plane: workspace home, guided chat/voice, source inbox, omnichannel inbox, blueprint editing, and readiness review.
CONTEXTE D’ENTREPRISE
Pass the optional companyContext controller to BuilderWorkbench to expose
CompanyContextPanel in Sources, or embed that panel independently. Hosts own authenticated retrieval; the shared projectCompanyContextView rejects stale workspace/question responses and malformed evidence before rendering text. The panel distinguishes missing configuration, denied access, conflicting sources, empty results, and loading. Knowledge does not grant release authority. English, French, and Spanish catalogs are included. Live provider activation, Storybook browser qualification, and visual baseline review remain required.
Model route inspection
The workbench exports route visibility components for Builder governance: ModelRouteBadge, ModelRouteInspector, ModelRouteOverridePanel, RiskFlagList, and RoutingEvidenceTimeline. These surfaces expose selected policy, difficulty, provider/model, risk flags, fallback routes, and rejected unsafe downgrades.
RoleMorph Workbench panels
The workbench exports RoleMorphWorkbenchPanels for rendering RoleMorph packet views with existing design-system/ui-kit primitives. The panel set covers role selection, surface preview/registry summaries, inspector diagnostics, policy diff summaries, safe missing-binding repairs, authorization/evidence summaries, and audit/replay timestamps. It renders serializable packet contracts only; provider execution, durable stores, and production authorization enforcement remain outside the module.
Candidate controls
Pass the optional candidate controller to BuilderWorkbench to expose
CandidateExecutionPanel in the Plan tab, or embed that panel directly. Prepare, approve, run and status controls follow server-resolved available actions. Unconfigured, denied, stale and indeterminate states do not appear as successful execution. English, French and Spanish messages are included. Candidate review is distinct from hosted preview or release.
useBuilderCandidate({ workspaceId, planRef, request, onRefreshPlan }) from
./presentation/hooks drives that controller: one in-flight action at a time, stale responses dropped across workspace/plan switches, bounded status polling (3 s, at most 20 polls) while queued or running, and onRefreshPlan on stale/succeeded. Hosts inject the request transport (BuilderCandidateRequest) and keep authentication and routing.
