@theglitchking/babel-fish 2.0.0 → 2.0.1

package/.claude/install.sh

@@ -456,7 +456,6 @@ CLAUDEMD
 # ║  MAIN FLOW                                                               ║
 # ╚══════════════════════════════════════════════════════════════════════════╝
 
-clear
 printf '%b\n' "
 ${CYAN}${BOLD}
   ╔══════════════════════════════════════════╗

package/.claude/project-map/generate.py

@@ -603,19 +603,32 @@ class FrontendScanner:
     FEATURE_DIRS = {'features', 'pages', 'views', 'screens', 'modules', 'app'}
     COMPONENT_EXTS = {'.tsx', '.jsx'}
     HOOK_PATTERN = re.compile(r'^use[A-Z]')
+    # Candidate bases to search for the FEATURE_DIRS, relative to PROJECT_ROOT.
+    # Covers repo-root and src/ layouts plus monorepos where the frontend is a
+    # subpackage (e.g. frontend/src/features), not just at the repo root.
+    SEARCH_PREFIXES = ('', 'src', 'frontend', 'frontend/src',
+                       'web', 'web/src', 'client', 'client/src', 'ui', 'ui/src')
 
     def scan(self) -> list[dict]:
-        features = []
-        for feat_dir_name in self.FEATURE_DIRS:
-            feat_dir = PROJECT_ROOT / feat_dir_name
-            if not feat_dir.exists():
-                # try nested src/
-                feat_dir = PROJECT_ROOT / 'src' / feat_dir_name
-            if not feat_dir.is_dir():
-                continue
-            for entry in sorted(feat_dir.iterdir()):
-                if entry.is_dir() and not entry.name.startswith('.'):
+        features, seen = [], set()
+        for prefix in self.SEARCH_PREFIXES:
+            base = PROJECT_ROOT / prefix if prefix else PROJECT_ROOT
+            for feat_dir_name in self.FEATURE_DIRS:
+                feat_dir = base / feat_dir_name
+                if not feat_dir.is_dir():
+                    continue
+                for entry in sorted(feat_dir.iterdir()):
+                    if not (entry.is_dir() and not entry.name.startswith('.')):
+                        continue
+                    rp = entry.resolve()
+                    if rp in seen:
+                        continue  # already counted via another prefix
                     stats = self._scan_feature_dir(entry)
+                    # Only emit dirs that actually contain frontend components, so a
+                    # backend package named e.g. 'app/' is not misread as a feature.
+                    if stats['component_count'] + stats['hook_count'] == 0:
+                        continue
+                    seen.add(rp)
                     stats['name'] = entry.name
                     stats['path'] = str(entry.relative_to(PROJECT_ROOT))
                     features.append(stats)

package/.claude/settings.local.json

@@ -0,0 +1,6 @@
+{
+  "enabledMcpjsonServers": [
+    "semantic-vault"
+  ],
+  "enableAllProjectMcpServers": true
+}

package/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.0.1] - 2026-06-08
+
+### Fixed
+
+- **Frontend feature scanner now detects monorepo layouts.** `FrontendScanner`
+  previously looked for `features/`, `pages/`, `views/`, etc. only at the repo
+  root or under a top-level `src/`. Projects that keep the frontend in a
+  subpackage (e.g. `frontend/src/features/`, the common React/Vite plus Python
+  backend split) were reported as "No frontend feature directories detected,"
+  leaving project-map sections 09 (Frontend Features) and 13 (Frontend to
+  Backend Map) empty. The scanner now searches `frontend/`, `web/`, `client/`,
+  and `ui/` (each with an optional `src/`) in addition to the repo root and
+  `src/`, dedupes by resolved path, and only emits directories that actually
+  contain `.jsx`/`.tsx` files so a backend package named `app/` is not
+  misclassified as a frontend feature.
+
 ## [2.0.0] — 2026-04-19
 
 ### Breaking changes

package/README.md

@@ -8,6 +8,9 @@
 [![Status: Production Ready](https://img.shields.io/badge/Status-Production%20Ready-green.svg)]()
 [![GitHub: TheGlitchKing/babel-fish](https://img.shields.io/badge/GitHub-TheGlitchKing%2Fbabel--fish-blue)](https://github.com/TheGlitchKing/babel-fish)
 
+> [!NOTE]
+> **Pairs with [`semantic-memory`](https://github.com/TheGlitchKing/semantic-sidekick) (formerly `semantic-sidekick`).** When both are installed, semantic-memory consumes babel-fish's auto-generated `.babel-fish/` output as a `project-map` corpus AND extracts `01-vocabulary.md` into a structured `glossary.json` side-channel. That gives your AI a deterministic `translate("deals page") → "features/deal-pipeline/DealPipeline.tsx"` MCP verb instead of relying on semantic-search-luck. See [`docs/glossary-contract.md`](./docs/glossary-contract.md) for the producer/consumer data contract and [`docs/integration-with-semantic-memory.md`](./docs/integration-with-semantic-memory.md) for the setup walkthrough. babel-fish standalone behavior is unchanged — semantic-memory is purely additive.
+
 ---
 
 ## What Does This Do?

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theglitchking/babel-fish",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "Gives your AI coding assistant instant, accurate knowledge of every route, model, service, feature, and infrastructure element in your codebase.",
   "type": "module",
   "bin": {