feat(apollo-vertex): add Solution Tests data layer (collection-backed hooks) [AGVSOL-3355]

[frankkluijtmans]

Summary

The data layer for the Solution Tests component, split out of #782 so it
can land and be reviewed ahead of the UI. The view depends on this, so the
components PR (#782) is stacked on this branch and merges after it.

This layer is collection-backed: reads stream from the vs-core 2.x Solution Test
collections, and writes go through the standard UiPath Solution Test API
triggers. There is no bespoke adapter or local read cache.

Contents (all under registry/solution-tests/, plus en.json keys):

• Reads — the per-query hooks use-solution-tests,
  use-solution-test-batch-runs, use-solution-test-runs, use-baseline-jobs,
  use-run-results read the UiPathST* collections directly from
  solution.api.collections.solutionTests via useLiveQuery. A dev-only type
  shim in types/optional-deps.d.ts types the name-keyed collection map for this
  repo's own typecheck; consumers rely on their own vs-core typings (nothing is
  shipped to override them).
• Writes — actions.ts (the SolutionTestsActions interface; each method
  rejects on failure), create-actions.ts (createSolutionTestActions builds it
  from triggerBaseUrl + getToken), and the mutation hooks (mutations.ts +
  use-force-stop.ts) run actions through TanStack Query's useMutation.
  Toggle-active is a direct collection .update() in use-solution-tests;
  attachment reads use the uipath-typescript SDK (attachments.ts).
• Wiring — context.tsx (SolutionTestsProvider + context hooks),
  config.ts (SolutionTestsConfig), constants.ts (collection names, trigger
  slugs/paths, labels, thresholds: the single setup file), hooks.ts (barrel).
• Validation — user-messages.ts validates parsed user-message payloads
  with zod.
• types.ts, status-maps.ts, utils.ts, and the en.json translation keys.

New runtime dependencies declared on the registry item: @tanstack/react-query
(mutations) and zod (validation), alongside the existing @tanstack/react-db,
@uipath/vs-core, and @uipath/uipath-typescript.

Consumer interface

The smart container has four inputs, all on SolutionTestsProvider. Reads are
implicit (the UiPathST* collections on the consumer's vs-core solution); writes,
attachment resolution, and presentation are explicit props:

interface SolutionTestsProviderProps {
  // Required. Base URL write-action slugs are appended to (no trailing slash):
  // `{base}/{org}/{tenant}/orchestrator_/t/{folderKey}`.
  triggerBaseUrl: string;
  // Required. Resolves the caller's current bearer token (refreshed near expiry).
  getToken: () => Promise<string | null> | string | null;
  // Required. Resolves a Solution Test entity name (e.g. `UiPathSTRunResults`) to
  // its DataFabric id (GUID); used for attachment reads. vs-core does not expose
  // this mapping, so the consumer supplies it (e.g. from its generated entities).
  getEntityId: (name: string) => string | undefined;
  // Optional per-vertical presentation config.
  config?: SolutionTestsConfig;
  children: ReactNode;
}

interface SolutionTestsConfig {
  // Columns inserted between Test Name and Version. Usually the only customization.
  subjectColumns?: ColumnDef<SolutionTest>[];
  // Turns the test name into a link to its subject.
  getSubjectHref?: (test: SolutionTest) => string | undefined;
  // Subject noun for labels, e.g. { singular: "Loan", plural: "Loans" }.
  subjectNoun?: { singular: string; plural: string };
  // Score at/above which a result passes (pass color + KPI trend line). Default 0.9.
  passThreshold?: number;
}

A consumer is responsible for exactly four things:

1. Reads — ensure the name-keyed UiPathST* collections exist on the vs-core
   solution (solution.api.collections.solutionTests). The hooks query them
   reactively; no further data wiring.
2. Writes — pass triggerBaseUrl + getToken. The provider builds the whole
   write surface (run, delete, force-stop, adopt / update / remove baseline) from
   them. Toggle-active isn't a trigger and needs no wiring. Mutations use
   useMutation, so the container must render under a QueryClientProvider
   (vs-core's solution provider supplies one).
3. Attachments — pass getEntityId. DataFabric addresses entities by GUID,
   not name, and vs-core doesn't surface the name-to-GUID mapping, so attachment
   reads (expected / actual output, evaluator results) need the consumer to
   resolve it (typically from its generated entities map).
4. Presentation — pass config.subjectColumns (and optionally
   getSubjectHref / subjectNoun / passThreshold) to flavor the table for the
   vertical.

Everything else (evaluator labels, status labels, the poll interval) is
hard-coded in constants.ts. The pass threshold defaults to 0.9 there but is
overridable via config.passThreshold.

Testing

pnpm typecheck, pnpm lint, pnpm format, and pnpm registry:build pass.

👨 Generated with Kluijt Code

[github-actions]

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

Project	Deployment	Review	Updated (PT)
apollo-design	🟢 Ready	Preview, Logs	Jun 17, 2026, 07:47:41 AM
apollo-docs	🟢 Ready	Preview, Logs	Jun 17, 2026, 07:47:41 AM
apollo-landing	🟢 Ready	Preview, Logs	Jun 17, 2026, 07:47:41 AM
apollo-vertex	🟢 Ready	Preview, Logs	Jun 17, 2026, 07:47:41 AM

[github-actions]

Dependency License Review

• ✅ 1926 package(s) scanned
• ✅ No license issues found
• ⚠️ 2 package(s) excluded (see details below)

License distribution

License	Packages
MIT	1696
ISC	89
Apache-2.0	55
BSD-3-Clause	27
BSD-2-Clause	23
BlueOak-1.0.0	8
MPL-2.0	4
MIT-0	3
CC0-1.0	3
MIT OR Apache-2.0	2
(MIT OR Apache-2.0)	2
Unlicense	2
LGPL-3.0-or-later	1
Python-2.0	1
CC-BY-4.0	1
(MPL-2.0 OR Apache-2.0)	1
Unknown	1
Artistic-2.0	1
(WTFPL OR MIT)	1
(BSD-2-Clause OR MIT OR Apache-2.0)	1
CC-BY-3.0	1
0BSD	1
(MIT OR CC0-1.0)	1
MIT AND ISC	1

Excluded packages

Package	Version	License	Reason
@img/sharp-libvips-linux-x64	1.2.4	LGPL-3.0-or-later	LGPL pre-built binary, not linked
khroma	2.1.0	Unknown	MIT per GitHub repo, missing license field in package.json

[Copilot]

Pull request overview

Introduces the initial data-layer foundation for the Solution Tests registry item in Apollo Vertex (adapter contract, DataFabric-backed default adapter, context/config wiring, and TanStack Query hook), plus supporting types/utilities and new English i18n keys needed by the upcoming UI.

Changes:

• Added SolutionTestsAdapter contract and a default DataFabric/Orchestrator-backed adapter factory (createDataFabricAdapter).
• Added provider/context + resolved presentation config, and a TanStack Query-based hook for reads/mutations with polling support.
• Added shared view-model types, status-to-badge maps, user-message parsing helpers, and new en.json translation keys.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
apps/apollo-vertex/registry/solution-tests/adapter.ts	Defines the adapter interface + mutation/attachment types used by the Solution Tests view.
apps/apollo-vertex/registry/solution-tests/config.ts	Defines per-vertical presentation configuration and default resolution.
apps/apollo-vertex/registry/solution-tests/context.tsx	Provides adapter/config via React context for deep component access.
apps/apollo-vertex/registry/solution-tests/data-fabric-adapter.ts	Implements a default adapter over a minimal “data port” for DataFabric queries + triggers/functions.
apps/apollo-vertex/registry/solution-tests/hooks.ts	Documents a future vs-core collection-backed hook API (stubbed, not wired).
apps/apollo-vertex/registry/solution-tests/status-maps.ts	Maps numeric statuses to badge variants / classes for display.
apps/apollo-vertex/registry/solution-tests/types.ts	Declares domain-neutral Solution Tests view model types + default label maps.
apps/apollo-vertex/registry/solution-tests/use-solution-tests-data.ts	Adds TanStack Query reads/mutations and run polling behavior for the view.
apps/apollo-vertex/registry/solution-tests/user-messages.ts	Adds parsing + severity helpers for user-messages payloads.
apps/apollo-vertex/registry/solution-tests/utils.ts	Adds formatting helpers and small run/result utilities.
apps/apollo-vertex/locales/en.json	Adds new English translation keys required by the Solution Tests feature.

[Copilot]

Pull request overview

Copilot reviewed 12 out of 12 changed files in this pull request and generated 5 comments.

[Copilot]

Pull request overview

Copilot reviewed 18 out of 19 changed files in this pull request and generated 7 comments.

[Copilot]

Pull request overview

Copilot reviewed 20 out of 21 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 20 out of 21 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 19 out of 20 changed files in this pull request and generated 1 comment.

[RobinMennens-UiPath]

A few changes requested, focused on configurability and one likely-inert filter. Inline comments below. Overall the move-over is clean and domain-neutral (no FINS-specific coupling found); the main asks are around making per-vertical values configurable and confirming the run-results filter actually works against the raw collection.

[Copilot]

Pull request overview

Copilot reviewed 19 out of 20 changed files in this pull request and generated 4 comments.

[github-actions]

📊 Coverage by package

No JS/TS source changes detected under packages/* or web-packages/* for this PR.

Package	Overall	New-line coverage
@uipath/apollo-core	9.0%	—
@uipath/apollo-react	34.8%	—
@uipath/apollo-wind	38.2%	—
@uipath/ap-chat	85.8%	—

_{"Overall" is each package's own coverage.include scope (e.g. apollo-core instruments only scripts/, not its generated tokens, so its % is not whole-package). "Untracked" = changed lines with no coverage instrumentation (types, config, generated code). Packages with no vitest config are omitted.}

[RobinMennens-UiPath]

Re-reviewed after the rebase. All four requested changes are addressed:

• PASS_THRESHOLD is now passThreshold?: number on SolutionTestsConfig (defaults via DEFAULT_PASS_THRESHOLD).
• isBaselineJobResult now joins UiPathSTJobs to read JobRole off the bare id, so the previously inert entry-point filter actually drops rows now.
• detectFailure unwraps output_data once and checks status_code/error/message against the same object, covering both contracts.
• Constant/variable renames done (RUN_TESTS_SLUG, AUTOMATION_FUNCTIONS_SLUG, AUTOMATION_FUNCTION_PATH, transaction).

Also sanity-checked the broader restructure (react-query useMutation adoption, removal of the collections.ts boundary helper in favor of typed stubs, entity-id plumbing for attachments). pnpm typecheck and pnpm lint both pass locally. LGTM.

[Copilot]

Pull request overview

Copilot reviewed 19 out of 20 changed files in this pull request and generated 4 comments.

[KokoMilev]

Copilot woke up 😆 , let me know when you resolve its comments, otherwise it looks good to me.