githits 0.22.1 → 0.23.0

package/dist/shared/{chunk-qjdh687v.js → chunk-4h6ejk0r.js}

@@ -1 +1 @@
-import{loadAutoLoginAuthSessionMetadata2,clearAutoLoginAuthSessionMetadata2,createAuthCommandDependencies2,createLogoutCommandDependencies2,createAuthStatusDependencies2,createContainer2}from"./chunk-737pd53s.js";export{clearAutoLoginAuthSessionMetadata2 as clearAutoLoginAuthSessionMetadata,createAuthCommandDependencies2 as createAuthCommandDependencies,createAuthStatusDependencies2 as createAuthStatusDependencies,createContainer2 as createContainer,createLogoutCommandDependencies2 as createLogoutCommandDependencies,loadAutoLoginAuthSessionMetadata2 as loadAutoLoginAuthSessionMetadata};
+import{loadAutoLoginAuthSessionMetadata2,clearAutoLoginAuthSessionMetadata2,createAuthCommandDependencies2,createLogoutCommandDependencies2,createAuthStatusDependencies2,createContainer2}from"./chunk-09ym653m.js";export{clearAutoLoginAuthSessionMetadata2 as clearAutoLoginAuthSessionMetadata,createAuthCommandDependencies2 as createAuthCommandDependencies,createAuthStatusDependencies2 as createAuthStatusDependencies,createContainer2 as createContainer,createLogoutCommandDependencies2 as createLogoutCommandDependencies,loadAutoLoginAuthSessionMetadata2 as loadAutoLoginAuthSessionMetadata};

package/dist/shared/{chunk-zged479w.js → chunk-rff2rnht.js}

@@ -1,2 +1,2 @@
-var description="The code context layer for AI coding agents";var version2="0.22.1";
+var description="The code context layer for AI coding agents";var version2="0.23.0";
 export{description,version2};

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "githits",
-  "version": "0.22.1",
+  "version": "0.23.0",
   "description": "The code context layer for AI coding agents",
   "mcpServers": {
     "githits": {

package/githits-icon.svg

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="UTF-8"?><svg id="Layer_2" xmlns="http://www.w3.org/2000/svg" width="1024" height="1024" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 1024 1024"><defs><style>.cls-1{fill:#fff;}.cls-2{fill:url(#linear-gradient);}</style><linearGradient id="linear-gradient" x1="82.04" y1="992.89" x2="989.54" y2="-22.11" gradientTransform="translate(0 1024) scale(1 -1)" gradientUnits="userSpaceOnUse"><stop offset=".29" stop-color="#ff4fae"/><stop offset="1" stop-color="#ff872f"/></linearGradient></defs><g id="Layer_1-2"><rect class="cls-2" width="1024" height="1024"/><path class="cls-1" d="M793.15,498.08h-160.84v-174.61h-80.1v388.96h80.1v-137.13h160.84v137.13h80.1v-388.96h-80.1v174.61Z"/><path class="cls-1" d="M410.43,575.29h-85.87v-76.89h173.01s3.84,13.78,3.52,38.77c-.96,98.04-81.06,177.82-179.1,178.46h-1.6c-115.66,0-208.58-96.44-203.45-213.38,4.81-103.17,87.79-187.11,190.95-193.52,67.28-3.84,128.16,24.67,167.89,71.77l-55.11,55.11c-24.67-32.36-65.04-52.54-109.89-49.34-62.16,4.49-112.14,54.79-116.62,116.94-5.13,73.69,53.19,135.21,125.91,135.21s89.71-63.12,89.71-63.12h.64Z"/></g></svg>

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "githits",
   "description": "The code context layer for AI coding agents",
-  "version": "0.22.1",
+  "version": "0.23.0",
   "mcpName": "com.githits/githits",
   "type": "module",
   "workspaces": [
@@ -18,6 +18,7 @@
     "mcp.json",
     "server.json",
     "gemini-extension.json",
+    "githits-icon.svg",
     "plugin.json",
     "mcp_config.json",
     "AGENTS.md",
@@ -53,6 +54,7 @@
     "plugins:generate": "bun run scripts/generate-plugin-assets.ts",
     "plugins:check": "bun run scripts/generate-plugin-assets.ts --check",
     "audit:pkg-ecosystems": "bun run scripts/pkg-ecosystem-audit.ts",
+    "bench:list-text": "bun run scripts/list-text-size-benchmark.ts",
     "agent:e2e": "bun run scripts/agent-eval.ts",
     "agent:e2e:suite": "bun run scripts/agent-eval-suite.ts",
     "agent:e2e:report": "bun run scripts/agent-eval-report.ts",

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "githits",
-  "version": "0.22.1",
+  "version": "0.23.0",
   "description": "The code context layer for AI coding agents",
   "author": {
     "name": "GitHits"

package/server.json

@@ -16,7 +16,7 @@
     "source": "github",
     "id": "1165453165"
   },
-  "version": "0.22.1",
+  "version": "0.23.0",
   "remotes": [
     {
       "type": "streamable-http",
@@ -28,7 +28,7 @@
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "githits",
-      "version": "0.22.1",
+      "version": "0.23.0",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"

package/skills/githits-code/SKILL.md

@@ -25,9 +25,9 @@ Use GitHits for evidence from real open-source code instead of guessing from mod
 - Need package metadata, vulnerability/advisory status, dependency graphs, or release notes: stop and use the `githits-package` skill instead.
 - Inspecting a known dependency or public repository: start with `githits search` scoped by `--in`.
 - Searching an exact standalone documentation site: use `githits search "<topic>" --source docs --in site:<host[/path]>`. If the result reports suggested site targets, retry one explicitly; suggestions are advisory targets, not aliases.
-- Need file/path enumeration: use `githits code files`; do not probe directories with `githits read`.
+- Need file/path enumeration: use `githits list <target> [paths...]`; add `--recursive` to traverse directories. Do not probe directories with `githits read`.
 - Know the exact text to match: use `githits code grep` (literal by default). Pass `--regex` for RE2 syntax; lookaround and backreferences are unsupported. Use `githits search` for discovery.
-- Need documentation pages: use `githits search "<topic>" --source docs --in <target>` for topic search, or `githits docs list <spec>` to browse available pages. Read returned targets with `githits read`.
+- Need documentation pages: use `githits search "<topic>" --source docs --in <target>` for topic search, or `githits list site:<host[/path]>` to browse a hosted site. Package/repository `list` targets include their local documentation files. Read emitted targets and paths with `githits read`; `githits docs list` remains a legacy package-page browser.
 
 ## Core Commands
 
@@ -41,13 +41,14 @@ githits search '"body parser" OR multer' --in npm:express --source docs
 githits search "middleware" --in site:expressjs.com --source docs
 githits search-status <searchRef>
 
-githits code files npm:express@5.2.1 lib/ --ext js --limit 100
+githits list npm:express@5.2.1 lib/ --recursive --limit 100
 githits read npm:express@5.2.1 lib/express.js --lines 1-90
 githits read 'npm:express@5.2.1#Router'
 githits read npm:express@5.2.1 --selector Router
 githits code grep npm:express@5.2.1 "require('router')" lib/ -C 3
 githits code grep --repo-url https://github.com/expressjs/express --git-ref v5.2.1 "require('router')" lib/
 
+githits list site:expressjs.com --limit 20
 githits docs list npm:express --limit 20
 githits read <docsReadTarget>
 githits read <docsReadTarget> --selector <heading-id>
@@ -61,6 +62,7 @@ githits read <docsReadTarget> --selector <heading-id>
 - For docs reads, use the search snippet when sufficient; otherwise run its generated `followUp`. From text, pass the displayed `[docs page]` target unchanged; from `docs list`, pass `docsReadTarget`. Hosted/crawled HTTP(S) targets address mutable current content, so automatic follow-ups forward the exact URL or fragment without search bounds. A fragment returns its heading and full subtree through the next equal-or-higher heading. Use `--selector <heading-id>` for a known logical heading ID without a URL fragment. Repository docs remain snapshot-addressed and keep returned ranges. Add `--lines` only when intentionally selecting a current page range; either bound replaces heading selection. Historical `pageId` works. Use `--json` only for required range/source metadata.
 - For multi-step code/docs investigations, keep raw CLI output out of the final answer unless it is the evidence the user needs.
 - Reuse returned targets, paths, locators, references, and ranges; never invent them. Cite the served target and report stale/provisional evidence, truncation, and coverage limits.
+- For a site inventory, pass the emitted `site:` target and host-relative page path separately to `githits read`. For list pagination, use `--json` to obtain `nextCursor`, then replay the same target and filters with `--after <nextCursor>`; do not edit the cursor. `list --wait` uses milliseconds.
 - Partial and capped documentation coverage are usable published evidence. Report the disclosed limit, but infer neither indexing progress nor retryability from coverage; follow only `searchRef` and the evidence notice.
 - Follow rendered continuation/recovery actions. Use `search-status <searchRef>` only when search explicitly supplies that follow-up; never repeat search to poll or poll a stopped reference. See `references/code-and-docs.md` for status/wait details.
 - If discovery search returns no useful hits, do not repeat it unchanged. Follow the rendered pivots; when the query is now an exact identifier or string, switch to `githits code grep` and read the focused match because symbol discovery may not include re-exports or generated aliases.

package/skills/githits-code/references/code-and-docs.md

@@ -6,7 +6,7 @@ Package target syntax requires an explicit registry: `registry:name@version`, fo
 
 `githits search "<query>" --in <target>` searches indexed dependency code, docs, symbols, and exact standalone documentation sites. Repeat `--in` for multiple targets. Use `--source code`, `--source docs`, or `--source symbol` to force a source; omit it for auto-routing. For a standalone site, pass `--source docs --in site:<host[/path]>`.
 
-Search text shows producer-proven matched source and structural documentation previews. Path-only matches render as compact file headers; they do not prove a source-content match. Follow the emitted read locator when source context is needed. JSON preserves compatibility evidence and adds indexed-field provenance, matched source, and documentation previews.
+Search text shows producer-proven matched source and structural documentation previews. Path-only matches render as compact file headers; they do not prove a source-content match. Follow the emitted read locator when source context is needed. JSON carries indexed-field provenance, matched source, semantic context, and documentation previews; retired summary, summary-highlight, content-safety, and compatibility focused-source fields are absent.
 
 Useful filters: `--kind`, `--category`, `--path-prefix`, `--intent`, `--public`, `--name`, `--lang`, `--limit`, `--offset`, `--wait`, `--allow-partial`, `--json`.
 
@@ -25,9 +25,17 @@ re-exports or generated aliases.
 
 If a missing or ambiguous site returns suggested site targets, retry one of those exact labels explicitly. They are advisory, not aliases, and GitHits does not select or retry one automatically. A truncation notice means more valid candidates were omitted.
 
-## Code Files
+## List
 
-`githits code files <spec> [path-prefix]` lists paths. Use this before `githits read` when you do not know the exact file path.
+`githits list <target> [paths...]` browses one package source tree, repository snapshot, or explicit `site:<host[/path]>` inventory. Package/repository inventories include local documentation files; hosted documentation requires a site target. Quote glob selectors so the shell does not expand them. Add `--recursive` to traverse matched directories.
+
+Useful flags: repeatable `--file-type`, `--language`, `--intent`, `--limit` (1-500), `--after`, `--wait` (milliseconds, 0-300000), `--silent`, `--json`. Text lists paths with direct read guidance; `--silent` emits paths only. JSON retains read/browse actions, lifecycle metadata, and `nextCursor`. Continue by replaying the same selection with the returned opaque cursor. Prefer exact emitted read actions to reconstructed locators.
+
+`githits read <site-target> <host-relative-page-path>` reads an emitted site PAGE action, including `/` for the root. A site display path alone is not a read locator.
+
+## Legacy Code Files
+
+`githits code files <spec> [path-prefix]` retains its existing behavior for compatibility; prefer `githits list` for new CLI inventory calls.
 
 Useful filters: `--path`, repeatable `--glob`, repeatable `--ext`, repeatable `--file-type`, repeatable `--language`, repeatable `--file-intent`, repeatable `--exclude-intent`, `--exclude-docs`, `--exclude-tests`, `--hidden`, `--limit`, `--wait`, `--verbose`, `--json`.
 
@@ -46,7 +54,7 @@ When grep returns no matches, do not repeat it unchanged. Change or shorten the
 
 ## Docs
 
-`githits docs list <spec>` browses available documentation pages. It is not topic search.
+`githits docs list <spec>` remains the legacy mixed package documentation-page browser. Prefer `githits list site:<host[/path]>` for hosted inventories or a package/repository `list` target for local documentation files. Neither listing command is topic search.
 
 For `githits read <target>`, use the search snippet when sufficient; otherwise run its generated `followUp`. From text, pass the displayed `[docs page]` target unchanged; from `docs list`, pass `docsReadTarget`. Hosted/crawled HTTP(S) targets address mutable current content, so automatic follow-ups forward the exact URL or fragment without search bounds. A fragment returns its heading and full subtree through the next equal-or-higher heading. Use `--selector <heading-id>` for a known logical heading ID without a URL fragment. Repository docs remain snapshot-addressed and keep returned ranges. Add `--lines` only when intentionally selecting a current page range; either bound replaces heading selection. Historical `pageId` values remain supported. `githits docs read` remains a compatibility alias. Use `--json` only for required range/source metadata.
 
@@ -60,13 +68,15 @@ Partial and capped documentation coverage are usable published evidence. Report
 - `githits search` maps to MCP `search`.
 - `githits search-status` maps to MCP `search_status`.
 - `githits code files` maps to MCP `code_files`.
+- `githits list` has no unified MCP counterpart yet; MCP retains `code_files` and `docs_list`.
 - `githits code grep` maps to MCP `code_grep`.
 - `githits read <target> <path>` maps to MCP `read` with `target` and `path`.
 - `githits read <target> --selector <name>` maps to MCP `read` with `target` and `selector`, optionally with `path` for code.
 - `githits read '<target>#<symbol>'` maps to MCP `read` with the fragment in `target`, optionally with `path` for code.
 - `githits docs list` maps to MCP `docs_list`.
 - `githits read <docs-target>` maps to MCP `read` with `target` alone.
+- `githits read <site-target> <host-relative-page-path>` maps to MCP `read` with `target` and `path`.
 
-Direct repository targets accept approved full HTTPS URLs on github.com, codeberg.org, and gitlab.com. Codeberg requires exactly owner/repo; GitLab allows nested namespaces. Only GitHub supports host shorthand and HTTP compatibility. Never infer a provider from bare owner/repo. Repository refs use an @ suffix and may themselves contain / and @; # is reserved for semantic fragments. Empty refs and mixed suffixes are invalid. Credentials, queries, provider web subpaths, and unsupported/self-hosted hosts are rejected. Package targets keep registry-native coordinates, including `zig:cb/owner/repo` and `swift:gitlab.com/group/project`. Changelog repo URL fields remain full HTTPS URLs.
+Direct repository targets accept approved full HTTPS URLs on github.com, codeberg.org, and gitlab.com. Codeberg requires exactly owner/repo; GitLab allows nested namespaces. Only GitHub supports host shorthand and HTTP compatibility. Never infer a provider from bare owner/repo. Repository refs use an @ suffix and may themselves contain / and @; # is reserved for semantic fragments. Empty refs and mixed suffixes are invalid. Credentials, queries, provider web subpaths, and unsupported/self-hosted hosts are rejected. Package targets keep registry-native coordinates, including `zig:cb/owner/repo` and `swift:gitlab.com/group/project`.
 
 GitLab web paths with `/-/` or reserved routes such as `tree`, `blob`, and `raw` are rejected. Unreserved names such as `issues` can be repository path components; without a web-route marker, the client treats the complete nested path as repository identity.

package/skills/githits-onboarding/SKILL.md

@@ -22,6 +22,7 @@ a GitHits account and configure GitHits unless they explicitly say otherwise.
 - Use `npx -y githits@latest ...` for every normal onboarding command. This guarantees the latest published GitHits CLI behavior for new users.
 - Do not use a globally installed `githits` binary for onboarding unless the user explicitly asks to test a local, dev, or pinned CLI build.
 - If the user explicitly asks for local/dev/pinned testing, preserve the command and environment they provide.
+- For explicit development testing, `GITHITS_ENV=dev` selects CLI/local MCP service defaults and a separate login namespace; use the same environment for login and verification. Unset or `prod` uses production. URL overrides remain independent; use `GITHITS_CODE_NAV_URL` instead of the removed `PKGSEER_URL`. This selector does not reconfigure hosted MCP connections or plugin endpoints.
 - Prefer `--json` for staged `init` commands because agents need stable fields.
 - Do not start `npx -y githits@latest` as a background task. If `npx` fails because of network, DNS, or package-fetch errors, stop and report that GitHits CLI is unavailable.