The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Apr 7, 2026 7:35pm

PR Summary

Low Risk
Low risk: changes are limited to the docs generation script and regenerated MDX output tables; no runtime/product code paths are affected beyond documentation builds.

Overview
Fixes the docs generator so tool output schemas are correctly detected even when a V2 tool inherits its config via spread (e.g., ...baseTool).

Refactors scripts/generate-docs.ts by centralizing delimiter matching into findMatchingClose and consolidating output parsing into extractOutputsFromToolContent, then regenerates several tool docs (extend, pulse, reducto, textract, vision, stt, mistral_parse) to include the previously-missing Output tables.

^{Reviewed by Cursor Bugbot for commit 785d9fe. Configure here.}

@greptile

@cursor review

Greptile Summary

This PR fixes a bug in scripts/generate-docs.ts where V2 tools inheriting properties via TypeScript spread syntax (e.g., ...extendParserTool) had empty outputs in generated docs. The root cause: extractToolInfo narrowed toolContent to start AFTER the spread line (past the id: field), so the spread was invisible to the output extractor.

The fix adds a fallback path — when no outputs are found, the script reconstructs the full enclosing export block (using a global regex to find the last export const ... = { before id:), detects *Tool/*Base spread inheritance, and fetches outputs from the base tool definition directly.

Additional refactoring:

• findMatchingClose helper extracted, replacing ~26 inline brace-counting loops throughout the file (-98 net lines)
• extractOutputsFromToolContent helper extracted, consolidating two duplicated output-extraction patterns (const-reference and inline-object)
• 7 MDX tool docs regenerated (extend, vision, stt, mistral_parse, reducto, textract, pulse) with correct output tables

One minor inconsistency: two inline brace-matching loops in parseConstFieldContent (~line 1403) and parseFieldContent (~line 1990) were not refactored to use findMatchingClose, leaving them out of step with the rest of the file."

Confidence Score: 5/5

Safe to merge — the fix is correct, well-scoped to a docs generation script with no app runtime impact, and the regenerated MDX files show the previously-missing outputs.

All findings are P2 style/consistency issues. The core V2 spread-inheritance fix is sound: the global-regex approach correctly identifies the last enclosing export declaration before the id: field, findMatchingClose is properly used with absolute file offsets, and baseToolRegex applies a word-boundary lookahead to avoid false matches. The two remaining inline brace-matching loops are a minor consistency issue but do not affect correctness.

scripts/generate-docs.ts — two inline brace-matching loops in parseConstFieldContent and parseFieldContent were not refactored to use findMatchingClose

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[getToolInfo
calls extractToolInfo] --> B[Narrow toolContent
find export block around id:]
    B --> C[extractOutputsFromToolContent
on narrowed toolContent]
    C --> D{Outputs
found?}
    D -- Yes --> G[Return outputs]
    D -- No --> E[Reconstruct fullToolBlock
find last 'export const = {'
in beforeId via global regex]
    E --> F[Search for spread:
...\w+Tool|Base\w*]
    F --> H{Spread
found?}
    H -- No --> I[Return empty]
    H -- Yes --> J[Locate base tool
export const baseVarName = {]
    J --> K[extractOutputsFromToolContent
on base tool block]
    K --> G

_{Reviews (2): Last reviewed commit: "fix(docs): remove unnecessary case-insen..." | Re-trigger Greptile}

@greptile

@cursor review