AIFACTORY-FEAT-169: UI kit: the token work and the Factory compositions the alignment gate ranks first¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
A design artefact, not a tracker
This backlog is generated from model/backlog/ and validated against the architecture model. No work item exists in any tracker, and no item carries a date, an estimate or an assignee (ADR-0029).
Epic Ecosystem component extensions · Increment I3 Studio · State elaborated · Route frontend-developer · Phase before development · Build order 33 of 185 (Templates and libraries)
Before development
Template or library work: every task of this feature changes a template or a shared library the Factory builds on, and it lands before the Factory's own repositories of I3 are developed. The mark travels with every task (tag phase:before-development).
The UI kit's own alignment gate (F01) against the design prototypes lists what the Studio screens need and the kit does not have: density that does not reach the cs-* spacing and type tokens, no named elevation scale, no motion tokens; the P0 primitives JsonViewer, DiffViewer and LogStream; and the P0 Factory compositions FactoryRunCard, AgentExecutionGraph, QualityGatePanel, TraceViewerPanel, ArtifactExplorer, ArtifactDiffPanel, ArtifactLineageGraph and HumanReviewQueue. The state-family, run-timeline and approval components are FEAT-101; this feature closes the rest of the P0 list and the adapter conformance of every new component across the Tokens, Flowbite and DaisyUI adapters. Component: Blazor Shell + MFEs + UIKit (extend).
| Delivers | — |
| Stubs | — |
| Realizes | components: cmp-blazor-shell adrs: ADR-0007, ADR-0026 |
| Requirements | — |
| Depends on | — |
| Sources | model/components.yaml, ConnectSoft.Blazor.UIKit/docs/F01-alignment-gate.md, ConnectSoft.Blazor.UIKit/docs/F02-uikit-coverage.md |
AIFACTORY-US-327: UI kit: the density bridge, the elevation scale and the motion tokens hold in the light, dark and accessibility variants and are locked by a test¶
enabling · persona asset-maintainer
As an asset maintainer, I want the three token gaps of the alignment gate to be closed in every variant of the token spine and kept closed by a test, so that a Studio screen changes density, depth and motion through tokens in every theme.
The alignment gate of the UI kit (the F01 page of its documentation) lists three token gaps as its first work: the density attribute reassigns only the older spacing, font size and radius variables and not the cs-* spacing, type and radius tokens; there is one cs-* shadow and no named elevation scale; and there are no cs-* motion tokens for fast, base and slow. The coverage page of the kit (its F02 page) records the three as closed, with the elevation and motion tokens in the cs-* token file and the Tailwind preset and the density bridge in the density token file. The ledger does not say whether the new tokens hold in the dark register and in the accessibility variants, and no test keeps them. This PBI confirms what the ledger records and completes what the confirmation finds missing. A token test reads the token files and asserts that the elevation scale from extra small to extra large and the three motion tokens are defined in the light register, in the dark register and in the accessibility variants, that each density value reassigns the cs-* spacing, type and radius tokens, and that no component stylesheet of the kit uses a raw shadow or a raw duration where a token exists. The motion tokens resolve to no motion under the reduced-motion preference. The token page of the documentation and a gallery route show the three families in every variant. A family the test finds missing in a variant is added in that variant, and the coverage page is corrected to what the test proves.
Acceptance criteria
| AC1 | Given the token files of the kit, when the token test runs, then the named elevation scale and the fast, base and slow motion tokens are defined in the light register, the dark register and the accessibility variants, and removing one of them from one variant fails the test with the token and the variant named (ADR-0007: the modules of the Studio share one design system; model/components.yaml names the token work as a need of this component). |
| AC2 | Given an element with each value of the density attribute, when its computed style is read in a component test, then the cs-* spacing, type and radius tokens differ between the values as the density token file defines, and under the reduced-motion preference the motion tokens resolve to no motion (ADR-0007: the modules share one design system, so density is a token concern of the kit; NFR-15 sets the accessibility level the motion behaviour is tested against; FUX-12). |
| AC3 | Given the documentation and the gallery of the kit, when the token page and the token gallery route are opened, then they show the elevation, motion and density families in the light, dark and accessibility variants, and the coverage page of the kit states for each family the test that proves it (ADR-0007, docs/architecture/ecosystem-composition.md). |
| Traces: adrs | ADR-0007 |
| Traces: requirements | FUX-12 |
| Relates: nfrs | NFR-15 |
| Sources | model/components.yaml, model/templates.yaml, model/traceability/nfr.yaml, model/traceability/fux.yaml, docs/architecture/ecosystem-composition.md, docs/architecture/adr/0007-blazor-mfe-studio-frontend.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-616 Density bridge, elevation scale and motion tokens |
implementation | The density attribute reassigns the cs-* spacing, type and radius tokens; a named cs-* elevation scale and the fast, base and slow motion tokens exist in the token spine and in the dark and accessibility variants, a variant the token test finds incomplete is completed, and the motion tokens resolve to no motion under the reduced-motion preference. |
ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1398 Token test over the spine, the dark register and the accessibility variants |
fixture | The unit test project of the kit holds a token test that parses the token files and asserts the elevation scale, the motion tokens and the density reassignment in every variant, and a scan that fails when a component stylesheet uses a raw shadow or duration where a token exists. | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1399 Token page, token gallery route and coverage page state the three families |
documentation | The token page of the documentation and a gallery route show the elevation, motion and density families in the light, dark and accessibility variants, and the coverage page names the token test as the evidence of each family. | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1400 Verify the token families in every variant |
verification | Run the token test and the density component tests, then remove a motion token from the dark register and rerun; the first run passes and the second fails with the token and the variant named, which proves AC1 to AC3 of AIFACTORY-US-327 (ADR-0007). | ConnectSoft.Blazor.UIKit |
AIFACTORY-US-328: UI kit: JsonViewer, DiffViewer and LogStream carry their accessibility contracts, the behaviours the Studio needs and render under the Tokens, Flowbite and DaisyUI adapters¶
enabling · persona asset-maintainer
As an asset maintainer, I want the three operational primitives to be complete for the artifact, diff and log views of the Studio, so that no Studio microfrontend builds its own viewer for a document, a diff or a stream.
The alignment gate of the kit ranks four new primitives first, and three of them are what the artifact, change and log views of the Studio are made of: JsonViewer, DiffViewer and LogStream. The coverage page records the three as closed with a gallery route for operational data and component tests named after each primitive. The ledger does not record an accessibility contract for them, does not say which behaviours they have, and does not show them under the three adapter packages of the kit. This PBI confirms what exists and completes each primitive to what the Studio needs. JsonViewer renders a document as a collapsible tree that is operated by keyboard, keeps large documents responsive by rendering only what is expanded, and never evaluates content. DiffViewer renders a unified and a side-by-side diff of two texts, announces additions and removals as text and not by colour alone, and lets a reader move between changes by keyboard. LogStream follows an appended stream, pauses and resumes following, searches within the received lines and announces new lines politely so that a screen reader is not flooded. Each primitive has a page in the documentation with its parameters and its accessibility contract, renders in right-to-left direction, and is rendered by a test under the Tokens, the Flowbite and the DaisyUI adapter. The adapter conformance suite of the kit, which covers the dialog, toast and validation adapters, keeps passing for the three adapters. The primitives take their data through parameters and make no HTTP call.
Acceptance criteria
| AC1 | Given the three primitives, when their component and accessibility tests run, then JsonViewer expands and collapses by keyboard, DiffViewer renders a unified and a side-by-side diff with additions and removals given as text, and LogStream follows a stream, pauses, resumes and searches, each with the roles and labels of its documented accessibility contract (NFR-15: WCAG 2.2 AA and keyboard operation; FUX-12: accessible journeys; model/ux/screens.yaml lists the screens artifacts and run-detail with the read models these views show). |
| AC2 | Given each primitive, when the render matrix test runs, then it renders without error and with the same accessible structure under the Tokens, the Flowbite and the DaisyUI adapter and in right-to-left direction, and the adapter conformance suite of the kit passes for the three adapters (ADR-0007: one design system for every module; NFR-15 for the right-to-left direction; model/components.yaml names the primitives as a need of this component). |
| AC3 | Given the documentation and the gallery of the kit, when the pages of the three primitives are opened, then each states its parameters, its behaviours and its accessibility contract and has a gallery route, and the kit library holds no reference to a shell or microfrontend project and no HTTP client (ADR-0007, docs/architecture/ecosystem-composition.md). |
| Traces: adrs | ADR-0007 |
| Traces: requirements | FUX-12 |
| Relates: nfrs | NFR-15 |
| Depends on | AIFACTORY-US-327 |
| Sources | model/components.yaml, model/ux/screens.yaml, docs/architecture/ecosystem-composition.md, model/traceability/nfr.yaml, model/traceability/fux.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-617 P0 primitives JsonViewer, DiffViewer and LogStream |
implementation | The three primitives exist with their accessibility contracts, documentation pages, gallery routes and component tests; DiffViewer renders a unified and a side-by-side diff with changes given as text; LogStream follows a stream with pause, resume and search and polite announcements; JsonViewer is a keyboard-operated collapsible tree; each renders under the three adapters and in right-to-left direction and takes its data through parameters. | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1401 Render matrix and accessibility tests of the three primitives |
fixture | The unit test project holds a render matrix that renders each primitive under the Tokens, Flowbite and DaisyUI adapters and in both directions and compares the accessible structure, and accessibility tests for the keyboard paths, the text form of changes and the announcement of new log lines. | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1402 Verify the behaviours, the accessibility contracts and the three adapters |
verification | Run the tests of AIFACTORY-TASK-1401 and the adapter conformance suite; every primitive passes under the three adapters and in both directions, which proves AC1 to AC3 of AIFACTORY-US-328 (ADR-0007, NFR-15). | ConnectSoft.Blazor.UIKit |
AIFACTORY-US-329: UI kit: the eight Factory compositions take the shapes and state families of the UX model through parameters and render under the three adapters¶
enabling · persona asset-maintainer
As an asset maintainer, I want the Factory compositions of the kit to accept what the Studio screens receive from their read models, so that a Studio microfrontend binds a screen model to a composition without an adapter layer of its own.
The alignment gate of the kit names eight Factory compositions as its first new compositions: FactoryRunCard, AgentExecutionGraph, QualityGatePanel, TraceViewerPanel, ArtifactExplorer, ArtifactDiffPanel, ArtifactLineageGraph and HumanReviewQueue. The coverage page records all eight as closed with one gallery route for the Factory compositions and one shared component test class. They were built against the design prototypes; the screens of the Studio are defined by the UX model of this repository, where every screen names its read models and its state families, and the state families fix the values a run, an approval, an asset, a delivery or a source can show. This PBI binds the compositions to that model. Each composition takes its data through typed parameters whose state values are the values of the matching family of model/ux/states.yaml, so a run shows the run family, a review item the approval family and every panel the freshness family of its source; a state is always given as text beside its colour. A composition makes no HTTP call and holds no subscription; the microfrontend passes it the screen model it received. A mapping table on the coverage page names, for each composition, the screens of model/ux/screens.yaml that use it. Each composition has a documentation page with its parameters and its accessibility contract, its own component tests in place of the single shared class, loading, empty and error states, and a render under the Tokens, Flowbite and DaisyUI adapters and in right-to-left direction. The state-family, run-timeline and approval components belong to the Studio shell feature of this epic and are not part of this PBI.
Acceptance criteria
| AC1 | Given the eight compositions, when their parameter models are compared with model/ux/states.yaml, then every state parameter accepts exactly the values of its family, an unknown value is rendered as unknown and never as a success, and every state is given as text beside its colour (model/ux/states.yaml defines the families and their values; NFR-15 for a state that is not given by colour alone; model/ux/screens.yaml names the read models and the state families of each screen). |
| AC2 | Given each composition, when its component tests and the render matrix run, then it renders its loaded, loading, empty and error states under the Tokens, the Flowbite and the DaisyUI adapter and in right-to-left direction, and a test fails when a composition references an HTTP client or a shell or microfrontend project (ADR-0007, NFR-15 for the right-to-left direction, model/components.yaml names the Factory compositions as a need of this component). |
| AC3 | Given the coverage page and the documentation of the kit, when they are read, then a table maps each of the eight compositions to the screens of model/ux/screens.yaml that use it, and each composition has a page with its parameters and its accessibility contract and a gallery route (FUX-12: documented views, states and permissions; model/ux/screens.yaml). |
| Traces: adrs | ADR-0007 |
| Traces: requirements | FUX-12 |
| Relates: nfrs | NFR-15 |
| Depends on | AIFACTORY-US-327, AIFACTORY-US-328 |
| Sources | model/components.yaml, model/ux/screens.yaml, model/ux/states.yaml, model/ux/prototype-alignment.yaml, model/traceability/nfr.yaml, model/traceability/fux.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-1403 Parameter models of the eight compositions in the vocabulary of the UX model |
contract | Each of the eight compositions has a typed parameter model whose state values are the values of its family in model/ux/states.yaml, with an explicit unknown value; the coverage page of the kit holds the table that maps each composition to the screens of model/ux/screens.yaml that use it. | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-618 P0 Factory compositions |
implementation | FactoryRunCard, AgentExecutionGraph, QualityGatePanel, TraceViewerPanel, ArtifactExplorer, ArtifactDiffPanel, ArtifactLineageGraph and HumanReviewQueue exist as compositions over the kit primitives, bound to the parameter models of AIFACTORY-TASK-1403, with loading, empty and error states, state given as text, documentation pages, gallery routes and no HTTP call. | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1404 Component tests per composition and the three-adapter render matrix |
fixture | The single shared composition test class is split into one test class per composition that covers the loaded, loading, empty and error states and the text form of every state; the render matrix renders each composition under the three adapters and in both directions; an architecture test forbids an HTTP client and a shell or microfrontend reference in the kit. | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1405 Verify the state vocabulary, the states and the adapters of the compositions |
verification | Run the tests of AIFACTORY-TASK-1404 and the snapshot comparison with model/ux/states.yaml; every composition passes under the three adapters and the state enumerations equal the families, which proves AC1 to AC3 of AIFACTORY-US-329 (FUX-12, model/ux/states.yaml). | ConnectSoft.Blazor.UIKit |
AIFACTORY-US-330: UI kit: the components package is built, tested and published to the ConnectSoft feed, proven with the adapter packages on the feed and pinned by the two templates of the shell family¶
evidence · persona asset-maintainer
As an asset maintainer, I want proof that the kit with the token work, the primitives and the Factory compositions is on the feed under one version, so that the shell template, the microfrontend library template and the Studio pin the same published kit.
This PBI is the publication proof of the feature. The kit is a library that the shell template, the microfrontend library template, the sample templates and the Studio consume by a version pin, and the integration checklist of the microfrontend library template records that the templates pin different versions of it. The pipeline of the kit restores, checks deprecated and vulnerable packages, builds, tests with a coverage threshold, packs, verifies that the package ships its web assets as static web assets only, and pushes to the feed. It packs the components package only: the Tokens, Flowbite and DaisyUI adapters ship from their own repositories, which are not repositories of this component, so this PBI publishes no adapter package and changes none. The proof adds what a consumer needs. The publication step runs only after the token test, the render matrix, the accessibility tests and the adapter conformance suite pass, pushes the components package ConnectSoft.Blazor.UIKit and refuses a version that is already on the feed. A probe proves the package from the side of a consumer: a clean Blazor host with the ConnectSoft feed as its only source restores the published kit version together with the version of each adapter package that is already on the feed, each adapter in turn, and renders a page with the three primitives and the eight compositions in the light and the dark theme and in right-to-left direction. The published version, what it carries and the adapter versions it was proven with are recorded on the release notes page of the kit. The last leg is the pin. The central package file of the shell template pins the published version and the template republishes through its gate; then the microfrontend library template pins the same version. The order matters because the pin check of the shell family (AIFACTORY-TASK-1382) has one reference, the pins of the latest published shell template package; the release notes page tells a maintainer which version to move to and is not a reference of the check. A new primitive or composition that needs a change inside an adapter cannot be delivered here, because the three adapter repositories would have to join the component first; that case is raised to the owner. This is an evidence PBI: a library feature has no scenario, so the proof names what it shows through traces.adrs and its sources.
Acceptance criteria
| AC1 | Given the pipeline of the kit after the work of this feature, when it runs, then the components package ConnectSoft.Blazor.UIKit is built, tested, packed and pushed to the ConnectSoft feed only after the token test, the render matrix, the accessibility tests and the adapter conformance suite pass, the pipeline packs and pushes no adapter package, and a version that is already on the feed is refused with the reason (ADR-0007, model/backlog/epics.yaml states publication before consumption as the completion of the epic). |
| AC2 | Given a clean probe host with the ConnectSoft feed as its only package source, when it restores the published kit version with the Tokens, the Flowbite and the DaisyUI adapter package versions already on the feed, each in turn, then a page with the three primitives and the eight compositions renders in the light and the dark theme and in right-to-left direction with no missing static web asset (ADR-0007: one design system shared by every module; model/templates.yaml lists the templates that pin the kit). |
| AC3 | Given the release notes page of the kit, when a maintainer of a consuming template reads it, then it names the published version, the token families, the primitives and the compositions the version carries and the adapter package versions it was proven with; and the central package files of the shell template and of the microfrontend library template pin that version, both solutions build and pass their tests, and the pin check of both pipelines is green against the republished shell template package (ADR-0007, docs/architecture/ecosystem-composition.md). |
| Traces: adrs | ADR-0007 |
| Depends on | AIFACTORY-US-327, AIFACTORY-US-328, AIFACTORY-US-329, feature:component-blazor-shell-template-studio |
| Sources | model/components.yaml, model/templates.yaml, model/backlog/epics.yaml, docs/architecture/ecosystem-composition.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-1406 Publication step of the components package after the new suites, with a version guard |
operations | The pipeline of the kit runs the token test, the render matrix, the accessibility tests and the adapter conformance suite before it packs, pushes the components package ConnectSoft.Blazor.UIKit only to the ConnectSoft feed, and refuses a version that is already on the feed with the reason; it packs and pushes no adapter package. |
ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1407 Feed probe host for the published kit with the adapter packages on the feed |
fixture | A probe host with the ConnectSoft feed as its only source restores the published kit version together with the adapter package versions already on the feed, each adapter in turn, and renders a page with the three primitives and the eight compositions in both themes and both directions; the probe runs as the last stage of the pipeline, fails on a missing static web asset and writes the adapter versions it used to its log. | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1408 Release notes page records the published version and what it carries |
documentation | The release notes page of the kit names the published version, the token families, the three primitives, the eight compositions and the adapter package versions the probe proved the kit with, and the coverage page points at it. | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-1428 Shell template pins the published UI kit version |
implementation | The central package file of the shell template pins the UI kit version published by AIFACTORY-TASK-1406, the solution builds and its tests pass, and the template republishes through its generated-solution gate, so that the latest published shell template package, the reference of the pin check of AIFACTORY-TASK-1382, carries the new pin. | ConnectSoft.Blazor.ShellTemplate |
AIFACTORY-TASK-1429 Microfrontend library template pins the published UI kit version |
implementation | The central package file of the microfrontend library template pins the same UI kit version as the republished shell template, the pin test IntegrationContractTests asserts it, the solution builds and its tests pass, and the pin check of its pipeline is green. |
ConnectSoft.Blazor.MicrofrontendLibraryTemplate |
AIFACTORY-TASK-1409 Verify the published package by the probe host and the two pinned templates |
verification | One pipeline run publishes the components package and the probe host renders the page with each adapter package version on the feed; a rerun with the same version is refused; the shell template and the microfrontend library template build and test green on the pinned version with a green pin check; the runs prove AC1 to AC3 of AIFACTORY-US-330 (ADR-0007). | ConnectSoft.Blazor.UIKit |
AIFACTORY-US-127: UI kit: the token work and the Factory compositions the alignment gate ranks first is delivered and proven on a generated solution¶
enabling · persona asset-maintainer
As an asset maintainer, I want Blazor Shell + MFEs + UIKit to carry the token work and the Factory compositions the alignment gate ranks first, so that it serves Factory Studio and generated product UIs without later rework.
This is the integration PBI of the feature. An asset maintainer builds the UI kit with the token families locked in every variant, the three operational primitives with their contracts and the eight Factory compositions on the vocabulary of the UX model, runs its suites and publishes the components package. The adapter packages ship from their own repositories and are not published here; the probe proves the kit with the adapter versions on the feed. A failing token, accessibility, render or conformance test blocks the publication. The implementation lives in the earlier PBIs of this file; this PBI proves them together from the side of the first consumer. The kit is also shipped as a template for component libraries; this feature changes the library and its package, and the template of the kit is not in its scope. From the published version a host in the shape of a Studio microfrontend renders a run card with the run family, a review queue with the approval family and an artifact diff, under the Tokens adapter, in the dark theme, at compact density and in right-to-left direction, with every state given as text. The feature is done when that host restores the published version from the ConnectSoft feed and renders the page, and the shell template and the microfrontend library template pin that version. Repository of the feature: ConnectSoft.Blazor.UIKit; one task each moves the pin in the two templates.
Acceptance criteria
| AC1 | Given the repository ConnectSoft.Blazor.UIKit with the work of this feature, when its pipeline runs, then the components package builds, its tests pass and it publishes to the ConnectSoft feed under one verified version, the probe proves it with the adapter package versions on the feed, and the shell template and the microfrontend library template pin that version (ADR-0007, model/components.yaml). |
| AC2 | Given the work of AIFACTORY-TASK-616 (density bridge, elevation scale and motion tokens) is done, then the density attribute reassigns the cs-* spacing, type and radius tokens, a named elevation scale and the fast, base and slow motion tokens exist in the token spine and in the dark and accessibility variants, and the token documentation and the gallery show them (ADR-0007, docs/architecture/ecosystem-composition.md). |
| AC3 | Given the work of AIFACTORY-TASK-617 (P0 primitives JsonViewer, DiffViewer and LogStream) is done, then the three primitives exist with their accessibility contracts, gallery routes and component tests, DiffViewer renders a unified and a side-by-side diff, LogStream follows a stream with pause and search, and each renders under the three adapters (NFR-15, model/ux/screens.yaml). |
| AC4 | Given the work of AIFACTORY-TASK-618 (P0 Factory compositions) is done, then FactoryRunCard, AgentExecutionGraph, QualityGatePanel, TraceViewerPanel, ArtifactExplorer, ArtifactDiffPanel, ArtifactLineageGraph and HumanReviewQueue exist as compositions over the kit primitives, bound to the state families of model/ux/states.yaml, with gallery routes, component tests and a render under the Tokens, Flowbite and DaisyUI adapters (FUX-12, NFR-15). |
| Traces: adrs | ADR-0007, ADR-0026 |
| Traces: requirements | FUX-12 |
| Relates: nfrs | NFR-15 |
| Depends on | AIFACTORY-US-327, AIFACTORY-US-328, AIFACTORY-US-329, AIFACTORY-US-330 |
| Sources | model/components.yaml, model/ux/screens.yaml, model/ux/states.yaml, docs/architecture/ecosystem-composition.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-1410 Render a Studio-shaped page from the published kit |
verification | A probe host in the shape of a Studio microfrontend restores the published version from the ConnectSoft feed and renders a run card, a review queue and an artifact diff under the Tokens adapter, in the dark theme, at compact density and in right-to-left direction with every state given as text; the run proves AC2 to AC4 of AIFACTORY-US-127 on the published package (ADR-0007, NFR-15). | ConnectSoft.Blazor.UIKit |
AIFACTORY-TASK-693 Verify uikit-factory-compositions-delivered by running the declared command |
verification | Run dotnet build -c Release and dotnet test -c Release --no-build on the solution of the kit and on the probe host after the published version is restored; they pass and prove AC1 to AC4 of AIFACTORY-US-127. |
ConnectSoft.Blazor.UIKit |