clavue 8.25.2 → 8.26.2

package/docs/clavue-high-efficiency-development-orchestration.md

@@ -1,83 +0,0 @@
-# Clavue high-efficiency development orchestration
-
-Clavue's fastest development path is not a new command surface. It is an intent-context layer that describes the user's likely development shape while the existing runtime route decision remains the authority for workflow mode, plan discipline, verification discipline, recovery, and visible tools.
-
-## Runtime model
-
-```text
-User turn
-  -> development intent classifier
-  -> route decision and visible tools
-  -> advisory development context derived from the route decision
-  -> model tool execution
-  -> verification and outcome
-```
-
-The development context layer must stay above tools and below user intent. It does not replace route policy, permissions, tool schemas, plan discipline, verification discipline, or recovery behavior. It only adds a compact system-context hint that summarizes intent and repeats the authoritative route decision.
-
-## Intent classes
-
-| Intent | Typical trigger | Runtime bias |
-|---|---|---|
-| `diagnose` | "先分析", "read-only", "do not edit" | inspect only |
-| `review_plan` | "审查项目并给升级方案", "review and provide upgrade plan" | analytical review only |
-| `continue` | "继续", "keep going", "做完" | continue active work |
-| `quick_fix` | direct bug/feature request | inspect, edit, targeted test |
-| `complex_implementation` | "实现架构调整", "重构并落地", "complex implementation" | non-trivial execution bias |
-| `parallel_investigation` | "team", "parallel", "并行" | team/agent fan-out |
-| `docs_plan` | "形成文档", "设计方案" | plan/document first |
-| `commit` | git commit request | git-only flow |
-| `release` / `publish` | release or npm publish | release gate |
-| `push` | git push/GitHub push | explicit external action |
-
-## Context outputs
-
-The context produces only advisory metadata:
-
-- `mode`: inspect, review, execute, plan, parallel, release, or git bias
-- route workflow mode copied from the runtime decision
-- route plan discipline copied from the runtime decision
-- route verification discipline copied from the runtime decision
-- route recovery mode copied from the runtime decision
-- `userFacingInstruction`: compact summary that says route policy remains authoritative
-
-## Safety boundaries
-
-- Route policy remains the source of truth for provider capability, workflow mode, plan discipline, verification discipline, recovery, and visible tools.
-- Tools remain generic. They do not decide when they should be used.
-- External side effects such as publish, push, tag, PR creation, or destructive cleanup still require explicit user authorization.
-- Parallel agents are recommended only for independent research or separated work streams.
-- Completion claims must cite verification when the policy requires it.
-
-## User-facing triggers
-
-Users can continue to write naturally:
-
-```text
-继续，把当前任务做到验证通过
-先只读分析，不要改代码
-审查当前项目并提供升级方案
-稳健实现这个功能，覆盖测试
-用 team 并行分析并推进这个问题
-确认发布 patch 版本到 npm，发布前跑完整检查
-按当前改动生成原子 git commit，只用 git
-```
-
-The runtime turns these into compact advisory context instead of requiring the user to learn a mode language.
-
-## Implementation locations
-
-- `src/runtime/developmentIntent.ts` classifies the turn intent.
-- `src/runtime/developmentOrchestrationPolicy.ts` maps intent plus route decision into advisory context.
-- `src/runtime/developmentOrchestrationPrompt.ts` renders the compact prompt block.
-- `src/runtime/turn-loop-orchestrator.ts` injects the block into system context for the current turn.
-- `tests/development-orchestration.test.mjs` locks the behavior.
-
-## Extension points
-
-Future product work can build on this without polluting tools:
-
-- Show the selected orchestration mode in the outcome card.
-- Let `/doctor` detect PATH shadowing and stale global installs.
-- Add a dedicated release skill that reuses `release_gate` policy.
-- Teach `/team` to recommend parallel layouts for common work shapes.