[Validation only - do not merge] API workflow infrastructure before AL uptake

[Prangshuman Das (t-prda)]

Validation only - do not merge

AB#646383

Validate the exact workflow-only intermediate, before AL uptake at review #11891. The tree matches that review branch; a forward-only validation merge preserves its historical ancestry, so commit heads differ; there are no validation-only code changes. This main-targeted draft remains outside native stack #11893 and must not be merged or auto-merged.

Review order: #10085 auth core -> #11862 URL/fixture prerequisites -> #11891 workflow infrastructure -> #11860 AL uptake -> #11224–#11230 -> #11322 -> #11451–#11454.

Main-target validation preserves warning-baseline policy. Previously observed missing feature-base baselines and the later stale-main AS0059 findings are different failures; neither is suppressed.

All AL source/exclusions equal integrated main df3ab2d79eb97aed4bef8db42748bc7fa3331a65; the 11 auth/URL methods are inherited. The real HTTP test belongs to subsequent uptake, not this workflow-only stage.

Clean-codeunit activation is absent/off at this stage. Ordinary execution, Legacy and the Unit Disabled fallback remain; newly discovered API Disabled-isolation lanes are activated only by uptake with authentication adoption.

Validation limits

Historical uptake/full runs verified CU139496 MicrosoftAuthenticationRespectsServerAuthMode in the actual UserPassword fixture (401/200/401). The Windows 200/200/200 expectations are implemented but Windows runtime remains unverified; no foreign local NST was used. Successful GitHub runs do not establish universal native NAV coverage. Excluded PDF cases, country-specific absent/excluded cases and tolerated-native distinctions are not claimed passing. No additional PR was merged or auto-merged during this refresh; validation drafts remain Do Not Merge outside stack #11893.

Historical targeted country evidence

Final workflow NZ Integration artifact at 9269e3df582704881a898e19029308e9296cbbf1 verifies 2,751 test cases, zero failures, and CU139700 absent. This confirms the default-off gate no longer prematurely runs the API Items codeunit that previously had 22 failures. Workflow run36157073629 succeeded with all113 test jobs.

Current checkpoint

Head 779308ea339d2ce54624f64376b36faf2ef20b72, tree 1f7315f2d7c72d7cc1e239db458d831f3257cbf5; parent df3ab2d79eb97aed4bef8db42748bc7fa3331a65.

Forward-merged actual remote main df3ab2d79eb97aed4bef8db42748bc7fa3331a65 into the open workflow root, then propagated the existing stack. The earlier PR API base SHA was stale; this refresh uses the actual Git main ref. Merged PRs #10085/#11862 are untouched. Permission cleanup from PR 11561 remains inherited; no force-push, rebase, PR merge or auto-merge was used.

The APIV2 exclusion conflict was resolved by replaying each layer's original exclusion-key delta onto the new parent, preserving all upstream entries/metadata and duplicate multiplicities. The new company/environment-description test remains excluded; older deliberately removed API exclusions were not restored. All fourteen owned non-exclusion patches and exact file scopes are unchanged. Expense re-enablement ownership remains4+5+1+2; the eleven restricted permission observations remain intact.

Local Pester:103 passed, zero failed/skipped at each refreshed workflow, uptake and full head. The three AL source-inspection checks remain removed; the remaining PowerShell test file matches workflow. Workflow retains exactly ten owned infrastructure files, default-off clean-codeunit execution, secure credential provisioning/cleanup, ordinary typed/Legacy behavior and the Unit Disabled fallback. No owned AL adoption is added to this stage.

Fresh runtime validation is pending, not passed. Previous successful AL/country evidence is historical after this baseline refresh. Windows runtime and excluded PDF/native cases remain unverified. Native stack #11893 and all user draft/ready states remain unchanged; validation drafts remain Do Not Merge outside the native group.

[github-actions]

Issue #11561 is not valid. Please make sure you link an issue that exists, is open and is approved.

[github-actions]

⚠️ Stale Status Check Deleted

The Pull Request Build workflow run for this PR was older than 72 hours and has been deleted.

📋 Why was it deleted?

Status checks that are too old may no longer reflect the current state of the target branch. To ensure this PR is validated against the latest code and passes up-to-date checks, a fresh build is required.

---

🔄 How to trigger a new status check:

1. 📤 Push a new commit to the PR branch, or
2. 🔁 Close and reopen the PR

This will automatically trigger a new Pull Request Build workflow run.