githits 0.12.1 → 0.13.0

package/.claude-plugin/marketplace.json

@@ -6,12 +6,12 @@
   },
   "metadata": {
     "description": "The code context layer for AI coding agents",
-    "version": "0.12.1"
+    "version": "0.13.0"
   },
   "plugins": [
     {
       "name": "githits",
-      "version": "0.12.1",
+      "version": "0.13.0",
       "description": "The code context layer for AI coding agents",
       "author": {
         "name": "GitHits"

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "githits",
-  "version": "0.12.1",
+  "version": "0.13.0",
   "description": "The code context layer for AI coding agents",
   "author": {
     "name": "GitHits"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "githits",
-  "version": "0.12.1",
+  "version": "0.13.0",
   "description": "The code context layer for AI coding agents",
   "author": {
     "name": "GitHits"

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "githits",
-  "version": "0.12.1",
+  "version": "0.13.0",
   "description": "The code context layer for AI coding agents",
   "author": {
     "name": "GitHits"

package/.plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "githits",
-  "version": "0.12.1",
+  "version": "0.13.0",
   "description": "The code context layer for AI coding agents",
   "author": {
     "name": "GitHits"

package/AGENTS.md

@@ -140,7 +140,7 @@ See `docs/guidelines/TESTING.md` for comprehensive patterns.
   `docs/implementation/release-process.md` and `changes/README.md`.
 - Treat dated, versioned changelog sections as immutable historical records. Change them only to correct blatant, demonstrable factual errors, and keep any correction minimal.
 - `githits` and `@githits/mcp` have separate release flows. They may be bumped together when both surfaces changed, but CLI-only changes should not bump `@githits/mcp`.
-- Root `githits` release versions must stay aligned with generated plugin/assistant manifests: `.plugin/plugin.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json`, `.cursor-plugin/plugin.json`, `.claude-plugin/marketplace.json`, and `gemini-extension.json`. The versionless Antigravity `plugin.json` and `mcp_config.json` must also be regenerated and checked.
+- Root `githits` release versions must stay aligned with generated plugin/assistant manifests: `.plugin/plugin.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json`, `.cursor-plugin/plugin.json`, `.claude-plugin/marketplace.json`, `gemini-extension.json`, and the portable/Antigravity `plugin.json`. The versionless `mcp_config.json` must also be regenerated and checked.
 - `@githits/mcp` release versions live in `packages/mcp/package.json` and should change only for MCP package API, tool behavior, MCP instructions, schemas, MCP auth/error behavior, or remote-server-facing public type changes.
 - For coordinated CLI and MCP releases, keep the MCP minor aligned with the CLI minor for discoverability. The first MCP release for a CLI minor starts at `X.Y.0`; later MCP-package-visible changes in that CLI minor bump the MCP patch.
 - A request to audit, prepare, create, cut, or release a version authorizes release preparation through opening the release PR only; it does not authorize merging, enabling auto-merge, tagging, or publishing. Merging requires separate, explicit human approval given after the release PR exists and identifying that PR. Earlier release requests do not count. Stop after opening the PR, report its URL and check status, and wait for that approval.

package/README.md

@@ -125,7 +125,7 @@ Browse and read package documentation:
 
 ```sh
 npx githits@latest docs list npm:express
-npx githits@latest docs read <page-id> --lines 20-80
+npx githits@latest docs read <docs-read-target> --lines 20-80
 ```
 
 ## Experimental Tools