codebeacon 0.6.7__tar.gz → 0.6.8__tar.gz

{codebeacon-0.6.7 → codebeacon-0.6.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codebeacon
-Version: 0.6.7
+Version: 0.6.8
 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
@@ -118,6 +118,20 @@ Description-Content-Type: text/markdown
 
 ---
 
+## What's new in 0.6.8
+
+A graphify-parity audit of upstream v0.8.41–v0.9.3 (reported issues through #1568). Every candidate was reproduced against codebeacon before fixing and re-checked by an adversarial review pass; **7 real bugs** confirmed, headlined by a data-loss trap and a privacy leak.
+
+- **`--obsidian-dir` can no longer delete your notes** — pointed at an existing Obsidian vault, the export swept *every* `.md` under it before regenerating, so it could wipe a real vault. codebeacon now refuses any directory it doesn't own (only a genuinely empty dir, or one carrying its `.codebeacon-vault.json` marker, is adopted) and skips the export with a clear message instead of deleting.
+- **`.gitignore` is no longer silently disabled by `.codebeaconignore`** — adding a `.codebeaconignore` used to *replace* the repo's `.gitignore`, so a file excluded only by `.gitignore` (a neutrally-named `prod-dump.sql`, `customer-data.*`) would get indexed into the committed `.codebeacon/` artifacts. The two are now merged (`.codebeaconignore` wins on conflict); adding it can only ever exclude *more*.
+- **No machine-absolute paths in committed artifacts** — edge/link `source_file` values (the bulk of `beacon.json`) and the `Source:` lines in wiki/obsidian notes kept absolute `/Users/you/...` paths, so the committed index wasn't portable and leaked local paths. All are now project-relative (edges included, and cross-project `shares_db_entity` files too).
+- **Same-named symbols in different directories no longer overwrite each other's notes** — wiki/obsidian filenames were derived from the label with no case-folding, so on macOS/Windows `UserService` and `userService` collided and one note was silently lost. Filenames are now collision-salted and case-folded; punctuation-only labels (`@`) fall back to `unnamed` instead of a broken `@.md`.
+- **A corrupt `beacon.json` no longer crashes** — `codebeacon affected`, the MCP server, and `--wiki-only` runs now back up a corrupt/truncated graph and report a clear "re-run scan" message instead of a raw traceback.
+- **More React components are captured** — `react.scm` missed function-expression components (`const X = function() {…}`), bare-imported HOCs (`const X = forwardRef(…)` without the `React.` prefix), and non-exported `function X()` components. All three are now extracted.
+- **Wiki links never dangle** — a link to a page that was never written is downgraded to plain text, and a link to an article in a sibling bucket (a service → its entity) is repaired to the correct relative path instead of pointing at a missing file.
+
+---
+
 ## What's new in 0.6.7
 
 Follow-ups to the 0.6.6 graphify-parity audit: grammar drift now fails loudly instead of silently, and ignore-file negations no longer slow scans down.

{codebeacon-0.6.7 → codebeacon-0.6.8}/README.de.md

@@ -27,6 +27,20 @@
 
 ---
 
+## Neu in 0.6.8
+
+Ein graphify-Parity-Audit von Upstream v0.8.41–v0.9.3 (gemeldete Issues bis #1568). Jeder Kandidat wurde vor der Behebung gegen codebeacon reproduziert und durch eine adversariale Review-Runde erneut geprüft; **7 echte Bugs** bestätigt, angeführt von einer Datenverlust-Falle und einem Privacy-Leak.
+
+- **`--obsidian-dir` kann keine Notizen mehr löschen** — bei einem bestehenden Obsidian-Vault fegte der Export vor der Neugenerierung *jede* `.md` darunter weg und konnte so ein echtes Vault leeren. codebeacon verweigert jetzt jedes Verzeichnis, das es nicht besitzt (nur ein wirklich leeres Verzeichnis oder eines mit seinem `.codebeacon-vault.json`-Marker wird übernommen) und überspringt den Export mit einer klaren Meldung statt zu löschen.
+- **`.gitignore` wird nicht mehr still durch `.codebeaconignore` deaktiviert** — das Hinzufügen einer `.codebeaconignore` *ersetzte* bisher die `.gitignore` des Repos, sodass eine nur durch `.gitignore` ausgeschlossene Datei (ein neutral benanntes `prod-dump.sql`, `customer-data.*`) in die committeten `.codebeacon/`-Artefakte indexiert werden konnte. Beide werden jetzt zusammengeführt (`.codebeaconignore` gewinnt bei Konflikten); das Hinzufügen kann nur *mehr* ausschließen.
+- **Keine maschinenabsoluten Pfade mehr in committeten Artefakten** — `source_file`-Werte an Edges/Links (der Großteil von `beacon.json`) und die `Source:`-Zeilen in Wiki-/Obsidian-Notizen behielten absolute `/Users/du/...`-Pfade, sodass der committete Index nicht portabel war und lokale Pfade preisgab. Alle sind jetzt projekt-relativ (inklusive Edges und projektübergreifender `shares_db_entity`-Dateien).
+- **Gleichnamige Symbole in unterschiedlichen Verzeichnissen überschreiben sich nicht mehr** — Wiki-/Obsidian-Dateinamen wurden ohne Groß-/Kleinschreibungs-Faltung aus dem Label abgeleitet, sodass unter macOS/Windows `UserService` und `userService` kollidierten und eine Notiz still verloren ging. Dateinamen sind jetzt kollisions-gesalzen und case-gefaltet; Labels aus reiner Interpunktion (`@`) fallen auf `unnamed` zurück statt auf ein kaputtes `@.md`.
+- **Ein beschädigtes `beacon.json` stürzt nicht mehr ab** — `codebeacon affected`, der MCP-Server und `--wiki-only`-Läufe sichern jetzt einen beschädigten/abgeschnittenen Graphen und melden eine klare „Scan erneut ausführen"-Meldung statt eines rohen Tracebacks.
+- **Mehr React-Komponenten werden erfasst** — `react.scm` übersah Function-Expression-Komponenten (`const X = function() {…}`), bare-importierte HOCs (`const X = forwardRef(…)` ohne `React.`-Präfix) und nicht exportierte `function X()`-Komponenten. Alle drei werden jetzt extrahiert.
+- **Wiki-Links laufen nie ins Leere** — ein Link auf eine nie geschriebene Seite wird zu reinem Text herabgestuft, und ein Link auf einen Artikel in einem Nachbar-Bucket (ein Service → seine Entity) wird auf den korrekten relativen Pfad repariert, statt auf eine fehlende Datei zu zeigen.
+
+---
+
 ## Neu in 0.6.7
 
 Folgearbeiten zum graphify-Parity-Audit aus 0.6.6: Grammar-Drift schlägt jetzt laut fehl statt stillschweigend, und Negationen in der Ignore-Datei verlangsamen Scans nicht mehr.

{codebeacon-0.6.7 → codebeacon-0.6.8}/README.es.md

@@ -27,6 +27,20 @@
 
 ---
 
+## Novedades en 0.6.8
+
+Una auditoría de paridad con graphify del upstream v0.8.41–v0.9.3 (issues reportados hasta el #1568). Cada candidato se reprodujo contra codebeacon antes de corregirlo y se volvió a comprobar con una ronda de revisión adversarial; se confirmaron **7 bugs reales**, encabezados por una trampa de pérdida de datos y una fuga de privacidad.
+
+- **`--obsidian-dir` ya no puede borrar tus notas** — apuntando a un vault de Obsidian existente, la exportación barría *todos* los `.md` debajo antes de regenerar, pudiendo vaciar un vault real. codebeacon ahora rechaza cualquier directorio que no posea (solo se adopta un directorio genuinamente vacío, o uno que lleve su marcador `.codebeacon-vault.json`) y omite la exportación con un mensaje claro en vez de borrar.
+- **`.gitignore` ya no queda deshabilitado en silencio por `.codebeaconignore`** — añadir un `.codebeaconignore` solía *reemplazar* el `.gitignore` del repo, así que un archivo excluido solo por `.gitignore` (un `prod-dump.sql`, `customer-data.*` de nombre neutro) podía terminar indexado en los artefactos `.codebeacon/` que se commitean. Ahora ambos se fusionan (`.codebeaconignore` gana en conflicto); añadirlo solo puede excluir *más*.
+- **Sin rutas absolutas de máquina en los artefactos commiteados** — los valores `source_file` de edges/links (el grueso de `beacon.json`) y las líneas `Source:` en las notas de wiki/obsidian conservaban rutas absolutas `/Users/tu/...`, así que el índice commiteado no era portable y filtraba rutas locales. Ahora todas son relativas al proyecto (edges incluidos, y también los archivos `shares_db_entity` entre proyectos).
+- **Símbolos con el mismo nombre en directorios distintos ya no se sobrescriben las notas** — los nombres de archivo de wiki/obsidian se derivaban de la etiqueta sin normalizar mayúsculas/minúsculas, así que en macOS/Windows `UserService` y `userService` colisionaban y una nota se perdía en silencio. Ahora los nombres de archivo llevan sal anti-colisión y normalización de mayúsculas; las etiquetas solo de puntuación (`@`) recurren a `unnamed` en vez de un `@.md` roto.
+- **Un `beacon.json` corrupto ya no provoca un cuelgue** — `codebeacon affected`, el servidor MCP y las ejecuciones `--wiki-only` ahora respaldan un grafo corrupto/truncado y muestran un mensaje claro de "vuelve a ejecutar scan" en vez de un traceback en crudo.
+- **Se capturan más componentes de React** — `react.scm` pasaba por alto los componentes de expresión de función (`const X = function() {…}`), los HOC importados sin calificar (`const X = forwardRef(…)` sin el prefijo `React.`) y los componentes `function X()` no exportados. Los tres se extraen ahora.
+- **Los enlaces del wiki nunca quedan rotos** — un enlace a una página que nunca se escribió se degrada a texto plano, y un enlace a un artículo en un bucket hermano (un servicio → su entidad) se repara a la ruta relativa correcta en vez de apuntar a un archivo inexistente.
+
+---
+
 ## Novedades en 0.6.7
 
 Seguimiento de la auditoría de paridad con graphify de 0.6.6: la deriva de gramática ahora falla de forma ruidosa en lugar de silenciosa, y las negaciones en el archivo de ignore ya no ralentizan los escaneos.

{codebeacon-0.6.7 → codebeacon-0.6.8}/README.fr.md

@@ -27,6 +27,20 @@
 
 ---
 
+## Nouveautés en 0.6.8
+
+Un audit de parité graphify de l'upstream v0.8.41–v0.9.3 (issues signalées jusqu'au #1568). Chaque candidat a été reproduit sur codebeacon avant correction, puis revérifié par une passe de revue adversariale ; **7 bugs réels** confirmés, avec en tête un piège à perte de données et une fuite de confidentialité.
+
+- **`--obsidian-dir` ne peut plus supprimer vos notes** — pointé vers un vault Obsidian existant, l'export balayait *tous* les `.md` en dessous avant de régénérer, pouvant ainsi vider un vrai vault. codebeacon refuse désormais tout répertoire qu'il ne possède pas (seul un répertoire réellement vide, ou portant son marqueur `.codebeacon-vault.json`, est adopté) et saute l'export avec un message clair au lieu de supprimer.
+- **`.gitignore` n'est plus désactivé silencieusement par `.codebeaconignore`** — ajouter un `.codebeaconignore` *remplaçait* auparavant le `.gitignore` du dépôt, si bien qu'un fichier exclu uniquement par `.gitignore` (un `prod-dump.sql`, `customer-data.*` au nom neutre) pouvait être indexé dans les artefacts `.codebeacon/` commités. Les deux sont désormais fusionnés (`.codebeaconignore` l'emporte en cas de conflit) ; l'ajouter ne peut que exclure *davantage*.
+- **Plus aucun chemin absolu machine dans les artefacts commités** — les valeurs `source_file` des edges/links (l'essentiel de `beacon.json`) et les lignes `Source:` des notes wiki/obsidian conservaient des chemins absolus `/Users/vous/...`, rendant l'index commité non portable et divulguant des chemins locaux. Tout est désormais relatif au projet (edges compris, ainsi que les fichiers `shares_db_entity` inter-projets).
+- **Des symboles homonymes dans des répertoires différents n'écrasent plus les notes l'un de l'autre** — les noms de fichiers wiki/obsidian étaient dérivés du label sans normalisation de casse, si bien que sur macOS/Windows `UserService` et `userService` entraient en collision et une note disparaissait silencieusement. Les noms de fichiers sont désormais salés anti-collision et normalisés en casse ; les labels tout en ponctuation (`@`) retombent sur `unnamed` au lieu d'un `@.md` cassé.
+- **Un `beacon.json` corrompu ne plante plus** — `codebeacon affected`, le serveur MCP et les exécutions `--wiki-only` sauvegardent désormais un graphe corrompu/tronqué et affichent un message clair « relancez scan » au lieu d'une trace brute.
+- **Davantage de composants React sont capturés** — `react.scm` manquait les composants en expression de fonction (`const X = function() {…}`), les HOC importés nus (`const X = forwardRef(…)` sans préfixe `React.`) et les composants `function X()` non exportés. Les trois sont désormais extraits.
+- **Les liens du wiki ne pointent plus jamais dans le vide** — un lien vers une page jamais écrite est rétrogradé en texte brut, et un lien vers un article dans un bucket voisin (un service → son entité) est réparé vers le bon chemin relatif au lieu de pointer vers un fichier manquant.
+
+---
+
 ## Nouveautés en 0.6.7
 
 Suite de l'audit de parité graphify de 0.6.6 : la dérive de grammaire échoue désormais bruyamment au lieu de silencieusement, et les négations du fichier d'ignore ne ralentissent plus les scans.

{codebeacon-0.6.7 → codebeacon-0.6.8}/README.ja.md

@@ -27,6 +27,20 @@
 
 ---
 
+## 0.6.8 の新機能
+
+アップストリーム v0.8.41–v0.9.3(報告された issue は #1568 まで)の graphify パリティ監査です。各候補は修正前に codebeacon 上で実際に再現し、敵対的レビューパスで再確認しました。**実バグ7件**を確認、データ損失トラップとプライバシー漏洩が目玉です。
+
+- **`--obsidian-dir` がノートを削除しなくなりました** — 既存の Obsidian vault を指定すると、再生成前にその配下の*すべて*の `.md` を一掃していたため、実際の vault を空にしてしまう可能性がありました。codebeacon は所有していないディレクトリを拒否するようになり(完全に空のディレクトリ、または `.codebeacon-vault.json` マーカーを持つディレクトリのみ採用)、削除する代わりに明確なメッセージとともにエクスポートをスキップします。
+- **`.codebeaconignore` によって `.gitignore` が静かに無効化されなくなりました** — `.codebeaconignore` を追加すると以前はリポジトリの `.gitignore` を*置き換えて*いたため、`.gitignore` だけで除外されているファイル(中立的な名前の `prod-dump.sql`、`customer-data.*`)がコミットされる `.codebeacon/` 成果物にインデックスされる可能性がありました。両者は今やマージされます(競合時は `.codebeaconignore` が優先);追加しても除外が*増える*だけになりました。
+- **コミットされる成果物にマシン絶対パスが含まれなくなりました** — エッジ/リンクの `source_file` 値(`beacon.json` の大半)と wiki/obsidian ノートの `Source:` 行が絶対パス `/Users/you/...` を保持していたため、コミットされたインデックスに可搬性がなく、ローカルパスが漏洩していました。すべてプロジェクト相対になりました(エッジ、およびプロジェクト横断の `shares_db_entity` ファイルも含む)。
+- **異なるディレクトリの同名シンボルがノートを上書きしなくなりました** — wiki/obsidian のファイル名は大文字小文字を畳み込まずにラベルから生成されていたため、macOS/Windows で `UserService` と `userService` が衝突し、片方のノートが静かに失われていました。ファイル名は衝突耐性のソルトと大文字小文字の畳み込みを行うようになり、記号のみのラベル(`@`)は壊れた `@.md` の代わりに `unnamed` にフォールバックします。
+- **破損した `beacon.json` でクラッシュしなくなりました** — `codebeacon affected`、MCP サーバー、`--wiki-only` 実行は、破損/切り詰められたグラフをバックアップし、生のトレースバックの代わりに明確な「scan を再実行してください」メッセージを報告するようになりました。
+- **より多くの React コンポーネントを捕捉するようになりました** — `react.scm` は関数式コンポーネント(`const X = function() {…}`)、`React.` プレフィックスなしの bare import HOC(`const X = forwardRef(…)`)、および非エクスポートの `function X()` コンポーネントを見落としていました。この3つすべてが抽出されるようになりました。
+- **wiki のリンクがリンク切れにならなくなりました** — 一度も書き込まれなかったページへのリンクはプレーンテキストに格下げされ、隣接バケット内の記事(サービス→そのエンティティ)へのリンクは、存在しないファイルを指す代わりに正しい相対パスに修復されます。
+
+---
+
 ## 0.6.7 の新機能
 
 0.6.6 の graphify パリティ監査のフォローアップ: grammar ドリフトが静かに埋もれず明示的に失敗するようになり、ignore ファイルの否定ルールがスキャンを遅くしなくなりました。

{codebeacon-0.6.7 → codebeacon-0.6.8}/README.ko.md

@@ -27,6 +27,20 @@
 
 ---
 
+## 0.6.8 새 소식
+
+업스트림 v0.8.41–v0.9.3(보고된 이슈 #1568까지)에 대한 graphify-패리티 감사입니다. 모든 후보를 수정 전에 codebeacon에서 실제로 재현하고 적대적 리뷰 패스로 재검증했으며, **7개의 실제 버그**를 확인했습니다 — 데이터 손실 함정과 프라이버시 유출이 핵심입니다.
+
+- **`--obsidian-dir`가 더 이상 사용자 노트를 삭제하지 않음** — 기존 Obsidian 볼트를 가리키면 재생성 전에 그 아래 *모든* `.md`를 지워서 실제 볼트를 통째로 날릴 수 있었습니다. 이제 codebeacon이 소유하지 않은 디렉터리는 거부하고(완전히 비어 있거나 `.codebeacon-vault.json` 마커를 가진 디렉터리만 채택), 삭제 대신 명확한 메시지와 함께 내보내기를 건너뜁니다.
+- **`.codebeaconignore`가 `.gitignore`를 조용히 무력화하지 않음** — `.codebeaconignore`를 추가하면 저장소의 `.gitignore`를 *대체*해서, `.gitignore`로만 제외된 파일(중립적 이름의 `prod-dump.sql`, `customer-data.*`)이 커밋되는 `.codebeacon/` 산출물에 인덱싱될 수 있었습니다. 이제 둘을 병합하며(충돌 시 `.codebeaconignore` 우선), 추가해도 *더 많이* 제외할 수만 있습니다.
+- **커밋되는 산출물에 머신 절대 경로 없음** — 엣지/링크의 `source_file`(`beacon.json`의 대부분)과 wiki/obsidian 노트의 `Source:` 줄이 절대 경로 `/Users/you/...`를 유지해서 인덱스가 이식성이 없고 로컬 경로가 유출됐습니다. 이제 모두 프로젝트 상대 경로입니다(엣지 포함, 교차 프로젝트 `shares_db_entity` 파일도).
+- **다른 디렉터리의 동일 이름 심볼이 서로의 노트를 덮어쓰지 않음** — wiki/obsidian 파일명이 대소문자 구분 없이 라벨에서 생성돼, macOS/Windows에서 `UserService`와 `userService`가 충돌해 한쪽 노트가 조용히 사라졌습니다. 이제 파일명이 충돌-솔팅 + 대소문자 폴딩되며, 구두점만 있는 라벨(`@`)은 깨진 `@.md` 대신 `unnamed`로 대체됩니다.
+- **손상된 `beacon.json`이 더 이상 크래시를 내지 않음** — `codebeacon affected`, MCP 서버, `--wiki-only` 실행이 이제 손상/절단된 그래프를 백업하고 원시 트레이스백 대신 명확한 "scan 재실행" 메시지를 보여줍니다.
+- **더 많은 React 컴포넌트 캡처** — `react.scm`이 함수식 컴포넌트(`const X = function() {…}`), bare-import HOC(`React.` 접두 없는 `const X = forwardRef(…)`), 비-export `function X()` 컴포넌트를 놓쳤습니다. 이제 셋 다 추출됩니다.
+- **wiki 링크가 깨지지 않음** — 작성되지 않은 페이지로의 링크는 일반 텍스트로 강등되고, 형제 버킷의 문서로 가는 링크(서비스 → 엔티티)는 없는 파일을 가리키는 대신 올바른 상대 경로로 복구됩니다.
+
+---
+
 ## 0.6.7 새 소식
 
 0.6.6 graphify-패리티 감사의 후속 작업: grammar 드리프트가 이제 조용히 묻히지 않고 명시적으로 실패하며, ignore 파일의 부정 규칙이 더 이상 스캔을 느리게 하지 않습니다.

{codebeacon-0.6.7 → codebeacon-0.6.8}/README.md

@@ -25,6 +25,20 @@
 
 ---
 
+## What's new in 0.6.8
+
+A graphify-parity audit of upstream v0.8.41–v0.9.3 (reported issues through #1568). Every candidate was reproduced against codebeacon before fixing and re-checked by an adversarial review pass; **7 real bugs** confirmed, headlined by a data-loss trap and a privacy leak.
+
+- **`--obsidian-dir` can no longer delete your notes** — pointed at an existing Obsidian vault, the export swept *every* `.md` under it before regenerating, so it could wipe a real vault. codebeacon now refuses any directory it doesn't own (only a genuinely empty dir, or one carrying its `.codebeacon-vault.json` marker, is adopted) and skips the export with a clear message instead of deleting.
+- **`.gitignore` is no longer silently disabled by `.codebeaconignore`** — adding a `.codebeaconignore` used to *replace* the repo's `.gitignore`, so a file excluded only by `.gitignore` (a neutrally-named `prod-dump.sql`, `customer-data.*`) would get indexed into the committed `.codebeacon/` artifacts. The two are now merged (`.codebeaconignore` wins on conflict); adding it can only ever exclude *more*.
+- **No machine-absolute paths in committed artifacts** — edge/link `source_file` values (the bulk of `beacon.json`) and the `Source:` lines in wiki/obsidian notes kept absolute `/Users/you/...` paths, so the committed index wasn't portable and leaked local paths. All are now project-relative (edges included, and cross-project `shares_db_entity` files too).
+- **Same-named symbols in different directories no longer overwrite each other's notes** — wiki/obsidian filenames were derived from the label with no case-folding, so on macOS/Windows `UserService` and `userService` collided and one note was silently lost. Filenames are now collision-salted and case-folded; punctuation-only labels (`@`) fall back to `unnamed` instead of a broken `@.md`.
+- **A corrupt `beacon.json` no longer crashes** — `codebeacon affected`, the MCP server, and `--wiki-only` runs now back up a corrupt/truncated graph and report a clear "re-run scan" message instead of a raw traceback.
+- **More React components are captured** — `react.scm` missed function-expression components (`const X = function() {…}`), bare-imported HOCs (`const X = forwardRef(…)` without the `React.` prefix), and non-exported `function X()` components. All three are now extracted.
+- **Wiki links never dangle** — a link to a page that was never written is downgraded to plain text, and a link to an article in a sibling bucket (a service → its entity) is repaired to the correct relative path instead of pointing at a missing file.
+
+---
+
 ## What's new in 0.6.7
 
 Follow-ups to the 0.6.6 graphify-parity audit: grammar drift now fails loudly instead of silently, and ignore-file negations no longer slow scans down.

{codebeacon-0.6.7 → codebeacon-0.6.8}/README.pt-BR.md

@@ -27,6 +27,20 @@
 
 ---
 
+## Novidades na 0.6.8
+
+Uma auditoria de paridade com graphify do upstream v0.8.41–v0.9.3 (issues reportadas até a #1568). Cada candidato foi reproduzido contra o codebeacon antes de ser corrigido e reverificado por uma rodada de revisão adversarial; **7 bugs reais** confirmados, com destaque para uma armadilha de perda de dados e um vazamento de privacidade.
+
+- **`--obsidian-dir` não consegue mais apagar suas notas** — apontado para um vault do Obsidian existente, a exportação varria *todo* `.md` abaixo dele antes de regenerar, podendo esvaziar um vault real. O codebeacon agora recusa qualquer diretório que não possua (só um diretório genuinamente vazio, ou um com o marcador `.codebeacon-vault.json`, é adotado) e pula a exportação com uma mensagem clara em vez de apagar.
+- **`.gitignore` não é mais desativado silenciosamente pelo `.codebeaconignore`** — adicionar um `.codebeaconignore` costumava *substituir* o `.gitignore` do repositório, então um arquivo excluído só pelo `.gitignore` (um `prod-dump.sql`, `customer-data.*` de nome neutro) podia acabar indexado nos artefatos `.codebeacon/` commitados. Agora os dois são mesclados (`.codebeaconignore` vence em conflito); adicioná-lo só pode excluir *mais*.
+- **Nenhum caminho absoluto de máquina nos artefatos commitados** — os valores `source_file` de edges/links (a maior parte do `beacon.json`) e as linhas `Source:` nas notas de wiki/obsidian mantinham caminhos absolutos `/Users/voce/...`, então o índice commitado não era portátil e vazava caminhos locais. Agora todos são relativos ao projeto (edges incluídos, e também os arquivos `shares_db_entity` entre projetos).
+- **Símbolos com o mesmo nome em diretórios diferentes não sobrescrevem mais as notas um do outro** — os nomes de arquivo de wiki/obsidian eram derivados do label sem normalização de maiúsculas/minúsculas, então no macOS/Windows `UserService` e `userService` colidiam e uma nota era silenciosamente perdida. Os nomes de arquivo agora recebem sal anticolisão e normalização de caixa; labels só com pontuação (`@`) caem para `unnamed` em vez de um `@.md` quebrado.
+- **Um `beacon.json` corrompido não trava mais** — `codebeacon affected`, o servidor MCP e execuções `--wiki-only` agora fazem backup de um grafo corrompido/truncado e mostram uma mensagem clara de "execute o scan novamente" em vez de um traceback bruto.
+- **Mais componentes React são capturados** — `react.scm` deixava passar componentes de expressão de função (`const X = function() {…}`), HOCs importados sem qualificação (`const X = forwardRef(…)` sem o prefixo `React.`) e componentes `function X()` não exportados. Os três agora são extraídos.
+- **Links do wiki nunca ficam quebrados** — um link para uma página que nunca foi escrita é rebaixado a texto simples, e um link para um artigo em um bucket irmão (um serviço → sua entidade) é reparado para o caminho relativo correto em vez de apontar para um arquivo inexistente.
+
+---
+
 ## Novidades na 0.6.7
 
 Acompanhamento da auditoria de paridade com graphify da 0.6.6: a deriva de gramática agora falha de forma ruidosa em vez de silenciosa, e as negações no arquivo de ignore não deixam mais os scans lentos.

{codebeacon-0.6.7 → codebeacon-0.6.8}/README.zh-CN.md

@@ -27,6 +27,20 @@
 
 ---
 
+## 0.6.8 新功能
+
+对上游 v0.8.41–v0.9.3 的 graphify 对齐审计(涵盖已报告的 issue,直到 #1568)。每个候选项在修复前都在 codebeacon 上实际复现,并通过对抗式复核再次确认;确认了 **7 个真实 bug**,以一个数据丢失陷阱和一个隐私泄露为首。
+
+- **`--obsidian-dir` 不会再删除你的笔记** — 指向一个已有的 Obsidian vault 时,导出会在重新生成前清空其下*所有* `.md` 文件,可能把一个真实的 vault 清空。codebeacon 现在会拒绝任何它不拥有的目录(只有真正为空的目录,或带有 `.codebeacon-vault.json` 标记的目录才会被采用),并以清晰的提示跳过导出,而不是删除。
+- **`.codebeaconignore` 不会再悄悄禁用 `.gitignore`** — 添加 `.codebeaconignore` 以前会*替换*仓库的 `.gitignore`,导致仅被 `.gitignore` 排除的文件(名称中立的 `prod-dump.sql`、`customer-data.*`)可能被索引进提交的 `.codebeacon/` 产物中。现在两者会合并(冲突时 `.codebeaconignore` 优先);添加它只会排除*更多*内容。
+- **提交的产物中不再有本机绝对路径** — 边/链接的 `source_file` 值(`beacon.json` 的绝大部分)以及 wiki/obsidian 笔记中的 `Source:` 行此前保留绝对路径 `/Users/you/...`,导致提交的索引不可移植且泄露本地路径。现在全部改为项目相对路径(包括边,以及跨项目的 `shares_db_entity` 文件)。
+- **不同目录下的同名符号不再互相覆盖笔记** — wiki/obsidian 的文件名此前直接由标签生成、不做大小写折叠,导致在 macOS/Windows 上 `UserService` 与 `userService` 冲突,一个笔记被静默丢失。文件名现在会做防冲突加盐和大小写折叠;仅由标点组成的标签(`@`)会回退为 `unnamed`,而不是生成损坏的 `@.md`。
+- **损坏的 `beacon.json` 不再导致崩溃** — `codebeacon affected`、MCP 服务器以及 `--wiki-only` 运行现在会备份损坏/截断的图,并给出清晰的"请重新运行 scan"提示,而不是抛出原始堆栈跟踪。
+- **捕获更多 React 组件** — `react.scm` 此前遗漏了函数表达式组件(`const X = function() {…}`)、未加 `React.` 前缀直接导入的 HOC(`const X = forwardRef(…)`),以及未导出的 `function X()` 组件。现在这三种都能被提取。
+- **wiki 链接不再指向空页面** — 指向从未写入的页面的链接会降级为纯文本,指向相邻分类目录中文章的链接(例如 service → 其 entity)会被修复为正确的相对路径,而不是指向一个不存在的文件。
+
+---
+
 ## 0.6.7 新功能
 
 对 0.6.6 graphify 对齐审计的后续:grammar 漂移现在会明确报错而非静默掩盖,ignore 文件中的否定规则也不再拖慢扫描。

codebeacon-0.6.8/codebeacon/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.6.8"

{codebeacon-0.6.7 → codebeacon-0.6.8}/codebeacon/cli.py

@@ -195,7 +195,7 @@ def _cmd_query(args: argparse.Namespace) -> int:
     idx = BeaconIndex(beacon_dir)
     try:
         idx.load()
-    except FileNotFoundError as e:
+    except (FileNotFoundError, ValueError) as e:
         print(f"Error: {e}", file=sys.stderr)
         return 1
     print(tool_beacon_query(idx, {"term": args.term, "limit": int(getattr(args, "limit", 20))}))
@@ -210,7 +210,7 @@ def _cmd_path(args: argparse.Namespace) -> int:
     idx = BeaconIndex(beacon_dir)
     try:
         idx.load()
-    except FileNotFoundError as e:
+    except (FileNotFoundError, ValueError) as e:
         print(f"Error: {e}", file=sys.stderr)
         return 1
     print(tool_beacon_path(idx, {"source": args.source, "target": args.target}))
@@ -503,7 +503,7 @@ def _cmd_semantic_prepare(args: argparse.Namespace) -> int:
             max_tasks=args.max_tasks,
             chunk_size=args.chunk_size,
         )
-    except FileNotFoundError as e:
+    except (FileNotFoundError, ValueError) as e:
         print(f"Error: {e}", file=sys.stderr)
         return 1
     print(
@@ -546,7 +546,7 @@ def _cmd_affected(args: argparse.Namespace) -> int:
             limit=int(getattr(args, "limit", 100)),
             include_wiki_paths=(output_format == "wiki"),
         )
-    except FileNotFoundError as e:
+    except (FileNotFoundError, ValueError) as e:
         print(f"Error: {e}", file=sys.stderr)
         return 1
 
@@ -574,7 +574,7 @@ def _cmd_semantic_apply(args: argparse.Namespace) -> int:
         min_conf = DEFAULT_MIN_CONFIDENCE_SCORE
     try:
         result = apply(beacon_dir, min_confidence=min_conf)
-    except FileNotFoundError as e:
+    except (FileNotFoundError, ValueError) as e:
         print(f"Error: {e}", file=sys.stderr)
         return 1
     print(

{codebeacon-0.6.7 → codebeacon-0.6.8}/codebeacon/common/safety.py

@@ -92,7 +92,13 @@ def cap_filename(name: str, limit: int = 200) -> str:
     Truncation slices the UTF-8 byte string and decodes with ``"ignore"`` so a
     multi-byte character straddling the cut is dropped rather than producing
     mojibake. Short names are returned untouched. Mirrors graphify 690b4e5.
+
+    A stem with no alphanumeric character (empty, whitespace-only, or all
+    punctuation such as ``"@"`` or ``"***"``) would produce a broken or hidden
+    filename (``@.md``, ``.md``); it falls back to ``"unnamed"`` (graphify #1409).
     """
+    if not any(c.isalnum() for c in name):
+        return "unnamed"
     encoded = name.encode("utf-8")
     if len(encoded) <= limit:
         return name
@@ -102,6 +108,32 @@ def cap_filename(name: str, limit: int = 200) -> str:
     return f"{truncated}_{digest}"
 
 
+def dedup_stem(stem: str, node_id: str, claimed: dict[str, str], scope: str = "") -> str:
+    """Return a filesystem-unique, case-folded stem for ``stem``.
+
+    ``claimed`` maps a lowercased ``"<scope>/<stem>"`` key → the node_id that owns
+    it, and is mutated in place. When a DIFFERENT node would map to an
+    already-claimed key (a collision on a case-insensitive filesystem — macOS
+    APFS, Windows NTFS — where ``UserService`` and ``userService`` are the same
+    file), the stem is salted with a short stable hash of ``node_id`` so both
+    notes survive as distinct files instead of one silently overwriting the
+    other (graphify #1453/#1504/#1522).
+
+    The salt is prefixed ``_h`` so the suffix never looks like the ``_<digits>``
+    dedup markers other export steps strip. ``scope`` namespaces the claim (e.g.
+    the wiki subdirectory) so files in different directories never false-collide.
+    """
+    key = f"{scope}/{stem.lower()}" if scope else stem.lower()
+    owner = claimed.get(key)
+    if owner is None or owner == node_id:
+        claimed[key] = node_id
+        return stem
+    salted = f"{stem}_h{hashlib.sha1(node_id.encode('utf-8')).hexdigest()[:6]}"
+    salted_key = f"{scope}/{salted.lower()}" if scope else salted.lower()
+    claimed[salted_key] = node_id
+    return salted
+
+
 def safe_wiki_filename(label: str) -> str:
     """Filename stem for a wiki article: filesystem-safe and byte-capped.
 

{codebeacon-0.6.7 → codebeacon-0.6.8}/codebeacon/discover/scanner.py

@@ -133,30 +133,42 @@ def read_ignore_file(
     *,
     gitignore_fallback: bool = True,
 ) -> list[str]:
-    """Return the raw lines of the project's ignore file (no filtering).
+    """Return the raw lines of the project's ignore rules (no filtering).
 
-    Looks for ``.codebeaconignore`` first; if absent and ``gitignore_fallback``
-    is True, falls back to the repo's ``.gitignore`` so users don't have to
-    duplicate already-curated patterns.
+    Reads ``.gitignore`` first (when ``gitignore_fallback``) and appends
+    ``.codebeaconignore`` last, so the two are **merged** rather than one
+    replacing the other. Because :class:`~codebeacon.discover.ignore.IgnoreMatcher`
+    uses gitignore last-match-wins semantics, ``.codebeaconignore`` patterns win
+    on conflict (including ``!`` negations), yet adding a ``.codebeaconignore``
+    can only ever exclude *more* — it never silently drops the repo's existing
+    ``.gitignore`` exclusions.
+
+    This matters for privacy: a file excluded only by ``.gitignore`` (e.g. a
+    neutrally-named ``prod-dump.sql`` or ``customer-data.*``) must keep being
+    skipped even after a ``.codebeaconignore`` is added, or it would get indexed
+    into the committed ``.codebeacon/`` artifacts (graphify #1363).
 
     Pattern parsing is delegated to :class:`codebeacon.discover.ignore.IgnoreMatcher`,
     which implements gitignore semantics (negation, dir-only, anchored, trailing
     whitespace handling).
     """
     root_path = Path(root)
-    primary = root_path / filename
-    try:
-        return primary.read_text(encoding="utf-8").splitlines()
-    except (FileNotFoundError, OSError):
-        pass
+    lines: list[str] = []
 
+    # .gitignore first (lower precedence).
     if gitignore_fallback:
-        gi = root_path / ".gitignore"
         try:
-            return gi.read_text(encoding="utf-8").splitlines()
+            lines.extend((root_path / ".gitignore").read_text(encoding="utf-8").splitlines())
         except (FileNotFoundError, OSError):
             pass
-    return []
+
+    # .codebeaconignore last, so its patterns win on conflict and only ever add.
+    try:
+        lines.extend((root_path / filename).read_text(encoding="utf-8").splitlines())
+    except (FileNotFoundError, OSError):
+        pass
+
+    return lines
 
 
 def _should_ignore_dir(name: str) -> bool:

{codebeacon-0.6.7 → codebeacon-0.6.8}/codebeacon/export/mcp.py

@@ -597,9 +597,12 @@ def serve(beacon_dir: str | Path) -> None:
 
     try:
         idx.load()
-    except FileNotFoundError as e:
+    except (FileNotFoundError, ValueError) as e:
+        # FileNotFoundError: no beacon.json yet. ValueError: corrupt/truncated
+        # beacon.json (load_beacon backs it up + raises). Either way, still start
+        # the server so the client can connect and tools explain the error rather
+        # than crashing at startup with a traceback (graphify #1536).
         print(f"[codebeacon-mcp] {e}", file=sys.stderr)
-        # Still start server so MCP client can connect — tools will explain the error
 
     print(f"[codebeacon-mcp] serving from {beacon_dir}", file=sys.stderr)
 

{codebeacon-0.6.7 → codebeacon-0.6.8}/codebeacon/export/obsidian.py

@@ -33,7 +33,8 @@ from typing import Any
 
 import networkx as nx
 
-from codebeacon.common.safety import cap_filename, escape_frontmatter_value, sanitize_label
+from codebeacon.common.safety import cap_filename, dedup_stem, escape_frontmatter_value, sanitize_label
+from codebeacon.graph.write import relativize_source_file
 
 
 # ── Regexes ────────────────────────────────────────────────────────────────────
@@ -53,6 +54,40 @@ _KEEP_RELS   = frozenset({"calls_api", "shares_db_entity"})  # always preserved
 _JAVA_EXTS = frozenset({".java", ".kt"})
 _TS_EXTS   = frozenset({".ts", ".tsx", ".js", ".jsx"})
 
+# Ownership marker dropped into a vault codebeacon manages, so a later run knows
+# it may safely clear/regenerate the vault (graphify #1506).
+_VAULT_MARKER = ".codebeacon-vault.json"
+
+
+class VaultNotOwnedError(ValueError):
+    """Raised when ``--obsidian-dir`` points at a directory codebeacon does not
+    own (non-empty, no marker). Subclasses ValueError so existing broad handlers
+    still catch it, while callers that want to skip *only* the ownership refusal
+    (not any other ValueError from the 12-step export) can catch this precisely.
+    """
+
+
+def _is_codebeacon_owned_vault(vault: Path, is_default: bool) -> bool:
+    """True when it is safe for codebeacon to wipe & regenerate ``vault``.
+
+    Owned when it is the default ``output_dir/obsidian`` (we created it), when a
+    prior run left the ownership marker, or when it is GENUINELY EMPTY (nothing
+    but, at most, our marker) — a brand-new directory is safe to adopt. A
+    directory that merely holds no ``.md`` yet is NOT safe: a real Obsidian vault
+    starts with a ``.obsidian/`` config folder (and possibly ``.canvas`` /
+    attachments) and zero notes, so a ``.md``-count probe would wrongly adopt it,
+    stamp the marker, and delete the notes the user later authors. Probing errors
+    fail closed (refuse) — when in doubt, do not delete (graphify #1506).
+    """
+    if is_default:
+        return True
+    if (vault / _VAULT_MARKER).exists():
+        return True
+    try:
+        return not any(p.name != _VAULT_MARKER for p in vault.iterdir())
+    except OSError:
+        return False  # cannot prove it is empty → refuse rather than wipe
+
 
 # ── Public entry point ─────────────────────────────────────────────────────────
 
@@ -61,6 +96,7 @@ def generate_obsidian_vault(
     communities: dict[str, int],
     output_dir: str | Path,
     obsidian_dir: str | Path | None = None,
+    project_roots: dict[str, str] | None = None,
 ) -> int:
     """Generate a fully post-processed Obsidian vault.
 
@@ -73,9 +109,32 @@ def generate_obsidian_vault(
     Returns:
         Total number of notes written.
     """
+    is_default = obsidian_dir is None
     vault = Path(obsidian_dir) if obsidian_dir else Path(output_dir) / "obsidian"
     vault.mkdir(parents=True, exist_ok=True)
 
+    # Guard: never wipe a directory codebeacon does not own (graphify #1506).
+    # The sweep below deletes every *.md under `vault`; if a user points
+    # `--obsidian-dir` at their real Obsidian vault, that destroys all their
+    # notes. We only sweep a vault we created: the default `output_dir/obsidian`,
+    # a directory that still carries our ownership marker from a prior run, or a
+    # directory with no notes yet (safe to adopt). Anything else is refused
+    # loudly *before* a single unlink, so the user's data is untouched.
+    if not _is_codebeacon_owned_vault(vault, is_default):
+        raise VaultNotOwnedError(
+            f"Refusing to write the Obsidian vault into {vault}: it already "
+            f"contains .md notes but no {_VAULT_MARKER} marker, so it looks like "
+            f"a user-managed vault. codebeacon would delete every .md under it. "
+            f"Point --obsidian-dir at an empty or codebeacon-managed directory, "
+            f"or drop the flag to use the default .codebeacon/obsidian."
+        )
+    # Stamp the ownership marker so subsequent runs recognise this vault as ours.
+    # It is a dot-file, so the sweep below (which skips dot-paths) preserves it.
+    (vault / _VAULT_MARKER).write_text(
+        json.dumps({"tool": "codebeacon", "owns": "obsidian-vault"}),
+        encoding="utf-8",
+    )
+
     # Clear stale notes from previous runs so step 1 regenerates cleanly. The
     # whole vault is generated from the graph, so we sweep every *.md anywhere
     # under it — not just one level inside service folders. Notes left at the
@@ -88,7 +147,7 @@ def generate_obsidian_vault(
         md.unlink()
 
     # Step 1 — basic note generation
-    _step1_generate_notes(G, communities, vault)
+    _step1_generate_notes(G, communities, vault, project_roots)
 
     # Step 2 — broken wikilink normalisation
     _step2_fix_wikilinks(vault)
@@ -133,6 +192,7 @@ def _step1_generate_notes(
     G: nx.DiGraph,
     communities: dict[str, int],
     vault: Path,
+    project_roots: dict[str, str] | None = None,
 ) -> None:
     """One Obsidian note per graph node (skipping external stubs)."""
 
@@ -145,6 +205,11 @@ def _step1_generate_notes(
         out_edges[src].append((tgt, data))
         in_edges[tgt].append((src, data))
 
+    # Lowercased-stem → node_id, so two labels that differ only by case (or two
+    # same-labelled nodes across projects in the combined vault) don't overwrite
+    # each other's note on a case-insensitive filesystem (graphify #1453/#1504).
+    claimed: dict[str, str] = {}
+
     for node_id, data in G.nodes(data=True):
         ntype = data.get("type", "unknown")
         if ntype == "external":
@@ -152,11 +217,13 @@ def _step1_generate_notes(
 
         project   = data.get("project", "_unknown")
         label     = data.get("label", node_id)
-        source_file = data.get("source_file", "")
+        source_file = relativize_source_file(
+            data.get("source_file", ""), (project_roots or {}).get(project)
+        )
         framework = data.get("framework", "")
         community_id = communities.get(node_id, -1)
 
-        note_name = _safe_note_name(label)
+        note_name = dedup_stem(_safe_note_name(label), node_id, claimed)
         content   = _build_note(
             node_id    = node_id,
             label      = label,

{codebeacon-0.6.7 → codebeacon-0.6.8}/codebeacon/extract/components.py

@@ -173,7 +173,10 @@ def _interpret_react(
                     parent_key = None
                     for k in ("component.export_func", "component.export_func_upper",
                               "component.export_default_func", "component.export_arrow",
-                              "component.local_arrow", "component.hoc"):
+                              "component.local_arrow", "component.hoc",
+                              "component.hoc_local", "component.hoc_bare_export",
+                              "component.hoc_bare_local", "component.export_fnexpr",
+                              "component.local_fnexpr", "component.local_func"):
                         if k in caps:
                             parent_key = k
                             break

{codebeacon-0.6.7 → codebeacon-0.6.8}/codebeacon/extract/queries/react.scm

@@ -96,6 +96,63 @@
   )
 ) @component.hoc_local
 
+; ── Bare-imported HOC: import { forwardRef, memo } from 'react' ───────────────
+; const Button = forwardRef((props, ref) => ...) — callee is a bare identifier,
+; not a React.* member_expression, so the patterns above miss it (graphify #1322).
+
+(export_statement
+  (lexical_declaration
+    (variable_declarator
+      name: (identifier) @component.memo_name
+      value: (call_expression
+        function: (identifier) @_hoc_bare
+        (#match? @_hoc_bare "^(memo|forwardRef|lazy)$")
+      )
+    )
+  )
+) @component.hoc_bare_export
+
+(lexical_declaration
+  (variable_declarator
+    name: (identifier) @component.memo_name
+    (#match? @component.memo_name "^[A-Z]")
+    value: (call_expression
+      function: (identifier) @_hoc_bare_l
+      (#match? @_hoc_bare_l "^(memo|forwardRef|lazy)$")
+    )
+  )
+) @component.hoc_bare_local
+
+; ── Function-expression component: const Foo = function () { return <jsx/> } ──
+; (arrow patterns above only match value: (arrow_function); graphify #1322)
+
+(export_statement
+  (lexical_declaration
+    (variable_declarator
+      name: (identifier) @component.arrow_name
+      (#match? @component.arrow_name "^[A-Z]")
+      value: (function_expression)
+    )
+  )
+) @component.export_fnexpr
+
+(lexical_declaration
+  (variable_declarator
+    name: (identifier) @component.arrow_name
+    (#match? @component.arrow_name "^[A-Z]")
+    value: (function_expression)
+  )
+) @component.local_fnexpr
+
+; ── Non-exported function-declaration component: function Foo () { ... } ──────
+; The function_declaration patterns above are all export_statement-wrapped, so a
+; local (non-exported) uppercase function component was never captured.
+
+(function_declaration
+  name: (identifier) @component.func_name
+  (#match? @component.func_name "^[A-Z]")
+) @component.local_func
+
 ; ── Hook usage ────────────────────────────────────────────────────────────────
 
 (call_expression