sinapse-ai 1.16.0 → 1.17.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sinapse-ai",
-  "version": "1.16.0",
+  "version": "1.17.0",
   "description": "SINAPSE AI: Framework de orquestracao de IA — 17 squads, 172 agentes especializados",
   "bin": {
     "sinapse": "bin/sinapse.js",

package/packages/installer/src/wizard/ide-config-generator.js

@@ -539,6 +539,7 @@ async function copyClaudeHooksFolder(projectRoot) {
     'enforce-architecture-first.cjs',
     'enforce-delegation.cjs',
     'enforce-story-gate.cjs',
+    'doc-first-gate.cjs',
     'enforce-framework-boundary.cjs',
     'secret-scanning.cjs',
     'write-path-validation.cjs',
@@ -603,6 +604,11 @@ const HOOK_EVENT_MAP = {
     matcher: 'Write|Edit',
     timeout: 5,
   },
+  'doc-first-gate.cjs': {
+    event: 'PreToolUse',
+    matcher: 'Write|Edit',
+    timeout: 5,
+  },
   // Boundary L1-L4 — protects untouchable framework core when
   // boundary.frameworkProtection=true (read dynamically from core-config.yaml).
   'enforce-framework-boundary.cjs': {

package/scripts/install-chrome-brain.sh

@@ -504,8 +504,8 @@ Nao precisa rodar `chrome-debug` manualmente.
 3. Testar em nova aba → comparar com original → iterar
 
 **Casos validados:**
-- itsoffbrand.com hero (orb WebGL, parallax, blend-mode) — 15min
-- sinapse.club face 3D (Three.js r183, WaltHead.obj, bloom) — 20min
+- Hero com orb WebGL (parallax, blend-mode) — ~15min
+- Cena 3D facial (Three.js, modelo .obj, bloom) — ~20min
 
 ### Animacoes 3D via AI
 

package/scripts/validate-no-personal-leaks.js

@@ -106,12 +106,14 @@ const BLOCKED_PATTERNS = [
   {
     pattern: /C:\\Users\\Caio[ ]?Imori/i,
     description: 'Absolute Windows path containing maintainer name',
-    suggestion: 'Use {REPO_ROOT} placeholder or relative paths',
+    suggestion: 'Use {REPO_ROOT} placeholder, process.cwd(), or relative paths',
+    always: true, // a hardcoded personal path is never acceptable — even in archive/allowlisted files
   },
   {
     pattern: /OneDrive[\\/].*Caio[ ]?Imori/i,
     description: 'OneDrive path containing maintainer name',
     suggestion: 'Remove or use {VAULT_ROOT} placeholder',
+    always: true, // a personal vault path is never acceptable anywhere
   },
   {
     pattern: /Caio can (reactivate|activate|approve|reject|merge|deploy)/i,
@@ -135,7 +137,15 @@ function isAllowed(filePath) {
 // real leak. Everything else (framework internals, squad agents, internal
 // docs) is intentionally OUT of scope.
 const CONCEPT_FILE_SCOPES = new Set(['README.md', 'docs/getting-started.md']);
-const CONCEPT_PREFIX_SCOPES = ['packages/installer/', 'bin/', 'docs/pt/', 'docs/en/'];
+// The atlas SOURCE (hand-authored "how SINAPSE works" flows/renderers) is a
+// public surface and must describe the framework generically — never naming the
+// maintainer's private grounding (Second Brain vault, personal/client DS). Only
+// the source is scoped here, NOT the generated output (docs/framework/atlas/*),
+// which aggregates squad/workflow descriptions that legitimately use generic
+// deliverable terms like "brandbook".
+const CONCEPT_PREFIX_SCOPES = [
+  'packages/installer/', 'bin/', 'docs/pt/', 'docs/en/', '.sinapse-ai/core/atlas/',
+];
 
 function isConceptScoped(filePath) {
   const normalized = filePath.replace(/\\/g, '/');
@@ -161,9 +171,9 @@ const CONCEPT_PATTERNS = [
     suggestion: 'Describe generically (e.g. "a session-start grounding hook") — do not name the private mechanism',
   },
   {
-    pattern: /\bsecond-brain\b/i,
-    description: "Maintainer's private knowledge base (Second-Brain) leaked to user-facing surface",
-    suggestion: 'Generalize to "external memory source (e.g. an Obsidian vault)"',
+    pattern: /\bsecond[ -]brain\b/i,
+    description: "Maintainer's private knowledge base (Second Brain) leaked to user-facing surface",
+    suggestion: 'Generalize to "knowledge base" / "external memory source" — do not name the private vault',
   },
   {
     pattern: /\bbrandbook\b/i,
@@ -244,7 +254,7 @@ function getTrackedFiles() {
   return out.split('\n').filter(Boolean);
 }
 
-function scanFile(filePath) {
+function scanFile(filePath, rules = BLOCKED_PATTERNS) {
   const fullPath = path.join(ROOT, filePath);
   if (!fs.existsSync(fullPath)) return [];
   const content = fs.readFileSync(fullPath, 'utf8');
@@ -252,7 +262,7 @@ function scanFile(filePath) {
   const violations = [];
   for (let i = 0; i < lines.length; i++) {
     const line = lines[i];
-    for (const rule of BLOCKED_PATTERNS) {
+    for (const rule of rules) {
       const match = line.match(rule.pattern);
       if (match) {
         violations.push({
@@ -278,9 +288,14 @@ function run() {
     if (!isTextFile(file)) continue;
 
     // CHECK 1 — operational personal references ("Caio" literals, paths).
-    // Scanned across the whole tree except the autorship/history allow-list.
+    // `always` patterns (hardcoded personal/vault paths) are checked on EVERY
+    // file — they are never acceptable, not even in archive/allowlisted docs.
+    // The remaining patterns are scanned across the tree except the
+    // authorship/history allow-list.
+    const alwaysRules = BLOCKED_PATTERNS.filter((r) => r.always);
+    allViolations.push(...scanFile(file, alwaysRules));
     if (!isAllowed(file)) {
-      allViolations.push(...scanFile(file));
+      allViolations.push(...scanFile(file, BLOCKED_PATTERNS.filter((r) => !r.always)));
     }
 
     // CHECK 2 — conceptual / business leaks, scoped ONLY to user-facing

package/squads/squad-copy/knowledge-base/consequence-headline-patterns.md

@@ -43,7 +43,7 @@ Quem entender antes, captura a vantagem. Cria urgencia sem ser explicitamente ur
 - "...enquanto a maioria ainda nao percebeu"
 - "...e por que os que entenderam primeiro nao voltam atras"
 
-## Padroes de Hook para Social (Soier-inspired)
+## Padroes de Hook para Social
 
 ### Para conteudo curto (Reels, Stories, Carrossel)
 
@@ -55,7 +55,7 @@ Quem entender antes, captura a vantagem. Cria urgencia sem ser explicitamente ur
 | **Mini-alerta** | "Se voce ainda faz [X] manualmente, leia isso." | Urgencia pratica |
 | **Numero concreto** | "Reduzi 40h/mes de operacao para 6h com este workflow." | Prova quantificavel |
 
-### Regras de compressao (Soier-inspired)
+### Regras de compressao
 
 - **Uma ideia por peca** — se precisa de "alem disso", e outra peca
 - **Hook entendido em 2 segundos** — se precisa reler, e longo demais

package/docs/guides/hooks-two-layers.md

@@ -1,66 +0,0 @@
-# Hooks: arquitetura de duas camadas
-
-O SINAPSE-AI tem hooks em dois lugares distintos. Isso é proposital, não bug. Esta nota documenta a separação pra evitar confusão futura (auditoria 2026-05-25 BUG-013).
-
-## Camada 1: hooks globais do user (`~/.claude/hooks/`)
-
-**Escopo:** Toda sessão Claude Code do Caio, em qualquer projeto.
-
-**18 hooks .cjs:**
-
-| Hook | Evento | Função |
-|---|---|---|
-| `unified-grounding.cjs` | UserPromptSubmit | Único entry point. Funde 4 geradores: vault-grounding, ds-grounding, build-best-practices, squad-grounding |
-| `vault-grounding.cjs` | gerador (chamado por unified) | Injeta notas do Second Brain por domínio |
-| `ds-anti-pattern-guard.cjs` | PostToolUse | Bloqueia Write/Edit com violações DS (C1-C9) |
-| `build-best-practices.cjs` | gerador | Injeta playbook de construção do Caio |
-| `squad-grounding-router.cjs` | gerador | Detecta squad ativo, injeta DS relacionado |
-| `workspace-routing.cjs` | PreToolUse Bash | Reescreve mkdir/git init fora do Workspace pra path canônico |
-| `vault-project-register.cjs` | PostToolUse Bash | Registra projeto novo no vault |
-| `session-capture.cjs` + `session-capture-worker.cjs` | SessionStart/End | Captura sessões pro cronjob 2:30 BRT enrichment |
-| `auto-checkpoint.cjs` | UserPromptSubmit | Cria checkpoints periódicos |
-| `precompact-session-digest.cjs` | PreCompact | Resume sessão antes de compactar |
-| `code-intel-pretool.cjs` | PreToolUse | Code intelligence prep |
-| `healthcheck.cjs` | manual | Diagnostico setup |
-| `repair.cjs` | manual | Auto-fix problemas |
-| `synapse-engine.cjs` | UserPromptSubmit (subset) | Motor synapse legacy |
-| `terminal-bus.cjs` | UserPromptSubmit | Cross-terminal messaging |
-
-**Registrados em `~/.claude/settings.json`:** unified-grounding, session-capture, auto-checkpoint, workspace-routing, vault-project-register, ds-anti-pattern-guard, build-best-practices, chrome-ensure, chrome-brain-log.
-
-**Não-registrados (presentes mas sem entry em settings):** code-intel-pretool, healthcheck, repair, precompact-session-digest, synapse-engine. Estes são executados manualmente ou via fluxo específico.
-
-## Camada 2: hooks do framework (`<repo>/.claude/hooks/`)
-
-**Escopo:** Apenas quando Claude Code está rodando dentro de um repo SINAPSE-AI.
-
-**Hooks principais:**
-
-| Hook | Evento | Função |
-|---|---|---|
-| `enforce-architecture-first.cjs` | UserPromptSubmit | Bloqueia geração de código sem arquitetura validada |
-| `enforce-delegation.cjs` | UserPromptSubmit | Força orchestrators a delegar pra specialists |
-| `enforce-nsn-guard.cjs` | UserPromptSubmit | NSN mode: bloqueia "não dá pra fazer" sem 3 tentativas |
-| `enforce-story-gate.cjs` | UserPromptSubmit | Bloqueia código sem story Ready |
-| `secret-scanning.cjs` | PreToolUse | Detecta secrets em arquivos antes de commit |
-| `ids-hook.cjs` | PreToolUse | Mantém install-manifest.yaml sincronizado |
-
-**Por que separados:** rules do framework (documentation-first, mandatory-delegation, workflow-execution) só fazem sentido dentro de um repo SINAPSE-AI. Aplicar globalmente em todo projeto pequeno seria over-engineering.
-
-## Como decidir onde colocar um hook novo
-
-| Hook deve rodar em... | Lugar |
-|---|---|
-| Toda sessão do Caio, qualquer projeto | `~/.claude/hooks/` |
-| Apenas dentro de repos SINAPSE-AI | `<repo>/.claude/hooks/` |
-| Toda sessão MAS com config diferente por projeto | `~/.claude/hooks/` + lê config local (`.claude/config.json` do projeto) |
-
-## Não duplicar
-
-Se um hook precisa rodar em ambas as camadas, criar em uma e o outro lugar **carrega** o primeiro. Não copy-paste. Exemplo: workspace-routing vive em `~/.claude/hooks/` e qualquer projeto que precisar usa via reference.
-
-## Refs
-
-- `~/.claude/settings.json` — registro dos hooks globais
-- `<repo>/.claude/settings.json` — registro dos hooks do framework
-- Auditoria que gerou esta nota: `docs/audits/2026-05-25-framework-gargalos-audit.md` (BUG-013)