githits 0.9.2 → 0.10.0

package/.claude-plugin/marketplace.json

@@ -6,12 +6,12 @@
   },
   "metadata": {
     "description": "The code context layer for AI coding agents",
-    "version": "0.9.2"
+    "version": "0.10.0"
   },
   "plugins": [
     {
       "name": "githits",
-      "version": "0.9.2",
+      "version": "0.10.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.9.2",
+  "version": "0.10.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.9.2",
+  "version": "0.10.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.9.2",
+  "version": "0.10.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.9.2",
+  "version": "0.10.0",
   "description": "The code context layer for AI coding agents",
   "author": {
     "name": "GitHits"

package/AGENTS.md

@@ -118,14 +118,20 @@ See `docs/guidelines/TESTING.md` for comprehensive patterns.
 
 ## Release Boundaries
 
-- Keep `CHANGELOG.md` current during development. Every notable user-, agent-, operator-, or public-API-visible change must update `Unreleased` in the same change, including the explicit pending SemVer impact for every public artifact. Follow `docs/implementation/release-process.md`.
+- Every notable user-, agent-, operator-, or public-API-visible change must add
+  one independent `changes/<unique-name>.<category>.md` fragment with an
+  explicit pending SemVer impact for every public artifact. Do not edit
+  `CHANGELOG.md` outside release preparation. Follow
+  `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.
 - `@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.
 - Successful `Main` runs on `main` trigger both root and MCP release workflows. The MCP workflow publishes only when the package version is not already published; manual dispatch is for recovery or dry runs.
-- Release preparation moves shipped entries from `Unreleased` into separate versioned sections for each released artifact and leaves a fresh impact table with pending bumps reset to `none`.
+- Release preparation consumes all fragments into separate versioned sections
+  for each released artifact and deletes the consumed files.
 - Validate package behavior from outside root path aliases. Repo-local imports can hide package export-map or declaration problems.
 
 ### Common Pitfalls

package/README.md

@@ -127,6 +127,31 @@ npx githits@latest docs list npm:express
 npx githits@latest docs read <page-id> --lines 20-80
 ```
 
+## Experimental Tools
+
+GitHits 0.10 adds two opt-in local tools for early dogfooding:
+
+- `resolve_target` / `githits resolve` turns a fuzzy or ambiguous package or
+  repository name into ranked canonical targets.
+- `code_diff` / `githits code diff` compares repository trees resolved from
+  exact package versions or public GitHub refs.
+
+They are hidden and disabled by default. They are available only through the
+local `githits` CLI and local stdio MCP server; the hosted MCP and plugin or
+extension installs keep the stable tool set. Enable them in the GitHits host
+config, then restart the coding agent so it restarts the local MCP server:
+
+```toml
+# macOS/Linux: ~/.config/githits/config.toml
+# Windows: %APPDATA%\githits\config.toml
+[experimental]
+tools = true
+```
+
+See [Experimental tools](docs/experimental-tools.md) for platform-specific
+config discovery, CLI examples, optional issue reporting, limitations, and how
+to disable the tools.
+
 ## Supported Sources
 
 GitHits works with package and repository targets such as:
@@ -350,11 +375,11 @@ githits example          Find real-world implementations from open source
 githits languages        List or filter supported programming languages
 githits feedback         Submit feedback about GitHits results
 githits doctor           Diagnose configuration and auth state
-githits resolve          Resolve a package or GitHub repository name to canonical targets
+githits resolve          Experimental: resolve a fuzzy name to canonical targets
 githits settings         View and update preferences, privacy, and terms
 githits search           Explore repository code, dependencies, docs, and symbols
 githits search-status    Check the status of a previous indexed search
-githits code             List, read, and grep indexed dependency source
+githits code             List, read, grep, or experimentally diff indexed source
 githits pkg              Inspect package metadata, vulnerabilities, deps, and changelogs
 githits docs             Browse and read package documentation
 githits auth             Manage authentication