Add pipeline/automation knowledge: PowerShell (BcContainerHelper) and AL-Go for GitHub

[JesperSchulz]

Context

The README lists "PowerShell scripting for BC" and "Pipelines (AL-Go, GitHub Actions)" in scope, and the frontmatter schema already allows technologies: [powershell]. Zero knowledge files exist for either. A model can't take an app from source to a deployable artifact without this.

Why it matters (admission test)

LLMs get BcContainerHelper cmdlet names/parameters, the AL-Go settings schema, and CI/CD wiring wrong — these are tool-specific surfaces with no stable representation in general training data.

Scope / checklist

PowerShell / BcContainerHelper (microsoft/knowledge/powershell/)

• Artifacts — Get-BCArtifactUrl, Download-Artifacts.
• Containers — New-BcContainer, Compile-AppInBcContainer, Publish-/Install-/Sync-BcContainerApp, Run-TestsInBcContainer.
• Common scripting gotchas (credential handling, artifact/version selection).

AL-Go for GitHub (microsoft/knowledge/pipelines/)

• .github/AL-Go-Settings.json + project/workspace settings schema.
• Standard workflows (CI/CD, Test Current, Create Release, Deliver) and when each runs.
• useProjectDependencies, app vs. test-app folders, multi-project repos.
• Environments, secrets, and deliver/release flow.
• Versioning strategy.

Mark files technologies: [powershell] / [yaml] as appropriate.

---

Each new knowledge file must pass the README admission test and the CI-validated frontmatter schema.