mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-10-05 14:46:55 +01:00
6c3e5ace35
Observed live: a consultant hit "no" reflexively on a setup confirmation while moving fast through onboarding, and only noticed afterward. Most of this document's ja/nej gates aren't real choices -- the standard is company policy, not a per-developer preference -- and a blocking question with only one sane answer just invites that kind of misclick. v24 -> v25. Converted to act-and-report (no question) wherever the file is git-tracked and the replacement is already verified correct: the v6-era repo-mirror cleanup, CLAUDE.md's obsolete-forms replacement, and the v24 migration's repo-local agent-file / find-altool.ps1 removal -- all fully recoverable via git revert if anyone ever wants the old version back. Converted the two genuine multi-developer-coordination steps (.mcp.json, .claude/settings.json -- whether every developer has migrated their own machine is a fact only a human knows) from a blocking question to a safe default (leave in place, report, offer removal later once a developer explicitly confirms). Left three gates as real questions, on purpose: uncommitted local changes on CLAUDE.md (actual risk of lost work), the developer's personal ~/.claude/CLAUDE.md (not git-tracked, carries personal customization), and the two "should I commit this?" prompts (commit timing is a legitimate choice, not a policy with one right answer). |
||
|---|---|---|
| .. | ||
| machine | ||
| templates | ||
| bc-mcp-bridge.js | ||
| curabis-standard.agent.md | ||
| support-users-onboarded.md | ||
| sync-bcquality-knowledge.ps1 | ||