[scout] Migrate onboarding deployment-agnostic API tests

[dmlemeshko]

Summary

Migrates Observability onboarding deployment-agnostic API integration coverage from the FTR suite (api_integration_deployment_agnostic/apis/onboarding) to Scout API tests under observability_onboarding/test/scout/api, with @kbn/scout-oblt + synthtrace fixtures, stateful + serverless tags, and auth aligned with the old FTR setup (cookies vs API keys where behavior differs). Removes the FTR onboarding API loadTestFile bundle and wires TypeScript Pattern A (test/scout/**/* in the plugin tsconfig + Scout kbn_references) so plugin-relative imports stay valid.

FTR file (removed)	Scout spec
get_progress.ts	onboarding_flow_progress.spec.ts
update_progress.ts	onboarding_flow_update_progress_404.spec.ts
update_progress.ts	onboarding_flow_update_progress_updates.spec.ts
custom_roles/index.ts	Inlined in onboarding_flow_progress.spec.ts (least-privilege / noAccessUserRole parity)

[rmyz]

obs-presentation changes LGTM

[csr]

Overall LGTM, I left a few comments. I also ran the tests on an observability MKI and they all pass.

[macroscopeapp]

🟡 Medium tests/onboarding_flow_update_progress_updates.spec.ts:39

The test creates two onboarding flows (lines 40-49 and 78-87) but onboardingId is overwritten by the second assignment before afterEach runs, so the first saved object is never deleted. Store both IDs or nest the steps in separate tests so cleanup runs between them.

        await apiTest.step('updates step status', async () => {
-          const createFlowResponse = await apiClient.post(
+          const createFlowResponse1 = await apiClient.post(
             'internal/observability_onboarding/flow',
             {
               headers: adminHeaders,
               responseType: 'json',
             }
           );
-          expect(createFlowResponse).toHaveStatusCode(200);
-          onboardingId = (createFlowResponse.body as { onboardingFlow: { id: string } })
+          expect(createFlowResponse1).toHaveStatusCode(200);
+          onboardingId = (createFlowResponse1.body as { onboardingFlow: { id: string } })
             .onboardingFlow.id;

🤖 Copy this AI Prompt to have your agent fix this:

In file x-pack/solutions/observability/plugins/observability_onboarding/test/scout/api/tests/onboarding_flow_update_progress_updates.spec.ts around lines 39-49:

The test creates two onboarding flows (lines 40-49 and 78-87) but `onboardingId` is overwritten by the second assignment before `afterEach` runs, so the first saved object is never deleted. Store both IDs or nest the steps in separate tests so cleanup runs between them.

Evidence trail:
x-pack/solutions/observability/plugins/observability_onboarding/test/scout/api/tests/onboarding_flow_update_progress_updates.spec.ts (viewed at REVIEWED_COMMIT):
- Line 19: `let onboardingId = ''` (single variable)
- Lines 21-28: `afterEach` hook deletes saved object by `onboardingId`
- Lines 48-49: First assignment of `onboardingId` in first step
- Lines 86-87: Second assignment overwrites `onboardingId` in second step
- Both steps are inside a single test (lines 30-113), so `afterEach` only runs once after both steps complete

[csr]

Recent changes LGTM. Thank you!

[benakansara]

actionable-obs changes LGTM

[kibanamachine]

Starting backport for target branches: 9.3

https://github.com/elastic/kibana/actions/runs/23682974324

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 5908511

Failed CI Steps

• x-pack/platform/test/serverless/functional/configs/security/config.group3.ts

Metrics [docs]

✅ unchanged

History

• 💚 Build #416097 succeeded f4953cd
• 💔 Build #416023 failed b3e59a9
• 💔 Build #415997 failed e9942d7
• 💔 Build #415933 failed 9d776b8
• 💔 Build #415836 failed 1835445
• 💔 Build #415782 failed 8ff237e

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	9.3	Backport failed because of merge conflicts You might need to backport the following PRs to 9.3: - Add kbn/test-saml-auth package (#259074) - Add kbn/test-es-server package (#259064) - Add shared validation runner package (#258768) - [Skills] Add Buildkite logs skill (#258587)

Manual backport

To create the backport manually run:

node scripts/backport --pr 259436

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259436 locally
cc: @dmlemeshko

[dmlemeshko]

💚 All backports created successfully

Status	Branch	Result
✅	9.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.
cc: @dmlemeshko