@mrciphersmith/keryx 0.2.17 → 0.2.18

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.
Files changed (3) hide show
  1. package/README.md +26 -0
  2. package/dist/cli.js +686 -279
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -166,6 +166,32 @@ keryx shell --chat # chat without tools
166
166
  keryx shell --provider ollama --model gemma4:e4b # fully local
167
167
  ```
168
168
 
169
+ ### Version update advisory
170
+
171
+ `keryx shell` starts one bounded, non-blocking version check in the background.
172
+ It shows a notice only when the registry returns a strictly newer validated
173
+ version; it never installs anything and never blocks the shell or project work.
174
+ The same check is available to humans and agents with:
175
+
176
+ ```bash
177
+ keryx version check [--json]
178
+ ```
179
+
180
+ Successful metadata is cached for 24 hours, failed checks are suppressed for 15
181
+ minutes, and each registry request times out after 2 seconds. When an update is
182
+ available, the exact command is:
183
+
184
+ ```bash
185
+ npm install -g @mrciphersmith/keryx@latest
186
+ ```
187
+
188
+ Offline, timed-out, unknown, or otherwise unavailable results remain advisory
189
+ and do not stop work. The generated `.metaproject/index.md` instruction is
190
+ prompt guidance rather than enforcement, and existing installations from
191
+ before the first feature-bearing release cannot discover that release through
192
+ code they do not yet contain; existing projects gain the guidance only after
193
+ their index is regenerated or updated.
194
+
169
195
  Here it is answering a blast-radius question through the project graph rather
170
196
  than by reading files and guessing — one tool call, twelve seconds:
171
197