@salesforce/afv-skills 1.58.0 → 1.60.0

package/skills/experience-ui-bundle-custom-app-generate/scripts/resolve-uibundle-path.mjs

@@ -0,0 +1,40 @@
+#!/usr/bin/env node
+// Resolve the existing path of a UIBundle's meta XML file.
+//
+// UIBundle metadata may live at either the nested bundle-style path
+// (uiBundles/{appName}/{appName}.uibundle-meta.xml) or, in older/hand-authored
+// projects, the flat path (uiBundles/{appName}.uibundle-meta.xml). This script
+// performs the deterministic file-existence check and prints whichever path
+// already exists, preferring the nested layout.
+//
+// Always invoke via `node` (never as a bare executable) so this works on
+// Windows cmd/PowerShell as well as macOS/Linux/Git Bash.
+//
+// Usage: node scripts/resolve-uibundle-path.mjs <appName>
+//
+// Exit 0: existing meta XML found — its path is printed to stdout.
+// Exit 1: appName argument missing, or no .uibundle-meta.xml found for it.
+
+import fs from "node:fs";
+import path from "node:path";
+
+const APP = process.argv[2] ?? "";
+
+if (!APP) {
+  console.error("ERROR: appName argument is required");
+  process.exit(1);
+}
+
+const NESTED = path.join("uiBundles", APP, `${APP}.uibundle-meta.xml`);
+const FLAT = path.join("uiBundles", `${APP}.uibundle-meta.xml`);
+
+if (fs.existsSync(NESTED) && fs.statSync(NESTED).isFile()) {
+  console.log(NESTED);
+  process.exit(0);
+} else if (fs.existsSync(FLAT) && fs.statSync(FLAT).isFile()) {
+  console.log(FLAT);
+  process.exit(0);
+} else {
+  console.error(`ERROR: no .uibundle-meta.xml found for ${APP}`);
+  process.exit(1);
+}

package/skills/experience-ui-bundle-frontend-generate/SKILL.md

@@ -10,6 +10,8 @@ metadata:
     - "experience-ui-bundle-metadata-generate"
     - "experience-ui-bundle-salesforce-data-access"
   cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
     - tool: ["npm"]
       semver: ">=8.0.0"
     - tool: ["npx"]
@@ -22,7 +24,7 @@ metadata:
 
 ## Resolve the Bundle Directory
 
-**MUST** run `scripts/resolve-ui-bundle.sh [project-root]` before applying any rule below or writing any file — an ad-hoc `find`/`ls` is not a substitute; it does not enforce the exit-code gate below. It reads `sfdx-project.json`'s `packageDirectories[0].path` (does not assume `force-app` — the source path is configurable) and looks under `<sourceDir>/main/default/uiBundles/`:
+**MUST** run `node scripts/resolve-ui-bundle.mjs [project-root]` before applying any rule below or writing any file — an ad-hoc `find`/`ls` is not a substitute; it does not enforce the exit-code gate below. Always invoke via `node` (never as a bare executable) so this works on Windows as well as macOS/Linux. It reads `sfdx-project.json`'s `packageDirectories[0].path` (does not assume `force-app` — the source path is configurable) and looks under `<sourceDir>/main/default/uiBundles/`:
 
 - **Exit 0**, bundle path printed to stdout: exactly one bundle directory found — that is the bundle directory. Use that exact directory name; never substitute a different name (e.g. a generic "AcmePortal" example from a prompt template) for the one actually printed.
 - **Exit 2**, candidates printed to stderr: multiple `uiBundles/*` subdirectories exist — do not guess, and do not write to any of them, or to a bundle name not in the printed list. Ask the user which app/bundle they mean before editing or running any command.
@@ -32,10 +34,10 @@ Run all `npm`/lint/build/dev commands from inside the resolved bundle directory,
 
 ## Preconditions
 
-Before applying any rule below, confirm this is an existing, scaffolded UI bundle: **MUST** run `scripts/check-preconditions.sh <bundle-dir>` with the directory `resolve-ui-bundle.sh` printed.
+Before applying any rule below, confirm this is an existing, scaffolded UI bundle: **MUST** run `node scripts/check-preconditions.mjs <bundle-dir>` with the directory `resolve-ui-bundle.mjs` printed.
 
 - **Single-bundle (exit 0) case**: run it once, on that bundle.
-- **Multi-bundle (exit 2) case**: do not run it yet — first ask the user which app/bundle they mean, per the Resolve step above. Once the user names the bundle, run `check-preconditions.sh` on that one bundle only. Never run it against multiple candidates speculatively before the user has chosen — that means touching/inspecting bundles the user didn't ask about.
+- **Multi-bundle (exit 2) case**: do not run it yet — first ask the user which app/bundle they mean, per the Resolve step above. Once the user names the bundle, run `check-preconditions.mjs` on that one bundle only. Never run it against multiple candidates speculatively before the user has chosen — that means touching/inspecting bundles the user didn't ask about.
 - **Exit 0**: the bundle has `src/appLayout.tsx`, `src/routes.tsx`, and `src/components/ui/` — proceed.
 - **Exit 1**, missing pieces listed: this is a fresh SFDX project, a non-UI-bundle React project, or a partially-scaffolded bundle — **stop**. Do not fall back to generic React knowledge (e.g. `react-router-dom`, a hardcoded basename, or raw HTML), and do not hand-write `appLayout.tsx`/`routes.tsx`/a page/a component to "fill in" the missing scaffold, even for a casual, vague, or urgent-sounding request ("just change the header", "make the background blue"). Tell the user the bundle isn't scaffolded yet and direct them to `experience-ui-bundle-app-coordinate` (or `experience-ui-bundle-metadata-generate`) to scaffold it first. If, after the user names their intended bundle, that one turns out to be unscaffolded, stop and redirect for it — do not silently switch to scaffolding a different candidate instead.
 
@@ -80,7 +82,7 @@ When making any change that affects navigation, header, footer, sidebar, theme,
 
 `index.html` lives at the bundle root (not under `src/`), but it is still in scope for this skill whenever branding or the app name changes — the leftover `<title>React App</title>` / `Vite + React` boilerplate is a common ship-blocker that `npm run lint`/`npm run build` never catches.
 
-Before finishing, confirm: Did I update `appLayout.tsx` with real nav items and branding? Then run `scripts/verify-rules.sh` to check for residual boilerplate (see Verification below).
+Before finishing, confirm: Did I update `appLayout.tsx` with real nav items and branding? Then run `node scripts/verify-rules.mjs` to check for residual boilerplate (see Verification below).
 
 | What | Where |
 |------|-------|
@@ -191,7 +193,7 @@ Before completing, run all of the following from the resolved UI bundle director
 2. `npm run build` — must succeed.
 3. `npm run dev` (or the project's dev-server script) — confirm the app starts cleanly so the change is verified at runtime, not just at build time.
 
-**`lint`/`build` alone do not catch the highest-risk rules in this skill** — a wrong `react-router-dom` import, a hardcoded basename, an inline `style={{}}`, or a stray `lightning/*` import can all lint and build clean while breaking at runtime. After any change that touches routing, layout, styling, or module imports, run `scripts/verify-rules.sh <files-or-dirs-you-edited>`:
+**`lint`/`build` alone do not catch the highest-risk rules in this skill** — a wrong `react-router-dom` import, a hardcoded basename, an inline `style={{}}`, or a stray `lightning/*` import can all lint and build clean while breaking at runtime. After any change that touches routing, layout, styling, or module imports, run `node scripts/verify-rules.mjs <files-or-dirs-you-edited>`:
 
 - **Exit 0**: no violations found.
 - **Exit 1**, violations listed by rule and file: fix every one before considering the task complete, even if lint and build passed.

package/skills/experience-ui-bundle-frontend-generate/scripts/check-preconditions.mjs

@@ -0,0 +1,70 @@
+#!/usr/bin/env node
+// Verify a resolved UI bundle directory is actually scaffolded before any
+// rule in this skill applies.
+// Usage: node check-preconditions.mjs <bundle-dir>
+//   <bundle-dir> is the path printed by resolve-ui-bundle.mjs.
+//
+// Always invoke via `node` (never as a bare executable) so this works on
+// Windows cmd/PowerShell as well as macOS/Linux/Git Bash. Quote
+// <bundle-dir> so Windows paths and spaces survive the shell.
+//
+// Exit 0 if the bundle is scaffolded (src/appLayout.tsx, src/routes.tsx, and
+// src/components/ui/ all present).
+// Exit 1 with the missing pieces listed if the bundle is a fresh SFDX
+// project, a non-UI-bundle React project, or only partially scaffolded —
+// the caller must stop and redirect the user to
+// experience-ui-bundle-app-coordinate (or experience-ui-bundle-metadata-generate)
+// instead of falling back to generic React knowledge.
+
+import fs from "node:fs";
+import path from "node:path";
+
+const BUNDLE_DIR = process.argv[2] ?? "";
+
+function fail(message) {
+  console.error(message);
+  process.exit(1);
+}
+
+if (!BUNDLE_DIR) {
+  fail("ERROR: check-preconditions.mjs requires a valid bundle directory argument");
+}
+
+let isDir = false;
+try {
+  isDir = fs.statSync(BUNDLE_DIR).isDirectory();
+} catch {
+  isDir = false;
+}
+
+if (!isDir) {
+  fail("ERROR: check-preconditions.mjs requires a valid bundle directory argument");
+}
+
+const missing = [];
+if (!fs.existsSync(path.join(BUNDLE_DIR, "src", "appLayout.tsx"))) {
+  missing.push("src/appLayout.tsx");
+}
+if (!fs.existsSync(path.join(BUNDLE_DIR, "src", "routes.tsx"))) {
+  missing.push("src/routes.tsx");
+}
+const uiDir = path.join(BUNDLE_DIR, "src", "components", "ui");
+if (!fs.existsSync(uiDir) || !fs.statSync(uiDir).isDirectory()) {
+  missing.push("src/components/ui/");
+}
+
+if (missing.length > 0) {
+  console.error(`ERROR: ${BUNDLE_DIR} is not a scaffolded UI bundle. Missing:`);
+  for (const item of missing) {
+    console.error(`  - ${item}`);
+  }
+  console.error(
+    "Stop here. Tell the user the bundle isn't scaffolded yet and direct them to experience-ui-bundle-app-coordinate (or experience-ui-bundle-metadata-generate) to scaffold it first.",
+  );
+  process.exit(1);
+}
+
+console.log(
+  `SUCCESS: ${BUNDLE_DIR} is scaffolded (src/appLayout.tsx, src/routes.tsx, src/components/ui/ present)`,
+);
+process.exit(0);

package/skills/experience-ui-bundle-frontend-generate/scripts/resolve-ui-bundle.mjs

@@ -0,0 +1,76 @@
+#!/usr/bin/env node
+// Resolve the single UI bundle directory for this project.
+// Usage: node resolve-ui-bundle.mjs [project-root]   (default: current directory)
+//
+// Reads sfdx-project.json's packageDirectories[0].path, looks under
+// <that-path>/main/default/uiBundles/, and prints the resolved bundle
+// directory to stdout on success.
+//
+// Always invoke via `node` (never as a bare executable) so this works on
+// Windows cmd/PowerShell as well as macOS/Linux/Git Bash. Quote the
+// project-root argument so paths with spaces or Windows backslashes stay
+// a single argv.
+//
+// Exit 0: exactly one bundle directory found — printed to stdout.
+// Exit 1: sfdx-project.json missing/invalid, or no uiBundles/* subdirectory
+//         found at all (not a scaffolded SFDX project yet).
+// Exit 2: multiple uiBundles/* subdirectories found — caller MUST ask the
+//         user which one they mean rather than guessing; candidate names are
+//         printed to stderr.
+
+import fs from "node:fs";
+import path from "node:path";
+
+const PROJECT_ROOT = path.resolve(process.argv[2] ?? ".");
+const SFDX_PROJECT = path.join(PROJECT_ROOT, "sfdx-project.json");
+
+function fail(code, message) {
+  console.error(message);
+  process.exit(code);
+}
+
+if (!fs.existsSync(SFDX_PROJECT) || !fs.statSync(SFDX_PROJECT).isFile()) {
+  fail(1, `ERROR: sfdx-project.json not found at ${SFDX_PROJECT}`);
+}
+
+let sourcePath = "";
+try {
+  const data = JSON.parse(fs.readFileSync(SFDX_PROJECT, "utf8"));
+  const dirs = data?.packageDirectories ?? [];
+  sourcePath = dirs[0]?.path ?? "";
+} catch {
+  sourcePath = "";
+}
+
+if (!sourcePath) {
+  fail(1, "ERROR: sfdx-project.json is invalid or has no packageDirectories[0].path");
+}
+
+const BUNDLES_DIR = path.join(PROJECT_ROOT, sourcePath, "main", "default", "uiBundles");
+
+if (!fs.existsSync(BUNDLES_DIR) || !fs.statSync(BUNDLES_DIR).isDirectory()) {
+  fail(1, `ERROR: No uiBundles/ directory found at ${BUNDLES_DIR}`);
+}
+
+const bundleDirs = fs
+  .readdirSync(BUNDLES_DIR, { withFileTypes: true })
+  .filter((entry) => entry.isDirectory())
+  .map((entry) => path.join(BUNDLES_DIR, entry.name))
+  .sort();
+
+if (bundleDirs.length === 0) {
+  fail(1, `ERROR: ${BUNDLES_DIR} exists but contains no bundle subdirectories`);
+}
+
+if (bundleDirs.length > 1) {
+  console.error(
+    "AMBIGUOUS: Multiple UI bundle directories found — ask the user which one they mean before editing or running any command:",
+  );
+  for (const dir of bundleDirs) {
+    console.error(`  - ${dir}`);
+  }
+  process.exit(2);
+}
+
+console.log(bundleDirs[0]);
+process.exit(0);

package/skills/experience-ui-bundle-frontend-generate/scripts/verify-rules.mjs

@@ -0,0 +1,115 @@
+#!/usr/bin/env node
+// Verification of the hard, checkable rules in this skill that
+// `npm run lint` / `npm run build` do not catch on their own — a wrong
+// react-router-dom import, a hardcoded basename, an inline style prop, a
+// stray lightning/*-or-@wire import, or leftover template boilerplate can
+// all lint and build clean while breaking at runtime or shipping unfinished
+// branding.
+//
+// Usage: node verify-rules.mjs <file-or-dir> [<file-or-dir> ...]
+//   Pass the specific files you edited, or the bundle's src/ directory (and
+//   its index.html) to check everything.
+//
+// Always invoke via `node` (never as a bare executable, and never via a
+// shell-specific tool like grep/sed) so this works on Windows
+// cmd/PowerShell as well as macOS/Linux/Git Bash. Quote path arguments so
+// Windows paths and spaces survive the shell.
+//
+// Exit 0 if no violations are found.
+// Exit 1 with every violation listed (rule + matching file paths) if any
+// are found — fix them before considering the task complete, even if lint
+// and build passed.
+
+import fs from "node:fs";
+import path from "node:path";
+
+const INCLUDE_EXT = new Set([".ts", ".tsx", ".js", ".jsx", ".html"]);
+const EXCLUDE_DIRS = new Set(["node_modules", "dist", "build"]);
+
+const RULES = [
+  {
+    label: 'import from "react-router-dom" (must be "react-router")',
+    pattern: /from\s+['"]react-router-dom['"]/,
+  },
+  {
+    label: "a hardcoded basename literal (must derive from <base href> at runtime)",
+    pattern: /basename:\s*['"][/A-Za-z0-9_-]+['"]/,
+  },
+  {
+    label: "an inline style={{...}} prop (Tailwind utility classes only)",
+    pattern: /style=\{\{/,
+  },
+  {
+    label: "a forbidden lightning/* import or @wire usage (LWC-only)",
+    pattern: /from\s+['"]lightning\/|@wire/,
+  },
+  {
+    label: "leftover boilerplate branding (<title>React App</title> / Vite + React)",
+    pattern: /<title>[^<]*React App[^<]*<\/title>|Vite\s*\+\s*React/,
+  },
+];
+
+const targets = process.argv.slice(2);
+
+if (targets.length === 0) {
+  console.error("ERROR: verify-rules.mjs requires at least one file or directory argument");
+  process.exit(1);
+}
+
+for (const p of targets) {
+  if (!fs.existsSync(p)) {
+    console.error(`ERROR: path does not exist: ${p}`);
+    process.exit(1);
+  }
+}
+
+function collectFiles(target, out) {
+  const stat = fs.statSync(target);
+  if (stat.isDirectory()) {
+    const base = path.basename(target);
+    if (EXCLUDE_DIRS.has(base)) return;
+    for (const entry of fs.readdirSync(target, { withFileTypes: true })) {
+      collectFiles(path.join(target, entry.name), out);
+    }
+    return;
+  }
+  if (stat.isFile() && INCLUDE_EXT.has(path.extname(target))) {
+    out.push(target);
+  }
+}
+
+const files = [];
+for (const t of targets) {
+  collectFiles(t, files);
+}
+
+let found = false;
+
+for (const rule of RULES) {
+  const hits = [];
+  for (const file of files) {
+    let content;
+    try {
+      content = fs.readFileSync(file, "utf8");
+    } catch {
+      continue;
+    }
+    if (rule.pattern.test(content)) {
+      hits.push(file);
+    }
+  }
+  if (hits.length > 0) {
+    found = true;
+    console.error(`ERROR: ${rule.label} found in:`);
+    for (const hit of hits) {
+      console.error(`  - ${hit}`);
+    }
+  }
+}
+
+if (found) {
+  process.exit(1);
+}
+
+console.log(`SUCCESS: No hard-rule violations found in: ${targets.join(" ")}`);
+process.exit(0);

package/skills/experience-ui-bundle-metadata-generate/SKILL.md

@@ -13,6 +13,8 @@ metadata:
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6.0"
+    - tool: ["node"]
+      semver: ">=18.0.0"
     - tool: ["sf"]
       semver: ">=2.0.0"
 ---
@@ -32,9 +34,11 @@ The frameworks this skill supports are exactly the reference files under `<skill
 **Detect the framework deterministically — run the script:**
 
 ```sh
-bash <skill_dir>/scripts/detect-framework.sh [<ROOT>]
+node <skill_dir>/scripts/detect-framework.mjs [<ROOT>]
 ```
 
+Always invoke via `node` (never as a bare executable) so this works on Windows cmd/PowerShell as well as macOS/Linux/Git Bash.
+
 `ROOT` defaults to the current directory; pass the bundle or project root when editing/configuring an existing bundle. The script prints exactly one token and sets a matching exit code — branch on it:
 
 - `react` / `angular` (exit 0) — open `<skill_dir>/references/<framework>-metadata-generate.md` and use it.
@@ -49,8 +53,8 @@ The reference file gives you the exact `--template` flag, the entry-file layout,
 - Pass `--output-dir` to use a different location for template generation. If you do, pass that same path to the verification script in step 1 below.
 
 After generation:
-1. **Verify the scaffold is complete** — run `bash <skill_dir>/scripts/verify-bundle-location.sh <BundleName> [<CustomOutputDir>] [<framework>]` from the project root and follow any error output. This checks both the bundle's location AND that `package.json`, `src/`, and an entry `index.html` exist — if any are missing, the scaffold step was skipped; go back and run `sf template generate ui-bundle` before continuing. Pass `<CustomOutputDir>` only if you used `--output-dir` during scaffolding (pass `""` to skip it while still supplying a framework); pass `<framework>` (`react` or `angular`) so the remediation hint uses the right template.
-2. **Verify API version** — run `bash <skill_dir>/scripts/check-api-version.sh` from the project root to ensure `sourceApiVersion` in `sfdx-project.json` is 67.0 or higher. The script will automatically update it if needed.
+1. **Verify the scaffold is complete** — run `node <skill_dir>/scripts/verify-bundle-location.mjs <BundleName> [<CustomOutputDir>] [<framework>]` from the project root and follow any error output. This checks both the bundle's location AND that `package.json`, `src/`, and an entry `index.html` exist — if any are missing, the scaffold step was skipped; go back and run `sf template generate ui-bundle` before continuing. Pass `<CustomOutputDir>` only if you used `--output-dir` during scaffolding (pass `""` to skip it while still supplying a framework); pass `<framework>` (`react` or `angular`) so the remediation hint uses the right template.
+2. **Verify API version** — run `node <skill_dir>/scripts/check-api-version.mjs` from the project root to ensure `sourceApiVersion` in `sfdx-project.json` is 67.0 or higher. The script will automatically update it if needed.
 3. Replace all default boilerplate — the framework reference file lists the exact stock `<title>` and placeholder strings to replace
 4. Populate the home page with real content (landing section, banners, hero, navigation)
 5. Update navigation and placeholders (see the `experience-ui-bundle-frontend-generate` skill)

package/skills/experience-ui-bundle-metadata-generate/references/angular-metadata-generate.md

@@ -12,7 +12,7 @@ Always pass `--template angularbasic` to scaffold an Angular bundle:
 sf template generate ui-bundle -n CoffeeBoutique --template angularbasic
 ```
 
-Pass `--output-dir` to generate at a different location. If you do, pass that same path to `verify-bundle-location.sh` in the verification step.
+Pass `--output-dir` to generate at a different location. If you do, pass that same path to `verify-bundle-location.mjs` in the verification step.
 
 ## What the scaffold produces
 

package/skills/experience-ui-bundle-metadata-generate/references/react-metadata-generate.md

@@ -12,7 +12,7 @@ Always pass `--template reactbasic` to scaffold a React/Vite bundle:
 sf template generate ui-bundle -n CoffeeBoutique --template reactbasic
 ```
 
-Pass `--output-dir` to generate at a different location. If you do, pass that same path to `verify-bundle-location.sh` in the verification step.
+Pass `--output-dir` to generate at a different location. If you do, pass that same path to `verify-bundle-location.mjs` in the verification step.
 
 ## What the scaffold produces
 

package/skills/experience-ui-bundle-metadata-generate/scripts/check-api-version.mjs

@@ -0,0 +1,43 @@
+#!/usr/bin/env node
+// Checks that sourceApiVersion in sfdx-project.json is 67.0 or higher.
+// If lower, updates it to "67.0".
+//
+// Usage: node check-api-version.mjs
+//
+// Always invoke via `node` (never as a bare executable) so this works on
+// Windows cmd/PowerShell as well as macOS/Linux/Git Bash. Parses and rewrites
+// sfdx-project.json with native JSON (no jq dependency).
+
+import fs from "node:fs";
+
+const PROJECT_FILE = "sfdx-project.json";
+
+if (!fs.existsSync(PROJECT_FILE) || !fs.statSync(PROJECT_FILE).isFile()) {
+  console.log(`ERROR: ${PROJECT_FILE} not found in current directory`);
+  process.exit(1);
+}
+
+let data;
+try {
+  data = JSON.parse(fs.readFileSync(PROJECT_FILE, "utf8"));
+} catch {
+  console.log(`ERROR: ${PROJECT_FILE} is not valid JSON`);
+  process.exit(1);
+}
+
+const version = data.sourceApiVersion || "0";
+const major = Number.parseInt(String(version).split(".")[0], 10);
+const isBelow = Number.isNaN(major) || major < 67;
+
+if (isBelow) {
+  console.log(`WARNING: sourceApiVersion is ${version} (< 67.0)`);
+  console.log(`Updating ${PROJECT_FILE} to set sourceApiVersion to "67.0"`);
+
+  data.sourceApiVersion = "67.0";
+  fs.writeFileSync(PROJECT_FILE, `${JSON.stringify(data, null, 2)}\n`);
+
+  console.log("OK: Updated sourceApiVersion to 67.0");
+  process.exit(0);
+}
+
+console.log(`OK: sourceApiVersion is ${version} (>= 67.0)`);

package/skills/experience-ui-bundle-metadata-generate/scripts/detect-framework.mjs

@@ -0,0 +1,131 @@
+#!/usr/bin/env node
+//
+// detect-framework.mjs — deterministic UI Bundle framework detector.
+//
+// Usage: node detect-framework.mjs [ROOT]
+//   ROOT  app or uiBundle root to inspect (default: current directory)
+//
+// Always invoke via `node` (never as a bare executable) so this works on
+// Windows cmd/PowerShell as well as macOS/Linux/Git Bash.
+//
+// Prints exactly one of the following tokens to stdout, nothing else, and sets
+// a matching exit code so callers can branch without parsing:
+//   react      (exit 0) — React signals only
+//   angular    (exit 0) — Angular signals only
+//   ambiguous  (exit 2) — both React and Angular signals present
+//   unknown    (exit 3) — neither framework detected
+//
+// Step 0 of the skill acts on the result: a single framework (exit 0) proceeds;
+// `ambiguous` asks the user to disambiguate; `unknown` TERMINATES the workflow
+// (no supported framework found — do not guess).
+
+import fs from "node:fs";
+import path from "node:path";
+
+const ROOT = process.argv[2] ?? ".";
+
+let angular = false;
+let react = false;
+
+// Resolve ROOT to an absolute path when possible (for the angular.json walk-up).
+let absRoot = "";
+try {
+  if (fs.statSync(ROOT).isDirectory()) {
+    absRoot = fs.realpathSync(ROOT);
+  }
+} catch {
+  absRoot = "";
+}
+
+// 1) angular.json at or above ROOT → Angular workspace.
+if (absRoot) {
+  let dir = absRoot;
+  for (;;) {
+    if (fs.existsSync(path.join(dir, "angular.json"))) {
+      angular = true;
+    }
+    const parent = path.dirname(dir);
+    if (parent === dir) break;
+    dir = parent;
+  }
+}
+
+// Recursively collect file paths under `root`, skipping node_modules directories.
+function walk(root) {
+  const results = [];
+  const stack = [root];
+  while (stack.length > 0) {
+    const current = stack.pop();
+    let entries;
+    try {
+      entries = fs.readdirSync(current, { withFileTypes: true });
+    } catch {
+      continue;
+    }
+    for (const entry of entries) {
+      if (entry.isDirectory()) {
+        if (entry.name === "node_modules") continue;
+        stack.push(path.join(current, entry.name));
+      } else if (entry.isFile()) {
+        results.push(path.join(current, entry.name));
+      }
+    }
+  }
+  return results;
+}
+
+const files = walk(ROOT);
+
+// 2) package.json dependencies (excluding node_modules).
+for (const file of files) {
+  if (path.basename(file) !== "package.json") continue;
+  let content = "";
+  try {
+    content = fs.readFileSync(file, "utf8");
+  } catch {
+    continue;
+  }
+  if (content.includes('"@angular/core"')) angular = true;
+  if (/"react"\s*:/.test(content)) react = true;
+}
+
+// 3) Source-file signatures (excluding node_modules).
+function hasFile(matches) {
+  return files.some(matches);
+}
+
+// Angular: component files, routing module, or @Component-decorated classes.
+if (hasFile((f) => f.endsWith(".component.ts"))) angular = true;
+if (hasFile((f) => path.basename(f) === "app.routes.ts")) angular = true;
+
+for (const file of files) {
+  if (!file.endsWith(".ts")) continue;
+  let content = "";
+  try {
+    content = fs.readFileSync(file, "utf8");
+  } catch {
+    continue;
+  }
+  if (content.includes("@Component")) {
+    angular = true;
+    break;
+  }
+}
+
+// React: JSX/TSX source files.
+if (hasFile((f) => f.endsWith(".tsx"))) react = true;
+if (hasFile((f) => f.endsWith(".jsx"))) react = true;
+
+if (angular && react) {
+  console.log("ambiguous");
+  process.exit(2);
+} else if (angular) {
+  console.log("angular");
+  process.exit(0);
+} else if (react) {
+  console.log("react");
+  process.exit(0);
+} else {
+  console.log("unknown");
+  process.exit(3);
+}