Maskin-onboarding: Install-CurabisMachine.ps1 - een kommando pr. ny udvikler

Torsten er den foerste friske udvikler paa kaeden, og maskinlaget
self-healer ikke: global CLAUDE.md, bridge og personlig BC-secret
skulle haandopsaettes uden procedure. Nu:

- custom/setup/machine/Install-CurabisMachine.ps1: idempotent
  onboarding - global CLAUDE.md fra template (identitet fra git
  config), bridge, config-template (personlig secret manuel),
  sync-script + mirror, versionsmarkoer. Roerer ALDRIG eksisterende
  CLAUDE.md eller config. Alt hentes som raa bytes fra stable.
- CONSUMPTION.md: Machine onboarding-sektion med een-linjes-kommandoen
  og de to manuelle efterfoelgende trin (client secret + AL: Configure
  MCP Server pr. repo).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Michael Dieringer 2026-07-03 15:22:56 +02:00
parent 0750def417
commit 1c875787f0
2 changed files with 95 additions and 0 deletions

View file

@ -38,6 +38,19 @@ future CI/PR-review integration:
currently consumed by nothing. Keep it — but do not mistake it for active
configuration of the session model.
## Machine onboarding (new developer)
A fresh developer machine is made CURABIS-ready with ONE command
(idempotent — safe to re-run):
powershell -ExecutionPolicy Bypass -Command "Invoke-WebRequest -UseBasicParsing https://raw.githubusercontent.com/Curabis/BCQuality/stable/custom/setup/machine/Install-CurabisMachine.ps1 -OutFile $env:TEMP\icm.ps1; & $env:TEMP\icm.ps1"
It installs the global CLAUDE.md (identity substituted from git config),
bc-mcp-bridge.js, the bc-mcp config template (the developer inserts their
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".
## Release channel: `stable`
Merging to `main` is **not** a deployment. All consumers — the machine