Knowledge/bc mcp scope tasks to repo#60
Conversation
newrules
TranslateRules
- Invoke-CurabisEval.ps1: general compile + analyzers quality eval (hill-climbing score, reads each project's own al.codeAnalyzers + ruleset, logs .eval/history.jsonl). - Invoke-CurabisEvidence.ps1: citation evidence validator that fails on hallucinated knowledge-file or CURABIS rule-code references (cite-or-flag enforcement). - README documenting both. Fetched by Setup-CurabisAppSource.ps1 into each project's scripts folder. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add curabis eval scripts
Rules derived from BC MCP API page development experience: - api-page-flowfields-must-be-calcfields: FlowFields return empty on API pages unless explicitly CalcFields'd in OnAfterGetRecord - stored-derived-fields-must-not-be-exposed-directly: Stored fields updated only via OnValidate triggers can be stale; recalculate live in OnAfterGetRecord - api-page-key-fields-must-be-editable-on-insert: ODataKeyFields with Editable=false are rejected as unknown properties on POST - api-page-least-privilege-write-access: Create dedicated minimal pages per write concern rather than widening general-purpose pages - agent-must-not-write-business-process-status: Agents must only write developer-tracking fields; business status fields affect invoicing/time registration Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- test-one-when-per-test: one WHEN per test, split if multiple actions - ui-test-codeunit-naming: _UT suffix for TestPage-based codeunits - test-feature-scenario-tags: [FEATURE]/[SCENARIO] comment structure Based on patterns from Automatiserede tests med Business Central (Dieringer). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Startup & agents
AutoUpdate
When a developer asks for open tasks, only return tasks from the project(s) linked to the current git repository. Flag it if no project is linked. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Deploys carlin.agent.md to all CURABIS projects via curabis-standard. Carlin surfaces with one dry observation when complexity, vague requirements, or feature creep earns it. Named after the CURABIS Kick-off 2026 Lego duck exercise. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
👋 Heads up @MichaelDieringer — and cc maintainers — this PR introduces new top-level entries that aren't part of BCQuality's known repository structure:
This isn't a block — just a flag. 🚩 New top-level folders and files are usually unintended (a stray export, a tool's scratch dir, or content that meant to land inside an existing layer like If this was intentional and the new entry genuinely belongs at the repo root, a maintainer can review and merge as normal — no action needed beyond a quick sanity check. If it wasn't, please move the content into the right existing layer (or drop it) and push an update. 🙏 A maintainer will take a look before merging. |
|
Hey @MichaelDieringer 👋 First off — thank you for jumping in and experimenting! It's awesome to see people pushing on the framework. 🎉 That said, let me gently redirect you, because I think there's a small but important misunderstanding about how the The The intended workflow is:
That way you get full control, your changes survive upstream updates cleanly, and you can pull in new core releases from this repo whenever you want. ✨ Now — here's the fun part: if while building out your fork you discover knowledge, patterns, or agents that you think would genuinely benefit everyone using BCQuality (not just your team), that's exactly what the Going to close this PR for now (since it's targeting Files in this PR that triggered the auto-close
May your merges be conflict-free. 🚀 🤖 This PR was closed automatically by the |
1 participant
No description provided.