fix(ui-react): wire the Results step Fetch results button (#110)

[mosoriob]

Closes the client half of #110.

What was wrong

MintThread.tsx rendered MintResults without onPublishResults, and
MintResults.handlePublish returns on its first line when that prop is absent.
So Fetch results made no network request at all — the click did nothing,
silently.

What changed

• publishResults in src/lib/ensemble-manager.ts, alongside the two calls
  Ensemble Manager calls send no Authorization header — localStorage key mismatch #85 moved there, so the Authorization header is still built in one place.
• MintThread passes onPublishResults. The route publishes every execution
  under the subtask, so its path needs the problem statement and task ids —
  thread_info carried task_id alone, and now selects
  task { problem_statement_id }. Confirmed readable at TACC under
  anonymous, so the user role sees it too.
• Each id is encodeURIComponent-ed as one path segment. TACC's ids are opaque
  and unaffected, but the legacy mint://…/… form carries slashes that would
  otherwise split into extra segments and miss the route.
• A failure is shown instead of dropped. handlePublish had no catch, so
  a rejection went nowhere. Registration reaches Tapis and CKAN, so it fails for
  reasons a user cannot guess at.
• .env is now git-ignored — it holds a live data-catalog credential and was
  only one git add away from a public repo.

What this does not fix

Results still will not appear at TACC. The deployment's CKAN API token no longer
authenticates: package_show on the target dataset answers
Access denied: User not authorized — an empty username, so the token is
not resolving to any user. That is why registerOutputs returns 403 and the
route reports it as a 500. Operational fix, tracked on #110.

Measured while diagnosing: the token in .env was issued 2026-05-03T22:52:02,
90 seconds before TACC's first successful output registration at 22:53:57 — so it
is the token that worked, and it has since been invalidated. A freshly minted
token reads the same dataset fine, which rules out nginx stripping the header.

Tests

928 pass (was 921). The MintThread guard asserts the outgoing request, not
the prop, and was checked to fail against the old code — a MintResults-level
test cannot catch this, since it passes the prop itself.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
monorepo	Ready	Preview	Aug 11, 2026 2:11am