Allow pull_request:linked-issue ownership source

[JesperSchulz]

Symptom

The team-ownership classification workflow (.github/workflows/ownership-classification.yml) in microsoft/BCApps rejects correct classifications as malformed, failing with:

The ownership result from BCAppsTriage was malformed, so no labels were changed.

This broke a real PR: microsoft/BCApps #9561 (base releases/28.x, linked issue #5383) was correctly classified as team Integration with source: pull_request:linked-issue, but the workflow threw the malformed error and applied no labels.

Root cause

The Validate and apply ownership result step validates result.ownership.source against a hardcoded sources allowlist. A merged BCAppsTriage change (PR #40, linked-issue PR routing) added a new emitted source value pull_request:linked-issue — a PR whose team is adopted from its linked issue when the changed files are ambiguous. The BCApps allowlist was never updated, so any such result is rejected as malformed.

Fix

Add 'pull_request:linked-issue' to the sources allowlist, immediately after 'pull_request:incomplete-files'. This restores parity with the classifier's decision.js source set in BCAppsTriage — the only emitted source value missing from the allowlist. The allowlist now contains all 12 valid source values.

Single-line change; no other edits.

Fixes AB#642506

[github-actions]

Copilot PR Review

Iteration 3 · Outcome: no-knowledge

All 16 sub-skills ran and found no applicable AL knowledge: the PR's only changed file is a non-AL GitHub Actions workflow (.github/workflows/ownership-classification.yml), so no leaf's Worklist matched any content.

Knowledge source: https://github.com/microsoft/BCQuality@186d8a131465475c79244d994acb872cd5c0d4bf

No findings were posted for this iteration.

Orchestrator pre-filter (2 file(s) excluded)

• layer-disabled (knowledge) : 2 file(s)

_{Findings produced by the AL review agent v1.7.3. Reply 👎 on any inline comment to flag false positives.}