fix(ci): require a default export before treating a file as a route entry

[waleedlatif1]

Follow-up to #7026. Both points were raised in review there and I merged before reading them, so they land here.

The filename was never the right test

#7026 added error.tsx to the entry filenames, and with it picked up [workspaceId]/components/error/error.tsx — named like a boundary, and not one:

export interface ErrorBoundaryProps { … }
export function ErrorShell(…) { … }
export function ErrorState(…) { … }

Named exports only. It is the shared helper the thirteen real boundaries render, and Next would reject it as a boundary for having no default export.

Counting it inflated the coverage number and — the part that would have bitten — recorded a shared component in the graph-weight baseline as though it were a route.

Every convention-composed entry must default-export the thing Next renders, so that is the discriminator now.

Entry count 60 → 59. All thirteen real error.tsx boundaries still walk; only the helper drops out.

Completing the enumeration

Also adds template.tsx and default.tsx. Neither exists under app/workspace today, so this changes nothing right now — but the list claims to cover what Next composes, and leaving two out makes that claim false the day someone adds one. That is the same failure the surrounding TSDoc already warns about: "A hardcoded list goes stale silently."

Verification

✓ tool registry stays out of 59 workspace page/layout graphs
error.tsx entries walked: 13
components/error/error.tsx: not present

Credit

The non-route entry was Cursor's; the missing template.tsx/default.tsx was Greptile's. Both were correct.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 24, 2026 3:06am

[cursor]

PR Summary

Low Risk
CI-only change to how route entries are enumerated; no runtime, auth, or data-path impact. The regex could miss unusual default-export forms, which would under-count entries rather than ship bad code.

Overview
Tightens how check-tool-registry-boundary.ts discovers Next.js workspace entries so a filename match is no longer enough.

collectEntries now also requires a default export (export default or export { … as default}). That drops the shared [workspaceId]/components/error/error.tsx helper (named like a boundary, no default) from the walk and graph-weight baseline, while the real error.tsx boundaries stay. Entry count goes 60 → 59.

Also enumerates template.tsx and default.tsx so the convention list matches what Next composes. Neither exists under app/workspace today.

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

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[greptile-apps]

Greptile Summary

This follow-up tightens workspace route discovery by requiring a default export and completes the convention-entry filename set.

• Recognizes direct default exports and default re-export forms, including the previously missed export { default } from syntax.
• Excludes named-export-only helpers from route graph checks.
• Adds template.tsx and default.tsx to the discovered entry filenames.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains; the previously reported omission of export { default } from is fixed at the current head.

Important Files Changed

Filename	Overview
scripts/check-tool-registry-boundary.ts	Route-entry discovery now requires a recognized default export, covers the previously missed default re-export form, and enumerates two additional Next.js entry filenames.

_{Reviews (2): Last reviewed commit: "fix(ci): count every form that declares ..." | Re-trigger Greptile}

[waleedlatif1]

@greptile-apps the score is a commit behind — last reviewed c01be22d1e, head is 376e373ec2. The missed export { default } from form behind the 4/5 is fixed there. Please re-review.