@event4u/agent-config 17.2.0 → 17.3.0

package/src/shared/zodJsonSchema.ts

@@ -0,0 +1,41 @@
+/**
+ * A Zod schema as a draft-07 JSON Schema, in the envelope the settings surface,
+ * the generated settings reference and the UI form renderer read:
+ * `{ $ref: '#/definitions/<name>', definitions: { <name>: … }, $schema }`.
+ *
+ * Zod 4 converts natively (`z.toJSONSchema`); this replaces `zod-to-json-schema`,
+ * which only understands Zod 3. `io: 'input'` keeps a defaulted field optional,
+ * as the old converter did, because a settings file may omit it.
+ */
+import * as z from 'zod';
+
+/**
+ * The places the native output differs from what consumers were built on: an
+ * object without `additionalProperties` (the old converter closed every
+ * object), an `enum` without a `type` (it named the primitive type), and an
+ * integer carrying the safe-integer bounds Zod 4 adds to `.int()`, which says
+ * nothing a reader of a settings schema can use.
+ */
+function normalise(node: unknown): void {
+    if (Array.isArray(node)) {
+        for (const n of node) normalise(n);
+        return;
+    }
+    if (typeof node !== 'object' || node === null) return;
+    const o = node as Record<string, unknown>;
+    if (o['properties'] !== undefined && o['additionalProperties'] === undefined) o['additionalProperties'] = false;
+    if (Array.isArray(o['enum']) && o['type'] === undefined) {
+        const kinds = new Set((o['enum'] as unknown[]).map((v) => typeof v));
+        if (kinds.size === 1 && (kinds.has('string') || kinds.has('number') || kinds.has('boolean'))) o['type'] = [...kinds][0];
+    }
+    if (o['maximum'] === Number.MAX_SAFE_INTEGER) delete o['maximum'];
+    if (o['minimum'] === Number.MIN_SAFE_INTEGER) delete o['minimum'];
+    for (const v of Object.values(o)) normalise(v);
+}
+
+export function toJsonSchema7(schema: z.ZodType, name: string): Record<string, unknown> {
+    const body = z.toJSONSchema(schema, { target: 'draft-7', io: 'input', unrepresentable: 'any' }) as Record<string, unknown>;
+    normalise(body);
+    const { $schema: _drop, ...definition } = body;
+    return { $ref: `#/definitions/${name}`, definitions: { [name]: definition }, $schema: 'http://json-schema.org/draft-07/schema#' };
+}

package/src/vendor/grammars/README.md

@@ -10,9 +10,9 @@ with no manual parser install (ADR-259).
 
 `tree-sitter-wasms` carries 36 grammars (49 MiB on disk). Depending on it at
 runtime would hand every consumer all 36, which is the option ADR-259 §
-Alternatives rejects on exactly that measurement. Only the six grammars below
+Alternatives rejects on exactly that measurement. Only the seven grammars below
 are loadable by the engine — `GRAMMAR_WASM` in `src/scripts/code_graph/types.ts`
-has six entries — so the other 30 would be payload with no reader. Vue needs no
+has seven entries — so the other 29 would be payload with no reader. Vue needs no
 grammar of its own: the extractor blanks a component's template and parses its
 `<script>` with the TypeScript grammar.
 
@@ -29,8 +29,9 @@ the tarball; the loader reads them from disk.
 | python | `tree-sitter-python.wasm` | `9056d0fb0c337810d019fae350e8167786119da98f0f282aceae7ab89ee8253b` |
 | go | `tree-sitter-go.wasm` | `9963ca89b616eaf04b08a43bc1fb0f07b85395bec313330851f1f1ead2f755b6` |
 | java | `tree-sitter-java.wasm` | `637aac4415fb39a211a4f4292d63c66b5ce9c32fa2cd35464af4f681d91b9a1f` |
+| csharp | `tree-sitter-c_sharp.wasm` | `6266a7e32d68a3459104d994dc848df15d5672b0ea8e86d327274b694f8e6991` |
 
-All six are built against **grammar ABI 14** (`EXPECTED_GRAMMAR_ABI` in
+All seven are built against **grammar ABI 14** (`EXPECTED_GRAMMAR_ABI` in
 `src/scripts/code_graph/types.ts`). The loader asserts the ABI on every load, so
 a drifted grammar fails loudly rather than parsing wrongly.
 
@@ -73,7 +74,7 @@ The pair is ABI-coupled and must move together:
 
 ```bash
 npm i -D web-tree-sitter@<v> tree-sitter-wasms@<v>
-for g in php typescript javascript python go java; do
+for g in php typescript javascript python go java c_sharp; do
   cp node_modules/tree-sitter-wasms/out/tree-sitter-$g.wasm src/vendor/grammars/
 done
 shasum -a 256 src/vendor/grammars/*.wasm   # update the table above
@@ -81,7 +82,7 @@ shasum -a 256 src/vendor/grammars/*.wasm   # update the table above
 
 Then update, in the same change:
 
-- the six entries in `src/config/packed-binary-manifest.json` (they are
+- the seven entries in `src/config/packed-binary-manifest.json` (they are
   path-, sha256- and size-bound, so any refresh invalidates them by design).
   This used to name `BINARY_PAYLOAD_EXCEPTIONS` in `src/scripts/check_pack_size.ts`,
   a constant that no longer exists — `grep -rn BINARY_PAYLOAD_EXCEPTIONS` returned