@@ -345,7 +345,7 @@ Per finding: `file:line` → what → generated-equivalent exists? → recommend
 
     **(i) Physical names — every port.** A table / view / stored-proc / column / schema name spelled as a literal outside its metadata declaration: in a hand-written repository, raw SQL, a migration script, a log line, or a hand-maintained body-to-column map. The per-object names artifact (`<Entity>.names.ts` / `<entity_snake>_names.py` / `<Entity>Names`) carries these on all five ports. Every port emits a per-object names artifact (`<Entity>Names` / `<entity_snake>_names.py`) from the declaration, so a literal is a second spelling of the same fact; and because the physical column is free-form, deriving it from the field name is a guess that fails silently.
 
-    **(ii) The rest of the constants surface — TypeScript today.** The generated entity module and its browser-safe `<Entity>.meta.ts` twin carry `$entity` (the logical name), `$table`, **`$path` (the resource route path)**, `$apiPrefix`, and a per-field object keyed by field name carrying `name`, `label`, `view`, `htmlType`, the RHF-shaped `rules` derived from validator children, and a `field.enum`'s member symbols. The generated file's own docblock says to use them *instead of magic strings*. **The test is whether anything TYPE-CHECKS the literal, not whether it looks like a name.** Score a site only where nothing does: a hand-written **API resource path** (`fetch("/api/subscribers")`, `app.get("/subscribers")`), a **form label** re-typed in hand JSX, a **re-typed validation limit or message**, or a **field name passed as loose text** to something that takes a bare `string`. Where the generated artifact is a union type or a typed handle, the compiler is already the gate and the literal is CORRECT — measured: an estate's 332 bare enum-member strings (`status === "edited_approved"`) are each checked against the generated `export type <Entity><Field> = "a" | "b"` union, so renaming the member in metadata breaks the build at every site rather than drifting silently. That is the opposite of the physical-name case, and flagging it would have produced 332 findings that are all false. Enum members, typed filter objects and ORM handles are checked; paths, labels and messages are not. On the other four ports the equivalent of (ii) is the generated typed handle (a Pydantic model attribute, an EF property, an Exposed `Column`) — already the gold standard, see the do-not-flag list.
+    **(ii) The rest of the constants surface — TypeScript today.** The generated entity module and its browser-safe `<Entity>.meta.ts` twin carry `$entity` (the logical name), `$table`, and **`$path` — the ENTITY-RELATIVE resource path** (`/customers`; the base URL is a DEPLOYMENT fact supplied at runtime by the fetcher provider and is deliberately not in the descriptor, so a hand-written `fetch("/api/customers")` hardcodes both facts at once) — plus a per-field object keyed by field name carrying `name`, `label`, `view`, `htmlType`, the RHF-shaped `rules` derived from validator children, and a `field.enum`'s member symbols. The generated file's own docblock says to use them *instead of magic strings*. **The test is whether anything TYPE-CHECKS the literal, not whether it looks like a name.** Score a site only where nothing does: a hand-written **API resource path** (`fetch("/api/subscribers")`, `app.get("/subscribers")`), a **form label** re-typed in hand JSX, a **re-typed validation limit or message**, or a **field name passed as loose text** to something that takes a bare `string`. Where the generated artifact is a union type or a typed handle, the compiler is already the gate and the literal is CORRECT — measured: an estate's 332 bare enum-member strings (`status === "edited_approved"`) are each checked against the generated `export type <Entity><Field> = "a" | "b"` union, so renaming the member in metadata breaks the build at every site rather than drifting silently. That is the opposite of the physical-name case, and flagging it would have produced 332 findings that are all false. Enum members, typed filter objects and ORM handles are checked; paths, labels and messages are not. On the other four ports the equivalent of (ii) is the generated typed handle (a Pydantic model attribute, an EF property, an Exposed `Column`) — already the gold standard, see the do-not-flag list.
 
     **Score only where a constant actually exists.** A fact declared in the project's CODEGEN CONFIG rather than in metadata — a bespoke route mount path, a hand-chosen JSON envelope key — is genuinely spelled twice when a client re-types it, but no generated constant holds it. That is a GENERATOR GAP, reported as one, never a literal-site finding: never invent a constant that the emitters do not emit.
 
 
@@ -273,7 +273,7 @@ subtypes with opposite polarity: `requirement.functional` fails when NOTHING imp
 ## Cross-cutting
 
 - **Generated constants vs magic strings beyond SQL (drift signature 11, half ii).** On TypeScript
-  the entity module and its `<Entity>.meta.ts` twin emit `$entity` / `$table` / `$path` / `$apiPrefix`
+  the entity module and its `<Entity>.meta.ts` twin emit `$entity` / `$table` / `$path` (entity-relative)
   plus a per-field object (`name`, `label`, `view`, `htmlType`, `rules`, enum member symbols) whose own
   docblock says to use them INSTEAD of magic strings. Hunt hand-written route paths and fetch URLs,
   sort/filter field names passed as text, enum members compared as bare strings, re-typed labels, and
 
@@ -55,7 +55,7 @@ value-sets against the constructs that replace them.
 | camelCase↔snake_case mapping tables | generated views handle this; diff field by field |
 | `@generated` file with hand edits | three-way merge preserves them; review at codegen; never delete |
 | a table/column string in a `sql` fragment, a Kysely identifier, or a migration/seed script outside the generated dir | second spelling of a declared physical name — reference `<Entity>.names.ts` (`ProgramNames.fields.<f>.column`): `generators: [...]` is the COMPLETE list and there is no default suite, so a project scaffolded before 1.0 emits NO names artifact and the missing `namesFile()` is the finding first; a Drizzle column object in its place is correct, not a finding |
-| an API resource path typed as a string — `fetch("/api/subscribers")`, `app.get("/subscribers")`, a TanStack `queryKey` path | second spelling of the generated `$path` / `$apiPrefix` on the entity module and its `<Entity>.meta.ts` twin — signature 11 half (ii). Most-missed row in this table, because the names hunt gets scoped to SQL |
+| an API resource path typed as a string — `fetch("/api/subscribers")`, `app.get("/subscribers")`, a TanStack `queryKey` path | second spelling of the generated `$path` (entity-relative) on the entity module and its `<Entity>.meta.ts` twin — signature 11 half (ii). Most-missed row in this table, because the names hunt gets scoped to SQL |
 | **NOT a finding:** a client-side page route or link (`<Route path="/programs">`, `<a href="/programs">`) | a navigation URL the app chose, declared nowhere in metadata and free to diverge from the API path it resembles. Measured on one estate: 11 apparent hits, 0 real. Match the fetch or the mount, not the string's shape |
 | a field name passed as TEXT — `sort: "created_at"`, `filter["email"]`, a column-id string in a grid config | the per-field constants object carries `name`; a typed property access is NOT this row and must be left alone |
 | **NOT a finding:** an enum member as a bare string (`status === "archived"`) | the generated `export type <Entity><Field> = "a" \| "b"` union already checks it — renaming the member in metadata breaks the build at every site. Measured on one estate: 332 such literals, 0 real findings. Emitted `options: [...]` on `.meta.ts` is for populating a dropdown, not for replacing checked literals |