Skip to content

Confirm SUBSIDE can live without the un-ported Lit screens #69

Closed

Description

@mosoriob

Question

Replacing the Lit UI at mint.tacc.utexas.edu removes these screens for SUBSIDE users, because they do not exist in ui-react and were never in the SOW's scope:

  • Analysis, Emulators, Messages
  • models-compare, models-calibrate, models-cromo
  • Thread Visualize and Summary steps
  • model-view (the 3,256-LOC model detail screen)

Max knows the answers here — this is a short conversation, not an outreach to TACC. Resolve it by walking the list and recording, per screen, whether SUBSIDE uses it and what happens when it disappears.

Several are dead or stubbed in the Lit app anyway: Messages lost its backend when Firebase was removed, and several Analysis screens are placeholders. Say so explicitly per screen rather than dismissing the list wholesale — the resolution is the record that T9 flips against.

Outcome is one of: (a) none are needed, flip freely; (b) a specific screen is needed, which either graduates a scoping conversation or forces T9 to keep Lit reachable at a second path.

Activity

  1. self-assigned this
    on Aug 8, 2026
  2. mosoriob commented on Aug 8, 2026

    @mosoriob
    ContributorAuthor

    Resolution

    Outcome (a): none of the un-ported screens are needed. The flip is free.

    Walked the list against both codebases rather than from memory. Two of the ticket's own
    premises turned out to be wrong, so the per-screen record below supersedes the question body.

    Per screen

    Screen Finding
    Messages Already dead in Lit. ui/src/screens/messages/actions.ts is entirely commented-out Firebase (/* TODO: Add this to graphql), and messages-post.ts is 0 bytes. No loss.
    Analysis — aggregate, compare, visualize Placeholders. Each renders a single <p>This page is in progress</p>. No loss.
    Analysis — report 502 LOC of real code, but the "Prepare Reports" nav link is commented out at ui/src/app/mint-app.ts:350, so it is URL-only today. Max confirms commenting the link out was the retirement. No loss.
    models-calibrate Placeholder, single paragraph. No loss.
    Emulators 1097 LOC of real code, but no nav link and a hardcoded CYCLES default. Leftover from a different project, not SUBSIDE. No loss.
    models-compare, models-cromo 581 + 745 LOC, real. SUBSIDE does not use either. No loss.
    Thread Summary Already ported — ui-react/src/pages/modeling/thread/MintSummary.tsx, wired at MintThread.tsx:309, a 1:1 port. The ticket listed this as missing; it is not.
    Thread Visualize Genuinely un-ported (Lit mint-visualize.ts, 320 LOC). But it only iframes URLs from getVisualizationURLs, which needs a MINT visualization service SUBSIDE does not have — so it renders empty in Lit too. Parity, not a gap. Not flagged on handover.
    model-view Lit's 3,256-LOC model/version explorer detail is not ported. React covers configuration detail via ConfigurationDetail at /modelconfigurations/:slugid. SUBSIDE users arrive through the configure workflow, not the explorer browse surface, so this covers the SOW. No loss.

    Consequences for the rest of the map

    The conversation also settled the deployment strategy, because outcome (a) removed the only
    user-facing reason to stage the rollout:

    • No parallel deploy. There are no users on Lit at TACC, so there is nothing to deploy
      beside. This invalidates the premise of Smoke-test ui-react on a Vercel preview against TACC's real Hasura and CKAN #76, which is rescoped to a Vercel smoke test.
    • Vercel is the test surface. Real-data behaviour is proven on a Vercel preview against
      TACC's Hasura and CKAN; production is then upgraded directly.
    • Lit stays running but unrouted at upgrade time. The production upgrade points
      mint.tacc.utexas.edu at ui-react and leaves the ui Helm component deployed but off the
      route — the only undo available if the client hits something during sign-off. The component
      is removed after sign-off, which graduates out of the map's fog as its own ticket.

    #77 no longer has to decide whether to keep Lit reachable at a second path: it does not, and
    the fallback is an unrouted deployment rather than a second URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

wayfinder:grillingWayfinder ticket: decision reached by conversation (HITL)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions