githits 0.10.0 → 0.10.2

package/server.json

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

package/skills/githits-code/SKILL.md

@@ -59,9 +59,10 @@ githits docs read <pageId> --lines 20-120
 - For source work, locate symbols or matches first, then read a focused window with explicit `--lines`.
 - Documentation text reads return at most 150 lines per call. Continue with explicit `--lines` windows when more context is needed; pass `--json` when you need `startLine`, `endLine`, or `totalLines` pagination metadata.
 - For multi-step code/docs investigations, keep raw CLI output out of the final answer unless it is the evidence the user needs.
-- If output says it used recent/stale indexed evidence, treat the displayed served target as provenance; if freshness matters, retry with a longer `--wait` or use one of the displayed `queryable now` versions/refs, or inspect JSON `targetResolution` for structured candidates.
+- If output says it used recent, stale, or provisional indexed evidence, treat the displayed served target as provenance. Provisional evidence is queryable while visibly still indexing. If freshness matters, follow the rendered continuation, retry with a longer `--wait`, use one of the displayed `queryable now` versions/refs, or inspect JSON `targetResolution` for structured candidates.
 - 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.
-- If search returns a `searchRef`, continue with `githits search-status <searchRef>` instead of repeating the original search. Its bounded wait defaults to 20 seconds; use `--wait <seconds>` with an integer from 0 to 60 to adjust it.
+- If search returns a `searchRef`, continue with `githits search-status <searchRef>` only when the output explicitly supplies that follow-up, including for active `PENDING`, `INDEXING`, or `SEARCHING` progress or a completed result with an evidence notice. Its bounded wait defaults to 20 seconds; use `--wait <seconds>` with an integer from 0 to 60 to adjust it. For terminal `DEFERRED`, `TIMEOUT`, or `FAILED` progress, or an unrecognized status, preserve any disclosed evidence, do not poll the reference again, and follow the rendered new-search action.
+- 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.
 - If grep returns no matches, do not repeat it unchanged. Follow the returned guidance by changing the pattern, broadening the file scope, or switching to `githits search` for conceptual discovery.
 - For a missing or ambiguous standalone site, use the returned `suggestedSiteTargets` in order. Do not rewrite the original target or retry automatically; when `suggestedSiteTargetsTruncated` is true, state that additional candidates were omitted.
 - If a code-navigation command returns `INDEXING`, use the elapsed/expected duration in the message to decide whether to retry with `--wait`; prefer any displayed indexed refs/versions when you need an immediate follow-up.

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

@@ -8,7 +8,16 @@ Package target syntax requires an explicit registry: `registry:name[@version]`,
 
 Useful filters: `--kind`, `--category`, `--path-prefix`, `--intent`, `--public`, `--name`, `--lang`, `--limit`, `--offset`, `--wait`, `--allow-partial`, `--json`.
 
-If search returns a `searchRef`, do not repeat the original search. Continue with `githits search-status <searchRef> [--wait <seconds>]`; the bounded wait defaults to 20 seconds, and the explicit value must be an integer from 0 to 60.
+If search returns a `searchRef`, continue with `githits search-status <searchRef> [--wait <seconds>]` only when the output explicitly supplies that follow-up, including for active `PENDING`, `INDEXING`, or `SEARCHING` progress or a completed result with an evidence notice. The bounded wait defaults to 20 seconds, and the explicit value must be an integer from 0 to 60. Terminal `DEFERRED`, `TIMEOUT`, or `FAILED` progress, and unrecognized statuses, do not advance: keep any disclosed evidence, do not poll the same reference, and follow the rendered new-search action.
+
+Stale or provisional evidence remains queryable while refresh or indexing
+continues. Treat the displayed served target as exact provenance and follow a
+`searchRef` only when the output renders the continuation.
+
+If discovery returns no useful hits, follow its rendered pivots instead of
+repeating it unchanged. Once the query is an exact identifier or string, use
+`code grep` and then read the focused match; symbol discovery may not include
+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.
 

package/skills/githits-mcp/SKILL.md

@@ -13,12 +13,12 @@ Scope boundaries:
 
 - GitHits indexes and searches public OSS repositories, package registry artifacts, and public package documentation. It does not index the user's local workspace, private repositories, uncommitted changes, or proprietary code unless that code is also available as public OSS/package evidence.
 - When the user references a public GitHub repository, GitHub file URL, package docs, or OSS registry package, prefer GitHits by translating the reference into a GitHits repository or package target. Use generic web search when GitHits lacks the content or the target is not available through GitHits.
-- If a public target is not indexed yet, wait for GitHits indexing to finish or retry with the provided indexing guidance. Do not fall back to generic web search just because indexing is still in progress.
+- If a public target is not fully indexed, use any returned provisional evidence with its exact served identity and follow only the rendered indexing or `search_status` guidance. Do not fall back to generic web search just because indexing is still in progress.
 
 Use the most targeted GitHits MCP tool or combination of tools for the job:
 
 - Use `search` and `docs_*` for package documentation, repository docs, exact APIs, configuration, or setup behavior.
-- For an exact standalone documentation site, call `search` with target `site:<host[/path]>` and source `docs`. Follow a returned `searchRef` with `search_status`; if a missing or ambiguous site instead returns `suggestedSiteTargets`, retry one exact suggestion explicitly rather than rewriting the target or treating it as an alias.
+- For an exact standalone documentation site, call `search` with target `site:<host[/path]>` and source `docs`. Follow a returned `searchRef` with `search_status` only when the output explicitly supplies that follow-up, including for active `PENDING`, `INDEXING`, or `SEARCHING` progress or a completed result with an evidence notice. For terminal `DEFERRED`, `TIMEOUT`, or `FAILED` progress, or an unrecognized status, keep any disclosed evidence, do not poll the reference again, and follow the rendered new-search action. If a missing or ambiguous site instead returns `suggestedSiteTargets`, retry one exact suggestion explicitly rather than rewriting the target or treating it as an alias.
 - Use `search`, `code_files`, `code_grep`, and `code_read` for version-specific package/repository source, tests, symbols, call sites, and implementation evidence.
 - Use `pkg_info`, `pkg_vulns`, `pkg_deps`, `pkg_changelog`, and `pkg_upgrade_review` for package metadata, versions, adoption, vulnerabilities, dependency graphs, changelogs, and upgrade-review evidence.
 - Use `get_example` as the broad OSS-first discovery, planning, and research path for vague issues, unfamiliar errors, "how do others do this" questions, multi-library/API combinations, global implementation-pattern scans, and rare needle-in-the-haystack examples that may appear in only one or a few repositories. When the dependency or repository is already known, default to `search`, `docs_*`, and `code_*` first; add `get_example` when you need broader cross-project evidence or a hard-to-find real-world example.

package/dist/shared/chunk-vzkfjt3p.js

@@ -1 +0,0 @@
-import{clearAutoLoginAuthSessionMetadata,createAuthCommandDependencies,createAuthStatusDependencies,createContainer,createLogoutCommandDependencies,loadAutoLoginAuthSessionMetadata,recordAuthFingerprint}from"./chunk-4vxe5qg5.js";import"./chunk-q6aqsqv3.js";export{recordAuthFingerprint,loadAutoLoginAuthSessionMetadata,createLogoutCommandDependencies,createContainer,createAuthStatusDependencies,createAuthCommandDependencies,clearAutoLoginAuthSessionMetadata};