conectese 0.1.14

package/dashboard/src/styles/globals.css

@@ -0,0 +1,36 @@
+*,
+*::before,
+*::after {
+  margin: 0;
+  padding: 0;
+  box-sizing: border-box;
+}
+
+:root {
+  --bg-primary: #101018;
+  --bg-secondary: #1a1a2e;
+  --bg-sidebar: #141422;
+  --border: #2a2a3e;
+  --text-primary: #e0e0e0;
+  --text-secondary: #8888a0;
+  --accent-cyan: #00d4ff;
+  --accent-green: #00e676;
+  --accent-amber: #ffab00;
+  --accent-red: #ff5252;
+}
+
+html,
+body,
+#root {
+  height: 100%;
+  width: 100%;
+  overflow: hidden;
+  font-family: "JetBrains Mono", "Fira Code", monospace;
+  background: var(--bg-primary);
+  color: var(--text-primary);
+}
+
+@keyframes pulse {
+  0%, 100% { opacity: 1; }
+  50% { opacity: 0.4; }
+}

package/dashboard/src/types/state.ts

@@ -0,0 +1,63 @@
+// state.json structure — matches Pipeline Runner output
+export interface AgentDesk {
+  col: number;
+  row: number;
+}
+
+export type AgentStatus =
+  | "idle"
+  | "working"
+  | "delivering"
+  | "done"
+  | "checkpoint";
+
+export interface Agent {
+  id: string;
+  name: string;
+  icon: string;
+  status: AgentStatus;
+  gender?: "male" | "female";
+  desk: AgentDesk;
+}
+
+export interface Handoff {
+  from: string;
+  to: string;
+  message: string;
+  completedAt: string;
+}
+
+export type SquadStatus =
+  | "idle"
+  | "running"
+  | "completed"
+  | "checkpoint";
+
+export interface SquadState {
+  squad: string;
+  status: SquadStatus;
+  step: {
+    current: number;
+    total: number;
+    label: string;
+  };
+  agents: Agent[];
+  handoff: Handoff | null;
+  startedAt: string | null;
+  updatedAt: string;
+}
+
+// Squad metadata from squad.yaml
+export interface SquadInfo {
+  code: string;
+  name: string;
+  description: string;
+  icon: string;
+  agents: string[]; // agent file paths
+}
+
+// WebSocket messages
+export type WsMessage =
+  | { type: "SNAPSHOT"; squads: SquadInfo[]; activeStates: Record<string, SquadState> }
+  | { type: "SQUAD_UPDATE"; squad: string; state: SquadState }
+  | { type: "SQUAD_INACTIVE"; squad: string };

package/dashboard/src/vite-env.d.ts

@@ -0,0 +1 @@
+/// <reference types="vite/client" />

package/dashboard/test-results/.last-run.json

@@ -0,0 +1,4 @@
+{
+  "status": "failed",
+  "failedTests": []
+}

package/dashboard/tsconfig.json

@@ -0,0 +1,24 @@
+{
+  "compilerOptions": {
+    "target": "ES2020",
+    "useDefineForClassFields": true,
+    "lib": ["ES2020", "DOM", "DOM.Iterable"],
+    "module": "ESNext",
+    "skipLibCheck": true,
+    "moduleResolution": "bundler",
+    "allowImportingTsExtensions": true,
+    "isolatedModules": true,
+    "moduleDetection": "force",
+    "noEmit": true,
+    "jsx": "react-jsx",
+    "strict": true,
+    "noUnusedLocals": true,
+    "noUnusedParameters": true,
+    "noFallthroughCasesInSwitch": true,
+    "noUncheckedSideEffectImports": true,
+    "paths": {
+      "@/*": ["./src/*"]
+    }
+  },
+  "include": ["src"]
+}

package/dashboard/tsconfig.tsbuildinfo

@@ -0,0 +1 @@
+{"root":["./src/app.tsx","./src/main.tsx","./src/vite-env.d.ts","./src/components/squadcard.tsx","./src/components/squadselector.tsx","./src/components/statusbadge.tsx","./src/components/statusbar.tsx","./src/hooks/usesquadsocket.ts","./src/lib/formattime.ts","./src/lib/normalizestate.ts","./src/office/agentsprite.ts","./src/office/officescene.ts","./src/office/phasergame.tsx","./src/office/roombuilder.ts","./src/office/assetkeys.ts","./src/office/palette.ts","./src/plugin/squadwatcher.ts","./src/store/usesquadstore.ts","./src/types/state.ts"],"version":"5.9.3"}

package/dashboard/vite.config.ts

@@ -0,0 +1,13 @@
+import { defineConfig } from "vite";
+import react from "@vitejs/plugin-react";
+import path from "node:path";
+import { squadWatcherPlugin } from "./src/plugin/squadWatcher";
+
+export default defineConfig({
+  plugins: [react(), squadWatcherPlugin()],
+  resolve: {
+    alias: {
+      "@": path.resolve(__dirname, "./src"),
+    },
+  },
+});

package/package.json

@@ -0,0 +1,53 @@
+{
+  "name": "conectese",
+  "version": "0.1.14",
+  "description": "Multi-agent orchestration framework — create AI squads that work together",
+  "type": "module",
+  "bin": {
+    "conectese": "bin/conectese.js"
+  },
+  "scripts": {
+    "test": "node --test tests/*.test.js",
+    "lint": "eslint src/ bin/ tests/",
+    "version": "node -e \"require('fs').writeFileSync('templates/_conectese/.conectese-version', require('./package.json').version + '\\n')\" && git add templates/_conectese/.conectese-version"
+  },
+  "keywords": [
+    "claude-code",
+    "ai-agents",
+    "multi-agent",
+    "orchestration",
+    "squads"
+  ],
+  "author": "Renato Asse (https://github.com/renatoasse)",
+  "homepage": "https://github.com/renatoasse/conectese#readme",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/renatoasse/conectese.git"
+  },
+  "bugs": {
+    "url": "https://github.com/renatoasse/conectese/issues"
+  },
+  "license": "MIT",
+  "engines": {
+    "node": ">=20.0.0"
+  },
+  "files": [
+    "bin/",
+    "src/",
+    "agents/",
+    "skills/",
+    "templates/",
+    "_conectese/",
+    "dashboard/"
+  ],
+  "dependencies": {
+    "@inquirer/checkbox": "^5.1.0",
+    "@inquirer/input": "^5.0.0",
+    "@inquirer/select": "^5.1.0"
+  },
+  "devDependencies": {
+    "@eslint/js": "^10.0.1",
+    "eslint": "^10.0.3",
+    "globals": "^17.4.0"
+  }
+}

package/skills/README.md

@@ -0,0 +1,63 @@
+# Conectese Skill Catalog
+
+Browse available skills for your squads. Install any skill with:
+
+```bash
+npx conectese install <skill-name>
+```
+
+## Available Skills
+
+| Skill | Type | Description | Env Vars | Install |
+|-------|------|-------------|----------|---------|
+| [apify](./apify/) | mcp | Web scraping and automation platform. Extract data from any website using pre-built Actors. | `APIFY_TOKEN` | `npx conectese install apify` |
+| [canva](./canva/) | mcp | Create, search, autofill, and export designs from Canva. | _(none -- OAuth)_ | `npx conectese install canva` |
+| [instagram-publisher](./instagram-publisher/) | script | Publish Instagram carousel posts from local JPEG images via the Graph API. | `INSTAGRAM_ACCESS_TOKEN`, `INSTAGRAM_USER_ID` | `npx conectese install instagram-publisher` |
+| [blotato](./blotato/) | mcp | Publish and schedule posts across Instagram, LinkedIn, Twitter/X, TikTok, YouTube, and more. | `BLOTATO_API_KEY` | `npx conectese install blotato` |
+| [resend](./resend/) | mcp | Send emails through Resend — single send, batch, scheduling, attachments, and contact management. | `RESEND_API_KEY` | `npx conectese install resend` |
+| [image-fetcher](./image-fetcher/) | hybrid | Acquire visual assets via web search, live screenshots (Playwright), and user-provided files. | _(none)_ | `npx conectese install image-fetcher` |
+| [image-creator](./image-creator/) | mcp | Render HTML/CSS into production-ready PNG images via Playwright. | _(none)_ | `npx conectese install image-creator` |
+| [image-ai-generator](./image-ai-generator/) | script | Generate AI images via Openrouter API. Test mode (cheap) and production mode (high-quality). Supports reference images for brand consistency. | `OPENROUTER_API_KEY` | `npx conectese install image-ai-generator` |
+
+## Skill Types
+
+- **mcp** -- Connects to an external MCP server (stdio or HTTP transport)
+- **script** -- Runs a local script (Node.js, Python, etc.)
+- **hybrid** -- Combines MCP server access with local script capabilities
+
+## Directory Structure
+
+Each skill lives in its own folder with a `SKILL.md` file:
+
+```
+skills/
+  apify/
+    SKILL.md
+  canva/
+    SKILL.md
+  instagram-publisher/
+    SKILL.md
+    scripts/
+      publish.js
+  blotato/
+    SKILL.md
+  resend/
+    SKILL.md
+  image-fetcher/
+    SKILL.md
+  image-creator/
+    SKILL.md
+  image-ai-generator/
+    SKILL.md
+    scripts/
+      generate.py
+```
+
+The `SKILL.md` file contains YAML frontmatter (name, type, version, MCP/script config, env vars, categories) and a Markdown body with usage instructions and available operations.
+
+## Adding a New Skill
+
+1. Create a new folder under `skills/` with the skill ID as the name
+2. Add a `SKILL.md` file with valid YAML frontmatter and Markdown body
+3. If the skill includes scripts, place them in a `scripts/` subfolder
+4. Update this README to include the new skill in the catalog table

package/skills/apify/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: apify
+description: >
+  Web scraping and automation platform. Extract data from any website,
+  run pre-built scrapers (Actors), and automate web workflows using
+  thousands of ready-made tools from the Apify Store.
+description_pt-BR: >
+  Plataforma de web scraping e automação. Extraia dados de qualquer site,
+  execute scrapers prontos (Actors) e automatize fluxos de trabalho web
+  com milhares de ferramentas da Apify Store.
+description_es: >
+  Plataforma de web scraping y automatización. Extrae datos de cualquier sitio web,
+  ejecuta scrapers prediseñados (Actors) y automatiza flujos de trabajo web
+  con miles de herramientas de la Apify Store.
+type: mcp
+version: "1.0.0"
+mcp:
+  server_name: apify
+  command: npx
+  args: ["-y", "@apify/actors-mcp-server@latest"]
+env:
+  - APIFY_TOKEN
+categories: [scraping, data, automation]
+---
+
+# Apify Web Scraper
+
+## When to use
+
+Use Apify when you need to extract data from websites, scrape social media profiles, run search engine queries, or automate web data collection workflows. Apify provides thousands of pre-built scrapers (called Actors) that handle common scraping tasks out of the box.
+
+## Instructions
+
+You have access to Apify tools for web scraping and data extraction.
+
+### Key capabilities
+
+- Use Apify Actors (pre-built scrapers) to extract data from websites
+- Popular Actors: web-scraper, instagram-scraper, google-search-scraper, youtube-scraper, twitter-scraper, tiktok-scraper
+- Each Actor has its own input schema -- check documentation before running
+
+### Best practices
+
+- Start with the simplest Actor that meets the need
+- Use `maxItems` to limit results and avoid excessive costs
+- Check Actor pricing before running (some have per-result costs)
+- Parse results and extract only the fields you need
+
+## Available operations
+
+- **Run Actor** -- Execute any Apify Actor with custom input parameters
+- **Web Scraping** -- Extract structured data from any website
+- **Social Media Scraping** -- Scrape profiles, posts, and engagement data from Instagram, YouTube, Twitter/X, TikTok
+- **Search Scraping** -- Run Google, Bing, or other search engine queries and collect results
+- **Data Export** -- Retrieve scraped datasets in JSON format

package/skills/blotato/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: blotato
+description: >
+  Social media publishing and scheduling platform.
+  Publish and schedule posts across Instagram, LinkedIn, Twitter/X,
+  TikTok, YouTube, and more. Upload media and monitor post status.
+description_pt-BR: >
+  Plataforma de publicação e agendamento em redes sociais.
+  Publique e agende posts no Instagram, LinkedIn, Twitter/X,
+  TikTok, YouTube e mais. Faça upload de mídia e monitore o status dos posts.
+description_es: >
+  Plataforma de publicación y programación en redes sociales.
+  Publica y programa posts en Instagram, LinkedIn, Twitter/X,
+  TikTok, YouTube y más. Sube contenido multimedia y monitorea el estado de los posts.
+type: mcp
+version: "1.0.0"
+mcp:
+  server_name: blotato
+  transport: http
+  url: "https://mcp.blotato.com/mcp"
+  headers:
+    blotato-api-key: BLOTATO_API_KEY
+env:
+  - BLOTATO_API_KEY
+categories: [social-media, automation, publishing, scheduling]
+---
+
+# Blotato Publisher
+
+## When to use
+
+Use Blotato when you need to publish or schedule social media posts across multiple platforms from a single interface. Blotato supports Instagram, LinkedIn, Twitter/X, TikTok, YouTube, and more. It handles media uploads, post scheduling, and status monitoring.
+
+## Instructions
+
+You have access to Blotato for social media publishing.
+
+### Key workflow
+
+1. Use `blotato_list_accounts` to get account IDs and platforms
+2. If post includes images or videos, upload them with `blotato_upload_media` first and use the returned media IDs in `blotato_create_post`
+3. Use `blotato_create_post` to publish or schedule
+4. Use `blotato_get_post_status` to confirm success
+
+### Best practices
+
+- Always call `blotato_list_accounts` first to get valid account IDs
+- For scheduled posts, use ISO 8601 format for datetime
+- After posting, poll `blotato_get_post_status` until status is "published" or "scheduled"
+- If status is "failed", report the error details to the user
+
+### Requirements
+
+- Blotato account required (blotato.com)
+- API key must be configured (Blotato Settings > API section)
+
+## Available operations
+
+- **List Accounts** -- Retrieve connected social media accounts and their platform types
+- **Upload Media** -- Upload images and videos for use in posts
+- **Create Post** -- Publish or schedule a post to one or more platforms
+- **Get Post Status** -- Monitor publishing status (published, scheduled, failed)
+- **Multi-platform Publishing** -- Post the same content across Instagram, LinkedIn, Twitter/X, TikTok, YouTube simultaneously

package/skills/canva/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: canva
+description: >
+  Create, search, autofill, and export designs from Canva.
+  Enables agents to generate visual content, fill templates
+  with brand assets, and export in various formats.
+description_pt-BR: >
+  Crie, busque, preencha e exporte designs do Canva.
+  Permite que agentes gerem conteúdo visual, preencham templates
+  com assets da marca e exportem em diversos formatos.
+description_es: >
+  Crea, busca, completa y exporta diseños de Canva.
+  Permite que los agentes generen contenido visual, completen plantillas
+  con recursos de marca y exporten en diversos formatos.
+type: mcp
+version: "1.0.0"
+mcp:
+  server_name: canva
+  transport: http
+  url: "https://mcp.canva.com/mcp"
+categories: [design, ui, assets, automation]
+---
+
+# Canva Connect
+
+## When to use
+
+Use Canva when you need to create, search, or export visual designs. This skill connects to the user's Canva account via OAuth and enables agents to generate presentations, social media posts, logos, and other visual content. It also supports autofilling templates with brand assets and exporting designs in various formats.
+
+## Instructions
+
+You have access to Canva through the Canva Connect MCP server.
+
+### Key capabilities
+
+- Create new designs (presentations, social posts, logos, etc.)
+- Autofill templates with content (text, images, brand elements)
+- Search existing designs in the user's Canva account
+- Export designs as PDF or image files
+
+### Best practices
+
+- Use templates when possible -- faster and more on-brand
+- When autofilling, match content to template placeholder names
+- Export in the format most useful for the pipeline (PNG for social, PDF for documents)
+- Respect the user's Canva plan limitations (some features require paid plans)
+
+### Requirements
+
+- User needs a Canva account (free or paid)
+- OAuth authorization is required on first use (browser popup)
+- Autofill templates require a Canva paid plan
+
+## Available operations
+
+- **Create Design** -- Generate new designs from scratch or templates
+- **Search Designs** -- Find existing designs in the user's Canva account
+- **Autofill Template** -- Fill template placeholders with text, images, and brand elements
+- **Export Design** -- Export designs as PDF, PNG, JPG, or other formats
+- **Browse Templates** -- Search Canva's template library for the right starting point

package/skills/conectese-agent-creator/SKILL.md

@@ -0,0 +1,192 @@
+---
+name: "Best-Practice Creator"
+description: >
+  Guides creation and maintenance of best-practice files for the Conectese best-practices library.
+  Handles format validation, cross-references, versioning, and catalog consistency.
+description_pt-BR: >
+  Guia a criação e manutenção de arquivos de best-practice na biblioteca de best-practices do Conectese.
+  Cuida de validação de formato, referências cruzadas, versionamento e consistência do catálogo.
+description_es: >
+  Guía la creación y mantenimiento de archivos de best-practice en la biblioteca de best-practices de Conectese.
+  Maneja validación de formato, referencias cruzadas, versionamiento y consistencia del catálogo.
+type: prompt
+version: "2.0.0"
+---
+
+# Best-Practice Creator — Workflow
+
+Use this workflow when creating a new best-practice file for the `_conectese/core/best-practices/` library.
+
+## Pre-flight Checks
+
+1. **Scan existing best-practice files**: Read `_conectese/core/best-practices/_catalog.yaml`. Extract `id`, `name`, `whenToUse`, `file` from each entry.
+2. **Check for overlap**: Verify the new best-practice file doesn't duplicate an existing entry's `whenToUse` scope. If there's overlap, clarify the differentiation before proceeding.
+3. **List available skills**: Read all `skills/*/SKILL.md` files. Extract `name`, `description`, `type` from each — these may inform the best-practice file's content.
+
+## Creation Checklist
+
+For each new best-practice file, ensure ALL of the following:
+
+### Frontmatter (YAML)
+
+- [ ] `id`: lowercase kebab-case (e.g., `copywriting`)
+- [ ] `name`: Display name for catalog listing (e.g., `"Copywriting & Persuasive Writing"`)
+- [ ] `whenToUse`: Multi-line with positive scope AND "NOT for: ..." negative scope referencing other best-practice IDs
+- [ ] `version`: `"1.0.0"` for new best-practice files
+
+### Body (Markdown) — All sections mandatory
+
+- [ ] **Core Principles**: 6+ numbered domain-specific decision rules, each with a bold title and detailed explanation
+- [ ] **Techniques & Frameworks**: Concrete methods, models, or processes practitioners use in this discipline (e.g., diagnostic steps, framework selections, structural patterns)
+- [ ] **Quality Criteria**: 4+ checkable criteria as `- [ ]` list that can be used to evaluate output
+- [ ] **Output Examples**: 2+ complete examples, 15+ lines each, realistic NOT template-like
+- [ ] **Anti-Patterns**: Never Do (4+) + Always Do (3+), each with explanation
+- [ ] **Vocabulary Guidance**: Terms/phrases to Always Use (5+), Terms/phrases to Never Use (3+), Tone Rules (2+)
+
+### Quality Minimums
+
+| Section | Minimum |
+|---------|---------|
+| Total file lines | 200+ |
+| Core Principles | 6+ numbered rules |
+| Techniques & Frameworks | 3+ concrete techniques |
+| Vocabulary Always Use | 5+ terms |
+| Vocabulary Never Use | 3+ terms |
+| Output Examples | 2 complete, 15+ lines each |
+| Anti-Patterns (Never Do) | 4+ |
+| Anti-Patterns (Always Do) | 3+ |
+| Quality Criteria | 4+ checkable items |
+
+## Post-Creation Steps
+
+### 1. Update existing best-practice files' `whenToUse`
+
+For each existing best-practice file whose scope overlaps with the new one:
+- Add a "NOT for: {overlapping-scope} → See {new-best-practice-id}" line to their `whenToUse`
+- Bump their version (patch increment)
+
+### 2. Update `_catalog.yaml`
+
+Add a new entry to `_conectese/core/best-practices/_catalog.yaml` with:
+- `id`: matching the frontmatter `id`
+- `name`: matching the frontmatter `name`
+- `whenToUse`: single-line summary of the scope (positive only, no "NOT for")
+- `file`: `{id}.md`
+
+Place it under the appropriate section comment (Discipline or Platform best practices).
+
+### 3. File placement
+
+Save to `_conectese/core/best-practices/{id}.md`.
+
+### 4. Validation
+
+Re-read the created file and verify:
+- [ ] All checklist items above are present
+- [ ] YAML frontmatter parses correctly (no syntax errors)
+- [ ] `whenToUse` references only existing best-practice IDs
+- [ ] Output examples are realistic, not template placeholders
+- [ ] File exceeds 200 lines
+- [ ] Corresponding entry exists in `_catalog.yaml`
+
+---
+
+# Best-Practice Updater — Workflow
+
+Use this workflow when updating best-practice files in the `_conectese/core/best-practices/` library.
+
+## Versioning Rules (Semver)
+
+| Change Type | Version Bump | Examples |
+|-------------|-------------|----------|
+| **Patch** (x.x.X) | Fix typos, adjust wording, minor refinements | Fix anti-pattern phrasing, correct a vocabulary term |
+| **Minor** (x.X.0) | Add new content, extend capabilities | Add new principle, new output example, new technique |
+| **Major** (X.0.0) | Rewrite or restructure significantly | Rewrite core principles, fundamentally change scope |
+
+Always update the `version` field in the YAML frontmatter after any change.
+
+## Update Scenarios
+
+### When a best-practice file is removed from the library
+
+1. Get the removed best-practice file's `id`
+2. Remove its entry from `_conectese/core/best-practices/_catalog.yaml`
+3. Scan ALL remaining best-practice files in `_conectese/core/best-practices/*.md`
+4. For each file, check if the removed ID is referenced in `whenToUse`
+   - Look for patterns: "NOT for: ... → See {removed-id}"
+5. If found, remove that "NOT for" line
+6. Bump the affected files' version (patch: x.x.X)
+
+### When a new best-practice file is added to the library
+
+The Best-Practice Creator workflow (above) handles the initial `whenToUse` cross-references during creation. This section is only needed if cross-references were missed or need adjustment after the fact.
+
+1. Read the new best-practice file's `whenToUse` — identify its scope
+2. Scan existing best-practice files for overlapping scope
+3. Add "NOT for: {new-scope} → See {new-id}" where appropriate
+4. Bump affected files' version (patch)
+5. Ensure the new entry exists in `_catalog.yaml`
+
+### When updating a best-practice file's content
+
+1. Make the content changes
+2. Verify ALL mandatory sections still exist:
+   - [ ] Core Principles (6+ rules)
+   - [ ] Techniques & Frameworks (3+ techniques)
+   - [ ] Quality Criteria (4+ checkable items)
+   - [ ] Output Examples (2+ complete examples)
+   - [ ] Anti-Patterns (Never Do + Always Do)
+   - [ ] Vocabulary Guidance (Always Use, Never Use, Tone Rules)
+3. Bump version according to semver rules above
+4. If the `whenToUse` scope changed, update cross-references in other best-practice files and in `_catalog.yaml`
+
+### When updating a best-practice file's `whenToUse` scope
+
+This is the most impactful change — it affects how the Architect selects best practices during squad creation.
+
+1. Document the old scope and new scope
+2. Update the best-practice file's `whenToUse` field
+3. Scan ALL other best-practice files' `whenToUse` for references to this ID
+4. Update cross-references to reflect the new scope
+5. Update the `whenToUse` summary in `_catalog.yaml`
+6. Bump version (minor if scope expanded, patch if scope narrowed)
+
+## Validation Checklist
+
+After ANY update, verify:
+
+- [ ] Version was bumped correctly (patch/minor/major per rules above)
+- [ ] All mandatory sections still present and non-empty
+- [ ] `whenToUse` cross-references are consistent across ALL best-practice files
+- [ ] No broken cross-references to removed best-practice IDs
+- [ ] Output examples are still realistic and complete
+- [ ] File still exceeds 200 lines minimum
+- [ ] `_catalog.yaml` entry is in sync with frontmatter (`id`, `name`, `whenToUse`)
+
+## Bulk Operations
+
+### Verify catalog consistency
+
+```
+Read _conectese/core/best-practices/_catalog.yaml
+For each entry in catalog:
+  1. Verify _conectese/core/best-practices/{entry.file} exists
+  2. Read the file's frontmatter
+  3. Verify entry.id matches frontmatter id
+  4. Verify entry.name matches frontmatter name
+  5. Flag any mismatches
+
+For each .md file in _conectese/core/best-practices/ (excluding _catalog.yaml):
+  1. Verify a corresponding entry exists in _catalog.yaml
+  2. Flag any orphaned files with no catalog entry
+```
+
+### Verify cross-reference consistency
+
+```
+For each best-practice file A in _conectese/core/best-practices/*.md:
+  For each "NOT for: ... → See {id}" in A.whenToUse:
+    1. Verify _conectese/core/best-practices/{id}.md exists
+    2. Verify {id}'s whenToUse covers the referenced scope
+    3. Flag inconsistencies
+```