Hardening: stable-branch som udrulningskanal - merge til main er ikke laengere deploy

Alle forbrugere laeser nu fra stable i stedet for main:
- curabis-standard.agent.md v10: BASE/AGENTS_BASE + self-heal-URL -> stable
- sync-bcquality-knowledge.ps1: $branch = stable
- machine/CLAUDE.md: auto-update gater paa stable-SHA og fetcher setup fra stable
- templates/bcquality.agent.md + al-triage.agent.md: knowledge-URLer -> stable
  (+ fix af doed reference: branch-merge-to-main-workflow.md var omdoebt til
  feature-branch-must-merge-to-track-branch.md - templaten shippede et 404)
- francis.agent.md + Invoke-CurabisEvidence.ps1: raw-base -> stable
- CONSUMPTION.md: Release channel-sektion med promote-procedure og rationale

Deploy sker herefter kun ved bevidst fast-forward af stable (kun Michael).
Kanal oprettet: stable @ 57b8292, tag v1.0.0.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

CONSUMPTION.md

@@ -38,6 +38,31 @@ future CI/PR-review integration:
   currently consumed by nothing. Keep it — but do not mistake it for active
   configuration of the session model.
 
+## Release channel: `stable`
+
+Merging to `main` is **not** a deployment. All consumers — the machine
+CLAUDE.md auto-update, `sync-bcquality-knowledge.ps1`, the setup agent's
+fetch URLs, and the agent templates' knowledge references — read from the
+**`stable`** branch, never from `main`. `main` is where PRs land and CI runs;
+`stable` is what every developer machine actually executes.
+
+Deploying is a deliberate act (Michael only):
+
+    git checkout stable
+    git merge --ff-only main
+    git push origin stable
+    git checkout main
+
+Optionally cut a version tag at the same commit (`git tag vX.Y.Z && git push
+origin vX.Y.Z`) for a historical record. If a bad change reaches `stable`,
+roll back by force-moving `stable` to the previous good commit — consumers
+follow the branch, so recovery is one push.
+
+Rationale: `main` used to be the live deploy channel — any merge silently
+overwrote `bc-mcp-bridge.js` (which handles S2S credentials) on every
+developer machine at next session start. The `stable` gate separates "CI
+accepted it" from "the organization runs it".
+
 ## Known deltas to close before activating the Entry flow
 
 1. **`custom/skills/` is empty.** The CURABIS review pass lives in the