Story

As a user of RHDH, I want to have a dedicated "Notebooks" experience under Lightspeed that is shipped as a separate dynamic plugin and only visible when my instance has the feature enabled and a supported LLM, so that platform engineers can integrate Notebooks as a Developer Preview independently from Lightspeed Chat, and users only see Notebooks when the administrator has enabled it and RAG is properly supported.

Background

Feature RHDHPLAN-382 requires a new "lightspeed-notebook" dynamic plugin (separate from the existing lightspeed chat plugin) so Notebooks can be released as a Developer Preview independently (RHDHPLAN-373). The Lightspeed top navigation must show "Chat" and "Notebooks" tabs. The Notebooks tab must be visible only when (1) the administrator sets the app-config flag for Notebooks to true, and (2) when the LLM check is implemented, the configured LLM is one of the validated RAG models. This story covers:
(1) creating the lightspeed-notebook frontend plugin and its dynamic plugin packaging,
(2) adding the Chat | Notebooks tab bar to the Lightspeed page and wiring the Notebooks tab to the new plugin, and
(3) conditional visibility of the Notebooks tab based on app-config.

Dependencies and Blockers

QE impacted work

Documentation impacted work

Acceptance Criteria

1. Lightspeed-notebook plugin
   A new frontend plugin "lightspeed-notebook" exists in the lightspeed workspace, buildable and packageable as a dynamic plugin (e.g. app-config.dynamic.yaml with dynamicRoutes or equivalent). README and config.d.ts document the plugin and the lightspeed.notebooks (and any other) config options. It should have Support status as Developer PReview
2. Chat and Notebooks tabs
   On the Lightspeed fullscreen page, the top bar includes a horizontal tab bar with "Chat" and "Notebooks" (per Figma). The Chat tab shows the existing Lightspeed chat UI. The Notebooks tab shows the lightspeed-notebook plugin content (e.g. placeholder or empty state) when the notebook plugin is installed and lightspeed.notebooks is true.
3. app-config drives visibility
   Given an Administrator configures the instance, when the app-config.yaml flag for lightspeed.notebooks is set to true, then the Notebooks feature is visible in the UI (e.g. the "Notebooks" tab appears in the Lightspeed top navigation next to "Chat"). When lightspeed.notebooks is false or not set, the Notebooks tab is not shown.

     lightspeed:
       notebooks: true
     

4. Integration
   Instructions (or automation) for adding the lightspeed-notebook dynamic plugin to an RHDH instance (e.g. dynamic-plugins.yaml and app-config snippet including lightspeed.notebooks: true) are documented as part of Readme. When only the lightspeed chat plugin is installed, the app works as today (no Notebooks tab). When both plugins are installed and lightspeed.notebooks is true, the tab bar appears with both tabs.
5. No regressions
   Existing Lightspeed Chat behavior (lightspeed.chat.read, etc.), and routes continue to work when the new plugin is not installed or when lightspeed.notebooks is false.

upstream documentation updates (design docs, release notes etc)

Technical enablement / Demo