[Fernando de Oliveira (fedeoliv)]

Discussion Link

Link: No linked discussion. Work is tracked by #39.

Context

Creating a CI pipeline does not ensure its checks are required before changes can merge into the integration branch.

Closes #39

Solution

Add a read-only protection check for created, changed, or detected pipelines, including mature projects and low-impact work. Inspect effective GitHub protection/rulesets or enabled blocking Azure DevOps build-validation policies. Recommend missing protection, retain explicit pending or unverified outcomes, and require approval before changing settings.

Stack dependency: #79. Merge that PR first, then retarget this PR to main if GitHub has not retargeted it automatically. This PR targets feature/38-required-work-item-labels so its diff contains only this issue's changes.

Validation

• npm --prefix docs run build: passed in an isolated snapshot of this PR's committed tree (39 pages).
• node --check docs/astro.config.mjs: passed.
• git diff feature/38-required-work-item-labels feature/39-pipeline-protection --check: passed.
• markdownlint --stdin --json --config .markdownlint.yaml: no new diagnostics versus the base across 7 changed Markdown/MDX files. Existing diagnostics are unchanged.
• Independent instruction review completed. No test board items or live branch-protection settings were changed.

Checklist

• Linked discussion exists
• Solution has been validated