feat: rename from lightspeed to intelligent-assistant

[Jdubrick]

Target branch

• I have verified this PR targets the correct branch (see branching strategy)

Description

• Renames lightspeed to intelligent-assistant in documentation, configuration files, and compose files.
• Updates intelligent-assistant plugin to use Quay instead of registry to match what is in the next catalog image and flips back to enabled by default

Which issue(s) does this PR fix or relate to

https://redhat.atlassian.net/browse/RHIDP-15898

PR acceptance criteria

• Tests updated and passing
• Documentation updated
• Built-in TechDocs updated if needed. Note that TechDocs changes may need to be reviewed by a Product Manager and/or Architect to ensure content accuracy, clarity, and alignment with user needs.

How to test changes / Special notes to the reviewer

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rhdh-qodo-merge]

PR Summary by Qodo

Rebrand Lightspeed as Developer Hub Intelligent Assistant

✨ Enhancement 📝 Documentation ⚙️ Configuration changes 🕐 20-40 Minutes

AI Description

• Rebrands Lightspeed as Developer Hub Intelligent Assistant across configuration and documentation.
• Moves renamed plugin images to Quay and enables both plugins by default.
• Aligns disablement instructions, routes, screenshots, and configuration keys with the renamed
 plugin.

Diagram

graph TD
  Manifest["Plugin manifest"] --> Installer["Plugin installer"] --> RHDH["RHDH instance"] --> Core["Lightspeed Core"] --> Provider["LLM provider"]
  AppConfig["Assistant config"] --> RHDH
  Docs["Assistant guides"] -. references .-> AppConfig
  Override["Disable override"] -. disables .-> Core

Loading

High-Level Assessment

The coordinated rename is the appropriate approach because the plugin packages, configuration namespace, routes, documentation, and catalog image must remain aligned. Retaining compatibility aliases for the old Lightspeed names would require upstream plugin support and would prolong ambiguous naming without clear benefit.

Files changed (18) +121 / -115

Enhancement (1) +7 / -9

dynamic-plugins.yamlEnable renamed Intelligent Assistant plugins from Quay +7/-9

Enable renamed Intelligent Assistant plugins from Quay

• Switches both dynamic plugin packages to their Intelligent Assistant Quay images and enables them by default.

configs/dynamic-plugins/dynamic-plugins.yaml

Documentation (12) +87 / -87

README.mdRename the default assistant and update guide links +3/-3

Rename the default assistant and update guide links

• Updates onboarding and guide references to use Developer Hub Intelligent Assistant terminology and renamed documentation paths.

README.md

developer-intelligent-assistant.mdRebrand the end-user assistant guide +34/-34

Rebrand the end-user assistant guide

• Renames Developer Lightspeed throughout the user guide and updates navigation instructions to match the Intelligent Assistant UI.

docs/getting-started-rhdh/developer-intelligent-assistant.md

extensions.mdRename the assistant extension example +1/-1

Rename the assistant extension example

• Uses Developer Hub Intelligent Assistant as the AI-assisted development plugin example.

docs/getting-started-rhdh/extensions.md

highlights.mdLink highlights to the renamed assistant guide +1/-1

Link highlights to the renamed assistant guide

• Updates the feature link label and target to the Intelligent Assistant documentation.

docs/getting-started-rhdh/highlights.md

index.mdUpdate the getting-started assistant link +1/-1

Update the getting-started assistant link

• Points the feature index to the renamed Developer Hub Intelligent Assistant guide.

docs/getting-started-rhdh/index.md

navigation.mdRename assistant navigation references +2/-2

Rename assistant navigation references

• Updates sidebar examples and navigation tips to use Developer Hub Intelligent Assistant terminology.

docs/getting-started-rhdh/navigation.md

your-first-day.mdRefresh first-day assistant references +2/-2

Refresh first-day assistant references

• Renames the assistant quickstart and updates the related guide link.

docs/getting-started-rhdh/your-first-day.md

Developer-Hub-Intelligent-Assistant.pngAdd the renamed assistant interface screenshot +0/-0

Add the renamed assistant interface screenshot

• Provides the screenshot asset referenced by the Intelligent Assistant setup guide.

docs/images/Developer-Hub-Intelligent-Assistant.png

maintaining-intelligent-assistant.mdRebrand the assistant maintainer guide +8/-8

Rebrand the assistant maintainer guide

• Updates integration terminology, internal links, and plugin descriptions while preserving Lightspeed Core service naming.

docs/intelligent-assistant/maintaining-intelligent-assistant.md

working-with-intelligent-assistant.mdAlign setup instructions with the renamed plugin +33/-33

Align setup instructions with the renamed plugin

• Updates configuration keys, UI routes, image references, package locations, and disablement instructions for Intelligent Assistant.

docs/intelligent-assistant/working-with-intelligent-assistant.md

help-and-contrib.mdUpdate the documented guide file layout +1/-1

Update the documented guide file layout

• Replaces the legacy Developer Lightspeed filename with the Intelligent Assistant guide filename.

docs/rhdh-local-guide/help-and-contrib.md

index.mdLink the local guide to Intelligent Assistant documentation +1/-1

Link the local guide to Intelligent Assistant documentation

• Renames the assistant feature entry and points it to the new guide path.

docs/rhdh-local-guide/index.md

Other (5) +27 / -19

compose.intelligent-assistant-disabled.override.example.yamlAdd renamed assistant disablement override +8/-0

Add renamed assistant disablement override

• Provides a compose override that places RAG initialization and Lightspeed Core behind the intelligent-assistant profile.

compose.intelligent-assistant-disabled.override.example.yaml

app-config.yamlAdopt the Intelligent Assistant configuration namespace +7/-7

Adopt the Intelligent Assistant configuration namespace

• Renames the plugin configuration key from 'lightspeed' to 'intelligent-assistant' and updates associated documentation and repository references.

configs/app-config/app-config.yaml

dynamic-plugins.override.example.yamlUpdate plugin disablement examples for renamed Quay images +5/-5

Update plugin disablement examples for renamed Quay images

• Replaces legacy registry package examples with the Intelligent Assistant frontend and backend images hosted on Quay.

configs/dynamic-plugins/dynamic-plugins.override.example.yaml

default.envRefresh assistant environment guidance +4/-4

Refresh assistant environment guidance

• Updates comments and documentation links to use the new product name while retaining Lightspeed Core provider settings.

default.env

mkdocs.yamlRegister renamed Intelligent Assistant documentation +3/-3

Register renamed Intelligent Assistant documentation

• Updates TechDocs navigation labels and paths for the user, setup, and maintenance guides.

mkdocs.yaml

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 🔗 Cross-repo conflicts (1) 📜 Skill insights (0)

1. Enabled artifacts are unavailable 🔗 Cross-repo conflict ☼ Reliability

Description

The PR enables both Intelligent Assistant packages through inherited Quay references, but RHDH's
catalog sanity configuration identifies these exact packages as unpublished or unauthorized from
public registries. Default dynamic-plugin installation can therefore fail when the local stack
starts.

Code

configs/dynamic-plugins/dynamic-plugins.yaml[R45-46]

+  - package: 'oci://quay.io/rhdh/red-hat-developer-hub-backstage-plugin-intelligent-assistant:{{inherit}}'
+    disabled: false

Relevance

●●● Strong

Concrete default-installation failure; similar enabled OCI reference corrections were accepted.

PR-#212

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The PR enables the exact frontend and backend Quay packages by default. The pinned RHDH repository
lists both package names under a documented exclusion for repositories that return unauthorized from
Quay and registry.access.redhat.com, specifically noting that these tag-style references are a
publication problem; the installer confirms that {{inherit}} is resolved from an included
configuration.

configs/dynamic-plugins/dynamic-plugins.yaml[41-50]
External repo: redhat-developer/rhdh, e2e-tests/local-harness/plugin-sanity-excludes.txt [45-58]
External repo: redhat-developer/rhdh-plugins, workspaces/install-dynamic-plugins/packages/install-dynamic-plugins/src/oci-key.ts [42-47]
External repo: redhat-developer/rhdh-plugins, workspaces/install-dynamic-plugins/packages/install-dynamic-plugins/src/oci-key.ts [76-81]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The newly enabled Intelligent Assistant OCI packages are explicitly excluded by the pinned RHDH catalog sanity tests because their public tag references do not resolve anonymously.

## Issue Context
`{{inherit}}` resolves the package version from the included catalog configuration. Keep these plugins disabled until the referenced Quay artifacts are publicly available, use verified resolvable digest-pinned references, or coordinate publication/catalog changes in `redhat-developer/rhdh` before enabling them by default.

## Fix Focus Areas
- configs/dynamic-plugins/dynamic-plugins.yaml[45-50]
- configs/dynamic-plugins/dynamic-plugins.override.example.yaml[120-127]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

⚠️ Tickets: not configured — ticket URL found in PR but could not be fetched — check ticket provider credentials

✅ Cross-repo context — repo relationships

  Explored: repo: redhat-developer/rhdh (sha: b9697de8)

  Explored: repo: redhat-developer/rhdh-plugins (sha: 2f7d1698)

Tip of the day

💡 Did you know, you can show, collapse, or hide each part of a finding: code, evidence, and all

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[Jdubrick]

@rm3l looks like the Extension plugin is causing all of the failure. Do you want me to include the fix in this PR, or accept the CI failures?

[rm3l]

@rm3l looks like the Extension plugin is causing all of the failure. Do you want me to include the fix in this PR, or accept the CI failures?

@Jdubrick I noticed that these failures are also occurring on other PRs targeting dev. I've filed https://redhat.atlassian.net/browse/RHDHBUGS-3687 to track this issue. It will be great to fix this issue first (in a separate PR) and make CI pass again, which would unblock your PR. We'll take a look at RHDHBUGS-3687 asap next week. Thanks.