fix: repoint docs base path and links to renamed repo

The repo was renamed codeanalyzer-ts -> codeanalyzer-typescript, but the
Astro base and all hardcoded content links still pointed at the old name,
so GitHub Pages (now served at /codeanalyzer-typescript/) 404'd every
asset — the site rendered unstyled. Update base, site edit links, and the
/codeanalyzer-ts/ content-link prefixes.

Author: rahlk

.codeanalyzer/analysis_cache.json

@@ -1,6 +1,6 @@
 # codeanalyzer-typescript — documentation site
 
-This branch holds the documentation site for [**codeanalyzer-typescript**](https://github.com/codellm-devkit/codeanalyzer-ts), the TypeScript/JavaScript static-analysis backend behind [CLDK](https://github.com/codellm-devkit/python-sdk). The tool's source code lives on `main`; this `docs` branch is the [Astro](https://astro.build/) + [Starlight](https://starlight.astro.build/) site that documents it.
+This branch holds the documentation site for [**codeanalyzer-typescript**](https://github.com/codellm-devkit/codeanalyzer-typescript), the TypeScript/JavaScript static-analysis backend behind [CLDK](https://github.com/codellm-devkit/python-sdk). The tool's source code lives on `main`; this `docs` branch is the [Astro](https://astro.build/) + [Starlight](https://starlight.astro.build/) site that documents it.
 
 ## Develop
 
@@ -36,22 +36,22 @@ astro.config.mjs                    # site + sidebar config
 
 ## Internal links (important)
 
-The site is served from a **base path** — `https://codellm-devkit.github.io/codeanalyzer-ts/` (set via `site` + `base` in `astro.config.mjs`). Astro does **not** rewrite links in page content, so every internal link must include the base prefix:
+The site is served from a **base path** — `https://codellm-devkit.github.io/codeanalyzer-typescript/` (set via `site` + `base` in `astro.config.mjs`). Astro does **not** rewrite links in page content, so every internal link must include the base prefix:
 
 ```md
 <!-- correct -->
-[Quickstart](/codeanalyzer-ts/quickstart/)
-<LinkCard href="/codeanalyzer-ts/guides/concepts/" ... />
+[Quickstart](/codeanalyzer-typescript/quickstart/)
+<LinkCard href="/codeanalyzer-typescript/guides/concepts/" ... />
 
 <!-- WRONG — 404s at the base path -->
 [Quickstart](/quickstart/)
 ```
 
-Sidebar `slug` entries in `astro.config.mjs` and assets are based automatically — only authored links in `.mdx` need the prefix. To verify after editing, build and grep `dist/` for any `href="/…"` that doesn't start with `/codeanalyzer-ts/`.
+Sidebar `slug` entries in `astro.config.mjs` and assets are based automatically — only authored links in `.mdx` need the prefix. To verify after editing, build and grep `dist/` for any `href="/…"` that doesn't start with `/codeanalyzer-typescript/`.
 
 ## Deploy
 
-Pushing to `docs` triggers `.github/workflows/deploy.yml`, which builds the site and publishes `dist/` to the `gh-pages` branch. GitHub Pages then serves it at `https://codellm-devkit.github.io/codeanalyzer-ts/`.
+Pushing to `docs` triggers `.github/workflows/deploy.yml`, which builds the site and publishes `dist/` to the `gh-pages` branch. GitHub Pages then serves it at `https://codellm-devkit.github.io/codeanalyzer-typescript/`.
 
 ## License
 

README.md

@@ -7,7 +7,7 @@ import { pluginLineNumbers } from "@expressive-code/plugin-line-numbers";
 // https://astro.build/config
 export default defineConfig({
   site: "https://codellm-devkit.github.io",
-  base: "/codeanalyzer-ts",
+  base: "/codeanalyzer-typescript",
   integrations: [
     // Mermaid must run BEFORE Starlight so it can preprocess ```mermaid blocks.
     mermaid({
@@ -65,12 +65,12 @@ export default defineConfig({
         {
           icon: "github",
           label: "codeanalyzer-typescript on GitHub",
-          href: "https://github.com/codellm-devkit/codeanalyzer-ts",
+          href: "https://github.com/codellm-devkit/codeanalyzer-typescript",
         },
         {
           icon: "seti:typescript",
           label: "codeanalyzer-typescript releases",
-          href: "https://github.com/codellm-devkit/codeanalyzer-ts/releases",
+          href: "https://github.com/codellm-devkit/codeanalyzer-typescript/releases",
         },
         {
           icon: "discord",
@@ -79,7 +79,7 @@ export default defineConfig({
         },
       ],
       editLink: {
-        baseUrl: "https://github.com/codellm-devkit/codeanalyzer-ts/edit/docs/",
+        baseUrl: "https://github.com/codellm-devkit/codeanalyzer-typescript/edit/docs/",
       },
       sidebar: [
         {

astro.config.mjs

@@ -5,7 +5,7 @@ description: How codeanalyzer-typescript builds the level-1 call graph — the T
 
 import { Aside, LinkCard, CardGrid } from "@astrojs/starlight/components";
 
-The call graph is the answer to *"who calls whom?"* — a flat list of identity-only `TSCallEdge` objects whose `source` and `target` are signature strings. This page is the deep dive on how the **level-1** graph is built: the TypeScript checker resolves each recorded call site, Rapid Type Analysis expands virtual dispatch, and phantom nodes capture the calls that leave the project. It's the always-on base graph; [level 2](/codeanalyzer-ts/guides/level-2/) enriches it.
+The call graph is the answer to *"who calls whom?"* — a flat list of identity-only `TSCallEdge` objects whose `source` and `target` are signature strings. This page is the deep dive on how the **level-1** graph is built: the TypeScript checker resolves each recorded call site, Rapid Type Analysis expands virtual dispatch, and phantom nodes capture the calls that leave the project. It's the always-on base graph; [level 2](/codeanalyzer-typescript/guides/level-2/) enriches it.
 
 ```mermaid
 flowchart TB
@@ -88,7 +88,7 @@ The edge into it carries `provenance: ["import"]`, and the phantom is recorded i
 A specifier is external only if it isn't a relative or absolute path. Packages (`express`), scoped packages (`@scope/pkg`), and `node:` URLs become phantoms; relative imports (`./x`, `../lib/y`) are internal and left to the checker, never faked. Phantom resolution reads only imports — no type checker, no `node_modules` — so it works identically for TypeScript `import` and JavaScript `require`.
 </Aside>
 
-Disable phantom resolution entirely with [`--no-phantoms`](/codeanalyzer-ts/guides/cli-usage/#phantom-nodes) if you want a graph restricted to in-project targets.
+Disable phantom resolution entirely with [`--no-phantoms`](/codeanalyzer-typescript/guides/cli-usage/#phantom-nodes) if you want a graph restricted to in-project targets.
 
 ## Why identity-only edges
 
@@ -109,8 +109,8 @@ exact = [(u, v) for u, v, d in g.edges(data=True) if not d["rta"]]
 ## Where to go next
 
 <CardGrid>
-  <LinkCard title="Core concepts" description="How the call graph sits alongside the symbol table and external symbols." href="/codeanalyzer-ts/guides/concepts/" />
-  <LinkCard title="Output schema" description="The TSCallEdge and TSExternalSymbol models in full." href="/codeanalyzer-ts/reference/schema/#tscalledge" />
-  <LinkCard title="Level 2: CodeQL & entrypoints" description="What enrichment will add on top of this graph." href="/codeanalyzer-ts/guides/level-2/" />
-  <LinkCard title="CLI usage" description="Flags that change the graph: analysis level, phantoms." href="/codeanalyzer-ts/guides/cli-usage/" />
+  <LinkCard title="Core concepts" description="How the call graph sits alongside the symbol table and external symbols." href="/codeanalyzer-typescript/guides/concepts/" />
+  <LinkCard title="Output schema" description="The TSCallEdge and TSExternalSymbol models in full." href="/codeanalyzer-typescript/reference/schema/#tscalledge" />
+  <LinkCard title="Level 2: CodeQL & entrypoints" description="What enrichment will add on top of this graph." href="/codeanalyzer-typescript/guides/level-2/" />
+  <LinkCard title="CLI usage" description="Flags that change the graph: analysis level, phantoms." href="/codeanalyzer-typescript/guides/cli-usage/" />
 </CardGrid>

bun.lock

@@ -5,7 +5,7 @@ description: Worked examples for the codeanalyzer-typescript command — output
 
 import { Aside, LinkCard, CardGrid, Tabs, TabItem } from "@astrojs/starlight/components";
 
-The `codeanalyzer-typescript` command runs static analysis on a TypeScript/JavaScript project and emits a `TSApplication` artifact. This guide walks through the common invocations; for the full flag table see the [CLI reference](/codeanalyzer-ts/reference/cli/).
+The `codeanalyzer-typescript` command runs static analysis on a TypeScript/JavaScript project and emits a `TSApplication` artifact. This guide walks through the common invocations; for the full flag table see the [CLI reference](/codeanalyzer-typescript/reference/cli/).
 
 <Aside type="note" title="Invoking the analyzer">
 The examples below call the compiled binary `codeanalyzer-typescript`. If you haven't built it, run from source instead — `bun run start -- --input …` — everything after `--` is identical.
@@ -56,7 +56,7 @@ codeanalyzer-typescript --input ./my-ts-project --analysis-level 2
 Every run produces a symbol table **and** a call graph. At level 1, edges come from the TypeScript checker plus Rapid Type Analysis, with phantom nodes for calls into imported libraries. Level 2 is intended to merge in CodeQL-derived edges.
 
 <Aside type="caution">
-Level-2 CodeQL enrichment is **experimental** and currently a stub: it logs a warning and emits no extra edges, falling back to the level-1 graph. See [Level 2: CodeQL & entrypoints](/codeanalyzer-ts/guides/level-2/).
+Level-2 CodeQL enrichment is **experimental** and currently a stub: it logs a warning and emits no extra edges, falling back to the level-1 graph. See [Level 2: CodeQL & entrypoints](/codeanalyzer-typescript/guides/level-2/).
 </Aside>
 
 ## Build control: materializing dependencies
@@ -71,7 +71,7 @@ codeanalyzer-typescript --input ./my-ts-project --no-build
 codeanalyzer-typescript --input ./my-ts-project --eager
 ```
 
-Materialization runs the project's package manager with `--ignore-scripts` and **degrades gracefully**: if the install fails, the run still completes with partial type information. See [Installation](/codeanalyzer-ts/installing/#why-your-project-needs-its-dependencies).
+Materialization runs the project's package manager with `--ignore-scripts` and **degrades gracefully**: if the install fails, the run still completes with partial type information. See [Installation](/codeanalyzer-typescript/installing/#why-your-project-needs-its-dependencies).
 
 ## Caching: eager vs lazy
 
@@ -117,7 +117,7 @@ By default, calls into imported libraries become phantom `external_symbols` so t
 codeanalyzer-typescript --input ./my-ts-project --no-phantoms
 ```
 
-See [Call graph & dispatch](/codeanalyzer-ts/guides/call-graph/#phantom-nodes) for what phantom nodes capture.
+See [Call graph & dispatch](/codeanalyzer-typescript/guides/call-graph/#phantom-nodes) for what phantom nodes capture.
 
 ## Verbosity
 
@@ -144,8 +144,8 @@ codeanalyzer-typescript \
 ## Where to go next
 
 <CardGrid>
-  <LinkCard title="CLI reference" description="The complete flag table with defaults." href="/codeanalyzer-ts/reference/cli/" />
-  <LinkCard title="Core concepts" description="What the artifact actually contains." href="/codeanalyzer-ts/guides/concepts/" />
-  <LinkCard title="Call graph & dispatch" description="How --analysis-level and --no-phantoms change the graph." href="/codeanalyzer-ts/guides/call-graph/" />
-  <LinkCard title="Output schema" description="The TSApplication data model." href="/codeanalyzer-ts/reference/schema/" />
+  <LinkCard title="CLI reference" description="The complete flag table with defaults." href="/codeanalyzer-typescript/reference/cli/" />
+  <LinkCard title="Core concepts" description="What the artifact actually contains." href="/codeanalyzer-typescript/guides/concepts/" />
+  <LinkCard title="Call graph & dispatch" description="How --analysis-level and --no-phantoms change the graph." href="/codeanalyzer-typescript/guides/call-graph/" />
+  <LinkCard title="Output schema" description="The TSApplication data model." href="/codeanalyzer-typescript/reference/schema/" />
 </CardGrid>

src/content/docs/guides/call-graph.mdx

@@ -40,7 +40,7 @@ flowchart LR
 
 A `TSCallable` (function, method, constructor, accessor, or arrow) carries its `signature`, source `code`, `parameters`, `type_parameters`, `decorators`, `call_sites`, accessed symbols, cyclomatic complexity, and TypeScript-native flags (`is_async`, `is_static`, `is_abstract`, `accessibility`, …). A `TSClass` carries its `base_classes`, `implements_types`, `methods`, `attributes`, and decorators. The TypeScript node kinds Python and Java don't have — interfaces, enums, type aliases, namespaces — are first-class. Each node records line/column spans so you can map any element back to source.
 
-Construction is done by the **TypeScript compiler** through [ts-morph](https://ts-morph.com/): the same checker that types the project resolves references, so the analyzer materializes the project's `node_modules` first (see [Installation](/codeanalyzer-ts/installing/)).
+Construction is done by the **TypeScript compiler** through [ts-morph](https://ts-morph.com/): the same checker that types the project resolves references, so the analyzer materializes the project's `node_modules` first (see [Installation](/codeanalyzer-typescript/installing/)).
 
 <Aside type="note" title="Signatures are the identity">
 A callable's `signature` (e.g. `src/user.UserService.getUser`) is its identity across the whole artifact. Call-graph edges and entrypoints both reference callables by signature, not by a separate node object — see [below](#signatures-are-the-identity).
@@ -58,7 +58,7 @@ flowchart LR
     B -->|import| E["node:fs.readFileSync"]
 ```
 
-The TypeScript checker resolves each recorded call site to a callee declaration and backfills `callee_signature` in place; the resulting edges are guaranteed to point at real signatures (no dangling edges). Virtual dispatch is expanded with **Rapid Type Analysis**, and calls leaving the project become phantom **external symbols**. The full mechanism is its own page — [Call graph & dispatch](/codeanalyzer-ts/guides/call-graph/).
+The TypeScript checker resolves each recorded call site to a callee declaration and backfills `callee_signature` in place; the resulting edges are guaranteed to point at real signatures (no dangling edges). Virtual dispatch is expanded with **Rapid Type Analysis**, and calls leaving the project become phantom **external symbols**. The full mechanism is its own page — [Call graph & dispatch](/codeanalyzer-typescript/guides/call-graph/).
 
 Because it's a plain edge list keyed by signature, loading it into a graph is direct:
 
@@ -92,7 +92,7 @@ Only **bare** specifiers become phantoms — packages like `express`, scoped pac
 **Entrypoints** are the framework-dispatched roots of an application — the functions a framework calls that your own code never calls directly: an HTTP route handler, a message consumer, a CLI command. They're collected into `entrypoints`, keyed by framework name, with each `TSEntrypoint` referencing a callable by signature and carrying framework metadata (route path, HTTP methods, …).
 
 <Aside type="caution" title="Empty at level 1">
-At level 1, `entrypoints` is always `{}`. Framework entrypoint detection is part of the **level-2** roadmap — see [Level 2: CodeQL & entrypoints](/codeanalyzer-ts/guides/level-2/).
+At level 1, `entrypoints` is always `{}`. Framework entrypoint detection is part of the **level-2** roadmap — see [Level 2: CodeQL & entrypoints](/codeanalyzer-typescript/guides/level-2/).
 </Aside>
 
 ## Signatures are the identity
@@ -126,8 +126,8 @@ flowchart LR
 ## Where to go next
 
 <CardGrid>
-  <LinkCard title="Call graph & dispatch" description="The tsc resolver, RTA expansion, and phantom nodes in depth." href="/codeanalyzer-ts/guides/call-graph/" />
-  <LinkCard title="Output schema" description="Every field of every model in the artifact." href="/codeanalyzer-ts/reference/schema/" />
-  <LinkCard title="CLI usage" description="The flags that control what ends up in the artifact." href="/codeanalyzer-ts/guides/cli-usage/" />
-  <LinkCard title="Level 2: CodeQL & entrypoints" description="What the experimental second layer will add." href="/codeanalyzer-ts/guides/level-2/" />
+  <LinkCard title="Call graph & dispatch" description="The tsc resolver, RTA expansion, and phantom nodes in depth." href="/codeanalyzer-typescript/guides/call-graph/" />
+  <LinkCard title="Output schema" description="Every field of every model in the artifact." href="/codeanalyzer-typescript/reference/schema/" />
+  <LinkCard title="CLI usage" description="The flags that control what ends up in the artifact." href="/codeanalyzer-typescript/guides/cli-usage/" />
+  <LinkCard title="Level 2: CodeQL & entrypoints" description="What the experimental second layer will add." href="/codeanalyzer-typescript/guides/level-2/" />
 </CardGrid>

src/content/docs/guides/cli-usage.mdx

@@ -78,7 +78,7 @@ That makes `--analysis-level 2` safe to wire into a pipeline now: when enrichmen
 ## Where to go next
 
 <CardGrid>
-  <LinkCard title="Call graph & dispatch" description="The level-1 graph that level 2 enriches." href="/codeanalyzer-ts/guides/call-graph/" />
-  <LinkCard title="Output schema" description="The TSEntrypoint and TSCallEdge models." href="/codeanalyzer-ts/reference/schema/#tsentrypoint" />
-  <LinkCard title="Core concepts" description="Provenance and how merged edges record their engines." href="/codeanalyzer-ts/guides/concepts/#provenance" />
+  <LinkCard title="Call graph & dispatch" description="The level-1 graph that level 2 enriches." href="/codeanalyzer-typescript/guides/call-graph/" />
+  <LinkCard title="Output schema" description="The TSEntrypoint and TSCallEdge models." href="/codeanalyzer-typescript/reference/schema/#tsentrypoint" />
+  <LinkCard title="Core concepts" description="Provenance and how merged edges record their engines." href="/codeanalyzer-typescript/guides/concepts/#provenance" />
 </CardGrid>