Merge branch 'main' of https://github.com/opendatahub-io/odh-dashboard into feat/autox-file-explorer-row-click

Author: Daniel Duong

.agentready-config.yaml

@@ -115,7 +115,7 @@ documentation:
 
   agent_specific:
     - "AGENTS.md"
-    - "docs/agent-rules/*.md"
+    - ".claude/rules/*.md"
     - "packages/*/AGENTS.md"
 
   technical_docs:

.claude/commands/create-package-doc.md

@@ -0,0 +1,16 @@
+# Create a Package Doc and Register in BOOKMARKS.md
+
+When asked to create documentation for a package, read and follow the full workflow in
+`.claude/skills/docs-create-package/SKILL.md`.
+
+## Quick Reference
+
+- **Verify** the package exists at `packages/$ARGUMENTS/` before doing anything.
+- **Determine package type first** (before creating any files):
+  - Has `frontend/src/` or `bff/` → **full doc** (`packages/$ARGUMENTS/docs/overview.md`)
+  - Tooling-only → **stub only** (README.md; no overview.md)
+- **Research** only files and directories that exist: README, Makefile, package.json, bff/, frontend/src/.
+- **Use** `docs/templates/package-template.md` and follow `docs/guidelines.md` for style.
+- **Omit** template sections that don't apply — no "Not applicable" filler.
+- **Update** `BOOKMARKS.md`: full-doc packages under **Packages > Full Docs**;
+  tooling-only packages under **Packages > Stubs**.

.claude/commands/docs-create.md

@@ -0,0 +1,16 @@
+# Create a New Doc from a Prompt
+
+When asked to create new documentation, read and follow the full workflow in
+`.claude/skills/docs-create/SKILL.md`.
+
+## Quick Reference
+
+- **Parse** `$ARGUMENTS` to identify the subject, doc type, and any files/packages mentioned.
+- **Select a template** if one exists: `docs/templates/frontend-template.md`,
+  `docs/templates/backend-template.md`, or `docs/templates/package-template.md`. For ADRs, check the package's own `docs/adr/`
+  directory. All other types: follow `docs/guidelines.md` directly.
+- **Research** the subject by reading relevant source files before writing.
+- **Determine the output path** by doc type (e.g., `frontend/docs/<area>.md`,
+  `packages/<name>/docs/overview.md`, `.claude/rules/<rule>.md`).
+- No placeholder text (`TODO`, `TBD`, `[Description]`) may remain in the final doc.
+- Omit template sections that don't apply — no "Not applicable" filler.

.claude/commands/docs-update.md

@@ -0,0 +1,15 @@
+# Update Documentation
+
+When asked to update documentation after code changes, read and follow the full workflow in
+`.claude/skills/docs-update/SKILL.md`.
+
+## Quick Reference
+
+- **No arguments**: defaults to uncommitted changes and new untracked files (`HEAD`).
+- **Git reference** (`HEAD~1`, `abc1234`, `abc1234..def5678`): diff-based update for those commits.
+- **`--no-cache`**: skip git diff entirely; rewrite every section of all targeted docs from current
+  source. Add a scope filter to limit the refresh (e.g., `--no-cache backend`,
+  `--no-cache packages/model-registry`, `--no-cache frontend/docs/pipelines.md`).
+- **Diff mode** (default): update only affected sections — do not rewrite unaffected content.
+- Show a summary of proposed changes and ask for confirmation before writing any file.
+- Verify any `BOOKMARKS.md` links to updated files still resolve correctly.

.claude/rules/jira-creation.md

@@ -16,12 +16,12 @@ User requests Jira creation (e.g., "create jira", "make jira tickets", "log a bu
 
 * **Project Key**: `RHOAIENG` (This is the primary project for Dashboard-related issues).
 * **Team Field**:
-  * ID: `customfield_12313240`
-  * Value: `'4158'` (This string value represents the "RHOAI Dashboard" team).
+  * ID: `customfield_10001` (Jira Teams / `atlassian-team`)
+  * Value: `"ec74d716-af36-4b3c-950f-f79213d08f71-1809"` (RHOAI Dashboard team)
 * **Component**: `'AI Core Dashboard'` (This string value should be used for the components field).
 * **Epic Link Custom Field ID** (for Stories/Tasks under an Epic): `customfield_12311140`.
 * **Verify Information**: Always confirm specific details like summaries, descriptions, parent epic keys, and any ambiguous fields with the user.
-* **Team Value is a STRING**: The team field value (`'4158'`) must be passed as a string.
+* **Team Value is a plain string**: Pass `{"customfield_10001": "ec74d716-af36-4b3c-950f-f79213d08f71-1809"}` in `additional_fields`. Do NOT wrap in `{"id": "..."}` — the mcp-atlassian server expects the bare team ID string.
 * **Component is a STRING argument**: The `components` parameter is a direct top-level argument in the tool call.
 * **Iterative Creation**: If multiple issues are requested, create them one by one, confirming success or handling errors for each before proceeding.
 * **Error Handling**: If a tool call fails, analyze the error message. It often provides clues about field formats or missing required fields.
@@ -121,7 +121,7 @@ A defect in the product — e.g., something should be working but it is not. Thi
 * **Bugs are NOT**:
   * New functionality that is unlike existing functionality.
   * A way to "improve" things outside of "expected functionality" - e.g., "A form should submit cleanly and report k8s errors on the form" (expected) vs "A form should scroll to where the error is in the form" (new functionality).
-  * Tests that are broken (these should be Tasks).
+  * Tests that are broken, **including intermittent Cypress/CI flakes** (file as **Task**). A failing or flaky test does not by itself prove a user-facing product defect — use Task for spec/CI stability work unless the report documents reproducible broken **product** behavior.
 
 ### Information Gathering
 
@@ -163,7 +163,7 @@ summary="BUG: [User-provided summary]",
 description="[Formatted markdown string including Description, Steps, Actual, Expected, Reproducibility, and Acceptance Criteria]",
 components="AI Core Dashboard",
 additional_fields={
-	"customfield_12313240": "4158",  # Team: RHOAI Dashboard
+	"customfield_10001": "ec74d716-af36-4b3c-950f-f79213d08f71-1809",  # Team: RHOAI Dashboard
 	"priority": {"name": "..."},     # e.g., "Critical", "Major", "Normal", "Minor" (See Appendix A)
 	"labels": ["..."]                # e.g., ["needs-info"] (See Appendix B for other general labels)
 }
@@ -179,6 +179,7 @@ A user-impact addition/change to the product — e.g., feature work to add parti
 
 * **Stories are NOT**:
   * Test additions (outside of expected tests accompanying new work - these are Tasks).
+  * Cypress/CI **flake** or spec-stability work (these are **Tasks**, not Stories or Bugs).
   * Fixes to defects in the product (these are Bugs).
 
 ### Information Gathering
@@ -212,7 +213,7 @@ summary="STORY: [User-provided summary]",
 description="[Formatted markdown string including Description of enhancement, Acceptance Criteria, and Additional info]",
 components="AI Core Dashboard",
 additional_fields={
-	"customfield_12313240": "4158",  # Team: RHOAI Dashboard
+	"customfield_10001": "ec74d716-af36-4b3c-950f-f79213d08f71-1809",  # Team: RHOAI Dashboard
 	"priority": {"name": "..."},     # e.g., "Major", "Normal" (See Appendix A)
 	"labels": ["enhancement", "..."] # e.g., ["enhancement", "needs-ux"] (See Appendix B for other general labels)
 }
@@ -226,6 +227,8 @@ additional_fields={
 
 A non-user facing change to the product — e.g., add a test, fix a test, or a refactor of code that does not impact the user (code cleanness / DRY / etc).
 
+* **Use Task for:** Cypress or CI **flakes** (intermittent failures, timing, unstable specs), E2E test stabilization, and similar work — consistent with triage rules that keep these as **Task**, not Bug.
+
 * **Tasks are NOT**:
   * New product functionality visible to the user.
 
@@ -259,7 +262,7 @@ summary="TASK: [User-provided summary]",
 description="[Formatted markdown string including Description of task, Acceptance Criteria, and Additional info]",
 components="AI Core Dashboard",
 additional_fields={
-	"customfield_12313240": "4158",  # Team: RHOAI Dashboard
+	"customfield_10001": "ec74d716-af36-4b3c-950f-f79213d08f71-1809",  # Team: RHOAI Dashboard
 	"priority": {"name": "..."},     # e.g., "Normal", "Minor" (See Appendix A)
 	"labels": ["tech-debt", "..."]   # e.g., ["tech-debt", "needs-info"] (See Appendix B for other general labels)
 }
@@ -295,7 +298,7 @@ description="[Formatted markdown string for Story description, AC, and Additiona
 components="AI Core Dashboard",
 additional_fields={
 	"customfield_12311140": PARENT_EPIC_KEY,  # Epic Link field
-	"customfield_12313240": "4158",           # Team: RHOAI Dashboard
+	"customfield_10001": "ec74d716-af36-4b3c-950f-f79213d08f71-1809",  # Team: RHOAI Dashboard
 	"priority": {"name": "..."},
 	"labels": ["enhancement", "..."]
 }
@@ -333,7 +336,7 @@ description="[Formatted markdown string for Task description, AC, and Additional
 components="AI Core Dashboard",
 additional_fields={
 	"customfield_12311140": PARENT_EPIC_KEY,  # Epic Link field
-	"customfield_12313240": "4158",           # Team: RHOAI Dashboard
+	"customfield_10001": "ec74d716-af36-4b3c-950f-f79213d08f71-1809",  # Team: RHOAI Dashboard
 	"priority": {"name": "..."},
 	"labels": ["tech-debt", "..."]
 }
@@ -386,7 +389,7 @@ summary="EPIC: [User-provided Epic Name]",
 description="[User-provided concise, high-level description of what the Epic aims to accomplish]",
 components="AI Core Dashboard",  # Or other relevant components for the Epic
 additional_fields={
-	"customfield_12313240": "4158",  # Team: RHOAI Dashboard
+	"customfield_10001": "ec74d716-af36-4b3c-950f-f79213d08f71-1809",  # Team: RHOAI Dashboard
 	"priority": {"name": "..."},     # e.g., "Major", "Critical"
 	"labels": ["..."]                # (See Appendix B for other general labels)
 }
@@ -424,7 +427,7 @@ These steps are typically for issues already created, but the principles guide f
    * **Informational**: Console output issues, React warnings.
    * *Note*: Set via `additional_fields`: `{"priority": {"name": "Blocker"}}` (or other levels).
 
-3. **Team**: Covered by `customfield_12313240: '4158'`.
+3. **Team**: Covered by `customfield_10001: "ec74d716-af36-4b3c-950f-f79213d08f71-1809"` (plain string, not `{"id": "..."}`).
 
 4. **Post-Creation Status**: API-created issues might start in 'New' or 'Backlog' depending on project workflow. If triaging implies moving from 'New' to 'Backlog', this might require a subsequent `mcp_atlassian_jira_transition_issue` call.
 

.claude/skills/dev-workflow/SKILL.md

@@ -68,7 +68,7 @@ Wait for both the backend (port `4000`) and the frontend dev server (port `4010`
 
 Use the browser MCP's navigation tool to open:
 
-```
+```text
 http://localhost:4010/<path>
 ```
 

.claude/skills/docs-create-package/SKILL.md

@@ -0,0 +1,49 @@
+# Create a Package Doc and Register in BOOKMARKS.md
+
+## Purpose
+
+Scaffold a package doc for any package under `packages/` and register it in `BOOKMARKS.md`.
+
+## Prerequisites
+
+- `docs/guidelines.md` — style and structure rules
+- `docs/templates/package-template.md` — the package doc template
+- `BOOKMARKS.md` — updated automatically by this skill
+
+## Inputs
+
+```text
+$ARGUMENTS — package name (directory name under packages/).
+```
+
+## Workflow
+
+1. **Verify** the package exists at `packages/$ARGUMENTS/`.
+
+2. **Determine package type** (before creating any files):
+   - Has `frontend/src/` or `bff/` → **full doc**
+   - Tooling-only → **stub only** (README.md; no overview.md)
+
+3. **Read** the template (`docs/templates/package-template.md`) and `docs/guidelines.md`.
+
+4. **Research the package** — read only files that exist:
+   - `packages/$ARGUMENTS/README.md`
+   - `packages/$ARGUMENTS/package.json`
+   - `packages/$ARGUMENTS/Makefile`
+   - `packages/$ARGUMENTS/bff/` or `packages/$ARGUMENTS/upstream/bff/`
+   - `packages/$ARGUMENTS/frontend/src/` (browse structure)
+
+5. **For full-doc packages** — create `packages/$ARGUMENTS/docs/overview.md`:
+   - Fill every applicable section with real content
+   - Omit template sections that don't apply — no "Not applicable" filler
+   - Interactions must name the main ODH Dashboard and at least one other dependency
+   - Target under 300 lines (hard limit 500)
+
+6. **Update BOOKMARKS.md**:
+   - Full-doc → **Packages > Full Docs**
+   - Stub → **Packages > Stubs**
+
+## Output
+
+- `packages/$ARGUMENTS/docs/overview.md` (full-doc packages only)
+- `BOOKMARKS.md` updated with the new entry

.claude/skills/docs-create/SKILL.md

@@ -0,0 +1,60 @@
+# Create a New Doc from a Prompt
+
+## Purpose
+
+Generate a new documentation file from a natural language description. Identifies the doc
+type, selects a template if one exists, reads source files, and writes a doc conforming to
+`docs/guidelines.md`.
+
+## Prerequisites
+
+- `docs/guidelines.md` — style and structure rules
+- Templates (when applicable): `docs/templates/frontend-template.md`,
+  `docs/templates/backend-template.md`, `docs/templates/package-template.md`
+
+## Inputs
+
+```text
+$ARGUMENTS — natural language description of what to document.
+```
+
+## Workflow
+
+1. **Parse** `$ARGUMENTS` to identify the subject, doc type, and any specific
+   files/packages mentioned.
+
+2. **Select template** (if one exists):
+   - Frontend area → `docs/templates/frontend-template.md`
+   - Backend module → `docs/templates/backend-template.md`
+   - Package overview → `docs/templates/package-template.md`
+   - ADR → check `packages/<pkg>/docs/adr/` for a template; else use MADR format
+   - All other types → follow `docs/guidelines.md` directly
+
+3. **Read** the template (if selected) and `docs/guidelines.md`.
+
+4. **Research the subject** — read relevant source files:
+   - Frontend area: `frontend/src/pages/<area>/`, `frontend/src/concepts/<area>/`
+   - Backend module: `backend/src/routes/`, `backend/src/`
+   - Package: README, bff/, frontend/src/, Makefile, package.json
+   - Other types: the relevant source code and any existing related docs
+
+5. **Determine output path**:
+   - Frontend area: `frontend/docs/<area-name>.md`
+   - Backend module: `backend/docs/<module-name>.md`
+   - Package overview: `packages/<name>/docs/overview.md`
+   - ADR: `packages/<name>/docs/adr/NNNN-<short-title>.md`
+   - Guide: `packages/<name>/docs/<guide-type>.md`
+   - README: `<directory>/README.md`
+   - Agent rule: `.claude/rules/<rule-name>.md`
+
+6. **Write the doc**:
+   - No placeholder text (`[Description]`, `TODO`, `TBD`)
+   - Omit template sections that don't apply — no "Not applicable" filler
+   - Interactions section must name at least 1 concrete dependency
+   - Target under 300 lines (hard limit 500)
+
+7. **Remind** user to verify links and update BOOKMARKS.md if applicable.
+
+## Output
+
+- A new doc file at the determined path.

.claude/skills/docs-update/SKILL.md

@@ -0,0 +1,72 @@
+# Update Documentation from Git Diff
+
+## Purpose
+
+Update docs to reflect code changes. Identifies affected docs via BOOKMARKS.md and updates
+only the sections that changed.
+
+## Prerequisites
+
+- `docs/guidelines.md` — style and structure rules
+- `BOOKMARKS.md` — index of all maintained docs (source of truth for file-to-doc mapping)
+
+## Inputs
+
+```text
+$ARGUMENTS (optional):
+  --no-cache [scope]   Full rewrite from source. Scope: path, keyword, or omit for all.
+  HEAD~1, abc1234, abc..def   Git reference for diff-based update.
+  (empty)              Defaults to HEAD (uncommitted changes + untracked files).
+```
+
+## Workflow
+
+### A. `--no-cache` mode (full refresh)
+
+1. **Resolve target docs**: If a scope filter is given, match it against BOOKMARKS.md entries.
+   Otherwise, collect every doc listed in BOOKMARKS.md.
+2. **Read `docs/guidelines.md`** and the relevant template for each doc.
+3. **For each doc**: read the doc, read the source code it describes, rewrite every section
+   from current source. Keep under 300 lines (hard limit 500).
+4. **Show summary** and ask for confirmation before writing.
+5. **Verify BOOKMARKS.md** links still resolve.
+
+### B. Diff-based mode (default)
+
+1. **Determine changed files**:
+   ```bash
+   git diff $ARGUMENTS --name-only
+   git ls-files --others --exclude-standard
+   ```
+
+2. **Map changed files to docs** using BOOKMARKS.md as the source of truth:
+   - Read BOOKMARKS.md to get all indexed doc paths and their descriptions.
+   - For each changed file, determine which doc covers that area:
+     - `frontend/src/pages/<area>/**` or `frontend/src/concepts/<area>/**` → the frontend
+       area doc listed in BOOKMARKS.md whose description matches `<area>`.
+     - `backend/src/**` → `backend/docs/overview.md`.
+     - `packages/<name>/**` → `packages/<name>/docs/overview.md`.
+   - Also check non-indexed docs if the change affects env vars, deployment config,
+     OpenAPI specs, webpack/MF config, or auth middleware — search nearby READMEs and
+     `docs/` directories for references to the changed files.
+
+3. **For each affected doc**:
+   a. Read the doc and its template (if template-based).
+   b. Read `docs/guidelines.md`.
+   c. Identify which sections are impacted by the diff.
+   d. Update only affected sections — do not rewrite unaffected content.
+   e. Keep under 300 lines (hard limit 500).
+
+4. **Show summary** of proposed changes and ask for confirmation:
+   ```text
+   The following docs will be updated:
+   - <file>: Section "<name>" — <reason>
+   Proceed? (yes/no)
+   ```
+
+5. **Write** after confirmation. **Verify BOOKMARKS.md** links still resolve.
+
+## Output
+
+- Updated doc file(s) with changed sections.
+- Summary of which sections changed and why.