v0.4.11

Fixes a redundant CI run on every promote.

consort keeps its own copy of the scaffold workflow templates (templates/project/common/.github/workflows); its kit refresh writes a project's .github/workflows from them. At promote, scm-merge compares against the pinned scm-utils templates and, on drift, self-heals by committing the refresh onto the PR head — which re-triggers the entire pr.yml CI (a redundant run every promote). consort's copies had drifted: merge.yml shipped lakebase-schema-migrate apply vs the pinned scm-utils apply-tier, and lacked the .NET/EF Core setup + the Flyway db/migrations/** guard.

• Synced merge.yml + pr.yml to the bundled scm-utils 0.3.1 (cleanup-orphans.yml already matched).
• New tests/bdd/workflow-template-drift-guard.test.ts byte-asserts consort's bundled workflow templates == the pinned scm-utils templates, with a header documenting the tiered-upgrade re-sync steps.
• Documented the e2e-assembly contract in the run-tests.sh template header (its Playwright block is appended per-project by enableE2eForProject, never inline — so it is intentionally not byte-guarded).

Pins scm-utils 0.3.1.