@aksp/opencrew 1.11.0 → 1.13.0

package/templates/_opencrew/core/runner/fontes-pendentes.md

@@ -0,0 +1,21 @@
+# Source check that did not end in FONTES:OK
+
+> Part of the Pipeline Runner (`_opencrew/core/runner.pipeline.md`). Read it only when the source check of the Initialization (1c) ended in `FONTES:PENDENTE` or did not run.
+
+If the last line is `FONTES:PENDENTE` (a cited file was moved, renamed or deleted), show the
+report and ask — never continue silently with a missing source:
+```
+Alguns arquivos que a crew usa não estão mais onde ela espera:
+{resumo do relatório}
+
+1. Corrigir os caminhos sugeridos (troco nos arquivos da crew e guardo .bak)
+2. Seguir assim mesmo
+3. Parar
+```
+On 1, run the same command with `--corrigir`, show the new result and re-read `crew.yaml` and
+any agent file already loaded (it may have changed them); 1d then loads the sources from the
+corrected paths. If the new result still ends in `FONTES:PENDENTE`, ask again with options 2 and
+3 only. Alerts — not portable (absolute paths) or "não conferido" (a network path or a site
+address: the script never accesses the network) — are mentioned once, without stopping. If the
+script did not run (no Node, an error, or no `FONTES:` status line), tell the user "⚠️ A
+conferência de fontes não rodou: {motivo}" and continue; the final approval repeats the warning.

package/templates/_opencrew/core/runner/memoria.md

@@ -0,0 +1,55 @@
+# Memory format
+
+> Part of the Pipeline Runner (`_opencrew/core/runner.pipeline.md`). Read it only when `memories.md` has no `## Estilo de Escrita` section header, is empty or does not exist.
+
+**Note on language**: The structural labels listed below are **fixed PT-BR** and must
+never be translated — opencrew's primary supported audience is PT-BR (see AGENTS.md →
+Language Handling). Only the *content* written under these headers follows the user's
+preferred language.
+
+| Fixed PT-BR header | Location | Purpose |
+|---|---|---|
+| `## Estilo de Escrita` | `memories.md` | Writing style rules accumulated per crew |
+| `## Design Visual` | `memories.md` | Visual design preferences per crew |
+| `## Estrutura de Conteúdo` | `memories.md` | Content structure rules per crew |
+| `## Proibições Explícitas` | `memories.md` | User bans and hard blocks per crew |
+| `## Técnico (específico do crew)` | `memories.md` | Technical crew-specific settings |
+| `Data \| Run ID \| Tema \| Output \| Score \| Resultado` | `runs.md` | Run history table columns |
+
+When adding new structural sections to `memories.md` or `runs.md`, keep headers in PT-BR
+unless the user base expands beyond PT-BR — at that point, discuss a migration strategy
+(e.g. i18n key mapping) rather than mixing languages in a single file.
+
+## Migration
+
+**Memory format migration** — After loading `memories.md`, check whether it uses the new format: it does when it has the `## Estilo de Escrita` section header (read the file with the read tool — no command).
+   - If it has the header → proceed normally.
+   - If it does not (or the file is empty / does not exist) → migrate before proceeding:
+     a0. If the file exists and is not empty, FIRST copy it to `crews/{name}/_memory/memories.md.bak`
+        (never lose what the crew learned), then tell the user in one line:
+        "Atualizei o formato da memória da crew; a versão anterior está em `memories.md.bak`."
+        Move every rule you can recognize from the old file into the matching new section.
+     a. Write `crews/{name}/_memory/memories.md` with the new sections format:
+        ```markdown
+        # Crew Memory: {crew-name}
+
+        ## Estilo de Escrita
+
+        ## Design Visual
+
+        ## Estrutura de Conteúdo
+
+        ## Proibições Explícitas
+
+        ## Técnico (específico do crew)
+        ```
+        (Use the crew's display name for `{crew-name}`, and the crew code for `{name}` in file paths — they refer to the same crew.)
+     b. Check if `crews/{name}/_memory/runs.md` exists (read tool — no command).
+        If it does not exist, create it with:
+        ```markdown
+        # Run History: {crew-name}
+
+        | Data | Run ID | Tema | Output | Score | Resultado |
+        |------|--------|------|--------|-------|-----------|
+        ```
+   - Do not pause execution for this migration (the one-line notice above is enough).

package/templates/_opencrew/core/runner/selecao-de-agentes.md

@@ -0,0 +1,79 @@
+# Pre-Execution Agent Selection
+
+> Part of the Pipeline Runner (`_opencrew/core/runner.pipeline.md`). Read it only when `crew.yaml` declares an `agent_dependencies:` field. It decides which agents actually run for this task.
+
+Run this step ONLY if `crew.yaml` declares an `agent_dependencies:` field (even an
+empty map `{}`). If the field is absent → skip this entire step and run ALL agents
+exactly as before (legacy behavior).
+
+When active, in this order:
+
+a. **Capture the task** — Determine the user's request for this run:
+   - If the run was invoked with a description (e.g. `/opencrew run {name} {description}`),
+     use that text as the task.
+   - Otherwise ask: `📝 What is the task for this run? Reply in one line.`
+     Wait for the user's reply before continuing.
+
+b. **Analyze against the decision matrix** — Scan the task text (case-insensitive,
+   PT-BR and EN keywords) for the signals below. Start with ALL agents suggested as
+   SELECTED (`required`). For each matching signal, find the affected agent(s) in
+   `crew-party.csv` by matching the role terms against the agent's `id` and `title`
+   (and `displayName` if ambiguous), then apply the suggested status:
+
+   | Signal in the task | Role terms to match (id / title) | Suggested status |
+   |--------------------|----------------------------------|------------------|
+   | "já pesquisei", "com base em", "fontes que tenho", "material pronto", "baseado nas fontes", "research already done" | researcher, pesquisad, research | optional |
+   | "revise", "melhore", "corrija", "refine", "edite" (sem criar do zero), "improve this draft" | copywriter, redator, writer, criador | optional |
+   | "só texto", "sem imagem", "sem visual", "sem arte", "no image" | designer, design, visual | skip |
+   | "já revisei", "já foi aprovado", "aprovado por terceiros", "revisão feita", "already reviewed" | reviewer, revisor | optional |
+   | "quero só revisar este texto", "apenas revisar", "review only" | researcher AND copywriter | skip |
+   | "tenho o conteúdo pronto", "forneço o documento", "docs em anexo", "segue o material", "here is the content" | copywriter, writer, creator | optional |
+
+   Resolution rules:
+   - `optional` = agent stays selected but may be unchecked.
+   - `skip` = agent is suggested deselected.
+   - Conflicting signals on the same agent → the more restrictive wins (`skip` > `optional`).
+   - Never suggest skipping an agent whose output is the run's final deliverable unless the
+     signal is explicit.
+   - No signal matches → suggest keeping all agents (no change).
+
+c. **Present the selection** — IDE-neutral numbered multi-select. List every agent from
+   `crew-party.csv` in party order:
+   ```
+   🧑‍🤝‍🧑 Which agents should work on this task?
+
+   Suggested selection:
+   1. [x] {icon} {displayName} ({id}) — {title}
+   2. [x] {icon} {displayName} ({id}) — {title}
+   3. [ ] {icon} {displayName} ({id}) — {title}
+   ...
+   [x] = suggested selected · [ ] = suggested deselected
+
+   Reply with the numbers of the agents you want to INCLUDE, separated by commas.
+   Example: "1, 2"   ·   Reply "all" to run everyone.
+   ```
+   Wait for the user's reply. Parse it into `selected_agents`. At least one agent must
+   be selected — if the user replies with none, repeat the prompt once.
+
+d. **Dependency warnings** — Using `crew.yaml → agent_dependencies`
+   (e.g. `copywriter: [researcher]` = copywriter consumes researcher's output):
+   for every dependency `dependent → required_agent`, if `dependent` is selected but
+   `required_agent` is NOT, warn:
+   ```
+   ⚠️ {dependent} normally depends on {required_agent}'s output, which you deselected.
+
+   1. Re-select {required_agent} (recommended)
+   2. Keep going without it — I will supply the input myself
+   3. Deselect {dependent} too
+   ```
+   Wait for the user's choice and apply it. If they pick option 2, set
+   `missing_dependency = true` in working memory (the existing Pre-Step Input
+   Validation recovery — "Skip step and continue / Abort" — then handles any
+   downstream gap).
+
+e. **Build the filtered step list** — Set `skipped_agents = all party agents − selected_agents`.
+   Build `filtered_steps` by walking `pipeline.yaml` in order, keeping a step when:
+   - its frontmatter has NO `agent:` field (checkpoints / generic steps), OR
+   - its `agent:` value is in `selected_agents`.
+   Store `selected_agents`, `skipped_agents`, and `filtered_steps` in working memory for
+   the per-step loop (steps 5 and 6 of the Initialization reflect them).

package/templates/_opencrew/core/runner/tarefas-do-agente.md

@@ -0,0 +1,34 @@
+# Task-Based Agent Execution
+
+> Part of the Pipeline Runner (`_opencrew/core/runner.pipeline.md`). Read it only when the agent of the step has a `tasks:` field in its frontmatter.
+
+When an agent's `.agent.md` frontmatter contains a `tasks:` field:
+
+1. **Load task list**: Read the `tasks:` array from the agent's frontmatter
+   - Each entry is a relative path to a task file (e.g., `tasks/analyze-source.md`)
+   - Tasks execute in the order listed
+
+2. **For each task in sequence**:
+   a. Read the task file from the agent's directory (`crews/{crew-name}/agents/{agent-id}/tasks/{task}.md`: a folder with the agent id, next to the agent file)
+   b. Construct the execution prompt:
+      - Agent persona + principles (from agent.md — fixed across all tasks)
+      - Task description and process (from task file)
+      - Task output format (from task file)
+      - Task quality criteria and veto conditions (from task file)
+      - Input: For the first task, use the step's input. For subsequent tasks, use the previous task's output.
+   c. Execute the task (inline or subagent, matching the step's execution mode)
+   d. Collect the task output
+   e. Check task veto conditions (same enforcement as the step veto conditions: "Veto Condition Enforcement", in the runner)
+
+3. **Final output**: The output of the LAST task in the chain becomes the step's output
+   - Resolve the `outputFile` path with the `saida` command (Output Path Transformation) before saving — this applies regardless of whether the step runs as `execution: inline` or `execution: subagent`
+   - Save to the **transformed** outputFile path
+   - This is what the next step (or checkpoint) receives
+
+4. **Progress reporting**: For inline execution, announce each task:
+   ```
+   {icon} {Agent Name} — Task {N}/{total}: {task name}...
+   ```
+
+5. **Backward compatibility**: If the agent's frontmatter does NOT contain a `tasks:` field,
+   execute the agent monolithically as before (current behavior unchanged).