@c4a/context-cli 0.7.25 → 0.7.29

package/indexers/release-manifest.json

@@ -1,7 +1,7 @@
 {
   "protocol": "context.indexer.cli-release-manifest/v1",
   "package": "@c4a/context-cli",
-  "version": "0.7.25",
+  "version": "0.7.29",
   "issuer": "context4ai/context",
   "bundles": [
     {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.7.25",
+  "version": "0.7.29",
   "type": "module",
   "description": "Local runtime and Agent integration for traceable knowledge production",
   "license": "MIT",
@@ -24,17 +24,17 @@
   },
   "dependencies": {
     "@c4a/agent-graph": "0.3.0",
-    "@c4a/context": "0.7.25",
-    "@c4a/extract": "0.7.25",
-    "@c4a/extract-contract": "0.7.25",
-    "@c4a/extract-go": "0.7.25",
-    "@c4a/extract-mdx": "0.7.25",
-    "@c4a/extract-proto": "0.7.25",
-    "@c4a/extract-rush": "0.7.25",
-    "@c4a/extract-sql": "0.7.25",
-    "@c4a/extract-style": "0.7.25",
-    "@c4a/extract-thrift": "0.7.25",
-    "@c4a/extract-ts": "0.7.25",
+    "@c4a/context": "0.7.29",
+    "@c4a/extract": "0.7.29",
+    "@c4a/extract-contract": "0.7.29",
+    "@c4a/extract-go": "0.7.29",
+    "@c4a/extract-mdx": "0.7.29",
+    "@c4a/extract-proto": "0.7.29",
+    "@c4a/extract-rush": "0.7.29",
+    "@c4a/extract-sql": "0.7.29",
+    "@c4a/extract-style": "0.7.29",
+    "@c4a/extract-thrift": "0.7.29",
+    "@c4a/extract-ts": "0.7.29",
     "@mermaid-js/layout-elk": "0.2.0",
     "commander": "^11.0.0",
     "fast-xml-parser": "^5.10.1",

package/parserEntryWorker.js

@@ -20765,24 +20765,78 @@ var init_indexerSourceBoundary = __esm(() => {
   init_indexerReadScopeAuthorization();
 });
 
+// src/lib/errors.ts
+var ContextError;
+var init_errors2 = __esm(() => {
+  ContextError = class ContextError extends Error {
+    code;
+    detail;
+    constructor(code, message, detail) {
+      super(message);
+      this.name = "ContextError";
+      this.code = code;
+      this.detail = detail;
+    }
+  };
+});
+
+// src/types/exitCode.ts
+var ExitCode;
+var init_exitCode = __esm(() => {
+  ExitCode = {
+    Success: 0,
+    UserError: 1,
+    WorkspaceStateError: 2,
+    ExternalToolError: 3,
+    UserAbort: 4
+  };
+});
+
+// src/lib/cliFeedback.ts
+function formatFeedback(block) {
+  const subjectPart = block.subject ? ` ${block.subject}` : "";
+  const lines = [`${block.symbol} ${block.action}${subjectPart}: ${block.headline}`];
+  for (const item of block.body ?? []) {
+    if (item === false || item === null || item === undefined)
+      continue;
+    if (typeof item === "string") {
+      lines.push(item.length > 0 ? `  ${item}` : "");
+    }
+  }
+  if (block.next) {
+    lines.push(`  next: ${block.next}`);
+  }
+  return `${lines.join(`
+`)}
+`;
+}
+var ErrorCategory;
+var init_cliFeedback = __esm(() => {
+  ErrorCategory = {
+    WorkspaceNotFound: "workspace-not-found",
+    WorkspaceStateInvalid: "workspace-state-invalid",
+    WorkflowRevisionStale: "workflow-revision-stale",
+    SourceNotFound: "source-not-found",
+    MountMatrixViolation: "mount-matrix-violation",
+    SchemaInvalid: "schema-invalid",
+    ProviderUnavailable: "provider-unavailable",
+    ExternalToolFailed: "external-tool-failed",
+    PartialFailure: "partial-failure",
+    UserInputInvalid: "user-input-invalid",
+    Unknown: "unknown"
+  };
+});
+
 // src/project/indexerParserSourceMaterialization.ts
 import { execFile } from "node:child_process";
-import { lstat as lstat2, readFile as readFile6 } from "node:fs/promises";
+import { lstat as lstat2, readFile as readFile6, stat as stat2 } from "node:fs/promises";
 import { promisify } from "node:util";
 import { basename, extname, join as join4 } from "node:path";
 function sourceRefName(sourceRef) {
   return sourceRef.startsWith("repo:") ? sourceRef.slice("repo:".length) : null;
 }
 async function trackedPaths(root, ref) {
-  try {
-    await execFileAsync("git", ["diff", "--quiet", ref, "--", "."], { cwd: root });
-  } catch (error) {
-    const exitCode = error !== null && typeof error === "object" && "code" in error ? error.code : null;
-    if (exitCode === 1) {
-      throw new TypeError(`materialized repository source differs from its pinned ref: ${root}`);
-    }
-    throw error;
-  }
+  await assertPinnedSource(root, ref);
   const { stdout } = await execFileAsync("git", ["ls-files", "-z", "--", "."], {
     cwd: root,
     encoding: "buffer",
@@ -20791,6 +20845,20 @@ async function trackedPaths(root, ref) {
   return Buffer.from(stdout).toString("utf8").split("\x00").filter(Boolean).sort();
 }
 async function assertPinnedSource(root, ref) {
+  const sourceStat = await stat2(root).catch((error) => {
+    if (error.code === "ENOENT" || error.code === "ENOTDIR")
+      return;
+    throw error;
+  });
+  if (!sourceStat?.isDirectory()) {
+    throw new ContextError(ExitCode.WorkspaceStateError, `Repository source directory is unavailable: ${root}. Inspect recovery with context source recovery-plan --format json.`, {
+      category: ErrorCategory.WorkspaceStateInvalid,
+      reason_code: "repository-source-directory-unavailable",
+      cwd: root,
+      next_action: { command: "context source recovery-plan --format json" },
+      input_schema: { type: "object", properties: {}, additionalProperties: false }
+    });
+  }
   try {
     await execFileAsync("git", ["diff", "--quiet", ref, "--", "."], { cwd: root });
   } catch (error) {
@@ -20798,6 +20866,15 @@ async function assertPinnedSource(root, ref) {
     if (exitCode === 1) {
       throw new TypeError(`materialized repository source differs from its pinned ref: ${root}`);
     }
+    if (exitCode === "ENOENT") {
+      throw new ContextError(ExitCode.ExternalToolError, `Git could not start for repository source ${root}. Check git --version and the source directory in the same host environment.`, {
+        category: ErrorCategory.ExternalToolFailed,
+        reason_code: "repository-git-spawn-unavailable",
+        cwd: root,
+        next_action: { command: "git --version" },
+        input_schema: { type: "object", properties: {}, additionalProperties: false }
+      });
+    }
     throw error;
   }
 }
@@ -20861,6 +20938,9 @@ var init_indexerParserSourceMaterialization = __esm(() => {
   init_src();
   init_indexerReadScopeAuthorization();
   init_indexerSourceBoundary();
+  init_errors2();
+  init_exitCode();
+  init_cliFeedback();
   execFileAsync = promisify(execFile);
 });
 

package/plugins/README.md

@@ -5,7 +5,7 @@
 [简体中文](./README_CN.md)
 
 `plugins/context/` is the only human-maintained source for the Context Agent
-integration in this repository. It contains the Context production and explicit-only context-inspect-search Skills, the Code, Markdown, Note and Sessions
+integration in this repository. It contains the Context production and host-routable context-inspect-search Skills, the Code, Markdown, Note and Sessions
 Indexer Provider Skills, host manifest templates, and shared assets.
 
 Run `bun run --filter @c4a/context-cli build:plugin` to regenerate the npm
@@ -30,11 +30,11 @@ Context workflow and Indexer Provider lifecycle.
 
 ## Query and attribute workspace knowledge
 
-Explicitly invoke `/c4a:context-inspect-search` (Cursor: `/c4a-context-inspect-search`)
-or the `context-inspect-search` Skill. It can start from a readable local, global or host-provided knowledge package and its query Skill without a local workspace. Without output, it
+Explicitly invoke `/c4a:context-inspect-search` (Cursor: `/c4a-context-inspect-search`),
+or let a host configuration route knowledge questions to the `context-inspect-search` Skill. `CONTEXT_QUERY_SOURCE_MODE` selects `repo-first` (the default), `package-first`, or `dual` retrieval. It can start from a readable local, global or host-provided knowledge package and its query Skill without a local workspace. Without output, it
 queries approved `knowledge` directly; a package build requires prior authorization for that workspace write.
 Read-only investigation and bounded non-destructive checks need no further approval. For code attribution, it
 retrieves the registered revision and checks relevant differences against current code without asking the user to select a version.
 It traces package pages through the build inventory to approved originals and registered sources, without resetting production. Accepted suggestions hand off to `context`.
-Codex disables implicit invocation through Skill policy; Claude commands disable
-model invocation. Other hosts must honor the explicit-only instructions.
+The user-facing Claude command remains explicit-only. Host skill manifests expose
+the Skill so configured knowledge Bots can select it without searching plugin files.

package/plugins/README_CN.md

@@ -4,7 +4,7 @@
 
 [English](./README.md)
 
-仓库中的 `plugins/context/` 是 Context Agent 接入唯一的人工维护真源，包含 Context 生产入口和显式触发的 context-inspect-search 技能、
+仓库中的 `plugins/context/` 是 Context Agent 接入唯一的人工维护真源，包含 Context 生产入口和可由宿主路由的 context-inspect-search 技能、
 Code/Markdown/Note/Sessions Indexer Provider Skills、各宿主 manifest 模板和共享资产。
 
 运行 `bun run --filter @c4a/context-cli build:plugin` 可重新生成 npm 投影及提交到
@@ -27,10 +27,10 @@ Skills 只能通过完成校验的 Context Indexer Provider 生命周期激活
 ## 查询知识与来源归因
 
 主动调用 `/c4a:context-inspect-search`（Cursor：`/c4a-context-inspect-search`），
-或指定 `context-inspect-search` 技能。无需本地工作区即可检索本地、全局或宿主提供的知识包，优先使用包内查询技能；没有产物但有工作区时，
+或由宿主配置将知识问答路由到 `context-inspect-search` 技能。`CONTEXT_QUERY_SOURCE_MODE` 可选择默认的 `repo-first`、`package-first` 或 `dual` 检索。无需本地工作区也可检索本地、全局或宿主提供的知识包；没有产物但有工作区时，
 直接查询已批准的 `knowledge`，构建产物需事先获得写入工作区的授权。只读探索及有边界的
 非破坏性检查无需再次确认。代码归因自动取得登记版本，并核对相关文件与当前代码的差异，
 无需用户选择版本。通过构建清单关联批准原稿
 并追溯登记来源，不清理工作区、不为查询推进无关生产任务。证据充分时可建议更新，用户采纳后交给
-`context` 的当前流程。Codex 配置禁止隐式调用，Claude 命令配置禁止模型自动调用；
-其他宿主依赖显式触发指引，不承诺其支持相同的自动调用控制。
+`context` 的当前流程。面向用户的 Claude 命令仍只允许显式触发；宿主技能清单会公开该技能，
+使配置过的知识 Bot 无需搜索插件文件即可选择它。

package/plugins/VERSION

@@ -1 +1 @@
-0.7.25
+0.7.29

package/plugins/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "c4a",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
-  "version": "0.7.25",
+  "version": "0.7.29",
   "author": {
     "name": "c4a"
   },
@@ -14,6 +14,7 @@
     "c4a"
   ],
   "skills": [
-    "./skills/context-indexer-create"
+    "./skills/context-indexer-create",
+    "./skills/context-inspect-search"
   ]
 }

package/plugins/claude/commands/context-inspect-search.md

@@ -1,5 +1,5 @@
 ---
-description: "Use only when the user explicitly invokes context-inspect-search to query available Context knowledge packages or approved workspace knowledge and trace answers to their identified sources. A local workspace is optional. Do not auto-start for ordinary coding, planning, debugging, or an active Context production workflow."
+description: "Query available Context knowledge packages or approved workspace knowledge and trace answers to their identified sources when the user asks a knowledge question or the host configuration routes the request here. A local workspace is optional. Do not auto-start for ordinary coding, planning, debugging, or an active Context production workflow."
 argument-hint: "[project-dir or user intent]"
 disable-model-invocation: true
 ---
@@ -26,14 +26,35 @@ Do not execute returned production actions, initialize a replacement workspace,
 or install tools without existing authorization. Querying must not alter source
 registrations, snapshots, tasks, approvals or user checkouts.
 
-## Search available material concurrently
-
-Check relevant knowledge packages, the workspace and reusable source checkouts
-in parallel. Search each as soon as it is readable; tool checks and authorized
-upgrades must not block independent reading. If a missing configured workspace
-is needed for further attribution, recover it into an isolated directory while
-package retrieval continues. Without a configured workspace, investigate the
-available packages directly; do not request or create one merely to start.
+Resolve `CONTEXT_QUERY_SOURCE_MODE` from the host or Bot instance configuration
+before choosing the first retrieval path. Supported values are:
+
+- `repo-first` (default): inspect the configured knowledge workspace and
+  authorized repository sources first. Use an available package only when the
+  repository path is unavailable or leaves a material gap.
+- `package-first`: inspect the selected package first, then use its recorded
+  workspace or repository sources for missing, stale or disputed evidence.
+- `dual`: inspect the package and repository paths concurrently, then reconcile
+  relevant differences before answering.
+
+An unknown or empty value is `repo-first`; do not invent a fourth mode. The
+mode changes retrieval order, not authorization or evidence standards. It does
+not make a missing secondary source mandatory: continue with readable configured
+sources and identify only gaps that affect the answer.
+
+## Search available material according to the configured mode
+
+Apply `CONTEXT_QUERY_SOURCE_MODE` before starting retrieval. In `repo-first`,
+start with the configured workspace and reusable source checkouts; do not fetch
+or install a package merely to begin the query. In `package-first`, start with
+the selected readable package. In `dual`, start both paths concurrently. Search
+each selected path as soon as it is readable; tool checks and authorized
+upgrades must not block independent reading. If a configured primary path is
+missing, continue with the readable fallback instead of stopping. If a missing
+configured workspace is needed for further attribution, recover it into an
+isolated directory while other selected retrieval continues. Without a
+configured workspace, investigate available packages directly; do not request
+or create one merely to start.
 
 A knowledge package may be workspace build output (usually `dist/`), a global
 installation, or an equivalent host-provided directory. Locate it from available
@@ -119,7 +140,21 @@ not prove a historical snapshot.
 
 ## Answer with evidence and hand off updates
 
-Lead with the conclusion and a concise evidence chain. Distinguish implementation,
+Answer the user's question directly, keeping conditions that change the conclusion
+beside it. For complex questions, explain the mechanism that determines the result,
+not just the verdict and source links. Explain its practical meaning before using
+a short code excerpt or concrete rule when that helps the reader verify or act.
+Keep decisive evidence beside the claim it supports; separate supplementary facts
+from the proof. State where a local rule applies rather than generalizing it to
+the whole system, and do not infer presentation or behavior from data retrieval
+alone without checking the controlling logic.
+
+Adapt depth and structure to the question: keep simple answers short; use short
+headings and, where supported, separators between major semantic sections in
+longer answers. Do not impose a fixed outline, separate every paragraph, repeat
+the conclusion, or remove necessary explanation just to shorten the answer.
+Keep conditions affecting the answer prominent and supplementary reading secondary.
+Distinguish implementation,
 declared contracts, test assertions, runtime observations and inferences. Perform
 bounded non-destructive validation only when useful; inspect its effects first
 and do not run unrelated scripts, builds or tests.

package/plugins/claude/skills/context-inspect-search/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: context-inspect-search
+description: Query available Context knowledge packages or approved workspace knowledge and trace answers to their identified sources when the user asks a knowledge question or the host configuration routes the request here. A local workspace is optional. Do not auto-start for ordinary coding, planning, debugging, or an active Context production workflow.
+---
+
+# Context Inspect Search
+
+## Entry and boundaries
+
+Use on explicit invocation and related follow-up questions; use the conversation
+language. The invocation authorizes read-only investigation of the selected
+knowledge packages, available workspace and identified sources within that scope,
+including isolated source retrieval and bounded non-destructive checks. The Skill
+can run from a global installation with host-provided packages and no workspace.
+Resolve scope from the request, conversation and configuration before asking.
+Continue through non-blocking issues; ask only for missing access, genuinely
+unresolved scope or effects outside existing authorization.
+
+Start from the supplied package locations or workspace configuration. If a
+workspace exists, read its `AGENTS.md` and relevant configuration;
+`context entry [project-dir] --format json` may help locate instructions.
+Neither a workspace nor a working Context CLI is required for package retrieval;
+do not call entry in an arbitrary directory just to satisfy a prerequisite.
+Do not execute returned production actions, initialize a replacement workspace,
+or install tools without existing authorization. Querying must not alter source
+registrations, snapshots, tasks, approvals or user checkouts.
+
+Resolve `CONTEXT_QUERY_SOURCE_MODE` from the host or Bot instance configuration
+before choosing the first retrieval path. Supported values are:
+
+- `repo-first` (default): inspect the configured knowledge workspace and
+  authorized repository sources first. Use an available package only when the
+  repository path is unavailable or leaves a material gap.
+- `package-first`: inspect the selected package first, then use its recorded
+  workspace or repository sources for missing, stale or disputed evidence.
+- `dual`: inspect the package and repository paths concurrently, then reconcile
+  relevant differences before answering.
+
+An unknown or empty value is `repo-first`; do not invent a fourth mode. The
+mode changes retrieval order, not authorization or evidence standards. It does
+not make a missing secondary source mandatory: continue with readable configured
+sources and identify only gaps that affect the answer.
+
+## Search available material according to the configured mode
+
+Apply `CONTEXT_QUERY_SOURCE_MODE` before starting retrieval. In `repo-first`,
+start with the configured workspace and reusable source checkouts; do not fetch
+or install a package merely to begin the query. In `package-first`, start with
+the selected readable package. In `dual`, start both paths concurrently. Search
+each selected path as soon as it is readable; tool checks and authorized
+upgrades must not block independent reading. If a configured primary path is
+missing, continue with the readable fallback instead of stopping. If a missing
+configured workspace is needed for further attribution, recover it into an
+isolated directory while other selected retrieval continues. Without a
+configured workspace, investigate available packages directly; do not request
+or create one merely to start.
+
+A knowledge package may be workspace build output (usually `dist/`), a global
+installation, or an equivalent host-provided directory. Locate it from available
+configuration or installation metadata rather than assuming a fixed path.
+Select packages relevant to the question. Follow their bundled query Skill when
+present; otherwise search readable indexes and pages. Missing Skills or build
+inventories do not block retrieval or justify rebuilding. If a needed package is
+missing, use the host's configured, authorized package retrieval mechanism while
+other reading continues. Only check or prepare tools needed for the next actual
+operation; installation failure does not block independent local retrieval.
+
+For gaps or latest-content questions, also search approved knowledge when a workspace is available:
+use `knowledge/structure.yaml` and relevant `knowledge/` paths, trying business
+terms, symbols and synonyms, then read matching sections in context. Delivered
+content may lag approved knowledge; they are not independent corroboration.
+Candidates and temporary reports are not approved pages. A search miss does not
+prove a capability is absent. Do not build merely to answer a query; a separately
+authorized build must follow its own workflow without advancing unrelated work.
+
+When package or approved knowledge leaves a gap, directly trace relevant sources
+without asking whether to deepen the query. Use available document, code-search
+or extraction tools within the authorized scope, recording source identity and
+version. Prepare sources while continuing other reading.
+One failed source blocks only dependent claims. Answer when evidence is
+sufficient, without completing unnecessary preparation.
+
+## Trace and retrieve only relevant sources
+
+Without a workspace, use explicit source references in the package, its metadata
+or user configuration to identify relevant documents or repository paths and
+commits. Read or retrieve those sources directly within scope; the workspace
+registry is not a mandatory intermediate step. If the source identity or version
+cannot be established, retain package-grounded findings and qualify attribution;
+do not invent a repository or equate current source with the package's baseline.
+
+When a workspace and `context-build-inventory.json` are available, map a delivered page's
+`dist_path` through `approved_knowledge.files` to its `approved_path`, relative
+to the workspace's `knowledge/` root. Follow the approved page's associations in
+`knowledge/structure.yaml` and `sources/*/index.yaml`. Without a reliable mapping,
+continue package retrieval and follow explicit source references where available.
+Do not guess originals from similar filenames or claim attribution without
+checking the referenced material.
+
+Use the repository and recorded commit identified by the package or workspace
+as the source baseline.
+Reuse existing checkouts only after checking remote, commit, module coverage
+and local changes; do not reset them or change their sparse configuration.
+Missing code goes into a reusable query-owned path such as
+`.tmp/context-inspect/<host>/<repository-path>/<commit>/`, separate from user
+checkouts and production-managed sources. Use safe, credential-free path
+components and the full commit. Verify identity before reuse; never overwrite
+a mismatched directory. Deduplicate recovery and use one writer per checkout;
+that writer may append sparse paths without resetting existing files.
+
+Default to lightweight retrieval and sparse checkout:
+
+- Use shallow history (`--depth=1`) and deferred contents (`--filter=blob:none`)
+  where supported, with a complete partial-clone setup and named promisor remote.
+  Configure the sparse scope before checkout and verify the resulting commit.
+- Start from known module paths. If unclear, inspect
+  `git ls-tree -r --name-only <commit>` for candidates, then read code to confirm
+  their relevance. Expand along imports, calls and service routes as needed;
+  deepen history only when needed. A sparse search miss is not a whole-repository miss.
+- Read ready modules while other recovery proceeds. Allow sufficient command
+  time (for example 300 seconds or more), but investigate confirmed stalls
+  without waiting for timeout; silence alone is not a stall. If unsupported or
+  unsuccessful, try caches, commit-specific file retrieval or bounded shallow
+  retrieval; use a full clone only when necessary. Do not retry blindly or
+  silently substitute the default branch for an unavailable recorded commit.
+
+Query retrieval never runs `context source restore`, `task prepare` or production
+capture/recovery actions. Production recovery gates do not block this independent
+inspection. Preserve unavailable-evidence gaps rather than changing production
+state to get past them.
+
+Compare relevant baseline files with current code when accessible, including
+relevant local changes. Use actual diffs to assess impact; current code is not a
+substitute for the baseline. Mention a missing comparison only when it limits
+the answer. For documents, notes and sessions, read saved bodies and necessary
+attachments; fetch missing accessible material within scope. A summary is not a
+full transcript, an unread link is not evidence, and current remote content does
+not prove a historical snapshot.
+
+## Answer with evidence and hand off updates
+
+Answer the user's question directly, keeping conditions that change the conclusion
+beside it. For complex questions, explain the mechanism that determines the result,
+not just the verdict and source links. Explain its practical meaning before using
+a short code excerpt or concrete rule when that helps the reader verify or act.
+Keep decisive evidence beside the claim it supports; separate supplementary facts
+from the proof. State where a local rule applies rather than generalizing it to
+the whole system, and do not infer presentation or behavior from data retrieval
+alone without checking the controlling logic.
+
+Adapt depth and structure to the question: keep simple answers short; use short
+headings and, where supported, separators between major semantic sections in
+longer answers. Do not impose a fixed outline, separate every paragraph, repeat
+the conclusion, or remove necessary explanation just to shorten the answer.
+Keep conditions affecting the answer prominent and supplementary reading secondary.
+Distinguish implementation,
+declared contracts, test assertions, runtime observations and inferences. Perform
+bounded non-destructive validation only when useful; inspect its effects first
+and do not run unrelated scripts, builds or tests.
+
+Link material actually read: source files at the inspected commit, knowledge
+website articles and original documents. If no reliable clickable link exists,
+give checkable local paths, symbols and short supporting excerpts with the
+limitation. Do not dump internal reasoning, runtime identifiers or routine
+version comparisons. Explain only differences affecting the answer; hashes may
+appear in source URLs without requiring a separate version audit in the prose.
+
+For website links, use `context-site-map.json` from the selected package or
+sibling website output. Match `pages[].package_path` or `approved_path`, and
+resolve `site_path` against `site_url` without prepending `base` again. Cite only
+matched pages, deduplicate links and do not invent anchors. If mapping is absent
+or invalid, retain local citations. Do not build, publish or probe remote sites
+just to format citations; a local map is not proof of the current online content.
+
+Suggest a knowledge update only with supporting evidence: identify the affected
+page or gap, proposed change and bounded source scope. Check neighboring content
+before proposing a new page. Only after user acceptance, hand the evidence and
+scope to the installed `context` production Skill in the selected workspace and
+its fresh Route. If no target workspace is known, resolve it at that handoff,
+not as a prerequisite to answering. Do not edit approved knowledge, clear state
+or reuse an earlier revision. If that entry
+is unavailable, provide the handoff and state that no update has started.

package/plugins/claude/skills/context-inspect-search/agents/openai.yaml

@@ -0,0 +1,2 @@
+policy:
+  allow_implicit_invocation: true

package/plugins/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "c4a",
-  "version": "0.7.25",
+  "version": "0.7.29",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": { "name": "c4a" },
   "homepage": "https://github.com/context4ai/c4a",
@@ -10,7 +10,7 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "C4A Context",
-    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.25",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.29",
     "longDescription": "Create a Context workspace and use agent-guided next steps to register sources, run extraction, review candidates, build package outputs, and verify health without silently mutating source repositories.",
     "developerName": "c4a",
     "category": "Productivity",

package/plugins/codex/skills/context-inspect-search/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: context-inspect-search
-description: Use only when the user explicitly invokes context-inspect-search to query available Context knowledge packages or approved workspace knowledge and trace answers to their identified sources. A local workspace is optional. Do not auto-start for ordinary coding, planning, debugging, or an active Context production workflow.
-disable-model-invocation: true
+description: Query available Context knowledge packages or approved workspace knowledge and trace answers to their identified sources when the user asks a knowledge question or the host configuration routes the request here. A local workspace is optional. Do not auto-start for ordinary coding, planning, debugging, or an active Context production workflow.
 ---
 
 # Context Inspect Search
@@ -26,14 +25,35 @@ Do not execute returned production actions, initialize a replacement workspace,
 or install tools without existing authorization. Querying must not alter source
 registrations, snapshots, tasks, approvals or user checkouts.
 
-## Search available material concurrently
-
-Check relevant knowledge packages, the workspace and reusable source checkouts
-in parallel. Search each as soon as it is readable; tool checks and authorized
-upgrades must not block independent reading. If a missing configured workspace
-is needed for further attribution, recover it into an isolated directory while
-package retrieval continues. Without a configured workspace, investigate the
-available packages directly; do not request or create one merely to start.
+Resolve `CONTEXT_QUERY_SOURCE_MODE` from the host or Bot instance configuration
+before choosing the first retrieval path. Supported values are:
+
+- `repo-first` (default): inspect the configured knowledge workspace and
+  authorized repository sources first. Use an available package only when the
+  repository path is unavailable or leaves a material gap.
+- `package-first`: inspect the selected package first, then use its recorded
+  workspace or repository sources for missing, stale or disputed evidence.
+- `dual`: inspect the package and repository paths concurrently, then reconcile
+  relevant differences before answering.
+
+An unknown or empty value is `repo-first`; do not invent a fourth mode. The
+mode changes retrieval order, not authorization or evidence standards. It does
+not make a missing secondary source mandatory: continue with readable configured
+sources and identify only gaps that affect the answer.
+
+## Search available material according to the configured mode
+
+Apply `CONTEXT_QUERY_SOURCE_MODE` before starting retrieval. In `repo-first`,
+start with the configured workspace and reusable source checkouts; do not fetch
+or install a package merely to begin the query. In `package-first`, start with
+the selected readable package. In `dual`, start both paths concurrently. Search
+each selected path as soon as it is readable; tool checks and authorized
+upgrades must not block independent reading. If a configured primary path is
+missing, continue with the readable fallback instead of stopping. If a missing
+configured workspace is needed for further attribution, recover it into an
+isolated directory while other selected retrieval continues. Without a
+configured workspace, investigate available packages directly; do not request
+or create one merely to start.
 
 A knowledge package may be workspace build output (usually `dist/`), a global
 installation, or an equivalent host-provided directory. Locate it from available
@@ -119,7 +139,21 @@ not prove a historical snapshot.
 
 ## Answer with evidence and hand off updates
 
-Lead with the conclusion and a concise evidence chain. Distinguish implementation,
+Answer the user's question directly, keeping conditions that change the conclusion
+beside it. For complex questions, explain the mechanism that determines the result,
+not just the verdict and source links. Explain its practical meaning before using
+a short code excerpt or concrete rule when that helps the reader verify or act.
+Keep decisive evidence beside the claim it supports; separate supplementary facts
+from the proof. State where a local rule applies rather than generalizing it to
+the whole system, and do not infer presentation or behavior from data retrieval
+alone without checking the controlling logic.
+
+Adapt depth and structure to the question: keep simple answers short; use short
+headings and, where supported, separators between major semantic sections in
+longer answers. Do not impose a fixed outline, separate every paragraph, repeat
+the conclusion, or remove necessary explanation just to shorten the answer.
+Keep conditions affecting the answer prominent and supplementary reading secondary.
+Distinguish implementation,
 declared contracts, test assertions, runtime observations and inferences. Perform
 bounded non-destructive validation only when useful; inspect its effects first
 and do not run unrelated scripts, builds or tests.

package/plugins/codex/skills/context-inspect-search/agents/openai.yaml

@@ -1,2 +1,2 @@
 policy:
-  allow_implicit_invocation: false
+  allow_implicit_invocation: true

package/plugins/cursor/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "c4a",
   "displayName": "C4A Context",
-  "version": "0.7.25",
+  "version": "0.7.29",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": {
     "name": "Context4AI",
@@ -26,6 +26,7 @@
   ],
   "commands": "./commands/",
   "skills": [
-    "./skills/context-indexer-create"
+    "./skills/context-indexer-create",
+    "./skills/context-inspect-search"
   ]
 }