@gate-forge/pack-http 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 UKD
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,224 @@
+# @gate-forge/pack-http — Generic HTTP exposure pack
+
+Pure-TypeScript in-process detector that finds **externally reachable HTTP
+artifacts** in `.ts`/`.tsx`/`.js`/`.jsx`/`.mjs`/`.cjs` source — no execution,
+no network, no external deps — and emits `http.contract` **evidence facts**
+(ADR 0004 D1) for the engine's endpoint-compiler join. It mints **no
+classification signals** (dogfood remediation phase 4):
+
+- **Server routes**: Express `app.get('/accounts', …)` / `router.post(…)`,
+  Fastify and Hono registrations (import-disambiguated, the pack-auth
+  convention), and NestJS `@Controller('accounts')` + `@Get/@Post/@Put/
+  @Patch/@Delete/@All('…')` decorators.
+- **Frontend API-client calls** (bounded static dataflow, plan phase 3):
+  direct literal `fetch`/Axios, `fetch(url, { method })`, Axios config
+  objects and instances, configured client symbols (`apiClient.get`),
+  pure URL builders (`buildApiPath` with a declared base), module
+  constants (local and imported within the scanned set), template
+  literals with positional `${}` slots, and simple single-return wrapper
+  functions. Computed methods, arbitrary concatenation,
+  environment-dependent hosts, undeclared wrappers, and wrapper flows
+  outside the model emit **typed unresolved entries** — they never
+  disappear and never default to GET. A modeled Axios instance creation
+  with a proven literal `baseURL` joins that base into the emitted call
+  path (see *Instance baseURL joining* below).
+
+## Client-scan configuration
+
+Configuration declares resolvable APIs, never coverage exemptions
+(`.gateforge/http-clients.json`, or pass `clientScan` to the factory):
+
+```json
+{
+  "clientScanRoots": ["frontend/**"],
+  "serverScanRoots": ["src/**", "services/**"],
+  "clientSymbols": [
+    "apiClient",
+    { "name": "api", "include": ["frontend/src/**"], "exclude": ["frontend/src/generated/**"] }
+  ],
+  "wrapperFunctions": [{ "name": "apiGet", "method": "GET", "include": ["frontend/**"] }],
+  "urlBuilders": [{ "name": "buildApiPath", "base": "/api" }],
+  "sameOriginHosts": ["app.example.com"]
+}
+```
+
+A module-scope function whose body issues client calls IS a client
+wrapper: calling it without declaring it blocks with
+`FRONTEND_CALL_TARGET_UNRESOLVED` — removing wrapper support can never
+make a call silently disappear (red probe).
+
+### Instance baseURL joining (source-proven, fail-closed)
+
+Frontends commonly create one Axios client with a base path and then
+write every call base-relative — `axios.create({ baseURL: '/api' })`
+plus `apiClient.get('/v1/x')` hits `/api/v1/x` at runtime. Without
+joining, those calls compare against backend routes as `/v1/x` and go
+unwired for the prefix alone. When an instance symbol's creation is
+modeled, its **proven literal `baseURL` joins into the emitted call
+path**: `normalizedPath = normalize(baseURL + callPath)`. This is
+source-proven, not configured — no new configuration key exists.
+
+**Extraction.** The modeled creation shape is a module-scope
+`const x = axios.create({...})`. The base is read from the config
+argument in property order, last writer wins (JavaScript object
+semantics): a direct `baseURL` property, and spreads of a **declared
+constant config object** the creation is assigned from or spreads
+(`axios.create(config)`, `axios.create({ ...defaults })`), resolved
+through the same bounded value table as path constants — local
+module-scope constants and relative imports, cycle-guarded. A
+non-literal base (env variable, computed, unmodeled factory) is simply
+unproven.
+
+**Where the creation is found (precedence).**
+
+1. The symbol's module-scope creation in the callsite file itself.
+2. The creation in the relative-import module providing the binding
+   (the existing bounded import machinery, nothing looser).
+3. Otherwise a **unique declaration of the symbol across the scanned
+   product set** — the configured-symbol channel already treats the
+   name as global, and real API clients are singletons, so an
+   alias-imported creation (`from '@/lib/apiClient'`) resolves here.
+   Fail-closed: every same-named creation must be a modeled
+   `axios.create` and all proven bases must agree; disagreement, a
+   second distinct base, or any unprovable same-named creation vetoes
+   the join. The search stays inside `clientScanRoots` (an out-of-scope
+   e2e mock instance cannot poison product calls) and never applies to
+   the bare `axios` global, whose base is axiomatically absent unless
+   shadowed in the callsite file itself.
+
+**Join semantics.** Exactly one slash seam, axios `combineURLs` style:
+trailing base slashes and leading call-path slashes collapse
+(`/api/` + `/v1/x` → `/api/v1/x`). Empty and `/` bases join nothing;
+an absolute call URL (`https://…`, protocol-relative `//`) ignores the
+base and keeps the existing absolute-URL / `sameOriginHosts` rules; a
+literal absolute base joins and canonicalizes to its path portion for
+configured same-origin hosts. A base template with a resolvable hole
+(`/api/${version}`) joins positionally; an unresolvable hole keeps
+the base unproven.
+
+**What changes and what never does.** Only the fact's `normalizedPath`
+gains the prefix — `rawPath` stays exactly as written, and
+normalization itself (query/fragment stripping, `${}`/`{}` slotting,
+slash collapsing) is unchanged. A joined path then meets the
+endpoint-compiler join's literal-precedence rules like any other path
+(that engine is owned by `@gate-forge/http-contract`). Callsites that
+join nothing behave byte-identically to before, and joining never
+turns a passing callsite into a blocker. Wrapper functions do not join
+their internal client's base (documented boundary — declare the
+wrapper's paths fully, or use a builder with `base`). The
+`urlBuilders[].base` channel is unchanged: it is configuration-declared,
+so the builder's base is part of the resolved value itself.
+
+### Scan scoping (optional, strict, back-compatible)
+
+All scoping keys are OPTIONAL; a config without them scans exactly as
+before (byte-identical). They exist because test-harness code is a
+different contract class: e2e helpers that share a configured symbol's
+name were scanned as product frontend consumption (typed blockers plus
+phantom consumption), and test-harness mock servers matched the generic
+server-route regex, producing false `http.endpoint` resources.
+
+- `clientScanRoots` — repo-root-relative globs. Client-call scanning
+  (`fetch`/Axios, configured symbols, wrappers, builders) applies ONLY
+  to matching files; files outside produce **no client-call facts and no
+  unresolved entries** (they still participate in import resolution, so
+  product code importing constants from outside the roots keeps
+  resolving).
+- `serverScanRoots` — repo-root-relative globs. Generic server-route
+  scanning (Express/Fastify/Hono registrations and NestJS controllers)
+  applies ONLY to matching files; files outside produce no server-route
+  facts. Reported `scannedPaths` coverage is unchanged either way —
+  scoping narrows facts, not coverage.
+
+Per-symbol scoping (`include`/`exclude` on a `clientSymbols`,
+`wrapperFunctions`, or `urlBuilders` entry; plain-string entries remain
+unscoped) composes with — never relaxes — the top-level roots. The
+precedence is deterministic:
+
+1. **Top-level roots gate first**: a file outside `clientScanRoots`
+   yields no client-call facts at all, regardless of any symbol's
+   scoping; the same holds for `serverScanRoots` and server routes.
+2. **`include` next**: if an entry declares `include`, the file must
+   match at least one glob (absent `include` = every in-root file).
+3. **`exclude` wins over `include`**: a file named by both is out of
+   scope for that entry.
+
+Consequences, kept deliberate and documented:
+
+- A call to a name the configuration declares, in a file outside that
+  name's declared scope (the e2e `api(...)` helper), is **ignored** —
+  neither resolved nor blocked. The undeclared-wrapper evidence rule
+  still blocks any name the configuration never mentions.
+- A configured builder or wrapper scoped away from a file simply stops
+  resolving there. If the enclosing call is still in scope (e.g. a bare
+  `fetch` whose target used the builder), the call fails closed with a
+  typed unresolved entry — it never silently vanishes.
+- Server-route disambiguation is scope-aware: where a client symbol is
+  NOT active for a file, `api.get('/x', handler)`-shaped code is free to
+  be discovered as a router registration.
+
+Malformed documents still fail closed: non-object roots, non-verb
+wrapper methods, scoping entries without a `name`, and non-array
+`include`/`exclude` values throw. Unknown keys and non-array known keys
+are ignored, exactly as before (unchanged parser posture).
+
+## Resources
+
+**None.** Routes are evidence, not business resources: an early design
+emitted one `http-route` resource per artifact, but a path-derived resource
+name collides with the converged SQLAlchemy table at the same
+plane-qualified id, so the resource channel was removed after a red-probe
+(`resources: []` always; see ADR 0004 D1 for the successor design —
+endpoint identities live in the `@gate-forge/http-contract` join, never in
+the path-derived table name).
+
+## Signals
+
+**None.** An earlier design minted a code-positive `exposure` signal per
+artifact (assertion `route`/`frontend-call`) plus `lifecycle.<op>` signals
+from the HTTP method (POST⇒create, GET/HEAD⇒read, PUT/PATCH⇒update,
+DELETE⇒delete; `app.all` asserted nothing), each targeted at the
+**path-derived resource name** — the last non-empty, non-parameter path
+segment, lower-cased, extension stripped (`/api/accounts/:id` →
+`accounts`). That target is a GUESS: in real repos it mostly names no
+discovered resource (route `/absences` vs table `employee_absences`), and
+every minted signal surfaced as a `STALE_SIGNAL_TARGET` blocker while
+adding no information — unknown exposure already defaults `user-facing`
+and unknown lifecycle operations already default enabled (ADR 0003 D5),
+so removing the guesses changes no classification outcome.
+
+Consequences, kept deliberate:
+
+- **Route→resource linkage is the CLI endpoint compiler's exclusive job**
+  (ADR 0004): it derives the same candidate name, links only when exactly
+  one discovered business resource matches AND a schema-symbol or
+  handler-name fact corroborates it (evidence this pack puts on the
+  `http.contract` facts), and emits typed
+  `ENDPOINT_RESOURCE_LINK_UNRESOLVED` blocks for ambiguity. Name
+  coincidence alone never links.
+- Removing signals conserves the defaults: exposure stays `user-facing`,
+  every lifecycle operation stays enabled (crud:/persistence: obligation
+  generation via `lifecycleAllowsContract` is unchanged), and delete
+  semantics remain blocked until the model pack proves them.
+- Core's `STALE_SIGNAL_TARGET` detection remains for genuinely stale
+  authority signals (declaration markers, adapter bindings, read-only
+  declarations) — this pack simply no longer produces false targets.
+- The pack emits **no negative proof anywhere** (no regex-only negative
+  proof, no "not found means internal") and never writes classifications.
+
+## Setup
+
+```yaml
+# .gateforge.yml
+plugins:
+  - id: gateforge.pack-http
+    version: 0.1.0
+    transport: in-process
+    module: '@gate-forge/pack-http'
+```
+
+The pack also emits `http.contract` evidence facts (one per server
+artifact and one per frontend callsite) for the endpoint compiler's join
+(ADR 0004 D1) — evidence-only, never business resources.
+
+Requires Node >= 20; no network at any point.

package/dist/client-calls.d.ts

@@ -0,0 +1,212 @@
+/**
+ * Bounded static dataflow for frontend API-client calls (ADR 0004 D6,
+ * plan phase 3).
+ *
+ * Real ASTs (the TypeScript compiler API, pure analysis — no evaluation,
+ * no I/O beyond the caller-provided file set) replace the old regex
+ * client scan. The model is deliberately bounded:
+ *
+ * - **Direct literal calls**: `fetch('/x')`, `axios.get('/x')`, instance
+ *   verbs, `axios({url, method})` — method from verb name or a literal /
+ *   const `method` property; never a silent GET default for computed
+ *   methods (those become `HTTP_METHOD_DYNAMIC`).
+ * - **Module constants**: `const X = '/x'` / template / builder call,
+ *   resolved across the scanned file set through relative imports with a
+ *   cycle guard and memoization.
+ * - **Templates**: `${expr}` holes resolve through the same value table;
+ *   rooted holes become positional `{}` slots without needing runtime
+ *   values; an unresolvable hole before the path is rooted (host/base)
+ *   makes the whole target `FRONTEND_CALL_TARGET_UNRESOLVED`.
+ * - **Configured client symbols** (`apiClient.get(...)`) and **pure URL
+ *   builders** (`buildApiPath('/v1/x')` with an optional declared base)
+ *   are configuration-declared resolvable APIs — never coverage
+ *   exemptions: unresolved flows still block.
+ * - **Instance baseURL joining**: when an instance symbol's creation is
+ *   modeled — a module-scope `const apiClient = axios.create({...})`
+ *   whose config carries a proven LITERAL `baseURL` (a direct property,
+ *   or one reaching it through a declared constant config object the
+ *   creation is assigned from or spreads, resolved by the same bounded
+ *   value table) — the base joins into the emitted call path:
+ *   `normalizedPath = normalize(baseURL + callPath)` with exactly one
+ *   slash seam. Empty/`/` bases, absolute call URLs, and unprovable
+ *   (env-dependent) bases join nothing: the callsite behaves exactly as
+ *   it would without the feature, and joining never turns a passing
+ *   callsite into a blocker. The raw path stays exactly as written.
+ * - **Simple wrapper functions**: a configured wrapper whose declaration
+ *   in the scanned set is a single `return <client call>(...)` arrow or
+ *   function resolves its internal call with the callsite's first
+ *   argument substituted for the wrapper's first parameter (one level,
+ *   one parameter — anything deeper is typed unresolved).
+ */
+import { FRONTEND_CALL_TARGET_UNRESOLVED, HTTP_METHOD_DYNAMIC, HTTP_PATH_DYNAMIC } from '@gate-forge/http-contract';
+import type { HttpMethod } from '@gate-forge/http-contract';
+import { type Location } from '@gate-forge/core';
+/**
+ * Optional per-entry file scoping (phase 3 scan-scoping). Globs are
+ * repo-root-relative posix (`frontend/src/**`), matched with core's
+ * deterministic `pathInScope` machinery — the same wildcards as the
+ * classification policy's scan roots.
+ */
+export interface ClientSymbolScoping {
+    /**
+     * Files the entry applies to. Absent = every scanned file (the
+     * back-compat default); present = at least one glob must match.
+     */
+    include?: readonly string[];
+    /**
+     * Files the entry never applies to. Any match wins over `include` —
+     * a deterministic precedence (documented in the README).
+     */
+    exclude?: readonly string[];
+}
+/** A configured client symbol: plain string (unscoped) or scoped object. */
+export interface ClientSymbolConfig extends ClientSymbolScoping {
+    /** Instance symbol exposing verb methods, e.g. `apiClient`. */
+    name: string;
+}
+/** A configured wrapper callable: `name` + concrete method + scoping. */
+export interface WrapperFunctionConfig extends ClientSymbolScoping {
+    name: string;
+    /**
+     * The concrete method the wrapper always issues (wrappers with
+     * computed methods stay unresolved).
+     */
+    method: HttpMethod;
+}
+/** A configured pure URL builder: `name` + optional base + scoping. */
+export interface UrlBuilderConfig extends ClientSymbolScoping {
+    name: string;
+    /** Optional literal base the builder prepends. */
+    base?: string;
+}
+/**
+ * Configuration for the client-call scanner (all optional).
+ *
+ * Scan scoping (phase 3): `clientScanRoots` / `serverScanRoots` narrow
+ * WHERE client-call and generic server-route scanning apply at all —
+ * two real dogfood failures drove this. A consumer's e2e specs defined
+ * a helper also named `api`, and every harness call was scanned as
+ * product frontend consumption (20 FRONTEND_CALL_TARGET_UNRESOLVED
+ * blockers + phantom consumption); another repo discovered false
+ * `http.endpoint` server routes inside `tests/e2e` because test-harness
+ * mock servers matched the generic route regex. Test-harness calls are
+ * a different contract class, so a file outside the roots produces NO
+ * facts of that kind at all. Absent keys scan everything — the
+ * byte-identical back-compat contract.
+ */
+export interface ClientScanConfig {
+    /** Instance symbols exposing verb methods, e.g. `['apiClient']`. */
+    clientSymbols?: ReadonlyArray<string | ClientSymbolConfig>;
+    /**
+     * Wrapper callables: `name` plus the concrete method the wrapper
+     * always issues (wrappers with computed methods stay unresolved).
+     */
+    wrapperFunctions?: ReadonlyArray<WrapperFunctionConfig>;
+    /** Pure URL builders with an optional literal base they prepend. */
+    urlBuilders?: ReadonlyArray<UrlBuilderConfig>;
+    /** Absolute-URL hosts treated as same-origin (canonicalized to path). */
+    sameOriginHosts?: readonly string[];
+    /**
+     * Repo-root-relative globs limiting client-call scanning (fetch,
+     * axios, configured symbols, wrappers, builders). Files outside
+     * produce NO client-call facts and NO unresolved entries.
+     */
+    clientScanRoots?: readonly string[];
+    /**
+     * Repo-root-relative globs limiting generic server-route scanning
+     * (`scanServerRoutes` / `scanNestControllers`). Files outside produce
+     * NO server-route facts — test servers are not product routes.
+     */
+    serverScanRoots?: readonly string[];
+}
+export declare const DEFAULT_CLIENT_SCAN_CONFIG: ClientScanConfig;
+/**
+ * Whether `file` (repo-root-relative posix) is inside the top-level
+ * client-call scan roots. Absent roots admit EVERY file — the
+ * back-compat contract: without the key, scanning is exactly as before.
+ */
+export declare function fileInClientScanRoots(config: ClientScanConfig, file: string): boolean;
+/**
+ * Whether `file` is inside the top-level server-route scan roots.
+ * Absent roots admit every file (back-compat, same rule as above).
+ */
+export declare function fileInServerScanRoots(config: ClientScanConfig, file: string): boolean;
+/**
+ * Whether a callsite in `file` uses the configured client symbol
+ * `name`: the file must match the top-level clientScanRoots (if
+ * present) AND the symbol's own include/exclude (if present). Both
+ * gates must pass — per-symbol scoping composes with (never relaxes)
+ * the top-level roots.
+ */
+export declare function clientSymbolActiveIn(config: ClientScanConfig, name: string, file: string): boolean;
+/**
+ * The configured client-symbol names ACTIVE for `file` — used by the
+ * server-route scanner to disambiguate `api.get('/x')`-shaped client
+ * calls from router registrations. Scope-aware: a symbol scoped away
+ * from this file does not suppress route discovery in it (out of client
+ * scope, `<symbol>.<verb>(path, handler)` can only be a router).
+ */
+export declare function activeClientSymbolNamesIn(config: ClientScanConfig, file: string): string[];
+/** One discovered frontend call (one row per source callsite). */
+export interface ClientCall {
+    method: HttpMethod;
+    /** Path exactly as written after constant substitution. */
+    rawPath: string;
+    /** Canonical positional form of {@link rawPath} (ADR 0004 D2). */
+    canonicalPath: string;
+    /**
+     * The proven literal instance `baseURL` that was joined into
+     * {@link canonicalPath} (`normalize(baseURL + rawPath)`), present ONLY
+     * when a join actually happened. Fact emission canonicalizes the joined
+     * path while {@link rawPath} stays as written; without a joined base
+     * this is absent and emission is byte-identical to the pre-feature
+     * contract.
+     */
+    joinedBaseURL?: string;
+    /** Producing client, e.g. `fetch`, `axios`, `apiClient`, `apiGet`. */
+    framework: string;
+    location: Location;
+}
+export interface ClientScanUnresolved {
+    code: typeof FRONTEND_CALL_TARGET_UNRESOLVED | typeof HTTP_METHOD_DYNAMIC | typeof HTTP_PATH_DYNAMIC;
+    detail: string;
+    location: Location;
+}
+export interface ClientScanResult {
+    calls: ClientCall[];
+    unresolved: ClientScanUnresolved[];
+}
+/**
+ * Scans one file for frontend API-client calls under the bounded model.
+ * `scannedFiles` maps repo-relative paths to source text for every file
+ * in the discovery request (import resolution stays inside the set).
+ *
+ * Scan scoping (phase 3): a file outside `clientScanRoots` (when the
+ * key is present) returns EMPTY — no calls AND no unresolved entries.
+ * The gate comes first on purpose: even bare `fetch` extraction must
+ * not run, because a scoped-out file (an e2e spec, a test harness) is
+ * not product frontend consumption and must be invisible to this
+ * channel, blockers included. Files outside the roots still participate
+ * in the value table as import targets — scoping narrows fact
+ * emission, not the dataflow's ability to resolve product code.
+ */
+export declare function scanClientCalls(file: string, sourceText: string, config: ClientScanConfig, scannedFiles: ReadonlyMap<string, string>): ClientScanResult;
+/**
+ * Reads a client-scan config document. Returns the default config when
+ * the file is absent; malformed documents throw (fail closed — the CLI
+ * surfaces the error instead of scanning with partial trust).
+ *
+ * Accepted shapes (phase 3 scan-scoping): `clientSymbols` entries are a
+ * plain string (back-compat, unscoped) or `{ name, include?, exclude? }`;
+ * `wrapperFunctions` / `urlBuilders` entries carry the same optional
+ * include/exclude next to their existing `method` / `base` fields; the
+ * top-level `clientScanRoots` / `serverScanRoots` arrays scope where
+ * client-call and server-route scanning apply at all. Consistent with
+ * the pre-existing parser posture: unknown keys are ignored, non-array
+ * known keys are ignored, but malformed ENTRY values throw (the wrapper
+ * verb check predates this; the new scoping fields throw on wrong
+ * shapes and missing names because silently dropping a scope widens the
+ * scan instead of narrowing it).
+ */
+export declare function readClientScanConfigOrNull(path: string | null): ClientScanConfig;
+//# sourceMappingURL=client-calls.d.ts.map

package/dist/client-calls.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"client-calls.d.ts","sourceRoot":"","sources":["../src/client-calls.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AAKH,OAAO,EACL,+BAA+B,EAC/B,mBAAmB,EACnB,iBAAiB,EAElB,MAAM,2BAA2B,CAAC;AACnC,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,2BAA2B,CAAC;AAC5D,OAAO,EAAe,KAAK,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAE9D;;;;;GAKG;AACH,MAAM,WAAW,mBAAmB;IAClC;;;OAGG;IACH,OAAO,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAC5B;;;OAGG;IACH,OAAO,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;CAC7B;AAED,4EAA4E;AAC5E,MAAM,WAAW,kBAAmB,SAAQ,mBAAmB;IAC7D,+DAA+D;IAC/D,IAAI,EAAE,MAAM,CAAC;CACd;AAED,yEAAyE;AACzE,MAAM,WAAW,qBAAsB,SAAQ,mBAAmB;IAChE,IAAI,EAAE,MAAM,CAAC;IACb;;;OAGG;IACH,MAAM,EAAE,UAAU,CAAC;CACpB;AAED,uEAAuE;AACvE,MAAM,WAAW,gBAAiB,SAAQ,mBAAmB;IAC3D,IAAI,EAAE,MAAM,CAAC;IACb,kDAAkD;IAClD,IAAI,CAAC,EAAE,MAAM,CAAC;CACf;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,WAAW,gBAAgB;IAC/B,oEAAoE;IACpE,aAAa,CAAC,EAAE,aAAa,CAAC,MAAM,GAAG,kBAAkB,CAAC,CAAC;IAC3D;;;OAGG;IACH,gBAAgB,CAAC,EAAE,aAAa,CAAC,qBAAqB,CAAC,CAAC;IACxD,oEAAoE;IACpE,WAAW,CAAC,EAAE,aAAa,CAAC,gBAAgB,CAAC,CAAC;IAC9C,yEAAyE;IACzE,eAAe,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IACpC;;;;OAIG;IACH,eAAe,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IACpC;;;;OAIG;IACH,eAAe,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;CACrC;AAED,eAAO,MAAM,0BAA0B,EAAE,gBAAqB,CAAC;AAE/D;;;;GAIG;AACH,wBAAgB,qBAAqB,CAAC,MAAM,EAAE,gBAAgB,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAErF;AAED;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,MAAM,EAAE,gBAAgB,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAErF;AAoBD;;;;;;GAMG;AACH,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,gBAAgB,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAGlG;AAsCD;;;;;;GAMG;AACH,wBAAgB,yBAAyB,CAAC,MAAM,EAAE,gBAAgB,EAAE,IAAI,EAAE,MAAM,GAAG,MAAM,EAAE,CAO1F;AAED,kEAAkE;AAClE,MAAM,WAAW,UAAU;IACzB,MAAM,EAAE,UAAU,CAAC;IACnB,2DAA2D;IAC3D,OAAO,EAAE,MAAM,CAAC;IAChB,kEAAkE;IAClE,aAAa,EAAE,MAAM,CAAC;IACtB;;;;;;;OAOG;IACH,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,sEAAsE;IACtE,SAAS,EAAE,MAAM,CAAC;IAClB,QAAQ,EAAE,QAAQ,CAAC;CACpB;AAED,MAAM,WAAW,oBAAoB;IACnC,IAAI,EAAE,OAAO,+BAA+B,GAAG,OAAO,mBAAmB,GAAG,OAAO,iBAAiB,CAAC;IACrG,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,QAAQ,CAAC;CACpB;AAED,MAAM,WAAW,gBAAgB;IAC/B,KAAK,EAAE,UAAU,EAAE,CAAC;IACpB,UAAU,EAAE,oBAAoB,EAAE,CAAC;CACpC;AAwLD;;;;;;;;;;;;;GAaG;AACH,wBAAgB,eAAe,CAC7B,IAAI,EAAE,MAAM,EACZ,UAAU,EAAE,MAAM,EAClB,MAAM,EAAE,gBAAgB,EACxB,YAAY,EAAE,WAAW,CAAC,MAAM,EAAE,MAAM,CAAC,GACxC,gBAAgB,CA6BlB;AA6uBD;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,0BAA0B,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,GAAG,gBAAgB,CA8DhF"}