codebeacon 0.6.4__tar.gz → 0.6.7__tar.gz

codebeacon-0.6.4/README.md → codebeacon-0.6.7/PKG-INFO

@@ -1,3 +1,96 @@
+Metadata-Version: 2.4
+Name: codebeacon
+Version: 0.6.7
+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
+Project-URL: Issues, https://github.com/codebeacon/codebeacon/issues
+License: MIT
+License-File: LICENSE
+Keywords: ai-context,ast,claude,codebase,knowledge-graph,mcp
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Requires-Dist: networkx>=3.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: tree-sitter-javascript<0.26,>=0.23
+Requires-Dist: tree-sitter-python<0.26,>=0.23
+Requires-Dist: tree-sitter-typescript<0.24,>=0.23
+Requires-Dist: tree-sitter<0.26,>=0.23
+Provides-Extra: backend
+Requires-Dist: tree-sitter-c-sharp<0.24,>=0.23; extra == 'backend'
+Requires-Dist: tree-sitter-go<0.26,>=0.23; extra == 'backend'
+Requires-Dist: tree-sitter-java<0.24,>=0.23; extra == 'backend'
+Requires-Dist: tree-sitter-kotlin<1.2,>=0.23; extra == 'backend'
+Requires-Dist: tree-sitter-php<0.25,>=0.23; extra == 'backend'
+Requires-Dist: tree-sitter-ruby<0.24,>=0.23; extra == 'backend'
+Requires-Dist: tree-sitter-rust<0.25,>=0.23; extra == 'backend'
+Provides-Extra: cluster
+Requires-Dist: graspologic>=1.0; extra == 'cluster'
+Provides-Extra: csharp
+Requires-Dist: tree-sitter-c-sharp<0.24,>=0.23; extra == 'csharp'
+Provides-Extra: dev
+Requires-Dist: pytest-cov>=4.0; extra == 'dev'
+Requires-Dist: pytest>=7.0; extra == 'dev'
+Requires-Dist: tree-sitter-c-sharp<0.24,>=0.23; extra == 'dev'
+Requires-Dist: tree-sitter-go<0.26,>=0.23; extra == 'dev'
+Requires-Dist: tree-sitter-html<0.24,>=0.23; extra == 'dev'
+Requires-Dist: tree-sitter-java<0.24,>=0.23; extra == 'dev'
+Requires-Dist: tree-sitter-kotlin<1.2,>=0.23; extra == 'dev'
+Requires-Dist: tree-sitter-php<0.25,>=0.23; extra == 'dev'
+Requires-Dist: tree-sitter-ruby<0.24,>=0.23; extra == 'dev'
+Requires-Dist: tree-sitter-rust<0.25,>=0.23; extra == 'dev'
+Requires-Dist: tree-sitter-svelte<1.1,>=0.23; extra == 'dev'
+Requires-Dist: tree-sitter-swift<0.8,>=0.0.1; extra == 'dev'
+Provides-Extra: dotnet
+Requires-Dist: tree-sitter-c-sharp<0.24,>=0.23; extra == 'dotnet'
+Provides-Extra: full
+Requires-Dist: tree-sitter-c-sharp<0.24,>=0.23; extra == 'full'
+Requires-Dist: tree-sitter-go<0.26,>=0.23; extra == 'full'
+Requires-Dist: tree-sitter-html<0.24,>=0.23; extra == 'full'
+Requires-Dist: tree-sitter-java<0.24,>=0.23; extra == 'full'
+Requires-Dist: tree-sitter-kotlin<1.2,>=0.23; extra == 'full'
+Requires-Dist: tree-sitter-php<0.25,>=0.23; extra == 'full'
+Requires-Dist: tree-sitter-ruby<0.24,>=0.23; extra == 'full'
+Requires-Dist: tree-sitter-rust<0.25,>=0.23; extra == 'full'
+Requires-Dist: tree-sitter-svelte<1.1,>=0.23; extra == 'full'
+Requires-Dist: tree-sitter-swift<0.8,>=0.0.1; extra == 'full'
+Provides-Extra: go
+Requires-Dist: tree-sitter-go<0.26,>=0.23; extra == 'go'
+Provides-Extra: html
+Requires-Dist: tree-sitter-html<0.24,>=0.23; extra == 'html'
+Provides-Extra: java
+Requires-Dist: tree-sitter-java<0.24,>=0.23; extra == 'java'
+Provides-Extra: jvm
+Requires-Dist: tree-sitter-java<0.24,>=0.23; extra == 'jvm'
+Requires-Dist: tree-sitter-kotlin<1.2,>=0.23; extra == 'jvm'
+Provides-Extra: kotlin
+Requires-Dist: tree-sitter-kotlin<1.2,>=0.23; extra == 'kotlin'
+Provides-Extra: mobile
+Requires-Dist: tree-sitter-kotlin<1.2,>=0.23; extra == 'mobile'
+Requires-Dist: tree-sitter-swift<0.8,>=0.0.1; extra == 'mobile'
+Provides-Extra: php
+Requires-Dist: tree-sitter-php<0.25,>=0.23; extra == 'php'
+Provides-Extra: ruby
+Requires-Dist: tree-sitter-ruby<0.24,>=0.23; extra == 'ruby'
+Provides-Extra: rust
+Requires-Dist: tree-sitter-rust<0.25,>=0.23; extra == 'rust'
+Provides-Extra: svelte
+Requires-Dist: tree-sitter-svelte<1.1,>=0.23; extra == 'svelte'
+Provides-Extra: swift
+Requires-Dist: tree-sitter-swift<0.8,>=0.0.1; extra == 'swift'
+Provides-Extra: web
+Requires-Dist: tree-sitter-html<0.24,>=0.23; extra == 'web'
+Requires-Dist: tree-sitter-svelte<1.1,>=0.23; extra == 'web'
+Description-Content-Type: text/markdown
+
 <p align="center">
   <a href="https://github.com/Wandererer/codebeacon/blob/main/README.md"><img src="https://img.shields.io/badge/lang-English-blue" alt="English"></a>
   <a href="https://github.com/Wandererer/codebeacon/blob/main/README.ko.md"><img src="https://img.shields.io/badge/lang-한국어-red" alt="Korean"></a>
@@ -25,6 +118,39 @@
 
 ---
 
+## 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.
+
+- **Grammar drift is a loud failure, not a silent empty graph** — when a tree-sitter query can't compile against a grammar it's *supposed* to support (e.g. a node-type rename in a future grammar bump), `run_query` now raises and the file is recorded as an `ExtractionFailure` instead of silently extracting nothing. Together with the 0.6.6 upper-bound pins and the "every query compiles against every grammar it claims" test, drift is now caught three independent ways.
+- **A single `!` negation in `.codebeaconignore` no longer forces a full-tree walk** — one negation rule anywhere used to disable directory pruning *everywhere*, so the scanner descended into every excluded directory (`node_modules`, `build`, …) even when the negation couldn't possibly rescue anything there. Each ignored directory is now kept only if a negation could actually re-include a file beneath *it*; unrelated `!` rules cost nothing.
+- **Ignore globs compile once** — the gitignore-style matcher memoizes each pattern's compiled regex instead of rebuilding it on every path check, speeding up discovery on deep trees with large ignore files. (Semantics unchanged.)
+
+---
+
+## What's new in 0.6.6
+
+A graphify-parity audit of upstream v0.8.37–v0.8.40 (and reported issues through #1362): a verify-then-adversarially-refute sweep of 32 candidates confirmed **6 real bugs**. The headline — three framework extractors were silently producing *nothing*.
+
+- **TypeScript Express / Koa / Fastify apps now extract routes** — `express.scm` hard-coded the JavaScript class-name node type, which is an "Impossible pattern" under the TypeScript grammar, so the whole query failed to compile and the error was swallowed: **TS Express apps extracted 0 routes**. (JavaScript apps worked, and the only test fixture was `.js`, so it went unnoticed.) The identical root cause hit `vue.scm` (Vue SFCs with a plain `<script>` → 0 components). Both now use a grammar-neutral node wildcard that compiles under JS and TS.
+- **Kotlin files in Spring projects no longer error** — `spring_boot.scm` is a Java-grammar query but was allowed to run against Kotlin, emitting `Invalid node type: marker_annotation` and dropping every `.kt` file. Kotlin is now gated off cleanly (Kotlin Spring Boot would need its own query).
+- **Tree-sitter grammars are pinned with upper bounds** — `pyproject.toml` pinned grammars open-ended (`>=0.23`), so a future grammar release that renames AST node types could silently re-break the queries. Every grammar now has a compatible-range ceiling, and a new test asserts every shipped `.scm` compiles against every grammar it claims to support.
+- **The extraction cache is versioned** — after upgrading codebeacon, an incremental `--update` could reuse results extracted by the *old* version for unchanged files (a content hash can't detect that the extractor itself changed). The cache is now stamped with the codebeacon version and discarded on mismatch.
+- **Accented / non-ASCII names resolve on macOS** — `codebeacon query` / `path` / MCP and `affected` now Unicode-NFC-normalise labels and paths, so a name copied from a macOS filename (stored as NFD) matches the NFC label in the graph (e.g. `Auditoría`).
+- Plus: a corrupt extraction `cache.json` is backed up and rebuilt instead of being silently reset and then overwritten.
+
+---
+
+## What's new in 0.6.5
+
+`codebeacon upgrade` now works everywhere — it previously assumed a plain pip install and died silently on machines where that wasn't true.
+
+- **Install-manager detection** — the upgrade command detects how codebeacon was installed and runs the matching tool: `pip install --upgrade` for pip installs, `pipx upgrade codebeacon` for pipx, `uv tool upgrade codebeacon` for uv. pipx/uv tool venvs ship *without* a `pip` module, so the old unconditional `python -m pip` call failed before doing anything.
+- **Upgrade verification** — after the upgrade a fresh interpreter re-reads the installed version and reports `0.6.4 -> 0.6.5`. If the version didn't change but PyPI has a newer release, you get a warning that the `codebeacon` on your PATH may belong to a different Python environment — instead of a false "Upgrade complete".
+- **Actionable failures** — a pip-less environment prints the exact commands to run; a PEP 668 `externally-managed-environment` refusal explains the fix (pipx or a virtualenv) instead of dumping a raw pip error. The command also shows the current vs. latest-on-PyPI version up front.
+
+---
+
 ## What's new in 0.6.4
 
 Deep-dive cleanup — outputs land where you look for them, and two silent-data-loss bugs found while verifying it on a 47-project workspace.
@@ -308,7 +434,7 @@ Run **one** command from anywhere:
 codebeacon upgrade
 ```
 
-This pip-upgrades the package, then re-runs `codebeacon install` so `~/.claude/skills/codebeacon/SKILL.md` is overwritten with the new release's copy. Restart your Claude Code session for the new SKILL.md to load. If codebeacon is installed in editable mode (`pip install -e .`), the pip step is skipped — pass `--force` to upgrade anyway.
+This upgrades the package using whichever tool installed it (`pip`, `pipx upgrade`, or `uv tool upgrade` — detected automatically), verifies the installed version actually changed, then re-runs `codebeacon install` so `~/.claude/skills/codebeacon/SKILL.md` is overwritten with the new release's copy. Restart your Claude Code session for the new SKILL.md to load. If codebeacon is installed in editable mode (`pip install -e .`), the package step is skipped — pass `--force` to upgrade anyway.
 
 ### MCP Server
 

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

@@ -27,6 +27,39 @@
 
 ---
 
+## 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.
+
+- **Grammar-Drift ist ein lauter Fehler, kein stiller leerer Graph** — wenn eine tree-sitter-Query gegen eine Grammar, die sie unterstützen *soll*, nicht kompiliert (z. B. eine umbenannte Node-Art in einem künftigen Grammar-Update), wirft `run_query` jetzt eine Ausnahme und die Datei wird als `ExtractionFailure` erfasst, statt still nichts zu extrahieren. Zusammen mit den Obergrenzen-Pins aus 0.6.6 und dem Test „jede Query kompiliert gegen jede Grammar, die sie beansprucht" wird Drift nun auf drei unabhängige Weisen erkannt.
+- **Eine einzelne `!`-Negation in `.codebeaconignore` erzwingt keinen vollständigen Baum-Durchlauf mehr** — eine Negationsregel irgendwo hat das Verzeichnis-Pruning *überall* deaktiviert, sodass der Scanner in jedes ausgeschlossene Verzeichnis (`node_modules`, `build`, …) hinabstieg, selbst wenn die Negation dort nichts retten konnte. Ein ignoriertes Verzeichnis wird jetzt nur behalten, wenn eine Negation tatsächlich eine Datei *darunter* wieder einschließen könnte; nicht zugehörige `!`-Regeln kosten nichts.
+- **Ignore-Globs werden einmal kompiliert** — der gitignore-artige Matcher merkt sich die kompilierte Regex je Muster, statt sie bei jeder Pfadprüfung neu zu bauen (schnellere Erkennung bei tiefen Bäumen mit großen Ignore-Dateien). Semantik unverändert.
+
+---
+
+## Neu in 0.6.6
+
+Ein graphify-Parity-Audit von Upstream v0.8.37–v0.8.40 (und gemeldeten Issues bis #1362): ein „prüfen, dann adversarial widerlegen"-Durchlauf über 32 Kandidaten bestätigte **6 echte Bugs**. Der Hauptpunkt — drei Framework-Extraktoren produzierten still *nichts*.
+
+- **TypeScript-Express/Koa/Fastify-Apps extrahieren jetzt Routen** — `express.scm` hatte die JavaScript-Node-Art für Klassennamen fest verdrahtet, was unter der TypeScript-Grammar ein „Impossible pattern" ist; die gesamte Query kompilierte nicht und der Fehler wurde verschluckt: **TS-Express-Apps extrahierten 0 Routen**. (JavaScript-Apps funktionierten, und die einzige Test-Fixture war `.js`, daher blieb es unbemerkt.) Dieselbe Ursache traf `vue.scm` (Vue-SFCs mit reinem `<script>` → 0 Komponenten). Beide nutzen jetzt einen grammar-neutralen Node-Wildcard, der unter JS und TS kompiliert.
+- **Kotlin-Dateien in Spring-Projekten verursachen keinen Fehler mehr** — `spring_boot.scm` ist eine Java-Grammar-Query, durfte aber gegen Kotlin laufen und gab `Invalid node type: marker_annotation` aus, wobei jede `.kt`-Datei verworfen wurde. Kotlin wird jetzt sauber ausgeschlossen (Kotlin-Spring-Boot bräuchte eine eigene Query).
+- **tree-sitter-Grammars haben jetzt Versions-Obergrenzen** — `pyproject.toml` pinnte Grammars nach oben offen (`>=0.23`), sodass ein künftiges Grammar-Release, das AST-Node-Arten umbenennt, die Queries still wieder hätte brechen können. Jede Grammar hat nun eine kompatible Obergrenze, und ein neuer Test prüft, dass jede ausgelieferte `.scm` gegen jede beanspruchte Grammar kompiliert.
+- **Der Extraktions-Cache ist versioniert** — nach einem Upgrade konnte ein inkrementelles `--update` für unveränderte Dateien Ergebnisse der *alten* Version wiederverwenden (ein Content-Hash erkennt nicht, dass sich der Extraktor geändert hat). Der Cache trägt jetzt die codebeacon-Version und wird bei Abweichung verworfen.
+- **Akzentuierte / Nicht-ASCII-Namen werden unter macOS aufgelöst** — `codebeacon query` / `path` / MCP und `affected` normalisieren Labels und Pfade jetzt nach Unicode-NFC, sodass ein aus einem macOS-Dateinamen (als NFD gespeichert) kopierter Name das NFC-Label im Graphen trifft (z. B. `Auditoría`).
+- Außerdem: eine beschädigte `cache.json` wird gesichert und neu aufgebaut, statt still zurückgesetzt und überschrieben zu werden.
+
+---
+
+## Neu in 0.6.5
+
+`codebeacon upgrade` funktioniert jetzt überall — bisher ging der Befehl von einer normalen pip-Installation aus und scheiterte auf anderen Maschinen stillschweigend.
+
+- **Erkennung des Installations-Managers** — der upgrade-Befehl erkennt, wie codebeacon installiert wurde, und führt das passende Tool aus: `pip install --upgrade` bei pip, `pipx upgrade codebeacon` bei pipx, `uv tool upgrade codebeacon` bei uv. pipx/uv-tool-venvs kommen *ohne* `pip`-Modul, daher starb der alte bedingungslose `python -m pip`-Aufruf, bevor er irgendetwas tat.
+- **Upgrade-Verifikation** — nach dem Upgrade liest ein frischer Interpreter die installierte Version neu ein und meldet `0.6.4 -> 0.6.5`. Hat sich die Version nicht geändert, obwohl PyPI ein neueres Release hat, gibt es eine Warnung, dass das `codebeacon` im PATH zu einer anderen Python-Umgebung gehören könnte — statt eines falschen „Upgrade complete".
+- **Handlungsfähige Fehlermeldungen** — eine Umgebung ohne pip zeigt die exakt auszuführenden Befehle; eine PEP-668-Ablehnung (`externally-managed-environment`) erklärt die Lösung (pipx oder ein virtualenv), statt einen rohen pip-Fehler auszugeben. Der Befehl zeigt außerdem vorab die aktuelle Version neben der neuesten auf PyPI.
+
+---
+
 ## Neu in 0.6.4
 
 Deep-dive-Aufräumarbeit — Ausgaben landen dort, wo man nach ihnen sucht, plus zwei Bugs mit stillem Datenverlust, gefunden bei der Verifikation an einem Workspace mit 47 Projekten.

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

@@ -27,6 +27,39 @@
 
 ---
 
+## 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.
+
+- **La deriva de gramática es un fallo ruidoso, no un grafo vacío silencioso** — cuando una query de tree-sitter no compila contra una gramática que *debería* soportar (p. ej. un nodo renombrado en una futura actualización de gramática), `run_query` ahora lanza una excepción y el archivo se registra como `ExtractionFailure` en lugar de extraer silenciosamente nada. Junto con los topes superiores de 0.6.6 y el test «cada query compila contra cada gramática que declara soportar», la deriva se detecta ahora de tres formas independientes.
+- **Una sola negación `!` en `.codebeaconignore` ya no fuerza un recorrido completo del árbol** — una regla de negación en cualquier sitio desactivaba el pruning de directorios *en todas partes*, así que el escáner descendía a cada directorio excluido (`node_modules`, `build`, …) aunque la negación no pudiera rescatar nada allí. Ahora un directorio ignorado solo se conserva si una negación realmente podría reincluir un archivo *debajo de él*; las reglas `!` no relacionadas no cuestan nada.
+- **Los globs de ignore se compilan una sola vez** — el matcher estilo gitignore memoiza la regex compilada por patrón en lugar de reconstruirla en cada comprobación de ruta (descubrimiento más rápido en árboles profundos con archivos de ignore grandes). La semántica no cambia.
+
+---
+
+## Novedades en 0.6.6
+
+Una auditoría de paridad con graphify de upstream v0.8.37–v0.8.40 (e issues reportados hasta #1362): un barrido de «verificar y luego refutar de forma adversaria» sobre 32 candidatos confirmó **6 bugs reales**. Lo principal: tres extractores de framework producían silenciosamente *nada*.
+
+- **Las apps de Express/Koa/Fastify en TypeScript ahora extraen rutas** — `express.scm` fijaba el nodo de nombre de clase de JavaScript, que es un «Impossible pattern» bajo la gramática de TypeScript, así que toda la query no compilaba y el error se tragaba: **las apps de Express en TS extraían 0 rutas**. (Las apps de JavaScript funcionaban, y la única fixture de test era `.js`, así que pasó desapercibido.) La misma causa afectaba a `vue.scm` (SFC de Vue con `<script>` plano → 0 componentes). Ambos usan ahora un comodín de nodo neutral a la gramática que compila en JS y TS.
+- **Los archivos Kotlin en proyectos Spring ya no dan error** — `spring_boot.scm` es una query de gramática Java pero se permitía ejecutarla contra Kotlin, emitiendo `Invalid node type: marker_annotation` y descartando cada archivo `.kt`. Kotlin ahora se bloquea limpiamente (Kotlin Spring Boot necesitaría su propia query).
+- **Las gramáticas de tree-sitter están fijadas con topes superiores** — `pyproject.toml` fijaba las gramáticas sin límite superior (`>=0.23`), así que un futuro release de gramática que renombrara nodos del AST podría romper las queries de nuevo en silencio. Cada gramática tiene ahora un tope de rango compatible, y un nuevo test verifica que cada `.scm` distribuida compila contra cada gramática que declara soportar.
+- **La caché de extracción está versionada** — tras actualizar codebeacon, un `--update` incremental podía reutilizar resultados extraídos por la versión *antigua* para archivos sin cambios (un hash de contenido no detecta que el extractor cambió). La caché ahora lleva la versión de codebeacon y se descarta si no coincide.
+- **Los nombres acentuados / no ASCII se resuelven en macOS** — `codebeacon query` / `path` / MCP y `affected` ahora normalizan etiquetas y rutas a Unicode NFC, de modo que un nombre copiado de un nombre de archivo de macOS (guardado como NFD) coincide con la etiqueta NFC del grafo (p. ej. `Auditoría`).
+- Además: una `cache.json` corrupta se respalda y se reconstruye en lugar de resetearse y sobrescribirse en silencio.
+
+---
+
+## Novedades en 0.6.5
+
+`codebeacon upgrade` ahora funciona en cualquier entorno — antes asumía una instalación pip normal y fallaba silenciosamente en máquinas donde no lo era.
+
+- **Detección del gestor de instalación** — el comando upgrade detecta cómo se instaló codebeacon y ejecuta la herramienta correspondiente: `pip install --upgrade` para instalaciones pip, `pipx upgrade codebeacon` para pipx, `uv tool upgrade codebeacon` para uv. Los venvs de pipx/uv tool vienen *sin* módulo `pip`, así que la antigua llamada incondicional a `python -m pip` moría antes de hacer nada.
+- **Verificación del upgrade** — tras actualizar, un intérprete nuevo relee la versión instalada y reporta `0.6.4 -> 0.6.5`. Si la versión no cambió pero PyPI tiene una release más nueva, recibes una advertencia de que el `codebeacon` en tu PATH puede pertenecer a otro entorno de Python — en lugar de un falso "Upgrade complete".
+- **Fallos accionables** — un entorno sin pip imprime los comandos exactos a ejecutar; un rechazo PEP 668 `externally-managed-environment` explica la solución (pipx o un virtualenv) en vez de volcar un error pip crudo. El comando también muestra de entrada la versión actual frente a la última en PyPI.
+
+---
+
 ## Novedades en 0.6.4
 
 Limpieza del deep-dive — las salidas aterrizan donde las buscas, más dos bugs de pérdida silenciosa de datos encontrados al verificarlo en un workspace de 47 proyectos.

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

@@ -27,6 +27,39 @@
 
 ---
 
+## 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.
+
+- **La dérive de grammaire est un échec bruyant, pas un graphe vide silencieux** — quand une requête tree-sitter ne compile pas contre une grammaire qu'elle est *censée* prendre en charge (p. ex. un nœud renommé dans une future mise à jour de grammaire), `run_query` lève désormais une exception et le fichier est enregistré comme `ExtractionFailure` au lieu de n'extraire silencieusement rien. Avec les bornes supérieures de 0.6.6 et le test « chaque requête compile contre chaque grammaire qu'elle revendique », la dérive est désormais détectée de trois façons indépendantes.
+- **Une seule négation `!` dans `.codebeaconignore` ne force plus un parcours complet de l'arbre** — une règle de négation où que ce soit désactivait l'élagage des répertoires *partout*, de sorte que le scanner descendait dans chaque répertoire exclu (`node_modules`, `build`, …) même si la négation ne pouvait rien y récupérer. Un répertoire ignoré n'est désormais conservé que si une négation pourrait réellement réinclure un fichier *en dessous* ; les règles `!` non liées ne coûtent rien.
+- **Les globs d'ignore sont compilés une seule fois** — le matcher de style gitignore mémorise la regex compilée par motif au lieu de la reconstruire à chaque vérification de chemin (découverte plus rapide sur les arbres profonds avec de gros fichiers d'ignore). Sémantique inchangée.
+
+---
+
+## Nouveautés en 0.6.6
+
+Un audit de parité graphify de l'upstream v0.8.37–v0.8.40 (et des issues signalées jusqu'à #1362) : un balayage « vérifier puis réfuter de façon adverse » sur 32 candidats a confirmé **6 vrais bugs**. L'essentiel — trois extracteurs de framework ne produisaient silencieusement *rien*.
+
+- **Les apps Express/Koa/Fastify en TypeScript extraient désormais des routes** — `express.scm` codait en dur le nœud de nom de classe de JavaScript, qui est un « Impossible pattern » sous la grammaire TypeScript ; toute la requête ne compilait pas et l'erreur était avalée : **les apps Express en TS extrayaient 0 route**. (Les apps JavaScript fonctionnaient, et la seule fixture de test était `.js`, donc c'est passé inaperçu.) La même cause touchait `vue.scm` (SFC Vue avec `<script>` simple → 0 composant). Les deux utilisent désormais un joker de nœud neutre vis-à-vis de la grammaire qui compile en JS et TS.
+- **Les fichiers Kotlin dans les projets Spring ne provoquent plus d'erreur** — `spring_boot.scm` est une requête de grammaire Java mais était autorisée à s'exécuter contre Kotlin, émettant `Invalid node type: marker_annotation` et écartant chaque fichier `.kt`. Kotlin est désormais proprement bloqué (Kotlin Spring Boot nécessiterait sa propre requête).
+- **Les grammaires tree-sitter sont épinglées avec des bornes supérieures** — `pyproject.toml` épinglait les grammaires sans limite supérieure (`>=0.23`), de sorte qu'une future version de grammaire renommant des nœuds de l'AST pouvait à nouveau casser les requêtes en silence. Chaque grammaire a désormais un plafond de plage compatible, et un nouveau test vérifie que chaque `.scm` livrée compile contre chaque grammaire qu'elle revendique.
+- **Le cache d'extraction est versionné** — après une mise à jour de codebeacon, un `--update` incrémental pouvait réutiliser des résultats extraits par l'*ancienne* version pour des fichiers inchangés (un hash de contenu ne détecte pas que l'extracteur a changé). Le cache porte désormais la version de codebeacon et est rejeté en cas de divergence.
+- **Les noms accentués / non-ASCII se résolvent sous macOS** — `codebeacon query` / `path` / MCP et `affected` normalisent désormais les libellés et chemins en Unicode NFC, de sorte qu'un nom copié depuis un nom de fichier macOS (stocké en NFD) correspond au libellé NFC dans le graphe (p. ex. `Auditoría`).
+- De plus : un `cache.json` corrompu est sauvegardé et reconstruit au lieu d'être silencieusement réinitialisé puis écrasé.
+
+---
+
+## Nouveautés en 0.6.5
+
+`codebeacon upgrade` fonctionne désormais partout — il supposait auparavant une installation pip classique et échouait silencieusement sur les machines où ce n'était pas le cas.
+
+- **Détection du gestionnaire d'installation** — la commande upgrade détecte comment codebeacon a été installé et exécute l'outil correspondant : `pip install --upgrade` pour pip, `pipx upgrade codebeacon` pour pipx, `uv tool upgrade codebeacon` pour uv. Les venvs pipx/uv tool sont livrés *sans* module `pip`, donc l'ancien appel inconditionnel à `python -m pip` mourait avant de faire quoi que ce soit.
+- **Vérification de la mise à jour** — après la mise à jour, un interpréteur neuf relit la version installée et rapporte `0.6.4 -> 0.6.5`. Si la version n'a pas changé alors que PyPI propose une release plus récente, un avertissement indique que le `codebeacon` de votre PATH appartient peut-être à un autre environnement Python — au lieu d'un faux « Upgrade complete ».
+- **Échecs actionnables** — un environnement sans pip affiche les commandes exactes à lancer ; un refus PEP 668 `externally-managed-environment` explique la solution (pipx ou un virtualenv) au lieu de déverser une erreur pip brute. La commande affiche aussi d'emblée la version actuelle face à la dernière sur PyPI.
+
+---
+
 ## Nouveautés en 0.6.4
 
 Nettoyage du deep-dive — les sorties atterrissent là où vous les cherchez, plus deux bugs de perte silencieuse de données trouvés en le vérifiant sur un workspace de 47 projets.

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

@@ -27,6 +27,39 @@
 
 ---
 
+## 0.6.7 の新機能
+
+0.6.6 の graphify パリティ監査のフォローアップ: grammar ドリフトが静かに埋もれず明示的に失敗するようになり、ignore ファイルの否定ルールがスキャンを遅くしなくなりました。
+
+- **grammar ドリフトは「静かな空グラフ」ではなく明示的な失敗に** — tree-sitter クエリがサポートすべき grammar に対してコンパイルに失敗すると（将来の grammar 更新でのノード型改名など）、`run_query` が例外を送出し、該当ファイルは静かに 0 件抽出される代わりに `ExtractionFailure` として記録されます。0.6.6 の上限ピン + 「すべてのクエリが、サポートを宣言したすべての grammar に対してコンパイルされる」テストと合わせ、ドリフトが 3 つの独立した方法で検出されます。
+- **`.codebeaconignore` の単一の `!` 否定が、もはやツリー全体の走査を強制しない** — どこかにある否定ルール 1 つがディレクトリ枝刈りを*全体的に*無効化していたため、その否定が中で何も復活させられない場合でも、スキャナはすべての除外ディレクトリ（`node_modules`、`build` など）へ降りていました。いまや無視されたディレクトリは、否定が実際に*その下*のファイルを再包含しうる場合にのみ走査され、無関係な `!` ルールはコストになりません。
+- **ignore glob を一度だけコンパイル** — gitignore 形式のマッチャは、パス検査ごとに正規表現を再構築する代わりに、パターンごとにコンパイル済み正規表現をメモ化します（大きな ignore ファイルを持つ深いツリーでの探索が高速化）。意味は不変です。
+
+---
+
+## 0.6.6 の新機能
+
+アップストリーム v0.8.37–v0.8.40（および #1362 までの報告 issue）の graphify パリティ監査: 32 候補を「検証してから敵対的に反証する」方式で精査し、**実バグ 6 件**を確定しました。要点 — フレームワーク抽出器 3 つが静かに*何も*生成していませんでした。
+
+- **TypeScript の Express/Koa/Fastify アプリがルートを抽出するように** — `express.scm` が JavaScript のクラス名ノード型をハードコードしており、これは TypeScript grammar では「Impossible pattern」となるため、クエリ全体がコンパイルに失敗し、そのエラーが握りつぶされていました: **TS の Express アプリはルート 0 件**。（JavaScript アプリは正常で、テストフィクスチャが `.js` のみだったため見過ごされていました。）同じ原因が `vue.scm` にもありました（素の `<script>` の Vue SFC → コンポーネント 0 件）。両者とも JS・TS の双方でコンパイルされる grammar 中立なノードワイルドカードに修正しました。
+- **Spring プロジェクトの Kotlin ファイルがエラーを出さないように** — `spring_boot.scm` は Java grammar のクエリですが Kotlin に対して実行が許可されており、`Invalid node type: marker_annotation` を出してすべての `.kt` ファイルを捨てていました。いまや Kotlin はきれいに除外されます（Kotlin Spring Boot には専用クエリが必要）。
+- **tree-sitter grammar に上限ピンを追加** — `pyproject.toml` が grammar を上限なし（`>=0.23`）でピンしていたため、AST ノード型を改名する将来の grammar リリースがクエリを静かに再び壊しうる状態でした。いまやすべての grammar に互換範囲の上限があり、出荷されるすべての `.scm` が、サポートを宣言したすべての grammar に対してコンパイルされることを検証する新しいテストを追加しました。
+- **抽出キャッシュをバージョン管理** — codebeacon のアップグレード後、変更のないファイルに対して増分 `--update` が*旧*バージョンの抽出結果を再利用しうる状態でした（コンテンツハッシュは抽出器自体の変更を検出できません）。キャッシュには codebeacon バージョンが刻印され、不一致時に破棄されます。
+- **アクセント付き / 非 ASCII 名が macOS で解決される** — `codebeacon query` / `path` / MCP と `affected` がラベルとパスを Unicode NFC 正規化するようになり、macOS のファイル名からコピーした名前（NFD で保存）がグラフ内の NFC ラベルに一致します（例: `Auditoría`）。
+- さらに: 破損した `cache.json` を静かにリセットして上書きする代わりに、バックアップして再構築します。
+
+---
+
+## 0.6.5 の新機能
+
+`codebeacon upgrade` がどの環境でも動作するようになりました — 従来は通常の pip インストールを前提としており、そうでないマシンでは何もせずに静かに失敗していました。
+
+- **インストールマネージャの自動検出** — upgrade コマンドが codebeacon のインストール方法を検出し、対応するツールを実行します: pip なら `pip install --upgrade`、pipx なら `pipx upgrade codebeacon`、uv なら `uv tool upgrade codebeacon`。pipx/uv tool の venv には `pip` モジュールが*存在しない*ため、従来の無条件な `python -m pip` 呼び出しは何もできずに失敗していました。
+- **アップグレード検証** — アップグレード後、新しいインタープリタでインストール済みバージョンを再読込し `0.6.4 -> 0.6.5` のように報告します。バージョンが変わっていないのに PyPI に新しいリリースがある場合は、偽の「Upgrade complete」ではなく、PATH 上の `codebeacon` が別の Python 環境のものかもしれないと警告します。
+- **対処可能な失敗メッセージ** — pip のない環境では実行すべき正確なコマンドを表示し、PEP 668 `externally-managed-environment` の拒否には生の pip エラーの代わりに解決策（pipx または virtualenv）を説明します。実行時には現在のバージョンと PyPI の最新バージョンも併記します。
+
+---
+
 ## 0.6.4 の新機能
 
 Deep-dive のクリーンアップ — 出力が探す場所に置かれるようになり、47 プロジェクトのワークスペースで検証中に見つかったサイレントなデータ損失バグ 2 件を修正。

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

@@ -27,6 +27,39 @@
 
 ---
 
+## 0.6.7 새 소식
+
+0.6.6 graphify-패리티 감사의 후속 작업: grammar 드리프트가 이제 조용히 묻히지 않고 명시적으로 실패하며, ignore 파일의 부정 규칙이 더 이상 스캔을 느리게 하지 않습니다.
+
+- **Grammar 드리프트가 "조용한 빈 그래프"가 아니라 명시적 실패로** — tree-sitter 쿼리가 지원해야 할 grammar에 대해 컴파일에 실패하면(향후 grammar 버전업의 노드 타입 개명 등), `run_query`가 이제 예외를 던져 해당 파일이 조용히 0개 추출되는 대신 `ExtractionFailure`로 기록됩니다. 0.6.6의 상한 핀 + "모든 쿼리가 자신이 지원한다고 선언한 모든 grammar에 대해 컴파일된다" 테스트와 함께, 드리프트가 세 가지 독립적인 방법으로 잡힙니다.
+- **`.codebeaconignore`의 단일 `!` 부정 규칙이 더 이상 전체 트리 순회를 강제하지 않음** — 부정 규칙 하나가 어디에 있든 디렉터리 가지치기를 *전역적으로* 비활성화해서, 그 부정 규칙이 안에서 아무것도 되살릴 수 없는 경우에도 스캐너가 모든 제외 디렉터리(`node_modules`, `build` 등)로 내려갔습니다. 이제 각 무시된 디렉터리는 부정 규칙이 실제로 *그 아래* 파일을 되살릴 수 있을 때만 순회되며, 무관한 `!` 규칙은 비용이 들지 않습니다.
+- **Ignore 글롭을 한 번만 컴파일** — gitignore 스타일 매처가 경로를 검사할 때마다 정규식을 다시 만드는 대신 패턴별 컴파일된 정규식을 메모이즈합니다(큰 ignore 파일을 가진 깊은 트리에서 탐색 속도 향상). 동작 의미는 동일합니다.
+
+---
+
+## 0.6.6 새 소식
+
+업스트림 v0.8.37–v0.8.40(및 #1362까지 리포트된 이슈)에 대한 graphify-패리티 감사: 32개 후보를 "검증 후 적대적 반박" 방식으로 훑어 **실제 버그 6개**를 확정했습니다. 핵심 — 프레임워크 추출기 3개가 조용히 *아무것도* 만들지 못하고 있었습니다.
+
+- **TypeScript Express / Koa / Fastify 앱이 이제 라우트를 추출** — `express.scm`이 JavaScript의 클래스 이름 노드 타입을 하드코딩했는데, 이는 TypeScript grammar에서 "Impossible pattern"이라 쿼리 전체가 컴파일에 실패하고 그 에러가 묻혔습니다: **TS Express 앱은 라우트 0개**. (JavaScript 앱은 정상이었고 테스트 픽스처가 `.js`뿐이라 발각되지 않았습니다.) 동일한 근본 원인이 `vue.scm`에도 있었습니다(JS `<script>` Vue SFC → 컴포넌트 0개). 둘 다 JS·TS 모두에서 컴파일되는 grammar 중립 노드 와일드카드로 수정했습니다.
+- **Spring 프로젝트의 Kotlin 파일이 더 이상 에러를 내지 않음** — `spring_boot.scm`은 Java grammar 쿼리인데 Kotlin에 대해 실행이 허용되어 `Invalid node type: marker_annotation`를 내며 모든 `.kt` 파일을 버렸습니다. 이제 Kotlin은 깨끗하게 차단됩니다(Kotlin Spring Boot는 별도 쿼리가 필요).
+- **tree-sitter grammar에 상한 핀 추가** — `pyproject.toml`이 grammar를 상한 없이(`>=0.23`) 핀해서, AST 노드 타입을 개명하는 향후 grammar 릴리스가 쿼리를 조용히 다시 깨뜨릴 수 있었습니다. 이제 모든 grammar에 호환 범위 상한이 있고, 모든 출고 `.scm`이 자신이 지원한다고 선언한 모든 grammar에 대해 컴파일되는지 검증하는 테스트가 추가되었습니다.
+- **추출 캐시에 버전 도장** — codebeacon 업그레이드 후 증분 `--update`가 변경되지 않은 파일에 대해 *이전* 버전이 추출한 결과를 재사용할 수 있었습니다(콘텐츠 해시는 추출기 자체가 바뀐 것을 감지하지 못함). 이제 캐시에 codebeacon 버전이 찍히고 버전 불일치 시 폐기됩니다.
+- **악센트 / 비-ASCII 이름이 macOS에서 해석됨** — `codebeacon query` / `path` / MCP와 `affected`가 라벨과 경로를 Unicode NFC로 정규화하므로, macOS 파일명에서 복사한 이름(NFD로 저장)이 그래프의 NFC 라벨과 매칭됩니다(예: `Auditoría`).
+- 추가로: 손상된 추출 `cache.json`을 조용히 리셋한 뒤 덮어쓰는 대신 백업하고 재생성합니다.
+
+---
+
+## 0.6.5 새 소식
+
+`codebeacon upgrade` 가 이제 어떤 환경에서도 동작합니다 — 이전에는 일반 pip 설치를 가정해서, 그렇지 않은 머신에서는 아무것도 못 하고 조용히 실패했습니다.
+
+- **설치 매니저 자동 감지** — upgrade 명령이 codebeacon 의 설치 방식을 감지해 맞는 도구를 실행합니다: pip 설치면 `pip install --upgrade`, pipx 면 `pipx upgrade codebeacon`, uv 면 `uv tool upgrade codebeacon`. pipx/uv tool 의 venv 에는 `pip` 모듈이 *없어서*, 기존의 무조건적인 `python -m pip` 호출은 시작도 못 하고 죽었습니다.
+- **업그레이드 검증** — 업그레이드 후 새 인터프리터로 설치된 버전을 다시 읽어 `0.6.4 -> 0.6.5` 처럼 보고합니다. 버전이 그대로인데 PyPI 에 더 새 릴리스가 있으면, 가짜 "Upgrade complete" 대신 PATH 의 `codebeacon` 이 다른 Python 환경 소속일 수 있다는 경고를 출력합니다.
+- **실패 메시지가 곧 해결책** — pip 없는 환경이면 실행할 정확한 명령을 안내하고, PEP 668 `externally-managed-environment` 거부에는 원시 pip 에러 대신 해결 방법(pipx 또는 virtualenv)을 설명합니다. 시작 시 현재 버전과 PyPI 최신 버전도 나란히 보여줍니다.
+
+---
+
 ## 0.6.4 새 소식
 
 Deep-dive 정리 — 출력물이 찾아보는 곳에 생성되도록 정돈하고, 47개 프로젝트 워크스페이스에서 이를 검증하던 중 발견한 조용한 데이터 손실 버그 2건 수정.
@@ -309,7 +342,7 @@ codebeacon install
 codebeacon upgrade
 ```
 
-이 명령은 pip 으로 패키지를 업그레이드한 뒤 `codebeacon install` 을 다시 실행해 `~/.claude/skills/codebeacon/SKILL.md` 을 새 릴리스의 사본으로 덮어씁니다. 새 SKILL.md 가 로드되려면 Claude Code 세션을 재시작하세요. editable 모드 (`pip install -e .`) 로 설치되어 있다면 pip 단계는 스킵됩니다 — 강제로 진행하려면 `--force` 를 붙이세요.
+이 명령은 설치에 사용된 도구(`pip`, `pipx upgrade`, `uv tool upgrade` — 자동 감지)로 패키지를 업그레이드하고, 설치된 버전이 실제로 바뀌었는지 검증한 뒤 `codebeacon install` 을 다시 실행해 `~/.claude/skills/codebeacon/SKILL.md` 을 새 릴리스의 사본으로 덮어씁니다. 새 SKILL.md 가 로드되려면 Claude Code 세션을 재시작하세요. editable 모드 (`pip install -e .`) 로 설치되어 있다면 패키지 단계는 스킵됩니다 — 강제로 진행하려면 `--force` 를 붙이세요.
 
 ### MCP 서버
 

codebeacon-0.6.4/PKG-INFO → codebeacon-0.6.7/README.md

@@ -1,96 +1,3 @@
-Metadata-Version: 2.4
-Name: codebeacon
-Version: 0.6.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
-Project-URL: Issues, https://github.com/codebeacon/codebeacon/issues
-License: MIT
-License-File: LICENSE
-Keywords: ai-context,ast,claude,codebase,knowledge-graph,mcp
-Classifier: Development Status :: 3 - Alpha
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Topic :: Software Development :: Build Tools
-Classifier: Topic :: Software Development :: Libraries :: Python Modules
-Requires-Python: >=3.10
-Requires-Dist: networkx>=3.0
-Requires-Dist: pyyaml>=6.0
-Requires-Dist: tree-sitter-javascript>=0.23
-Requires-Dist: tree-sitter-python>=0.23
-Requires-Dist: tree-sitter-typescript>=0.23
-Requires-Dist: tree-sitter>=0.23
-Provides-Extra: backend
-Requires-Dist: tree-sitter-c-sharp>=0.23; extra == 'backend'
-Requires-Dist: tree-sitter-go>=0.23; extra == 'backend'
-Requires-Dist: tree-sitter-java>=0.23; extra == 'backend'
-Requires-Dist: tree-sitter-kotlin>=0.23; extra == 'backend'
-Requires-Dist: tree-sitter-php>=0.23; extra == 'backend'
-Requires-Dist: tree-sitter-ruby>=0.23; extra == 'backend'
-Requires-Dist: tree-sitter-rust>=0.23; extra == 'backend'
-Provides-Extra: cluster
-Requires-Dist: graspologic>=1.0; extra == 'cluster'
-Provides-Extra: csharp
-Requires-Dist: tree-sitter-c-sharp>=0.23; extra == 'csharp'
-Provides-Extra: dev
-Requires-Dist: pytest-cov>=4.0; extra == 'dev'
-Requires-Dist: pytest>=7.0; extra == 'dev'
-Requires-Dist: tree-sitter-c-sharp>=0.23; extra == 'dev'
-Requires-Dist: tree-sitter-go>=0.23; extra == 'dev'
-Requires-Dist: tree-sitter-html>=0.23; extra == 'dev'
-Requires-Dist: tree-sitter-java>=0.23; extra == 'dev'
-Requires-Dist: tree-sitter-kotlin>=0.23; extra == 'dev'
-Requires-Dist: tree-sitter-php>=0.23; extra == 'dev'
-Requires-Dist: tree-sitter-ruby>=0.23; extra == 'dev'
-Requires-Dist: tree-sitter-rust>=0.23; extra == 'dev'
-Requires-Dist: tree-sitter-svelte>=0.23; extra == 'dev'
-Requires-Dist: tree-sitter-swift>=0.0.1; extra == 'dev'
-Provides-Extra: dotnet
-Requires-Dist: tree-sitter-c-sharp>=0.23; extra == 'dotnet'
-Provides-Extra: full
-Requires-Dist: tree-sitter-c-sharp>=0.23; extra == 'full'
-Requires-Dist: tree-sitter-go>=0.23; extra == 'full'
-Requires-Dist: tree-sitter-html>=0.23; extra == 'full'
-Requires-Dist: tree-sitter-java>=0.23; extra == 'full'
-Requires-Dist: tree-sitter-kotlin>=0.23; extra == 'full'
-Requires-Dist: tree-sitter-php>=0.23; extra == 'full'
-Requires-Dist: tree-sitter-ruby>=0.23; extra == 'full'
-Requires-Dist: tree-sitter-rust>=0.23; extra == 'full'
-Requires-Dist: tree-sitter-svelte>=0.23; extra == 'full'
-Requires-Dist: tree-sitter-swift>=0.0.1; extra == 'full'
-Provides-Extra: go
-Requires-Dist: tree-sitter-go>=0.23; extra == 'go'
-Provides-Extra: html
-Requires-Dist: tree-sitter-html>=0.23; extra == 'html'
-Provides-Extra: java
-Requires-Dist: tree-sitter-java>=0.23; extra == 'java'
-Provides-Extra: jvm
-Requires-Dist: tree-sitter-java>=0.23; extra == 'jvm'
-Requires-Dist: tree-sitter-kotlin>=0.23; extra == 'jvm'
-Provides-Extra: kotlin
-Requires-Dist: tree-sitter-kotlin>=0.23; extra == 'kotlin'
-Provides-Extra: mobile
-Requires-Dist: tree-sitter-kotlin>=0.23; extra == 'mobile'
-Requires-Dist: tree-sitter-swift>=0.0.1; extra == 'mobile'
-Provides-Extra: php
-Requires-Dist: tree-sitter-php>=0.23; extra == 'php'
-Provides-Extra: ruby
-Requires-Dist: tree-sitter-ruby>=0.23; extra == 'ruby'
-Provides-Extra: rust
-Requires-Dist: tree-sitter-rust>=0.23; extra == 'rust'
-Provides-Extra: svelte
-Requires-Dist: tree-sitter-svelte>=0.23; extra == 'svelte'
-Provides-Extra: swift
-Requires-Dist: tree-sitter-swift>=0.0.1; extra == 'swift'
-Provides-Extra: web
-Requires-Dist: tree-sitter-html>=0.23; extra == 'web'
-Requires-Dist: tree-sitter-svelte>=0.23; extra == 'web'
-Description-Content-Type: text/markdown
-
 <p align="center">
   <a href="https://github.com/Wandererer/codebeacon/blob/main/README.md"><img src="https://img.shields.io/badge/lang-English-blue" alt="English"></a>
   <a href="https://github.com/Wandererer/codebeacon/blob/main/README.ko.md"><img src="https://img.shields.io/badge/lang-한국어-red" alt="Korean"></a>
@@ -118,6 +25,39 @@ Description-Content-Type: text/markdown
 
 ---
 
+## 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.
+
+- **Grammar drift is a loud failure, not a silent empty graph** — when a tree-sitter query can't compile against a grammar it's *supposed* to support (e.g. a node-type rename in a future grammar bump), `run_query` now raises and the file is recorded as an `ExtractionFailure` instead of silently extracting nothing. Together with the 0.6.6 upper-bound pins and the "every query compiles against every grammar it claims" test, drift is now caught three independent ways.
+- **A single `!` negation in `.codebeaconignore` no longer forces a full-tree walk** — one negation rule anywhere used to disable directory pruning *everywhere*, so the scanner descended into every excluded directory (`node_modules`, `build`, …) even when the negation couldn't possibly rescue anything there. Each ignored directory is now kept only if a negation could actually re-include a file beneath *it*; unrelated `!` rules cost nothing.
+- **Ignore globs compile once** — the gitignore-style matcher memoizes each pattern's compiled regex instead of rebuilding it on every path check, speeding up discovery on deep trees with large ignore files. (Semantics unchanged.)
+
+---
+
+## What's new in 0.6.6
+
+A graphify-parity audit of upstream v0.8.37–v0.8.40 (and reported issues through #1362): a verify-then-adversarially-refute sweep of 32 candidates confirmed **6 real bugs**. The headline — three framework extractors were silently producing *nothing*.
+
+- **TypeScript Express / Koa / Fastify apps now extract routes** — `express.scm` hard-coded the JavaScript class-name node type, which is an "Impossible pattern" under the TypeScript grammar, so the whole query failed to compile and the error was swallowed: **TS Express apps extracted 0 routes**. (JavaScript apps worked, and the only test fixture was `.js`, so it went unnoticed.) The identical root cause hit `vue.scm` (Vue SFCs with a plain `<script>` → 0 components). Both now use a grammar-neutral node wildcard that compiles under JS and TS.
+- **Kotlin files in Spring projects no longer error** — `spring_boot.scm` is a Java-grammar query but was allowed to run against Kotlin, emitting `Invalid node type: marker_annotation` and dropping every `.kt` file. Kotlin is now gated off cleanly (Kotlin Spring Boot would need its own query).
+- **Tree-sitter grammars are pinned with upper bounds** — `pyproject.toml` pinned grammars open-ended (`>=0.23`), so a future grammar release that renames AST node types could silently re-break the queries. Every grammar now has a compatible-range ceiling, and a new test asserts every shipped `.scm` compiles against every grammar it claims to support.
+- **The extraction cache is versioned** — after upgrading codebeacon, an incremental `--update` could reuse results extracted by the *old* version for unchanged files (a content hash can't detect that the extractor itself changed). The cache is now stamped with the codebeacon version and discarded on mismatch.
+- **Accented / non-ASCII names resolve on macOS** — `codebeacon query` / `path` / MCP and `affected` now Unicode-NFC-normalise labels and paths, so a name copied from a macOS filename (stored as NFD) matches the NFC label in the graph (e.g. `Auditoría`).
+- Plus: a corrupt extraction `cache.json` is backed up and rebuilt instead of being silently reset and then overwritten.
+
+---
+
+## What's new in 0.6.5
+
+`codebeacon upgrade` now works everywhere — it previously assumed a plain pip install and died silently on machines where that wasn't true.
+
+- **Install-manager detection** — the upgrade command detects how codebeacon was installed and runs the matching tool: `pip install --upgrade` for pip installs, `pipx upgrade codebeacon` for pipx, `uv tool upgrade codebeacon` for uv. pipx/uv tool venvs ship *without* a `pip` module, so the old unconditional `python -m pip` call failed before doing anything.
+- **Upgrade verification** — after the upgrade a fresh interpreter re-reads the installed version and reports `0.6.4 -> 0.6.5`. If the version didn't change but PyPI has a newer release, you get a warning that the `codebeacon` on your PATH may belong to a different Python environment — instead of a false "Upgrade complete".
+- **Actionable failures** — a pip-less environment prints the exact commands to run; a PEP 668 `externally-managed-environment` refusal explains the fix (pipx or a virtualenv) instead of dumping a raw pip error. The command also shows the current vs. latest-on-PyPI version up front.
+
+---
+
 ## What's new in 0.6.4
 
 Deep-dive cleanup — outputs land where you look for them, and two silent-data-loss bugs found while verifying it on a 47-project workspace.
@@ -401,7 +341,7 @@ Run **one** command from anywhere:
 codebeacon upgrade
 ```
 
-This pip-upgrades the package, then re-runs `codebeacon install` so `~/.claude/skills/codebeacon/SKILL.md` is overwritten with the new release's copy. Restart your Claude Code session for the new SKILL.md to load. If codebeacon is installed in editable mode (`pip install -e .`), the pip step is skipped — pass `--force` to upgrade anyway.
+This upgrades the package using whichever tool installed it (`pip`, `pipx upgrade`, or `uv tool upgrade` — detected automatically), verifies the installed version actually changed, then re-runs `codebeacon install` so `~/.claude/skills/codebeacon/SKILL.md` is overwritten with the new release's copy. Restart your Claude Code session for the new SKILL.md to load. If codebeacon is installed in editable mode (`pip install -e .`), the package step is skipped — pass `--force` to upgrade anyway.
 
 ### MCP Server
 

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

@@ -27,6 +27,39 @@
 
 ---
 
+## 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.
+
+- **A deriva de gramática é uma falha ruidosa, não um grafo vazio silencioso** — quando uma query do tree-sitter não compila contra uma gramática que *deveria* suportar (p. ex. um nó renomeado em uma futura atualização de gramática), `run_query` agora lança uma exceção e o arquivo é registrado como `ExtractionFailure` em vez de extrair silenciosamente nada. Junto com os limites superiores da 0.6.6 e o teste "cada query compila contra cada gramática que declara suportar", a deriva agora é detectada de três formas independentes.
+- **Uma única negação `!` no `.codebeaconignore` não força mais um percurso completo da árvore** — uma regra de negação em qualquer lugar desativava o pruning de diretórios *em todo lugar*, então o scanner descia em cada diretório excluído (`node_modules`, `build`, …) mesmo quando a negação não podia resgatar nada ali. Agora um diretório ignorado só é mantido se uma negação realmente puder reincluir um arquivo *abaixo dele*; regras `!` não relacionadas não custam nada.
+- **Globs de ignore são compilados uma única vez** — o matcher no estilo gitignore memoiza a regex compilada por padrão em vez de reconstruí-la a cada verificação de caminho (descoberta mais rápida em árvores profundas com arquivos de ignore grandes). Semântica inalterada.
+
+---
+
+## Novidades na 0.6.6
+
+Uma auditoria de paridade com graphify do upstream v0.8.37–v0.8.40 (e issues reportadas até #1362): uma varredura de "verificar e então refutar de forma adversária" sobre 32 candidatos confirmou **6 bugs reais**. O destaque — três extratores de framework produziam silenciosamente *nada*.
+
+- **Apps Express/Koa/Fastify em TypeScript agora extraem rotas** — `express.scm` fixava o nó de nome de classe do JavaScript, que é um "Impossible pattern" sob a gramática do TypeScript, então a query inteira não compilava e o erro era engolido: **apps Express em TS extraíam 0 rotas**. (Apps JavaScript funcionavam, e a única fixture de teste era `.js`, então passou despercebido.) A mesma causa atingia `vue.scm` (SFCs Vue com `<script>` simples → 0 componentes). Ambos agora usam um coringa de nó neutro de gramática que compila em JS e TS.
+- **Arquivos Kotlin em projetos Spring não dão mais erro** — `spring_boot.scm` é uma query de gramática Java mas tinha permissão de rodar contra Kotlin, emitindo `Invalid node type: marker_annotation` e descartando cada arquivo `.kt`. Kotlin agora é bloqueado de forma limpa (Kotlin Spring Boot precisaria de sua própria query).
+- **Gramáticas do tree-sitter têm limites superiores fixados** — `pyproject.toml` fixava as gramáticas sem limite superior (`>=0.23`), então um futuro release de gramática que renomeasse nós da AST poderia quebrar as queries silenciosamente de novo. Cada gramática agora tem um teto de faixa compatível, e um novo teste verifica que cada `.scm` distribuída compila contra cada gramática que declara suportar.
+- **O cache de extração é versionado** — após atualizar o codebeacon, um `--update` incremental podia reutilizar resultados extraídos pela versão *antiga* para arquivos inalterados (um hash de conteúdo não detecta que o extrator mudou). O cache agora carrega a versão do codebeacon e é descartado em caso de divergência.
+- **Nomes acentuados / não ASCII resolvem no macOS** — `codebeacon query` / `path` / MCP e `affected` agora normalizam rótulos e caminhos para Unicode NFC, de modo que um nome copiado de um nome de arquivo do macOS (armazenado como NFD) corresponde ao rótulo NFC no grafo (p. ex. `Auditoría`).
+- Além disso: um `cache.json` corrompido é salvo em backup e reconstruído em vez de ser silenciosamente resetado e sobrescrito.
+
+---
+
+## Novidades na 0.6.5
+
+`codebeacon upgrade` agora funciona em qualquer ambiente — antes ele presumia uma instalação pip comum e falhava silenciosamente em máquinas onde não era o caso.
+
+- **Detecção do gerenciador de instalação** — o comando upgrade detecta como o codebeacon foi instalado e executa a ferramenta correspondente: `pip install --upgrade` para instalações pip, `pipx upgrade codebeacon` para pipx, `uv tool upgrade codebeacon` para uv. Os venvs do pipx/uv tool vêm *sem* o módulo `pip`, então a antiga chamada incondicional a `python -m pip` morria antes de fazer qualquer coisa.
+- **Verificação do upgrade** — após o upgrade, um interpretador novo relê a versão instalada e reporta `0.6.4 -> 0.6.5`. Se a versão não mudou mas o PyPI tem uma release mais nova, você recebe um aviso de que o `codebeacon` no seu PATH pode pertencer a outro ambiente Python — em vez de um falso "Upgrade complete".
+- **Falhas acionáveis** — um ambiente sem pip imprime os comandos exatos a executar; uma recusa PEP 668 `externally-managed-environment` explica a solução (pipx ou um virtualenv) em vez de despejar um erro pip cru. O comando também mostra logo de início a versão atual e a mais recente no PyPI.
+
+---
+
 ## Novidades na 0.6.4
 
 Limpeza do deep-dive — as saídas caem onde você procura por elas, mais dois bugs de perda silenciosa de dados encontrados ao verificá-lo num workspace de 47 projetos.