Publish open-source LiDMaS+ UI v1.2.2

.gitignore

@@ -68,21 +68,33 @@ paper/figures/
 
 # Paper workflow outputs
 examples/paper_runs/paper_*/results/
+/paper_04/
+/figures/
+examples/paper_runs/paper_05/ibm_credentials.local.json
 
 # LaTeX artifacts and drafts
 *.tex
+/paper_*.bib
 
 # Local manuscript/support files kept out of VCS
 lidmas.bib
 live demo
 us-patent/
+/.local_artifacts/
+/run_lidmas.sh
+/simulator-data-source-reversed.png
 
 # Local PhD proposal workspace
 phd_tubaf/
 
+# Local startup/commercialization notes
+/startup/
+gottesman-startup-web/
+
 # Local slide/PPT workspace artifacts
 .venv_ppt/
 *_talk.pptx
+*_talk*.pptx
 
 # Rust backend build artifacts
 lidmas+/target/
@@ -96,9 +108,10 @@ lidmas+/frontend/*.tsbuildinfo
 lidmas+/design/*.png
 lidmas+/design/*.pdf
 
-# Private LiDMaS+ commercialization workspace
-lidmas+/
+# LiDMaS+ generated/local artifacts
+lidmas+/dashboard_metric_trust_classification.txt
 lidmas+/design/
-lidmas+/frontend/
-lidmas+/README.md
-gottesman-startup-web/
+lidmas+/desktop-swiftui/.build/
+
+# Large local data slices
+/hardware_integration/xanadu/sliced_real_data_1gb/

lidmas+/README.md

@@ -0,0 +1,237 @@
+# LiDMaS+ Open-Source UI
+
+Version target: `v1.2.2`
+
+This folder contains the open-source web UI for LiDMaS+. The UI is built against a backend service contract for decoder studies, replay workflows, validation views, provider metadata, and lab-facing integration sessions.
+
+## Scope
+
+- Provider registry and metadata (`/providers`)
+- Job orchestration metadata (`/jobs`)
+- Run tracking and artifact lineage (`/runs`)
+- Adapter session orchestration for hardware/replay flows (`/integrations/sessions`)
+- Provider-output integrity validation (`/providers/{id}/validate`)
+- Research system log scanning (`/system/logscan`)
+- Health and uptime (`/health`)
+
+Storage and runtime policy are owned by the backend service. The frontend can run against a local or hosted `VITE_API_BASE_URL`.
+
+## Frontend
+
+A React + TypeScript GUI scaffold is available in:
+
+`lidmas+/frontend`
+
+Run it with:
+
+```bash
+cd "lidmas+/frontend"
+npm install
+npm run dev
+```
+
+## Backend Target
+
+```bash
+VITE_API_BASE_URL=http://127.0.0.1:8080/api/v1 npm run dev
+```
+
+Default frontend URL: `http://127.0.0.1:5173`
+Default backend target: `http://127.0.0.1:8080/api/v1`
+
+## API Root
+
+- `GET /api/v1/health`
+
+## paper_04 App Parity Endpoints
+
+LiDMaS+ now exposes app-driven `paper_04` execution and manifest parity checks against the canonical CLI workflow (`./examples/paper_runs/paper_04/run_all.sh`).
+
+- `GET /api/v1/system/paper_04/manifest`
+- `POST /api/v1/system/paper_04/run`
+
+`POST /run` executes the same `paper_04` runner script and returns:
+
+- execution status (`succeeded`, `failed`, `timeout`, or `parity_mismatch`)
+- stdout/stderr tails
+- deterministic artifact manifest hash over key `paper_04/results` outputs
+- optional parity comparison (`compare_with_manifest_hash`)
+
+## Authentication
+
+Most `/api/v1/*` endpoints now require bearer authentication.
+
+Public auth endpoints:
+
+- `POST /api/v1/auth/signup`
+- `POST /api/v1/auth/signin`
+
+Protected auth endpoints:
+
+- `GET /api/v1/auth/me`
+- `POST /api/v1/auth/signout`
+
+Example sign-in:
+
+```bash
+curl -s -X POST http://127.0.0.1:8080/api/v1/auth/signin \
+  -H "content-type: application/json" \
+  -d '{"email":"you@example.org","password":"your-password"}'
+```
+
+Use returned `token` as:
+
+```bash
+-H "authorization: Bearer <TOKEN>"
+```
+
+`POST /api/v1/runs/{run_id}/telemetry` remains open for adapter push workflows.
+
+## Example Flow
+
+1. Register provider:
+
+```bash
+curl -s -X POST http://127.0.0.1:8080/api/v1/providers \
+  -H "content-type: application/json" \
+  -d '{
+    "name":"Xanadu",
+    "kind":"photonic",
+    "supported_formats":["aurora_switch_dir","shot_matrix","count_table_json"],
+    "contact_email":"integration@example.org",
+    "notes":"provider integration test"
+  }'
+```
+
+2. Create job:
+
+```bash
+curl -s -X POST http://127.0.0.1:8080/api/v1/jobs \
+  -H "content-type: application/json" \
+  -d '{
+    "provider_id":"<PROVIDER_UUID>",
+    "dataset_label":"aurora_batch0_qpu5",
+    "decoders":["mwpm","uf","bp","neural_mwpm"],
+    "priority":5
+  }'
+```
+
+3. Validate provider result integrity:
+
+```bash
+curl -s -X POST http://127.0.0.1:8080/api/v1/providers/<PROVIDER_UUID>/validate \
+  -H "content-type: application/json" \
+  -d '{
+    "dataset_label":"aurora_batch0_qpu5",
+    "request_lines":500,
+    "response_lines":500,
+    "request_parse_errors":0,
+    "response_parse_errors":0,
+    "decoder_name_mismatch_count":0,
+    "warning_no_syndrome_count":346
+  }'
+```
+
+4. Create run:
+
+```bash
+curl -s -X POST http://127.0.0.1:8080/api/v1/runs \
+  -H "content-type: application/json" \
+  -d '{
+    "provider_id":"<PROVIDER_UUID>",
+    "dataset_label":"aurora_batch0_qpu5",
+    "decoders":["mwpm","uf","bp","neural_mwpm"]
+  }'
+```
+
+5. Attach artifact:
+
+```bash
+curl -s -X POST http://127.0.0.1:8080/api/v1/runs/<RUN_UUID>/artifacts \
+  -H "content-type: application/json" \
+  -d '{
+    "name":"figure_A_decoder_tradeoff_scatter",
+    "kind":"figure_pdf",
+    "path":"examples/paper_runs/paper_03/results/08_extended_analysis/figures/figure_A_decoder_tradeoff_scatter.pdf",
+    "sha256":"<optional_sha256>"
+  }'
+```
+
+6. Run research log scan:
+
+```bash
+curl -s -X POST http://127.0.0.1:8080/api/v1/system/logscan \
+  -H "content-type: application/json" \
+  -d '{
+    "logs":[
+      {
+        "timestamp":"2026-04-20 15:28:02.341",
+        "level":"ERROR",
+        "message":"Provider-03 returned timeout during parity check replay",
+        "source":"providers/health.rs:156"
+      }
+    ],
+    "max_findings":50
+  }'
+```
+
+7. Start integration session (IBM live example):
+
+```bash
+curl -s -X POST http://127.0.0.1:8080/api/v1/integrations/sessions \
+  -H "content-type: application/json" \
+  -d '{
+    "run_id":"<RUN_UUID>",
+    "adapter_id":"ibm_superconducting_live",
+    "config":{
+      "backend_name":"ibm_kingston",
+      "poll_interval":30
+    }
+  }'
+```
+
+8. Tail integration session logs:
+
+```bash
+curl -s "http://127.0.0.1:8080/api/v1/integrations/sessions/<SESSION_UUID>/logs?tail=100"
+```
+
+## Adapter Session Endpoints
+
+- `GET /api/v1/integrations/sessions`
+- `POST /api/v1/integrations/sessions`
+- `GET /api/v1/integrations/sessions/{session_id}`
+- `POST /api/v1/integrations/sessions/{session_id}/stop`
+- `GET /api/v1/integrations/sessions/{session_id}/logs?tail=200`
+- `POST /api/v1/system/credentials/ibm` (store IBM API key in runtime memory)
+
+Supported adapter ids:
+
+- `ibm_superconducting_live`
+- `ankaa_superconducting_replay`
+- `xanadu_gkp_remote_replay`
+
+IBM auth note:
+
+- Adapter session payloads do not carry API keys.
+- The frontend may submit an IBM key to `/system/credentials/ibm`, where the backend stores it in runtime memory for the current service session.
+- If no runtime key is provided, the backend may use `IBM_QUANTUM_API_KEY` or a saved `qiskit-ibm-runtime` account.
+
+## Troubleshooting
+
+If frontend shows `Backend missing /integrations/sessions (old server)`, your UI is connected to an older backend build.
+Restart the backend service and verify:
+
+```bash
+curl -i http://127.0.0.1:8080/api/v1/integrations/sessions
+```
+
+Expected status is `200` (not `404`).
+
+## Next Steps
+
+- Persist state to PostgreSQL (providers/jobs/runs/artifacts tables)
+- Add auth/roles for provider portal vs researcher views
+- Add async worker queue for real run execution
+- Add run logs/streaming endpoint for GUI live monitor
+- Add schema versioning + provider plugin registry contract

lidmas+/frontend/.env.example

@@ -0,0 +1 @@
+VITE_API_BASE_URL=http://127.0.0.1:8080/api/v1

lidmas+/frontend/.gitignore

@@ -0,0 +1,4 @@
+node_modules/
+dist/
+.DS_Store
+*.tsbuildinfo

lidmas+/frontend/README.md

@@ -0,0 +1,103 @@
+# LiDMaS+ Frontend (React + TypeScript)
+
+This frontend is an open-source research UI scaffold for the LiDMaS+ control plane.
+
+## Features in scaffold
+
+- App shell with top mode chips + persistent sidebar navigation
+- Auth gate overlay (Sign In / Sign Up) before workspace access
+- Post-login IBM onboarding popup for optional live-noise key setup
+- Routed modules:
+  - Dashboard
+  - Providers
+  - Jobs Queue
+  - Runs & Logs
+  - Analysis
+  - Artifacts
+  - Conformance
+  - Settings
+- API integration against Rust backend `/api/v1` endpoints
+- React Query data fetching + mutations
+- Structured components ready for research-workspace expansion
+- Jobs page Adapter Sessions panel:
+  - provider-family launcher (`IBM`, `Ankaa`, `Xanadu`)
+  - automatic adapter selection
+  - optional auto-create run/provider when no run is selected
+  - stop and log-tail actions for active sessions
+
+## Run
+
+```bash
+cd "lidmas+/frontend"
+npm install
+npm run dev
+```
+
+Default frontend URL: `http://127.0.0.1:5173`
+Default backend target: `http://127.0.0.1:8080/api/v1`
+
+To use a different backend:
+
+```bash
+VITE_API_BASE_URL=http://127.0.0.1:8080/api/v1 npm run dev
+```
+
+## Adapter Session Flow
+
+1. Set data mode to `Live API`.
+2. Open `Jobs & Runs`.
+3. Click `+ Start Adapter Session`.
+4. Pick provider family (`IBM`, `Ankaa`, or `Xanadu`) and fill provider-specific fields.
+5. Start session and monitor from `Adapter Sessions` table (status/logs/stop).
+
+Provider-to-adapter mapping is automatic:
+
+- `IBM` -> `ibm_superconducting_live`
+- `Ankaa` -> `ankaa_superconducting_replay`
+- `Xanadu` -> `xanadu_gkp_remote_replay`
+
+IBM authentication behavior:
+
+- After login, frontend can collect IBM API key and submit it to backend runtime memory (`POST /api/v1/system/credentials/ibm`).
+- Backend injects stored key into IBM adapter session process env (`IBM_QUANTUM_API_KEY`).
+- If no key is provided, backend falls back to existing runtime env/saved Qiskit credentials.
+- Missing credentials surface as adapter session failure logs.
+
+Backend auth behavior:
+
+- Frontend sign-in/sign-up is now backed by backend auth endpoints (`/api/v1/auth/*`).
+- API requests include bearer token automatically after successful login.
+
+## paper_04 CLI/IDE Parity Flow
+
+From `Runs` page:
+
+1. Click `Capture CLI Baseline` after generating `paper_04` from CLI (or existing artifacts).
+2. Click `Run paper_04 In LiDMaS+` to execute the same workflow through backend.
+3. Compare returned manifest parity (`MATCH` / `MISMATCH`).
+
+Backend endpoints used:
+
+- `GET /api/v1/system/paper_04/manifest`
+- `POST /api/v1/system/paper_04/run`
+
+## Troubleshooting
+
+If Adapter Sessions shows:
+
+- `Backend missing /integrations/sessions (old server)`
+
+your frontend is pointed to an older backend binary. Restart backend from latest source and verify:
+
+```bash
+curl -i http://127.0.0.1:8080/api/v1/integrations/sessions
+```
+
+Expected response: `200` with JSON array.
+
+## Next recommended additions
+
+1. Auth (OIDC/JWT) and route guards by role.
+2. Real-time logs/telemetry via SSE or WebSocket.
+3. Rich tables and charting for figure/table previews.
+4. Provider mapping editor with schema-diff preview.