Persist the scope selected when creating Flows and Entries

[gbaudrit]

Area

Console

Description

The Flow and Entry create editors render a ResourceScopeFormField bound to a local selectedScope, but the selected value is never included in the create/save operation. The controls therefore present an ownership choice that has no effect.

Evidence on current main:

• NewFlow.razor declares and binds selectedScope, then calls CreateDraftAsync or CreateFlowAsync without using it.
• EntryEditor.razor declares and binds selectedScope, then calls SaveEntryAsync(EntryResourceNamespace, Draft(), ...) without using it.
• The Agent editor provides the expected contrast by applying ScopeRef = selectedScope to its request.

Expected behavior

Creating a Flow or Entry in the Console persists the ownership scope selected by the user, and the resulting resource is visible from exactly that scope according to the resource-scope policy.

Observed behavior

Changing the displayed scope selector does not change the request made by either editor. The server receives no selected scope, so it applies the default/current behavior independently of the user choice.

Reproduction steps

1. Open the Console on current main with more than one writable resource scope.
2. Open Flows > New or create a new Entry.
3. Select a non-default writable scope.
4. Create/save the resource.
5. Inspect the request or resulting resource ownership.
6. Observe that the selected scope was not propagated.

Environment

• Agentstration commit: 43c209c (current origin/main during the FR Provide reusable Playwright journeys for UX tests and communication captures #283 / PR feat(testing): add reusable Playwright browser journeys #170 Playwright review).
• Storage: behavior is visible before the storage boundary and is not storage-profile-specific.
• Provider: deterministic/default; provider-independent.
• OS and .NET SDK: source-level review; runtime reproduction still required.

Observed impact

Major

Regression

Unknown

Relevant logs

No runtime logs captured. The bound selectedScope value has no read usage in either component.

Attachments

None.

Preliminary checks

• I searched for an existing issue covering this behavior.
• I removed secrets, credentials, personal data, and sensitive content from this report.

Related browser-coverage work: #283, #288, and #291.