Tianyi Cui
71b0d83822
Compose the shared release branch PTC rename with the structural system-head migration in the existing V2-to-V3 stage. Audit source payloads and remap local coordinates before renaming dispatch vocabulary and owned plugin attribution; retain original message identities and generation-qualified references. Native V3 validation combines the same system and PTC lifecycle semantics through a private released-validation view. Reuse the V3 row-admission owner in current JSONL scanning before recoverable-tail suppression, so malformed rows cannot hide retired required PTC tags or header.system. The new corruption-prefix regressions and all173 existing JSONL scanner tests pass. Combined migration/catalog/persistence suite:300 tests; executable V3 migration source has100% coverage. No released generation, prior migration implementation, shared release branch, benchmark or CI workflow is modified by this integration.
description, kind
| description | kind |
|---|---|
| Package map for the plan group: the plan-mode feature that guides the agent to explore and design before executing, for users and maintainers navigating the group. | package-group |
plan/ — plan collaboration state
English | 中文
Summary
The plan/ group provides plan mode: while it is active, the agent explores and designs before executing, guided by instructions the deployment writes, and presents the finished plan for your approval before carrying it out. You can enter and leave plan mode with the /plan command and approve the plan or send the agent back to keep planning. Plan mode guides rather than restricts: every tool stays available, and limits such as sandbox mode and approval prompts are configured separately. The group contains one package, plan-mode.
Table of Contents
Packages
One package provides the whole plan-mode feature; the subsystem reference owns the exhaustive contracts.
| Package | Role | ctx key |
|---|---|---|
plan-mode/ |
Provides plan mode: /plan enters and leaves it, deployment guidance steers the agent while planning, and exit_plan_mode presents the finished plan for your review |
ctx.planMode |
Related documentation
Start with the subsystem reference for the shared vocabulary, then read the design note for the decisions.
- Plan mode subsystem reference — how plan mode works, its configuration, and the exit tool's behavior.
- Plan-specific collaboration state — the design decision behind plan mode.
Dev Note
Working context for maintainers — click to expand
None.