@semacode/cli 2.1.0 → 2.3.0

package/README.md

@@ -59,8 +59,9 @@ generated `AGENTS.md`. Installing this npm package never writes into
 
 - `AGENTS.md` is the only official entrypoint. `sync-codex` changes only valid
   Sema-managed blocks and preserves malformed or manual content for review.
-- Agent Context Pack consumers use schema version 6 and the fields
-  `entrypointCodex`, `codexNativo`, and `cliLocalSemAutorizacao`.
+- Agent Context Pack consumers use schema version 7, including the deterministic
+  discovery summary and the fields `entrypointCodex`, `codexNativo`, and
+  `cliLocalSemAutorizacao`.
 - The Sema Codex skill is required for first contact. It initializes the
   workspace and generates `AGENTS.md`; it does not duplicate the governed
   workflow after that handoff.
@@ -109,10 +110,112 @@ sema testar contratos/app.sema --alvo cpp --saida .tmp/app-cpp-tests
 sema verificar contratos/app.sema --saida .tmp/app-check --json
 ```
 
+## AI-native Content Pipeline
+
+`sema conteudo` validates and plans multi-channel, multi-format content work,
+verifies signed policies and evidence, replays canonical state, and projects
+non-authoritative manifests. Producer agents, specialized AI evaluators,
+creative tools, and delivery adapters run in an external runner; there is no
+native human-review transition.
+
+```bash
+sema conteudo validar exemplos/pipeline-conteudo/definicao.json --json
+sema conteudo planejar exemplos/pipeline-conteudo/definicao.json --alvos-arquivo exemplos/pipeline-conteudo/alvos.json --json
+```
+
+See `docs/pipeline-conteudo.md` for the signed trust, quorum, ledger, target,
+adapter, and projection model.
+
+## Capability Discovery and Interactive Systems
+
+`sema descobrir` exposes one explainable catalog and a deterministic intent
+router. `sema interativo` validates and plans games, simulations, and hybrids
+across independent spatial models, render modes, retro visual profiles, control,
+time, determinism, and fidelity axes without running an engine or silently
+mutating a workspace.
+
+```bash
+sema descobrir catalogo --json
+sema descobrir recomendar --intencao "calibrate a headless autonomous simulation" --json
+sema interativo schema --json
+sema interativo pipelines --json
+sema interativo validar exemplos/sistemas-interativos/simulation-headless-autonomous-batch.json --json
+```
+
+The canonical interactive catalog contains 35 unique pipelines and 28 unique
+external adapter descriptors. Its advanced P0/P1/P2 surface covers Experience
+IR, semantic engine snapshots, asset provenance, editor-state descriptions,
+multimodal evidence, resumable jobs, acceptance locks, temporal/shot/physics QA,
+clean-install and hardware constraints, safe autonomous repair, bounded
+playtest/fuzz plans, multiplayer authority, portability with declared losses,
+and distributed worker DAGs.
+
+Advanced read-only commands:
+
+```bash
+sema interativo validar-ir <file> --json
+sema interativo indexar-ir <file> --json
+sema interativo consultar-ir <file> --semantic-id <id> --json
+sema interativo chunk-ir <file> --semantic-id <id> [--raso] --json
+sema interativo descrever-ir --json
+
+sema interativo validar-engine-snapshot <file> --json
+sema interativo diff-engine-snapshots <before> <after> --json
+sema interativo validar-asset-provenance <file> --json
+sema interativo validar-editor-state <file> --json
+sema interativo planejar-jobs <file> --json
+sema interativo validar-acceptance <file> --json
+sema interativo operar-acceptance <lock> --operation <VALIDATE|EVALUATE|INVALIDATE> --context-file <file> --json
+sema interativo validar-multimodal <file> --json
+
+sema interativo validar-temporal <file> --json
+sema interativo validar-evidencia-temporal <contract> --bundle-arquivo <file> --json
+sema interativo validar-autonomia <file> --json
+sema interativo validar-playtest-fuzz <file> --json
+sema interativo validar-multiplayer <file> --json
+sema interativo analisar-portabilidade <file> --json
+sema interativo validar-workers <file> --json
+
+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
+```
+
+All of these commands are local and read-only. Adapter entries are external
+capability descriptors: the package does not detect, probe, launch, install, or
+control any engine, editor, plug-in, process, verifier, or worker. A
+`STRUCTURALLY_COMPLETE` result is local structural coverage only; it always
+remains `completed: false`, `authoritative: false`, and awaits external
+attestation. The CLI never equates a descriptor, fixture, plan, or supplied JSON
+record with proof that external work occurred.
+
+See `docs/descoberta-capacidades.md` and `docs/sistemas-interativos.md` for the
+ranking, adapter protocol, evidence boundary, fidelity, and coverage model.
+
+## Programmatic API
+
+The package root can be imported without executing the CLI process:
+
+```js
+import {
+  analisarPlanoPortabilidadeInterativa,
+  indexarExperienceIr,
+  montarCatalogoCapacidades,
+  validarContratoTemporalInterativo,
+  validarControlRunInterativo,
+  validarDefinicaoSistemaInterativo,
+  validarExperienceIr,
+} from "@semacode/cli";
+```
+
+Only the package-root exports are public. Internal `dist/*` deep imports remain
+blocked, and importing the package never parses CLI arguments or exits the host
+process. Programmatic validators and planners preserve the same read-only,
+non-authoritative boundary as their CLI equivalents.
+
 ## Public Boundary
 
-The npm package is for local CLI usage only. It must not contain private or
-sensitive operational material.
+The npm package is local-only: its CLI and programmatic API do not depend on a
+hosted Sema service. It must not contain private or sensitive operational
+material.
 
 ## Commercial Use
 

package/dist/agentContext.d.ts

@@ -13,7 +13,7 @@ export declare function criarEntradaCanonicaProjeto(guiaPorCapacidade: GuiaCapac
         pequena: import("./agentContextTipos.js").CapacidadeIa;
         grande: import("./agentContextTipos.js").CapacidadeIa;
     };
-    docsSuporte: ("docs/ai-integration.md" | "docs/ai-workflow.md" | "docs/ai-onboarding.md" | "docs/syntax.md" | "docs/cli.md" | "docs/commands.md" | "docs/profiles.md" | "docs/testing.md" | "docs/documentation.md" | "docs/deploy.md" | "docs/env.md" | "docs/rollback.md")[];
+    docsSuporte: ("docs/ai-integration.md" | "docs/ai-workflow.md" | "docs/ai-onboarding.md" | "docs/syntax.md" | "docs/cli.md" | "docs/commands.md" | "docs/descoberta-capacidades.md" | "docs/profiles.md" | "docs/sistemas-interativos.md" | "docs/testing.md" | "docs/documentation.md" | "docs/deploy.md" | "docs/env.md" | "docs/rollback.md")[];
     agentContextPack: import("./agentContextTipos.js").AgentContextPack;
     guiaPorCapacidade: GuiaCapacidadeIaMap;
 };

package/dist/agentContextPack.js

@@ -2,6 +2,7 @@
 // Descrição: monta o Agent Context Pack e políticas que agentes fracos, médios e fortes consomem antes do código.
 import { LIMITE_AVISO_LINHAS_CODIGO_GOVERNADO, LIMITE_AVISO_LINHAS_CONTRATO_SEMA, LIMITE_BLOQUEIO_LINHAS_CODIGO_GOVERNADO, LIMITE_BLOQUEIO_LINHAS_CONTRATO_SEMA, } from './driftOrcamento.js';
 import { ALIASES_CAPACIDADE_IA, ARQUIVO_AGENT_CONTEXT_PACK, ARQUIVO_DOC_AGENTES_CAPACIDADE, ARQUIVO_ENTRYPOINT_CODEX, ARQUIVO_SEMA_BOOT, ARQUIVO_SEMA_SMALL_MODEL, EXEMPLOS_OFICIAIS_AGENT_CONTEXT, } from './agentContextTipos.js';
+import { criarResumoDescobertaAgentContext } from "./discovery/index.js";
 export const LIMITE_CARACTERES_PAYLOAD_INLINE = 262144;
 export function criarGuiaCapacidadeIa() {
     const fraca = {
@@ -287,7 +288,7 @@ export function criarAgentContextPack(guiaPorCapacidade) {
     ];
     return {
         nome: "Agent Context Pack",
-        versao: 6,
+        versao: 7,
         objetivo: "Dar a agentes IA uma entrada curta, estruturada e auditável antes de abrir código cru ou inventar contexto.",
         ordemLeitura: [
             ARQUIVO_SEMA_BOOT,
@@ -304,6 +305,7 @@ export function criarAgentContextPack(guiaPorCapacidade) {
             "Leia SEMA_BOOT.md antes de qualquer outro artefato de IA.",
             "Leia AGENTS.md antes de editar código, contrato, docs operacionais, release ou deploy.",
             "Leia docs/commands.md antes de escolher comando Sema, interpretar um gate ou usar --saida de sema compilar.",
+            "Quando a intenção não deixar claro qual profile, workflow, pipeline, gerador ou adapter usar, rode `sema descobrir recomendar --intencao \"<objetivo>\" --json`; a recomendação informa, mas nunca se autoexecuta.",
             "Em workspace local, rode sema --version; se falhar, pare e peça a instalação da CLI. Com a CLI disponível, use diretamente sema resumo, docs-impacto, inspecionar, drift e impacto sobre a pasta local.",
             "Antes de editar, rode `sema inspecionar <contrato.sema> --json`, `sema drift <contrato.sema> --escopo modulo --json` e `sema impacto <contrato.sema> --alvo <token> --mudanca \"<descricao>\" --json`.",
             "Use exemplos oficiais antes de criar ou corrigir sintaxe .sema.",
@@ -326,6 +328,7 @@ export function criarAgentContextPack(guiaPorCapacidade) {
         ],
         proibicoes: [
             "Não inventar sintaxe Sema fora da gramática e dos exemplos oficiais.",
+            "Não adivinhar nem executar automaticamente uma capacidade quando discovery reportar no-match, ambiguidade ou inputs ausentes.",
             "Não tratar README, texto livre ou código como fonte superior ao contrato.",
             "Não substituir os gates da CLI Sema por README.md, busca local, inferência pelo nome do projeto ou bom senso.",
             "Não tratar a pasta --saida de sema compilar como entrega final; entrega são os arquivos alvo/vínculos do contrato.",
@@ -349,6 +352,7 @@ export function criarAgentContextPack(guiaPorCapacidade) {
         ],
         prioridades: [
             "Menor artefato suficiente primeiro.",
+            "Catálogo de discovery antes de escolher por chute entre profile, workflow, pipeline, gerador ou adapter.",
             "Workspace local: sema --version, resumo, docs-impacto, inspecionar, drift e impacto pela CLI; se sema não existir, pare e peça a instalação da CLI.",
             "Contrato, índice e AGENTS complementam o contexto Sema; não substituem chamada Sema.",
             "Exemplos oficiais antes de nova sintaxe.",
@@ -363,6 +367,7 @@ export function criarAgentContextPack(guiaPorCapacidade) {
             "Se risco ou escopo estiver ambíguo, parar e pedir contrato/contexto.",
         ],
         fontes,
+        descoberta: criarResumoDescobertaAgentContext(),
         exemplosOficiais: [...EXEMPLOS_OFICIAIS_AGENT_CONTEXT],
         textoBrutoSobDemanda: Object.fromEntries(fontes.map((fonte) => [fonte.caminho, fonte.incluirTextoBrutoQuando])),
         guiaPorCapacidade: {

package/dist/agentContextTipos.d.ts

@@ -1,3 +1,4 @@
+import type { ResumoDescobertaAgentContext } from "./discovery/types.js";
 export type CapacidadeIa = "fraca" | "media" | "forte";
 export type CapacidadeIaLegada = "pequena" | "grande";
 export type ChaveGuiaCapacidadeIa = CapacidadeIa | CapacidadeIaLegada;
@@ -65,6 +66,7 @@ export interface AgentContextPack {
     proibicoes: string[];
     prioridades: string[];
     fontes: FonteAgentContextPack[];
+    descoberta: ResumoDescobertaAgentContext;
     exemplosOficiais: string[];
     textoBrutoSobDemanda: Record<string, string>;
     guiaPorCapacidade: Record<ChaveGuiaCapacidadeIa, string[]>;
@@ -89,5 +91,5 @@ export declare const CAPACIDADES_IA_OPERACIONAIS: readonly ["fraca", "media", "f
 export declare const ALIASES_CAPACIDADE_IA: Record<CapacidadeIaLegada, CapacidadeIa>;
 export declare const MARCADOR_SEMA_AGENT_ENTRYPOINT_INICIO = "<!-- sema:agent-entrypoint:start -->";
 export declare const MARCADOR_SEMA_AGENT_ENTRYPOINT_FIM = "<!-- sema:agent-entrypoint:end -->";
-export declare const DOCUMENTOS_SUPORTE_IA: readonly ["docs/ai-integration.md", "docs/ai-workflow.md", "docs/ai-onboarding.md", "docs/syntax.md", "docs/cli.md", "docs/commands.md", "docs/profiles.md", "docs/testing.md", "docs/documentation.md", "docs/deploy.md", "docs/env.md", "docs/rollback.md"];
-export declare const EXEMPLOS_OFICIAIS_AGENT_CONTEXT: readonly ["exemplos/calculadora.sema", "exemplos/pagamento.sema", "exemplos/profile_software.sema", "exemplos/profile_workflow_n8n.sema", "exemplos/profile_ops.sema", "exemplos/profile_game.sema", "exemplos/profile_legal.sema", "exemplos/profile_research.sema", "exemplos/author_obra_comum.sema"];
+export declare const DOCUMENTOS_SUPORTE_IA: readonly ["docs/ai-integration.md", "docs/ai-workflow.md", "docs/ai-onboarding.md", "docs/syntax.md", "docs/cli.md", "docs/commands.md", "docs/descoberta-capacidades.md", "docs/profiles.md", "docs/sistemas-interativos.md", "docs/testing.md", "docs/documentation.md", "docs/deploy.md", "docs/env.md", "docs/rollback.md"];
+export declare const EXEMPLOS_OFICIAIS_AGENT_CONTEXT: readonly ["exemplos/calculadora.sema", "exemplos/pagamento.sema", "exemplos/profile_software.sema", "exemplos/profile_workflow_n8n.sema", "exemplos/profile_ops.sema", "exemplos/profile_game.sema", "exemplos/profile_simulation.sema", "exemplos/sistemas-interativos/game-pixel-16-bit.json", "exemplos/sistemas-interativos/simulation-headless-autonomous-batch.json", "exemplos/sistemas-interativos/simulation-3d-calibrated-autonomous.json", "exemplos/sistemas-interativos/protocol-read-only-valid.json", "exemplos/profile_legal.sema", "exemplos/profile_research.sema", "exemplos/author_obra_comum.sema"];

package/dist/agentContextTipos.js

@@ -30,7 +30,9 @@ export const DOCUMENTOS_SUPORTE_IA = [
     "docs/syntax.md",
     "docs/cli.md",
     "docs/commands.md",
+    "docs/descoberta-capacidades.md",
     "docs/profiles.md",
+    "docs/sistemas-interativos.md",
     "docs/testing.md",
     "docs/documentation.md",
     "docs/deploy.md",
@@ -44,6 +46,11 @@ export const EXEMPLOS_OFICIAIS_AGENT_CONTEXT = [
     "exemplos/profile_workflow_n8n.sema",
     "exemplos/profile_ops.sema",
     "exemplos/profile_game.sema",
+    "exemplos/profile_simulation.sema",
+    "exemplos/sistemas-interativos/game-pixel-16-bit.json",
+    "exemplos/sistemas-interativos/simulation-headless-autonomous-batch.json",
+    "exemplos/sistemas-interativos/simulation-3d-calibrated-autonomous.json",
+    "exemplos/sistemas-interativos/protocol-read-only-valid.json",
     "exemplos/profile_legal.sema",
     "exemplos/profile_research.sema",
     "exemplos/author_obra_comum.sema",

package/dist/agentEntryPoints.js

@@ -148,12 +148,13 @@ Você está em um projeto governado por Sema. O contrato semântico vem antes de
 
 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\`.
-3. Não use fonte externa de workspace para substituir a CLI local quando ela estiver operacional.
-4. Este boot é para workspace local em disco; se não houver workspace local, pare bloqueado em vez de inventar caminho.
-5. Antes de criar módulo, rota, task ou contrato, inspecione o contrato \`.sema\` aplicável.
-6. Antes de editar código existente, rode drift e impacto pela CLI local.
-7. Antes de criar ou corrigir \`.sema\`, use os exemplos oficiais na CLI local.
-8. Se qualquer etapa falhar, pare e diga que está bloqueado.
+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.
+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.
 
 Não substitua esse fluxo por leitura manual de \`AGENTS.md\`, \`README.md\`, busca local, inferência pelo nome do projeto, bom senso ou ferramenta não citada aqui.
 
@@ -376,6 +377,12 @@ export function renderizarDocumentoAgentesPorCapacidade(agentContextPack) {
         "points back to the applicable contract. The marker is not a substitute for",
         "validation, drift, impact, or finalization gates.",
         "",
+        "Generated Lua tests preserve the contract's failure shape. A case whose only",
+        "expectation is `sucesso: falso` may terminate without an output, while a case",
+        "that also declares observable output fields must return a structured failure",
+        "result. The generator keeps these paths distinct instead of forcing every",
+        "failure into one representation.",
+        "",
         `Governed code above ${LIMITE_AVISO_LINHAS_CODIGO_GOVERNADO} lines requires a`,
         `split plan. Governed code above ${LIMITE_BLOQUEIO_LINHAS_CODIGO_GOVERNADO}`,
         "lines blocks closure. Markdown documentation is not counted as governed code",
@@ -410,7 +417,7 @@ export function renderizarDocumentoAgentesPorCapacidade(agentContextPack) {
         "",
         "Sema governs contract, scope, drift, evidence, and quality. It does not bypass",
         "platform policies, terms of use, permissions, security controls, or laws.",
-    ].join("\n");
+    ].join("\n") + "\n";
 }
 function renderizarInstrucaoCodexSema(agentContextPack) {
     const capacidade = "media";
@@ -425,13 +432,14 @@ Este workspace é governado por Sema. Antes de qualquer ação em código, contr
 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\`.
-4. Não use fonte externa de workspace para substituir a CLI local quando ela estiver operacional.
-5. Chame docs-impacto com a intenção declarada antes de agir.
-6. Chame inspecionar no contrato \`.sema\` aplicável.
-7. Antes de editar código existente, rode drift e impacto.
-8. Antes de criar ou editar \`.sema\`, use exemplos oficiais.
-9. Ao concluir mudança de contrato, rode validar.
-10. Antes de finalizar, use finalizar-mudanca com as docs lidas.
+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.
+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.
 
 É proibido substituir esse fluxo por leitura manual de \`AGENTS.md\`, \`README.md\`, busca local por arquivos, inferência pelo nome do projeto, bom senso ou ferramenta não citada nesta lista.
 
@@ -621,10 +629,11 @@ This is the minimum workflow for Codex in a local workspace.
 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. Use \`exemplos/\` and \`docs/syntax.md\` before creating or editing a contract.
-8. Run \`sema drift\` and \`sema impacto\` before editing existing code.
-9. Run \`sema formatar\` and \`sema validar\` after changing a \`.sema\` contract.
-10. Run \`sema finalizar-mudanca\` with the documents read before closure.
+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.
+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\`.
 
@@ -680,6 +689,10 @@ Then read every required doc returned by \`docs-impacto\`.
 - \`sema inspecionar <arquivo-ou-pasta> --json\`: shows modules, tasks, routes, entities, links, and expected files.
 - \`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.
+- \`sema descobrir recomendar --intencao "<goal>" --json\`: ranks compatible capabilities deterministically without executing the selected command.
+- \`sema descobrir explicar <id> --json\`: explains inputs, boundaries, reasons, and the command template for one capability.
+- \`sema pipeline listar|descrever <id> --json\` and \`sema capabilities --json\`: compact projections of the same discovery catalog.
 
 ## Change and Closure
 
@@ -725,10 +738,48 @@ Ready UI rule: if the task generates an app, site, dashboard, form, or static HT
 ## Profiles and Author
 
 - \`sema author iniciar|validar|briefing|revisar-cliches|validar-narrativa|validar-proibicoes\`: governs authorial writing.
-- \`sema profile validar <software|workflow|ops|game|legal|research|redacao|propostas|conversas> <arquivo> --json\`: validates an artifact by profile.
+- \`sema profile validar <software|workflow|ops|game|simulation|legal|research|redacao|propostas|conversas> <arquivo> --json\`: validates an artifact by profile.
 - \`sema profile capabilities --json\`: lists profiles/capabilities.
 - \`sema rule-packs --profile <profile> --json\`: lists rule packs.
 
+\`author\` is a specialized \`sema author\` workflow, not a \`profile validar\` alias. Discovery exposes that distinction explicitly.
+
+## AI-native Content Pipeline
+
+- \`sema conteudo capabilities --json\`: lists generic producer, evaluator, and adapter capabilities without fixing a platform.
+- \`sema conteudo validar <definition.json> --json\`: validates the content DAG, gates, and open adapters.
+- \`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 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.
+
+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.
+
+## 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 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.
+
 ## Operational
 
 - \`sema doctor\`: diagnoses local installation.

package/dist/comandos.js

@@ -3,6 +3,9 @@
 import { comandoDev } from "./dev/index.js";
 import { comandoInit } from "./init/index.js";
 import { comandoSyncPrisma } from "./sync/index.js";
+import { comandoPipelineConteudo } from "./pipelineConteudo/command.js";
+import { REGISTRO_HANDLERS_DESCOBERTA } from "./discovery/index.js";
+import { comandoSistemasInterativos } from "./sistemasInterativos/command.js";
 async function comandoInitHandler(posicionais, args, _emJson) {
     try {
         await comandoInit([...posicionais, ...args]);
@@ -59,5 +62,8 @@ export const REGISTRO_COMANDOS = {
     init: comandoInitHandler,
     dev: comandoDevHandler,
     sync: comandoSyncPrismaHandler,
+    conteudo: comandoPipelineConteudo,
+    interativo: comandoSistemasInterativos,
+    ...REGISTRO_HANDLERS_DESCOBERTA,
 };
 //# sourceMappingURL=comandos.js.map

package/dist/discovery/catalog.d.ts

@@ -0,0 +1,11 @@
+import { type DiscoveryCatalogFilters, type DiscoveryCatalogPayload, type DiscoveryCommandTemplate, type DiscoveryEntry, type DiscoveryKind, type ResumoDescobertaAgentContext } from "./types.js";
+export declare function normalizarDiscoveryKind(valor: string | null | undefined): DiscoveryKind | null;
+export interface SuperficieCliPipelineInterativo {
+    readonly command: string;
+    readonly requiredInputs: readonly string[];
+    readonly effectClass: DiscoveryCommandTemplate["effectClass"];
+}
+export declare const SUPERFICIES_CLI_PIPELINES_AVANCADOS: Readonly<Record<string, SuperficieCliPipelineInterativo>>;
+export declare function montarCatalogoCapacidades(filtros?: DiscoveryCatalogFilters): DiscoveryCatalogPayload;
+export declare function obterEntradaDescoberta(id: string): DiscoveryEntry | null;
+export declare function criarResumoDescobertaAgentContext(): ResumoDescobertaAgentContext;