@aksp/opencrew 1.9.0 → 1.11.0

package/templates/_opencrew/core/prompts/discovery.prompt.md

@@ -80,12 +80,15 @@ After the user answers Step 1, classify their intent into one of the following d
 
 | Domain | Signals in the user's answer |
 |---|---|
+| `document` | minutes (ata), official letter (ofício), contract, proposal, bylaws (estatuto), legal opinion (parecer), formal report, statement: a text to print, sign or file |
 | `content` | posts, articles, videos, captions, social media, campaigns, copy, newsletter, creative, reels, threads |
 | `research` | data, analysis, reports, competitor, market, insights, scraping, summarizing, monitoring |
 | `automation` | workflows, triggers, scheduling, notifications, integrations, pipelines, bots, recurring tasks |
 | `analysis` | metrics, dashboards, KPIs, performance, trends, tracking, visualization |
 | `mixed` | answer spans two or more domains above |
 
+When the request is a text to print, sign or file, the domain is `document` even if the words also fit `content` or `research`.
+
 Save the detected domain as `domain`.
 
 ---
@@ -99,6 +102,13 @@ Based on the detected domain, ask the most relevant contextual question first. W
 2. What platforms or formats? (wait for answer — do not list formats yet, that comes in Step 6)
 3. What tone or personality should the content have? (multiple choice: professional / casual / educational / entertaining / other)
 
+**If domain = `document`:**
+1. Which documents should the crew produce? (open-ended: ata, ofício, contrato, proposta…)
+2. Who signs each document, and who receives it? (open-ended)
+3. Does the organization have letterhead (logo, header lines, footer) that these documents must carry? (yes / no / not sure — the letterhead itself is set up later, the first time a Word document is generated; here you only record the answer)
+
+The project sources question below matters most here: ask which files of the project rule the text (bylaws, previous minutes, price table, contract template).
+
 **If domain = `research`:**
 1. What sources will the crew draw from? (multiple choice: public websites / internal documents / social media / databases / other)
 2. What is the output format? (multiple choice: summary report / structured data / slide deck / raw export / other)
@@ -143,7 +153,9 @@ Do NOT ask the user about tools. Instead:
 
 ### Step 5 — Investigation (optional)
 
-Offer the investigation option to the user. The investigation is powerful but consumes tokens and time — make the trade-off clear:
+**If domain = `document`, skip this step entirely** (set `investigation.enabled: false`): a document crew follows the project's own sources, not reference profiles.
+
+For every other domain, offer the investigation option to the user. The investigation is powerful but consumes tokens and time — make the trade-off clear:
 
 > "Want to investigate reference profiles before building the crew? The investigation analyzes real content from profiles you admire to extract patterns, hooks, and styles. It uses extra tokens and takes a few minutes, but can significantly improve the final quality."
 >
@@ -194,7 +206,8 @@ Set `investigation.enabled: false` and continue.
 
 ### Step 6 — Target Formats (content crews ONLY)
 
-Skip this step entirely for non-content domains.
+If domain = `document`, do not ask: save `target_formats: ["documento-oficial"]`. When the crew also produces a short piece for a channel (a WhatsApp notice, an e-mail to the members), add that format id to the list — pick it from the filenames of `_opencrew/core/best-practices/` — and go on.
+Skip this step entirely for the other non-content domains.
 
 If domain = `content`, ask:
 > "Para quais formatos/plataformas esse crew vai produzir conteúdo?"
@@ -254,7 +267,7 @@ project_sources:                     # relative to the project root; becomes `fo
   - path: "{e.g. Memoria/01_Decisoes.md}"
     purpose: "{what the crew uses it for}"
 purpose: "{user's description from Step 1}"
-domain: "{content | research | automation | analysis | mixed}"
+domain: "{document | content | research | automation | analysis | mixed}"
 # When a template was used (Step 0), these fields are populated from discovery.template.yaml:
 domains: []                          # list of domain tags from template (e.g., [content-marketing, seo])
 tier: "standard"                     # from template or preferences Default Tier
@@ -272,6 +285,11 @@ company:
 language: "{user's preferred language}"
 
 context:
+  # For document crews:
+  documents: "{answer from Step 3}"
+  signer: "{who signs}"
+  recipients: "{who receives}"
+  letterhead: "{yes | no | not sure}"
   # For content crews:
   audience: "{answer from Step 3}"
   platforms: "{answer from Step 3}"
@@ -299,7 +317,7 @@ investigation:
       platform: "{instagram | youtube | twitter | linkedin}"
       investigation_mode: "{single_post | profile_1 | profile_3}"
 
-target_formats:  # content crews only; empty list for others
+target_formats:  # content and document crews; empty list for others
   - "{format-id}"
 ```
 
@@ -317,7 +335,7 @@ The `crew_code` must be a short, URL-safe slug derived from the crew's purpose (
 - **NEVER ask more than 8 questions total** — respect the user's time
 - **NEVER ask about tools** — auto-detect from installed skills and include in the summary
 - **NEVER ask about performance mode** — crews are always built lean and agile
-- **Investigation is always offered** — Step 5 presents the option for all domains, not just content
+- **Investigation is offered to every domain except `document`** — Step 5 presents the option; a document crew skips it
 - **Target formats are content-only** — Step 6 is skipped entirely for non-content crews
 - **One question at a time** — never combine two questions in one message, even if they feel related
 - **Domain detection is silent** — do not announce "I detected your domain is X"; just use the classification internally

package/templates/_opencrew/core/prompts/documento.prompt.md

@@ -0,0 +1,134 @@
+# Documento Word — A Text File Turned into a `.docx`
+
+One script turns a text file of the project (markdown, `.md` or `.txt`) into a Word document with
+the same words and the same numbers, in the same order. When the project has a profile
+(`_opencrew/_memory/documento-oficial.md`: logo, header, footer, margins and font), the document
+comes out on letterhead. Your part is to find out which file, ask about the letterhead when the
+project has none, run the script and show its report.
+
+You do NOT write the `.docx` yourself, and you never change the user's text to make it convert:
+the script reads the file as it is. The writing rules of a text that becomes a document (title,
+sections, page break, signatures) are in `_opencrew/core/best-practices/documento-oficial.md`.
+
+## Step 1: Which file
+
+`/opencrew documento <arquivo>` names the file. With no file (the command alone, or the menu
+option "Documento Word"), ask and wait:
+
+```
+Qual arquivo de texto (.md ou .txt) você quer em Word? Diga o caminho a partir da pasta do projeto (por exemplo, `Atas/ata-de-marco.md`).
+```
+
+- `{arquivo}` is a path inside the project, written from its root. One file per command: for
+  several files, run Steps 3 to 5 once for each.
+- Never guess the file, and never pick one "that looks like it": with a name that matches more
+  than one file, list them and ask.
+
+## Step 2: The letterhead, when the project has none
+
+Check, with the read tool (no command), whether `_opencrew/_memory/documento-oficial.md` exists.
+If it does, go to Step 3: nothing is asked. If it does not, ask and wait:
+
+```
+Este projeto ainda não tem papel timbrado configurado. Quer configurar agora (logotipo, cabeçalho e rodapé)? (sim / não)
+```
+
+- **"Sim"** —
+  1. Run, from the project root: `node _opencrew/core/scripts/documento.mjs --criar-perfil`
+     Its last line is `PERFIL:CRIADO` (the file was created from the model) or `PERFIL:JA-EXISTE`
+     (it was already there and was not touched).
+  2. Ask the user for: the logo (a PNG file of up to 2 MB that is inside the project, with its
+     path from the root — or none), the three lines of the header (the name of the organization;
+     a second line; a third line, such as site and e-mail) and the text of the footer. Any of them
+     may stay empty: what is empty does not appear in the document.
+  3. Fill the file `_opencrew/_memory/documento-oficial.md` with the answers: write only the value
+     after the colon of `logotipo`, `cabecalho_1`, `cabecalho_2`, `cabecalho_3` and `rodape`, each
+     exactly as the user gave it. Leave every other line as it is (comments, margins, font).
+     Never invent a value (a registration number, an address, a slogan), and never copy a logo
+     into the project by yourself: if the file is outside the project, ask the user to put it in.
+- **"Não"** — go on without the profile: the document comes out with no letterhead, with the
+  standard margins and "Página X de Y" in the footer. Do not ask again in this conversation.
+
+After this step the profile belongs to the user. Change it only when the user asks, and only the
+line asked for.
+
+## Step 3: Run the script
+
+From the project root, one line, the path between double quotes:
+
+`node _opencrew/core/scripts/documento.mjs "{arquivo}"`
+
+- **`{arquivo}` was typed by the user and goes into a command** — the safe-name rule (nome seguro)
+  of `_opencrew/core/runner.pipeline.md` applies: between double quotes and only if it is made of
+  letters (accents included), digits, space and `. _ - / \ : ( )`. With any other character do NOT
+  run the command; say
+  `⚠️ O nome `{arquivo}` tem um caractere que não posso usar em comandos ({caractere}). Use só letras, números, espaço, ponto, hífen, sublinhado e parênteses.`
+  and ask for the file again. The same rule holds for every path below.
+- The Word goes next to the text, with the same name (`Atas/ata.md` → `Atas/ata.docx`). Only when
+  the user asks for another place, the command ends with `--saida "{pasta ou arquivo.docx}"`
+  (inside the project; a folder is created if it is missing).
+- Only when the user asks for a document with no letterhead this time, add `--sem-perfil`; only
+  when the user names another profile file, add `--perfil "{arquivo do perfil}"`.
+
+The output of the script is the report: where the document was written, which profile was used,
+the conversion warnings ("Avisos:") and two tips — "Para ter um PDF: abra o documento no Word e
+use Arquivo → Salvar como → PDF." and "O Word é uma cópia do texto. O que você mudar nele não
+volta sozinho: altere o texto e gere de novo.". Show it to the user as it came, without the
+`DOCUMENTO:OK` line. It is fixed PT-BR, whatever the user's language: do not rewrite it.
+
+- `DOCUMENTO:OK` → done. A warning does not change that: it says what stayed as plain text (an
+  image, an unknown `:::` line, a signature block with no closing `:::`) or what was removed (an
+  invalid character). Offer to fix the text and generate again; change the text only on a "sim".
+- "{arquivo} já existe e está igual. Nada a fazer." is also `DOCUMENTO:OK`: nothing was written.
+
+## Step 4: A Word that is already there
+
+When the output is the line "Já existe {arquivo}, diferente do que eu ia gravar. Para trocar, rode
+de novo com --substituir.", nothing was written: there is a different `.docx` at the destination,
+and the user may have edited it in Word. Ask before replacing it, and wait:
+
+```
+Já existe {arquivo}, diferente do que eu ia gravar. Posso substituir? O que foi mudado direto no Word se perde. (sim / não)
+```
+
+- "Sim" → the same command again, ending with `--substituir`.
+- "Não" → nothing is replaced. Offer another name or folder (`--saida`, Step 3).
+
+The first call never has `--substituir`, and a "sim" is worth for that file and that call only.
+
+## Step 5: When the command fails
+
+The command failed when there is no Node, an error, or no `DOCUMENTO:` line at the end (it prints
+one message in PT-BR and stops, with nothing written). Show the message to the user as it came.
+
+- **The message points to something in the command you wrote** (an option, a path, more than one
+  file): fix the command and run it once more.
+- **The message starts with "Perfil, linha {n}:"** (an unknown key, a value out of range, a logo
+  that is missing, is not a PNG or is over 2 MB): the document is not generated with a wrong
+  letterhead. Show the message, ask the user for the right value of that line, write it in the
+  profile and run again. Do not switch to `--sem-perfil` by yourself.
+- **"Não consegui gravar {arquivo}. …"**: the file is open in Word or the folder is syncing. Ask
+  the user to close it and run the same command again.
+- **Anything else**, or the command did not run at all:
+
+  ```
+  ⚠️ A conversão para Word não rodou: {motivo}. O texto continua em {arquivo}.
+  ```
+
+  `{motivo}` is the message the script printed (without its final period), or what kept it from
+  running. Stop there.
+
+Never generate the document by any other means: no other script, no library, no Word or office
+automation, no HTML or RTF saved with another extension. A document made another way would not
+have the same guarantees (the same words, the letterhead of the profile), and the user would not
+know.
+
+## Rules
+
+- **DO** show the report of the script as it came.
+- **DO** ask before `--substituir`, every time.
+- **DO NOT** generate the `.docx` by any other means, even when the script fails.
+- **DO NOT** edit the user's text to remove a warning without a "sim".
+- **DO NOT** write in `_opencrew/_memory/documento-oficial.md` anything the user did not give you.
+- **DO NOT** promise how the document looks in Word: you did not open it. The user checks the
+  header, the pages, the tables and the signatures in Word.

package/templates/_opencrew/core/prompts/entrega.prompt.md

@@ -45,8 +45,8 @@ sozinha. Antes de postar à mão, confira se já saiu."
   `_opencrew/best-practices.local/{format}.md` when that file declares `platform:`, otherwise in
   `_opencrew/core/best-practices/{format}.md`. For a step with no `format:`, the one of the skill
   (`instagram-publisher` → `instagram`). With neither, do not pass the option.
-- `{canal}` is the folder name: `instagram`, `linkedin`, `blog`, `email`, `whatsapp`, `twitter` or
-  `youtube`. Only a channel that has an item in the list (an item whose format has that
+- `{canal}` is the folder name: `instagram`, `linkedin`, `blog`, `email`, `whatsapp`, `twitter`,
+  `youtube` or `documentos` (the folder of `platform: "documento"`). Only a channel that has an item in the list (an item whose format has that
   `platform:`) — for any other the script stops with `Canal não encontrado nesta entrega: {canal}.`
 
 ## Step 3: Run the script
@@ -68,7 +68,8 @@ without the `ENTREGA:` line. Do not rewrite it and do not add files it does not
 `entrega/` folder, the script also writes `crews/{name}/output/{run_id}/verificacao-entrega.md`,
 the report of the check made at delivery time (it is not part of the delivery).
 
-- `ENTREGA:OK` → go on with the run (Step 5 first, when it applies).
+- `ENTREGA:OK` → go on with the run (Step 5 first, when it applies). When the summary has a line
+  `
 - `ENTREGA:COM_RESSALVA` → everything that was missing is a ressalva the user accepted: the
   `LEIA-ME.md` opens with it and the channel is "Pronto, com ressalva"; go on as with `ENTREGA:OK`.
 - `ENTREGA:INCOMPLETA` → a channel is not ready, the destination was refused or a file could not be
@@ -102,7 +103,7 @@ the report of the check made at delivery time (it is not part of the delivery).
     "Não consegui gravar …"): show the message as it came and ask for another folder (Step 5, with
     the new answer) or for a new attempt, which is the same command again. A file of the list that
     does not exist: ask for it, or take it out of the list.
-
+  - **A Word document that was not generated** (the line `
   The first call never has `--aceitar-pendencias`. Outside option 2 it goes only when the user
   already chose "Aceitar assim mesmo" in the review loop of this run and what is missing is only
   what was accepted there: then run the command again with it, without asking.

package/templates/_opencrew/core/prompts/repair.prompt.md

@@ -1,114 +1,105 @@
-# Repair — Fix Crew Agent Names / Manifest
+# Repair — bring an existing crew up to date (conserto)
 
-You are the opencrew Repair agent. Your job is to fix an **already-created** crew whose
-agents show their function/role but not their persona names (e.g. the Escritório and the
-Pipeline Runner show "Pesquisador" instead of "Pedro Pesquisa").
+You are the opencrew Repair agent. A crew built by an older version misses what later versions
+added: the format of each text, the project sources, bans the checker can enforce, the persona
+names. Your job is to show the user what is missing in **one crew that already exists** and fix
+one point at a time, each with the user's yes.
 
-This is a known defect in crews built by older versions: the `crew-party.csv` manifest was
-generated without a `displayName` column (or with the role/title in it instead of the
-persona name), while the correct two-word names already live in each agent's `.agent.md`
-`name:` frontmatter. This repair is **deterministic** — you pull names from the `.agent.md`
-files and rewrite the manifest. You do NOT re-generate agent personas, re-run research, or
-re-run the Build phase.
+**You never write inside `crews/` yourself.** Every change is one command of the script below,
+which keeps a `.bak` copy of the file before changing it. You do not re-run Discovery, Design or
+Build, and you do not rewrite the crew into a new layout: older shapes of `crew.yaml` and
+`pipeline.yaml` still work (see `_opencrew/core/formato-da-crew.md`).
 
-## Scope
-
-You may ONLY touch these files under `crews/{code}/`:
-- `crews/{code}/crew-party.csv`
-- `crews/{code}/agents/*.agent.md` (only in the fallback case — see Step 4)
-
-Never modify `_opencrew/`, `templates/`, or any other crew. Use the Write tool for all file
-writes (never Bash `mkdir`).
-
----
+Speak to the user in their language (`_opencrew/_memory/preferences.md`). The script answers in
+fixed PT-BR: when the user's language is another one, translate what you show.
 
 ## Step 1: Identify the crew
 
-- If the user passed a crew code (`/opencrew repair <name>`), use it.
-- Otherwise, list the directories under `crews/` and ask which crew to repair.
-  - If exactly 1 crew exists, offer it plus a "Cancel" option.
-  - If 0 crews exist, tell the user there is nothing to repair and stop.
-
-Verify `crews/{code}/crew.yaml` and `crews/{code}/agents/` exist. If not, report and stop.
+- If the user passed a crew (`/opencrew repair <name>`), use it.
+- Otherwise list the crews and ask which one. **A folder under `crews/` without a `crew.yaml` is
+  not a crew** (the template folders installed with the product): leave it out of the list.
+  - Exactly 1 crew: offer it plus a "Cancelar" option.
+  - 0 crews: say there is nothing to repair and stop.
 
-## Step 2: Read the source of truth (the agent files)
+## Step 2: Diagnose
 
-For EACH `crews/{code}/agents/*.agent.md`, read the YAML frontmatter and extract:
-- `id` (or derive it from the filename: `researcher.agent.md` → `researcher`)
-- `name` — the persona name (expected: two words, "FirstName LastName")
-- `title` — the role/function label
-- `icon` — the emoji
-- `execution` — `inline` or `subagent`
-
-Also read the current `crews/{code}/crew-party.csv` (if present) to preserve any
-`execution`/`title` values that are correct there but missing from a `.agent.md`.
-
-## Step 3: Rebuild `crew-party.csv`
-
-Write `crews/{code}/crew-party.csv` with the canonical header and one row per agent:
+From the project root, with the crew folder between double quotes:
 
 ```
-id,displayName,title,icon,path,execution
+node _opencrew/core/scripts/conserto.mjs --crew "crews/{code}"
 ```
 
-- `displayName` = the agent's `name:` from its `.agent.md` (the two-word persona name).
-- `title` = the agent's `title:`.
-- `icon` = the agent's `icon:`.
-- `path` = `./agents/{id}.agent.md`.
-- `execution` = the agent's `execution:` (default `inline` if absent).
-- Quote any field containing a space or comma with double quotes.
-- Preserve the original agent order (match the previous CSV order if it existed).
+It only reads. Its last line is the status:
 
-## Step 4: Fallback — agent whose `.agent.md` name is itself broken
+- `CONSERTO:OK` — say "A crew {nome} está em dia: não há o que consertar." and stop.
+- `CONSERTO:PENDENTE` — one block per finding, each starting with `[código]`. Go to Step 3.
+- `CONSERTO:ERRO`, or the script did not run (no Node, an error) — show the user the message as
+  it came and stop. Do not repair by hand.
 
-If an agent's `.agent.md` `name:` is empty or has only ONE word, the persona name never
-existed and must be generated now, following the **Agent Naming Convention** from
-`_opencrew/core/prompts/design.prompt.md`:
+Open with: "Olhei a crew {nome}. Encontrei {n} ponto(s) para consertar. Vou mostrar um por vez;
+nada é gravado sem o seu sim, e cada arquivo alterado ganha uma cópia `.bak`."
 
-1. Read the user's Output Language from `_opencrew/_memory/preferences.md`.
-2. Generate a two-word name: "FirstName LastName" — both words start with the SAME letter
-   (alliteration); the first name is common in the user's language; the last name is a
-   playful reference to the agent's function (from its `title:`). Each agent in the crew
-   must use a DIFFERENT initial letter.
-3. Update BOTH the `.agent.md` `name:` frontmatter AND the `# {Name}` heading in that file.
-4. Use the new name as the `displayName` in the rebuilt CSV.
+## Step 3: One finding at a time
 
-Only do this for agents that are actually broken. Agents that already have a valid two-word
-`name:` are left untouched (only the CSV is rewritten to carry it).
+Take the findings in the order the script printed them. For each: say what it is, ask the
+question, wait for the answer, and only then run the command. Never group two findings in one
+question. A "não" leaves the point as it is: go on to the next one.
 
-## Step 5: Report
+The script's output is for you. To the user, say each point in plain words: do not show the
+codes between brackets, the `--aplicar` lines or the `CONSERTO:` status line.
 
-Present a summary table of what changed:
+| Finding | What you say and ask | Command after the yes |
+|---|---|---|
+| `nome-de-agente` | The agent has no two-word persona name. Propose one by the Agent Naming Convention of `_opencrew/core/prompts/design.prompt.md` (two words with the same initial, a different initial for each agent of the crew), keeping the first name the agent already has, and ask: "O agente {id} está sem nome de pessoa. Proponho {Nome Sobrenome}. Posso gravar?" | `--aplicar "nome:{id}={Nome Sobrenome}"`; the names reach the list of the crew with `manifesto`, below — when `manifesto` is not among the findings, run it right after this one |
+| `manifesto` | "O arquivo de nomes da crew está incompleto; por isso aparece a função no lugar do nome. Posso refazer a partir dos arquivos dos agentes?" | `--aplicar "manifesto"` |
+| `formato` | Read each listed step and propose one format per step, among the files of `_opencrew/core/best-practices/` (and `_opencrew/best-practices.local/`). A text to print, sign or file — ata, ofício, contrato, minuta, proposta, parecer — gets `documento-oficial`. Then: "Estes passos não dizem que tipo de texto produzem; sem isso, o verificador mede cada um como post de blog. Minha proposta: {passo → formato}. Posso gravar assim?" | one `--aplicar "formato:{passo}={formato}"` per step |
+| `fontes` | "Esta crew não registra os arquivos do projeto que ela deve ler antes de escrever. Quais arquivos ou pastas ela precisa conhecer? (Pode responder 'nenhum'.)" Confirm that each one exists (search the project when only a name was given) and ask what the crew uses it for | one `--aplicar "fonte:{caminho}={para que}"` per file or folder, the path relative to the project root |
+| `proibicao` | For each listed item: "Esta proibição não tem um trecho entre aspas, então o verificador não consegue barrar: «{item}». Qual trecho exato devo barrar? Se for uma regra de conteúdo, e não uma palavra ou expressão, responda 'revisão humana': ela fica para o revisor." The excerpt must be words of the item itself | `--aplicar "proibicao:{n}={trecho}"` or `--aplicar "proibicao:{n}=revisao-humana"` |
+| `irreversivel` | For each listed step: "O passo {n} é feito por um agente que tem uma ferramenta de publicar ou enviar ({skill}). Este passo publica ou envia alguma coisa para fora do projeto? Se sim, marco o passo para que ele nunca seja repetido sozinho." | `--aplicar "irreversivel:{n}"` only for a yes |
+| `sem-revisao` | "Esta crew não tem passo de revisão: nada é conferido antes de chegar a você. Isso se resolve editando a crew: /opencrew edit {nome}." | none |
+| `sem-aprovacao-final` | "Depois da revisão não há um ponto de aprovação seu. Isso se resolve editando a crew: /opencrew edit {nome}." | none |
+| `publica-antes` | "O passo {n} publica ou envia antes da revisão e da sua aprovação final. Enquanto estiver assim, o que sai não passou pela revisão. Isso se resolve editando a crew: /opencrew edit {nome}." | none |
+| `passo-faltando` | Show the lines the script printed and say that it is solved by editing the crew: `/opencrew edit {nome}` | none |
 
+The command is always the same line, with the item between double quotes:
+
+```
+node _opencrew/core/scripts/conserto.mjs --crew "crews/{code}" --aplicar "{item}"
 ```
-Crew "{name}" repaired.
 
-| Agent id    | Before        | After            | Source        |
-|-------------|---------------|------------------|---------------|
-| researcher  | (role only)   | 🔎 Pedro Pesquisa | .agent.md     |
-| copywriter  | Guilherme     | ✍️ Guilherme Gancho | generated   |
+Several items of the same finding may go in one call (`--aplicar "…" --aplicar "…"`). The last
+line must be `CONSERTO:APLICADO`. With `CONSERTO:ERRO` nothing was written: read the reason to the
+user, correct the item and ask again — do not write the file yourself.
 
-crew-party.csv: rewritten with displayName column
+## Step 4: Project paths
 
-Run it: /opencrew run {code}
+After the findings, run the sources check:
+
+```
+node _opencrew/core/scripts/conferir-fontes.mjs --crew "crews/{code}"
 ```
 
-The Escritório (the optional live view) takes the names from the CSV when the next run starts:
-there is nothing else to refresh.
+When it lists a path with a suggestion (`Sugestão: …` — an absolute path left in a step, or a
+file that moved), show the user each path and its suggestion and ask: "Posso corrigir estes
+caminhos nos arquivos da crew?" After a yes, run the same command ending with `--corrigir`: the
+script rewrites only those paths and keeps a copy of each file it changes. A missing file with
+no suggestion is the user's to solve: say which one.
+
+## Step 5: Report
+
+Run the diagnosis of Step 2 once more and close with what really happened:
 
-If nothing was broken (CSV already had a valid `displayName` for every agent), say so
-plainly instead of inventing changes: "This crew's manifest is already correct — no repair
-needed."
+"Pronto: {k} conserto(s) gravado(s). Cópias do que mudou: {lista de .bak}. Ficou pendente:
+{lista ou 'nada'}." — `{k}` is the number of points the user said yes to and the script wrote.
 
----
+Then: `Run it: /opencrew run {code}`.
 
 ## Rules
 
-- **DO** pull names from `.agent.md` `name:` — that is the source of truth.
-- **DO** rewrite the whole `crew-party.csv` with the canonical header.
-- **DO** limit persona generation to agents whose own `.agent.md` name is missing/one-word.
-- **DO NOT** re-run Discovery, Design, Build, research, or investigations.
-- **DO NOT** modify agent personas, principles, or any section other than the `name:` line
-  and `# {Name}` heading (and only in the fallback case).
-- **DO NOT** touch any file outside `crews/{code}/`.
-- **DO NOT** fabricate a summary — report only what you actually changed.
+- **DO** run the diagnosis before and after; report only what the script printed.
+- **DO** ask before every `--aplicar`, one finding at a time.
+- **DO NOT** create, edit or delete any file under `crews/` with your own tools — not even to
+  "finish" a repair the script refused.
+- **DO NOT** reorder, renumber, add or remove steps here: that is `/opencrew edit`.
+- **DO NOT** touch `_opencrew/` or any other crew.
+- **DO NOT** delete the `.bak` copies: they belong to the user.

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

@@ -114,7 +114,7 @@ Before starting execution:
     briefing, the research or your own assumptions, the sources take precedence over them
     (as fontes valem sobre o briefing e a pesquisa) — and say so when it matters.
 
-2. Read `crews/{name}/pipeline/pipeline.yaml` for the pipeline definition
+2. Read `crews/{name}/pipeline/pipeline.yaml` for the pipeline definition. The format of the crew files — where each field lives and the older shapes that still count — is in `_opencrew/core/formato-da-crew.md`; read it when a field is not where you expect.
 3. **Resolve skills**: Read `crew.yaml` → `skills` section. For each non-native skill (anything other than web_search, web_fetch):
    a. Verify `skills/{skill}/SKILL.md` exists
       - If missing → ask user: "Skill '{skill}' is not installed. Install now? (y/n)"
@@ -124,13 +124,9 @@ Before starting execution:
    c. If type: mcp, verify MCP is configured in `.claude/settings.local.json`
       - If missing → **ERROR**: "Skill '{skill}' MCP not configured. Reinstall the skill."
    All skills must resolve successfully before the pipeline starts (fail fast).
-4. **Model tiers**: Individual steps declare their own `model_tier` in their frontmatter (`fast` or `powerful`), set by the Architect at crew creation time based on the crew's tier (Express/Standard/Full).
-   - Read `crew.yaml` → `crew.tier` field to understand the crew's depth level:
-     - `express`: all steps use `model_tier: fast` by default
-     - `standard`: mixed — research/data steps use `fast`, creative/review steps use `powerful`
-     - `full`: all steps use `model_tier: powerful` by default
-   - If a step has its own `model_tier` in frontmatter → step-level override takes priority over crew-level default.
-    - If neither crew tier nor step model_tier is set → default to `powerful` at dispatch.
+4. **Model tiers**: a `subagent` step declares its own `model_tier` (`fast` or `powerful`), set at crew creation by the crew's tier; inline steps carry none.
+   - Read the crew's tier for the run header: `crew.tier` in `crew.yaml` (older crews: `tier` loose at the top level).
+   - A subagent step with no `model_tier` → `powerful` at dispatch.
 
 4b. **Pre-Execution Agent Selection** — Decide which agents actually run for this task.
     Run this step ONLY if `crew.yaml` declares an `agent_dependencies:` field (even an
@@ -563,7 +559,7 @@ root the one-line command of each moment and read the last line (`CAMINHO:OK {pa
   Atualizo o perfil da empresa?" — change `company.md` only after a yes.
 - **If the step frontmatter contains `outputFile`**: after collecting the user's full response,
   insert only the run_id in the `outputFile` path (item 1 of the rule in Output Path Transformation — no version folder, no `saida` command), then write the response to that path using the Write tool (it creates the folder) before moving to the next step. Checkpoint files are user input captures, not versioned output: they live in the group itself, where `entrada` finds them.
-  Use this format:
+  For the checkpoint that precedes the researcher, use this format:
   ```
   # Research Focus
 
@@ -571,7 +567,8 @@ root the one-line command of each moment and read the last line (`CAMINHO:OK {pa
   **Time Range:** {selected time range label, e.g., "Últimos 7 dias"}
   **Date:** {today's date in YYYY-MM-DD format}
   ```
-  This file is the `inputFile` for the researcher step that follows.
+  For any other checkpoint: `# {the checkpoint's title}`, the user's answer as given (the option chosen and every comment), and `**Date:** {today, YYYY-MM-DD}`.
+  This file is the `inputFile` of the step that follows.
 
 ### Post-Step Output Validation
 
@@ -681,8 +678,8 @@ When a step has `on_reject: {step-id}` (a review step):
    (real data only the user has): do NOT reject for them — the reviewer judges the rest, and the
    final approval below collects the missing data from the user.
 3. Track the review cycle count: a **cycle** is one pass of the reviewer. The maximum is
-   `max_review_cycles`, an integer from 1 declared where the step declares `on_reject` (the step
-   frontmatter or its `pipeline.yaml` entry); absent or invalid: 3. On every rejection, with or
+   `max_review_cycles`, an integer from 1: the one declared where the step declares `on_reject` (the
+   step frontmatter or its `pipeline.yaml` entry); without it, the one in `crew.yaml`; absent or invalid in both: 3. On every rejection, with or
    without a block, send the reviewer's feedback to the writer and go back to the referenced step.
 4. If the last allowed pass also rejects, stop; the status of the last report picks the message, as
    in item 2 — `VERIFICACAO:BLOQUEADA`: the blocks; any other status: the reviewer's feedback, also