verify

name	verify
description	Verify LLM Prompt Builder changes end-to-end by serving the built dist/index.html from a mock SAS Viya server and driving it with Playwright against the system Edge browser. Use after changing LLM-Prompt-Builder source to observe the real UI instead of only building.

Verify the LLM Prompt Builder without a live SAS Viya

The app is a single-file browser bundle that calls SAS Viya REST APIs on its own origin (viyaHost defaults to window.location.origin). That makes it fully drivable against a local mock: serve dist/index.html from a Node server that also implements the handful of Viya endpoints the app calls.

Recipe

1. Build: npm run build in LLM-Prompt-Builder/ (runs tsc --noEmit first; the committed dist/index.html must match a fresh build or the verify-prompt-builder.yml CI check fails).
2. Start the mock (records every request; GET /__log returns them, POST /__reset clears): node mock-server.js <abs-path-to>/LLM-Prompt-Builder/dist/index.html (serves on http://localhost:4173 — see mock-server.js next to this file).
3. Drive with Playwright using the system Edge (no browser download needed): npm i playwright in a scratch dir, then chromium.launch({ channel: 'msedge', headless: true }). verify.js next to this file covers the deletion flows end-to-end and is a good template for new flows.
4. Open the app with config in the URL (no VA embed needed): http://localhost:4173/?modelRepositoryID=repo-1&llmProjectID=llm-proj&SCREndpoint=http://localhost:9/scr

Endpoints the app needs mocked at minimum

• GET /identities/users/@currentUser
• GET /modelRepository/projects (project dropdown, filter Prompt-Engineering)
• GET /modelRepository/projects/{llmProjectID}/models (plus the same URL with filter=eq(tags,'deprecated') returning empty) and per-LLM GET /modelRepository/models/{id}/contents → an options.json entry whose fileUri + /content returns e.g. { "temperature": { "default": 0.7 } } — without this the whole builder fails to load
• GET /modelRepository/projects/{id}/models for the selected project
• GET /modelRepository/models/{id}/contents → Prompt-Experiment-Tracker.json entry; its {fileUri}/content returns the PETRow[] fixture
• POST /relationships/relationships, GET /decisions/flows/{id}
• Save flow: POST .../modelVersions (200 JSON), DELETE .../contents/{id} (204), POST .../contents?... (201 JSON, multipart body)

Gotchas

• Element ids are prefixed with the config id (default LPB) and the pane id app: dropdowns are #LPB-project-dropdown / #LPB-prompt-dropdown, the tracker container is #app-obj-LPB-pet, run accordions #app-obj-LPB-pet-{i} (newest run first in the DOM).
• Bootstrap modals: the .show class disappears at the START of the hide transition, but promise resolution / button re-enabling happens on hidden.bs.modal (~300ms later) — poll instead of asserting immediately. Escape only dismisses after the fade-in finished (focus trap active); wait for document.activeElement to be the modal before pressing it.
• The run-header system prompt element id contains a pre-existing typo: ...-run-systenPrompt.