@c4a/context-cli 0.5.33-alpha.3 → 0.5.33-alpha.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/cli.js +44632 -42314
  2. package/package.json +1 -1
  3. package/plugin/commands/capture.md +1 -1
  4. package/plugin/commands/compile.md +2 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@c4a/context-cli",
3
- "version": "0.5.33-alpha.3",
3
+ "version": "0.5.33-alpha.4",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "context": "./cli.js"
package/plugin/commands/capture.md CHANGED
@@ -91,5 +91,5 @@ Your prose to the user follows the user's conversation language. CLI commands, f
91
91
  - In `--format json`, code capture runner cache state is authoritative in `result.runner.cacheMode`: `prepared` means a workspace runner was prepared, `cached` means workspace cache hit, and `bypass` means `--no-runner-cache` used a temporary runner directory instead of the workspace runner cache.
92
92
  - Aspect snapshots default to `evidence.mode: none`. Prose-like custom aspects must opt in with `evidence: { mode: block }` in `aspects/<name>/aspect.yaml` before they generate evidence manifests. Invalid `evidence.mode` values are reported as `evidence-policy-invalid`; they are not silently treated as `none`.
93
93
  - Code aspect snapshots ship with `evidence.mode: none`; symbols/files/edges are indexed inside the code bucket. Do not ask users to inspect or repair a code `.evidence` manifest.
94
- - Code aspect capture does not currently generate active knowledge Nodes. Do not ask users to run `/context:compile` just because no code Nodes appear; that is the expected boundary.
94
+ - Code aspect capture writes raw code snapshots first. Materialize them with `context compile --code <slug>` (or no slug for all actionable code sources) before prose align needs to attach documentation to code Nodes.
95
95
  - On duplicate capture of the same URL: identical `content_hash` → CLI skips with `unchanged`; different hash → CLI appends a new snapshot.
package/plugin/commands/compile.md CHANGED
@@ -29,6 +29,8 @@ Modes:
29
29
 
30
30
  Code mode short-circuit: if `$ARGUMENTS` contains `--code`, run `context compile --code [slug]` immediately, relay the CLI output, and stop. Do not run the default compile doctor/draft/reconcile preflight for code projection.
31
31
 
32
+ Code-only default routing: if `$ARGUMENTS` is empty, first run `context status --view summary --format json`. When its `next_actions[]` / `next_step.command` contain only `context compile --code ...` actions for active code sources, run `context compile --code` once with no slug so the CLI projects all actionable code sources, then run `context compile --close` only if the compile output says close is needed. If the code projection status asks for `context align --code <slug>` instead, run that dry-run diagnostic and stop with the reported conflict. Do not ask the user whether to run deterministic code projection after they invoked `/context:compile`.
33
+
32
34
  Delegated workflow mode:
33
35
 
34
36
  - If the user explicitly authorized托管/全自动/delegated mode at the start of this conversation, add `--delegated` to the first compile workflow-creating command, preferably `context compile --scan-changes --delegated --format json`. Do not add it for vague "continue" / "继续" permission.