@c4a/context-cli 0.6.0-beta.6 → 0.6.0-beta.8

package/README.md

@@ -19,8 +19,8 @@ stable protocol text and are not translated.
 ## Global Plugin + Project Workspace
 
 ```bash
-# Install or refresh global agent commands/skills.
-bunx @c4a/context-cli plugin install
+# Install the CLI and refresh available global agent commands/skills.
+npm install -g @c4a/context-cli
 
 # Create a standalone context project.
 context init context
@@ -30,6 +30,11 @@ bun install
 /context:continue
 ```
 
+Global installation runs `context plugin install` automatically for the
+available Claude and Codex CLIs. Plugin refresh is best-effort and does not
+make the CLI installation fail; rerun `context plugin install` manually after
+installing an agent CLI. Set `CONTEXT_CLI_SKIP_PLUGIN_INSTALL=1` to opt out.
+
 The global plugin calls `context ...` from the current project root.
 Agent commands follow CLI `next:` hints: they execute safe mechanical steps and
 stop at `Human gate:` / placeholder next steps, source registration, source scope
@@ -110,6 +115,11 @@ Runtime scratch lives under `.tmp/context-runtime/` and is ignored. It may conta
 The project-local workflow is status-driven. Register sources, declare phases in
 `src/index.ts`, then let `context status` and phase views route each gate:
 
+Building a package completes the currently active structure snapshots, not the
+workspace forever. Additional captured documents remain in
+`pendingStructureTargets` until their own declared align/compile/review route is
+completed; they can be added without creating a new workspace.
+
 | Gate | Current surface |
 |---|---|
 | Source setup | `context source add repo/file/lark`, `context source ensure`, and project source declarations. |
@@ -136,22 +146,23 @@ For project workflows, `context` is a semantic service. Agents should call the C
 | `context plugin path` | CLI | Print the bundled plugin marketplace root. Installed packages normally use `dist/plugins`; source checkouts use the same path after build. |
 | `context plugin install [--agent claude\|codex\|all] [--dry-run]` | CLI | Install or refresh the bundled plugin marketplace globally for Claude and/or Codex. It replaces existing `context` marketplace entries and Codex cache owned by this package before reinstalling. |
 | `context plugin status [--agent claude\|codex\|all]` | CLI | Inspect bundled plugin path and agent CLI availability. |
-| `context init [project-dir] [--name <name>] [--dev]` | CLI | Create a project-local context workspace. Defaults to `context/`; use `.` to initialize the current directory. Use `--dev` for local checkout testing before `@c4a/context` is published. |
+| `context init [project-dir] [--name <name>] [--dev]` | CLI | Create a project-local context workspace. Defaults to `context/`; use `.` to initialize the current directory. Use `--dev` for local checkout or prepared-pack testing before the matching `@c4a/context` version is published. |
 | `context source add repo <name> --local <repo-or-subdir> [--remote <url>] [--ref <sha>]` | CLI | Register a repo source and pin it to a commit. Local paths may point at a monorepo subdirectory; the CLI stores the git root plus subpath, and materializes the source view to the subdirectory. Remote and ref are inferred from local origin / HEAD when omitted. Short SHAs are resolved to full commits when the local repo is available. |
 | `context source ensure [name]` | CLI | Validate and materialize local source symlinks. Missing remotes only produce hints; the CLI does not clone or checkout automatically. |
 | `context source add batch [date] --input <file|->` | CLI | Register multiple repo, file, or Lark modules under one project write lock from YAML/JSON input. Repo modules are explicit; file/Lark modules may be derived when omitted. |
 | `context source list|get <name>` | CLI | Inspect the repo source registry and readiness metadata. |
 | `context source inspect [name]` | CLI | Detect module/package boundaries in registered repo sources without extraction. Use this before extracting monorepo roots; it prints package names, paths, versions when available, and suggested source registration commands. |
 | `context run --list` | CLI | List phases declared by `src/index.ts`. |
-| `context run <phase-id> [--dry-run] [--auto-promote]` | CLI | Inspect or run one declared phase. Extract dry-run separates discovered, AST-analyzed, skipped, symbol, and relation counts. Missing/empty entries fail with `NO_ENTRY_DETECTED`; TypeScript aliases come from tsconfig/jsconfig `baseUrl` and `paths`. Codegraph defaults to first-run full Review and later delta-only Review; `--auto-promote` applies deterministic codegraph deltas, refreshes deterministic close when needed, then verifies. Existing package outputs become stale and remain an explicit downstream build step. |
+| `context run <phase-id> [--dry-run] [--auto-promote] [--managed]` | CLI | Inspect or run one declared phase. Extract dry-run separates discovered, AST-analyzed, skipped, symbol, and relation counts. Missing/empty entries fail with `NO_ENTRY_DETECTED`; TypeScript aliases come from tsconfig/jsconfig `baseUrl` and `paths`. Codegraph defaults to first-run full Review and later delta-only Review; `--auto-promote` applies deterministic codegraph deltas, refreshes deterministic close when needed, then verifies. `--managed` is current-conversation authority propagated by an Agent, never project policy. Existing package outputs become stale and remain an explicit downstream build step. |
 | `context review html [collection] [--open]` | CLI | Render the local self-contained HTML review surface under `.tmp/context-runtime/review/`, emit a clickable `file://` URL, and optionally open it with the system browser. |
 | `context review list [collection]` | CLI | List draft candidates for CLI-oriented review. |
 | `context review apply <payload-file>` | CLI | Apply copied review decisions; approved entities materialize to `knowledge/`, rejected entities remain in `unapproved/entities.jsonl`. |
 | `context review approve|reject <candidate-id> --collection <collection>` / `--all` | CLI | Scoped quick marking for a single draft candidate when the user explicitly authorizes an automated or quick path. |
+| `context review approve-all [collection] --managed` / `--all --managed` | CLI | Atomically approve the current validated Review scope under explicit current-conversation fully managed authority. The flag is required and no policy is persisted. |
 | `context review migrate-codegraph-refs` | CLI | Upgrade legacy approved codegraph refs to `src-N#symbol:<file>:<symbol>:<kind>@<digest>`, remove redundant `code_origin`, and verify. Rerun declared codegraph extraction first; this metadata migration does not repeat Review. |
 | `context build` | CLI | Build declared project packages from approved knowledge into `dist/<package-name>/`. |
 | `context verify [--format table\|json]` | CLI | Validate the project skeleton, registry, unapproved ledger, approved Markdown, source refs, and package outputs. |
-| `context status [--format json\|table]` | CLI | Workspace overview + a canonical `next:` hint. Agent plugins expose this workflow as `/context:continue`; do not add or call `context continue`. |
+| `context status [--managed] [--format json\|table]` | CLI | Workspace overview + a canonical `next:` hint. `--managed` resolves eligible human gates only for the explicitly authorized current conversation; source permission, external operations, validation, and verification remain enforced. Agent plugins expose this workflow as `/context:continue`; do not add or call `context continue`. |
 
 Commands that require a project exit with a workspace-not-found error if run outside a directory tree containing a `package.json` `context.project=true` / `context.entry` marker. `context init` is the command that creates one.