codebeacon 0.1.3__tar.gz → 0.1.4__tar.gz

{codebeacon-0.1.3 → codebeacon-0.1.4}/.github/workflows/ci.yml

@@ -16,9 +16,9 @@ jobs:
         python-version: ["3.10", "3.11", "3.12"]
 
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v6
 
-      - uses: actions/setup-python@v5
+      - uses: actions/setup-python@v6
         with:
           python-version: ${{ matrix.python-version }}
           cache: "pip"

{codebeacon-0.1.3 → codebeacon-0.1.4}/.github/workflows/release.yml

@@ -10,9 +10,9 @@ jobs:
     name: Build distribution
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v6
 
-      - uses: actions/setup-python@v5
+      - uses: actions/setup-python@v6
         with:
           python-version: "3.12"
 
@@ -23,7 +23,7 @@ jobs:
         run: python -m build
 
       - name: Upload dist artifacts
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: dist
           path: dist/
@@ -40,7 +40,7 @@ jobs:
 
     steps:
       - name: Download dist artifacts
-        uses: actions/download-artifact@v4
+        uses: actions/download-artifact@v8
         with:
           name: dist
           path: dist/

{codebeacon-0.1.3 → codebeacon-0.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codebeacon
-Version: 0.1.3
+Version: 0.1.4
 Summary: Source code AST analysis tool for AI context generation — unified multi-framework knowledge graph
 Project-URL: Homepage, https://github.com/codebeacon/codebeacon
 Project-URL: Repository, https://github.com/codebeacon/codebeacon
@@ -89,6 +89,7 @@ Existing tools solve this partially. Route analyzers map your controllers but mi
 - **Community detection** — Leiden/Louvain clustering reveals your actual architectural boundaries
 - **Incremental cache** — SHA-256 based; only re-extracts files that changed since the last scan
 - **Zero configuration** — auto-detects frameworks and languages; generates `codebeacon.yaml` for repeat runs
+- **Deep-dive mode** — `--deep-dive` generates per-project `.codebeacon/` + `CLAUDE.md` for every sub-project; running `codebeacon scan . --update` from any sub-project folder automatically syncs all projects in the workspace
 
 ---
 
@@ -176,6 +177,47 @@ project-root/
     obsidian/            ← Obsidian vault (one note per graph node)
 ```
 
+### Deep Dive Mode
+
+With `--deep-dive`, each sub-project also gets its own `.codebeacon/` directory and `CLAUDE.md`, so AI sessions opened inside a sub-project have full project-specific context:
+
+```
+workspace/
+  CLAUDE.md                   ← combined (all projects)
+  .cursorrules
+  AGENTS.md
+  codebeacon.yaml             ← deep_dive: true
+  .codebeacon/                ← combined knowledge graph
+    beacon.json
+    wiki/
+    obsidian/
+  api-server/
+    CLAUDE.md                 ← api-server only
+    .codebeacon/              ← api-server graph
+      beacon.json
+      wiki/
+      obsidian/
+  frontend/
+    CLAUDE.md                 ← frontend only
+    .codebeacon/              ← frontend graph
+      beacon.json
+      wiki/
+      obsidian/
+```
+
+Claude Code loads `CLAUDE.md` hierarchically, so opening a session in `api-server/` loads both the parent workspace overview **and** the project-specific details.
+
+To update from any sub-project directory after the initial scan:
+
+```bash
+# Initial deep-dive scan
+codebeacon scan /workspace --deep-dive
+
+# Later, from any sub-project — finds the parent config and updates ALL projects
+cd /workspace/api-server
+codebeacon scan . --update
+```
+
 ---
 
 ## AI Integration
@@ -270,6 +312,7 @@ codebeacon scan . --wiki-only             # skip re-extraction, regenerate wiki/
 codebeacon scan . --obsidian-dir <path>   # write Obsidian vault to custom location
 codebeacon scan . --semantic              # enable LLM semantic extraction
 codebeacon scan . --list-only             # detect frameworks only, don't extract
+codebeacon scan /workspace --deep-dive    # per-project + combined workspace outputs
 
 # Config-driven mode
 codebeacon init [path]                    # auto-generate codebeacon.yaml
@@ -317,6 +360,8 @@ wave:
 
 semantic:
   enabled: false               # override with --semantic flag
+
+deep_dive: false               # set to true to generate per-project outputs
 ```
 
 ### .codebeaconignore

{codebeacon-0.1.3 → codebeacon-0.1.4}/README.de.md

@@ -48,6 +48,7 @@ Bestehende Tools lösen dieses Problem nur teilweise. Route-Analyzer erfassen Ih
 - **Community-Erkennung** — Leiden/Louvain-Clustering deckt tatsächliche Architekturgrenzen auf
 - **Inkrementeller Cache** — SHA-256-basiert; extrahiert nur seit dem letzten Scan geänderte Dateien neu
 - **Keine Konfiguration notwendig** — erkennt Frameworks und Sprachen automatisch; generiert `codebeacon.yaml` für Folgeläufe
+- **Deep-Dive-Modus** — `--deep-dive` erzeugt für jedes Sub-Projekt eigene `.codebeacon/` + `CLAUDE.md`; ein Update-Aufruf aus **beliebigem** Sub-Projekt-Ordner synchronisiert automatisch alle Projekte im Workspace
 
 ---
 
@@ -129,6 +130,69 @@ project-root/
     obsidian/            ← Obsidian Vault (eine Notiz pro Graph-Knoten)
 ```
 
+### Deep-Dive-Modus
+
+Mit `--deep-dive` erhält jedes Sub-Projekt sein eigenes `.codebeacon/` + `CLAUDE.md`. Claude Code lädt `CLAUDE.md`-Dateien hierarchisch — eine Sitzung in `api-server/` lädt also sowohl den Workspace-Überblick als auch die projektspezifischen Details.
+
+Das entscheidende Merkmal: ein Update-Aufruf aus **jedem beliebigen Sub-Projekt** synchronisiert automatisch den gesamten Workspace:
+
+```bash
+# Erster Deep-Dive-Scan
+codebeacon scan /workspace --deep-dive
+
+# Später aus einem beliebigen Sub-Projekt — findet die übergeordnete Konfig und aktualisiert ALLE Projekte
+cd /workspace/api-server
+codebeacon scan . --update
+```
+
+Ausgabestruktur:
+```
+workspace/
+  CLAUDE.md                   ← kombiniert (alle Projekte)
+  codebeacon.yaml             ← deep_dive: true
+  .codebeacon/                ← kombinierter Knowledge Graph
+  api-server/
+    CLAUDE.md                 ← nur api-server
+    .codebeacon/              ← api-server-Graph
+  frontend/
+    CLAUDE.md                 ← nur frontend
+    .codebeacon/              ← frontend-Graph
+```
+
+## Konfiguration
+
+Führe `codebeacon init` aus, um `codebeacon.yaml` zu generieren, oder erstelle die Datei manuell:
+
+```yaml
+version: 1
+
+projects:
+  - name: api-server
+    path: ./api-server
+    type: spring-boot          # optional: wird automatisch erkannt
+
+  - name: frontend
+    path: ./frontend
+    type: react
+
+output:
+  dir: .codebeacon
+  wiki: true
+  obsidian: true
+  context_map:
+    targets: [CLAUDE.md, .cursorrules, AGENTS.md]
+
+wave:
+  auto: true
+  chunk_size: 300              # Dateien pro Chunk
+  max_parallel: 5              # parallele Threads
+
+semantic:
+  enabled: false               # mit --semantic überschreiben
+
+deep_dive: false               # auf true setzen für Pro-Projekt-Ausgabe
+```
+
 ### .codebeaconignore
 
 Platziere eine `.codebeaconignore`-Datei im Projektstammverzeichnis, um Verzeichnisse oder Dateien vom Scan auszuschließen. Gleiche Syntax wie `.gitignore` — ein Muster pro Zeile, `#` für Kommentare.
@@ -231,6 +295,7 @@ codebeacon scan . --update                # inkrementell: nur geänderte Dateien
 codebeacon scan . --wiki-only             # Extraktion überspringen, Wiki/Obsidian/Kontext aus vorhandenem beacon.json regenerieren
 codebeacon scan . --semantic              # LLM-semantische Extraktion
 codebeacon scan . --list-only             # nur Frameworks erkennen
+codebeacon scan /workspace --deep-dive    # Pro-Projekt- + kombinierte Workspace-Ausgabe
 
 codebeacon init [pfad]                    # codebeacon.yaml generieren
 codebeacon sync                           # von codebeacon.yaml ausführen

{codebeacon-0.1.3 → codebeacon-0.1.4}/README.es.md

@@ -48,6 +48,7 @@ Las herramientas existentes resuelven esto de forma parcial. Los analizadores de
 - **Detección de comunidades** — clustering Leiden/Louvain revela los límites arquitectónicos reales
 - **Caché incremental** — basado en SHA-256; solo re-extrae archivos modificados desde el último escaneo
 - **Cero configuración** — detecta frameworks y lenguajes automáticamente; genera `codebeacon.yaml` para ejecuciones posteriores
+- **Modo Deep Dive** — `--deep-dive` genera `.codebeacon/` + `CLAUDE.md` propios para cada sub-proyecto; ejecutar el comando de actualización desde **cualquier** sub-proyecto sincroniza automáticamente todos los proyectos del workspace
 
 ---
 
@@ -128,6 +129,69 @@ project-root/
     obsidian/            ← Obsidian Vault (una nota por nodo del grafo)
 ```
 
+### Modo Deep Dive
+
+Con `--deep-dive`, cada sub-proyecto recibe su propio `.codebeacon/` + `CLAUDE.md`. Claude Code carga los archivos `CLAUDE.md` de forma jerárquica, por lo que una sesión en `api-server/` carga tanto la visión general del workspace como los detalles específicos del proyecto.
+
+La clave: un comando de actualización desde **cualquier sub-proyecto** sincroniza todo el workspace automáticamente:
+
+```bash
+# Primer escaneo deep dive
+codebeacon scan /workspace --deep-dive
+
+# Más tarde, desde cualquier sub-proyecto — encuentra la config padre y actualiza TODOS los proyectos
+cd /workspace/api-server
+codebeacon scan . --update
+```
+
+Estructura de salida:
+```
+workspace/
+  CLAUDE.md                   ← combinado (todos los proyectos)
+  codebeacon.yaml             ← deep_dive: true
+  .codebeacon/                ← grafo combinado
+  api-server/
+    CLAUDE.md                 ← solo api-server
+    .codebeacon/
+  frontend/
+    CLAUDE.md                 ← solo frontend
+    .codebeacon/
+```
+
+## Configuración
+
+Ejecuta `codebeacon init` para generar `codebeacon.yaml`, o escríbelo manualmente:
+
+```yaml
+version: 1
+
+projects:
+  - name: api-server
+    path: ./api-server
+    type: spring-boot          # opcional: se detecta automáticamente
+
+  - name: frontend
+    path: ./frontend
+    type: react
+
+output:
+  dir: .codebeacon
+  wiki: true
+  obsidian: true
+  context_map:
+    targets: [CLAUDE.md, .cursorrules, AGENTS.md]
+
+wave:
+  auto: true
+  chunk_size: 300              # archivos por chunk
+  max_parallel: 5              # hilos paralelos
+
+semantic:
+  enabled: false               # sobrescribir con --semantic
+
+deep_dive: false               # establecer true para salida por proyecto
+```
+
 ### .codebeaconignore
 
 Coloca un archivo `.codebeaconignore` en la raíz del proyecto para excluir directorios o archivos del escaneo. Misma sintaxis que `.gitignore` — un patrón por línea, `#` para comentarios.
@@ -230,6 +294,7 @@ codebeacon scan . --update                # incremental: solo archivos modificad
 codebeacon scan . --wiki-only             # saltar extracción, regenerar wiki/obsidian/contexto desde beacon.json existente
 codebeacon scan . --semantic              # extracción semántica con LLM
 codebeacon scan . --list-only             # solo detectar frameworks
+codebeacon scan /workspace --deep-dive    # salida por proyecto + workspace combinado
 
 codebeacon init [ruta]                    # generar codebeacon.yaml
 codebeacon sync                           # ejecutar desde codebeacon.yaml

{codebeacon-0.1.3 → codebeacon-0.1.4}/README.fr.md

@@ -48,6 +48,7 @@ Les outils existants ne résolvent ce problème qu'en partie. Les analyseurs de
 - **Détection de communautés** — clustering Leiden/Louvain révèle les vraies frontières architecturales
 - **Cache incrémental** — basé sur SHA-256 ; ré-extrait uniquement les fichiers modifiés depuis le dernier scan
 - **Zéro configuration** — détecte automatiquement les frameworks et langages ; génère `codebeacon.yaml` pour les exécutions suivantes
+- **Mode Deep Dive** — `--deep-dive` génère un `.codebeacon/` + `CLAUDE.md` propre à chaque sous-projet ; une commande de mise à jour depuis **n'importe quel** sous-projet synchronise automatiquement tous les projets du workspace
 
 ---
 
@@ -128,6 +129,69 @@ project-root/
     obsidian/            ← Obsidian Vault (une note par nœud du graphe)
 ```
 
+### Mode Deep Dive
+
+Avec `--deep-dive`, chaque sous-projet reçoit son propre `.codebeacon/` + `CLAUDE.md`. Claude Code charge les fichiers `CLAUDE.md` de manière hiérarchique — une session dans `api-server/` charge à la fois la vue d'ensemble du workspace et les détails spécifiques au projet.
+
+Le point clé : une commande de mise à jour depuis **n'importe quel sous-projet** synchronise automatiquement tout le workspace :
+
+```bash
+# Premier scan deep dive
+codebeacon scan /workspace --deep-dive
+
+# Plus tard, depuis n'importe quel sous-projet — trouve la config parente et met à jour TOUS les projets
+cd /workspace/api-server
+codebeacon scan . --update
+```
+
+Structure de sortie :
+```
+workspace/
+  CLAUDE.md                   ← combiné (tous les projets)
+  codebeacon.yaml             ← deep_dive: true
+  .codebeacon/                ← graphe combiné
+  api-server/
+    CLAUDE.md                 ← api-server uniquement
+    .codebeacon/
+  frontend/
+    CLAUDE.md                 ← frontend uniquement
+    .codebeacon/
+```
+
+## Configuration
+
+Exécutez `codebeacon init` pour générer `codebeacon.yaml`, ou créez-le manuellement :
+
+```yaml
+version: 1
+
+projects:
+  - name: api-server
+    path: ./api-server
+    type: spring-boot          # optionnel : détecté automatiquement
+
+  - name: frontend
+    path: ./frontend
+    type: react
+
+output:
+  dir: .codebeacon
+  wiki: true
+  obsidian: true
+  context_map:
+    targets: [CLAUDE.md, .cursorrules, AGENTS.md]
+
+wave:
+  auto: true
+  chunk_size: 300              # fichiers par chunk
+  max_parallel: 5              # threads parallèles
+
+semantic:
+  enabled: false               # écraser avec --semantic
+
+deep_dive: false               # mettre à true pour une sortie par projet
+```
+
 ### .codebeaconignore
 
 Placez un fichier `.codebeaconignore` à la racine du projet pour exclure des répertoires ou fichiers du scan. Même syntaxe que `.gitignore` — un motif par ligne, `#` pour les commentaires.
@@ -230,6 +294,7 @@ codebeacon scan . --update                # incrémental : fichiers modifiés se
 codebeacon scan . --wiki-only             # ignorer la ré-extraction, régénérer wiki/obsidian/contexte depuis beacon.json existant
 codebeacon scan . --semantic              # extraction sémantique LLM
 codebeacon scan . --list-only             # détecter les frameworks uniquement
+codebeacon scan /workspace --deep-dive    # sortie par projet + workspace combiné
 
 codebeacon init [chemin]                  # générer codebeacon.yaml
 codebeacon sync                           # exécuter depuis codebeacon.yaml

{codebeacon-0.1.3 → codebeacon-0.1.4}/README.ja.md

@@ -48,6 +48,7 @@ AI コーディングセッションを新しく開くたびに、アシスタ
 - **コミュニティ検出** — Leiden/Louvain クラスタリングで実際のアーキテクチャ境界を発見
 - **インクリメンタルキャッシュ** — SHA-256 ベース；前回スキャン以降に変更されたファイルのみ再抽出
 - **ゼロ設定** — フレームワークと言語を自動検出；繰り返し実行のために `codebeacon.yaml` を自動生成
+- **ディープダイブモード** — `--deep-dive` で各サブプロジェクトに専用の `.codebeacon/` + `CLAUDE.md` を生成；**どのサブプロジェクトからでも**更新コマンドを実行するだけでワークスペース全体が自動同期
 
 ---
 
@@ -135,6 +136,35 @@ project-root/
     obsidian/            ← Obsidian Vault (グラフノードごとに 1 ノート)
 ```
 
+### ディープダイブモード
+
+`--deep-dive` を使うと、各サブプロジェクトが独自の `.codebeacon/` + `CLAUDE.md` を持ちます。Claude Code は `CLAUDE.md` を階層的にロードするため、`api-server/` でセッションを開くとワークスペース全体の概要とプロジェクト固有の詳細が両方ロードされます。
+
+最大のポイント：**どのサブプロジェクトから実行しても**、親の設定ファイルを自動検出してワークスペース全体を更新します：
+
+```bash
+# 初回ディープダイブスキャン
+codebeacon scan /workspace --deep-dive
+
+# 以降、どのサブプロジェクトからでも — 親の設定を見つけ、全プロジェクトを更新
+cd /workspace/api-server
+codebeacon scan . --update
+```
+
+出力構造：
+```
+workspace/
+  CLAUDE.md                   ← 統合 (全プロジェクト)
+  codebeacon.yaml             ← deep_dive: true
+  .codebeacon/                ← 統合ナレッジグラフ
+  api-server/
+    CLAUDE.md                 ← api-server のみ
+    .codebeacon/
+  frontend/
+    CLAUDE.md                 ← frontend のみ
+    .codebeacon/
+```
+
 ---
 
 ## AI 連携
@@ -229,6 +259,7 @@ codebeacon scan . --wiki-only             # 再抽出をスキップし、既存
 codebeacon scan . --obsidian-dir <path>   # Obsidian Vault をカスタム場所に書き込み
 codebeacon scan . --semantic              # LLM セマンティック抽出を有効化
 codebeacon scan . --list-only             # フレームワーク検出のみ、抽出なし
+codebeacon scan /workspace --deep-dive    # プロジェクト別 + 統合ワークスペース出力
 
 # 設定ベースモード
 codebeacon init [path]                    # codebeacon.yaml を自動生成
@@ -276,6 +307,8 @@ wave:
 
 semantic:
   enabled: false               # --semantic フラグでオーバーライド
+
+deep_dive: false               # true にすると各プロジェクト別出力を生成
 ```
 
 ### .codebeaconignore

{codebeacon-0.1.3 → codebeacon-0.1.4}/README.ko.md

@@ -48,6 +48,7 @@ AI 코딩 세션을 새로 열 때마다 어시스턴트는 백지 상태에서
 - **커뮤니티 감지** — Leiden/Louvain 클러스터링으로 실제 아키텍처 경계 도출
 - **증분 캐시** — SHA-256 기반; 마지막 스캔 이후 변경된 파일만 재추출
 - **제로 설정** — 프레임워크와 언어 자동 감지; 반복 실행을 위한 `codebeacon.yaml` 자동 생성
+- **딥다이브 모드** — `--deep-dive`는 각 서브 프로젝트에 개별 `.codebeacon/` + `CLAUDE.md`를 생성; 어느 서브 프로젝트 폴더에서든 `codebeacon scan . --update`를 실행하면 워크스페이스의 모든 프로젝트가 자동으로 업데이트됨
 
 ---
 
@@ -134,6 +135,47 @@ project-root/
     obsidian/            ← Obsidian 볼트 (그래프 노드당 노트 1개)
 ```
 
+### 딥다이브 모드
+
+`--deep-dive`를 사용하면 각 서브 프로젝트에도 자체 `.codebeacon/` 디렉토리와 `CLAUDE.md`가 생성되어, 서브 프로젝트 내에서 열린 AI 세션이 프로젝트별 전체 컨텍스트를 갖게 됩니다:
+
+```
+workspace/
+  CLAUDE.md                   ← 통합 (모든 프로젝트)
+  .cursorrules
+  AGENTS.md
+  codebeacon.yaml             ← deep_dive: true
+  .codebeacon/                ← 통합 지식 그래프
+    beacon.json
+    wiki/
+    obsidian/
+  api-server/
+    CLAUDE.md                 ← api-server 전용
+    .codebeacon/              ← api-server 그래프
+      beacon.json
+      wiki/
+      obsidian/
+  frontend/
+    CLAUDE.md                 ← frontend 전용
+    .codebeacon/              ← frontend 그래프
+      beacon.json
+      wiki/
+      obsidian/
+```
+
+Claude Code는 `CLAUDE.md`를 계층적으로 로드하므로, `api-server/`에서 세션을 열면 상위 워크스페이스 개요와 프로젝트별 세부 정보가 모두 로드됩니다.
+
+초기 스캔 이후 어느 서브 프로젝트에서든 업데이트:
+
+```bash
+# 초기 딥다이브 스캔
+codebeacon scan /workspace --deep-dive
+
+# 이후 어느 서브 프로젝트에서든 — 부모 설정을 찾아 모든 프로젝트 업데이트
+cd /workspace/api-server
+codebeacon scan . --update
+```
+
 ---
 
 ## AI 통합
@@ -228,6 +270,7 @@ codebeacon scan . --wiki-only             # 재추출 건너뛰고 기존 beacon
 codebeacon scan . --obsidian-dir <path>   # Obsidian 볼트를 커스텀 위치에 저장
 codebeacon scan . --semantic              # LLM 시맨틱 추출 활성화
 codebeacon scan . --list-only             # 프레임워크 감지만, 추출 제외
+codebeacon scan /workspace --deep-dive    # 프로젝트별 + 통합 워크스페이스 출력
 
 # 설정 기반 모드
 codebeacon init [path]                    # codebeacon.yaml 자동 생성
@@ -275,6 +318,8 @@ wave:
 
 semantic:
   enabled: false               # --semantic 플래그로 오버라이드
+
+deep_dive: false               # true로 설정하면 프로젝트별 출력 생성
 ```
 
 ### .codebeaconignore

{codebeacon-0.1.3 → codebeacon-0.1.4}/README.md

@@ -46,6 +46,7 @@ Existing tools solve this partially. Route analyzers map your controllers but mi
 - **Community detection** — Leiden/Louvain clustering reveals your actual architectural boundaries
 - **Incremental cache** — SHA-256 based; only re-extracts files that changed since the last scan
 - **Zero configuration** — auto-detects frameworks and languages; generates `codebeacon.yaml` for repeat runs
+- **Deep-dive mode** — `--deep-dive` generates per-project `.codebeacon/` + `CLAUDE.md` for every sub-project; running `codebeacon scan . --update` from any sub-project folder automatically syncs all projects in the workspace
 
 ---
 
@@ -133,6 +134,47 @@ project-root/
     obsidian/            ← Obsidian vault (one note per graph node)
 ```
 
+### Deep Dive Mode
+
+With `--deep-dive`, each sub-project also gets its own `.codebeacon/` directory and `CLAUDE.md`, so AI sessions opened inside a sub-project have full project-specific context:
+
+```
+workspace/
+  CLAUDE.md                   ← combined (all projects)
+  .cursorrules
+  AGENTS.md
+  codebeacon.yaml             ← deep_dive: true
+  .codebeacon/                ← combined knowledge graph
+    beacon.json
+    wiki/
+    obsidian/
+  api-server/
+    CLAUDE.md                 ← api-server only
+    .codebeacon/              ← api-server graph
+      beacon.json
+      wiki/
+      obsidian/
+  frontend/
+    CLAUDE.md                 ← frontend only
+    .codebeacon/              ← frontend graph
+      beacon.json
+      wiki/
+      obsidian/
+```
+
+Claude Code loads `CLAUDE.md` hierarchically, so opening a session in `api-server/` loads both the parent workspace overview **and** the project-specific details.
+
+To update from any sub-project directory after the initial scan:
+
+```bash
+# Initial deep-dive scan
+codebeacon scan /workspace --deep-dive
+
+# Later, from any sub-project — finds the parent config and updates ALL projects
+cd /workspace/api-server
+codebeacon scan . --update
+```
+
 ---
 
 ## AI Integration
@@ -227,6 +269,7 @@ codebeacon scan . --wiki-only             # skip re-extraction, regenerate wiki/
 codebeacon scan . --obsidian-dir <path>   # write Obsidian vault to custom location
 codebeacon scan . --semantic              # enable LLM semantic extraction
 codebeacon scan . --list-only             # detect frameworks only, don't extract
+codebeacon scan /workspace --deep-dive    # per-project + combined workspace outputs
 
 # Config-driven mode
 codebeacon init [path]                    # auto-generate codebeacon.yaml
@@ -274,6 +317,8 @@ wave:
 
 semantic:
   enabled: false               # override with --semantic flag
+
+deep_dive: false               # set to true to generate per-project outputs
 ```
 
 ### .codebeaconignore

{codebeacon-0.1.3 → codebeacon-0.1.4}/README.pt-BR.md

@@ -48,6 +48,7 @@ As ferramentas existentes resolvem isso apenas parcialmente. Analisadores de rot
 - **Detecção de comunidades** — clustering Leiden/Louvain revela as fronteiras arquiteturais reais
 - **Cache incremental** — baseado em SHA-256; extrai novamente apenas arquivos alterados desde o último scan
 - **Zero configuração** — detecta frameworks e linguagens automaticamente; gera `codebeacon.yaml` para execuções futuras
+- **Modo Deep Dive** — `--deep-dive` gera `.codebeacon/` + `CLAUDE.md` próprios para cada sub-projeto; executar o comando de atualização de **qualquer** sub-projeto sincroniza automaticamente todos os projetos do workspace
 
 ---
 
@@ -128,6 +129,69 @@ project-root/
     obsidian/            ← Obsidian Vault (uma nota por nó do grafo)
 ```
 
+### Modo Deep Dive
+
+Com `--deep-dive`, cada sub-projeto recebe seu próprio `.codebeacon/` + `CLAUDE.md`. O Claude Code carrega os arquivos `CLAUDE.md` de forma hierárquica — uma sessão em `api-server/` carrega tanto a visão geral do workspace quanto os detalhes específicos do projeto.
+
+O ponto-chave: um comando de atualização de **qualquer sub-projeto** sincroniza todo o workspace automaticamente:
+
+```bash
+# Primeiro scan deep dive
+codebeacon scan /workspace --deep-dive
+
+# Depois, de qualquer sub-projeto — encontra a config pai e atualiza TODOS os projetos
+cd /workspace/api-server
+codebeacon scan . --update
+```
+
+Estrutura de saída:
+```
+workspace/
+  CLAUDE.md                   ← combinado (todos os projetos)
+  codebeacon.yaml             ← deep_dive: true
+  .codebeacon/                ← grafo combinado
+  api-server/
+    CLAUDE.md                 ← apenas api-server
+    .codebeacon/
+  frontend/
+    CLAUDE.md                 ← apenas frontend
+    .codebeacon/
+```
+
+## Configuração
+
+Execute `codebeacon init` para gerar `codebeacon.yaml`, ou crie manualmente:
+
+```yaml
+version: 1
+
+projects:
+  - name: api-server
+    path: ./api-server
+    type: spring-boot          # opcional: detectado automaticamente
+
+  - name: frontend
+    path: ./frontend
+    type: react
+
+output:
+  dir: .codebeacon
+  wiki: true
+  obsidian: true
+  context_map:
+    targets: [CLAUDE.md, .cursorrules, AGENTS.md]
+
+wave:
+  auto: true
+  chunk_size: 300              # arquivos por chunk
+  max_parallel: 5              # threads paralelas
+
+semantic:
+  enabled: false               # sobrescrever com --semantic
+
+deep_dive: false               # definir true para saída por projeto
+```
+
 ### .codebeaconignore
 
 Coloque um arquivo `.codebeaconignore` na raiz do projeto para excluir diretórios ou arquivos do scan. Mesma sintaxe do `.gitignore` — um padrão por linha, `#` para comentários.
@@ -230,6 +294,7 @@ codebeacon scan . --update                # incremental: apenas arquivos alterad
 codebeacon scan . --wiki-only             # pular re-extração, regenerar wiki/obsidian/contexto a partir do beacon.json existente
 codebeacon scan . --semantic              # extração semântica com LLM
 codebeacon scan . --list-only             # apenas detectar frameworks
+codebeacon scan /workspace --deep-dive    # saída por projeto + workspace combinado
 
 codebeacon init [caminho]                 # gerar codebeacon.yaml
 codebeacon sync                           # executar a partir do codebeacon.yaml