@grum-os/cli 0.3.49 → 0.3.51

package/README.md

@@ -52,6 +52,8 @@ Use `codex`, `claude` (Claude Code) or `generic` instead of `cursor` for those a
 
 Rerunning setup refreshes existing integration files while preserving your own hooks and settings. The agent finishes verification with `grum_doctor` through MCP, which confirms the connection in that chat. If a shell check cannot verify the tools, it asks the agent to discover and call the tool before sending you to settings. Codex is ready when its MCP connection is confirmed and a hook has successfully run. Changed hook commands require review in Codex; new Grum releases using the same commands keep their existing trust.
 
+Grum's files for each agent (`.cursor/rules/grum.mdc` and the Grum blocks in `AGENTS.md` and `CLAUDE.md`) are short and rarely change. The detailed rules arrive as `guidance` in every `grum_contract` and `grum_check` result, and in `grum contract`, so a new Grum release does not need to edit them. When one of these files is from an older version, Grum updates it only after a successful `grum_contract` or `grum_check` call in MCP, and only when you already have other uncommitted work in the repository. Opening your editor, connecting Grum and hooks never write it, so a clean repository stays clean. Grum never stages the change; the tool result names the files it updated. A file that is staged, has your own edits, is a link or is not tracked is left alone, and the first result that skips it says so once. `grum doctor` lists every file it would skip. Run setup to update one yourself.
+
 Agent setup asks where your app runs locally. Repository URLs and `index.html` are suggestions; the agent must ask before selecting one. An older saved address is confirmed once. A local HTTP page must return 200; redirects, 404, access denial, connection refusal and timeouts keep setup incomplete. After a successful probe, the agent opens the page in its visible browser (Codex uses its browser panel), checks rendering, and reports any problems. Setup returns `preview-local-app` until the agent acknowledges the shown URL with `localPreviewed` in `grum_setup`, or `--local-previewed <url>` in the CLI. If browser control is unavailable, the agent asks you to open the URL and confirm it renders. A new address requires a new preview. An explicitly chosen static HTML file also needs preview; file existence does not prove rendering. Choose `none` only if you want to skip the local app.
 
 Agents may also open a page in their visible browser when they want you to see the page they are referring to or asking you about. Grum setup operations still use the CLI; when browser control is available, the agent opens the page itself.

package/content.md5

@@ -1 +1 @@
-d5fc9dcd3c7ecaef007d835831cbcbd0
+d38b8700027a5c3aef181ecf1088f71c