@orchestrator-claude/definitions 3.38.0 → 3.40.0

package/agents/agentic-architect.md

@@ -1,7 +1,7 @@
 ---
 name: agentic-architect
 description: Arquiteto do sistema agêntico EMBARCADO NO PRODUTO, na lane 3 (Arquitetura Mediada) — o comportamento que depende de modelo em runtime, invocado pelo usuário final e pago por chamada. Transforma o Ciclo aprovado da lane 2 em decisão sobre onde o produto usa modelo e onde não usa, qual modelo e com qual alternativa rejeitada, a forma de orquestração (chamada única, cadeia, laço de agente com ferramentas), o prompt como artefato versionado, o eval que diz se o comportamento está certo, as guardas e o que acontece quando o modelo falha ou erra. Produz ADR, RFC, parecer e os mapas de dead code e dual path do substrato agêntico (dois prompts para o mesmo comportamento, duas configurações de modelo que divergiram, ferramenta declarada que nada chama). Nasce SEM engenheiro par (D-096): o parecer declara para quem não há. Emite CONTESTAÇÃO quando a premissa está contradita pelo Ciclo ou pelo que roda — e para. NÃO use para os agentes, hooks e skills que a CASA opera (→ harness-architect), para endpoint, quota, custo e latência provisionados do modelo (→ infra-architect), para a forma do contrato de ferramenta (→ contract-architect), para o modelo de dados da memória do agente (→ datamodel-architect), para o domínio que o agente consome (→ backend-architect), nem para implementar.
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbSearch, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__kbListDocuments, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
+tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
 model: opus
 color: cyan
 permissionMode: acceptEdits

package/agents/architecture-mediator.md

@@ -1,7 +1,7 @@
 ---
 name: architecture-mediator
 description: Mediador da lane 3 (Arquitetura Mediada) — o JUIZ do leque-e-mediação, sem substrato e por isso sem sufixo -architect. Recebe as saídas que os arquitetos convocados produziram em paralelo e de forma independente a partir do mesmo Ciclo aprovado, ISOLA as divergências entre elas e DESEMPATA cada uma por medição — mutação-e-reversão nos dois sentidos, com o instrumento que responde à pergunta em disputa —, sem delegar o assert. Pode dar razão a um contra seis; ninguém vota. Produz o registro de mediação e a ADR/RFC mediada, e INSTRUMENTA a rodada (pares que podiam divergir, pares que divergiram, sessões gastas) para que o custo de mediação deixe de ser hipótese. Antes de publicar que um arquiteto errou, roda o instrumento que responde à pergunta DELE. Emite CONTESTAÇÃO quando a divergência não é desempatável por medição ou quando a premissa da rodada está contradita — e para. NÃO use para decidir substrato (→ o arquiteto do eixo), para aprovar o resultado mediado (é gate do orquestrador com o PM), para review adversarial de artefato (→ adversarial-reviewer), nem para implementar (→ o engenheiro do eixo).
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__orchestrator-tools__kbSearch, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__kbListDocuments, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
+tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
 model: opus
 color: red
 permissionMode: acceptEdits
@@ -9,6 +9,7 @@ skills:
   - arquitetura-mediada-arquiteto
   - kb-lookup
   - project-conventions
+  - archify
   - systematic-debugging
 ---
 

package/agents/backend-architect.md

@@ -1,7 +1,7 @@
 ---
 name: backend-architect
 description: Arquiteto de backend sênior da lane 3 (Arquitetura Mediada) — DONO DO MODELO CANÔNICO do domínio. Transforma o Ciclo aprovado da lane 2 em decisão de estrutura do lado servidor — bounded contexts, agregados com a raiz escolhida, entidades, value objects, invariantes, regras e eventos de domínio, casos de uso — e publica o modelo canônico que o frontend-architect consome e especializa declarando. Produz ADR, RFC, parecer e os mapas de dead code e dual path do backend; carrega Clean Architecture como CRITÉRIO DE VERIFICAÇÃO (com qual instrumento se prova que a dependência aponta para dentro), não como regra recitada. Use quando a decisão é sobre a estrutura do domínio e da aplicação do lado servidor. Emite CONTESTAÇÃO quando a premissa está contradita pelo Ciclo ou pelo código — e para. NÃO use para contrato de API/wire (→ contract-architect), schema e persistência (→ datamodel-architect), runtime/rede/IaC (→ infra-architect), sistema agêntico do produto (→ agentic-architect), estrutura do front (→ frontend-architect), harness (→ harness-architect), nem para implementar (→ implementer).
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_serena_serena__get_diagnostics_for_file, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbSearch, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__kbListDocuments, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
+tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_serena_serena__get_diagnostics_for_file, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
 model: opus
 color: blue
 permissionMode: acceptEdits

package/agents/contract-architect.md

@@ -1,7 +1,7 @@
 ---
 name: contract-architect
 description: Arquiteto de contrato sênior da lane 3 (Arquitetura Mediada) — DONO ÚNICO DO CONTRATO, dos dois lados do fio: a API que o backend expõe e o wire que o front consome. Transforma o Ciclo aprovado da lane 2 em decisão sobre o que atravessa a fronteira entre processos — operações, tipos de entrada e saída, envelope de erro, eventos e mensagens no fio, a fonte única de onde o tipo sai e a direção em que ele é gerado, e a política de versão e compatibilidade — e publica o contrato com id de versão, que backend-architect e frontend-architect consomem sem redeclarar. Existe para impedir o dual path do mesmo contrato, que é o mais comum que há. Produz ADR, RFC, parecer e o mapa de dual path de contrato, citando o instrumento pelo recorte que ele realmente tem. Sem engenheiro par na primeira volta. Emite CONTESTAÇÃO quando a premissa está contradita pelo Ciclo ou pelo código — e para. NÃO use para o domínio atrás do contrato (→ backend-architect), a estrutura do front (→ frontend-architect), schema e persistência (→ datamodel-architect), política de borda — gateway, rate limit, auth na borda (→ infra-architect), o uso que um agente do produto faz de uma tool (→ agentic-architect), contratos cujo consumidor é agente da casa — tools MCP do harness, JSON de hook (→ harness-architect), nem para implementar (→ implementer / frontend-engineer).
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_serena_serena__get_diagnostics_for_file, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbSearch, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__kbListDocuments, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
+tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_serena_serena__get_diagnostics_for_file, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
 model: opus
 color: yellow
 permissionMode: acceptEdits

package/agents/datamodel-architect.md

@@ -1,7 +1,7 @@
 ---
 name: datamodel-architect
 description: Arquiteto de modelo de dados sênior da lane 3 (Arquitetura Mediada) — DONO DO MODELO DE PERSISTÊNCIA. Transforma o Ciclo aprovado da lane 2 e o modelo canônico do backend-architect em decisão sobre como os dados são guardados — schema, tabelas e coleções, chaves, constraints, índices, a fronteira de transação, a estratégia de migração e o ciclo de vida do dado (retenção, histórico, exclusão) — e publica o MAPEAMENTO escrito entre o modelo de domínio e o de persistência, citando a versão do canônico. "datamodel" = banco de dados, nunca "modelo" no sentido de LLM. Produz ADR, RFC, parecer e os mapas de dead code e dual path de dados. Sem engenheiro par na primeira volta. Emite CONTESTAÇÃO quando a premissa está contradita pelo Ciclo, pelo canônico ou pelo schema vivo — e para. NÃO use para o modelo de domínio — entidades, agregados, invariantes (→ backend-architect), a forma do contrato (→ contract-architect), provisionamento do banco — instância, backup, rede, réplica (→ infra-architect), o uso que um agente do produto faz de memória e vetores (→ agentic-architect), os stores do próprio harness (→ harness-architect, com a dúvida ao architecture-mediator), pipelines ETL (→ python-data-engineer), documentar schema de legado alheio (→ schema-extractor), nem para implementar (→ implementer).
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_serena_serena__get_diagnostics_for_file, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbSearch, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__kbListDocuments, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
+tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_serena_serena__get_diagnostics_for_file, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
 model: opus
 color: green
 permissionMode: acceptEdits

package/agents/frontend-architect.md

@@ -1,7 +1,7 @@
 ---
 name: frontend-architect
 description: Arquiteto de frontend sênior da lane 3 (Arquitetura Mediada) — decide a estrutura do lado cliente a partir do Ciclo aprovado da lane 2 — fronteiras de componente, estado (onde mora cada verdade), fluxo e navegação (wizard, retomada, offline) e o domínio de tela (entidades, invariantes e casos de uso que existem no front). CONSOME o modelo canônico do backend-architect e ESPECIALIZA para a tela DECLARANDO cada especialização, nunca implicitamente; consome o contrato do contract-architect sem redefinir o tipo. Produz ADR, RFC, parecer e os mapas de dead code e dual path do front; carrega Clean Architecture como CRITÉRIO DE VERIFICAÇÃO, não como regra recitada. Use quando a decisão é sobre a estrutura do front, não sobre a tela pronta. Emite CONTESTAÇÃO quando a premissa está contradita pelo Ciclo ou pelo código — e para. NÃO use para o modelo canônico do domínio (→ backend-architect), a forma do contrato (→ contract-architect), hosting/CDN/deploy (→ infra-architect), mudança no Design System em si, nem para autoria de tela e componente (→ frontend-engineer).
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_serena_serena__get_diagnostics_for_file, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbSearch, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__kbListDocuments, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
+tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__find_declaration, mcp__plugin_serena_serena__find_implementations, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_serena_serena__get_diagnostics_for_file, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
 model: opus
 color: green
 permissionMode: acceptEdits

package/agents/harness-architect.md

@@ -1,7 +1,7 @@
 ---
 name: harness-architect
 description: Arquiteto sênior do HARNESS — hooks, skills, agentes, servidores MCP, plugin/distribuição e integrações com ferramentas externas (Pane, Graphify, Serena, Playwright). Produz ADR e RFC do lado harness, especifica agentes e skills novos, e avalia adoção de ferramenta CONTRA A LACUNA MEDIDA que ela alega fechar — nunca contra entusiasmo ou demo. Orça o custo próprio deste substrato — definição nova só fica viva depois de release + update, e somar definição mexe em contagens espalhadas pelo repo — e cita o harness-engineer, dono do procedimento, em vez de executá-lo; sabe que o harness tem superfícies que discordam entre si. Na lane 3 (Arquitetura Mediada) senta na mesa quando a task toca o harness, lendo o Ciclo aprovado da lane 2 como os outros arquitetos. Use quando a decisão é sobre o que intercepta, carrega, roteia ou distribui comportamento de agente. Emite CONTESTAÇÃO quando a premissa da task está contradita pela medição — e para. O substrato dele é o tooling que a casa OPERA, não o produto que a casa ENTREGA. NÃO use para código de aplicação, API, domínio ou infra do produto (→ backend-architect / contract-architect / infra-architect), para executar o procedimento de somar definição, bumpar contagem ou fazer release (→ harness-engineer), implementação de task (→ implementer), IaC Azure (→ azure-devops-engineer), CI/containers (→ cicd-platform-engineer), nem para sistema agêntico embarcado no produto entregue (modelo em runtime, invocado por usuário final, pago por chamada) — esse substrato é do agentic-architect.
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbSearch, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__kbListDocuments, mcp__orchestrator-tools__listAgentDefinitions, mcp__orchestrator-tools__getAgentDefinition, mcp__orchestrator-tools__listSkillDefinitions, mcp__orchestrator-tools__getSkillDefinition, mcp__orchestrator-tools__listHooks, mcp__orchestrator-tools__getHook, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
+tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__listAgentDefinitions, mcp__orchestrator-tools__getAgentDefinition, mcp__orchestrator-tools__listSkillDefinitions, mcp__orchestrator-tools__getSkillDefinition, mcp__orchestrator-tools__listHooks, mcp__orchestrator-tools__getHook, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
 model: opus
 color: purple
 permissionMode: acceptEdits

package/agents/infra-architect.md

@@ -1,7 +1,7 @@
 ---
 name: infra-architect
 description: Arquiteto de infraestrutura sênior da lane 3 (Arquitetura Mediada) — decide ONDE e COMO o produto roda. Transforma o Ciclo aprovado da lane 2 em decisão sobre runtime e topologia de execução, rede e borda (gateway, rate limit, auth na borda), identidade de workload e segredos, provisionamento de banco e de endpoint de modelo, ambientes e promoção entre eles, pipeline de build e deploy, observabilidade e a configuração que o código lê — publicada como contrato declarado. "infra", não "cloud": nuvem é um caso de infra. Produz ADR, RFC, parecer e os mapas de dead code e dual path de infra. É o único eixo com DOIS engenheiros, e o charter diz a qual vai o quê: azure-devops-engineer (tudo que toca API ou recurso Azure) e cicd-platform-engineer (container, CI e git cloud-agnósticos). Emite CONTESTAÇÃO quando a premissa está contradita pelo Ciclo ou pelo que está provisionado — e para. NÃO use para a estrutura do código (→ backend-architect / frontend-architect), a forma do contrato (→ contract-architect), o schema (→ datamodel-architect), escolha de modelo e orquestração do agente do produto (→ agentic-architect), distribuição do plugin e pipeline de release da casa (→ harness-architect), nem para implementar (→ azure-devops-engineer / cicd-platform-engineer).
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__plugin_microsoft-docs_microsoft-learn__microsoft_docs_search, mcp__plugin_microsoft-docs_microsoft-learn__microsoft_docs_fetch, mcp__orchestrator-tools__kbSearch, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__kbListDocuments, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
+tools: Read, Edit, Write, Bash, Grep, Glob, Agent, mcp__plugin_serena_serena__find_symbol, mcp__plugin_serena_serena__find_referencing_symbols, mcp__plugin_serena_serena__get_symbols_overview, mcp__plugin_serena_serena__search_for_pattern, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs, mcp__plugin_microsoft-docs_microsoft-learn__microsoft_docs_search, mcp__plugin_microsoft-docs_microsoft-learn__microsoft_docs_fetch, mcp__orchestrator-tools__kbGetDocument, mcp__orchestrator-tools__startAgentInvocation, mcp__orchestrator-tools__completeAgentInvocation, mcp__orchestrator-extended__artifactStore, mcp__orchestrator-extended__artifactRetrieve
 model: opus
 color: orange
 permissionMode: acceptEdits

package/manifest.json

@@ -1,8 +1,8 @@
 {
   "schema": "orchestrator-definitions/v1",
   "namespace": "orchestrator",
-  "version": "3.38.0",
-  "generatedAt": "2026-09-24T18:09:21.408Z",
+  "version": "3.40.0",
+  "generatedAt": "2026-09-25T13:12:10.970Z",
   "definitions": {
     "agents": [
       {
@@ -17,7 +17,7 @@
         "slug": "agentic-architect",
         "file": "agents/agentic-architect.md",
         "version": "1.0.0",
-        "checksum": "sha256:8e59be6bdaddc848db04f161318f9ecb40952341dc1e590a2ced342cd15aa46c",
+        "checksum": "sha256:0d4f1c8d5babbd1a1a204778dfe67d7db55d809fbaefa8dc74015a8650df39ed",
         "supersedes": null,
         "metadata": {}
       },
@@ -33,7 +33,7 @@
         "slug": "architecture-mediator",
         "file": "agents/architecture-mediator.md",
         "version": "1.0.0",
-        "checksum": "sha256:078045ce3d9c55d5c931a8def5ef571c566200513160c2801bdc6e409e715647",
+        "checksum": "sha256:c72668aee1556e527289820caa2c4a9066f21a3760183f5862093b9360728397",
         "supersedes": null,
         "metadata": {}
       },
@@ -49,7 +49,7 @@
         "slug": "backend-architect",
         "file": "agents/backend-architect.md",
         "version": "1.0.0",
-        "checksum": "sha256:491bded03d17d5a0fcd9314759c1a1d011596f22a9e27c1b3465ee67cf88f11a",
+        "checksum": "sha256:af734c97ef76784444926d4f947432de0a712eb3fef977ce82801818e24fcc8c",
         "supersedes": null,
         "metadata": {}
       },
@@ -89,7 +89,7 @@
         "slug": "contract-architect",
         "file": "agents/contract-architect.md",
         "version": "1.0.0",
-        "checksum": "sha256:635ca408fe1ae628491ad9cdf0c7b6b05e35dbd03ca8d811ae6b916861e98a4c",
+        "checksum": "sha256:b2ff958105a0d236378c6e182478679e93269fe1aa4805d282583482890bc81e",
         "supersedes": null,
         "metadata": {}
       },
@@ -97,7 +97,7 @@
         "slug": "datamodel-architect",
         "file": "agents/datamodel-architect.md",
         "version": "1.0.0",
-        "checksum": "sha256:5ca8eb6cc693f274ca62dd4c9907eb9652d53f94089d393625a734a51bfbb8c6",
+        "checksum": "sha256:63e1411a88d0e156476bd80b2f7c8b080cd12f433e71d765b3836c1a61558b40",
         "supersedes": null,
         "metadata": {}
       },
@@ -129,7 +129,7 @@
         "slug": "frontend-architect",
         "file": "agents/frontend-architect.md",
         "version": "1.0.0",
-        "checksum": "sha256:e2a9c3313852d275eef6f19917960788e3177d7c99d8ca64e51f98444971ce72",
+        "checksum": "sha256:bce5374534f92715606fd782f63a518398388d738119d152e495ce492c0a0fce",
         "supersedes": null,
         "metadata": {}
       },
@@ -145,7 +145,7 @@
         "slug": "harness-architect",
         "file": "agents/harness-architect.md",
         "version": "1.0.0",
-        "checksum": "sha256:e9d32c230d68eaac0377a0f402df3d90e59103551f833aaedb2fbde8e4e20d04",
+        "checksum": "sha256:d3dc897e15577053a6bdf8184e222a928c4fdf3d60f59124e790ae97fe870472",
         "supersedes": null,
         "metadata": {}
       },
@@ -169,7 +169,7 @@
         "slug": "infra-architect",
         "file": "agents/infra-architect.md",
         "version": "1.0.0",
-        "checksum": "sha256:fccaf3594c7e63326cf5bd1d2ac78c4e8da58d816cb4a12e9d8fe643cc42b90e",
+        "checksum": "sha256:7787eb178cb92d578800ba0a1fc80073ce42ab9524162e2e792d7b1d974a6dc7",
         "supersedes": null,
         "metadata": {}
       },
@@ -295,6 +295,14 @@
       }
     ],
     "skills": [
+      {
+        "slug": "archify",
+        "file": "skills/archify/SKILL.md",
+        "version": "1.0.0",
+        "checksum": "sha256:453c292c0201c03cae2bf1e91c2e4fde1b104bb53b3bda255b4d0004fdd701aa",
+        "supersedes": null,
+        "metadata": {}
+      },
       {
         "slug": "arquitetura-lane-dispatch",
         "file": "skills/arquitetura-lane-dispatch/SKILL.md",
@@ -307,7 +315,7 @@
         "slug": "arquitetura-mediada-arquiteto",
         "file": "skills/arquitetura-mediada-arquiteto/SKILL.md",
         "version": "1.0.0",
-        "checksum": "sha256:5966550b7f82767c1709260f1f131acb39e91b652aae048c7e17430d920a3c2b",
+        "checksum": "sha256:6f77a9ddb673948ae3a53d107df8010a2c7d4b51fa76320e309ddc255b2c44f2",
         "supersedes": null,
         "metadata": {}
       },
@@ -435,7 +443,7 @@
         "slug": "kb-api-pattern",
         "file": "skills/kb-api-pattern/SKILL.md",
         "version": "1.0.0",
-        "checksum": "sha256:e35f0d964eb1d55db648477443c0cbb44e5a87b642b3671325c2603b6bf12fb3",
+        "checksum": "sha256:67dbf72831c92fed9f3b04b8d8630032ffece3afcb84fc62aeec529d1ddabeff",
         "supersedes": null,
         "metadata": {}
       },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orchestrator-claude/definitions",
-  "version": "3.38.0",
+  "version": "3.40.0",
   "description": "Built-in definitions (agents, skills, hooks, workflows, KB seeds) for the Orchestrator ecosystem",
   "type": "module",
   "main": "dist/index.js",

package/skills/archify/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 tt-a1i (Archify)
+Copyright (c) 2025 Cocoon AI (original "architecture-diagram-generator")
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/archify/SKILL.md

@@ -0,0 +1,278 @@
+---
+name: archify
+description: Create professional architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as standalone HTML files with SVG graphics, a built-in dark/light theme toggle, and one-click export to PNG / JPEG / WebP / SVG. Accepts plain-language descriptions or pasted Mermaid code (flowchart, sequenceDiagram, stateDiagram) and lays the diagram out from scratch in archify style. Use when the user asks for system architecture diagrams, infrastructure diagrams, cloud architecture visualizations, security diagrams, network topology, technical workflows, approval flows, runbooks, CI/CD flows, process diagrams, API call sequences, request lifecycles, data pipelines, ETL/ELT maps, PII boundaries, data lineage, state machines, lifecycle diagrams, status transitions, or asks to convert/beautify a Mermaid diagram.
+license: MIT
+metadata:
+  version: "2.11"
+  author: tt-a1i
+  based_on: Cocoon-AI/architecture-diagram-generator (MIT, v1.0)
+---
+
+# Archify Skill
+
+Create professional technical diagrams as self-contained HTML files with inline SVG, a theme toggle, and a built-in image/SVG export menu.
+
+Every diagram ships with a **dark/light theme toggle** (persists in `localStorage`, respects `prefers-color-scheme`), an **export menu** (copy PNG to clipboard; download PNG/JPEG/WebP rasterized natively at up to 4× resolution; download a **dual-theme SVG** that follows the embedding host's `prefers-color-scheme` — ideal for GitHub READMEs), and a **CSS-variable color system** that keeps both themes consistent.
+
+## Setup
+
+No dependency installation is required. The distributed skill includes standalone validators compiled from all five JSON Schemas, so schema and layout validation work immediately after installation. The generated HTML and the renderer runtime are both dependency-free.
+
+Run `node bin/archify.mjs doctor` to verify an installation. Run `node bin/archify.mjs demo [output-directory]` to generate a ready-to-open example before creating the first custom diagram.
+
+If you have no shell access at all (e.g. the skill was added as project knowledge), fall back to architecture mode for every request: hand-place SVG into `assets/template.html` following the Design System below, and run the self-review checklist before delivering.
+
+## Choosing a Diagram Type
+
+| Type | Use for | How |
+|------|---------|-----|
+| `architecture` | System components, cloud resources, services, security boundaries, infrastructure | `renderers/architecture/render-architecture.mjs` + JSON (or hand-place SVG when renderers can't run) |
+| `workflow` | Technical flows, approval gates, tool calls, runbooks, CI/CD, incident response | `renderers/workflow/render-workflow.mjs` + JSON |
+| `sequence` | API call chains, request lifecycles, cache fallback, async traces, return paths | `renderers/sequence/render-sequence.mjs` + JSON |
+| `dataflow` | Pipelines, ETL/ELT, PII isolation, lineage, warehouse sync, consumers | `renderers/dataflow/render-dataflow.mjs` + JSON |
+| `lifecycle` | State machines, status transitions, wait states, retries, terminal states | `renderers/lifecycle/render-lifecycle.mjs` + JSON |
+
+Trigger phrases: "architecture/system/cloud diagram" → `architecture` (unless clearly process-oriented). "workflow/flow/process/runbook/approval/CI-CD/incident" → `workflow`. "sequence/interaction/call chain/who calls whom" → `sequence`. "data flow/pipeline/ETL/lineage/PII/governance" → `dataflow`. "state/status/lifecycle/state machine/retry/terminal" → `lifecycle`.
+
+## Mermaid as an Input Dialect
+
+When the user pastes Mermaid code, do NOT try to render or parse it mechanically — read it for structure and **lay out from scratch** in the matching archify mode:
+
+| Mermaid | Archify mode | Mapping |
+|---------|--------------|---------|
+| `flowchart` / `graph` | `workflow` (or `architecture` if it's a component map) | `subgraph` → lane or region boundary; node shape `{}` (diamond) → decision/security node; `-->` labels → edge labels (use sparingly); `classDef`/`style` → nearest semantic type |
+| `sequenceDiagram` | `sequence` | `participant` → participants (pick semantic `type` from the name); `->>` → message, `-->>` → `return` variant; `Note` → message `note`; `rect` blocks → segments |
+| `stateDiagram` | `lifecycle` | states → states (pick `start`/`active`/`waiting`/`success`/`failure` from names); `[*]` start/end → `start` type / `terminal` lane; transition labels → event-like labels |
+
+Drop Mermaid styling; keep only the topology and meaning. You choose grouping, lane order, and what deserves emphasis — that judgment is the product.
+
+## Layout principles (read before placing)
+
+Archify's readability comes from **spatial narrative**, not from drawing every dependency as an arrow. Before you write coordinates or edge lists, plan one clear story:
+
+1. **One main path** — left → right (architecture) or lane → column (workflow). The reader should trace the happy path without crossing lines.
+2. **Few labeled edges** — label only cross-boundary or non-obvious transitions on the main path. Adjacent steps stay unlabeled.
+3. **Short side branches** — permissions, storage, bots, CI: connect **up or down** from the nearest node on the main path. Never route a secondary edge diagonally across unrelated components.
+4. **Cards for detail** — policies, tech stack notes, and "also connects to X" belong in summary cards, not as extra arrows.
+5. **Mode fit** — process / approval / tool-call stories → `workflow` or `sequence`. Component maps with ≤12 nodes → `architecture`. If the diagram needs 20+ edges, remove edges until the main path is obvious.
+
+Worked examples on this pattern: `examples/archify-repo.architecture.json` (this repo) and `examples/maka-architecture.architecture.json` (third-party desktop app).
+
+When validation fails on label overlap, read the **Suggested fix** lines (coordinates / `labelAt` / `labelDy`) and apply them directly — do not guess offsets blindly.
+
+## Renderer Modes (architecture / workflow / sequence / dataflow / lifecycle)
+
+All five modes follow the same loop:
+
+1. **Read first**: the schema (`schemas/<type>.schema.json`) and the complete worked example (`examples/*.{architecture,workflow,sequence,dataflow,lifecycle}.json`) — copy its patterns instead of guessing field shapes.
+2. Write `<name>.<type>.json`.
+3. Render: `node bin/archify.mjs render <type> <input>.json <output>.html` (paths relative to this skill's folder).
+4. Validate the generated artifact: `node bin/archify.mjs validate <type> <input>.json --json`, or check an existing HTML file with `node bin/archify.mjs check <output>.html`. This catches malformed SVG output, non-finite SVG values, two-point diagonal arrows, and arrows crossing the legend.
+5. If either step fails, the error names the JSON path or the fix (thresholds, valid ranges, which knob to change). Fix the JSON and re-run; never edit the renderer.
+
+Schema violations exit non-zero with path-prefixed messages like `/nodes/3 (id/label: "router") must NOT have additional properties`. The renderers additionally fail fast on layout problems: node/state overlap (including cross-lane), labels colliding with nodes or other labels, labels wider than their node, out-of-range columns/rows, too-short edges, workflow edges crossing unrelated nodes, and legends outside the viewBox. CJK text is measured at double width automatically.
+
+Set `meta.animation: "trace"` only when the user asks for motion or a presentation/demo view. It adds lightweight SVG/CSS trace animation to renderer-marked arrows and nodes, respects `prefers-reduced-motion`, and leaves the default static output unchanged.
+
+### Workflow
+
+```json
+{
+  "schema_version": 1,
+  "diagram_type": "workflow",
+  "meta": { "title": "Release Workflow", "subtitle": "PR to production", "output": "release.html" },
+  "lanes": [ { "id": "dev", "label": "Developer" }, { "id": "ci", "label": "CI" }, { "id": "exceptions", "label": "Exception Handling", "variant": "exception" } ],
+  "phases": [ { "id": "intake", "label": "Intake", "fromCol": 0, "toCol": 1 } ],
+  "groups": [ { "id": "checks", "label": "Parallel checks", "lane": "ci", "fromCol": 1, "toCol": 3, "variant": "emphasis" } ],
+  "mainPath": ["pr", "build"],
+  "nodes": [
+    { "id": "pr", "lane": "dev", "col": 0, "type": "frontend", "label": "Open PR", "sublabel": "feature branch" },
+    { "id": "build", "lane": "ci", "col": 1, "type": "backend", "label": "Build", "sublabel": "lint + test", "tag": "blocking" }
+  ],
+  "edges": [
+    { "from": "pr", "to": "build", "label": "webhook", "variant": "emphasis", "fromSide": "bottom", "toSide": "top", "route": "drop" }
+  ],
+  "cards": []
+}
+```
+
+**Layout budget**: 6 columns (`col` 0–5) at fixed x positions `[88, 220, 300, 430, 500, 625]` — columns 1↔2 and 3↔4 are only 70–80px apart, so default-width (92px) nodes in those adjacent columns of the same lane overlap; skip a column or shrink `width`. Lane content width is 640px. Omit `meta.viewBox` — the renderer sizes height to the lane count automatically. Use `phases` for top-of-diagram story beats, `groups` to frame parallel work or a branch inside one lane, and `lane.variant: "exception"` for error/retry/fallback lanes. `mainPath` is optional but recommended: list the happy-path node ids in order so the renderer can catch missing edges or accidental backward movement. Edge routes: `straight`, `drop` (bend between lanes; `bias` 0–1 picks where), `outside-right`, `return-left`, `bottom-channel`, `up-channel`, or explicit `via` points. Keep adjacent-step edges unlabeled; reserve labels for cross-lane transitions, approvals, async traces, and returns.
+
+### Sequence
+
+```json
+{
+  "schema_version": 1,
+  "diagram_type": "sequence",
+  "meta": { "title": "Cache Miss Request", "subtitle": "auth and cache fallback", "output": "cache-miss.html" },
+  "participants": [
+    { "id": "web", "type": "frontend", "label": "Web App", "sublabel": "React UI" },
+    { "id": "api", "type": "backend", "label": "API", "sublabel": "handler" }
+  ],
+  "segments": [ { "from": 160, "to": 320, "label": "01 / AUTH" } ],
+  "messages": [
+    { "from": "web", "to": "api", "y": 200, "label": "GET /data", "variant": "emphasis" },
+    { "from": "api", "to": "web", "y": 290, "label": "200 JSON", "variant": "return" }
+  ],
+  "activations": [ { "participant": "api", "from": 190, "to": 300, "type": "backend" } ],
+  "cards": []
+}
+```
+
+**Layout budget**: participants sit at x = 62 + index×108, so a 920-wide viewBox fits at most 8. Message `y` must stay within `[160, viewBox_height − 83]`; messages that share horizontal space need ≥28px vertical separation; arrows need ≥60px horizontal span. `segments[].from/to` and `activations[].from/to` are **y pixel coordinates**, not participant ids. A taller `meta.viewBox` (default `[920, 760]`) buys more timeline room. Keep labels short: "GET /path", "verify JWT", "cache miss", "200 JSON".
+
+### Dataflow
+
+```json
+{
+  "schema_version": 1,
+  "diagram_type": "dataflow",
+  "meta": { "title": "Product Analytics", "subtitle": "events to consumers", "output": "analytics.html" },
+  "stages": [ { "label": "Sources" }, { "label": "Ingest" }, { "label": "Store" } ],
+  "nodes": [
+    { "id": "web", "type": "frontend", "label": "Web App", "stage": 0, "row": 0, "sublabel": "clickstream" },
+    { "id": "kafka", "type": "messagebus", "label": "Kafka", "stage": 1, "row": 0, "tag": "accepted events" }
+  ],
+  "flows": [
+    { "from": "web", "to": "kafka", "label": "events", "classification": "PII touch", "variant": "emphasis" }
+  ],
+  "cards": []
+}
+```
+
+**Layout budget**: 2–5 stages at x = 100 + stage×215; 5 rows (`row` 0–4) at y `[128, 242, 356, 470, 584]`; default node 112×58. Default viewBox `[940, 720]`. Flow labels are mandatory and asset-like ("clickstream", "identity map", "feature vectors"); put sensitivity in `classification` ("PII touch", "approved only", "non-PII"). Variants: `emphasis` = primary path, `security` = PII/policy/consent, `dashed` = async/batch.
+
+### Lifecycle
+
+```json
+{
+  "schema_version": 1,
+  "diagram_type": "lifecycle",
+  "meta": { "title": "Agent Run Lifecycle", "subtitle": "states and terminal outcomes", "output": "agent-run.html" },
+  "lanes": [
+    { "id": "main", "label": "Lifecycle phases" },
+    { "id": "waiting", "label": "Interruptions" },
+    { "id": "terminal", "label": "Terminal exits" }
+  ],
+  "states": [
+    { "id": "queued", "type": "start", "label": "Queued", "lane": "main", "col": 0, "step": "01" },
+    { "id": "running", "type": "active", "label": "Executing", "lane": "main", "col": 2, "step": "02" },
+    { "id": "approval", "type": "waiting", "label": "Needs Approval", "lane": "waiting", "col": 0 },
+    { "id": "done", "type": "success", "label": "Completed", "lane": "terminal", "col": 2 }
+  ],
+  "transitions": [
+    { "from": "queued", "to": "running", "variant": "emphasis" },
+    { "from": "running", "to": "approval", "label": "needs approval", "variant": "security", "fromSide": "bottom", "toSide": "right" },
+    { "from": "running", "to": "done", "label": "success", "variant": "emphasis", "fromSide": "bottom", "toSide": "top" }
+  ],
+  "cards": []
+}
+```
+
+**Layout budget — lane ids are semantic and reserved**: `main` is required and maps to the top phase band (cols 0–4); `terminal` maps to the bottom outcome band (cols 0–2); **every other lane id shares the single middle event band** (cols 0–2) — separate same-band states with different `col` or `yOffset`. Band headers render from your lane labels. Default viewBox `[980, 660]`. Keep transition labels event-like and sparse ("retry", "timeout", "cancel"); prefer state `tag`s, `step` numbers, and summary cards over label-heavy arrows. Put terminal states in the `terminal` lane so endings are unambiguous.
+
+### Per-mode deep guidance
+
+Each renderer has a README with its full design language (route presets, semantic types, story guidance): `renderers/workflow/README.md`, `renderers/sequence/README.md`, `renderers/dataflow/README.md`, `renderers/lifecycle/README.md`. Read the matching one before your first diagram of that mode in a session.
+
+## Architecture Mode
+
+Architecture has the same read-schema-then-render loop as the other modes — prefer it. Hand-placed SVG is the fallback for when renderers can't run.
+
+```json
+{
+  "schema_version": 1,
+  "diagram_type": "architecture",
+  "meta": { "title": "Sample Web App", "subtitle": "3-tier SaaS on AWS", "output": "web-app.html" },
+  "components": [
+    { "id": "users", "type": "external", "label": "Users", "sublabel": "Browser", "pos": [40, 300] },
+    { "id": "api", "type": "backend", "label": "API Server", "sublabel": "FastAPI :8000", "pos": [460, 300] },
+    { "id": "db", "type": "database", "label": "PostgreSQL", "sublabel": ":5432", "pos": [680, 300] }
+  ],
+  "boundaries": [
+    { "kind": "region", "label": "AWS us-west-2", "wraps": ["api", "db"] }
+  ],
+  "connections": [
+    { "from": "users", "to": "api", "label": "HTTPS", "variant": "emphasis" },
+    { "from": "api", "to": "db", "label": "SQL" }
+  ],
+  "cards": []
+}
+```
+
+Render: `node bin/archify.mjs render architecture <input>.json <output>.html`.
+
+**Free placement** — `pos: [x, y]` is the component's top-left; `size: [w, h]` defaults to `[120, 60]`. Unlike typed modes there is no lane/stage grid — asymmetric placement is yours to choose. `meta.viewBox` is optional (auto-fitted).
+
+**Grid placement (#8)** — when manual coordinates are painful, set semantic cells instead of doing arithmetic:
+
+```json
+{
+  "layout": { "mode": "grid", "cols": 7, "origin": [40, 100], "gapX": 24, "gapY": 48, "cellW": 120, "cellH": 60 },
+  "components": [
+    { "id": "agents", "type": "frontend", "label": "Agent Hosts", "row": 1, "col": 1 },
+    { "id": "ir", "type": "messagebus", "label": "JSON IR", "row": 1, "col": 2 }
+  ]
+}
+```
+
+`pos` still wins when present (override one cell). This is **not** auto-layout — spacing is fixed cell math. Example: `examples/archify-repo-grid.architecture.json`.
+
+**Inspect layout (#9)** — after editing JSON, dump computed boxes without opening HTML:
+
+```bash
+node bin/archify.mjs inspect architecture my.architecture.json
+# or: node bin/archify.mjs validate architecture my.architecture.json --layout-json
+```
+
+Output includes component rects, boundaries, connection point paths, and label positions.
+
+**The renderer does the mechanical work that used to be hand-tuned**, so you only choose coordinates and meaning:
+
+- **Free coordinates** — `pos: [x, y]` is the component's top-left; `size: [w, h]` defaults to `[120, 60]`. Unlike the typed modes there is no lane/stage grid — asymmetric placement is yours to choose. `meta.viewBox` is optional (auto-fitted to your components + a legend row).
+- **Grid placement** — optional `layout.mode: "grid"` with `row`/`col` per component (see above). Not dagre; fixed cell spacing only.
+- **Boundaries from `wraps`** — list the component ids a `region` (dashed amber) or `security-group` (dashed rose) encloses; the renderer computes the box with correct 30/50 padding automatically. Never hand-arithmetic a boundary again.
+- **Connections** route like edges (`variant`, `fromSide`/`toSide`, `route: straight|orthogonal-h|orthogonal-v|auto`, `via`, `labelDx/labelDy/labelAt`). For a vertical labeled connection, push the label into the gap with `labelDy` (the validator will tell you if it lands on a box).
+- The renderer auto-emits the two-rect `c-mask` pattern, draws arrows before boxes (z-order), builds the legend from the component types you used, and **fails fast on component overlap, off-canvas components/boundaries, unknown wraps/connection ids, label-vs-component collisions, and non-finite coordinates** — the same reliability the other four modes already had.
+
+### Hand-placed fallback (no renderer available)
+
+When Node/ajv can't run, copy `assets/template.html` and place SVG by hand. Study the worked diagram inside the template and `examples/web-app.html` for coordinate idioms, follow the Design System below, and run the self-review checklist before delivering.
+
+### The Cardinal Rule: CSS classes, not inline colors
+
+The theme toggle works by switching CSS custom properties. Hardcoded `fill="rgba(...)"` or `stroke="#22d3ee"` will NOT update on theme change. Always use the class system:
+
+```svg
+<rect x="X" y="Y" width="W" height="H" rx="6" class="c-mask"/>
+<rect x="X" y="Y" width="W" height="H" rx="6" class="c-backend" stroke-width="1.5"/>
+<text x="CX" y="CY" class="t-primary" font-size="11" font-weight="600" text-anchor="middle">API Server</text>
+<text x="CX" y="CY+16" class="t-muted" font-size="9" text-anchor="middle">FastAPI :8000</text>
+```
+
+### Design system
+
+Component fills `c-frontend` (clients/UI), `c-backend` (services/APIs), `c-database` (stores/caches), `c-cloud` (managed infra), `c-security` (auth/secrets), `c-messagebus` (Kafka/queues), `c-external` (3rd parties); text accents `t-<same>` plus neutrals `t-primary` / `t-muted` / `t-dim`. Arrows `a-default`, `a-emphasis` (hot path), `a-security` (dashed), `a-dashed` (async) — always set `stroke-width` and pair `marker-end="url(#arrowhead[-variant])"` with the matching class. Boundaries: `c-security-group` (dashed rose), `c-region` (dashed amber), `c-lane` (swimlane).
+
+Typography inherits JetBrains Mono from the SVG root. Sizes: 11–12px component names, 9px sublabels, 8px annotations, 7px tiny labels.
+
+### Hard layout rules
+
+- **Two-rect pattern everywhere**: opaque `c-mask` rect first, styled `c-<type>` rect on top — semi-transparent fills otherwise let arrows bleed through.
+- **Arrows before components** in document order (SVG paints in order; arrows must sit behind boxes).
+- **Vertical stacking**: ≥40px gap between components; inline connectors (message buses, 20px tall) live inside the gap, never overlapping boxes.
+- **Boundary padding**: boundary `y` = inner `y` − 30, boundary `height` = inner `height` + 50, label baseline 18px below the boundary top.
+- **Legend placement**: outside ALL boundary boxes, ≥20px below the lowest one; grow the viewBox if needed.
+
+### Self-review checklist (run before delivering)
+
+1. `grep -E 'fill="(#|rgb)|stroke="(#|rgb)' out.html` inside the SVG returns nothing except the template's own defs (Cardinal Rule).
+2. Every `c-<type>` rect has an identical-geometry `c-mask` rect immediately before it.
+3. All `<line>`/`<path>` arrows appear before all component rects in document order.
+4. Compute max(y + height) over all SVG elements: viewBox height must exceed it by ≥20px; same for x/width.
+5. Legend y is below every boundary's y + height.
+6. The `.toolbar`, `<script>` blocks, and `:root` / `[data-theme]` CSS are untouched — they ARE the theme toggle and export menu.
+
+## Output
+
+A single self-contained `.html`: embedded CSS (Google Fonts loads async and degrades to system monospace offline), inline SVG, ~19KB embedded JS for theme + export. It renders directly in any modern browser. Raster exports render natively at up to 4× the viewBox (large diagrams step down to 3×/2× to stay under canvas limits); the SVG download is dual-theme self-contained and follows the host's `prefers-color-scheme` (manual override via `svg[data-theme="..."]`).

package/skills/archify/VENDOR.txt

@@ -0,0 +1,70 @@
+VENDOR -- archify (skill de terceiro vendorizada no plugin orchestrator)
+=========================================================================
+
+Este arquivo e o UNICO arquivo deste diretorio que nao veio do upstream.
+Todo o resto e copia byte-a-byte e NAO deve ser editado aqui: correcao vai
+para o upstream, e a proxima vendorizacao traz.
+
+Por que .txt e nao .md: o gerador do manifest
+(packages/definitions/src/scripts/generate-manifest.ts, scanDirectory +
+scanSubDirectory) registra como definicao de skill TODO arquivo .md no
+primeiro nivel de skills/<slug>/ (e o caso de brainstorming/visual-companion.md).
+Um VENDOR.md viraria uma skill "VENDOR" no manifest e no seed. Um .txt fica
+fora do manifest e ainda viaja com o plugin e com o orch-defs install
+(Materializer.copySkillAssets copia os arquivos nao-manifestados).
+
+Origem
+------
+- repositorio:     https://github.com/tt-a1i/archify.git (github, tt-a1i/archify)
+- skillPath:       archify/SKILL.md
+- versao:          2.11 (SKILL.md metadata.version; package.json 2.11.0)
+- skillFolderHash: adf032ee538a5d9b08977bcf41246bb923fc5f42
+- instalada:       2026-07-18T17:10:52.539Z (~/.agents/.skill-lock.json)
+- vendorizada:     2026-09-24, S533, decisoes do PM D-183 (c) e D-187 (caminho C,
+                   mesmo nome bare "archify")
+- fonte local:     ~/.claude/skills/archify -> ~/.agents/skills/archify, copiada com
+                   `cp -rL` (46 arquivos, 0 symlinks, `diff -r` vazio)
+
+Verificacao do hash
+-------------------
+O skillFolderHash e o hash de ARVORE git da pasta upstream. Medido na
+vendorizacao: os 46 arquivos copiados, staged, dao
+`git write-tree --prefix=packages/definitions/skills/archify/` =
+adf032ee538a5d9b08977bcf41246bb923fc5f42, identico ao do lock. Para
+re-verificar depois do commit (exclui so este VENDOR.txt):
+
+  git ls-tree HEAD packages/definitions/skills/archify/ \
+    | grep -v 'VENDOR.txt$' \
+    | sed 's#packages/definitions/skills/archify/##' \
+    | git mktree
+
+Licenca
+-------
+MIT, com DOIS copyrights, ambos no LICENSE deste diretorio (intacto):
+- Copyright (c) 2026 tt-a1i (Archify)
+- Copyright (c) 2025 Cocoon AI (original "architecture-diagram-generator")
+O frontmatter da SKILL.md declara license: MIT e
+based_on: Cocoon-AI/architecture-diagram-generator (MIT, v1.0).
+
+Defeitos conhecidos do upstream (NAO corrigidos aqui)
+-----------------------------------------------------
+A SKILL.md cita arquivos em examples/ que nao existem no pacote. O pacote
+traz 5 exemplos: agent-run.lifecycle.json, agent-tool-call.workflow.json,
+cache-miss-request.sequence.json, product-analytics.dataflow.json,
+web-app.architecture.json. Citados e ausentes (medido na vendorizacao):
+- SKILL.md:59  examples/archify-repo.architecture.json
+- SKILL.md:59  examples/maka-architecture.architecture.json
+- SKILL.md:219 examples/archify-repo-grid.architecture.json
+- SKILL.md:240 examples/web-app.html
+
+Isolamento do conteudo vendorizado (medido na vendorizacao)
+-----------------------------------------------------------
+- test/*.test.mjs: nao sao coletados. O vitest da raiz inclui so *.test.ts em
+  tests/, src/**/__tests__, scripts/**/__tests__ e .claude/hooks/__tests__; o
+  de packages/definitions inclui so tests/**/*.test.ts. O `node --test` do
+  upstream so roda se alguem chamar o `npm test` DESTE diretorio.
+- package.json / package-lock.json: nao viram workspace. Os workspaces da raiz
+  sao `packages/*` (um nivel), e o `npm ci` da raiz nao le este lock.
+- Nenhuma dependencia de runtime: a SKILL.md declara que os validadores
+  compilados ja vem no pacote (renderers/shared/generated-validators.mjs); o
+  ajv e devDependency so para regenera-los.