githits 0.11.2 → 0.11.4

package/.claude-plugin/marketplace.json

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

package/.plugin/plugin.json

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

package/AGENTS.md

@@ -32,6 +32,18 @@ Philosophy: "Create architecture that is performant and easy to test"
 
 See `docs/guidelines/ARCHITECTURAL_GUIDELINES.md` for detailed planning checklist and design principles.
 
+## Tool output UX
+
+Human-readable tool text is an optimized product surface, not raw field
+serialization. Before editing it, inspect real output and preserve existing
+strengths: lead with the outcome, group related evidence, remove repetition and
+scaffolding, and retain stable follow-up locators, actions, and trust facts.
+Wrap free prose to the caller's width, keep formatter-authored punctuation ASCII
+while preserving backend Unicode, and never make color carry meaning. When CLI
+and MCP need the same information, share one formatter per tool with color and
+width as inputs; keep JSON lossless for machines. A complete data dump is not
+good output merely because it is complete.
+
 ## Testing
 
 Philosophy: "If it is not tested, it is likely broken"
@@ -40,7 +52,7 @@ Philosophy: "If it is not tested, it is likely broken"
 
 - Use `bun test` for running tests
 - Use `bun run smoke:mcp` and `bun run smoke:cli` when changing MCP tools, CLI commands, shared formatters, auth/error envelopes, or MCP/CLI parity behavior. These are live-capable local suites, not the normal unit suite; they must pass unauthenticated by validating auth handling, and provide deeper coverage when authenticated. After building, also run `bun run smoke:cli:built` and `bun run smoke:mcp:built` when changing smoke launch behavior or CI product validation; these secret-free modes execute `dist/cli.js` under Node.
-- Use `bun run agent:e2e` when changing MCP instructions, tool descriptions, or agent-facing tool behavior. This is a human/agent-driven qualitative eval, not a deterministic CI gate. Pick targeted workloads from `eval/agentic/README.md`; run both Claude and Codex for broad instruction changes when practical. Inspect `tool-calls.json` and `final.json` for actual tool use, `toolIssues`, `instructionIssues`, and usefulness, not just harness pass/fail.
+- Use `bun run agent:e2e` when changing MCP instructions, tool descriptions, or agent-facing tool behavior. This is a human/agent-driven qualitative eval, not a deterministic CI gate. Pick targeted workloads from `eval/agentic/README.md`; run both Claude and Codex for broad instruction changes when practical. Inspect `tool-calls.json` and `final.json` for actual tool use and the neutral answer/confidence, `metrics.json` for derived token/cost/duration/tool-call metrics, and `isolation-violations.json` for trace-validation failures, not just harness pass/fail. Treat usefulness or quality as reportable only when a later grading stage provides it.
 - Maintain smoke coverage when adding or changing user-facing tools/commands. Prefer structural UX assertions over brittle snapshots, and keep MCP `format: "json"` and CLI `--json` behavior aligned.
 - When changing GraphQL/API selections, add regression tests for over-fetch controls (for example `@include` variables, body omission, field lists, or query builders) and live-smoke the affected CLI/MCP surfaces when authenticated access is available.
 - Keep tests async and isolated
@@ -114,8 +126,9 @@ See `docs/guidelines/TESTING.md` for comprehensive patterns.
 - Root `src/**` is still the published `githits` CLI implementation until the CLI package move completes. It owns Commander commands, local auth storage, browser login, init/setup flows, local stdio MCP startup, plugin/assistant packaging assets, and the diagnostics implementation/lifecycle (environment, process, and output destinations).
 - `packages/core-internal` is private source. It owns transport-neutral service clients, service interfaces, shared request/header primitives, the host-supplied `ServiceDiagnostics` contract, neutral service errors, PKCE helpers, and `TokenProvider`. It must not discover diagnostics environment settings or own diagnostics process/output destinations. Never publish or leak `@githits/core-internal` into public artifacts.
 - `packages/mcp` is the public `@githits/mcp` package. Its public tool/server API is `packages/mcp/src/index.ts`: transport-neutral MCP server creation, tool registration, descriptors, instructions, request-scoped service provider types, and MCP service types. Its public runtime/client API is `packages/mcp/src/client.ts`, exported as `@githits/mcp/client`, for remote MCP servers that need concrete service implementations, token/header/config helpers, and optional injected `ServiceDiagnostics`.
+- The production hosted server at `https://mcp.githits.com` lives in the separate `remote-mcp` repository and consumes the published `@githits/mcp` package as the canonical implementation of tool registration, descriptors, `quick_start`, and tool logic. `remote-mcp` owns HTTP transport, request-scoped service composition, auth/session handling, deployment, and observability; do not duplicate package-owned MCP behavior there. A change in this repository reaches hosted clients only after `@githits/mcp` is released, `remote-mcp` updates that dependency, and the hosted server is deployed.
 - `@githits/mcp/smoke-test` is a public validation helper entrypoint for remote MCP servers. It exports smoke assertions and `runMcpSmoke()` without depending on local CLI startup.
-- `@githits/mcp/internal` is a workspace-only alias for root CLI transition helpers. External packages and the future remote MCP server repo must never import it. If remote server work needs something internal, promote the smallest stable API through `@githits/mcp` instead.
+- `@githits/mcp/internal` is a workspace-only alias for root CLI transition helpers. External packages and the `remote-mcp` repository must never import it. If remote server work needs something internal, promote the smallest stable API through `@githits/mcp` instead.
 - Public package artifacts for both root `githits` and `@githits/mcp` must not contain `@githits/core-internal`, `workspace:*`, `@githits/mcp/internal`, or private source aliases in JS, declarations, or manifests. The public-package validator also rejects static `fs`, `node:fs`, `fs/promises`, and `node:fs/promises` imports in core source and packed MCP artifacts, and rejects direct core `process.stderr`/`process.stdout` access. These checks cover statically resolved string-literal module edges; they do not claim browser compatibility.
 
 ## Release Boundaries

package/README.md

@@ -132,8 +132,9 @@ npx githits@latest docs read <page-id> --lines 20-80
 
 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.
+- `resolve_target` / `githits resolve` turns a fuzzy or ambiguous package,
+  repository, or documentation-site name into grouped canonical targets with
+  related project identities kept together.
 - `code_diff` / `githits code diff` compares repository trees resolved from
   exact package versions or public GitHub refs.