@c4a/context-cli 0.7.14-beta.1 → 0.7.14

package/indexers/release-manifest.json

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

package/package.json

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

package/plugins/VERSION

@@ -1 +1 @@
-0.7.14-beta.1
+0.7.14

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.14-beta.1",
+  "version": "0.7.14",
   "author": {
     "name": "c4a"
   },

package/plugins/claude/commands/context.md

@@ -49,6 +49,17 @@ Within an active Context workflow, requests include, but are not limited to:
 | Commit workspace results | Save selected workspace files in local Git, without pushing or including unrelated changes. |
 | Restore a historical workspace version | Select a saved commit, restore only the agreed workspace scope and make its sources usable again. |
 
+## Preserve existing reading organization
+
+For additions as well as navigation edits, first read the workspace AGENTS.md,
+current map and relevant overview/category articles. Reuse their category intent;
+a new source or product does not by itself justify a top-level menu. Follow the
+knowledge-updates guidance returned by `context entry` or the current Route,
+especially "Preserve established navigation intent". Include proposed top-level
+changes in the work-start report or current plan for explicit human review before
+applying them; reuse a concrete structure the user has already approved. Ordinary
+placements within the approved organization do not require another review gate.
+
 ## Read the task before registering sources
 
 For a knowledge-map-only request, use the existing workspace directly. Read

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

@@ -1,6 +1,6 @@
 {
   "name": "c4a",
-  "version": "0.7.14-beta.1",
+  "version": "0.7.14",
   "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.14-beta.1",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.14",
     "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

@@ -47,6 +47,17 @@ Within an active Context workflow, requests include, but are not limited to:
 | Commit workspace results | Save selected workspace files in local Git, without pushing or including unrelated changes. |
 | Restore a historical workspace version | Select a saved commit, restore only the agreed workspace scope and make its sources usable again. |
 
+## Preserve existing reading organization
+
+For additions as well as navigation edits, first read the workspace AGENTS.md,
+current map and relevant overview/category articles. Reuse their category intent;
+a new source or product does not by itself justify a top-level menu. Follow the
+knowledge-updates guidance returned by `context entry` or the current Route,
+especially "Preserve established navigation intent". Include proposed top-level
+changes in the work-start report or current plan for explicit human review before
+applying them; reuse a concrete structure the user has already approved. Ordinary
+placements within the approved organization do not require another review gate.
+
 ## Read the task before registering sources
 
 For a knowledge-map-only request, use the existing workspace directly. Read

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

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

package/plugins/cursor/commands/c4a-context.md

@@ -44,6 +44,17 @@ Within an active Context workflow, requests include, but are not limited to:
 | Commit workspace results | Save selected workspace files in local Git, without pushing or including unrelated changes. |
 | Restore a historical workspace version | Select a saved commit, restore only the agreed workspace scope and make its sources usable again. |
 
+## Preserve existing reading organization
+
+For additions as well as navigation edits, first read the workspace AGENTS.md,
+current map and relevant overview/category articles. Reuse their category intent;
+a new source or product does not by itself justify a top-level menu. Follow the
+knowledge-updates guidance returned by `context entry` or the current Route,
+especially "Preserve established navigation intent". Include proposed top-level
+changes in the work-start report or current plan for explicit human review before
+applying them; reuse a concrete structure the user has already approved. Ordinary
+placements within the approved organization do not require another review gate.
+
 ## Read the task before registering sources
 
 For a knowledge-map-only request, use the existing workspace directly. Read

package/plugins/skills/context/SKILL.md

@@ -47,6 +47,17 @@ Within an active Context workflow, requests include, but are not limited to:
 | Commit workspace results | Save selected workspace files in local Git, without pushing or including unrelated changes. |
 | Restore a historical workspace version | Select a saved commit, restore only the agreed workspace scope and make its sources usable again. |
 
+## Preserve existing reading organization
+
+For additions as well as navigation edits, first read the workspace AGENTS.md,
+current map and relevant overview/category articles. Reuse their category intent;
+a new source or product does not by itself justify a top-level menu. Follow the
+knowledge-updates guidance returned by `context entry` or the current Route,
+especially "Preserve established navigation intent". Include proposed top-level
+changes in the work-start report or current plan for explicit human review before
+applying them; reuse a concrete structure the user has already approved. Ordinary
+placements within the approved organization do not require another review gate.
+
 ## Read the task before registering sources
 
 For a knowledge-map-only request, use the existing workspace directly. Read

package/providers/context/manifest.json

@@ -2,7 +2,7 @@
   "schema": "agent-graph.bundle.v1",
   "provider": {
     "id": "c4a/context",
-    "version": "0.7.14-beta.1"
+    "version": "0.7.14"
   },
   "providerManifest": "provider.yaml",
   "graphs": [
@@ -308,7 +308,7 @@
     {
       "id": "procedure.knowledge-updates",
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:f43943fdf9265e5181c2e8cf3753d981fc9f59a44ee11b5beac404ec481344ea"
+      "digest": "sha256:6132bad75635e1ef388c5bf7dd6cd0d3d1fc521a16b44c3bc4d934a7467e516e"
     },
     {
       "id": "procedure.note",
@@ -383,7 +383,7 @@
     {
       "id": "procedure.work-start-report",
       "path": "resources/procedures/work-start-report.md",
-      "digest": "sha256:d41a91d89eb917bcc15a601ef85d4ac5187bec18365098442e45647eb19b1e90"
+      "digest": "sha256:7e27909f3e0209ff88c98a87db8cab3bbf84a915ae2abb5c2453b7525315e45e"
     },
     {
       "id": "procedure.workspace-commit",
@@ -413,7 +413,7 @@
     {
       "id": "template.work-start-report",
       "path": "resources/templates/work-start-report.md",
-      "digest": "sha256:fb7c5bba6d1c6b9f71e28539c5edda63c162e6a3ccc6623d81e6d649638c8802"
+      "digest": "sha256:f9acb9a959dee3d93e1877cd9737dfff7702733ae2121b454a9cc90adbaf89b2"
     }
   ],
   "schemas": [
@@ -570,7 +570,7 @@
     },
     {
       "path": "provider.yaml",
-      "digest": "sha256:820cc81bd72613211c7f1a48406bc881f6f4baf09ef415e635aa8da01aa08f0a"
+      "digest": "sha256:d7932685876d1ce6ae7d06442f8d59249de936893d22cf46fcca25a8949ba18f"
     },
     {
       "path": "resources/contracts/indexer-provider-guide.yaml",
@@ -626,7 +626,7 @@
     },
     {
       "path": "resources/manuals/guides/knowledge-updates.md",
-      "digest": "sha256:fe8c9e4dbe7413bce3c2007bf230f1312fca31de69d434d0c41171a27e1a68f5"
+      "digest": "sha256:263410c1a4c34ae843297552b6575fa23a780c4095c694e03cc64e9cb292325c"
     },
     {
       "path": "resources/manuals/guides/lark-resources.md",
@@ -706,7 +706,7 @@
     },
     {
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:f43943fdf9265e5181c2e8cf3753d981fc9f59a44ee11b5beac404ec481344ea"
+      "digest": "sha256:6132bad75635e1ef388c5bf7dd6cd0d3d1fc521a16b44c3bc4d934a7467e516e"
     },
     {
       "path": "resources/procedures/note.md",
@@ -766,7 +766,7 @@
     },
     {
       "path": "resources/procedures/work-start-report.md",
-      "digest": "sha256:d41a91d89eb917bcc15a601ef85d4ac5187bec18365098442e45647eb19b1e90"
+      "digest": "sha256:7e27909f3e0209ff88c98a87db8cab3bbf84a915ae2abb5c2453b7525315e45e"
     },
     {
       "path": "resources/procedures/workspace-commit.md",
@@ -790,7 +790,7 @@
     },
     {
       "path": "resources/templates/work-start-report.md",
-      "digest": "sha256:fb7c5bba6d1c6b9f71e28539c5edda63c162e6a3ccc6623d81e6d649638c8802"
+      "digest": "sha256:f9acb9a959dee3d93e1877cd9737dfff7702733ae2121b454a9cc90adbaf89b2"
     },
     {
       "path": "resources/views/package-current.yaml",
@@ -862,12 +862,12 @@
     },
     {
       "path": "skills/work-production-stage/SKILL.md",
-      "digest": "sha256:5bb250f42d5d28243daca30427b5fd9db52127460862748fc36935f0e0d0f754"
+      "digest": "sha256:cacf6ce1b106cfe7af7b07009e6a3658c04007c6eb49127069fa16e3b2892f31"
     }
   ],
   "graphDependencies": {
     "indexer": [],
     "workspace": []
   },
-  "digest": "sha256:0ce9bbc43630874ad90cf5663348b2c6f96dcdf7dd911f5e6b33c71154a3ea9e"
+  "digest": "sha256:4b30698cc222807e84c58c14e0d5a367786e65d3173aca206ee68ab3b44bd052"
 }

package/providers/context/provider.yaml

@@ -1,6 +1,6 @@
 schema: agent-graph.provider.v1
 id: c4a/context
-version: 0.7.14-beta.1
+version: 0.7.14
 name: Context workflow
 description: Internal work contract for Context knowledge workspaces.
 graphs:

package/providers/context/resources/manuals/guides/knowledge-updates.md

@@ -200,6 +200,48 @@ coverage by mechanically placing every new page under an unrelated catch-all.
 Build reports missing bindings for the Agent to resolve; it does not classify
 content. Moving a menu entry does not change the article URL.
 
+### Preserve established navigation intent
+
+Before placing new knowledge, read the workspace's AGENTS.md, current
+`src/knowledge-map.yaml`, existing overview pages and relevant category/article
+bodies. Reuse any settled directory intent in the current plan. Establish what
+each affected category helps readers do and why adjacent categories are separate;
+do not infer this from labels alone. Read only affected branches and enough
+neighboring content to distinguish them, not the entire library on every update.
+If intent remains ambiguous, state the proposed interpretation in the plan.
+
+Prefer, in order: revise an existing article; add a page to a matching category;
+add a coherent child category; propose a top-level change only when existing
+categories cannot serve a distinct, lasting reader need. Do not create a top-level
+category merely because a source, repository, product, team or batch is new.
+For example, a new assistant's usage guide, frontend integration and runtime
+architecture can belong in existing usage, frontend and backend categories, with
+cross-links for the shared product. Keep them together only when the site's
+established organizing principle supports that choice.
+
+In the work-start report or current plan, briefly state the affected articles'
+intended placements and reused category intent. For proposed top-level additions,
+renames, removals or changes of purpose, show the before/after tree, why reuse is
+insufficient, affected existing pages and reading order. Present that change for
+human review before applying it. This uses the existing report feedback where
+available; do not add a new CLI state, schema field or routine per-article gate.
+Explicit user approval of that concrete structure is sufficient; do not ask again.
+General permission to write knowledge or organize batches is not approval to
+change the site's top-level organization. If the need emerges after report
+approval, update the same plan and ask about that structural change only; continue
+independent work within the approved organization.
+
+Before delivery, compare the resulting map with the approved plan: article
+placement matches its main reader task, titles match the bodies, sibling ordering
+is deliberate, and directories are neither empty nor accidental duplicates.
+Honor the workspace's chosen directory depth and homogeneous sibling convention;
+where it requires directory-only or article-only siblings, do not mix them.
+Use an "Other" group last only for genuinely useful residual content, not to
+avoid classification. Apply supported map adjustments through the current CLI
+flow, retaining article identities and URLs. Record lasting category intent
+briefly in the workspace AGENTS.md or existing organization guide; do not create
+a separate taxonomy ledger or put planning instructions in reader articles.
+
 ### Reader tasks, names and reading order
 
 Read the affected articles' bodies before changing their categories or titles.
@@ -257,8 +299,8 @@ change does not require a prose rewrite or file migration; changing its label do
 not silently rename the approved article. Needed title or content revisions use
 the existing revision and Review flow. Splits and merges use ordinary article
 tasks, link repair and any explicit retirement after replacement content is
-delivered. These are Agent editorial decisions, not new CLI checks or approval
-gates.
+delivered. These are Agent editorial decisions, not new CLI checks or routine per-article
+approval gates. Top-level changes follow the focused review described above.
 
 ## Edit one section or review part of a batch
 

package/providers/context/resources/procedures/knowledge-updates.md

@@ -200,6 +200,48 @@ coverage by mechanically placing every new page under an unrelated catch-all.
 Build reports missing bindings for the Agent to resolve; it does not classify
 content. Moving a menu entry does not change the article URL.
 
+### Preserve established navigation intent
+
+Before placing new knowledge, read the workspace's AGENTS.md, current
+`src/knowledge-map.yaml`, existing overview pages and relevant category/article
+bodies. Reuse any settled directory intent in the current plan. Establish what
+each affected category helps readers do and why adjacent categories are separate;
+do not infer this from labels alone. Read only affected branches and enough
+neighboring content to distinguish them, not the entire library on every update.
+If intent remains ambiguous, state the proposed interpretation in the plan.
+
+Prefer, in order: revise an existing article; add a page to a matching category;
+add a coherent child category; propose a top-level change only when existing
+categories cannot serve a distinct, lasting reader need. Do not create a top-level
+category merely because a source, repository, product, team or batch is new.
+For example, a new assistant's usage guide, frontend integration and runtime
+architecture can belong in existing usage, frontend and backend categories, with
+cross-links for the shared product. Keep them together only when the site's
+established organizing principle supports that choice.
+
+In the work-start report or current plan, briefly state the affected articles'
+intended placements and reused category intent. For proposed top-level additions,
+renames, removals or changes of purpose, show the before/after tree, why reuse is
+insufficient, affected existing pages and reading order. Present that change for
+human review before applying it. This uses the existing report feedback where
+available; do not add a new CLI state, schema field or routine per-article gate.
+Explicit user approval of that concrete structure is sufficient; do not ask again.
+General permission to write knowledge or organize batches is not approval to
+change the site's top-level organization. If the need emerges after report
+approval, update the same plan and ask about that structural change only; continue
+independent work within the approved organization.
+
+Before delivery, compare the resulting map with the approved plan: article
+placement matches its main reader task, titles match the bodies, sibling ordering
+is deliberate, and directories are neither empty nor accidental duplicates.
+Honor the workspace's chosen directory depth and homogeneous sibling convention;
+where it requires directory-only or article-only siblings, do not mix them.
+Use an "Other" group last only for genuinely useful residual content, not to
+avoid classification. Apply supported map adjustments through the current CLI
+flow, retaining article identities and URLs. Record lasting category intent
+briefly in the workspace AGENTS.md or existing organization guide; do not create
+a separate taxonomy ledger or put planning instructions in reader articles.
+
 ### Reader tasks, names and reading order
 
 Read the affected articles' bodies before changing their categories or titles.
@@ -257,8 +299,8 @@ change does not require a prose rewrite or file migration; changing its label do
 not silently rename the approved article. Needed title or content revisions use
 the existing revision and Review flow. Splits and merges use ordinary article
 tasks, link repair and any explicit retirement after replacement content is
-delivered. These are Agent editorial decisions, not new CLI checks or approval
-gates.
+delivered. These are Agent editorial decisions, not new CLI checks or routine per-article
+approval gates. Top-level changes follow the focused review described above.
 
 ## Edit one section or review part of a batch
 

package/providers/context/resources/procedures/work-start-report.md

@@ -78,6 +78,17 @@ Estimate timing or savings only when supported by measurements and conditions.
 For a small addition to an existing site, describe only the affected reading
 position; reuse its layout and delivery choices instead of proposing them again.
 
+## Review navigation changes in context
+
+Read the knowledge-updates guidance on preserving established navigation intent.
+For an existing site, explain the category intent being reused and the affected
+article placements. A new source or product is not a reason for a new top-level
+menu. If a top-level addition, rename, removal or purpose change is warranted,
+include its before/after tree, reuse alternatives and impact in this report.
+Obtain explicit feedback before applying that structural change, reusing a
+concrete structure already approved by the user. If it emerges later, update this
+same plan and review only the changed decision; do not restart approved batches.
+
 ## Mandatory feedback
 
 Write the scratch report using the host file tool, show its clickable path,

package/providers/context/resources/templates/work-start-report.md

@@ -44,7 +44,13 @@ modules, public capabilities, product operations or another evidenced structure.
 Distinguish navigation groups from sourced articles; reuse articles rather than
 duplicating bodies. Retain existing KB, website and LLMS delivery choices.
 
-For website delivery, add a compact sketch showing the site title, top-level
+For an existing site, summarize the existing categories' intent and affected
+article placements. For a proposed top-level change, show the before/after tree,
+why existing categories cannot accommodate it and the affected pages/order.
+Mark it as a decision for review; omit this comparison when top-level structure
+is unchanged. Reuse explicit prior approval of the concrete structure.
+
+For a new website or an approved navigation redesign, add a compact sketch showing the site title, top-level
 groups, a representative left menu, article chapters and on-page outline.
 For a new homepage or requested redesign, also propose a short title, slogan,
 description and the verified optional resource cards. Briefly explain mobile

package/providers/context/skills/work-production-stage/SKILL.md

@@ -9,7 +9,9 @@ in the user's conversation language.
 When planning or revising article placement, titles or reading order, read
 [reader organization guidance](../../resources/procedures/knowledge-updates.md#reader-tasks-names-and-reading-order).
 Apply it to the affected topics within the user's scope; it adds no production
-stage or permission gate.
+stage. Reuse existing category intent; propose top-level changes in the current
+report/plan for explicit review before applying them, unless the concrete
+structure is already approved. Ordinary placements need no additional gate.
 
 For investigation, use the supplied directory and its submission schema. Start
 with code skeletons and document outlines; selectively read original material