@aksp/opencrew 1.10.0 → 1.12.0

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 that must become a Word file to print, sign or file — ata, ofício, contrato, parecer — gets `documento-oficial`; a text with no channel that does not become a Word file (a plan, an internal report, a proposal or a draft that becomes HTML or PDF) gets `texto-livre`. When you cannot tell which of the two it is (a proposta, a minuta), ask first: "O texto do passo {n} precisa virar um arquivo Word para imprimir ou assinar?" — sim: `documento-oficial`; não: `texto-livre`. When the user refuses your proposal and says what the text is, propose once more with the right format. Then: "Estes passos não dizem que tipo de texto produzem; sem isso, o redator não recebe o guia do tipo de texto e o verificador procura no arquivo peças de rede. 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,23 +114,19 @@ 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)"
       - If yes → read `_opencrew/core/skills.engine.md`, follow Operation 2 (Install)
       - If no → **ERROR**: stop pipeline
    b. Read SKILL.md, parse frontmatter for type
-   c. If type: mcp, verify MCP is configured in `.claude/settings.local.json`
+   c. If type: mcp, verify the MCP server is configured in your IDE's MCP configuration (the project's `.mcp.json`, or the file your IDE uses)
       - 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
@@ -221,11 +217,11 @@ Before starting execution:
    ```
    When the selection step was skipped (no `agent_dependencies:` in crew.yaml), this is
    identical to today: all agents listed, no Skipped line.
-5b. **Initialize run folder**: Generate a unique run ID for this execution:
-   - Format: `YYYY-MM-DD-HHmmss` using the current timestamp (e.g. `2026-03-03-143022`)
-   - Check (folder-listing tool, no command) if `crews/{name}/output/{run_id}/` already exists
-     - If it does (sub-second collision), append `-2`, `-3`, etc. until the folder does not exist
-   - Create the folder: run the `pasta` command (see "Output Path Transformation" below) — never create a folder by command yourself
+5b. **Initialize run folder**: the script names the run — never build the date or the time yourself:
+   - Run the `pasta` command (see "Output Path Transformation" below). It creates the folder of this run and answers `CAMINHO:OK crews/{name}/output/{run_id}`
+   - The `run_id` is the last segment of that path: `YYYY-MM-DD-HHmmss` from the computer's clock (e.g. `2026-03-03-143022`; `-2`, `-3` when that folder already exists)
+   - The date of this run, wherever one is asked below, is the first 10 characters of the `run_id`
+   - Never create a folder by command yourself
    - Store `run_id` in working memory for this run — it will be used for ALL output paths
 6. **Escritório** — if it is on, run `iniciar`, then one `pular` per deselected agent, one after the other (see "Escritório" below).
 
@@ -234,7 +230,7 @@ Before starting execution:
 A local page that shows the crew at work, off by default. Follow this section only when the
 already-loaded `preferences.md` has `Dashboard: enabled` (written `- **Dashboard:** enabled` or
 plain `Dashboard: enabled`, any letter case); otherwise run none of these commands. When it is on,
-run via Bash, from the project root, the one-line command of each moment:
+run, from the project root, the one-line command of each moment:
 
 | Moment | Command |
 |---|---|
@@ -452,7 +448,7 @@ root the one-line command of each moment and read the last line (`CAMINHO:OK {pa
 
 | Moment | Command |
 |---|---|
-| Start of the run (Initialization, step 5b) | `node _opencrew/core/scripts/caminho.mjs "{name}" pasta --run "{run_id}"` |
+| Start of the run (Initialization, step 5b) | `node _opencrew/core/scripts/caminho.mjs "{name}" pasta` (no `--run`: the script creates the `run_id`) |
 | Before a step, for its `inputFile` | `node _opencrew/core/scripts/caminho.mjs "{name}" entrada --run "{run_id}" --arquivo "{inputFile}"` |
 | Before a step writes, for the first `outputFile` of each group | `node _opencrew/core/scripts/caminho.mjs "{name}" saida --run "{run_id}" --arquivo "{outputFile}"` |
 | After a step wrote, for each output file | `node _opencrew/core/scripts/caminho.mjs "{name}" conferir --arquivo "{path}"` |
@@ -480,7 +476,7 @@ root the one-line command of each moment and read the last line (`CAMINHO:OK {pa
   and reads `…/v1/pesquisa.md`. Never assume `v1`.
 - **Script that does not run** (no Node, an error, or no `CAMINHO:` line): tell the user once per
   run `Não consegui rodar a conferência de caminhos; sigo pela regra escrita e marco os arquivos como não verificados.`,
-  build the path by the rule above (the Write tool creates the folder) and continue. A file handled
+  build the path by the rule above (your file-writing tool creates the folder) and continue. A file handled
   this way skips its gate and is listed at the final approval:
   `{arquivo} — não verificado: a conferência de caminhos não rodou`.
 
@@ -522,10 +518,10 @@ root the one-line command of each moment and read the last line (`CAMINHO:OK {pa
 - Read the step's `model_tier` frontmatter field (if present).
   Valid values: `fast` or `powerful`. If absent or any other value: default to `powerful`.
 - **Before building the subagent prompt**: Resolve all output paths referenced in the step file with the `saida` command (Output Path Transformation, once per group). Store the transformed path(s) in working memory — they will be used both in the prompt and in post-completion verification. Never pass raw paths from the step file to the subagent.
-- Use the Task tool to dispatch the step as a subagent:
+- Dispatch the step with your IDE's subagent mechanism (an IDE without one: run the step inline, in this conversation):
   - If `model_tier: fast`: use the fastest/lightest model available in your current IDE.
   - If `model_tier: powerful` or absent/invalid: use the default model (no model override needed)
-- In the Task prompt, include:
+- In the subagent's prompt, include:
   - The full agent persona from the party CSV
   - The full agent `.agent.md` content (persona, principles, voice guidance, anti-patterns)
   - If the agent has tasks: include ALL task files in order with instructions to execute sequentially, piping output from each task to the next
@@ -562,16 +558,17 @@ root the one-line command of each moment and read the last line (`CAMINHO:OK {pa
   (e.g. the organization's name, the main audience), ask: "Isso vale para todas as crews?
   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:
+  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 with your file-writing 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.
+  For the checkpoint that precedes the researcher, use this format:
   ```
   # Research Focus
 
   **Topic:** {user's typed topic}
   **Time Range:** {selected time range label, e.g., "Últimos 7 dias"}
-  **Date:** {today's date in YYYY-MM-DD format}
+  **Date:** {the date of this run, YYYY-MM-DD}
   ```
-  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:** {the date of this run, YYYY-MM-DD}`.
+  This file is the `inputFile` of the step that follows.
 
 ### Post-Step Output Validation
 
@@ -602,7 +599,7 @@ After a step produces output (subagent or inline) and BEFORE Veto Condition Enfo
 - If the step does not declare an `outputFile` (e.g., steps that only produce inline console output) → skip output validation.
 - Checkpoint steps (`type: checkpoint`) are exempt — their output is the user's response, not a file.
 
-**IMPORTANT**: Do NOT rely on reading the file with the Read tool to "verify" output. The Read tool returns content that can be misinterpreted. Use ONLY the `conferir` command — its last line is binary and cannot be hallucinated.
+**IMPORTANT**: Do NOT rely on reading the file yourself to "verify" output: what you read can be misinterpreted. Use ONLY the `conferir` command — its last line is binary and cannot be hallucinated.
 
 ### Output Contract Validation
 
@@ -646,7 +643,7 @@ After an agent completes a step (before moving to the next step):
    - Check each condition (e.g., "slides exceed 30 words", "no CTA", "missing sources")
 3. If ANY veto condition is triggered:
    - Inform user: "⚠️ {Agent Name}'s output triggered a veto: {condition}"
-   - Ask the agent to fix the specific issue (re-execute with targeted correction)
+   - Ask the agent to fix the specific issue (re-execute with targeted correction), then run the `conferir` command on the rewritten file again (Post-Step Output Validation) before judging the veto once more
    - Maximum 2 veto fix attempts per step
    - After 2 failed attempts, present to user for manual decision
    - **Never auto-fix an irreversible step** (`side_effects: irreversible`): re-executing it
@@ -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
@@ -781,7 +778,7 @@ One script turns the approved files into `crews/{name}/output/{run_id}/entrega/`
    Then proceed to prepend the new row.
 
    Read `crews/{name}/_memory/runs.md`. Prepend one new row to the table (immediately after the header row), with:
-   - `Data`: today's date in YYYY-MM-DD format
+   - `Data`: the date of this run (the first 10 characters of the `run_id`)
    - `Run ID`: the `run_id` for this execution
    - `Tema`: the topic or user request from this run (1 sentence max)
    - `Output`: brief description of what was generated (e.g., "Carrossel 9 slides", "Thread 7 posts")

package/templates/_opencrew/core/scripts/caminho/argumentos.mjs

@@ -41,7 +41,9 @@ export function erroDeArgumentos({ crew, acao, run, arquivo, secoes }) {
   if (!crew) return 'Falta o nome da crew.';
   if (!acao) return `Falta a ação. Ações: ${LISTA}.`;
   if (!ACOES.includes(acao)) return `Ação desconhecida: ${limpar(acao)}. Ações: ${LISTA}.`;
-  if (acao !== 'conferir' && !run) return MSG.faltaOpcao('--run');
+  // `pasta` sem --run: o script dá o nome à execução (data e hora do computador).
+  if (acao !== 'conferir' && acao !== 'pasta' && !run) return MSG.faltaOpcao('--run');
+  if (run === '') return MSG.faltaOpcao('--run'); // `--run` sem valor não vira "sem --run"
   if (run !== undefined && !RUN.test(run)) return 'O --run só aceita letras, dígitos, ponto, sublinhado e hífen.';
   if (acao !== 'pasta' && !arquivo) return MSG.faltaOpcao('--arquivo');
   if (secoes !== undefined && !INTEIRO.test(secoes)) return 'O --secoes é um número inteiro a partir de 1.';

package/templates/_opencrew/core/scripts/caminho/nucleo.mjs

@@ -29,6 +29,22 @@ export function naExecucao(declarado, crew, run) {
   return { grupo: [`${saida}${run}`, ...partes].join('/'), nome };
 }
 
+const dois = (n) => String(n).padStart(2, '0');
+
+/**
+ * O nome de uma execução nova: `AAAA-MM-DD-HHmmss` na hora local; se já existe pasta com esse
+ * nome, `-2`, `-3`… (spec fase-u5a-polimento-do-uso.md, decisão 2).
+ * @param {Date} agora · @param {string[]} existentes as pastas que já estão em `output/`
+ */
+export function novoRun(agora, existentes) {
+  const base = `${agora.getFullYear()}-${dois(agora.getMonth() + 1)}-${dois(agora.getDate())}-${dois(agora.getHours())}${dois(agora.getMinutes())}${dois(agora.getSeconds())}`;
+  const usados = new Set(existentes);
+  for (let n = 1; ; n++) {
+    const nome = n === 1 ? base : `${base}-${n}`;
+    if (!usados.has(nome)) return nome;
+  }
+}
+
 /** O número de uma pasta de versão (`v` + número), ou `null` para qualquer outro nome. */
 function numero(nome) {
   const [, digitos] = /^v(\d{1,9})$/.exec(nome) ?? [];

package/templates/_opencrew/core/scripts/caminho.mjs

@@ -2,7 +2,8 @@
 // Caminho da execução de uma crew: diz onde cada passo grava, de onde lê e se o arquivo gravado
 // está lá. Quem calcula é este script, igual em qualquer sistema — a IA não monta o caminho.
 // Uso (na pasta do projeto): node _opencrew/core/scripts/caminho.mjs <crew> <ação> --run <id> [opções]
-//   pasta    --run <id>                       cria crews/<crew>/output/<id>/
+//   pasta    [--run <id>]                     cria crews/<crew>/output/<id>/; sem --run, o id é a
+//                                             data e a hora do computador (AAAA-MM-DD-HHmmss)
 //   saida    --run <id> --arquivo <declarado> onde o passo grava (abre a pasta de versão seguinte)
 //   entrada  --run <id> --arquivo <declarado> a saída mais nova desse arquivo
 //   conferir --arquivo <caminho já resolvido> [--secoes N] [--tldr]
@@ -17,7 +18,7 @@
 import path from 'node:path';
 import { MSG, dentroDoProjeto, ehPrincipal, realDentroDe } from './comum.mjs';
 import { USO, erroDeArgumentos, lerArgs, limpar } from './caminho/argumentos.mjs';
-import { MOTIVO, daMaisNova, motivoDeReprovacao, naExecucao, normalizar, proximaVersao } from './caminho/nucleo.mjs';
+import { MOTIVO, daMaisNova, motivoDeReprovacao, naExecucao, normalizar, novoRun, proximaVersao } from './caminho/nucleo.mjs';
 import { criarPasta, ehPasta, lerTexto, pastasDe, temConteudo } from './caminho/disco.mjs';
 
 const ok = (caminho) => `CAMINHO:OK ${caminho}`;
@@ -31,7 +32,8 @@ const reprovado = (motivo) => `CAMINHO:REPROVADO ${motivo}`;
  */
 function erroDoArquivo(raiz, crew, { acao, run, arquivo }) {
   if (!dentroDoProjeto(raiz, arquivo)) return MSG.foraDoProjeto(limpar(arquivo));
-  const local = acao === 'conferir' ? null : naExecucao(arquivo, crew, run);
+  // `pasta` não usa arquivo, e `conferir` recebe o caminho já resolvido: nenhum dos dois o põe na execução.
+  const local = acao === 'conferir' || acao === 'pasta' ? null : naExecucao(arquivo, crew, run);
   if (!local) return null;
   if (!local.nome) return `Falta o nome do arquivo em --arquivo: ${limpar(arquivo)}`;
   const execucao = path.resolve(raiz, 'crews', crew, 'output', run);
@@ -88,23 +90,24 @@ function conferir(raiz, { arquivo, secoes, tldr }) {
   return motivo ? reprovado(motivo) : ok(caminho);
 }
 
-function responder(raiz, crew, args) {
+function responder(raiz, crew, args, agora) {
   if (args.acao === 'saida') return saida(raiz, crew, args);
   if (args.acao === 'entrada') return entrada(raiz, crew, args);
   if (args.acao === 'conferir') return conferir(raiz, args);
-  const pasta = `crews/${crew}/output/${args.run}`;
+  const run = args.run || novoRun(agora(), pastasDe(path.resolve(raiz, 'crews', crew, 'output')));
+  const pasta = `crews/${crew}/output/${run}`;
   criarPasta(path.resolve(raiz, pasta));
   return ok(pasta);
 }
 
 /**
  * @param {string[]} argv
- * @param {object} [deps] `cwd` (a pasta do projeto) e `escrever`
+ * @param {object} [deps] `cwd` (a pasta do projeto), `escrever` e `agora` (o relógio, para o id da execução)
  * @returns {number} 0 = a linha `CAMINHO:` saiu · 1 = erro de uso, ou falha ao ler ou criar pasta
  *   (a linha de uso e o motivo, ou só o erro; sem linha `CAMINHO:`)
  */
 export function main(argv, deps = {}) {
-  const { cwd = process.cwd(), escrever = (s) => process.stdout.write(`${s}\n`) } = deps;
+  const { cwd = process.cwd(), escrever = (s) => process.stdout.write(`${s}\n`), agora = () => new Date() } = deps;
   const args = lerArgs(argv);
   const local = localizar(cwd, args);
   if (local.erro) {
@@ -113,7 +116,7 @@ export function main(argv, deps = {}) {
     return 1;
   }
   try {
-    escrever(responder(cwd, local.crew, args));
+    escrever(responder(cwd, local.crew, args, agora));
     return 0;
   } catch (erro) {
     escrever(`Não consegui resolver o caminho: ${limpar(erro?.message ?? erro)}`);

package/templates/_opencrew/core/scripts/conferir-fontes/relatorio.mjs

@@ -7,7 +7,8 @@ const plural = (n, um, varios) => `${n} ${n === 1 ? um : varios}`;
 
 export const MSG = {
   nadaACorrigir: 'Nada a corrigir.',
-  corrigidos: (n) => `${plural(n, 'caminho corrigido', 'caminhos corrigidos')} (cópia .bak ao lado de cada arquivo alterado).\n`,
+  corrigido: (arquivo, copia) => `Corrigi: ${arquivo} (cópia: ${copia})`,
+  comoCorrigir: 'Para trocar os caminhos que têm sugestão, rode de novo com --corrigir (cada arquivo alterado ganha uma cópia).',
   semCorrecaoAutomatica: (n) => `Não há correção automática para ${n} pendência(s): escolha um candidato ou corrija o caminho na crew.`,
   buscaParcial: (limite) => `Procurei só nos primeiros ${limite} itens do projeto; pode existir um arquivo com esse nome que eu não vi.`,
   linkParaFora: (arquivo) => `Não corrigi \`${arquivo}\`: é um link que aponta para fora da crew. O caminho citado nele continua como estava.`,
@@ -59,6 +60,7 @@ export function formatar(r) {
   }
   if (apontados.length) linhas.push(''); // sem pendência nem alerta, uma linha em branco só
   const alertas = contar('nao-portatil') + contar('nao-conferido');
-  linhas.push(`**Resumo: ${r.refs.length} fontes — ${contar('ok')} ok, ${contar('faltando')} pendentes, ${alertas} alertas**`, '');
+  const pendentes = contar('faltando');
+  linhas.push(`**Resumo: ${plural(r.refs.length, 'fonte', 'fontes')} — ${contar('ok')} ok, ${plural(pendentes, 'pendente', 'pendentes')}, ${plural(alertas, 'alerta', 'alertas')}**`, '');
   return linhas.join('\n');
 }

package/templates/_opencrew/core/scripts/conferir-fontes.mjs

@@ -87,18 +87,17 @@ export async function conferir({ raiz, crew, limite = LIMITE_DA_BUSCA }) {
   return { crew, raiz, refs, status, buscaParcial: Boolean(ctx.indice?.parcial), limite };
 }
 
+/** @returns {Promise<string>} o caminho da cópia que ficou */
 async function copiaDeSeguranca(arquivo) {
   const bak = existsSync(`${arquivo}.bak`) ? `${arquivo}.bak-${new Date().toISOString().replace(/[:.]/g, '-')}` : `${arquivo}.bak`;
   await copyFile(arquivo, bak);
+  return bak;
 }
 
-/** Regrava a citação num arquivo; a cópia .bak é feita uma vez por arquivo. */
+/** Regrava a citação num arquivo; a cópia .bak é feita uma vez por arquivo (`tocados`: arquivo → cópia). */
 async function regravar(arquivo, item, tocados) {
   const texto = await readFile(arquivo, 'utf8');
-  if (!tocados.has(arquivo)) {
-    await copiaDeSeguranca(arquivo);
-    tocados.add(arquivo);
-  }
+  if (!tocados.has(arquivo)) tocados.set(arquivo, await copiaDeSeguranca(arquivo));
   await writeFile(arquivo, trocarCitacao(texto, item, path.basename(arquivo) === 'crew.yaml'));
 }
 
@@ -118,9 +117,10 @@ function guardaDeEscrita(raiz, crew) {
  * Troca, nos arquivos da crew, cada caminho com sugestão única — só a citação que a coleta leu,
  * nunca um pedaço de outro texto. O que a guarda de escrita barra não muda: `avisar` recebe uma
  * linha por arquivo pulado, ou uma só quando a crew inteira é um link para fora do projeto.
+ * `gravado` recebe cada arquivo alterado e a cópia que ficou dele.
  * @returns quantos caminhos foram gravados, em ao menos um arquivo
  */
-export async function corrigir({ resultado, avisar = () => {} }) {
+export async function corrigir({ resultado, avisar = () => {}, gravado = () => {} }) {
   const { raiz, crew } = resultado;
   const comSugestao = resultado.refs.filter((i) => i.sugestao && i.estado !== 'ok');
   const podeGravar = comSugestao.length ? guardaDeEscrita(raiz, crew) : null;
@@ -128,7 +128,7 @@ export async function corrigir({ resultado, avisar = () => {} }) {
     if (comSugestao.length) avisar(MSG.crewLigadaParaFora(crew));
     return 0;
   }
-  const tocados = new Set();
+  const tocados = new Map();
   const pulados = new Set();
   let gravados = 0;
   for (const item of comSugestao) {
@@ -138,19 +138,22 @@ export async function corrigir({ resultado, avisar = () => {} }) {
     if (dentro.length) gravados += 1;
   }
   for (const arquivo of pulados) avisar(MSG.linkParaFora(relativoAoProjeto(raiz, arquivo)));
+  for (const [arquivo, copia] of tocados) gravado(relativoAoProjeto(raiz, arquivo), path.basename(copia));
   return gravados;
 }
 
-/** --corrigir: troca o que tem sugestão única, diz o que pulou e quantas pendências ficam sem correção. */
+/**
+ * --corrigir: troca o que tem sugestão única e diz cada arquivo alterado, com a cópia; o relatório
+ * sai uma vez só — o de depois, quando algo mudou. Diz também o que pulou e o que ficou sem correção.
+ */
 async function corrigirEAvisar(r, escrever) {
   const pulados = [];
-  const n = await corrigir({ resultado: r, avisar: (linha) => pulados.push(linha) });
-  let atual = r;
-  if (n) {
-    escrever(MSG.corrigidos(n));
-    atual = await conferir({ raiz: r.raiz, crew: r.crew });
-    escrever(formatar(atual));
-  }
+  const feitos = [];
+  const n = await corrigir({ resultado: r, avisar: (linha) => pulados.push(linha), gravado: (arquivo, copia) => feitos.push(MSG.corrigido(arquivo, copia)) });
+  const atual = n ? await conferir({ raiz: r.raiz, crew: r.crew }) : r;
+  for (const linha of feitos) escrever(linha);
+  if (n) escrever('');
+  escrever(formatar(atual));
   for (const linha of pulados) escrever(linha);
   const semSugestao = atual.refs.filter((i) => i.estado === 'faltando' && !i.sugestao).length;
   if (semSugestao) escrever(MSG.semCorrecaoAutomatica(semSugestao));
@@ -177,8 +180,11 @@ export async function main(argv, { cwd = process.cwd(), escrever = (s) => proces
   }
   try {
     let r = await conferir({ raiz: cwd, crew });
-    escrever(formatar(r));
     if (argv.includes('--corrigir')) r = await corrigirEAvisar(r, escrever);
+    else {
+      escrever(formatar(r));
+      if (r.refs.some((i) => i.sugestao && i.estado !== 'ok')) escrever(MSG.comoCorrigir);
+    }
     escrever(`FONTES:${r.status}`);
     return 0;
   } catch (erroDeLeitura) {