@erclx/aitk 0.46.0 → 0.46.1

package/README.md

@@ -21,7 +21,7 @@ claude plugin install aitk@aitk
 
 ![Adding the aitk marketplace and installing the plugin in Claude Code](assets/install.png)
 
-The skills land as `/aitk:<name>`. If your session was already open, run `/reload-plugins` to pick them up. Updates arrive on release, so a push to this repo won't reach your installed copy.
+The skills land as `/aitk:<name>`. If your session was already open, run `/reload-plugins` to pick them up.
 
 Several skills call the `aitk` CLI to read catalogs and run installs, and the plugin doesn't put it on your path. Install it from the registry.
 
@@ -31,6 +31,20 @@ bun install --global @erclx/aitk
 
 [Bun](https://bun.sh) is the CLI runtime and has to be on your path first. Confirm the install by resolving `aitk --help`.
 
+## Update
+
+Nothing refreshes on its own. Claude Code ships auto-update off for third-party marketplaces, so an installed copy serves whatever version it was installed at until you refresh it.
+
+```bash
+claude plugin marketplace update aitk
+claude plugin update aitk@aitk
+bun install --global @erclx/aitk
+```
+
+The first two update the skills, the third updates the CLI, and they move independently. Restart Claude Code, or run `/reload-plugins`, to pick the skills up.
+
+To stop doing this by hand, turn auto-update on once under `/plugin` in the Marketplaces tab. Confirm what you are running with `aitk --version` and `claude plugin list`.
+
 ## Why
 
 Every AI coding setup accumulates the same assets. Prompts to reuse, rules agents should follow, slash commands, skills, seed docs, sync scripts. Once you have enough projects, your copies drift and your agents stop getting consistent signals.

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "aitk",
   "description": "Automated governance, versioning, and discovery tools for Claude Code.",
-  "version": "0.46.0",
+  "version": "0.46.1",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/docs/target-projects.md

@@ -12,7 +12,7 @@ This doc stays at the narrative layer. For command flags and JSON shapes, see [a
 
 ## Getting the skills
 
-The skills reach a session through a marketplace install, once per machine. Every session on that machine carries them afterward, and updates arrive on release, so an upstream push does not reach an installed copy.
+The skills reach a session through a marketplace install, once per machine. Every session on that machine carries them afterward, and the installed copy stays at the version it was installed at. Claude Code ships auto-update off for third-party marketplaces, so neither a push nor a release reaches that copy until someone refreshes it with `claude plugin marketplace update aitk` followed by `claude plugin update aitk@aitk`, or turns auto-update on once under `/plugin`. The `aitk` CLI moves on its own schedule through the registry, so a machine can hold current skills against a stale CLI or the reverse.
 
 ```bash
 claude plugin marketplace add https://github.com/erclx/aitk

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/aitk",
   "type": "module",
-  "version": "0.46.0",
+  "version": "0.46.1",
   "description": "Infrastructure and quality tooling for developer workflows",
   "license": "MIT",
   "bin": {

package/src/cli.ts

@@ -1,5 +1,7 @@
 #!/usr/bin/env bun
 
+import { readFileSync } from 'node:fs'
+import { join } from 'node:path'
 import { Command } from 'commander'
 import { register as init } from '@/commands/init'
 import { register as sandbox } from '@/commands/sandbox'
@@ -20,6 +22,7 @@ import { register as transcripts } from '@/commands/transcripts'
 import { register as tasks } from '@/commands/tasks'
 import { register as comments } from '@/commands/comments'
 import { register as context } from '@/commands/context'
+import { PROJECT_ROOT } from '@/exec'
 
 const GREY = '\x1b[0;90m'
 const WHITE = '\x1b[1;37m'
@@ -87,10 +90,26 @@ function showHelp(): void {
   console.log(lines.join('\n'))
 }
 
+/**
+ * Read at runtime rather than inlined, because a literal here is a second place
+ * the version lives and it stopped tracking `package.json` at `0.1.0`. The
+ * release tool writes one file and this follows it. `package.json` ships in
+ * every npm tarball regardless of the `files` list, so the read resolves from a
+ * registry install as well as from a clone.
+ */
+function readVersion(): string {
+  try {
+    const raw = readFileSync(join(PROJECT_ROOT, 'package.json'), 'utf8')
+    return (JSON.parse(raw) as { version?: string }).version ?? 'unknown'
+  } catch {
+    return 'unknown'
+  }
+}
+
 const program = new Command()
 program
   .name('aitk')
-  .version('0.1.0')
+  .version(readVersion())
   .enablePositionalOptions()
   .helpOption(false)
 program.action(() => showHelp())