refactor(javascript): consolidate semantic graph boundaries

Retire the unused graph serialization facade and use one typed query implementation after canonical request admission. Migrate tests to the owning schemas while preserving graph commitments, Unicode transport, provenance, uncertainty, traversal and reconstruction controls.

src/domain/javascript/javascriptSemanticQuery.ts

@@ -6,7 +6,6 @@ import type {
 import type { JavaScriptSemanticGraphUnknown } from "./javascriptSemanticGraphSchemas.js";
 import { isJavaScriptSemanticOwnershipRelation as ownershipRelation } from "./javascriptSemanticQueryRelations.js";
 import {
-  javaScriptSemanticQueryInputSchema,
   javaScriptSemanticQueryResultSchema,
   type JavaScriptSemanticQueryInput,
   type JavaScriptSemanticQueryResult,
@@ -34,18 +33,8 @@ interface QueryResult {
   readonly retainedRelations: JavaScriptSemanticGraphRelation[];
 }
 
-/** Run one deterministic traversal over a verified semantic graph. */
-export const queryJavaScriptSemanticGraph = (
-  graph: JavaScriptSemanticGraph,
-  rawInput: unknown,
-): JavaScriptSemanticQueryResult =>
-  queryJavaScriptSemanticGraphValidated(
-    graph,
-    javaScriptSemanticQueryInputSchema.parse(rawInput),
-  );
-
 /** Run a query already parsed by its owning request boundary. */
-export const queryJavaScriptSemanticGraphValidated = (
+export const queryJavaScriptSemanticGraph = (
   graph: JavaScriptSemanticGraph,
   input: JavaScriptSemanticQueryInput,
 ): JavaScriptSemanticQueryResult => {