@contentrain/rules 0.5.0 → 0.5.1

package/context/context-bridge.md

@@ -4,7 +4,7 @@
 
 `context.json` is the project intelligence file. It provides AI agents and Contentrain Studio with structured knowledge about the project: its tech stack, content patterns, conventions, and normalize configuration.
 
-- **Written by:** MCP tools (committed together with content changes in the same branch, not as a separate commit)
+- **Written by:** MCP tools (regenerated on the `contentrain` branch after each merge — feature branches never carry it, so parallel writes cannot conflict on it)
 - **Read by:** AI agents (at the start of every session) and Studio (for UI configuration)
 - **Location:** `.contentrain/context.json`
 
@@ -206,7 +206,7 @@ When creating `context.json` for the first time, use stack-appropriate defaults.
 
 ## Update Behavior
 
-MCP tools update `context.json` as part of each write operation, committed together with the content changes in the same branch (not as a separate commit):
+MCP tools update `context.json` after each write operation lands. The file is never committed on `cr/*` feature branches (its timestamps would make parallel branches conflict); it is regenerated deterministically on the `contentrain` branch after merge:
 - `contentrain_init` creates the initial file
 - `contentrain_model_save` updates the domains list if a new domain is used
 - `contentrain_content_save` updates content stats

package/essential/contentrain-essentials.md

@@ -77,7 +77,7 @@ MCP is **deterministic infrastructure**. The agent (you) is the **intelligence l
 - Developer's working tree is never mutated during MCP git operations (no stash, no checkout, no merge on the developer's tree)
 - If the developer manually edits `.contentrain/` files, MCP sync skips dirty files and warns
 - The `contentrain` branch is protected from deletion
-- context.json is committed together with content changes, not as a separate commit
+- context.json is never committed on feature branches — it is regenerated on the `contentrain` branch after merge
 - Never create branches manually, never commit directly to main or the `contentrain` branch
 - 50+ active `cr/*` branches = warning, 80+ = blocked
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentrain/rules",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "license": "MIT",
   "description": "AI agent rules for Contentrain — quality standards, architecture conventions, IDE integration",
   "type": "module",
@@ -55,7 +55,7 @@
     "tsdown": "^0.21.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0",
-    "@contentrain/mcp": "1.5.0"
+    "@contentrain/mcp": "1.5.1"
   },
   "scripts": {
     "build": "tsdown src/index.ts --format esm,cjs --dts",

package/shared/mcp-usage.md

@@ -297,7 +297,7 @@ contentrain_apply(mode: "reuse", scope: {model: "model-id"}, dry_run: true) (pre
 - Branch naming: `cr/{operation}/{model}[/{locale}]/{timestamp}-{suffix}` (locale included when applicable; legacy `contentrain/*` branches are auto-migrated on first init).
 - You do not create branches manually. MCP handles Git transactions.
 - Developer's working tree is never mutated during MCP operations (no stash, no checkout, no merge on the developer's tree).
-- context.json is committed together with content changes, not as a separate commit.
+- context.json is never committed on feature branches — it is regenerated on the `contentrain` branch after merge.
 - In `auto-merge` mode: feature branch is merged into `contentrain`, then baseBranch is advanced via update-ref (fast-forward), then `.contentrain/` files are selectively synced to the developer's working tree. Dirty files are skipped with a warning.
 - In `review` mode: feature branch stays local until `contentrain_submit` pushes it to remote.
 

package/shared/workflow-rules.md

@@ -75,7 +75,7 @@ The `contentrain` branch is the **single source of truth** for content state:
 - Created automatically at `contentrain_init`.
 - All content writes happen on feature branches forked from `contentrain`.
 - The `contentrain` branch is **protected from deletion**.
-- context.json is committed together with content changes, not as a separate commit.
+- context.json is never committed on feature branches — it is regenerated on the `contentrain` branch after merge.
 
 ### 3.2 Worktree-Based Transactions