Repository navigation
v1.3.0 — Named CI setup and direct model search
New CI setup now starts with a named task and direct search over verified eligible models. Users explicitly choose a provider deployment and source observation; comparable benchmark recommendations stay separate from supported unranked choices and empty runnable sets. Explorer links carry exact model/evidence intent through sign-in, draft restoration and project editing.
Add Python/Node test-environment inputs, diagnosis stage/log inputs and the optional repair scope. Profile changes invalidate the previous pick visibly; saves and restores revalidate exact selections. Reuse Jenkins metadata with versioned commands and in-memory one-time tokens. Same-profile re-picks preserve configuration/preferences. Legacy history, edit workflows and /legacy-setup remain compatible; Other authoring belongs to B14.
Validation: 143 unit tests, 21 integration tests, 14 named-setup desktop/mobile checks, 12 catalog checks, and 12 legacy/public browser checks passed. Typecheck, lint (14 existing warnings; no errors) and production build passed. Visual inspection fixed mobile fieldset overflow and unnecessary navigation snapshots; focus behavior is preserved. Browser success paths use synthetic verified fixtures only. No pending integration is activated and no provider call or deployment occurred.
Release: frontend 1.2.0 → 1.3.0 MINOR for compatible named setup/search workflows. Requires the B13 backend additive filters/setup seam (1.12.0). Publishing does not update runtime pins.
Published image verified anonymously: ghcr.io/steve-droid/driftplain-frontend:1.3.0 at sha256:0de414edf0e485a8783694518ebf8fb336ee1c985cfc21508100add43cd587cc. OCI revision/version match reviewed main. Release workflow 35973040252 succeeded. The subsequent immutable 1.3.1 release only corrects availability wording.