allye-opencode 1.2.5 → 1.2.7

package/dist/index.js

@@ -749,9 +749,15 @@ You drive delivery. You don't plan \u2014 that already happened in Technical Pla
 
 ## 1. On start
 
-If you arrived via a \`technical-to-orchestration\` handover (see \`handover-protocol\`), read it in full \u2014 it's your only context, there is no prior conversation to fall back on. Load everything it points at: the doc, the epic, the feature, every story, every task, grouped by wave.
+If you arrived via a \`technical-to-orchestration\` handover (see \`handover-protocol\`), read it in full \u2014 it's your only context, there is no prior conversation to fall back on.
 
-If you arrived without a handover (the user just wants to resume coordinating an in-progress feature), ask for the feature key if it isn't already clear, then load the same hierarchy via \`work_get\`/\`work_children\`.
+Then load the actual work. **The handover's list is an index to verify against, not a substitute for reading:**
+
+1. **Read the full subtree under the handover's parent item.** \`work_get\` the parent (a feature \u2014 or an epic, when the user chose to hand over a whole epic), then walk \`work_children\` level by level all the way down (epic \u2192 features \u2192 stories \u2192 tasks), reading every item's description \u2014 not just its key and status. Nothing below the parent is out of scope just because the handover didn't happen to list it.
+2. **Consult every reference the handover names.** Docs get opened via \`doc_get\` (locate via \`doc_full_tree\` if only named); suggested memory queries actually get run. A reference listed but never opened is a briefing you skipped.
+3. **Cross-check against the handover's list.** If the subtree you loaded and the handover disagree \u2014 items in Allye missing from the handover, listed items that don't exist, wave structure that doesn't match \u2014 stop and ask before dispatching anything.
+
+If you arrived without a handover (the user just wants to resume coordinating an in-progress feature), ask for the feature or epic key if it isn't already clear, then do the same full subtree read via \`work_get\`/\`work_children\`.
 
 Search memories for relevant prior context (\`memory_search("Session State {feature key}")\`, \`memory_search("decision {feature key}")\`) \u2014 a delivery already in progress may have decisions and blockers recorded from earlier sessions.
 
@@ -1072,7 +1078,7 @@ After completing a task, pick the next one from the **handover's own wave-ordere
 - If the current wave is done \u2192 move to the next wave (per the handover's list)
 - If every task in the story has reached \`review\` (implementation complete, awaiting Reviewer) \u2192 emit an **\`execution-report\`** handover (see the \`handover-protocol\` skill) back to the Orchestrator
 
-Use \`work_children(id: "{story uuid}")\` only to **verify/check the status** of tasks already in the handover's list (e.g. confirming a dependency reached \`review\`) \u2014 never to discover new tasks to work on. If \`work_children\` reveals a task under this story that is **not** in the handover's task list, do not execute it \u2014 it wasn't in scope when the handover was dispatched. Instead, note it as an open question ("D\xFAvidas em aberto") in the \`execution-report\` handover so the Orchestrator can decide whether to bring it into scope.
+Use \`work_children(id: "{story uuid}")\` only to **verify/check the status** of tasks already in the handover's list (e.g. confirming a dependency reached \`review\`) \u2014 never to discover new tasks to work on. If \`work_children\` reveals a task under this story that is **not** in the handover's task list, do not execute it \u2014 it wasn't in scope when the handover was dispatched. Instead, note it as an open question ("Open questions") in the \`execution-report\` handover so the Orchestrator can decide whether to bring it into scope.
 
 ---
 
@@ -2006,29 +2012,29 @@ Generate a complete handoff using the shared marker format \u2014 same shape Cla
 
 \`\`\`
 ## \uD83D\uDD04 Allye Handover \u2014 technical-to-orchestration
-**Skill a carregar:** orchestrator
+**Skill to load:** orchestrator
 
-### Objetivo
-Conduzir a entrega de {FEATURE-KEY} \u2014 {feature title}
+### Objective
+Drive delivery of {FEATURE-KEY} \u2014 {feature title}
 
-### Leitura obrigat\xF3ria
+### Required reading
 - Epic: {EPIC-KEY}
 - Feature: {FEATURE-KEY}
-- Stories e tasks por wave:
+- Stories and tasks by wave:
   - {STORY-KEY} \u2014 {title}
     - Wave 1: {TASK-KEY}, {TASK-KEY}
     - Wave 2: {TASK-KEY}
 
-### Decis\xF5es de arquitetura travadas
+### Locked architecture decisions
 - {decision 1}: {rationale}
 - {decision 2}: {rationale}
 
-### Contexto adicional
+### Additional context
 - {anything the user mentioned}
 - {relevant memories saved during planning}
 
 ---
-Se algo n\xE3o estiver claro, PARE e pergunte \u2014 n\xE3o prossiga chutando.
+If anything is unclear, STOP and ask \u2014 don't proceed on a guess.
 \`\`\`
 
 ### Step 4: Instruct the user
@@ -2090,7 +2096,7 @@ Generate a handoff scoped to exactly ONE story and its tasks \u2014 never a whol
 
 \`\`\`
 ## \uD83D\uDD04 Allye Handover \u2014 story-execution
-**Skill a carregar:** execution
+**Skill to load:** execution
 
 ### Story
 {STORY-KEY} \u2014 {title}, with acceptance criteria copied in full
@@ -2098,11 +2104,11 @@ Generate a handoff scoped to exactly ONE story and its tasks \u2014 never a whol
 ### Tasks
 {TASK-KEY list with acceptance criteria}
 
-### Decis\xF5es travadas aplic\xE1veis
+### Applicable locked decisions
 {locked decisions from planning}
 
 ---
-Se algo n\xE3o estiver claro, PARE e pergunte \u2014 n\xE3o prossiga chutando.
+If anything is unclear, STOP and ask \u2014 don't proceed on a guess.
 \`\`\`
 
 ### Step 2: Receive the execution report, dispatch Review
@@ -2124,16 +2130,16 @@ Review returns its standard \u2705/\u26A0\uFE0F/\u274C-per-task output.
 
 \`\`\`
 ## \uD83D\uDD04 Allye Handover \u2014 correction
-**Skill a carregar:** execution
+**Skill to load:** execution
 
-### Achados a corrigir (\u274C apenas)
+### Findings to fix (\u274C only)
 - {TASK-KEY}: "{finding, quoted literally}"
 
-### Rodada de corre\xE7\xE3o
-Esta \xE9 a {N}\xAA tentativa de corre\xE7\xE3o nesta story.
+### Correction round
+This is correction attempt {N} for this story.
 
 ---
-Corrija S\xD3 o que est\xE1 listado acima \u2014 n\xE3o refa\xE7a a story inteira.
+Fix ONLY what's listed above \u2014 don't redo the whole story.
 \`\`\`
 
 **Escalate to the user instead of emitting a 4th correction handoff if the same task fails review 3 times.** Two rounds failing for different specific reasons is normal; three usually means something deeper is being missed.
@@ -2225,26 +2231,26 @@ When all tasks in the current story are done \u2014 or you've hit a genuine bloc
 
 \`\`\`
 ## \uD83D\uDD04 Allye Handover \u2014 execution-report
-**Skill a carregar:** orchestrator
+**Skill to load:** orchestrator
 
-### Story implementada
+### Story implemented
 {STORY-KEY} \u2014 {title}
 
-### Tasks e status por crit\xE9rio de aceite
-- {TASK-KEY}: {\u2705 conclu\xEDda | \u26A0\uFE0F parcial | \u274C bloqueada}
-  - {crit\xE9rio}: {atendido | n\xE3o atendido \u2014 por qu\xEA}
+### Tasks and status per acceptance criterion
+- {TASK-KEY}: {\u2705 done | \u26A0\uFE0F partial | \u274C blocked}
+  - {criterion}: {met | not met \u2014 why}
 
-### Arquivos alterados
+### Files changed
 - {path} \u2014 {what changed}
 
-### Decis\xF5es novas tomadas durante a implementa\xE7\xE3o
-- {decision}, or "Nenhuma decis\xE3o nova"
+### New decisions made during implementation
+- {decision}, or "No new decision"
 
-### D\xFAvidas em aberto
-{anything unresolved, or "Nenhuma"}
+### Open questions
+{anything unresolved, or "None"}
 
 ---
-Se algo n\xE3o estiver claro, PARE e pergunte \u2014 n\xE3o prossiga chutando.
+If anything is unclear, STOP and ask \u2014 don't proceed on a guess.
 \`\`\`
 
 > "Story {STORY-KEY} is implemented. Switch to **Allye Orchestrator** (Ctrl+T \u2192 Allye Orchestrator) and paste the handover above \u2014 it'll dispatch review and handle status from here."

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "allye-opencode",
-  "version": "1.2.5",
+  "version": "1.2.7",
   "description": "Allye multi-agent plugin for OpenCode — planning, building, reviewing, and delivering with structured workflows",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",