@semacode/cli 2.3.0 → 3.0.0

package/dist/agentEntryPoints.js

@@ -1,5 +1,5 @@
-// SEMA-GOVERNED: sema.produto.governanca_ia.contexto.entrypoints, sema.produto.escrita_segura_workspace
-// Descrição: sincroniza o entrypoint Codex com marcadores estritos e escrita contida no workspace.
+// SEMA-GOVERNED: sema.produto.governanca_ia.contexto.entrypoints, sema.produto.escrita_segura_workspace, sema.produto.governanca_ia.drift.cache.modos
+// Descrição: sincroniza o protocolo Codex, incluindo a distinção entre contexto contratual e evidência fresh de drift.
 import { readFile, rm, rmdir, stat } from 'node:fs/promises';
 import path from 'node:path';
 import { escreverArquivoWorkspaceSeguro, validarDestinosEscritaWorkspace, } from './workspaceWrite.js';
@@ -146,13 +146,13 @@ Você está em um projeto governado por Sema. O contrato semântico vem antes de
 
 ## Primeira ação
 
-1. Confirme \`AGENTS.md\` na raiz e rode \`sema --version\`; se o comando não existir, pare e peça a instalação da CLI.
-2. Use a CLI local diretamente para ler o workspace: \`sema resumo\`, \`sema docs-impacto\`, \`sema inspecionar\`, \`sema drift\` e \`sema impacto\`.
+1. Confirme \`AGENTS.md\` na raiz e rode \`sema --version\`. Se o shell não localizar o comando, use \`$HOME/.sema/bin/sema\` no macOS/Linux; no Windows, PowerShell usa \`sema.ps1\` no PATH, cmd.exe usa \`sema.cmd\`, e o fallback absoluto é \`& "$env:SystemRoot\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$HOME\\.sema\\bin\\sema-managed.ps1" --version\`. Só então declare a CLI indisponível.
+2. Use a CLI local diretamente para ler o workspace: \`sema resumo --drift none\`, \`sema docs-impacto\`, \`sema inspecionar --drift none\`, \`sema drift --cache fresh\` e \`sema impacto\`. Na 3.0.0, \`sema --version\` continua texto SemVer exato; com \`--json\`, help e falhas de controle usam \`sema.cli.control/v1\`, enquanto comandos sintaticamente válidos usam o envelope exato de oito campos \`sema.cli.result/v1\`, com o resultado aninhado em \`payload\` e \`ok\` separado do veredito de domínio desse payload.
 3. Se não estiver claro qual profile, workflow, pipeline, gerador ou adapter usar, rode \`sema descobrir recomendar --intencao "<objetivo>" --json\`; não execute automaticamente uma recomendação ambígua.
 4. Não use fonte externa de workspace para substituir a CLI local quando ela estiver operacional.
 5. Este boot é para workspace local em disco; se não houver workspace local, pare bloqueado em vez de inventar caminho.
 6. Antes de criar módulo, rota, task ou contrato, inspecione o contrato \`.sema\` aplicável.
-7. Antes de editar código existente, rode drift e impacto pela CLI local.
+7. Antes de editar código existente, rode \`sema drift --cache fresh\` e impacto pela CLI local.
 8. Antes de criar ou corrigir \`.sema\`, use os exemplos oficiais na CLI local.
 9. Se qualquer etapa falhar, pare e diga que está bloqueado.
 
@@ -197,7 +197,10 @@ Score composto, \`achados[]\` e \`decisaoAgente\` são sinais para guiar a próx
 - Fraca: se o score passou, confira se cada achado tem evidência concreta; se não souber provar, pare.
 - Média: conecte regra, arquivo, contrato e evidência antes de concluir aderência.
 - Forte: não transforme regex, palavra-chave ou score 100 em ritual vazio; valide substância, risco e comportamento.
-- Fechamento governado: se \`sema drift --json\` retornar \`sucesso:false\`, \`vinculos_quebrados\`, \`rotas_divergentes\` ou impls quebradas, não diga que passou limpo. Corrija e rode drift de novo.
+- Consultas honestas: \`resumo\` e \`inspecionar\` usam \`--drift none\` por padrão; score, confiança, implementação, rotas e superfícies não observadas ficam nulos/não avaliados.
+- Se uma consulta executar drift explicitamente, \`payload.analiseDrift.sucesso\` expõe o resultado e uma falha solicitada retorna exit code diferente de zero.
+- Cache: \`sema drift\` usa \`fresh\` por padrão. \`--cache none\` ainda executa sem persistência; \`cache\` acelera extrações validadas, mas não é prova final.
+- Fechamento governado: se o \`payload\` de \`sema drift --cache fresh --json\` retornar \`sucesso:false\`, \`vinculos_quebrados\`, \`rotas_divergentes\` ou \`impls_quebrados\`, não diga que passou limpo. Corrija e rode drift de novo.
 - Experiência governada: se a tarefa cria ou altera site, sistema, app, UI, painel, jogo, CLI/TUI ou terminal, prove acabamento moderno, contextual e não genérico. Em UI estreita (ex. 390px), \`document.documentElement.scrollWidth <= document.documentElement.clientWidth\` precisa ser verdadeiro.
 - Caminho fora do workspace local aberto pelo usuário não substitui a pasta local.
 
@@ -245,7 +248,7 @@ export function renderizarSemaSmallModel(agentContextPack) {
 Leia isto primeiro se você tem pouco contexto, pouca memória, pouco tool use ou tendência a ignorar instruções longas.
 
 1. Não edite nada antes de chamar Sema.
-2. Em workspace local, rode \`sema --version\`; se falhar, pare e peça a instalação da CLI. Com a CLI disponível, opere diretamente sobre a pasta local e não use espelho externo.
+2. Em workspace local, rode \`sema --version\`; se o shell falhar, use \`$HOME/.sema/bin/sema\` no macOS/Linux. No Windows, PowerShell usa \`sema.ps1\` no PATH e cmd.exe usa \`sema.cmd\`; o fallback absoluto é \`& "$env:SystemRoot\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$HOME\\.sema\\bin\\sema-managed.ps1" --version\`. Só então pare e peça instalação ou reparo.
 3. Sema não contorna políticas da plataforma: ele governa contrato, escopo, drift, evidência e qualidade.
 4. Se aparecer alerta de política: pare, explique de forma neutra e não tente burlar filtro.
 5. Se não houver workspace local em disco: pare bloqueado e peça o fluxo apropriado; não invente leitura por caminho.
@@ -261,7 +264,7 @@ Leia isto primeiro se você tem pouco contexto, pouca memória, pouco tool use o
 15. Payload inline acima de ${LIMITE_CARACTERES_PAYLOAD_INLINE} caracteres não é lentidão: divida por responsabilidade; não aumente timeout para tentar passar limite de transporte.
 16. Se aparecer caminho que não pertence ao workspace local aberto pelo usuário, pare e confirme a fonte antes de agir.
 17. Se Sema estourar por timeout local: aumente o timeout e tente de novo. Não trate isso como falha do Sema.
-18. Se \`sema drift --json\` retornar \`sucesso:false\`, \`vinculos_quebrados\`, \`rotas_divergentes\` ou impl quebrada, não conclua. Corrija contrato/código e rode drift de novo.
+18. Para fechamento, rode \`sema drift --cache fresh --json\`; cache persistente só acelera navegação e não é prova final. Se o \`payload\` retornar \`sucesso:false\`, \`vinculos_quebrados\`, \`rotas_divergentes\` ou \`impls_quebrados\`, não conclua. Na 3.0.0, não procure campos de domínio no topo do envelope \`sema.cli.result/v1\` nem use \`ok\` como substituto do veredito do payload.
 19. Se a tarefa tiver site, sistema, app, UI, painel, jogo, CLI/TUI ou terminal: aplique acabamento moderno, contextual, responsivo/ergonômico, com hierarquia clara, estados e evidência. Em UI, valide mobile/desktop e prove \`scrollWidth <= clientWidth\` em viewport estreito como 390px.
 20. Não substitua o contexto Sema por AGENTS.md, README.md, busca local, inferência por nome ou bom senso.
 
@@ -284,7 +287,7 @@ Timeout:
 - Timeout local do agente não é falha do Sema.
 - Projeto inteiro: comece com ${politicaTimeout.timeoutInicialSegundos}s ou mais.
 - Escalonamento: ${politicaTimeout.escalonamentoSegundos.map((segundos) => `${segundos}s`).join(" -> ")}.
-- Se o projeto inteiro for lento, escopar para \`sema resumo <arquivo.sema> --micro --para mudanca\`.
+- Se o projeto inteiro for lento, escopar para \`sema resumo <arquivo.sema> --micro --para mudanca --drift none\`.
 - ${politicaTimeout.ateQuandoTentar}
 
 Acabamento visual e terminal:
@@ -315,18 +318,22 @@ export function renderizarDocumentoAgentesPorCapacidade(agentContextPack) {
         "",
         "## Before AGENTS.md Exists",
         "",
-        "The official Sema skill is the required first-contact bootstrap for Codex in a",
-        "project that does not have Sema yet. Install it explicitly:",
+        "The official Sema skill is the first-contact bootstrap for a project that does",
+        "not have Sema yet. A global CLI install bundles and synchronizes it:",
         "",
         "```bash",
-        "codex plugin marketplace add gerlanss/Sema",
-        "codex plugin add sema@sema",
+        "npm install -g @semacode/cli",
+        "sema skill status --json",
         "```",
         "",
-        "The skill locates the local CLI, runs `sema iniciar`, generates `AGENTS.md`, and",
-        "then delegates all ongoing workspace governance to that file. It contains no",
+        "The package creates an absolute launcher under `~/.sema/bin`, synchronizes the",
+        "canonical skill under `~/.agents/skills/sema`, and mirrors Claude only when",
+        "detected. Informational requests stay read-only; before implementation the skill asks",
+        "for explicit project-adoption authorization, then generates `AGENTS.md` and delegates",
+        "ongoing governance. Installing or updating the global CLI authorizes distribution only.",
+        "Already-open tasks may need a reload. The distribution contains no",
         "MCP server, remote workspace bridge, login, license, billing, token, credit,",
-        "panel, or authorization gate.",
+        "panel, or runtime authorization gate.",
         "",
         `Supported capacity labels: ${supportedCapacities}.`,
         "",
@@ -336,10 +343,11 @@ export function renderizarDocumentoAgentesPorCapacidade(agentContextPack) {
         "",
         "```bash",
         "sema --version",
-        "sema resumo",
+        "sema resumo --drift none",
         "```",
         "",
-        "A successful `sema --version` is enough to use the local CLI directly. Local",
+        "If the shell cannot resolve `sema`, use `~/.sema/bin/sema` on macOS/Linux. On Windows, PowerShell uses `sema.ps1` from PATH and cmd.exe uses `sema.cmd`; use `& \"$env:SystemRoot\\System32\\WindowsPowerShell\\v1.0\\powershell.exe\" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File \"$HOME\\.sema\\bin\\sema-managed.ps1\" --version` as the absolute fallback",
+        "before declaring the CLI unavailable. A successful version check is enough. Local",
         "commands require no login, activation key, license check, token, credits, billing",
         "service, control panel, or external authorization request.",
         "",
@@ -347,13 +355,15 @@ export function renderizarDocumentoAgentesPorCapacidade(agentContextPack) {
         "",
         "```bash",
         "sema docs-impacto --intencao \"describe the change\" --json",
-        "sema inspecionar contratos/example.sema --json",
-        "sema drift contratos/example.sema --escopo modulo --json",
+        "sema inspecionar contratos/example.sema --drift none --json",
+        "sema drift contratos/example.sema --escopo modulo --cache fresh --json",
         "sema impacto contratos/example.sema --alvo app.example --mudanca \"describe the change\" --json",
         "```",
         "",
         "Read every document listed by `docs-impacto` before changing code, contracts,",
         "operational docs, generated artifacts, workflows, profiles, or release material.",
+        "A cache hit is acceleration, not evidence: closing requires `--cache fresh`,",
+        "while contract-only queries keep unobserved implementation fields null inside the command payload.",
         "",
         "## Codex Context Tiers",
         "",
@@ -430,13 +440,13 @@ function renderizarInstrucaoCodexSema(agentContextPack) {
 Este workspace é governado por Sema. Antes de qualquer ação em código, contrato, documentação operacional, workflow, profile ou deploy:
 
 1. Leia \`${ARQUIVO_SEMA_BOOT}\`.
-2. Rode \`sema --version\`; se falhar, pare e peça a instalação da CLI.
-3. Use diretamente a CLI local: \`sema resumo\`, \`sema docs-impacto\`, \`sema inspecionar\`, \`sema drift\` e \`sema impacto\`.
+2. Rode \`sema --version\`; se o shell falhar, use \`$HOME/.sema/bin/sema\` no macOS/Linux. No Windows, PowerShell usa \`sema.ps1\` no PATH e cmd.exe usa \`sema.cmd\`; use \`& "$env:SystemRoot\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$HOME\\.sema\\bin\\sema-managed.ps1" --version\` como fallback absoluto. Só então pare e peça instalação ou reparo.
+3. Use diretamente a CLI local: \`sema resumo --drift none\`, \`sema docs-impacto\`, \`sema inspecionar --drift none\`, \`sema drift --cache fresh\` e \`sema impacto\`. Na 3.0.0, \`sema --version\` continua texto SemVer exato; com \`--json\`, help e falhas de controle usam \`sema.cli.control/v1\`, enquanto comandos sintaticamente válidos usam o envelope exato de oito campos \`sema.cli.result/v1\`, com resultado em \`payload\` e \`ok\` distinto do veredito de domínio do payload.
 4. Quando a capacidade correta não estiver clara, use \`sema descobrir recomendar --intencao "<objetivo>" --json\`; não autoexecute resultado ambíguo.
 5. Não use fonte externa de workspace para substituir a CLI local quando ela estiver operacional.
 6. Chame docs-impacto com a intenção declarada antes de agir.
 7. Chame inspecionar no contrato \`.sema\` aplicável.
-8. Antes de editar código existente, rode drift e impacto.
+8. Antes de editar código existente, rode \`sema drift --cache fresh\` e impacto.
 9. Antes de criar ou editar \`.sema\`, use exemplos oficiais.
 10. Ao concluir mudança de contrato, rode validar.
 11. Antes de finalizar, use finalizar-mudanca com as docs lidas.
@@ -459,7 +469,7 @@ Timeout:
 - Timeout local do agente não é falha do Sema.
 - Se uma chamada Sema estourar, aumente o timeout e tente de novo antes de declarar bloqueio.
 - Para projeto inteiro, comece com ${politicaTimeout.timeoutInicialSegundos}s ou mais; se for lento, escale ${politicaTimeout.escalonamentoSegundos.map((segundos) => `${segundos}s`).join(" -> ")}.
-- Se possível, reduza escopo para \`sema resumo <arquivo.sema> --micro --para mudanca\`.
+- Se possível, reduza escopo para \`sema resumo <arquivo.sema> --micro --para mudanca --drift none\`.
 
 Código governado:
 - Mantenha o marcador \`${agentContextPack.politicaCodigoGovernado.marcador}\` em código gerado ou governado.
@@ -472,7 +482,8 @@ Código governado:
 Sinal e evidência:
 - Score composto, \`achados[]\` e \`decisaoAgente\` orientam a ação; abaixo de 80 bloqueia, alvo evolui 0.5 ponto até 100, e nada substitui evidência concreta.
 - Palavra-chave ou regex passando não prova governança se contrato, código e comportamento não batem.
-- \`sema drift --json\` com \`sucesso:false\`, \`vinculos_quebrados\`, \`rotas_divergentes\` ou impls quebradas bloqueia fechamento. Não diga "drift limpo" até rodar de novo e ficar verde.
+- \`resumo\` e \`inspecionar\` usam \`--drift none\` por padrão; campos derivados nulos significam não avaliados, nunca zero.
+- \`sema drift --cache fresh --json\` com \`payload.sucesso:false\`, \`payload.vinculos_quebrados\`, \`payload.rotas_divergentes\` ou \`payload.impls_quebrados\` bloqueia fechamento. Cache persistente é aceleração, não prova final.
 - Caminho fora do workspace local aberto pelo usuário não substitui a pasta local.
 
 Acabamento visual e terminal:
@@ -624,20 +635,26 @@ function renderizarDocFluxoPraticoSemaLocal(_agentContextPack) {
 This is the minimum workflow for Codex in a local workspace.
 
 1. Read \`${ARQUIVO_SEMA_BOOT}\`.
-2. Run \`sema --version\`. Success enables direct local execution; there is no login, license, token, billing, panel, or authorization gate.
-3. Run \`sema resumo\`.
+2. Run \`sema --version\`. If the shell cannot find it, use \`$HOME/.sema/bin/sema\` on macOS/Linux. On Windows, PowerShell resolves \`sema.ps1\` from PATH and cmd.exe resolves \`sema.cmd\`; use \`& "$env:SystemRoot\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$HOME\\.sema\\bin\\sema-managed.ps1" --version\` as the absolute fallback. Only then declare the CLI unavailable.
+3. Run \`sema resumo --drift none\` for contract-only orientation; request \`--drift cache\` or \`--drift fresh\` only when code evidence is needed.
 4. Run \`sema docs-impacto --intencao "<change>" --json\`.
 5. Read every required document returned by the command.
 6. Read \`docs/commands.md\` before selecting a command or interpreting \`--saida\`.
 7. If the right capability is unclear, run \`sema descobrir recomendar --intencao "<goal>" --json\`; do not auto-run ambiguous recommendations.
 8. Use \`exemplos/\` and \`docs/syntax.md\` before creating or editing a contract.
-9. Run \`sema drift\` and \`sema impacto\` before editing existing code.
+9. Run \`sema drift --cache fresh\` and \`sema impacto\` before editing existing code.
 10. Run \`sema formatar\` and \`sema validar\` after changing a \`.sema\` contract.
 11. Run \`sema finalizar-mudanca\` with the documents read before closure.
 
 Contract edit rule: \`.sema\` has its own size budget. Above ${LIMITE_AVISO_LINHAS_CONTRATO_SEMA} lines, plan a split by domain/capability; above ${LIMITE_BLOQUEIO_LINHAS_CONTRATO_SEMA}, do not create or edit before splitting. Do not use parte_1/parte_2 and do not force a 1:1 contract-to-file relationship; several contracts can govern the same file through \`vinculos\`.
 
-Closing rule: \`sema drift --json\` must return \`sucesso:true\`. If it reports \`sucesso:false\`, \`vinculos_quebrados\`, \`rotas_divergentes\`, or broken impls, the task is still blocked. Passing unit tests do not replace green drift.
+Closing rule: the \`payload\` of \`sema drift --cache fresh --json\` must return \`sucesso:true\`. If it reports \`sucesso:false\`, \`vinculos_quebrados\`, \`rotas_divergentes\`, or \`impls_quebrados\`, the task is still blocked. Passing unit tests or a cache hit do not replace fresh green drift. In 3.0.0, \`ok\` describes the CLI result path and never replaces a command-specific domain verdict.
+
+Focused drift rule: file and module scopes plan their physical file set before cataloging. They never fall back to a whole-project walk when no safe anchor exists. All indexers and semantic-budget checks reuse the same in-memory source read; a global walk is reserved for explicit \`--escopo projeto\`. Code discovery is deferred until that plan exists, homonymous candidates fail as ambiguous, and configured contract origins or code roots resolving outside the workspace are rejected before enumeration. \`inspecionar\`, \`impacto\`, and \`renomear-semantico\` preserve the same directed boundary. Missing local dependencies make coverage partial and block success.
+
+Cache rule: a closure gate should use \`sema drift <contrato> --escopo modulo --cache fresh --json\`. \`--cache none\` executes the same analysis without persistent-cache I/O, while \`--cache cache\` may reuse only extraction data whose schema, workspace identity, Git HEAD, plan, configuration, contracts, member paths, and strong content digests all match. Cache objects are stored in the operating system's user-cache directory, never below the workspace. A hit is acceleration, not evidence: final links, diagnostics, score, and success are always recalculated. Corruption or an unavailable cache degrades to an in-memory calculation.
+
+Query honesty rule: \`resumo\` and \`inspecionar\` default to \`--drift none\`. When analysis is skipped, score, confidence, implementation, routes, and other unobserved code claims inside the command payload must be \`null\` or explicitly marked not evaluated; zero is not a substitute for absent evidence.
 
 UI rule: if the task involves an interface, minimum evidence includes desktop and mobile. On a narrow viewport such as 390px, \`document.documentElement.scrollWidth <= document.documentElement.clientWidth\` must pass; horizontal scroll blocks closure.
 
@@ -673,20 +690,31 @@ Use this file when Codex does not know which command to run. A Sema command is a
 ## Minimum Local Flow
 
 \`\`\`bash
-sema --version
-sema resumo
-sema docs-impacto --intencao "<acao>" --json
-\`\`\`
-
-Then read every required doc returned by \`docs-impacto\`.
+sema --version
+sema resumo --drift none
+sema docs-impacto --intencao "<acao>" --json
+\`\`\`
+
+If \`sema\` is absent from \`PATH\`, use \`$HOME/.sema/bin/sema\` on macOS/Linux. On Windows, PowerShell resolves \`sema.ps1\` from PATH, cmd.exe resolves \`sema.cmd\`, and the absolute fallback is \`& "$env:SystemRoot\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$HOME\\.sema\\bin\\sema-managed.ps1" --version\`. \`sema skill sync --json\` repairs launcher and skill without touching the workspace or plugin caches.
 
-## Contract and Discovery
+Then read every required doc returned by \`docs-impacto\`.
+
+## Public JSON output
+
+\`sema --version\` stays plain exact SemVer text. With \`--json\`, help and command-control failures use exactly one six-field \`sema.cli.control/v1\` document on stdout with empty stderr. Every syntactically valid command uses exactly one eight-field \`sema.cli.result/v1\` document containing only \`schemaVersion\`, \`ok\`, \`kind\`, \`command\`, \`code\`, \`message\`, \`exitCode\`, and \`payload\`. The command-specific result is nested under \`payload\`, never \`data\`; envelope \`ok\` does not replace domain fields inside that payload. Valid structured domain failures use \`DOMAIN_ERROR\`, while uncaught runtime exceptions remain redacted \`FATAL_ERROR\` control failures.
+
+## Global Distribution
+
+- \`sema skill status --json\`: diagnoses the managed launcher and bundled skill without writing.
+- \`sema skill sync --json\`: repairs only Sema-managed launcher and skill destinations; it never writes into the workspace or plugin caches.
+
+## Contract and Discovery
 
 - \`sema iniciar --template <template> [--force]\`: creates a new Sema project and preserves existing files by default; \`--force\` is the only explicit overwrite path.
 - \`sema validar <arquivo-ou-pasta> --json\`: validates \`.sema\` contracts.
 - \`sema diagnosticos <arquivo.sema> --json\`: details errors and warnings.
 - \`sema formatar <arquivo-ou-pasta>\`: formats contracts.
-- \`sema inspecionar <arquivo-ou-pasta> --json\`: shows modules, tasks, routes, entities, links, and expected files.
+- \`sema inspecionar <arquivo-ou-pasta> [--drift <none|cache|fresh>] --json\`: shows the contract surface; drift is skipped by default.
 - \`sema ast <arquivo.sema> --json\`: shows AST for syntax debugging.
 - \`sema ir <arquivo.sema> --json\`: shows the IR used by gates and generators.
 - \`sema descobrir catalogo --json\`: lists governance flows, profiles, specialized workflows, pipelines, generators, capability tokens, and adapters from their canonical registries.
@@ -697,12 +725,24 @@ Then read every required doc returned by \`docs-impacto\`.
 ## Change and Closure
 
 - \`sema docs-impacto --intencao "<acao>" --json\`: discovers required docs and documentary blockers.
-- \`sema drift <arquivo-ou-pasta> --escopo modulo --json\`: compares contract and implementation.
+- \`sema drift <arquivo-ou-pasta> --escopo modulo [--cache <none|cache|fresh>] --json\`: plans a safe physical scope, then compares contract and implementation without a global fallback.
 - \`sema impacto <arquivo-ou-pasta> --alvo <token> --mudanca "<descricao>" --json\`: maps impact before changing behavior.
 - \`sema verificar <arquivo-ou-pasta> --json\`: runs aggregated final verification.
 - \`sema finalizar-mudanca --intencao "<acao>" --doc-lida <arquivo> --json\`: proves documentation reading before closure.
 
-Honest closure: treat drift JSON as the source of truth. \`sucesso:false\`, \`vinculos_quebrados\`, \`rotas_divergentes\`, or broken impls mean the change is not complete yet. Do not report "clean drift" without green JSON.
+Honest closure: unwrap drift JSON and treat its command payload as the source of truth. \`payload.sucesso:false\`, non-empty \`payload.vinculos_quebrados\`, non-empty \`payload.rotas_divergentes\`, or non-empty \`payload.impls_quebrados\` mean the change is not complete yet. Do not report "clean drift" without a green payload.
+
+Focused drift exposes its planned, declared, inferred, and missing files plus catalog visit/read metrics in \`escopo_aplicado\`. File and module scopes fail closed without a safe anchor, with homonymous implementation candidates, or with missing local dependencies; only \`--escopo projeto\` may walk every configured code root. Logical roots such as \`src\` are probed deterministically without a discovery walk. Configured contract origins and code roots are confined before enumeration, and \`inspecionar\`, \`impacto\`, and \`renomear-semantico\` reuse the same directed boundary without reopening arbitrary external paths.
+
+Drift analysis and cache modes are explicit:
+
+- \`sema drift\` defaults to \`--cache fresh\`. \`none\` still executes drift but performs zero persistent-cache I/O; \`cache\` reuses a fully validated extraction hit and publishes misses; \`fresh\` ignores hits, recalculates, and publishes the new extraction.
+- \`sema resumo\` and \`sema inspecionar\` default to \`--drift none\`. In that mode their payload does not execute drift and returns \`null\` for score, confidence, implementation, routes, or other code evidence that was not observed. Use \`--drift cache\` or \`--drift fresh\` when that evidence is required. \`--com-drift\` remains a temporary alias for \`--drift fresh\`.
+- When a query explicitly runs drift, \`payload.analiseDrift.sucesso\` exposes the result and a failed requested analysis returns a nonzero exit code.
+- The value aliases \`off\`, \`auto\`, and \`refresh\` normalize to \`none\`, \`cache\`, and \`fresh\` for one compatibility release and emit a structured deprecation warning. Wrong flags, repeated flags, conflicts, and invalid values fail instead of falling back silently.
+- Persistent cache objects live outside the workspace under the operating system's user-cache directory. Workspace identity is hashed; public JSON and events expose only an opaque key and \`$SEMA_CACHE/...\` paths. Corruption or cache unavailability becomes a miss and never changes the drift result. Only validated extraction data is reused; links, diagnostics, scores, and the final success decision are recalculated.
+
+A cache hit is acceleration, not final evidence; closure still requires fresh drift.
 
 ## Sema Code
 
@@ -729,7 +769,8 @@ Ready UI rule: if the task generates an app, site, dashboard, form, or static HT
 
 - \`sema ajuda-ia\`: short guidance for Codex.
 - \`sema starter-ia\`: operational starter.
-- \`sema contexto-ia <arquivo.sema> --saida <dir> --json\`: AI context package.
+- \`sema contexto-ia <arquivo.sema> --saida <dir> --json\`: AI context package.
+- \`sema resumo <arquivo-ou-pasta> [--drift <none|cache|fresh>] --json\`: compact context; drift is not executed unless requested.
 - \`sema prompt-curto <arquivo-ou-pasta> --json\`: compact prompt.
 - \`sema sync-codex --json\`: synchronizes the official Codex entrypoint and local support docs.
 - \`sema instalar-exemplos --json\`: installs official examples in the workspace.
@@ -751,34 +792,34 @@ Ready UI rule: if the task generates an app, site, dashboard, form, or static HT
 - \`sema conteudo planejar <definition.json> --alvos-arquivo <targets.json> --json\`: creates a declarative multi-target plan for an external runner.
 - \`sema conteudo validar-envelope --envelope-arquivo <envelope.json> --confianca-arquivo <trust.json> --trust-root-digest <sha256:...> --revocation-digest <sha256:...> --payload-type <type> --json\`: verifies Ed25519 identity, authorization, freshness, scope, and the separately pinned trust root and current revocation overlay.
 - \`sema conteudo registrar <ledger.ndjson> --envelope-arquivo <envelope.json> --politica-arquivo <policy-envelope.json> --confianca-arquivo <trust.json> --trust-root-digest <sha256:...> --revocation-digest <sha256:...> --ledger-id <id> --expected-head <sha256:...> --json\`: appends a verified envelope under the signed run policy to the local replay ledger at an externally retained head.
-- \`sema conteudo status <definition.json> --politica-arquivo <policy-envelope.json> --confianca-arquivo <trust.json> --trust-root-digest <sha256:...> --revocation-digest <sha256:...> --ledger-arquivo <ledger.ndjson> --expected-head <sha256:...> --json\`: verifies the signed policy and its \`targetSetDigest\`, then derives verdicts, operational conditions, completion, and next actions from canonical events.
+- \`sema conteudo status <definition.json> --politica-arquivo <policy-envelope.json> --confianca-arquivo <trust.json> --trust-root-digest <sha256:...> --revocation-digest <sha256:...> --ledger-arquivo <ledger.ndjson> --expected-head <sha256:...> --json\`: verifies the signed policy and its \`targetSetDigest\`, then derives verdicts, operational conditions, completion, and next actions from canonical events.
 - \`sema conteudo projetar <definition.json> --politica-arquivo <policy-envelope.json> --confianca-arquivo <trust.json> --trust-root-digest <sha256:...> --revocation-digest <sha256:...> --ledger-arquivo <ledger.ndjson> --expected-head <sha256:...> --saida <manifest.json> --json\`: regenerates a non-authoritative manifest bound to the ledger head.
 
-The content command is an AI-native, multi-channel, multi-format control plane. It never runs producers, evaluators, creative tools, or publication adapters; those belong to an external runner. It has no native human-review transition. A signed policy binds \`runId\`, definition, ledger, trust root, gates, complete target set, and the full \`issuedAt\`/\`expiresAt\` authorization window; no event may be recorded outside it. Stages select \`adapterPolicy\` as \`NONE\`, \`CONSTRAINTS\`, or \`CONFIRMATION\`; definition v1 accepts one output per stage. Constraint results must come from independent signed observations, including independently observed media type, not artifact metadata or executor claims. Target metadata is an exact scalar allowlist from \`requiredMetadata + optionalMetadata\`; \`accountScope\` is a credential-free \`account:<alias>\` reference, and artifact metadata is prohibited in v1. Deterministic evidence and AI opinions have separate quorum fields. Evidence requires an exact \`content.evidence.attest:<evidenceType>\` capability; adapter evidence requires \`content.adapter.attest:<adapterId>@<version>:<evidenceType>\` plus signed adapter binding.
+The content command is an AI-native, multi-channel, multi-format control plane. It never runs producers, evaluators, creative tools, or publication adapters; those belong to an external runner. It has no native human-review transition. A signed policy binds \`runId\`, definition, ledger, trust root, gates, complete target set, and the full \`issuedAt\`/\`expiresAt\` authorization window; no event may be recorded outside it. Stages select \`adapterPolicy\` as \`NONE\`, \`CONSTRAINTS\`, or \`CONFIRMATION\`; definition v1 accepts one output per stage. Constraint results must come from independent signed observations, including independently observed media type, not artifact metadata or executor claims. Target metadata is an exact scalar allowlist from \`requiredMetadata + optionalMetadata\`; \`accountScope\` is a credential-free \`account:<alias>\` reference, and artifact metadata is prohibited in v1. Deterministic evidence and AI opinions have separate quorum fields. Evidence requires an exact \`content.evidence.attest:<evidenceType>\` capability; adapter evidence requires \`content.adapter.attest:<adapterId>@<version>:<evidenceType>\` plus signed adapter binding.
 
-Verdicts such as \`APROVADO\`, \`REPROVADO\`, and \`INCONCLUSIVO\` remain separate from operational conditions such as \`AGUARDANDO_EVENTO_EXTERNO\` and \`FERRAMENTA_INDISPONIVEL\`. A generated manifest is only a projection and cannot alter canonical state.
+Verdicts such as \`APROVADO\`, \`REPROVADO\`, and \`INCONCLUSIVO\` remain separate from operational conditions such as \`AGUARDANDO_EVENTO_EXTERNO\` and \`FERRAMENTA_INDISPONIVEL\`. A generated manifest is only a projection and cannot alter canonical state.
 
-Local NDJSON plus a hash chain is portable evidence for replay, not a strong append-only trust boundary. Retain \`expectedHead\`, the canonical trust-root digest, and the current revocation digest externally, or use protected storage for high assurance. The trust-root pin identifies the authority snapshot independently from the revocation overlay. A workspace-local trust file additionally requires \`--development-local-trust\`; the flag does not disable digest pinning. Append freshness uses the platform clock rather than caller-provided \`recordedAt\`, and an authority in the current revocation overlay cannot sign an accepted policy.
+Local NDJSON plus a hash chain is portable evidence for replay, not a strong append-only trust boundary. Retain \`expectedHead\`, the canonical trust-root digest, and the current revocation digest externally, or use protected storage for high assurance. The trust-root pin identifies the authority snapshot independently from the revocation overlay. A workspace-local trust file additionally requires \`--development-local-trust\`; the flag does not disable digest pinning. Append freshness uses the platform clock rather than caller-provided \`recordedAt\`, and an authority in the current revocation overlay cannot sign an accepted policy.
 
 ## AI-native Interactive Systems
 
 - \`sema interativo capabilities --json\`: lists the canonical interactive capability vocabulary.
-- \`sema interativo schema --json\`: exposes the stable read-only definition schema, enum matrix, constraints, extension-command and data-schema shapes, plus canonical example paths for AI clients.
+- \`sema interativo schema --json\`: exposes the stable read-only definition schema, enum matrix, constraints, extension-command and data-schema shapes, plus canonical example paths for AI clients.
 - \`sema interativo pipelines --json\`: lists reusable game, simulation, and hybrid pipelines.
 - \`sema interativo adapters [--spatial-model <NON_SPATIAL|TWO_D|TWO_POINT_FIVE_D|THREE_D>] [--render-mode <HEADLESS|TEXT|VISUAL|XR>] --json\`: lists compatible external adapter descriptors.
 - \`sema interativo validar <definition.json> --json\`: validates independent kind, spatial model, render mode, visual profile, fidelity, control, time, world, budget, pipeline, and acceptance axes.
 - \`sema interativo planejar <definition.json> --json\`: expands compatible stages and required evidence without running an engine.
 - \`sema interativo validar-evidencias|status <definition.json> [--plano-arquivo <plan.json>] --bundle-arquivo <bundle.json> --json\`: validates a portable evidence bundle or derives non-authoritative status; \`--evidencias-arquivo\` is an alias and an omitted plan is recomputed deterministically.
 - \`sema interativo validar-protocolo <adapter-run.json> --json\`: checks DETECT/PROBE/SNAPSHOT/PLAN/APPLY/VALIDATE/EVIDENCE/ROLLBACK ordering and stable target binding.
-- Experience IR: \`validar-ir\`, \`indexar-ir\`, \`consultar-ir --semantic-id <id>\`, \`chunk-ir --semantic-id <id> [--raso]\`, and \`descrever-ir\`.
-- Operational state: \`validar-engine-snapshot\`, \`diff-engine-snapshots\`, \`validar-asset-provenance\`, \`validar-editor-state\`, \`planejar-jobs\`, \`validar-acceptance\`, \`operar-acceptance --operation <VALIDATE|EVALUATE|INVALIDATE> --context-file <file>\`, and \`validar-multimodal\`.
-- Temporal, autonomy, and testing: \`validar-temporal\`, \`validar-evidencia-temporal --bundle-arquivo <file>\`, \`validar-autonomia\`, \`validar-playtest-fuzz\`, and \`validar-multiplayer\`.
-- Portability and workers: \`analisar-portabilidade\` and \`validar-workers\`.
-- \`sema interativo validar-control-run <control-run.json> --definition-arquivo <definition.json> --plano-arquivo <plan.json> --contrato-arquivo <validation-contract.json> --entrada-arquivo <input.json> [--entrada-auxiliar-arquivo <supporting-input.json>] --evidencia-arquivo <evidence.json> --resultado-arquivo <result.json> --json\`: binds one advanced validation to its complete local digest chain instead of trusting a standalone result.
-
-The control-run command recomputes the canonical plan and selected pure validator, then verifies the definition, pipeline descriptor, validation contract, schema-declared inputs, evidence, and result digests. Prefix advanced items with \`sema interativo\` and pass the documented JSON file as the positional argument; an agent does not have to infer the validator or payload shape from a filename or visual style. The machine-readable schema publishes command maps, input/output schema links, required top-level fields, \`outputTargets\` path segments from the payload root, at least one real output shape per command, and official fixtures for all 20 advanced commands. Validation-result shapes describe \`payload.resultado\`; projected IR values use \`indice\`, \`entry\`, \`chunk\`, or \`descriptor\`; operation projections such as \`engineDiff\` and \`jobOrchestrationPlan\` live under \`payload.resultado.value\`; the job plan's ordered \`queue\` is the assignment list and exposes kind, priority, adapter, dependencies, locks, budgets, heartbeat, checkpoint, and recovery data.
-
-Spatial model and render mode are orthogonal: \`THREE_D + HEADLESS\` is valid, while XR requires \`THREE_D\`. \`PIXEL_8_BIT\` and \`PIXEL_16_BIT\` are independent visual profiles available to games and simulations. Every command above rejects unknown, duplicate, missing-value, or invalid-enum arguments, remains local, read-only, and non-authoritative, and leaves engine/editor execution, authorization, mutation, rollback, migration, rendering, playtest, and worker scheduling to external runners. Full local coverage is \`STRUCTURALLY_COMPLETE\`, never authoritative completion, and a local evidence bundle is never presented as authoritative trust.
+- Experience IR: \`validar-ir\`, \`indexar-ir\`, \`consultar-ir --semantic-id <id>\`, \`chunk-ir --semantic-id <id> [--raso]\`, and \`descrever-ir\`.
+- Operational state: \`validar-engine-snapshot\`, \`diff-engine-snapshots\`, \`validar-asset-provenance\`, \`validar-editor-state\`, \`planejar-jobs\`, \`validar-acceptance\`, \`operar-acceptance --operation <VALIDATE|EVALUATE|INVALIDATE> --context-file <file>\`, and \`validar-multimodal\`.
+- Temporal, autonomy, and testing: \`validar-temporal\`, \`validar-evidencia-temporal --bundle-arquivo <file>\`, \`validar-autonomia\`, \`validar-playtest-fuzz\`, and \`validar-multiplayer\`.
+- Portability and workers: \`analisar-portabilidade\` and \`validar-workers\`.
+- \`sema interativo validar-control-run <control-run.json> --definition-arquivo <definition.json> --plano-arquivo <plan.json> --contrato-arquivo <validation-contract.json> --entrada-arquivo <input.json> [--entrada-auxiliar-arquivo <supporting-input.json>] --evidencia-arquivo <evidence.json> --resultado-arquivo <result.json> --json\`: binds one advanced validation to its complete local digest chain instead of trusting a standalone result.
+
+The control-run command recomputes the canonical plan and selected pure validator, then verifies the definition, pipeline descriptor, validation contract, schema-declared inputs, evidence, and result digests. Prefix advanced items with \`sema interativo\` and pass the documented JSON file as the positional argument; an agent does not have to infer the validator or payload shape from a filename or visual style. The machine-readable schema publishes command maps, input/output schema links, required top-level fields, \`outputTargets\` path segments from the payload root, at least one real output shape per command, and official fixtures for all 20 advanced commands. Validation-result shapes describe \`payload.resultado\`; projected IR values use \`indice\`, \`entry\`, \`chunk\`, or \`descriptor\`; operation projections such as \`engineDiff\` and \`jobOrchestrationPlan\` live under \`payload.resultado.value\`; the job plan's ordered \`queue\` is the assignment list and exposes kind, priority, adapter, dependencies, locks, budgets, heartbeat, checkpoint, and recovery data.
+
+Spatial model and render mode are orthogonal: \`THREE_D + HEADLESS\` is valid, while XR requires \`THREE_D\`. \`PIXEL_8_BIT\` and \`PIXEL_16_BIT\` are independent visual profiles available to games and simulations. Every command above rejects unknown, duplicate, missing-value, or invalid-enum arguments, remains local, read-only, and non-authoritative, and leaves engine/editor execution, authorization, mutation, rollback, migration, rendering, playtest, and worker scheduling to external runners. Full local coverage is \`STRUCTURALLY_COMPLETE\`, never authoritative completion, and a local evidence bundle is never presented as authoritative trust.
 
 ## Operational
 
@@ -786,52 +827,17 @@ Spatial model and render mode are orthogonal: \`THREE_D + HEADLESS\` is valid, w
 
 ## Forbidden
 
-- Do not use an external workspace source to inspect a local workspace when \`sema --version\` works.
+- Do not use an external workspace source to inspect a local workspace when \`sema --version\` or the managed launcher works.
 - Do not search the entire disk for \`.sema\` syntax; use \`exemplos/\`, \`docs/syntax.md\`, and this catalog.
 - Do not stop after \`sema compilar\` if the contract target files still do not exist.
 - Do not replace \`sema compilar\` with \`sema testar\` when the contract requires generated code.
 - Do not create a Markdown report to pretend a gate ran.
-- Do not say drift passed when \`sema drift --json\` returned \`sucesso:false\`, broken link, divergent route, or broken impl.
+- Do not say drift passed when the unwrapped \`sema drift --cache fresh --json\` payload returned \`sucesso:false\`, a non-empty \`vinculos_quebrados\`, \`rotas_divergentes\`, or \`impls_quebrados\` list.
 - Do not declare a UI responsive without mobile/desktop proof; horizontal scroll at 390px blocks closure.
 
 Governed code policy: keep the \`SEMA-GOVERNED\` marker, split large code by real responsibility, preserve contract links, and never treat a generated output directory as the final delivery.
 `;
 }
-function renderizarAgentStarterLocal(_agentContextPack) {
-    return `# Codex Starter
-
-Codex is operating in a Sema-governed project.
-
-Read in this order:
-
-1. \`${ARQUIVO_SEMA_BOOT}\`
-2. \`${ARQUIVO_AGENT_CONTEXT_PACK}\`
-3. \`SEMA_INDEX.json\`
-4. \`AGENTS.md\`
-5. \`docs/commands.md\`
-6. \`docs/syntax.md\`
-7. \`exemplos/\`
-
-Basic commands:
-
-\`\`\`bash
-sema --version
-sema resumo
-sema docs-impacto --intencao "<acao>" --json
-sema validar contratos/orders.sema --json
-sema drift contratos/orders.sema --escopo modulo --json
-sema compilar contratos/orders.sema --alvo javascript --saida ./generated/javascript
-\`\`\`
-
-Do not replace these gates with local search, guessing from a filename, or random contract reading outside the project.
-
-Closure is not an opinion: \`sema drift --json\` must be green. \`sucesso:false\`, \`vinculos_quebrados\`, \`rotas_divergentes\`, or broken impls block closure.
-
-Ready UI requires proof: desktop/mobile and a narrow viewport without horizontal overflow (\`scrollWidth <= clientWidth\`).
-
-Keep \`SEMA-GOVERNED\` markers and follow the applicable contract before editing governed code.
-`;
-}
 export async function sincronizarEntrypointCodex(baseProjeto, agentContextPack) {
     const resultados = [];
     await validarDestinosEscritaWorkspace(baseProjeto, listarDestinosEntrypointCodex(agentContextPack.entrypointCodex));
@@ -869,10 +875,15 @@ export async function sincronizarEntrypointCodex(baseProjeto, agentContextPack)
         codexNativo: true,
         cliLocalSemAutorizacao: true,
         skillBootstrapCodexDocumentada: true,
+        launcherGlobalFallbackDocumentado: true,
+        cliIndisponivelSomenteAposFallback: true,
+        skillGlobalDelegaAgentsMd: true,
         idiomaHumanoPreservado: true,
         retryTimeoutProgressivo: true,
         politicaPlataformaExplicita: true,
         politicaSinalVsRitualExplicita: true,
+        politicaModosDriftExplicita: true,
+        docsComandos: true,
         divisaoPorResponsabilidadeExplicita: true,
         contextoLocalSemEspelho: true,
         destinosEntrypointPrevalidados: true,

package/dist/angular-consumer-standalone.d.ts

@@ -1,6 +1,8 @@
+import ts from "typescript";
 export interface SuperficieAngularStandaloneConsumer {
     rota: string;
     arquivo: string;
     tipoArquivo: "app" | "component";
 }
-export declare function coletarSuperficiesAngularStandaloneConsumer(baseProjeto: string, arquivos: string[]): Promise<SuperficieAngularStandaloneConsumer[]>;
+export type LeitorTextoAngularConsumer = (arquivo: string) => Promise<string>;
+export declare function coletarSuperficiesAngularStandaloneConsumer(baseProjeto: string, arquivos: string[], leitorTexto?: LeitorTextoAngularConsumer, sourceFiles?: ReadonlyMap<string, ts.SourceFile>): Promise<SuperficieAngularStandaloneConsumer[]>;

package/dist/angular-consumer-standalone.js

@@ -1,3 +1,5 @@
+// SEMA-GOVERNED: sema.produto.governanca_ia.drift
+// Descricao: extrai superficies Angular com leitura compartilhada opcional, sem manter cache proprio.
 import { readFile } from "node:fs/promises";
 import path from "node:path";
 import ts from "typescript";
@@ -134,7 +136,7 @@ function extrairIdentificadorImportado(expressao) {
     }
     return undefined;
 }
-async function extrairTemplateAngularStandalone(baseProjeto, relacaoArquivo, metadata) {
+async function extrairTemplateAngularStandalone(baseProjeto, relacaoArquivo, metadata, leitorTexto) {
     const templateInline = extrairTextoLiteral(obterExpressaoPropriedade(metadata, "template"));
     if (templateInline) {
         return templateInline;
@@ -148,19 +150,21 @@ async function extrairTemplateAngularStandalone(baseProjeto, relacaoArquivo, met
         return "";
     }
     try {
-        return await readFile(path.join(baseProjeto, templateRelativo), "utf8");
+        const arquivo = path.join(baseProjeto, templateRelativo);
+        return leitorTexto ? await leitorTexto(arquivo) : await readFile(arquivo, "utf8");
     }
     catch {
         return "";
     }
 }
-async function indexarComponenteAngularStandalone(baseProjeto, arquivo) {
+async function indexarComponenteAngularStandalone(baseProjeto, arquivo, leitorTexto, sourceFiles) {
     const relacaoArquivo = normalizarCaminhoConsumer(path.relative(baseProjeto, arquivo));
     if (!arquivoEhComponenteAngularStandalone(relacaoArquivo)) {
         return undefined;
     }
-    const codigo = await readFile(arquivo, "utf8");
-    const sourceFile = ts.createSourceFile(arquivo, codigo, ts.ScriptTarget.Latest, true, ts.ScriptKind.TS);
+    const codigo = leitorTexto ? await leitorTexto(arquivo) : await readFile(arquivo, "utf8");
+    const sourceFile = sourceFiles?.get(path.resolve(arquivo))
+        ?? ts.createSourceFile(arquivo, codigo, ts.ScriptTarget.Latest, true, ts.ScriptKind.TS);
     const imports = extrairImportsTypeScriptAngular(relacaoArquivo, codigo);
     for (const statement of sourceFile.statements) {
         if (!ts.isClassDeclaration(statement)) {
@@ -192,7 +196,7 @@ async function indexarComponenteAngularStandalone(baseProjeto, arquivo) {
             arquivo: relacaoArquivo,
             selector: extrairTextoLiteral(obterExpressaoPropriedade(metadata, "selector")),
             imports: [...importsArquivos],
-            template: await extrairTemplateAngularStandalone(baseProjeto, relacaoArquivo, metadata),
+            template: await extrairTemplateAngularStandalone(baseProjeto, relacaoArquivo, metadata, leitorTexto),
             raiz: arquivoEhRaizAngularStandalone(relacaoArquivo),
         };
     }
@@ -205,10 +209,10 @@ function templateReferenciaSelector(template, selector) {
     const escapado = selector.replace(/[.*+?^${}()|[\]\\]/g, "\\$&");
     return new RegExp(`<${escapado}(?:\\s|>)`, "i").test(template);
 }
-export async function coletarSuperficiesAngularStandaloneConsumer(baseProjeto, arquivos) {
+export async function coletarSuperficiesAngularStandaloneConsumer(baseProjeto, arquivos, leitorTexto, sourceFiles) {
     const componentes = new Map();
     for (const arquivo of arquivos) {
-        const componente = await indexarComponenteAngularStandalone(baseProjeto, arquivo);
+        const componente = await indexarComponenteAngularStandalone(baseProjeto, arquivo, leitorTexto, sourceFiles);
         if (componente) {
             componentes.set(componente.arquivo, componente);
         }

package/dist/bin.d.ts

@@ -0,0 +1,6 @@
+#!/usr/bin/env node
+/**
+ * Única entrada executável pública. O import do runtime ocorre somente depois
+ * de ajuda, argv vazio e versão encerrarem sem resolver handlers.
+ */
+export declare function executarCliPublica(argv?: readonly string[]): Promise<number>;