feat(core): Class.register() — drop the import.meta.url argument

Authors no longer write `Counter.register(import.meta.url)`; the call
is just `Counter.register()`. Module URLs (used by SSR to emit
`<link rel=modulepreload>` hints) are derived server-side at boot by
scanning the app tree for `class X extends WebComponent { static tag =
'...' }` declarations and priming the core registry.

Same DX, same SSR behaviour, one less piece of boilerplate — and the
awkward `import.meta.url` string no longer leaks into user code.

BREAKING — pre-launch, no back-compat shim:
• `WebComponent.register()` no longer accepts any argument.
• `registry.register(tag, cls)` no longer accepts a third moduleUrl arg.
• Added `registry.primeModuleUrl(tag, moduleUrl)` for server-side use.

Components / scaffold
• All 11 blog components migrated (counter, error-card, theme-toggle,
  auth-forms, new-post, comments-thread, chat-box, 4 test fixtures).
• Scaffold theme-toggle template migrated.
• CONVENTIONS.md / cursorrules / copilot-instructions / AGENTS.md
  templates migrated.

Server
• New packages/server/src/component-scanner.js — regex-based walker
  that finds component classes in the app tree, derives
  browser-visible URLs, and primes the core registry. Balanced-brace
  parsing handles nested methods / objects inside class bodies.
• Wired into createRequestHandler boot and into rebuild(), so tags
  added / renamed during dev-server sessions stay up to date.
• `webjs check`'s `components-have-register` rule updated to accept
  `.register()` (no args).

Docs
• AGENTS.md, README.md, and 14 docs/ pages updated.
• Editor setup / Styling / Components / Getting Started / Lazy
  Loading / Context / Controllers / Task / WebSockets / SSR /
  Server Actions / Conventions pages + doc-shell / doc-search /
  theme-toggle component sources.

Tests
• New test/component-scanner.test.js — 6 unit tests:
  extractComponents shape matching, hyphen requirement, multi-class
  files, full directory scan, skip rules (.server.ts, .test.ts,
  node_modules), priming verification via lookupModuleUrl.
• test/check.test.js fixtures migrated.
• Full suite: 266 unit / 21 browser, all green.

Author: vivek7405

AGENTS.md

@@ -432,7 +432,7 @@ class MyThing extends WebComponent {
     return html`…`;
   }
 }
-MyThing.register(import.meta.url);
+MyThing.register();
 ```
 
 Mutate state with `this.setState({...})` — it batches a re-render via microtask.
@@ -458,7 +458,7 @@ class StudentCard extends WebComponent {
     return html`<p>${this.student.name}</p>`;
   }
 }
-StudentCard.register(import.meta.url);
+StudentCard.register();
 ```
 
 Built-in constructors (`String`, `Number`, `Boolean`, `Array`, `Object`)
@@ -802,7 +802,7 @@ When you mark an action as `expose('METHOD /path', fn)`, you are declaring it pa
 
 ### Components (`components/*.js`)
 
-- Each file should define **one** custom element and call `Class.register(import.meta.url)` at module top level.
+- Each file should define **one** custom element and call `Class.register()` at module top level.
   Passing `import.meta.url` lets the SSR shell emit a `<link rel="modulepreload">` so the browser can fetch the module without waiting for its parent to parse. Zero build step; big first-paint win.
 - Imported by pages (for SSR) and/or other components (for composition).
 - **Styling convention: shadow-DOM CSS via `static styles = css\`…\``, not inline `style="…"` attributes.** Any repeated visual chunk in pages (layout chrome, cards, muted labels, etc.) should become a component whose styles live in its shadow root. The example app's `<blog-shell>` and `<muted-text>` demonstrate this — pages emit semantic HTML with zero inline styles.

README.md

@@ -100,7 +100,7 @@ export class Counter extends WebComponent {
     `;
   }
 }
-Counter.register(import.meta.url);
+Counter.register();
 ```
 
 Need scoped styles, `<slot>` projection, or embed-ready isolation? Opt

docs/app/docs/components/page.ts

@@ -36,7 +36,7 @@ class MyCounter extends WebComponent {
   }
 }
 
-MyCounter.register(import.meta.url);</pre>
+MyCounter.register();</pre>
 
     <p>That is a complete, working component. Import it from a page or layout and use it like any HTML element:</p>
 
@@ -85,7 +85,7 @@ export default function Home() {
     \`;
   }
 }
-UserCard.register(import.meta.url);</pre>
+UserCard.register();</pre>
 
     <h3>Attribute-to-Property Coercion</h3>
     <p>When an attribute changes on the DOM element, webjs coerces the string value to the declared type:</p>
@@ -146,7 +146,7 @@ UserCard.register(import.meta.url);</pre>
     \`;
   }
 }
-TodoList.register(import.meta.url);</pre>
+TodoList.register();</pre>
 
     <h3>How setState Works</h3>
     <ul>
@@ -189,7 +189,7 @@ class StyledCard extends WebComponent {
     \`;
   }
 }
-StyledCard.register(import.meta.url);</pre>
+StyledCard.register();</pre>
 
     <h3>How Styles Are Applied</h3>
     <ul>
@@ -243,7 +243,7 @@ static styles = css\`
     \`;
   }
 }
-AppCard.register(import.meta.url);</pre>
+AppCard.register();</pre>
 
     <h3>Class-prefix rule for custom CSS</h3>
     <p>Tailwind utilities are unique by construction, so most light-DOM components need zero custom CSS. If you <em>do</em> author a <code>&lt;style&gt;</code> block or import a stylesheet, <strong>every class selector MUST be prefixed with the component's tag name</strong>. Otherwise two components with a <code>.card</code> or <code>.header</code> class will style each other.</p>
@@ -299,7 +299,7 @@ class MyCard extends WebComponent {
     \`;
   }
 }
-Card.register(import.meta.url);</pre>
+Card.register();</pre>
 
     <p><code>static styles</code> on a light-DOM component is silently ignored — there's no shadow root to adopt them into. If you see your styles failing, check whether you forgot <code>static shadow = true</code>.</p>
 
@@ -371,7 +371,7 @@ html\`
     \`;
   }
 }
-PageLayout.register(import.meta.url);
+PageLayout.register();
 
 // Usage: assign content to named slots with the slot="" attribute
 html\`
@@ -491,10 +491,10 @@ render() {
 
     <p>During SSR, <code>?disabled=\${true}</code> emits <code>disabled=""</code> and <code>?disabled=\${false}</code> emits nothing — matching how the browser interprets boolean attributes.</p>
 
-    <h2>register(import.meta.url)</h2>
+    <h2>register()</h2>
     <p>Every component must call <code>register()</code> after its class definition. This static method does two things:</p>
 
-    <pre>MyCounter.register(import.meta.url);</pre>
+    <pre>MyCounter.register();</pre>
 
     <ol>
       <li><strong>Registers with <code>customElements.define()</code></strong> — on the browser, this tells the browser to upgrade all <code>&lt;my-counter&gt;</code> elements with the <code>MyCounter</code> class. On the server, it stores the class in an internal registry so <code>renderToString</code> can look it up.</li>
@@ -504,7 +504,7 @@ render() {
     <p>You can omit <code>import.meta.url</code> and just call <code>MyCounter.register()</code>, but you lose the modulepreload optimization.</p>
 
     <pre>// With module URL — recommended
-Counter.register(import.meta.url);
+Counter.register();
 
 // Without module URL — works but no modulepreload hint
 Counter.register();</pre>
@@ -553,7 +553,7 @@ Counter.register();</pre>
     \`;
   }
 }
-UserProfile.register(import.meta.url);</pre>
+UserProfile.register();</pre>
 
     <p>On the client, <code>render()</code> is called synchronously. If you need async data on the client, fetch it in <code>connectedCallback()</code> and call <code>setState()</code> when the data arrives.</p>
 
@@ -622,7 +622,7 @@ class TaskList extends WebComponent {
     \`;
   }
 }
-TaskList.register(import.meta.url);</pre>
+TaskList.register();</pre>
 
     <h3>How repeat() Works</h3>
     <ul>
@@ -701,13 +701,13 @@ class ChatBox extends WebComponent {
     \`;
   }
 }
-ChatBox.register(import.meta.url);</pre>
+ChatBox.register();</pre>
 
     <h2>Quick Reference</h2>
     <ul>
       <li><strong>Extend</strong> <code>WebComponent</code> and set <code>static tag</code>, <code>static properties</code>, <code>static styles</code>.</li>
       <li><strong>Implement</strong> <code>render()</code> returning <code>html\`...\`</code>.</li>
-      <li><strong>Register</strong> with <code>ClassName.register(import.meta.url)</code>.</li>
+      <li><strong>Register</strong> with <code>ClassName.register()</code>.</li>
       <li><strong>State</strong> — use <code>this.setState({...})</code> for shallow merge + batched re-render.</li>
       <li><strong>Events</strong> — <code>@click</code>, <code>@submit</code>, <code>@input</code> in templates. Stable dispatchers, no listener churn.</li>
       <li><strong>Bindings</strong> — <code>attr=\${v}</code> for attributes, <code>.prop=\${v}</code> for properties, <code>?bool=\${v}</code> for booleans.</li>

docs/app/docs/context/page.ts

@@ -71,7 +71,7 @@ class AppShell extends WebComponent {
     \`;
   }
 }
-AppShell.register(import.meta.url);</pre>
+AppShell.register();</pre>
 
     <p>When you call <code>provider.setValue(newValue)</code>, every subscribed consumer is notified and its host component re-renders automatically.</p>
 
@@ -106,7 +106,7 @@ class ThemedCard extends WebComponent {
     \`;
   }
 }
-ThemedCard.register(import.meta.url);</pre>
+ThemedCard.register();</pre>
 
     <h2>Subscribe vs One-Shot Mode</h2>
     <p>The <code>subscribe</code> option controls whether the consumer receives ongoing updates:</p>
@@ -178,7 +178,7 @@ class AppRoot extends WebComponent {
     return html\`&lt;slot&gt;&lt;/slot&gt;\`;
   }
 }
-AppRoot.register(import.meta.url);</pre>
+AppRoot.register();</pre>
 
     <h2>Nested Providers</h2>
     <p>Providers can be nested. A consumer resolves to the nearest ancestor provider with a matching context key:</p>
@@ -230,7 +230,7 @@ class AuthProvider extends WebComponent {
     return html\`&lt;slot&gt;&lt;/slot&gt;\`;
   }
 }
-AuthProvider.register(import.meta.url);
+AuthProvider.register();
 
 // components/user-menu.ts
 import { WebComponent, html } from 'webjs';
@@ -252,7 +252,7 @@ class UserMenu extends WebComponent {
     return html\`&lt;span&gt;Hi, \${user.name}&lt;/span&gt;\`;
   }
 }
-UserMenu.register(import.meta.url);</pre>
+UserMenu.register();</pre>
 
     <h2>Next Steps</h2>
     <ul>

docs/app/docs/controllers/page.ts

@@ -79,7 +79,7 @@ class LazyImage extends WebComponent {
     \`;
   }
 }
-LazyImage.register(import.meta.url);</pre>
+LazyImage.register();</pre>
 
     <h2>Example: FetchController</h2>
     <p>A reusable controller that fetches data from a URL and exposes loading/error/data states:</p>
@@ -137,7 +137,7 @@ class UserList extends WebComponent {
     \`;
   }
 }
-UserList.register(import.meta.url);</pre>
+UserList.register();</pre>
 
     <h2>Multiple Controllers on One Component</h2>
     <p>Controllers compose naturally. A single component can use any number of controllers:</p>
@@ -159,7 +159,7 @@ UserList.register(import.meta.url);</pre>
     return html\`&lt;div&gt;\${this.#data.data?.summary}&lt;/div&gt;\`;
   }
 }
-DashboardWidget.register(import.meta.url);</pre>
+DashboardWidget.register();</pre>
 
     <h2>Built-in Controllers</h2>
     <p>webjs ships three controllers out of the box:</p>

docs/app/docs/conventions/page.ts

@@ -26,7 +26,7 @@ export default function Conventions() {
 
 - Opt in to shadow DOM (static shadow = true) for every component
 - Author styles via static styles = css`...`
-- Always call register(import.meta.url)</pre>
+- Always call register()</pre>
 
     <p>AI agents read <code>CONVENTIONS.md</code> before every task and follow the overrides. You can also disable specific convention rules in <code>package.json</code>:</p>
 

docs/app/docs/editor-setup/page.ts

@@ -57,7 +57,7 @@ export class StudentCard extends WebComponent {
     return html\`<p>\${this.student.name}</p>\`;
   }
 }
-StudentCard.register(import.meta.url);</pre>
+StudentCard.register();</pre>
 
     <p>Inside the class, <code>this.student</code> is a real <code>Student</code> — hover, autocomplete, type-checking all work. <code>this.setState</code>, <code>this.state</code>, <code>this.requestUpdate</code>, and all lifecycle hooks are typed by the framework's <code>.d.ts</code> overlay.</p>
 

docs/app/docs/getting-started/page.ts

@@ -109,7 +109,7 @@ export class Counter extends WebComponent {
     \`;
   }
 }
-Counter.register(import.meta.url);</pre>
+Counter.register();</pre>
 
     <h3>Run it</h3>
     <pre>npx webjs dev

docs/app/docs/lazy-loading/page.ts

@@ -35,7 +35,7 @@ class HeavyChart extends WebComponent {
     return html${'`'}<canvas></canvas>${'`'};
   }
 }
-HeavyChart.register(import.meta.url);</pre>
+HeavyChart.register();</pre>
 
     <h2>How it works</h2>
     <ol>

docs/app/docs/server-actions/page.ts

@@ -112,7 +112,7 @@ export class PostForm extends WebComponent {
     \`;
   }
 }
-PostForm.register(import.meta.url);</pre>
+PostForm.register();</pre>
 
     <h2>The superjson Wire Format</h2>
     <p>Server actions use <strong>superjson</strong> for serialisation, not plain <code>JSON.stringify</code>. The content type is <code>application/vnd.webjs+json</code>. This means rich JavaScript types survive the round trip:</p>
@@ -323,7 +323,7 @@ export class TodoApp extends WebComponent {
     \`;
   }
 }
-TodoApp.register(import.meta.url);
+TodoApp.register();
 
 // 3. Call the REST endpoint from curl
 // curl -X POST http://localhost:3000/api/todos \\