@c4a/context-cli 0.7.10-alpha.2 → 0.7.10

package/indexers/release-manifest.json

@@ -1,7 +1,7 @@
 {
   "protocol": "context.indexer.cli-release-manifest/v1",
   "package": "@c4a/context-cli",
-  "version": "0.7.10-alpha.2",
+  "version": "0.7.10",
   "issuer": "context4ai/context",
   "bundles": [
     {
@@ -11,7 +11,7 @@
         "kind": "cli-bundled",
         "locator": "cli-bundled://context/context-code-indexer"
       },
-      "integrity": "sha256:0774f0507464b2c9d9220b22355bd399c08dd855567eadcd26b59c6fdd2119cf",
+      "integrity": "sha256:c752399ea2ea0252c4805ecdb0f9563c335c345adb303ae73678abd219d5117e",
       "manifest_digest": "sha256:1bb49c2cfaaf1cc847dccd90c5f2bb6465941217a0e0d6053c0a5aeff467a013",
       "files": [
         {
@@ -124,7 +124,7 @@
         },
         {
           "path": "references/indexer.md",
-          "digest": "sha256:cb5828b5f63e765785413793e702cc78606db858d54dc69dd2883b8b770f38b7"
+          "digest": "sha256:fb778aaeb370fc399ba7a8ac9cfd0a2c596b6bceb42eab602c93f16cc0fc134b"
         },
         {
           "path": "references/metrics.md",
@@ -148,7 +148,7 @@
         },
         {
           "path": "templates/adapter-integration.md",
-          "digest": "sha256:be6aa650aad7f70f4bf924c64f4bc73fa28314d512245d61d159ffde6c29a91d"
+          "digest": "sha256:daf8cab4d9d833e2c6ad1fa2284394450b6bbdcc6c09602696b7b5ea05b204af"
         },
         {
           "path": "templates/api-service-maintenance-guide.md",
@@ -160,7 +160,7 @@
         },
         {
           "path": "templates/api-service.md",
-          "digest": "sha256:55b1f42541a001d3a86b815e14b03ac6e5dfab8480e5e133c8425c946e7e96dc"
+          "digest": "sha256:d45aa05476537beffda0b67a459f05a364b4597cc952c57c683191596f68c5b5"
         },
         {
           "path": "templates/articles/c01.md",
@@ -320,7 +320,7 @@
         },
         {
           "path": "templates/background-runtime.md",
-          "digest": "sha256:ab79645c0e32921a69dc1e82cc98da030958579ce3b525c162077d040fd7a40d"
+          "digest": "sha256:4c4aa491c75fcf9ca0188251c17e41ccbc1cdbe50a2608fbb4b9bb9c21728a5b"
         },
         {
           "path": "templates/cli-tool-maintenance-guide.md",
@@ -336,7 +336,7 @@
         },
         {
           "path": "templates/cli-tool.md",
-          "digest": "sha256:4de15964d515a28c8f6e56786f1b287a5132159a29f5f0fae1022aaaa84c0313"
+          "digest": "sha256:7ebcc0b7d77f5c0847fe251259ccc79c0c2a73bb73512439a1cdf3e4fefd7181"
         },
         {
           "path": "templates/component-library-maintenance-guide.md",
@@ -352,7 +352,7 @@
         },
         {
           "path": "templates/component-library.md",
-          "digest": "sha256:bbea3dc04ea8841a5185d3f51779bd5bae3fe8288912abf1f1cb0dfeecf99065"
+          "digest": "sha256:12b202bd0acb407c934b9b15acfcc429d8bdaa539dd242f4409093736291be88"
         },
         {
           "path": "templates/contract-source-public-api-reference.md",
@@ -364,7 +364,7 @@
         },
         {
           "path": "templates/contract-source.md",
-          "digest": "sha256:c4eec319e3b5b7e178f8dfd4d28fe8b497ae0d85fd2bb4e2588a08e50a6e0746"
+          "digest": "sha256:bb13c7b536ef518ed74bbccbb02d795d32c37ecbda6b0f0b8e5ee588f4625ff3"
         },
         {
           "path": "templates/data-sync-reconciliation-maintenance-guide.md",
@@ -376,7 +376,7 @@
         },
         {
           "path": "templates/data-sync-reconciliation.md",
-          "digest": "sha256:87d168f49f1a695e01c231a3853c29bd2f6c878df4e9ef8d201e7c18c72f2cb8"
+          "digest": "sha256:505f3f07c14b3f4dffc2ba301a9b307a707d83e0af055be751935e00114ffc00"
         },
         {
           "path": "templates/derived-generated-source-public-api-reference.md",
@@ -400,7 +400,7 @@
         },
         {
           "path": "templates/domain-service.md",
-          "digest": "sha256:a249498adf6b6a3a88997946964c7ff11448e18a3efaba2f6feccbb7bac314d5"
+          "digest": "sha256:08a3d725369be798801cc6bed50c7145d1075b961efd26a5ec7422e8bb1eb884"
         },
         {
           "path": "templates/event-consumer-maintenance-guide.md",
@@ -440,7 +440,7 @@
         },
         {
           "path": "templates/monorepo-container.md",
-          "digest": "sha256:35052bf151fdcad39c056580c3b02e26f2612c7d9fb0d485add15fc0b1de9950"
+          "digest": "sha256:1c53d2f7037cfa65ec65804810eeaa65d2d97542382add387ce4a0ac06aab201"
         },
         {
           "path": "templates/plugin-extension-maintenance-guide.md",
@@ -472,7 +472,7 @@
         },
         {
           "path": "templates/sdk-library.md",
-          "digest": "sha256:a46a8d057ba422dfb0265b9942a96fda8fa2ffe735952e545bae6480901270d7"
+          "digest": "sha256:d84865c19c2473e0a6431ddd2123a025c50fdc32362ab05ad082149c51107c9b"
         },
         {
           "path": "templates/storage-repository-maintenance-guide.md",
@@ -500,7 +500,7 @@
         },
         {
           "path": "templates/web-application.md",
-          "digest": "sha256:c8d734caec97b1a42f12fcf4cc029a4dc49cc1ba7edfbb5b7fdb9293cf40aa26"
+          "digest": "sha256:2e47c70380bbd254a988bc97578f986c6f602c5e5d2d7d73ffbcb335dd7d9a92"
         },
         {
           "path": "tests/fixtures/chapters.json",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.7.10-alpha.2",
+  "version": "0.7.10",
   "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.10-alpha.2",
-    "@c4a/extract": "0.7.10-alpha.2",
-    "@c4a/extract-contract": "0.7.10-alpha.2",
-    "@c4a/extract-go": "0.7.10-alpha.2",
-    "@c4a/extract-mdx": "0.7.10-alpha.2",
-    "@c4a/extract-proto": "0.7.10-alpha.2",
-    "@c4a/extract-rush": "0.7.10-alpha.2",
-    "@c4a/extract-sql": "0.7.10-alpha.2",
-    "@c4a/extract-style": "0.7.10-alpha.2",
-    "@c4a/extract-thrift": "0.7.10-alpha.2",
-    "@c4a/extract-ts": "0.7.10-alpha.2",
+    "@c4a/context": "0.7.10",
+    "@c4a/extract": "0.7.10",
+    "@c4a/extract-contract": "0.7.10",
+    "@c4a/extract-go": "0.7.10",
+    "@c4a/extract-mdx": "0.7.10",
+    "@c4a/extract-proto": "0.7.10",
+    "@c4a/extract-rush": "0.7.10",
+    "@c4a/extract-sql": "0.7.10",
+    "@c4a/extract-style": "0.7.10",
+    "@c4a/extract-thrift": "0.7.10",
+    "@c4a/extract-ts": "0.7.10",
     "commander": "^11.0.0",
     "fast-xml-parser": "^5.10.1",
     "handlebars": "^4.7.8",

package/parserEntryWorker.js

@@ -474,8 +474,16 @@ var init_debugTrace = __esm(() => {
 
 // src/project/commandReadCache.ts
 import { AsyncLocalStorage as AsyncLocalStorage2 } from "node:async_hooks";
-import { stat } from "node:fs/promises";
+import { readdir, stat } from "node:fs/promises";
 import { resolve as resolve2 } from "node:path";
+async function readCommandDirectory(path) {
+  const entries = await reuseCommandFileRead({
+    key: "directory-entries",
+    paths: [path],
+    read: () => readdir(path, { withFileTypes: true })
+  });
+  return [...entries];
+}
 function withCommandReadCache(action) {
   return commandReads.getStore() === undefined ? commandReads.run(new Map, action) : action();
 }
@@ -19987,7 +19995,7 @@ var init_sessionMetadata = __esm(() => {
 });
 
 // ../context/src/managedSources.ts
-import { readdir, lstat, realpath, readFile as readFile2 } from "node:fs/promises";
+import { readdir as readdir2, lstat, realpath, readFile as readFile2 } from "node:fs/promises";
 import { join as join2, relative as relative2, isAbsolute as isAbsolute3 } from "node:path";
 function assertManagedDocumentName(name) {
   if (!/^\d{8}\/[^/\\\x00-\x1f\s:#?]+\.md$/u.test(name) || name.includes("/..")) {
@@ -20024,7 +20032,7 @@ async function discoverManagedDocuments(rootDir, type) {
   await assertManagedDocumentPath(rootDir, type, "20000101/discovery.md");
   let dates;
   try {
-    dates = await readdir(base, { withFileTypes: true });
+    dates = await readdir2(base, { withFileTypes: true });
   } catch (error) {
     if (error && typeof error === "object" && "code" in error && error.code === "ENOENT")
       return [];
@@ -20034,7 +20042,7 @@ async function discoverManagedDocuments(rootDir, type) {
   for (const date of dates.sort((a, b) => a.name.localeCompare(b.name))) {
     if (!date.isDirectory() || !/^\d{8}$/u.test(date.name))
       continue;
-    for (const file of (await readdir(join2(base, date.name), { withFileTypes: true })).sort((a, b) => a.name.localeCompare(b.name))) {
+    for (const file of (await readdir2(join2(base, date.name), { withFileTypes: true })).sort((a, b) => a.name.localeCompare(b.name))) {
       if (!file.isFile() || !file.name.endsWith(".md"))
         continue;
       const name = `${date.name}/${file.name}`;
@@ -20559,6 +20567,7 @@ function normalizedVirtualPath(path) {
 }
 function sourceFileSystem(root, tracked, texts, readSource) {
   const files = new Set(tracked.map(normalizedVirtualPath));
+  const contents = new Map(Object.entries(texts).map(([path, text2]) => [normalizedVirtualPath(path), text2]));
   const directories = new Map([[".", new Set]]);
   for (const file of files) {
     const parts = file.split("/");
@@ -20585,7 +20594,7 @@ function sourceFileSystem(root, tracked, texts, readSource) {
   return {
     readFile: async (path) => {
       const normalized = assertTrackedFile(path);
-      return Object.hasOwn(texts, normalized) ? texts[normalized] : readSource ? readSource(normalized) : readFile5(safeCodeSourcePath(root, normalized), "utf8");
+      return contents.has(normalized) ? contents.get(normalized) : readSource ? readSource(normalized) : readFile5(safeCodeSourcePath(root, normalized), "utf8");
     },
     async readdir(path) {
       const normalized = normalizedVirtualPath(path);
@@ -20616,7 +20625,7 @@ async function prepareCodeAnalysisInput(input) {
       path: manifestPath,
       content: await fs.readJson(manifestPath)
     }, fs) : { entries: [] };
-    return plugin.extractSymbolsInScope(detected.entries, input.scopedPaths, fs);
+    return plugin.extractSymbolsInScope(detected.entries, input.scopedPaths.map(normalizedVirtualPath), fs);
   }
   if (input.capability === "parser.go") {
     const Plugin = input.loadedModule.GoPlugin;
@@ -20632,8 +20641,8 @@ async function prepareCodeAnalysisInput(input) {
       content: { raw: manifestContent }
     };
     const detected = await plugin.detectEntries(manifest, fs);
-    const allowed = new Set(input.scopedPaths);
-    return plugin.extractSymbols(detected.entries.filter((entry) => allowed.has(entry.path)), fs);
+    const allowed = new Set(input.scopedPaths.map(normalizedVirtualPath));
+    return plugin.extractSymbols(detected.entries.filter((entry) => allowed.has(normalizedVirtualPath(entry.path))), fs);
   }
   if (input.capability === "parser.rush") {
     const indexRushWorkspace = input.loadedModule.indexRushWorkspace;

package/plugins/VERSION

@@ -1 +1 @@
-0.7.10-alpha.2
+0.7.10

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.10-alpha.2",
+  "version": "0.7.10",
   "author": {
     "name": "c4a"
   },

package/plugins/claude/commands/context.md

@@ -93,7 +93,7 @@ present an unresolved draft as the report that authorizes production. The report
 or checklist is task guidance, not a source unless the user explicitly asks to
 ingest it. Before the complete report has been presented, do not write a
 source-registration payload, start capture or extraction, configure Indexers,
-or enter Partition/Author work. A
+or begin knowledge writing. A
 managed-mode choice does not waive this first reading opportunity. After feedback,
 use the exact current Route and include its work-start report reference in the
 source batch payload. Existing workspace updates follow their current update Route
@@ -119,9 +119,16 @@ Once the activation condition is met, run:
 context entry [project-dir] --language <language> --format json
 ```
 
-Use the requested language, otherwise `zh-CN` for Chinese or `en` for English.
-Pass `project-dir`, `--name`, `--dev` and `--debug` only when requested. Add
-`--managed` only with explicit fully managed authorization in this conversation.
+Use the requested output language, otherwise `zh-CN` for Chinese or `en` for
+English; explain actions in the conversation language from the first reply.
+Preserve the user's requested project directory, name and initialization flags
+in the first entry command. Normalize conversational `-dev` to `--dev` (not a
+CLI alias). `--dev` selects the local SDK instead of a registry version;
+`--debug` enables diagnostics independently. Neither implies the other.
+Pass these flags only when requested; add `--managed` only with explicit fully
+managed authorization. For a Chinese request for local SDK, debug and managed
+initialization, use `context entry context/ --dev --debug --language zh-CN
+--managed --format json` as one command, then preserve its returned init flags.
 
 Follow the returned `next_action.command`:
 
@@ -280,9 +287,8 @@ none was returned. A phase-local `next_action` is not a workspace Route.
 If `next_preparation` fails after committed outcomes, execute its recovery
 without resubmitting accepted work. Stage completion is not workspace completion:
 Changed delivery content must finish Review, close and build through their Routes.
-An empty Composer result is a decision not to add derived content, not an API
-regeneration or proof that existing pages meet a later revision request. Do not
-infer maintenance targets from Composer task names or count.
+An empty result does not prove that existing pages meet a later revision request.
+Register the actual maintenance targets rather than inferring them from task names.
 
 When the Graph reports complete, compare the user's original and subsequent
 requests with actual delivered results and registered maintenance targets.
@@ -292,7 +298,7 @@ conversational requests. Continue already authorized outstanding work through th
 normal Context revision/update entry and its fresh Route, respecting existing
 Gates. Do not ask for another "continue" solely because production finished.
 Report a blocker only when a required input, permission or actual entry failure
-prevents progress; do not invent a missing Review/build after an empty Composer.
+prevents progress; do not invent missing work solely because a result is empty.
 
 For an authorized end-to-end task, continue while the current Route is actionable
 within that authority. Report batch progress during execution, without ending
@@ -310,74 +316,32 @@ and when the user declined it. Use the commit guide if the user chooses it.
 ## When selecting or customizing Indexers
 
 Read `context.indexer.provider-guide` at the path supplied by the Route and the
-selected Action's instructions. They own the selection schema, layer rules,
-customization ladder, program authorization and upgrade recovery.
-
-Use the supplied requirements and CLI-bundled catalog. Discover relevant
-external Providers only among Host-visible `context-…-indexer…` Skills and read
-their exposed manifest. Host switches and installation channels determine
-availability; the catalog does not override a disabled Skill or a chosen
-business replacement. Do not scan caches, run a discovery preflight, or create
-a second enabled-Skill registry.
-
-Copy bundled Provider identities from the catalog, even if the same version
-is Host-visible. Read only selected Provider guidance. Keep one primary for an
-existing page; supporting note/session material belongs in its evidence/read
-scope, with compatible extension guidance when needed. Source type alone does
-not require a new page. Submit the selection through the Route's
-`complete-current` contract; the CLI validates, resolves and applies it. Follow
-returned Host-resolution and program Gates without calling low-level commands
-as a parallel workflow. Provider finalization consumes its existing input and
-must not resolve or install the Provider again.
+selected Action's instructions. Select relevant available Skills for the actual
+materials and reader task, respecting disabled Skills and explicit business
+replacements. Record usage through the current planning schema; do not reconstruct
+a separate Provider selection, primary-owner or finalization workflow. Read only
+selected guidance; do not scan plugin caches or create another Skill registry.
+Supporting notes or sessions can enrich an existing article; a different source
+type alone does not require another page.
 
 ## Progress reporting format
 
-For production progress updates, use two bold lines in this order. Describe
-the actual stage when counters are unavailable; include counts only when supplied:
-
-**[总体进展：已交付 33/125 页]**
-**[当前进展：已规划 3/8 项]**
-
-Use CLI `progress.scopes` (or `indexerProgress.scopes` in status) as the
-single source for progress in conversation and reports. It separates:
-- `overall`: delivered pages and cumulative planning for the current Indexer run;
-- `wave`: writing tasks, observed pages and composition for the current wave;
-- `slice`: tasks in the currently active Route slice.
-
-Planning completed counts currently valid accepted tasks, not lifetime effort.
-When overall.planning.needs_recheck is nonzero, report “规划当前有效 X/Y 项；Z 项因任务绑定变化待复核”.
-Do not describe a lower valid count as lost pages or silently restarting from zero.
-The CLI reason identifies binding changes, not proof that source code changed;
-do not invent a more specific cause.
-
-Keep these scopes separate. A wave or pause target never replaces the overall
-scope. Preserve overall planning across Author, Composer and Review transitions.
-Use each counter's `unit`: task means 项/任务, page means 页. A writing task is
-not automatically one page. A null total means 总数待确定, not zero or the
-number of currently prepared tasks. Revisions can overlap delivered pages;
-do not add wave tasks to delivered pages to invent a page total.
-
-Use two bold progress lines. The first combines `overall` and a clearly labelled
-`wave` supplement; the second describes the current action, using `slice` counts
-when available. Internal wave/slice names need not appear in user-facing text. For example, with matching CLI values:
-**[总体进展：已交付 33 页，总页数待确定；规划完成 50/122 项；本轮写作完成 30/30 项]**
-**[当前进展：补充内容检查 0/8 项]**
-
-A completion receipt's `submitted_slice` describes the slice just submitted;
-`progress.scopes.slice` can already describe the next Route. Use the former when
-reporting submission success and the latter when announcing the next slice.
-Never combine their numerators and denominators. A null slice means no active
-Agent task slice, not that the workflow is complete. During Review/build, state
-the returned Route action briefly rather than inventing a slice ratio.
-Before counters exist or after task cleanup, describe the known stage and current
-action instead of repeatedly saying counters are unavailable. For example:
-**[总体进展：正在准备知识工作区]**
-**[当前进展：已读取启动清单，正在整理仓库与文档范围]**
-During review or packaging, name that action rather than a nonexistent slice.
-Do not turn the last wave into the overall scope or report delivery as zero.
-Continue authorized work after an update; only the agreed delivery stop or an
-actual unresolved blocker permits stopping. This format governs progress, not
-answers, review findings or necessary questions.
+For production updates, use two bold lines: overall progress, then the current
+action. Use the conversation language. For example, when supported by the receipt:
+
+**[总体进展：已交付 10 页；本轮写作已接收 3/5 项]**
+**[当前进展：正在审核本轮文章]**
+
+Use counts and their meanings from the current CLI result. Distinguish accepted
+drafts from delivered pages, and the just-submitted subset from remaining work.
+Do not require older overall/wave/slice fields or reconstruct missing totals.
+Tasks and pages are not interchangeable; revisions do not automatically add pages.
+Before counts exist or after cleanup, describe the actual stage without invented
+ratios or reporting previously delivered pages as zero.
+
+Continue authorized work after a progress update. End only at the agreed scope,
+a user pause or an actual unresolved blocker. This format applies to production
+progress, not answers, review findings or necessary questions.
 
 ## Report the actual outcome
 

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

@@ -1,6 +1,6 @@
 {
   "name": "c4a",
-  "version": "0.7.10-alpha.2",
+  "version": "0.7.10",
   "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.10-alpha.2",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.10",
     "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/SKILL.md

@@ -91,7 +91,7 @@ present an unresolved draft as the report that authorizes production. The report
 or checklist is task guidance, not a source unless the user explicitly asks to
 ingest it. Before the complete report has been presented, do not write a
 source-registration payload, start capture or extraction, configure Indexers,
-or enter Partition/Author work. A
+or begin knowledge writing. A
 managed-mode choice does not waive this first reading opportunity. After feedback,
 use the exact current Route and include its work-start report reference in the
 source batch payload. Existing workspace updates follow their current update Route
@@ -117,9 +117,16 @@ Once the activation condition is met, run:
 context entry [project-dir] --language <language> --format json
 ```
 
-Use the requested language, otherwise `zh-CN` for Chinese or `en` for English.
-Pass `project-dir`, `--name`, `--dev` and `--debug` only when requested. Add
-`--managed` only with explicit fully managed authorization in this conversation.
+Use the requested output language, otherwise `zh-CN` for Chinese or `en` for
+English; explain actions in the conversation language from the first reply.
+Preserve the user's requested project directory, name and initialization flags
+in the first entry command. Normalize conversational `-dev` to `--dev` (not a
+CLI alias). `--dev` selects the local SDK instead of a registry version;
+`--debug` enables diagnostics independently. Neither implies the other.
+Pass these flags only when requested; add `--managed` only with explicit fully
+managed authorization. For a Chinese request for local SDK, debug and managed
+initialization, use `context entry context/ --dev --debug --language zh-CN
+--managed --format json` as one command, then preserve its returned init flags.
 
 Follow the returned `next_action.command`:
 
@@ -278,9 +285,8 @@ none was returned. A phase-local `next_action` is not a workspace Route.
 If `next_preparation` fails after committed outcomes, execute its recovery
 without resubmitting accepted work. Stage completion is not workspace completion:
 Changed delivery content must finish Review, close and build through their Routes.
-An empty Composer result is a decision not to add derived content, not an API
-regeneration or proof that existing pages meet a later revision request. Do not
-infer maintenance targets from Composer task names or count.
+An empty result does not prove that existing pages meet a later revision request.
+Register the actual maintenance targets rather than inferring them from task names.
 
 When the Graph reports complete, compare the user's original and subsequent
 requests with actual delivered results and registered maintenance targets.
@@ -290,7 +296,7 @@ conversational requests. Continue already authorized outstanding work through th
 normal Context revision/update entry and its fresh Route, respecting existing
 Gates. Do not ask for another "continue" solely because production finished.
 Report a blocker only when a required input, permission or actual entry failure
-prevents progress; do not invent a missing Review/build after an empty Composer.
+prevents progress; do not invent missing work solely because a result is empty.
 
 For an authorized end-to-end task, continue while the current Route is actionable
 within that authority. Report batch progress during execution, without ending
@@ -308,74 +314,32 @@ and when the user declined it. Use the commit guide if the user chooses it.
 ## When selecting or customizing Indexers
 
 Read `context.indexer.provider-guide` at the path supplied by the Route and the
-selected Action's instructions. They own the selection schema, layer rules,
-customization ladder, program authorization and upgrade recovery.
-
-Use the supplied requirements and CLI-bundled catalog. Discover relevant
-external Providers only among Host-visible `context-…-indexer…` Skills and read
-their exposed manifest. Host switches and installation channels determine
-availability; the catalog does not override a disabled Skill or a chosen
-business replacement. Do not scan caches, run a discovery preflight, or create
-a second enabled-Skill registry.
-
-Copy bundled Provider identities from the catalog, even if the same version
-is Host-visible. Read only selected Provider guidance. Keep one primary for an
-existing page; supporting note/session material belongs in its evidence/read
-scope, with compatible extension guidance when needed. Source type alone does
-not require a new page. Submit the selection through the Route's
-`complete-current` contract; the CLI validates, resolves and applies it. Follow
-returned Host-resolution and program Gates without calling low-level commands
-as a parallel workflow. Provider finalization consumes its existing input and
-must not resolve or install the Provider again.
+selected Action's instructions. Select relevant available Skills for the actual
+materials and reader task, respecting disabled Skills and explicit business
+replacements. Record usage through the current planning schema; do not reconstruct
+a separate Provider selection, primary-owner or finalization workflow. Read only
+selected guidance; do not scan plugin caches or create another Skill registry.
+Supporting notes or sessions can enrich an existing article; a different source
+type alone does not require another page.
 
 ## Progress reporting format
 
-For production progress updates, use two bold lines in this order. Describe
-the actual stage when counters are unavailable; include counts only when supplied:
-
-**[总体进展：已交付 33/125 页]**
-**[当前进展：已规划 3/8 项]**
-
-Use CLI `progress.scopes` (or `indexerProgress.scopes` in status) as the
-single source for progress in conversation and reports. It separates:
-- `overall`: delivered pages and cumulative planning for the current Indexer run;
-- `wave`: writing tasks, observed pages and composition for the current wave;
-- `slice`: tasks in the currently active Route slice.
-
-Planning completed counts currently valid accepted tasks, not lifetime effort.
-When overall.planning.needs_recheck is nonzero, report “规划当前有效 X/Y 项；Z 项因任务绑定变化待复核”.
-Do not describe a lower valid count as lost pages or silently restarting from zero.
-The CLI reason identifies binding changes, not proof that source code changed;
-do not invent a more specific cause.
-
-Keep these scopes separate. A wave or pause target never replaces the overall
-scope. Preserve overall planning across Author, Composer and Review transitions.
-Use each counter's `unit`: task means 项/任务, page means 页. A writing task is
-not automatically one page. A null total means 总数待确定, not zero or the
-number of currently prepared tasks. Revisions can overlap delivered pages;
-do not add wave tasks to delivered pages to invent a page total.
-
-Use two bold progress lines. The first combines `overall` and a clearly labelled
-`wave` supplement; the second describes the current action, using `slice` counts
-when available. Internal wave/slice names need not appear in user-facing text. For example, with matching CLI values:
-**[总体进展：已交付 33 页，总页数待确定；规划完成 50/122 项；本轮写作完成 30/30 项]**
-**[当前进展：补充内容检查 0/8 项]**
-
-A completion receipt's `submitted_slice` describes the slice just submitted;
-`progress.scopes.slice` can already describe the next Route. Use the former when
-reporting submission success and the latter when announcing the next slice.
-Never combine their numerators and denominators. A null slice means no active
-Agent task slice, not that the workflow is complete. During Review/build, state
-the returned Route action briefly rather than inventing a slice ratio.
-Before counters exist or after task cleanup, describe the known stage and current
-action instead of repeatedly saying counters are unavailable. For example:
-**[总体进展：正在准备知识工作区]**
-**[当前进展：已读取启动清单，正在整理仓库与文档范围]**
-During review or packaging, name that action rather than a nonexistent slice.
-Do not turn the last wave into the overall scope or report delivery as zero.
-Continue authorized work after an update; only the agreed delivery stop or an
-actual unresolved blocker permits stopping. This format governs progress, not
-answers, review findings or necessary questions.
+For production updates, use two bold lines: overall progress, then the current
+action. Use the conversation language. For example, when supported by the receipt:
+
+**[总体进展：已交付 10 页；本轮写作已接收 3/5 项]**
+**[当前进展：正在审核本轮文章]**
+
+Use counts and their meanings from the current CLI result. Distinguish accepted
+drafts from delivered pages, and the just-submitted subset from remaining work.
+Do not require older overall/wave/slice fields or reconstruct missing totals.
+Tasks and pages are not interchangeable; revisions do not automatically add pages.
+Before counts exist or after cleanup, describe the actual stage without invented
+ratios or reporting previously delivered pages as zero.
+
+Continue authorized work after a progress update. End only at the agreed scope,
+a user pause or an actual unresolved blocker. This format applies to production
+progress, not answers, review findings or necessary questions.
 
 ## Report the actual outcome
 

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

@@ -1,7 +1,7 @@
 {
   "name": "c4a",
   "displayName": "C4A Context",
-  "version": "0.7.10-alpha.2",
+  "version": "0.7.10",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": {
     "name": "Context4AI",