CI and green builds

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Platform Specification.

CI runs per repo and submodule. When red, use GitHub CLI before guessing:

gh run list --limit 5
gh run view <run-id> --log-failed

Superrepo changes often need commits in compiler, pckg, or beskid_vscode first, then a submodule pointer bump—pushing only the parent repo is a classic way to achieve “green locally, red everywhere.”

Website CI

site/website prebuild tests typed embeds and catalog-backed platform-spec aliases before Astro renders the Book. Root CI separately runs openspec validate --all --strict; neither build may substitute for the other.