@mrciphersmith/keryx 0.2.16 → 0.2.18

package/README.md

@@ -166,6 +166,32 @@ keryx shell --chat                            # chat without tools
 keryx shell --provider ollama --model gemma4:e4b     # fully local
 ```
 
+### Version update advisory
+
+`keryx shell` starts one bounded, non-blocking version check in the background.
+It shows a notice only when the registry returns a strictly newer validated
+version; it never installs anything and never blocks the shell or project work.
+The same check is available to humans and agents with:
+
+```bash
+keryx version check [--json]
+```
+
+Successful metadata is cached for 24 hours, failed checks are suppressed for 15
+minutes, and each registry request times out after 2 seconds. When an update is
+available, the exact command is:
+
+```bash
+npm install -g @mrciphersmith/keryx@latest
+```
+
+Offline, timed-out, unknown, or otherwise unavailable results remain advisory
+and do not stop work. The generated `.metaproject/index.md` instruction is
+prompt guidance rather than enforcement, and existing installations from
+before the first feature-bearing release cannot discover that release through
+code they do not yet contain; existing projects gain the guidance only after
+their index is regenerated or updated.
+
 Here it is answering a blast-radius question through the project graph rather
 than by reading files and guessing — one tool call, twelve seconds:
 
@@ -315,6 +341,13 @@ Alternative install paths — the managed installer (`~/.keryx` with a wrapper i
 Bare `keryx` prints the main commands; `keryx shell` starts the agent harness
 described [above](#the-agent-harness).
 
+Agent mode protects each user turn with nested unique-signature budgets: `48`
+total, including at most `40` risk-`read` signatures and `8` non-read (or
+unknown-risk) signatures. An identical `tool + normalized input` may retry up
+to three times while occupying one unique slot. Reaching a limit exactly still
+gives the model a normal round to answer; only a new signature beyond a pool or
+a no-progress repeat loop forces the final tool-free wrap-up.
+
 ## Agent integrations
 
 | Runtime | Integration |
@@ -328,6 +361,11 @@ After `init`, agents follow the root `AGENTS.md`/`CLAUDE.md` pointer to
 `.metaproject/index.md`, which routes them to the right capability. Two commands
 sharpen that routing:
 
+`keryx orient` emits a bounded excerpt of the launch project's own
+`.metaproject/index.md`, followed by the graph map and wiki index. The excerpt
+directs the agent to read the full project-root entrypoint; it does not discover
+or substitute an ancestor Metaproject.
+
 ```bash
 keryx orient install-hook --runtime codex   # graph + wiki map at turn start
 keryx agents bootstrap install --runtime claude