Auto-onboarding: kloning af et CURABIS-repo onboarder maskinen selv

Setup v15: projekt-CLAUDE.md-templatens self-heal udvidet fra kun
mirror til hele maskinen - mangler ~/.claude/CLAUDE.md eller bridgen,
koerer sessionen Install-CurabisMachine.ps1 fra stable selv
(idempotent, identitet fra git config), rapporterer de manuelle
rest-trin (personlig secret, AL: Configure MCP Server) og beder om
Claude Code-genstart. Mirror-only-staleness beholder det lette
self-heal.

CONSUMPTION.md: Auto-trigger-afsnit - een-linjes-kommandoen er
fallback, ikke procedure; foerste session i et klonet repo goer
arbejdet.

Torsten-scenariet (frisk maskine, manuel onboarding-viden paakraevet)
forsvinder dermed for alle fremtidige udviklere.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Michael Dieringer 2026-07-03 15:39:24 +02:00
parent 13e9861351
commit 8e1c392181
2 changed files with 20 additions and 6 deletions

View file

@ -51,6 +51,13 @@ personal client secret), the knowledge sync script, and syncs the machine
mirror. Per repo afterwards: VS Code → `AL: Configure MCP Server` (generates
`.vscode/find-altool.ps1`), then "Opdater CURABIS Standard fra BCQuality".
**Auto-trigger:** the command above rarely needs to be run by hand. Every
project CLAUDE.md (setup v15+) carries a machine self-heal: any Claude Code
session in any configured CURABIS repo detects an un-onboarded machine
(missing `~/.claude/CLAUDE.md` or bridge) and runs the onboarding itself —
cloning a CURABIS repo IS the onboarding. Only the personal client secret
and the VS Code AL extension remain manual by design.
## Release channel: `stable`
Merging to `main` is **not** a deployment. All consumers — the machine