@cratis/pi 7.27.0 → 7.27.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -6,9 +6,11 @@ profile: cratis/codescene
6
6
 
7
7
  This policy applies only when the repository explicitly selects `cratis/codescene`
8
8
  or a descendant profile. It overrides the vendored CodeScene skills where they
9
- differ. Selecting the profile does not register the MCP server in every harness.
10
- Where registration is not supported, manually register `cs-mcp` as a stdio
11
- server in the harness's MCP configuration, or use `npx -y @codescene/codehealth-mcp`.
9
+ differ. Neither the Cratis CLI nor any harness registers the CodeScene MCP server,
10
+ because it needs a per-user CodeScene account and a locally installed binary.
11
+ Each user registers it in their own user-level MCP configuration, never in
12
+ committed project files: `cs-mcp` over stdio (`brew install cs-mcp`), or
13
+ `npx -y @codescene/codehealth-mcp`.
12
14
  CodeScene needs an account and OAuth `login`. Without an account or available
13
15
  CodeScene tools, skip these steps and say so; never block contributors who have
14
16
  not opted in.
@@ -141,7 +141,7 @@ Standalone Chronicle client usage (no Arc) in TypeScript is
141
141
  | `cratis/documentation` | Reader-centered product docs, technical examples, release notes, and voice review |
142
142
  | `cratis/content` | Release notes, social feed posts, voice review, content length, and developer marketing and distribution |
143
143
  | `cratis/review` | Code review, performance, security |
144
- | `cratis/codescene` | Opt-in CodeScene Code Health change gates, refactoring, debt prioritization and risk-based testing; requires an account and available MCP tools; server registration may be manual (see below) |
144
+ | `cratis/codescene` | Opt-in CodeScene Code Health change gates, refactoring, debt prioritization and risk-based testing; requires an account and available MCP tools; each user registers the MCP server (see below) |
145
145
  | `cratis/studio` | Studio MCP safety guidance |
146
146
  | `cratis/cli` | CLI operations |
147
147
  | `cratis/lens` | Lens browser extension |
@@ -158,9 +158,11 @@ The [CodeScene policy](./codescene.md) overrides those skills where they differ.
158
158
  No other profile, including `cratis` and `cratis/full`, composes it.
159
159
 
160
160
  The profile selects the `codescene` stdio server (`cs-mcp`, no arguments) from
161
- `mcp-servers.json`, but selecting it does not register the server in every harness.
162
- Where registration is not supported, manually register `cs-mcp` as a stdio
163
- server in the harness's MCP configuration, or use `npx -y @codescene/codehealth-mcp`.
161
+ `mcp-servers.json`, but neither the Cratis CLI nor any harness registers it,
162
+ because it needs a per-user CodeScene account and a locally installed binary.
163
+ Each user registers it in their own user-level MCP configuration, never in
164
+ committed project files: `cs-mcp` over stdio (`brew install cs-mcp`), or
165
+ `npx -y @codescene/codehealth-mcp`.
164
166
  CodeScene needs an account and OAuth `login`; without an account or available
165
167
  CodeScene tools, skip its steps and say so rather than blocking contributors.
166
168
  The MCP catalog has no install-hints field and does not install the executable.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cratis/pi",
3
- "version": "7.27.0",
3
+ "version": "7.27.1",
4
4
  "description": "Configuration-aware Cratis AI integration for Pi",
5
5
  "type": "module",
6
6
  "files": [