Skip to content

AIFACTORY-FEAT-101: Blazor shell, microfrontends and UI kit for the Studio

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 backend-developer · Build order 122 of 185 (Factory code)

The Blazor shell template, the microfrontend library template and the UI kit are extended with what the Studio needs: the work-area navigation, the state families, the run timeline and approval components, and the realtime connection. Component: Blazor Shell + MFEs + UIKit (extend).

Delivers —
Stubs —
Realizes components: cmp-blazor-shell
Requirements —
Depends on AIFACTORY-FEAT-167 Blazor shell template: gateway adapters, filter diagnostics and pinned packages before the Studio
AIFACTORY-FEAT-168 Blazor microfrontend library template: AppShell chrome, a neutral exemplar and a generated-solution gate
AIFACTORY-FEAT-169 UI kit: the token work and the Factory compositions the alignment gate ranks first
Sources model/components.yaml, docs/architecture/ecosystem-composition.md

AIFACTORY-US-331: Studio shell: the Studio repository is generated from the published shell template, composes a first microfrontend and calls the Studio backend through a generated client

enabling · persona asset-maintainer As an asset maintainer, I want the Studio shell to be assembled from the published shell template, microfrontend library template, UI kit and API library template, so that the Studio starts from proven packages and holds no copy of what a template or a library owns.

ADR-0007 builds the Studio as a Blazor shell that composes microfrontends, and the three template features this feature depends on deliver what it is built from: the shell template with gateway adapters, a token per gateway client, filter diagnostics and aligned pins; the microfrontend library template with the AppShell chrome and a neutral exemplar; and the UI kit with its Factory compositions. This PBI assembles the shell of the Studio from their published packages in the Studio repository. The shell is generated from the published shell template package, and at generation its package pins for the UI kit and the shell packages equal those of the template. Afterwards the central package file of the Studio is the one place a kit or shell package version is set for the shell and every microfrontend of the Studio; the pin check of the shared installer job keeps the shell package pins equal to the template, while the kit pin may move ahead when the Studio adopts a newer published kit version. The gateway adapters of the template are bound by configuration to the routes of StudioBff, so the Studio writes no adapter of its own. The client the shell uses for StudioBff is generated with the API library template from the OpenAPI document of StudioBff, with the JWT bearer layout because the shell forwards the token of the signed-in user; it takes the shared types from the contracts package by a version pin and defines none. A first microfrontend, generated from the exemplar of the microfrontend library template, is composed through the registry to prove the contract; the work-area features of the Studio add their microfrontends the same way. Architecture tests keep the rules of the templates in the Studio: a microfrontend references the shell contracts and abstractions and never the shell services package or the host, no project holds a hand-written gateway client, and every named gateway client declares its audience.

Acceptance criteria

AC1 Given the Studio repository generated from the published shell template package, when it is restored and built in Release, then it builds unchanged, its pins for the UI kit and the shell packages equal those of the shell template, no project sets a kit or shell package version outside the central package file, and the pin check of its pipeline passes for the shell package pins (ADR-0007: the Studio is a shell composing microfrontends on one design system; ADR-0028: the Studio is its own repository scaffolded from a published template).
AC2 Given the shell with authentication on and its gateway routes configured for StudioBff, when a user signs in, then the switchers, the flags and the notifications come from StudioBff/GetStudioSession and the notification route through the adapters of the template and the generated client, and the repository holds no hand-written adapter or client for StudioBff (ADR-0007, model/services/factory-studio/StudioBff.yaml).
AC3 Given the composed first microfrontend, when the architecture tests of the Studio run, then its routes answer in the shell, it references the shell contracts and abstractions only, a planted reference to the shell services package fails the test, and a named gateway client without an audience fails the test (ADR-0007, docs/architecture/ecosystem-composition.md).
Traces: adrs ADR-0007, ADR-0028
Traces: services StudioBff
Traces: apis StudioBff/GetStudioSession
Depends on feature:component-blazor-shell-template-studio, feature:component-blazor-mfe-library-template, feature:component-uikit-factory-compositions, feature:component-api-library-template-factory-clients, feature:contracts-package, feature:studio-bff
Sources model/components.yaml, model/services/factory-studio/StudioBff.yaml, docs/architecture/ecosystem-composition.md, docs/architecture/adr/0007-blazor-mfe-studio-frontend.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1411 Studio shell generated from the published shell template with its adapters bound to StudioBff implementation The Studio repository holds the shell generated from the published connectsoft-blazor-shell package with the pins of the template, the gateway routes of the tenant, flag, notification and activity adapters configured for StudioBff, the audience of its gateway client set, and a first microfrontend generated from the exemplar of the microfrontend library template composed through the registry. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1412 StudioBff client generated with the API library template implementation The client of StudioBff is generated with connectsoft-api-library from the OpenAPI document of StudioBff with the JWT bearer layout and with generation on, pins the contracts package for the shared types and is the only code of the Studio that calls StudioBff; a change of the document regenerates it at build. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1413 Architecture tests of the Studio for references, clients and audiences fixture The architecture test project of the Studio fails when a microfrontend references the shell services package or the host, when a microfrontend opens a connection to StudioRealtimeGateway of its own instead of using the subscription abstraction of the contracts project of the Studio, when a project other than the generated client calls StudioBff, when a named gateway client declares no audience, and when a project sets a kit or shell package version outside the central package file; a pipeline step runs the pin check of the shared installer job limited to the shell package pins. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1414 Verify the assembled shell against a StudioBff stub verification Build the Studio shell, start it against a stub of StudioBff/GetStudioSession and run the architecture tests with the planted reference and the planted client; the shell shows the session data, the composed route answers and both planted cases fail, which proves AC1 to AC3 of AIFACTORY-US-331 (ADR-0007). ConnectSoft.AI.SoftwareFactory.Studio

AIFACTORY-US-332: I see the work areas my role allows and switch tenant, project and environment without gaining anything by the switch

behavior · persona requester As a requester, I want the Studio to show the work areas of my role and to let me change the tenant, project and environment I work in, so that I always know in which scope I act and never see an area I may not use.

A signed-in user opens the Studio. The shell asks StudioBff for the session projection, which carries the scope, a snapshot of the permissions, the work area and the feature flags, and renders its chrome from it. The navigation shows the seven work areas of the UX model, Workspace, Software Factory, Assets, Intelligence, Quality and releases, Operations and usage, and Governance and administration, each only when a role of the user, its flag and its entitlement allow it; the entries pass the navigation filter of the shell and the host policy of each entry. The switchers list the tenant, the project and the environment items the session offers. When the user picks another item the shell sends the switch to StudioBff, which validates it; on success the shell reloads the session and rebuilds the navigation for the new scope. A switch grants nothing: the permissions of the new scope are whatever the session returns for it. A switch that StudioBff refuses leaves the scope unchanged and tells the user why: a 403 means the token lacks the scope inside the tenant, and a 404 means the item does not exist for this user, which is also the answer for an item of another tenant. When StudioBff cannot be reached the shell fails closed: it shows no work area beyond the home page and says that the scope could not be loaded. Every successful switch is recorded by StudioBff with the session; the shell records nothing of its own. The navigation and the switchers live in the Studio repository because the generic shell template ships an empty registry.

Acceptance criteria

AC1 Given a user whose session from StudioBff/GetStudioSession holds the Requester role in one project, when the shell renders, then the navigation shows only the work areas that role, the flags and the entitlements allow, and the switchers list the tenant, project and environment items of the session (FUX-01; the screen my-work of model/ux/screens.yaml reads the session).
AC2 Given the user picks another project, when the shell calls StudioBff/SetStudioScope and the switch is accepted, then the shell reloads the session and the navigation and every open screen reflect the new scope, and a role the user holds only in the former project is no longer applied (FUX-01, NFR-01).
AC3 Given StudioBff/SetStudioScope answers 403 for a scope the token lacks or 404 for an item that is not visible to the user, when the shell handles the answer, then the scope stays unchanged, the user is told the reason and an item answered 404 leaves the switcher, as the amendment of ADR-0015 on a resource of another tenant prescribes.
AC4 Given StudioBff cannot be reached or answers 401, when the shell loads the session, then no work area beyond the home page is shown, the user is told that the scope could not be loaded, and no token or header value is logged (ADR-0015, NFR-01).
Traces: services StudioBff
Traces: apis StudioBff/GetStudioSession, StudioBff/SetStudioScope
Traces: adrs ADR-0015
Traces: requirements FUX-01
Relates: screens my-work
Relates: nfrs NFR-01
Depends on AIFACTORY-US-331, feature:studio-bff
Sources model/components.yaml, model/ux/screens.yaml, model/services/factory-studio/StudioBff.yaml, docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-359 Work-area navigation and scope switchers in the shell implementation The Studio shell shows the seven work areas by role, flag and entitlement and the tenant, project and environment switchers from the session projection; a switcher sends the change to StudioBff, reloads the session on success and grants nothing by itself; a refused switch leaves the scope unchanged with its reason, and an unreachable StudioBff fails closed. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1415 Navigation entries of the seven work areas and the switcher region of the chrome ui The registry of the Studio shell holds one navigation group per work area of model/ux/screens.yaml with its flag, entitlement and host policy, and the switcher region of the AppShell chrome renders the three switchers with their loading, empty and refused states in the three locales. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1416 StudioBff stub with roles, a refused switch and an outage fixture The test project of the Studio shell holds a stub of StudioBff/GetStudioSession and StudioBff/SetStudioScope with sessions for each role, a switch answered 403, a switch answered 404 and an unreachable backend, and a log capture that fails a test when a token or a header value is written. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1417 Verify the navigation by role, the accepted switch and the refusals verification Run the shell tests against the stub of AIFACTORY-TASK-1416; each role sees its work areas only, an accepted switch reloads the session, and the 403, 404 and outage cases leave the scope unchanged or fail closed, which proves AC1 to AC4 of AIFACTORY-US-332 (FUX-01). ConnectSoft.AI.SoftwareFactory.Studio

AIFACTORY-US-333: UI kit: components for the state families of the UX model, the run timeline and the approval card, with their accessibility contracts

enabling · persona asset-maintainer As an asset maintainer, I want the UI kit to carry the state, timeline and approval components every Studio work area shows, so that a run state or an approval looks and reads the same in every microfrontend.

The UX model of this repository fixes eight state families, among them the run, the approval, the usage and the freshness family, each with its values and its colour group, and the screens of the Studio name the families they show. The kit already documents a status badge and a timeline component, and its Factory compositions are closed by the preceding feature; what the Studio still lacks are the three components this feature names. This PBI adds them to the kit as library components, because a shared type lives in the library and a microfrontend consumes it by the version pin. The state indicator renders any value of any family of model/ux/states.yaml with the colour group of the family and always with the value as text, so a state is never given by colour alone, and renders a value it does not know as unknown. The run timeline renders the steps and attempts of a run in order with their states, marks the step that waits for an approval, and is read and operated by keyboard. The approval card shows the proposal a decision is bound to with its exact version, the expiry of a pending request, the state Superseded when the proposal changed, and the decision actions as parameters the microfrontend wires; the card decides nothing and calls nothing. Each component has a documentation page with its parameters and its accessibility contract, a gallery route, component tests, a render under the Tokens, Flowbite and DaisyUI adapters and in right-to-left direction, and honours the reduced-motion preference through the motion tokens. The components reach the Studio as a published package and not as a project reference: after the snapshot, keyboard and render tests pass, the pipeline of the kit publishes the components package under the version guard of AIFACTORY-US-330, the release notes page of the kit names the version, and the central package file of the Studio pins it.

Acceptance criteria

AC1 Given the state indicator, when it is rendered with every value of every family of model/ux/states.yaml, then each value appears as text with the colour group of its family, an unknown value appears as unknown, and a snapshot test fails when a family of the model gains a value the kit does not know (FUX-04, ADR-0026).
AC2 Given a run with steps and attempts in mixed states, when the run timeline renders, then steps and attempts appear in order with their states as text, the step that waits for an approval is marked, and the timeline is read and operated by keyboard with visible focus (FUX-04; the screens run-detail and run-timeline of model/ux/screens.yaml use it).
AC3 Given a pending approval bound to a proposal version, when the approval card renders, then it shows the proposal and its exact version and the expiry, shows Superseded when the proposal changed, exposes the decision actions as parameters and makes no call of its own (FUX-05; the screen approval-card of model/ux/screens.yaml uses it).
AC4 Given the three components, when the render matrix runs, then each renders under the Tokens, the Flowbite and the DaisyUI adapter and in right-to-left direction, plays no animation under the reduced-motion preference, and has a documentation page and a gallery route; and the components package that carries them is on the ConnectSoft feed under a version the release notes page of the kit names, and the Studio builds against that pinned version (ADR-0007, ADR-0026).
Traces: adrs ADR-0007, ADR-0026
Traces: requirements FUX-04, FUX-05
Relates: screens run-detail, run-timeline, approval-card
Depends on feature:component-uikit-factory-compositions, AIFACTORY-US-331
Sources model/components.yaml, model/ux/states.yaml, model/ux/screens.yaml, docs/architecture/adr/0026-requirements-to-ux-handoff.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-360 State-family, run timeline and approval components in the UI kit ui Components for the state families of the UX model, the run timeline and the approval card exist in the kit with their accessibility contracts, documentation pages and gallery routes; every state is given as text beside its colour, the approval card shows the exact proposal version and the expiry and makes no call; the components reach the Studio through the publication of AIFACTORY-TASK-1432 and the pin of AIFACTORY-TASK-1433. ConnectSoft.Blazor.UIKit
AIFACTORY-TASK-1418 Family snapshot, keyboard and render matrix tests of the three components fixture The unit test project of the kit holds a snapshot of the families of model/ux/states.yaml that the state indicator is tested against, keyboard and focus tests of the run timeline and the approval card, a reduced-motion test and a render of each component under the three adapters and in both directions. ConnectSoft.Blazor.UIKit
AIFACTORY-TASK-1419 Component pages and gallery routes of the three components documentation The documentation of the kit holds a page per component with its parameters, its states and its accessibility contract, and the gallery shows each component with every family, a mixed run and a pending, an expired and a superseded approval. ConnectSoft.Blazor.UIKit
AIFACTORY-TASK-1432 Kit pipeline publishes the version that carries the three components operations After the family snapshot, keyboard, reduced-motion and render matrix tests of AIFACTORY-TASK-1418 pass, the pipeline of the kit publishes the components package ConnectSoft.Blazor.UIKit to the ConnectSoft feed under the version guard of AIFACTORY-US-330, and the release notes page of the kit names the version and the state indicator, the run timeline and the approval card it carries. ConnectSoft.Blazor.UIKit
AIFACTORY-TASK-1433 Studio pins the kit version that carries the three components implementation The central package file of the Studio, the one place the kit version is set for the shell and every microfrontend, pins the UI kit version published by AIFACTORY-TASK-1432; the solution builds in Release and a component test of the first microfrontend renders the state indicator, the run timeline and the approval card from the pinned package. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1420 Verify the three components against the families, the adapters and the published version verification Run the tests of AIFACTORY-TASK-1418; every value of every family renders as text, the timeline and the card pass their keyboard tests and each component renders under the three adapters. Then name the version AIFACTORY-TASK-1432 published, as the release notes page of the kit records it, and build the Studio against the pin of AIFACTORY-TASK-1433; the published version and the green Studio build are the proof of AC4, and the runs together prove AC1 to AC4 of AIFACTORY-US-333 (FUX-04, FUX-05). ConnectSoft.Blazor.UIKit

AIFACTORY-US-334: I see live updates through one connection per session, and the Studio tells me when they are unavailable

behavior · persona requester As a requester, I want the Studio to keep the screens I watch current and to say so when it cannot, so that I never take a stale run state for a live one.

A user watches a run or an approval list in the Studio. The shell opens one connection to StudioRealtimeGateway for the session, and no microfrontend opens a connection of its own. A microfrontend may reference only the shell contracts and abstractions, so the subscription abstraction lives in the contracts project of the Studio repository, ConnectSoft.AI.SoftwareFactory.Studio.Contracts, which references neither the host nor the shell services package; its implementation lives in the shell host. The connection carries a token issued for the audience of the realtime gateway; a user token has one audience, so the shell requests this token separately from the one it sends to StudioBff and never sends either to the other gateway. A subscription names what a screen watches and is bounded by the scope of the session; the gateway refuses a subscription outside it, and the shell shows the refusal on the screen and does not retry it. When the connection drops, the shell reconnects with a growing delay, subscribes again to everything the open screens watch and asks each screen to reload its model once, because updates were missed in between. While the connection is down or a source is degraded, every watching screen shows the freshness family of the UX model: the data is marked stale or degraded with the last observation, never hidden and never shown as fresh. When the user switches the scope, the shell drops every subscription of the old scope before it subscribes under the new one, so no update of the former project reaches a screen of the new one. When the session ends, the connection is closed. The shell keeps no update on disk and writes no payload of an update to a log.

Acceptance criteria

AC1 Given a session with two screens that watch a run, when both subscribe, then the shell holds exactly one connection to the realtime gateway, negotiated through StudioRealtimeGateway/Realtime.Subscribe with a token whose audience is that gateway, and the token sent to StudioBff is never sent on the connection (FUX-04; ADR-0015 amendment on the token audience).
AC2 Given the connection drops and returns, when the shell reconnects, then it subscribes again to everything the open screens watch, each screen reloads its model once, and while the connection was down every watching screen showed the freshness state stale with the last observation (FUX-04; the screen run-detail of model/ux/screens.yaml carries the freshness family).
AC3 Given the user switches the project, when the shell applies the new scope, then every subscription of the former scope is dropped before a new one is made and no update of the former project reaches a screen; a subscription the gateway refuses is shown as refused and is not retried (ADR-0015, NFR-01).
AC4 Given live updates cannot be established at all, when a watching screen renders, then it says that live updates are unavailable, keeps working by reload, and no update payload is written to a log (FUX-04; the screen my-work of model/ux/screens.yaml stays usable).
Traces: services StudioRealtimeGateway, StudioBff
Traces: apis StudioRealtimeGateway/Realtime.Subscribe
Traces: adrs ADR-0015
Traces: requirements FUX-04
Relates: screens run-detail, my-work
Relates: nfrs NFR-01
Depends on AIFACTORY-US-331, AIFACTORY-US-332, feature:studio-realtime-gateway, feature:studio-bff
Sources model/components.yaml, model/ux/states.yaml, model/ux/screens.yaml, model/services/factory-studio/StudioRealtimeGateway.yaml, docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-361 Realtime connection of the shell ui The Studio shell holds one connection to StudioRealtimeGateway per session. The subscription abstraction lives in the contracts project ConnectSoft.AI.SoftwareFactory.Studio.Contracts of the Studio, which a microfrontend may reference and which references neither the host nor the shell services package; its implementation in the shell host re-subscribes after a reconnect, asks the watching screens to reload once and shows the freshness state and a notice when live updates are unavailable; the architecture test of AIFACTORY-TASK-1413 forbids a connection a microfrontend opens itself. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1421 Token of the realtime audience and subscriptions that follow the scope implementation The realtime service of the shell requests a token for the audience of the realtime gateway through a second named client, drops every subscription on a scope switch before it subscribes under the new scope, closes the connection at the end of the session and logs no update payload. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1422 Hub stub with a drop, a refused subscription and an unreachable gateway fixture The test project of the Studio shell holds a hub stub that records the audience of the token of every connection and the subscriptions it receives, drops and restores the connection on demand, refuses a subscription outside the scope and can be unreachable from the start. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1423 Verify the single connection, the reconnect, the scope switch and the unavailable state verification Run the realtime tests against the hub stub of AIFACTORY-TASK-1422; one connection serves two screens, a reconnect re-subscribes and reloads once, a scope switch drops the former subscriptions and the unreachable gateway shows the notice, which proves AC1 to AC4 of AIFACTORY-US-334 (FUX-04, StudioRealtimeGateway/Realtime.Subscribe). ConnectSoft.AI.SoftwareFactory.Studio

AIFACTORY-US-039: The Studio works with a keyboard, in my language and direction

behavior · persona reviewer As a reviewer, I want to use the Studio with a keyboard, in my locale and reading direction, with the motion I can tolerate, so that I can decide and submit without barriers.

This is the integration PBI of the feature: it proves the assembled shell, its navigation and switchers, the kit components and the realtime connection together on the two paths every user of the Studio walks. A reviewer sets the locale, the theme and the reduced-motion preference; the shell stores them through StudioBff and reads them back with the session, so they hold on the next sign-in and on another device. Storing and reading back is work of the Studio shell and not of the kit: the kit is a component library that makes no call, and it delivers the mechanism, the two directions, the localised state texts and the motion tokens. The Studio supports English, Hebrew and Russian. In Hebrew the shell and every kit component render in right-to-left direction: the navigation, the tables and the timelines are mirrored and no text is clipped. With a keyboard alone a requester submits a run and a reviewer opens an approval card and decides it; focus is always visible and never trapped, and the order of focus follows the reading order of the direction. With the reduced-motion preference a live update changes the screen without an animation. A state shown by colour is also given as text, in the locale of the user. A preference StudioBff refuses is not applied locally: the shell keeps the stored value and says that the change was not saved. The kit changes of this PBI reach the Studio as a published version that the Studio pins. The paths are covered by automated accessibility tests that run in the pipeline of the Studio, so a microfrontend that breaks a path fails the run. Usability at this level is the baseline of the Factory: the accessibility level, the three locales, the direction and the keyboard are requirements of every screen.

Acceptance criteria

AC1 Given a right-to-left locale set through StudioBff/SetStudioPreferences, when the shell renders, then navigation, tables and timelines are mirrored and no text is clipped, and the locale is read back from StudioBff/GetStudioSession on the next sign-in (NFR-15, FUX-12).
AC2 Given only a keyboard, when a user submits a run and decides an approval, then both complete without a pointer, focus is always visible and never trapped, and the focus order follows the reading order of the direction (NFR-15; the screens run-submit and approval-card of model/ux/screens.yaml are the two paths).
AC3 Given the reduced-motion preference stored through StudioBff/SetStudioPreferences, when a screen updates live, then no animation plays; given StudioBff refuses a preference, then the shell keeps the stored value and tells the user that the change was not saved (NFR-15, ADR-0026).
AC4 Given a state shown by colour, when it renders in each of the three locales, then the state is also given as text in that locale, for every family of model/ux/states.yaml (FUX-12, NFR-15).
Traces: services StudioBff
Traces: apis StudioBff/SetStudioPreferences, StudioBff/GetStudioSession
Traces: adrs ADR-0026
Traces: requirements FUX-12
Relates: screens run-submit, approval-card
Relates: nfrs NFR-15
Depends on AIFACTORY-US-331, AIFACTORY-US-332, AIFACTORY-US-333, AIFACTORY-US-334, feature:studio-bff
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-533 Direction and locale in the shell and the kit implementation Every kit component renders in both directions and in each of the three supported locales; the state texts of the families of model/ux/states.yaml are localised resources of the kit; a test renders the AppShell chrome and the components in the right-to-left locale and fails on clipped text. ConnectSoft.Blazor.UIKit
AIFACTORY-TASK-534 Keyboard paths for submit and decide implementation The two paths, submitting a run on the screen run-submit and deciding on the screen approval-card, are covered by automated keyboard tests of the Studio that assert visible focus, no focus trap and the focus order of each direction. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-535 Reduced motion and state text implementation Live updates of the kit components honour the reduced-motion preference through the motion tokens of the kit, and every state family of model/ux/states.yaml has a text form in the three locales; the kit stores no preference and makes no call. ConnectSoft.Blazor.UIKit
AIFACTORY-TASK-1430 Locale, theme and reduced motion stored through StudioBff and read back with the session implementation The Studio shell stores the locale, the theme and the reduced-motion preference through StudioBff/SetStudioPreferences, reads them back from StudioBff/GetStudioSession at sign-in and applies them to the direction, the theme and the motion setting the kit components read; when StudioBff refuses a change the shell keeps the stored value and shows a notice that the change was not saved. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1431 StudioBff stub with an accepted and a refused preference fixture The test project of the Studio shell holds a stub of StudioBff/SetStudioPreferences and StudioBff/GetStudioSession with an accepted change that the next session returns and a refused change, and tests that assert the read-back on a new session and the kept value with the notice on the refusal. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-1434 Kit pipeline publishes the version that carries the localised state texts and the reduced-motion behaviour operations After the direction, locale and reduced-motion tests of AIFACTORY-TASK-533 and AIFACTORY-TASK-535 pass, the pipeline of the kit publishes the components package to the ConnectSoft feed under the version guard of AIFACTORY-US-330, and the release notes page of the kit names the version and what it carries. ConnectSoft.Blazor.UIKit
AIFACTORY-TASK-1435 Studio pins the kit version of the accessibility work implementation The central package file of the Studio pins the UI kit version published by AIFACTORY-TASK-1434 and the solution builds in Release against it. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-677 Verify studio-shell-accessible-and-localised by running the declared command verification Run dotnet test -c Release --filter Category=Accessibility on the Studio shell pinned to the kit version of AIFACTORY-TASK-1435, including the preference tests of AIFACTORY-TASK-1430 against the stub of AIFACTORY-TASK-1431; it passes and proves AC1 to AC4 of AIFACTORY-US-039. ConnectSoft.AI.SoftwareFactory.Studio