@c4a/context-cli 0.6.1-beta.3 → 0.6.1-beta.4

package/docs/quickstart.md

@@ -31,6 +31,13 @@ Create a standalone workspace:
 context init context
 ```
 
+Choose the generated workspace and starter-template language explicitly when
+needed; the CLI does not infer it from terminal locale or conversation text:
+
+```bash
+context init context --language zh-CN
+```
+
 Then enter it and install dependencies:
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.6.1-beta.3",
+  "version": "0.6.1-beta.4",
   "type": "module",
   "description": "Local CLI for capturing, compiling, and governing knowledge workspaces",
   "license": "MIT",
@@ -20,8 +20,8 @@
     "context": "cli.js"
   },
   "dependencies": {
-    "@c4a/agent-graph": "0.2.2",
-    "@c4a/context": "0.6.1-beta.3",
+    "@c4a/agent-graph": "0.2.3",
+    "@c4a/context": "0.6.1-beta.4",
     "commander": "^11.0.0",
     "handlebars": "^4.7.8",
     "ink": "^5.0.0",

package/plugins/README.md

@@ -40,8 +40,13 @@ context status --format json
 ```
 
 `workflow.current` is the current-step authority. The Agent reads every required
-resource, executes only returned commands, preserves revision and authority
-flags, and reevaluates status after each action. Long procedures and semantic
+resource marked `read_state: read-required`, executes only returned commands,
+preserves revision and authority flags, and reevaluates status after each
+action. Current-conversation read receipts may be passed back through
+`context status --resource-receipts @<file>` so unchanged resources are marked
+`current`. A dynamic materialization becomes a receipt only after the Agent
+reads the complete returned file. `context.source-body/*` resources are source
+text; source indexes and heading metadata never replace the body. Long procedures and semantic
 judgment rules are published in the Context workflow bundle and loaded only
 when the current route or operation selects them.
 

package/plugins/README_CN.md

@@ -38,8 +38,13 @@ Continuation 从以下命令开始：
 context status --format json
 ```
 
-`workflow.current` 是当前步骤的权威协议。Agent 读取全部 required 资源，只执行
-返回的命令，完整保留 revision 与 authority 参数，并在每次动作后重新求值。
+`workflow.current` 是当前步骤的权威协议。Agent 读取所有标记为
+`read_state: read-required` 的 required 资源，只执行返回的命令，完整保留
+revision 与 authority 参数，并在每次动作后重新求值。当前会话可通过
+`context status --resource-receipts @<file>` 回传读取回执，使未变化资源标记为
+`current`。动态资源的 materialize 结果只有在 Agent 完整读取返回文件后才可作为
+回执；`context.source-body/*` 是必须阅读的正文，source-index 和标题元数据不能
+替代正文。
 长篇流程与语义判断规则发布在 Context workflow bundle 中，仅在当前路线或操作
 选中时加载。
 

package/plugins/VERSION

@@ -1 +1 @@
-0.6.1-beta.3
+0.6.1-beta.4

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

@@ -1,7 +1,7 @@
 {
   "name": "context",
   "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
-  "version": "0.6.1-beta.3",
+  "version": "0.6.1-beta.4",
   "author": {
     "name": "c4a"
   },

package/plugins/claude/commands/continue.md

@@ -44,15 +44,29 @@ JSONL payload keys, `source_ref` values, and copied CLI output tokens unchanged.
 
 Treat `workflow.current` as the current-step authority:
 
-1. Read every `resources.required` item. Read a `path` directly; for a resource
-   with `command`, execute that command and read the returned file.
+1. Read every `resources.required` item whose `read_state` is
+   `read-required`. Read a `path` directly; for a resource with `command`,
+   execute that command and read the returned file. Keep read receipts only in
+   the current conversation and pass the merged receipt set back with
+   `context status --resource-receipts @<file>`; an unchanged static digest or
+   matching dynamic Route revision then returns `read_state: current`.
+   Materializing a resource is not a read: use the returned
+   `after_read_receipts` only after reading the complete returned file. A
+   `context.source-body/*` resource is the complete captured Markdown body;
+   source indexes and heading metadata never replace it. The exact
+   `resources.after_read.command` returns the re-evaluated `workflow.current`;
+   continue from that response without an additional status call.
 2. At a Gate, keep conditional context phase-local. An `inspection_action`
    Skill or Schema is read only when performing that pre-decision inspection;
    a `resolution_action` Skill or Schema is read only after the user confirms
    the Gate. Neither replaces ordinary `resources.required`.
 3. Execute only `commands` returned by the Route, preserving revision and
    authority flags exactly. A command marked `after-human-confirmation` must
-   wait for the current Gate decision.
+   wait for the current Gate decision. Run a command whose
+   `execution.target` is `agent-host` as a top-level host action with the
+   host's external and credential access, not inside a restricted child
+   sandbox. Request host approval when required; never weaken credential
+   storage as a workaround.
 4. If `configuration` is present, edit only the named project file using the
    selected resources as its contract.
 5. After every action or configuration change, run status again. The managed

package/plugins/claude/commands/init.md

@@ -1,6 +1,6 @@
 ---
 description: "Initialize a Context knowledge workspace."
-argument-hint: "[project-dir] [--name <name>]"
+argument-hint: "[project-dir] [--name <name>] [--language en|zh-CN]"
 allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
 ---
 
@@ -12,9 +12,12 @@ step, then hand control to the current workflow route.
 Use the user's language for conversation. Keep command and payload tokens
 unchanged.
 
-Run `context init [project-dir] [--name <name>]` with only the arguments the
-user supplied. Never substitute `.` when `project-dir` was omitted; the default
-is `context/`. Use `--dev` only for an explicitly requested local-link test.
+Run `context init [project-dir] [--name <name>] --language <language>`. Use the
+user's explicit language choice when present; otherwise pass `zh-CN` for a
+Chinese conversation and `en` for an English conversation. This explicit CLI
+value controls generated workspace instructions and starter templates. Never
+substitute `.` when `project-dir` was omitted; the default is `context/`. Use
+`--dev` only for an explicitly requested local-link test.
 
 If init reports `init-target-nonempty`, explain that existing files would share
 the workspace root. Run the returned `--allow-nonempty` command only after

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

@@ -1,6 +1,6 @@
 {
   "name": "context",
-  "version": "0.6.1-beta.3",
+  "version": "0.6.1-beta.4",
   "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
   "author": {
     "name": "c4a"
@@ -18,7 +18,7 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "C4A Context",
-    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.6.1-beta.3",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.6.1-beta.4",
     "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/continue/SKILL.md

@@ -56,15 +56,29 @@ JSONL payload keys, `source_ref` values, and copied CLI output tokens unchanged.
 
 Treat `workflow.current` as the current-step authority:
 
-1. Read every `resources.required` item. Read a `path` directly; for a resource
-   with `command`, execute that command and read the returned file.
+1. Read every `resources.required` item whose `read_state` is
+   `read-required`. Read a `path` directly; for a resource with `command`,
+   execute that command and read the returned file. Keep read receipts only in
+   the current conversation and pass the merged receipt set back with
+   `context status --resource-receipts @<file>`; an unchanged static digest or
+   matching dynamic Route revision then returns `read_state: current`.
+   Materializing a resource is not a read: use the returned
+   `after_read_receipts` only after reading the complete returned file. A
+   `context.source-body/*` resource is the complete captured Markdown body;
+   source indexes and heading metadata never replace it. The exact
+   `resources.after_read.command` returns the re-evaluated `workflow.current`;
+   continue from that response without an additional status call.
 2. At a Gate, keep conditional context phase-local. An `inspection_action`
    Skill or Schema is read only when performing that pre-decision inspection;
    a `resolution_action` Skill or Schema is read only after the user confirms
    the Gate. Neither replaces ordinary `resources.required`.
 3. Execute only `commands` returned by the Route, preserving revision and
    authority flags exactly. A command marked `after-human-confirmation` must
-   wait for the current Gate decision.
+   wait for the current Gate decision. Run a command whose
+   `execution.target` is `agent-host` as a top-level host action with the
+   host's external and credential access, not inside a restricted child
+   sandbox. Request host approval when required; never weaken credential
+   storage as a workaround.
 4. If `configuration` is present, edit only the named project file using the
    selected resources as its contract.
 5. After every action or configuration change, run status again. The managed

package/plugins/codex/skills/init/SKILL.md

@@ -24,9 +24,12 @@ step, then hand control to the current workflow route.
 Use the user's language for conversation. Keep command and payload tokens
 unchanged.
 
-Run `context init [project-dir] [--name <name>]` with only the arguments the
-user supplied. Never substitute `.` when `project-dir` was omitted; the default
-is `context/`. Use `--dev` only for an explicitly requested local-link test.
+Run `context init [project-dir] [--name <name>] --language <language>`. Use the
+user's explicit language choice when present; otherwise pass `zh-CN` for a
+Chinese conversation and `en` for an English conversation. This explicit CLI
+value controls generated workspace instructions and starter templates. Never
+substitute `.` when `project-dir` was omitted; the default is `context/`. Use
+`--dev` only for an explicitly requested local-link test.
 
 If init reports `init-target-nonempty`, explain that existing files would share
 the workspace root. Run the returned `--allow-nonempty` command only after

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

@@ -1,7 +1,7 @@
 {
   "name": "context",
   "displayName": "C4A Context",
-  "version": "0.6.1-beta.3",
+  "version": "0.6.1-beta.4",
   "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
   "author": {
     "name": "Context4AI",

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

@@ -48,15 +48,29 @@ JSONL payload keys, `source_ref` values, and copied CLI output tokens unchanged.
 
 Treat `workflow.current` as the current-step authority:
 
-1. Read every `resources.required` item. Read a `path` directly; for a resource
-   with `command`, execute that command and read the returned file.
+1. Read every `resources.required` item whose `read_state` is
+   `read-required`. Read a `path` directly; for a resource with `command`,
+   execute that command and read the returned file. Keep read receipts only in
+   the current conversation and pass the merged receipt set back with
+   `context status --resource-receipts @<file>`; an unchanged static digest or
+   matching dynamic Route revision then returns `read_state: current`.
+   Materializing a resource is not a read: use the returned
+   `after_read_receipts` only after reading the complete returned file. A
+   `context.source-body/*` resource is the complete captured Markdown body;
+   source indexes and heading metadata never replace it. The exact
+   `resources.after_read.command` returns the re-evaluated `workflow.current`;
+   continue from that response without an additional status call.
 2. At a Gate, keep conditional context phase-local. An `inspection_action`
    Skill or Schema is read only when performing that pre-decision inspection;
    a `resolution_action` Skill or Schema is read only after the user confirms
    the Gate. Neither replaces ordinary `resources.required`.
 3. Execute only `commands` returned by the Route, preserving revision and
    authority flags exactly. A command marked `after-human-confirmation` must
-   wait for the current Gate decision.
+   wait for the current Gate decision. Run a command whose
+   `execution.target` is `agent-host` as a top-level host action with the
+   host's external and credential access, not inside a restricted child
+   sandbox. Request host approval when required; never weaken credential
+   storage as a workaround.
 4. If `configuration` is present, edit only the named project file using the
    selected resources as its contract.
 5. After every action or configuration change, run status again. The managed

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

@@ -1,6 +1,6 @@
 ---
 description: "Initialize a Context knowledge workspace."
-argument-hint: "[project-dir] [--name <name>]"
+argument-hint: "[project-dir] [--name <name>] [--language en|zh-CN]"
 allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
 ---
 
@@ -16,9 +16,12 @@ step, then hand control to the current workflow route.
 Use the user's language for conversation. Keep command and payload tokens
 unchanged.
 
-Run `context init [project-dir] [--name <name>]` with only the arguments the
-user supplied. Never substitute `.` when `project-dir` was omitted; the default
-is `context/`. Use `--dev` only for an explicitly requested local-link test.
+Run `context init [project-dir] [--name <name>] --language <language>`. Use the
+user's explicit language choice when present; otherwise pass `zh-CN` for a
+Chinese conversation and `en` for an English conversation. This explicit CLI
+value controls generated workspace instructions and starter templates. Never
+substitute `.` when `project-dir` was omitted; the default is `context/`. Use
+`--dev` only for an explicitly requested local-link test.
 
 If init reports `init-target-nonempty`, explain that existing files would share
 the workspace root. Run the returned `--allow-nonempty` command only after

package/plugins/skills/context-continue/SKILL.md

@@ -56,15 +56,29 @@ JSONL payload keys, `source_ref` values, and copied CLI output tokens unchanged.
 
 Treat `workflow.current` as the current-step authority:
 
-1. Read every `resources.required` item. Read a `path` directly; for a resource
-   with `command`, execute that command and read the returned file.
+1. Read every `resources.required` item whose `read_state` is
+   `read-required`. Read a `path` directly; for a resource with `command`,
+   execute that command and read the returned file. Keep read receipts only in
+   the current conversation and pass the merged receipt set back with
+   `context status --resource-receipts @<file>`; an unchanged static digest or
+   matching dynamic Route revision then returns `read_state: current`.
+   Materializing a resource is not a read: use the returned
+   `after_read_receipts` only after reading the complete returned file. A
+   `context.source-body/*` resource is the complete captured Markdown body;
+   source indexes and heading metadata never replace it. The exact
+   `resources.after_read.command` returns the re-evaluated `workflow.current`;
+   continue from that response without an additional status call.
 2. At a Gate, keep conditional context phase-local. An `inspection_action`
    Skill or Schema is read only when performing that pre-decision inspection;
    a `resolution_action` Skill or Schema is read only after the user confirms
    the Gate. Neither replaces ordinary `resources.required`.
 3. Execute only `commands` returned by the Route, preserving revision and
    authority flags exactly. A command marked `after-human-confirmation` must
-   wait for the current Gate decision.
+   wait for the current Gate decision. Run a command whose
+   `execution.target` is `agent-host` as a top-level host action with the
+   host's external and credential access, not inside a restricted child
+   sandbox. Request host approval when required; never weaken credential
+   storage as a workaround.
 4. If `configuration` is present, edit only the named project file using the
    selected resources as its contract.
 5. After every action or configuration change, run status again. The managed

package/plugins/skills/context-init/SKILL.md

@@ -24,9 +24,12 @@ step, then hand control to the current workflow route.
 Use the user's language for conversation. Keep command and payload tokens
 unchanged.
 
-Run `context init [project-dir] [--name <name>]` with only the arguments the
-user supplied. Never substitute `.` when `project-dir` was omitted; the default
-is `context/`. Use `--dev` only for an explicitly requested local-link test.
+Run `context init [project-dir] [--name <name>] --language <language>`. Use the
+user's explicit language choice when present; otherwise pass `zh-CN` for a
+Chinese conversation and `en` for an English conversation. This explicit CLI
+value controls generated workspace instructions and starter templates. Never
+substitute `.` when `project-dir` was omitted; the default is `context/`. Use
+`--dev` only for an explicitly requested local-link test.
 
 If init reports `init-target-nonempty`, explain that existing files would share
 the workspace root. Run the returned `--allow-nonempty` command only after

package/providers/context/actions/accept-package-templates.yaml

@@ -0,0 +1,5 @@
+schema: agent-graph.action.v1
+id: accept-package-templates
+runner: command
+effect: write
+command: context package template accept --all --format json

package/providers/context/actions/align-next.yaml

@@ -3,3 +3,4 @@ id: align-next
 runner: host
 effect: write
 handler: context.align.next
+inputSchema: schemas/prose-structure-batch.schema.json

package/providers/context/codes.yaml

@@ -8,6 +8,7 @@ codes:
   - { code: diagnostic.compile-route-ambiguous, kind: diagnostic, severity: error, summary: More than one compile lifecycle owns the same source and collection., document: resources/diagnostics/workspace-state.md }
   - { code: diagnostic.structure-snapshot-missing, kind: diagnostic, severity: error, summary: A compile batch references a missing confirmed structure snapshot., document: resources/diagnostics/workspace-state.md }
   - { code: diagnostic.verify-failed, kind: diagnostic, severity: error, summary: Verification found one or more blocking findings., document: resources/diagnostics/verification.md }
+  - { code: diagnostic.projection-stale, kind: diagnostic, severity: info, summary: Approved knowledge changed and deterministic close must refresh its derived projection., document: resources/diagnostics/projection-stale.md }
   - { code: diagnostic.evidence-degraded, kind: diagnostic, severity: warning, summary: Approved knowledge has evidence that cannot currently be rechecked., document: resources/diagnostics/verification.md }
   - { code: diagnostic.evidence-stale, kind: diagnostic, severity: warning, summary: Approved knowledge evidence is stale against its registered source., document: resources/diagnostics/verification.md }
   - { code: diagnostic.evidence-orphaned, kind: diagnostic, severity: warning, summary: Approved knowledge no longer resolves to registered source evidence., document: resources/diagnostics/verification.md }
@@ -35,4 +36,5 @@ codes:
   - { code: route.close.projection-stale, kind: route-reason, summary: Rebuild the deterministic approved structure projection., document: resources/procedures/close-and-build.md }
   - { code: route.package.output-required, kind: route-reason, summary: Approved knowledge has no confirmed package output., document: resources/procedures/package-output.md }
   - { code: route.package.configuration-required, kind: route-reason, summary: Declare the confirmed package output in the Context project., document: resources/procedures/package-output.md }
+  - { code: route.package.template-review-required, kind: route-reason, summary: "Replace or edit package templates, or explicitly accept the generic defaults.", document: resources/procedures/package-output.md }
   - { code: route.build.package-stale, kind: route-reason, summary: Build the declared package outputs from current approved knowledge., document: resources/procedures/close-and-build.md }

package/providers/context/graphs/workspace.yaml

@@ -384,6 +384,8 @@ nodes:
       required:
         - resources/procedures/close-and-build.md
         - resources/views/verification-current.yaml
+      recommended:
+        - resources/diagnostics/projection-stale.md
 
   - id: choose-package-output
     kind: gate
@@ -402,6 +404,7 @@ nodes:
         - resources/dialogue/human-gates.md
         - resources/dialogue/package-output.md
         - resources/views/package-current.yaml
+      recommended:
         - resources/manuals/guides/package-outputs.md
         - resources/manuals/reference/package-templates.md
         - resources/manuals/reference/template-variables.md
@@ -418,7 +421,9 @@ nodes:
         - resources/procedures/project-configuration.md
         - resources/procedures/package-output.md
         - resources/views/package-current.yaml
+      recommended:
         - resources/manuals/guides/package-outputs.md
+        - resources/manuals/reference/project-api.md
         - resources/manuals/reference/package-templates.md
         - resources/manuals/reference/template-variables.md
 
@@ -434,6 +439,25 @@ nodes:
         - resources/procedures/close-and-build.md
         - resources/views/package-current.yaml
 
+  - id: review-package-template
+    kind: gate
+    reasonCode: route.package.template-review-required
+    resolutionAction: actions/accept-package-templates.yaml
+    gate:
+      id: package-template-review
+      prompt: Replace or edit the declared package templates, or explicitly accept the unchanged generic defaults.
+      authority: context.package-template-review
+      delegatable: true
+    satisfiedBy:
+      - path: packages.templates_reviewed
+        equals: true
+    resources:
+      required:
+        - resources/procedures/package-output.md
+        - resources/dialogue/human-gates.md
+        - resources/views/package-current.yaml
+        - resources/manuals/reference/package-templates.md
+
   - id: current-scope-complete
     kind: terminal
     terminalOutcome: completed
@@ -465,5 +489,6 @@ edges:
   - { from: configure-prose-lifecycle, to: align-next }
   - { from: align-next, to: choose-package-output }
   - { from: choose-package-output, to: configure-package-output, kind: gatedBy }
-  - { from: configure-package-output, to: build-next }
+  - { from: configure-package-output, to: review-package-template }
+  - { from: review-package-template, to: build-next, kind: gatedBy }
   - { from: build-next, to: current-scope-complete }