Release v7.27.0

Summary

An opt-in cratis/codescene profile lets agents use CodeScene Code Health as a gate on their own changes. Repositories and contributors that have not opted in are unaffected.

Added

• cratis/codescene profile, not part of cratis or cratis/full. It provides the CodeScene MCP server (cs-mcp), four CodeScene skills (safeguarding-ai-generated-code, guiding-refactoring-with-code-health, prioritizing-technical-debt, risk-based-testing-with-code-health) and a Code Health policy rule (#584)
• The skills are taken from codescene-oss/codescene-mcp-server under Apache-2.0. Apart from licence metadata and modification notices, the only changes are an opt-in guard and a pointer to the Cratis policy. Each skill applies only in repositories that select the profile and have the CodeScene MCP tools available
• The Code Health policy judges the change, not the file:
  • changed files must not decline in Code Health, and new files must score at least 9.0
  • files that already score low are improved only through dedicated, tested work
  • generated code is excluded, and Cratis conventions take precedence over findings
  • state-changing CodeScene tools need the user's approval

Changed

• Pi rule delivery now honours cratis/<profile>-scoped rules: in a repository with .cratis/ai.json, such a rule loads only when it selects that profile or one nested under it. application and framework rules behave as before