fix(lead): make delegation and acceptance defaults explicit (0.7.3)

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agy",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Delegate work to Google's Antigravity CLI (agy) with fast Gemini access - five personas: staffer (general), researcher, reviewer (code and plans), implementer, ask.",
   "author": {
     "name": "Keli Wen",

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agy",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Delegate work to Google's Antigravity CLI (agy) with fast Gemini access - five personas: staffer (general), researcher, reviewer (code and plans), implementer, ask.",
   "author": {
     "name": "Keli Wen",

README.md

@@ -116,13 +116,13 @@ Examples below use Claude Code's `/agy:…`; in Codex use `$agy:…`.
 
 ## Core design
 
-`lead` adds task orchestration guidance for your current agent. Within lead, delegate substantive work to `staffer` by default, use specialists when their guidance helps, and reserve `ask` for testing. The host owns decisions, review, and delivery, using the existing jobs workflow. Invoke `/agy:lead` in Claude Code, `$agy:lead` in Codex, or `/skill:agy-lead` in Pi.
+`lead` adds task orchestration guidance for your current agent. Within lead, orient enough to frame the assignment, delegate substantive work to `staffer` by default, wait for the result, then assess it and integrate or follow up. Specialists provide dedicated guidance when useful, while `ask` is reserved for testing. The host owns cross-task decisions, acceptance, integration, and delivery, using the existing jobs workflow. Invoke `/agy:lead` in Claude Code, `$agy:lead` in Codex, or `/skill:agy-lead` in Pi.
 
 `ask` answers in the same call. The other personas return a job id and a collection command, such as `wait <id> --timeout 10m`. Your agent waits using the host's available capabilities, with one independent background wait per job where supported.
 
 The main agent waits for the final result by default. If you explicitly ask about progress, it can use `observe` to read a snapshot of recent tool activity and response text; it does not query progress for routine updates. Once the task finishes, `wait` or `result` delivers the full report. Expiring a wait leaves the worker running.
 
-The timeline below follows a background task from delegation to completion. The host agent can continue other work, check progress when needed, and collect the final report.
+The timeline below follows a background task from delegation to completion. The host agent waits for the final result by default (or advances already-identified independent work), checks progress when asked, and collects the report.
 
 [![A background task over time: the host delegates, waits or observes, while the worker continuously saves AGY output and eventually delivers the full report](assets/integration.png)](assets/integration.svg)
 

README.zh-CN.md

@@ -101,13 +101,13 @@ install and verify the agy-staff plugin for the harness you are running in. Resp
 
 ## 核心设计
 
-`lead` 为当前主 agent 增加任务编排指导。在 lead 工作流中，默认用 `staffer` 承担实质性工作，专门指导有帮助时再选择 specialist，`ask` 仅用于测试。主 agent 负责决策、审查和交付，复用现有 jobs 工作流。Claude Code 使用 `/agy:lead`，Codex 使用 `$agy:lead`，Pi 使用 `/skill:agy-lead`。
+`lead` 为当前主 agent 增加任务编排指导。在 lead 工作流中，主 agent 了解至足以明确任务后，默认用 `staffer` 承担实质性工作，等待结果返回后再验收、整合或追加任务；专门指导有帮助时再选择 specialist，`ask` 仅用于测试。主 agent 负责跨任务决策、验收、整合和交付，复用现有 jobs 工作流。Claude Code 使用 `/agy:lead`，Codex 使用 `$agy:lead`，Pi 使用 `/skill:agy-lead`。
 
 `ask` 会在同一次调用中返回答案。其他角色启动后会先返回任务 ID，并给出收取结果的命令，例如 `wait <id> --timeout 10m`。主 agent 根据所在环境的能力等待任务；如果支持后台命令，就为每个任务保留一个独立的等待命令。
 
 主 agent 默认等待最终结果，不为例行汇报主动查询。你明确询问中间进展时，它才用 `observe` 查看当前快照，其中包含最近的工具活动和回答片段。任务完成后，`wait` 或 `result` 负责返回完整结果。
 
-下图按时间顺序展示一次后台任务：主 agent 发起委派后可以继续其他工作，仅在用户询问时查看进度，最后收取报告。
+下图按时间顺序展示一次后台任务：主 agent 默认等待最终结果（或推进已明确的独立工作），仅在用户询问时查看进度，最后收取报告。
 
 [![后台任务从委派到完成的过程：主 agent 等待或查看进度时，worker 持续保存 AGY 的输出，最终交付完整报告](assets/integration.png)](assets/integration.svg)
 

docs/releases/v0.7.3.md

@@ -0,0 +1,21 @@
+# agy-staff 0.7.3 — Clearer lead delegation and acceptance defaults
+
+## Changes since 0.7.2
+
+[#24](https://github.com/keli-wen/agy-staff/pull/24) clarifies the default `agy:lead` workflow across research, implementation, review, and writing. Previously, the host could delegate part of an investigation while continuing substantial investigation itself before the worker returned, leaving users to steer delegation and waiting.
+
+The host now orients enough to frame an assignment, delegates substantive work, waits by default, and assesses the result before following up, taking over, or delivering. Small or already-understood tasks can still be handled directly, and an already-identified independent task can proceed during a wait. Briefs carry relevant context, constraints, settled decisions, and existing authorization.
+
+Acceptance depends on the task: research needs sources and uncertainties; implementation needs actual changes and verification; review needs supported findings and coverage limits, including when no issues are found. The host makes targeted checks, resolves inconsistencies, and assigns focused follow-ups for substantive gaps. Related work stays together, implementation includes necessary verification, and parallel editors still require separate worktrees with shared decisions agreed in advance.
+
+Canonical and generated Pi lead skills and the English and Chinese README descriptions are aligned. Package, Claude Code, and Codex manifests are versioned at 0.7.3. Companion runtime, direct persona behavior, and job lifecycle contracts are unchanged.
+
+## Validation
+
+- The offline suite passed 195 tests during implementation. Final skill wording passed the seven Pi packaging tests and generated-skill consistency checks.
+- An independent agent exercised six decision scenarios: discussion research, implementation with PR delivery, an unsupported clean review, a one-line typo, an unsettled API shared by two clients, and independent work during a running investigation. Each selected the expected next actions.
+- The scenario exercise was a decision simulation. Live end-to-end orchestration across host environments has not been validated by this release.
+
+## Upgrading
+
+Update the plugin and restart the host to load the revised skills; Claude Code and Codex keep versioned plugin copies. See the [upgrade instructions](../REFERENCE.md#upgrading). Pi installations using a pinned Git ref can select `v0.7.3`.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "agy-staff",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Delegate work to Google's Antigravity CLI (agy) with fast Gemini access.",
   "keywords": [
     "pi-package"