Generated word-boundary regex contains backspace characters, so referencedTypes is always empty

[j2bap]

Summary

The catalog generator emits a broken regex into the generated API catalogs. The regex must match type names on word boundaries. Instead, it matches backspace control characters. Because of this, referencedTypeClosure never matches a type, and queryServiceApi / queryEventApi always return an empty referencedTypes list.

Location

• Origin (the line to fix): packages/typert/generator/src/cordis-catalog.ts:829
• Generated copies that carry the defect:
  • packages/extensions/tool-cordis/src/api-catalog.ts:4671
  • packages/extensions/cordis-client-runner/src/client/api-catalog.ts:891

Details

The emitter writes the line from a single-quoted string:

'      const pattern = new RegExp(`\\b${entry.name}\\b`)',

In a single-quoted string, \\b produces the two characters \b. The generated file then contains:

const pattern = new RegExp(`\b${entry.name}\b`)

In a template literal, \b is the backspace character (U+0008), not the two characters backslash + b. The regex source becomes <BS>TypeName<BS>. Signature text never contains backspace characters, so the regex never matches.

Repro in Node:

const text = 'run(call: ToolCall): Promise<ToolExecutionResult>'
new RegExp(`\b${'ToolExecutionResult'}\b`).test(text)  // false (generated form)
new RegExp('\\bToolExecutionResult\\b').test(text)     // true  (intended form)

Effect

The cordis_inspect tool documents that its detail view includes the referenced type closure. Because the regex never matches, the tool always returns referencedTypes: []. The model gets the signatures but never the type declarations.

Evidence of intent

The hand-written analog in the same package is correct. packages/extensions/tool-cordis/src/inspect.ts:223 uses a real template literal with \\b, which yields a word-boundary regex. Only the string-emitted copy lost one level of escaping. No test asserts the contents of referencedTypes, which is why this slipped through.

Suggested fix

Add one more level of escaping in the emitter string (\\\\b), then regenerate both catalog files. A test that asserts a non-empty referencedTypes for a known service would prevent a regression.

[IoveCelestina]

Thanks @9710willy for the precise report and root-cause analysis. I prepared a minimal, cherry-pick-ready fix against upstream master at 47f943859bef60e4160492346772ded9b24f765a.

Patch

• Branch: https://github.com/IoveCelestina/deepseek-harness/tree/fix/cordis-catalog-word-boundary
• Atomic commit: IoveCelestina@67be850
• Compare: master...IoveCelestina:deepseek-harness:fix/cordis-catalog-word-boundary
• Cherry-pick: git cherry-pick 67be850387532396a754b1539ae1d960bdd98069

What changed

• Escaped the word-boundary backslashes through the source emitter, so the generated TypeScript retains \\b and RegExp receives real word boundaries at runtime.
• Regenerated both runtime API catalogs.
• Added a regression test covering referenced type closures for both a service (tools) and an event (tools/execute).

The patch changes 4 files only: the generator, its regression test, and the two generated catalogs. It does not change signatures or catalog shape; it restores the documented referencedTypes behavior.

Verification

• Before the fix, pnpm exec vitest run packages/typert/generator/tests/tools-catalog.spec.ts -t "returns referenced type declarations" failed with empty referencedTypes arrays.
• After the fix, the focused test passed.
• Full owning test file: 2/2 passed.
• pnpm run verify-cordis-api: all 93 generated files/regions up to date.
• Repository doc-sync gate: 28/28 passed.
• Repository pre-push typecheck passed.
• git diff --check passed.

The patch is offered under the repository's MIT license. If the maintainers prefer to reimplement or squash it internally, please reference this Discussion/commit when practical so the report and contribution remain traceable.