mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-10-05 14:46:55 +01:00
5fb29ee749
Felttest paa fremmed maskine afsloerede at VS Code-kommandoen AL: Configure MCP Server IKKE FINDES - den har staaet i setup- dokumentationen siden v6 og er blevet gentaget ukritisk siden, inkl. af Claude i dag. find-altool.ps1 var i virkeligheden haandlavet i Jernpladsen/Wareco (funktionelt identiske kopier). - custom/setup/templates/find-altool.ps1: kanonisk template med robust versionssortering ([version]-parse i stedet for leksikalsk) og klar fejlbesked ved manglende/for gammel AL-extension - Setup v16: 4b deployer filen fra templaten (raa bytes) og skriver ALTID al-entryen i .mcp.json; det betingede spor og fantom-noten er fjernet. Mode B: ny raekke deployer filen hvis den mangler - Install-CurabisMachine.ps1 + CONSUMPTION.md: pr.-repo-trinnet er nu bare Opdater CURABIS Standard - AL-extensionen fra Marketplace er eneste maskinforudsaetning - Roemer v5, station 12: AL MCP-wiring paa runden med autoriseret stille korrektion. Evidens: en session skrev AL-kode den ikke kunne compile og flagede det foerst ved forespoergsel (Conzept) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
100 lines
5.2 KiB
Markdown
100 lines
5.2 KiB
Markdown
# How CURABIS consumes BCQuality today
|
|
|
|
[agent-consumption.md](agent-consumption.md) describes the upstream
|
|
Microsoft/BCQuality architecture: an orchestrator invokes `/skills/entry.md`,
|
|
Entry dispatches layer action skills, each skill runs Source → Relevance →
|
|
Worklist → Action and emits DO-shaped findings. That document is the
|
|
*architecture*. This document is the *actual state* — which consumption paths
|
|
are live in the CURABIS fork, and which are dormant upstream inheritance.
|
|
|
|
## Active: the CURABIS Standard session model
|
|
|
|
The only consumption path in production. Deployed and updated by
|
|
[custom/setup/curabis-standard.agent.md](custom/setup/curabis-standard.agent.md):
|
|
|
|
- **Knowledge** is mirrored to each developer's machine at
|
|
`~/.claude/bcquality-knowledge/` (all three layers + `INDEX.md`) by
|
|
`custom/setup/sync-bcquality-knowledge.ps1`. The mirror is machine-local,
|
|
never committed to a project repo — see rule
|
|
`custom/knowledge/architecture/bcquality-knowledge-must-mirror-to-machine-not-repo.md`.
|
|
- **Sessions** (Claude Code, and Copilot via each repo's
|
|
`copilot-instructions.md`) read the project's `.github/.agents/bcquality.agent.md`
|
|
plus the machine mirror at session start: `custom/` in full, `community/` and
|
|
`microsoft/` on relevance via `INDEX.md`.
|
|
- **Agents** (`.github/.agents/*.agent.md`) are per-repo copies fetched from
|
|
`custom/agents/` and `custom/setup/templates/`, reconciled by Mode B.
|
|
|
|
## Dormant: the Entry/orchestrator flow
|
|
|
|
Inherited from upstream and kept in sync with it, but **no orchestrator invokes
|
|
it today** — no CURABIS AL-Go workflow references `entry.md`. Reserved for a
|
|
future CI/PR-review integration:
|
|
|
|
- `/skills/entry.md` + READ · DO · WRITE contracts
|
|
- Layer action skills (`microsoft/skills/review/*` — 12 review skills)
|
|
- `tools/Build-KnowledgeIndex.ps1` + `knowledge-index.json` generation
|
|
- `.github/bcquality.config.yaml` in project repos: the consumer pruning
|
|
policy for this flow (repo, ref, enabled-layers, disabled-skills). It is
|
|
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: "Opdater CURABIS Standard fra BCQuality" — it
|
|
deploys `.vscode/find-altool.ps1` (a CURABIS template; no VS Code command
|
|
generates it) and the AL MCP wiring itself. The AL Language extension from
|
|
the Marketplace is the only per-machine prerequisite for AL MCP.
|
|
|
|
**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
|
|
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
|
|
per-project `bcquality.agent.md` template, which Entry's skill discovery
|
|
(`*/skills/**/*.md`) never sees. Before wiring an orchestrator, move or
|
|
mirror the CURABIS review skill into `custom/skills/review/`.
|
|
2. **Two index generators.** The session model's `INDEX.md` is generated by
|
|
`sync-bcquality-knowledge.ps1`'s own frontmatter parser; the Entry flow uses
|
|
`tools/Build-KnowledgeIndex.ps1` (CI-validated, schema in lockstep with the
|
|
Source contract). Converge on the official generator.
|
|
3. **Layer precedence is not mirrored.** The READ contract defines what wins
|
|
when layers conflict; the machine mirror carries knowledge only, so sessions
|
|
have no formal precedence rule.
|