fix(ci): count every form that declares a default export

`export { default } from './page'` is a valid Next entry and the regex required
`as default`, so such an entry would have dropped out of the walk and skipped
both the registry gate and the graph-weight ratchet — silently, which is the
dangerous direction for a discriminator to fail in.

Latent rather than live: the form appears once under `app/workspace`, in a
barrel, not in an entry filename.

Four forms now count — `export default …`, `export { default } from`,
`export { default, … } from`, and `export { X as default }`.
`export { default as X }` still does not: it re-exports another module's default
under a name and leaves this one without one. Verified all ten variants,
including that last distinction.

Raised by both Cursor and Greptile on #7028.

Author: waleedlatif1

scripts/check-tool-registry-boundary.ts

@@ -86,9 +86,16 @@ const ENTRY_FILENAMES = new Set([
  * it as a boundary for having no default. Counting it as an entry both inflated
  * the coverage number and would have recorded a shared component in the
  * graph-weight baseline as though it were a route.
+ *
+ * All four declaring forms count — `export default …`, `export { default } from`,
+ * `export { default, … } from`, and `export { X as default }`. `export { default
+ * as X }` does not: it re-exports someone else's default under a name and leaves
+ * the module without one. Missing a form is the dangerous direction, since the
+ * entry would drop out of the walk and skip both the registry gate and the
+ * graph-weight ratchet silently.
  */
 const DEFAULT_EXPORT_RE =
-  /(?:^|\n)\s*export\s+default\b|(?:^|\n)\s*export\s*\{[^}]*\bas\s+default\b/
+  /(?:^|\n)\s*export\s+default\b|(?:^|\n)\s*export\s*\{[^}]*(?:\bas\s+default\b|\bdefault\s*[,}])/
 
 function hasDefaultExport(file: string): boolean {
   try {