AIFACTORY-FEAT-075: Studio work area: Assets¶
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 Factory Studio (PF-14) · Increment I3 Studio · State elaborated · Route frontend-developer · Build order 115 of 185 (Factory code)
The 11 screens of the Studio work area Assets on the Blazor shell and microfrontends, bound to the read models and commands the model names for them, with their state families, roles, locales and accessibility contracts. Screens come from model/ux/screens.yaml and the prototype alignment.
| Delivers | — |
| Stubs | — |
| Realizes | ux work areas: Assets components: cmp-blazor-shell |
| Requirements | — |
| Depends on | — |
| Sources | model/ux/screens.yaml, model/ux/prototype-alignment.yaml |
AIFACTORY-US-1391: Assets: I inspect tool descriptors and dry-run a tool, and see the MCP server registry in its thin scope, through StudioBff¶
behavior · persona asset-maintainer
As an asset maintainer, I want to read every tool descriptor with its classes, schema and limits and to dry-run a tool without executing it, so that I know what a tool may do and which approval it needs before an agent is bound to it.
An asset maintainer, a platform admin or an observer opens the screen tool-descriptor at /assets/tools/{toolId} in the Assets microfrontend. The page asks StudioBff for GetScreenModel of that screen, and StudioBff composes it under the scope of the session from ListTools and GetTool of ToolAdapterService, reached through ToolExecutorHost, with the freshness of the source: the active descriptors visible to the caller with side-effect and risk class, kind, server and health, and for one descriptor its schema, authorization, secret dependencies, limits and audit requirements. DryRunTool uses the read scope factory.tools.read, so the dry run is offered to every role of the screen whose session holds that scope, an observer included, because it executes nothing: the page sends it through ForwardCommand with an idempotency key, ToolAdapterService validates the arguments and answers the pipeline outcome (class, policy, approval needed, sandbox kind), and the page shows that outcome; nothing changes. A session without that scope sees the dry run disabled with the reason. A tool of another tenant is answered 404 by GetTool and DryRunTool like a tool that does not exist, a dry run sent without the scope is answered 403 by DryRunTool, and the page shows either in words; ListTools lists only the descriptors visible to the caller. When ToolExecutorHost does not answer, the composition marks the source degraded with its last freshness and a dry run is refused with 503, never queued by StudioBff. StudioBff consumes ToolDescriptorActivated and ToolDescriptorRetired, refreshes the tool descriptor view and signals the open page, which updates without a reload. The screen mcp-servers reads ListMcpServers of McpServerRegistryService. In I3 that registry is static and holds no MCP server, every tool of the chain being native, so the screen says that no server is registered; GetMcpCapabilities and the commands RegisterMcpServer, DiscoverMcpCapabilities, ActivateMcpServer and RetireMcpServer arrive with the complete delivery of the registry in I5, so the screen offers none of them and lists the capability source as not delivered.
Acceptance criteria
| AC1 | Given an asset maintainer with the screen tool-descriptor open, when StudioBff/GetScreenModel composes it, then the list and the descriptor come from ToolAdapterService/ListTools and ToolAdapterService/GetTool under the scope of the session with the freshness of the source, and the browser calls no address other than StudioBff (model/ux/screens.yaml, FUX-02). |
| AC2 | Given a role of the screen whose session holds factory.tools.read, an observer included, when they dry-run a tool, then StudioBff/ForwardCommand forwards ToolAdapterService/DryRunTool with an idempotency key, the page shows class, policy, approval needed and sandbox kind, nothing is executed, and a session without that scope sees the control disabled with the reason (FUX-05, ADR-0028 decision 3 keeps ToolAdapterService the only executor). |
| AC3 | Given a tool of another tenant, when ToolAdapterService/GetTool or ToolAdapterService/DryRunTool is requested, then the answer is 404 like a tool that does not exist; given a dry run sent without the scope, then ToolAdapterService/DryRunTool answers 403; the page explains either in words, and when ToolExecutorHost does not answer the source is shown degraded with its last freshness and the dry run is refused with 503 without being queued (ADR-0015, model/services/factory-studio/StudioBff.yaml). |
| AC4 | Given the descriptor open and ToolAdapterService/ToolDescriptorActivated or ToolAdapterService/ToolDescriptorRetired consumed by StudioBff, when the view is refreshed, then the page shows the new state without a reload; and given the screen mcp-servers, when it opens in I3, then McpServerRegistryService/ListMcpServers answers an empty registry, the page says that no MCP server is registered and no registration, discovery, activation or retirement is offered (FUX-02). |
| Traces: services | StudioBff, ToolAdapterService, McpServerRegistryService |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, ToolAdapterService/ListTools, ToolAdapterService/GetTool, ToolAdapterService/DryRunTool, McpServerRegistryService/ListMcpServers |
| Traces: events | ToolAdapterService/ToolDescriptorActivated, ToolAdapterService/ToolDescriptorRetired |
| Traces: adrs | ADR-0015, ADR-0022, ADR-0028 |
| Traces: requirements | FUX-02, FUX-05 |
| Relates: screens | tool-descriptor, mcp-servers |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:tool-adapter-service, feature:tool-executor-host, feature:mcp-server-registry-service-thin |
| Sources | model/ux/screens.yaml, model/services/factory-studio/StudioBff.yaml, model/services/tools-mcp/ToolAdapterService.yaml, model/services/tools-mcp/McpServerRegistryService.yaml, docs/planes/experience/studio/screens/assets.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5621 Tool descriptor and MCP server screens in the Assets microfrontend |
ui | The Assets microfrontend renders tool-descriptor and mcp-servers from the screen model of StudioBff with the asset-readiness and deployment-availability families of model/ux/states.yaml, a dry-run panel with the returned class, policy, approval and sandbox kind, the disabled control with its reason for a session without factory.tools.read, the empty registry message, and the not-delivered marker of the capability source. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5622 Screen models of the tool descriptor and MCP server screens in StudioBff |
contract | StudioBff composes tool-descriptor from ListTools and GetTool and mcp-servers from ListMcpServers through ToolExecutorHost with the freshness of each source, forwards DryRunTool with an idempotency key and the scope of the session, returns its 403 and 404 unchanged, refuses it with 503 while ToolExecutorHost does not answer, and refreshes the tool descriptor view on ToolDescriptorActivated and ToolDescriptorRetired. |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5623 Verify the tool descriptor and MCP server screens against a stubbed StudioBff |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium on the Studio with a StudioBff stub that serves descriptors, a dry-run outcome for an observer, a 404 of GetTool and DryRunTool for a tool of another tenant, a 403 of a dry run without the scope, a degraded source and an empty MCP registry; the tests prove AC1 to AC4 of AIFACTORY-US-1391 (ToolAdapterService/DryRunTool, McpServerRegistryService/ListMcpServers). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5695 Verify the StudioBff side of the tool descriptor and MCP server screens |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-assets-tool-descriptor-and-mcp-servers" in StudioBff against stubbed platform gateways, where a filter that matches no test fails the run; the tests prove on the StudioBff side AC1 (composition from ListTools, GetTool and ListMcpServers through ToolExecutorHost with freshness), AC2 (DryRunTool forwarded once with its idempotency key and the scope of the session), AC3 (403 and 404 returned unchanged, 503 while ToolExecutorHost does not answer, nothing queued) and AC4 (refresh on ToolDescriptorActivated and ToolDescriptorRetired) of AIFACTORY-US-1391 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-1392: Assets: I read model profiles and deployments, workflow definition versions and the template catalog, and act on them only with the role and class the owning service requires¶
behavior · persona platform-admin
As a platform admin, I want to see the model profiles with their deployments and route plans, the loaded workflow definition versions and the template catalog with its compatibility evidence, and to act on them from the Studio, so that I govern the assets the chain depends on with the evidence beside each decision.
Three screens of the Assets area read services that are delivered before I3. The screen model-profiles reads ListModelProfiles, GetModelProfile, ListModelDeployments and PreviewRoutePlan of ModelRouterService through ModelGatewayHost: the active profiles with capabilities, privacy class, limits and fallback chains, their deployments, and a dry run of the router for a scope and profile with the candidates, the filters and the reasons for exclusion. A platform admin may register a Candidate deployment with RegisterDeployment (credentials are brokered, never posted), run the capability suite with EvaluateDeployment, a sandbox action whose evidence ModelRouterService records, and move an Evaluated deployment to Approved with ApproveDeployment, a publication-class action; ADR-0021 decision 1 makes profiles assets approved by a platform admin. The screen workflow-definitions reads ListWorkflowDefinitionVersions of WorkflowEngineService with their graph hashes, and an asset maintainer or a platform admin validates a DSL document with ValidateWorkflowDefinition, a sandbox action that answers the findings on acyclicity, action classes, failure policies, schema references and bounded loops and stores nothing. The screen template-catalog reads ListTemplates, GetTemplateVersion, ListLibraries and QueryCompatibility of TemplateRegistryService, and an administrator of the platform tenant may run DiscoverTemplates and PublishTemplateVersion; a caller of another tenant is answered 403. Every command goes through ForwardCommand with an idempotency key and the scope of the session; for a publication-class command it carries the approval binding the owning service requires, and the gate is the owning service, never StudioBff. A 400, 409, 412 or 422 answer is shown in words with the current state, and a 503 of a fail-fast dependency is shown with the statement that nothing changed. StudioBff consumes DeploymentStateChanged, CapabilityEvidenceRecorded and TemplateVersionDiscovered and refreshes the open views.
Acceptance criteria
| AC1 | Given a platform admin on model-profiles, when the screen model is composed, then profiles, deployments and the route-plan preview come from ModelRouterService/ListModelProfiles, ModelRouterService/GetModelProfile, ModelRouterService/ListModelDeployments and ModelRouterService/PreviewRoutePlan through StudioBff/GetScreenModel, and a refresh follows ModelRouterService/DeploymentStateChanged and ModelRouterService/CapabilityEvidenceRecorded without a reload (FUX-02, FUX-10). |
| AC2 | Given a platform admin, when they register, evaluate or approve a deployment, then StudioBff/ForwardCommand forwards ModelRouterService/RegisterDeployment, ModelRouterService/EvaluateDeployment or ModelRouterService/ApproveDeployment with an idempotency key and, for the publication-class approval, the approval binding; an answer 409 or 412 is shown with the current state of the deployment and a role other than platform admin sees the controls disabled with the reason (ADR-0021 decision 1). |
| AC3 | Given an asset maintainer on workflow-definitions, when they validate a document, then WorkflowEngineService/ValidateWorkflowDefinition answers its findings or 400 and the page lists them by rule beside the versions of WorkflowEngineService/ListWorkflowDefinitionVersions, and nothing is stored (model/ux/screens.yaml). |
| AC4 | Given the screen template-catalog, when it opens, then templates, versions, libraries and compatibility come from TemplateRegistryService/ListTemplates, TemplateRegistryService/GetTemplateVersion, TemplateRegistryService/ListLibraries and TemplateRegistryService/QueryCompatibility, and TemplateRegistryService/DiscoverTemplates and TemplateRegistryService/PublishTemplateVersion are offered only to an administrator of the platform tenant, a 403 or a 503 being shown with the statement that nothing changed (TemplateRegistryService/TemplateVersionDiscovered refreshes the view; FUX-11). |
| Traces: services | StudioBff, ModelRouterService, WorkflowEngineService, TemplateRegistryService |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, ModelRouterService/ListModelProfiles, ModelRouterService/GetModelProfile, ModelRouterService/ListModelDeployments, ModelRouterService/PreviewRoutePlan, ModelRouterService/RegisterDeployment, ModelRouterService/EvaluateDeployment, ModelRouterService/ApproveDeployment, WorkflowEngineService/ListWorkflowDefinitionVersions, WorkflowEngineService/ValidateWorkflowDefinition, TemplateRegistryService/ListTemplates, TemplateRegistryService/GetTemplateVersion, TemplateRegistryService/ListLibraries, TemplateRegistryService/QueryCompatibility, TemplateRegistryService/DiscoverTemplates, TemplateRegistryService/PublishTemplateVersion |
| Traces: events | ModelRouterService/DeploymentStateChanged, ModelRouterService/CapabilityEvidenceRecorded, TemplateRegistryService/TemplateVersionDiscovered |
| Traces: adrs | ADR-0021, ADR-0028 |
| Traces: requirements | FUX-02, FUX-10, FUX-11 |
| Relates: screens | model-profiles, workflow-definitions, template-catalog |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:model-router-service, feature:model-gateway-host, feature:workflow-engine-service, feature:agent-runtime-worker, feature:template-registry-service, feature:template-catalog-host |
| Sources | model/ux/screens.yaml, model/services/factory-studio/StudioBff.yaml, model/services/model-compute/ModelRouterService.yaml, model/services/agent-mesh/WorkflowEngineService.yaml, model/services/template-library/TemplateRegistryService.yaml, docs/architecture/adr/0021-quality-gates.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5624 Model profile, workflow definition and template catalog screens in the Assets microfrontend |
ui | The Assets microfrontend renders model-profiles, workflow-definitions and template-catalog from the screen model with the asset-readiness and deployment-availability families, a route-plan preview panel, validation findings listed by rule, compatibility evidence per version, and every command disabled with its reason for a role or tenant the owning service does not admit. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5625 Screen models and command routes of the model, workflow and template screens in StudioBff |
contract | StudioBff composes the three screens through ModelGatewayHost, AgentRuntimeWorker and TemplateCatalogHost with the freshness of each source, forwards the eight commands with an idempotency key and, for ApproveDeployment and PublishTemplateVersion, the approval binding, returns the answer of the owning service unchanged, and refreshes the views on DeploymentStateChanged, CapabilityEvidenceRecorded and TemplateVersionDiscovered. |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5626 Verify the model, workflow and template screens by role |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub that serves each screen for a platform admin, an asset maintainer, an observer and a caller of another tenant, and answers 409, 412 and 503 on the commands; the tests prove AC1 to AC4 of AIFACTORY-US-1392 (ModelRouterService/ApproveDeployment, TemplateRegistryService/PublishTemplateVersion). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5696 Verify the StudioBff side of the model, workflow and template screens |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-assets-model-profiles-workflows-and-templates" in StudioBff against stubbed platform gateways, where a filter that matches no test fails the run; the tests prove on the StudioBff side AC1 (composition through ModelGatewayHost and refresh on DeploymentStateChanged and CapabilityEvidenceRecorded), AC2 (the deployment commands forwarded once with an idempotency key and the approval binding of ApproveDeployment), AC3 (ValidateWorkflowDefinition forwarded through AgentRuntimeWorker with its answer unchanged) and AC4 (composition through TemplateCatalogHost, the approval binding of PublishTemplateVersion, a 403 and a 503 returned unchanged and refresh on TemplateVersionDiscovered) of AIFACTORY-US-1392 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-129: The Assets work area of the Studio is bound to the model¶
behavior · persona asset-maintainer
As an asset maintainer, I want the Assets work area of the Studio (11 screens) bound to the read models, commands, state families and roles the model names for it, so that I can inspect and govern agents, tools, profiles, workflows and templates from one place, with every control reflecting what I may do and how fresh what I see is.
This is the integration PBI of the Assets area. The Assets microfrontend is generated from the microfrontend library template, composed into the Studio shell through its registry and holds the eleven screens of model/ux/screens.yaml with their routes, read models, commands, state families and roles; it calls StudioBff only, through the generated client of the shell. A screen is offered to the roles its list names; for any other role it is absent from the navigation and GetScreenModel refuses it with 403. Six screens read services that are not delivered in I3 at the depth they need. asset-catalog and release-detail read ListReleases, GetRelease and ListReleaseEvaluations: the thin AgentRegistryService only loads the seeded Draft releases by alias with no publication gate, as the amendment of ADR-0021 on Draft releases records, and the thin QualityScoreService only stores evaluation events, so both screens and their lifecycle commands complete with the complete deliveries of the two services in I4. agent-card reads AgentCardService and the three marketplace screens read MarketplaceCatalogService and LicenseService, all delivered in I8. In I3 each of these screens is registered, offered to its roles, and shows its sources as unknown in the freshness family, named, never hidden and never filled from a fake; none of its commands is offered. The other five screens are delivered by AIFACTORY-US-1391 and AIFACTORY-US-1392. Every screen subscribes through Realtime.Subscribe of StudioRealtimeGateway; when the channel drops the page marks its data stale, and when it returns the page reloads the screen model and shows the current state without a reload of the browser. Every screen renders in English, Russian and Hebrew right to left and is built to the accessibility contract of docs/planes/experience/studio/localization-accessibility.md; the area evidence that follows this PBI checks it on the finished area.
Acceptance criteria
| AC1 | Given the shell with the Assets microfrontend, when each of the 11 screens of model/ux/screens.yaml opens for a role its list names, then it renders from StudioBff/GetScreenModel only, and for a role its list does not name the screen is not offered and StudioBff/GetScreenModel answers 403 (ADR-0007, ADR-0015). |
| AC2 | Given asset-catalog, release-detail, agent-card, marketplace-browse, marketplace-installations and publisher-console, when they open in I3, then each shows its sources as unknown in the freshness family of model/ux/states.yaml with the source named, shows no invented value and offers none of its commands, as the amendment of ADR-0021 on Draft releases leaves publication to the fourth increment (FUX-12). |
| AC3 | Given an open screen and its subscription through StudioRealtimeGateway/Realtime.Subscribe, when the channel drops, then the page marks the data stale and never presents it as current, and when the channel returns the page reloads StudioBff/GetScreenModel and shows the current state without a browser reload (FUX-02). |
| AC4 | Given the commands of the five delivered screens, when a role issues one, then it is forwarded once through StudioBff/ForwardCommand with an idempotency key and the scope of the session, a role without the right sees the control disabled with the reason, and the screens render in en, ru and he right to left under docs/planes/experience/studio/localization-accessibility.md. |
| Traces: services | StudioBff, StudioRealtimeGateway, ToolAdapterService, McpServerRegistryService, ModelRouterService, WorkflowEngineService, TemplateRegistryService |
| Traces: apis | StudioBff/GetStudioSession, StudioBff/GetScreenModel, StudioBff/ForwardCommand, StudioRealtimeGateway/Realtime.Subscribe |
| Traces: adrs | ADR-0007, ADR-0015, ADR-0021 |
| Traces: requirements | FUX-02, FUX-12 |
| Relates: screens | asset-catalog, release-detail, agent-card, marketplace-browse, marketplace-installations, publisher-console |
| Depends on | AIFACTORY-US-1391, AIFACTORY-US-1392, feature:studio-bff, feature:studio-realtime-gateway, feature:component-blazor-shell |
| Sources | model/ux/screens.yaml, model/ux/states.yaml, model/ux/prototype-alignment.yaml, docs/planes/experience/studio/screens/assets.md, docs/architecture/adr/0007-blazor-mfe-studio-frontend.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-433 Screens of the work area Assets: Asset catalog, Asset release, Agent card, Tool descriptor, MCP servers, Model profiles and deployments, Workflow definitions, Template catalog and 3 more |
ui | The Assets microfrontend is composed into the shell through the registry with one navigation group and the eleven routes of model/ux/screens.yaml; each screen renders from StudioBff only, and the six screens of later sources render their sources as unknown with the source named and no command. | ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-434 Commands of the work area Assets |
implementation | The commands of the five delivered screens are forwarded through StudioBff with an idempotency key and the scope of the session, a publication-class command carries its approval binding, and the commands of the six screens of later sources (release lifecycle, listings, pricing, installations) are not offered in I3. | ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-435 States, roles, locales and accessibility of the work area Assets |
implementation | Each screen shows the state families the model names for it, hides or disables what the role may not do with the reason, marks stale data on a dropped channel and reloads on its return, renders in every supported locale including right-to-left, and passes the accessibility checks of the UX model. | ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-740 Verify studio-assets-work-area by running the declared command |
verification | Run dotnet build -c Release, dotnet test -c Release --no-build and npx playwright test --project=chromium; they pass and prove AC1 to AC4 of AIFACTORY-US-129 (StudioBff/GetScreenModel, StudioRealtimeGateway/Realtime.Subscribe). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-US-1393: Assets area evidence: every screen passes the accessibility and phone-width checks and an end-to-end walk of the area through StudioBff is recorded¶
evidence · persona observer
As an observer, I want proof that every screen of the Assets area is usable by keyboard, in every locale and at phone width, and that a walk of the area reads only StudioBff, so that the area is accepted on a recorded check and not on a screenshot.
This PBI is the proof of the Assets area and comes after its integration PBI AIFACTORY-US-129, which registers the eleven screens. Two checks run against the Studio on the acceptance estate. The accessibility and phone-width check opens each of the eleven screens of the area for a role its list in model/ux/screens.yaml names and asserts the rules of docs/planes/experience/studio/localization-accessibility.md: WCAG 2.2 AA by the automated checks, every action reachable by keyboard with a visible focus ring and focus returned to the triggering control after a dialog, status badges with text and never colour alone, server refusals explained in words, reduced motion honoured, in English, Russian and Hebrew rendered right to left, in light and dark, at 1440 by 900 and at 390 by 844, where the page has no horizontal scroll. The end-to-end walk signs in as an asset maintainer, opens the catalog, a tool descriptor and its dry run, the MCP server registry, a model profile with its route-plan preview, a workflow definition with a validation and a template version with its compatibility, and then signs in as an observer and as a requester to see the same screens with the commands their roles allow or not offered. Each screen whose source is delivered after I3 shows that source as unknown in the freshness family and is listed by name. The record holds per screen and role the expected and observed result and the network log, which shows no address other than StudioBff and StudioRealtimeGateway. A failing screen is recorded with its failing rule and the area stays open.
Acceptance criteria
| AC1 | Given each screen of the Assets area in model/ux/screens.yaml, when the accessibility check runs in the three locales, both schemes and the two viewports of docs/planes/experience/studio/localization-accessibility.md, then every screen passes the automated WCAG 2.2 AA checks and keyboard operation, renders Hebrew right to left, and has no horizontal scroll at 390 by 844 (NFR-15, FUX-12). |
| AC2 | Given the end-to-end walk as an asset maintainer, an observer and a requester, when it runs on the acceptance estate, then every screen renders from StudioBff/GetScreenModel, the commands offered match the roles of model/ux/screens.yaml, and a screen of a later source shows that source as unknown and is listed by name (ADR-0007). |
| AC3 | Given the network log and the record of the walk, when they are read, then the browser called no address other than StudioBff and StudioRealtimeGateway and the record holds one line per screen and role with the expected and observed result (FUX-12). |
| Traces: services | StudioBff |
| Traces: apis | StudioBff/GetScreenModel |
| Traces: adrs | ADR-0007 |
| Traces: requirements | FUX-12 |
| Relates: screens | asset-catalog, release-detail, agent-card, tool-descriptor, mcp-servers, model-profiles, workflow-definitions, template-catalog, marketplace-browse, marketplace-installations, publisher-console |
| Relates: nfrs | NFR-15 |
| Depends on | AIFACTORY-US-1391, AIFACTORY-US-1392, AIFACTORY-US-129, feature:studio-bff, feature:component-blazor-shell |
| Sources | model/ux/screens.yaml, docs/planes/experience/studio/localization-accessibility.md, docs/planes/experience/studio/screens/assets.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5627 End-to-end walk of the Assets area with three roles |
fixture | A browser-driven walk in the Studio repository that signs in as an asset maintainer, an observer and a requester, opens the eleven screens of the Assets area, performs the dry run, the route-plan preview, the workflow validation and the compatibility query, and records per screen and role the rendered state, the offered commands and the addresses the browser called. | ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5628 Accessibility and phone-width check of the Assets screens |
verification | Run dotnet test -c Release --filter Category=Accessibility, npx playwright test --project=chromium at 1440 by 900 and npx playwright test --project=phone-390x844, the Playwright project of the Studio at 390 by 844, on the eleven screens in en, ru and he, light and dark; the results prove AC1 of AIFACTORY-US-1393 against docs/planes/experience/studio/localization-accessibility.md. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5629 Verify the walk record of the Assets area |
verification | Run the walk of AIFACTORY-TASK-5627 on the acceptance estate; its record and network log prove AC2 and AC3 of AIFACTORY-US-1393 (StudioBff/GetScreenModel), every screen of a later source is listed by name, and the record is kept with the evidence of increment I3. | ConnectSoft.AI.SoftwareFactory.Studio |