Tech debt: Prepare Elemental extension "clone" for extension compatibility tests

[aalves08]

Is your feature request related to a problem? Please describe.

The idea is to prepare an Elemental extension clone for compatibility tests on extensions.

Describe the solution you'd like

• Probably what would work better is to create a new branch off of main in https://github.com/rancher/elemental-ui
• Add all of the extensions points to the code, as per documentation https://extensions.rancher.io/extensions/next/support-matrix#extension-api-support-matrix
• Add all Shell API usages to the code, as per documentation https://extensions.rancher.io/extensions/next/shell-api
• Set a version of 99.99.xxx so that we can publish it to gh-pages but not interfere with the clean-cut versions that are synced with ui-plugin-charts

Describe alternatives you've considered

Additional context

[github-actions]

🎯 Agentic Issue Triage

Summary: This is an internal tech-debt task to prepare a modified clone of the elemental-ui extension that exercises every extension API and Shell API surface point. The resulting "canary" extension will be used to validate extension compatibility across Dashboard versions.

The issue is well-scoped with clear sub-tasks, an existing assignee, and a milestone (v2.15.0). No duplicate open issues were found.

---

📋 Task Breakdown

Based on the issue description, here's a suggested implementation checklist:

• Create a new branch off of main in rancher/elemental-ui (e.g. compat-test or compatibility-tests)
• Audit the [Extension API Support Matrix]((extensions.rancher.io/redacted) and add code stubs for every listed extension point
• Audit the [Shell API docs]((extensions.rancher.io/redacted) and add usage examples for every Shell API entry
• Bump the package version to 99.99.x (e.g. 99.99.0) to isolate from production releases
• Publish the branch to gh-pages as a test artifact
• Verify the extension loads correctly in the Dashboard without conflicts with production elemental-ui versions
• Wire the extension into the Dashboard compatibility CI pipeline (if applicable)

💡 Implementation Notes & Nudges

• Version strategy: Using 99.99.x is a safe sentinel version. Make sure the publishing workflow in elemental-ui is either skipped or overridden for this branch so it doesn't accidentally sync to ui-plugin-charts.
• Minimal logic, maximum API coverage: The clone doesn't need real Elemental functionality — each extension point only needs a minimal stub that proves the API can be registered and invoked without errors.
• Shell API surface: Pay special attention to dynamic APIs (e.g. $store, $plugin, navigation guards) which are more likely to break across versions.
• Tracking drift: Consider adding a comment/TODO in the clone whenever a new entry is added to the support matrix, so it's easy to keep the clone up-to-date.
• Dashboard integration test: After publishing, manually verify the extension loads in a local dev build (API=<rancher-url> yarn dev) with the test extension registered.

🔗 Useful Resources

• [Extension API Support Matrix]((extensions.rancher.io/redacted)
• [Shell API Reference]((extensions.rancher.io/redacted)
• rancher/elemental-ui repository
• [Dashboard Extensions Developer Docs]((extensions.rancher.io/redacted)
• [Creating & Publishing Extensions Guide]((extensions.rancher.io/redacted)

Generated by Agentic Triage for issue #17189 · ◷

[github-actions]

🤖 Issue grooming analysis

This tech-debt issue is well-scoped and ready for triage.

✅ Clear Problem Statement
The title clearly communicates the goal. The description explains the need to prepare an Elemental extension clone specifically for compatibility testing, with the target repository and purpose identified.

✅ Acceptance Criteria
Four concrete, testable checklist items are provided:

• Create a new branch off main in https://github.com/rancher/elemental-ui
• Add all extension points per the [Extension API Support Matrix]((extensions.rancher.io/redacted)
• Add all Shell API usages per the [Shell API docs]((extensions.rancher.io/redacted)
• Set version 99.99.xxx to allow gh-pages publishing without interfering with release versions

✅ Technical Details
The specific target repository (rancher/elemental-ui), relevant documentation links, and the versioning strategy (99.99.xxx) are all identified.

✅ Reproducibility / User Story
This is a feature/tech-debt item with a clear desired end state. The checklist items unambiguously describe the work to be done.

➖ Dependencies
No related issues or PRs are linked, but the external documentation and repository references provide sufficient context.

This analysis was generated automatically based on the repository's grooming checklist.

Generated by Daily Issue Grooming · ◷

[aalves08]

Completed in https://github.com/aalves08/elemental-ui/tree/compatibility-tests-version