chore: bump release references to v2.4.0

Follow wcstack v2.4.0 (2026-09-15) - the $scan release (monorepo PRs
#262-#278). One feature and five state fixes; the package set is
unchanged at 50 and no I/O node or router surface changed.

Six cards. Two on the feature: $scan itself (an accumulation that
outlives a $streams restart - from folds each landing of a state path
once per batch, on folds each event of a declared token, the output is
materialized from initial with plain data copied, and it survives
restarts, disconnects and re-sets of the same object), and where the
fold sits (the fixed $updatedCallback -> $scan -> $watch -> restart
order, on before $on, reset wins / restart wins, a getter is never a
source, wcs/scan-feedback-loop, once per landing rather than once per
page, and wcs/scan-path-missing in the linter).

Four on the fixes: rows repaired instead of rebuilt when row objects are
replaced but their children arrays kept (#256 - only the row's own
aggregate froze, and a rebuild was measured to destroy a bind-component
child scope's rows, an open <details>, focus and a JS marker); an
element that fails to initialize reporting once and rejecting
connectedCallbackPromise with the original error instead of hanging
(#257); token registries kept across a root re-attach (#273) together
with a re-set reading the new generation (#258, with #267 / #268 stated
as still open); and a wildcard $watch firing once per row as the list
stands at the drain (#274).

state/ gains a "Scan: $scan" section between $streams and $watch (the
feed + log example, field and rule tables, firing timing, and the
getter / $streams fold / $scan / $watch choice table) with a TOC entry
and a meta description mention, plus v2.4.0 notes in Lifecycle hooks
(init failure, re-set), Recursive paths (#256), Event tokens (#273),
$streams (a pointer to $scan) and the $watch rules table (row firing;
$scan joins the mounted-scope exclusion). Hero release pill v2.3.0 ->
v2.4.0; state/ and signals/ pills follow. The remaining "v2.3.0"
strings on state/ are feature-introduction labels and stay.

llms regenerated at v2.4.0 against clean v2.4.0 worktrees of both the
monorepo and wcstack-skill (tag v2.4.0, 9c53280, stamped for v2.4.0), so
the build runs without the stamp warning and llms-full.txt carries the
$scan reference. llms.txt keeps 39 I/O node packages with every link
re-pinned. sitemap lastmod 2026-09-15.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: mogera551

index.html

@@ -308,7 +308,7 @@ <h1 class="pkg-title">@wcstack/signals</h1>
       <p class="pkg-sub">A signals-based, <strong>fine-grained</strong> reactive core &mdash; <code style="font-family:var(--mono)">signal</code> / <code style="font-family:var(--mono)">computed</code> / <code style="font-family:var(--mono)">effect</code>, async resources, a no-VDOM DOM layer, and bridges for wc-bindable elements or their headless Cores. Zero runtime dependencies, buildless, standards-first.</p>
       <p class="pkg-sub-ja">シグナルベースの細粒度リアクティブコア。TC39形のAPI、非同期resource、VDOMなしのDOM層、wc-bindable要素とヘッドレスCoreのブリッジ。ランタイム依存ゼロ。</p>
       <div class="pill-row">
-        <span class="pill accent">v2.3.0</span>
+        <span class="pill accent">v2.4.0</span>
         <span class="pill">@wcstack/signals</span>
         <span class="pill">core &asymp;3.1 KB gz</span>
         <span class="pill">dom +&asymp;3.8 KB gz</span>

llms-full.txt

@@ -2,19 +2,19 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://wcstack.github.io/</loc>
-    <lastmod>2026-09-12</lastmod>
+    <lastmod>2026-09-15</lastmod>
     <changefreq>weekly</changefreq>
     <priority>1.0</priority>
   </url>
   <url>
     <loc>https://wcstack.github.io/state/</loc>
-    <lastmod>2026-09-12</lastmod>
+    <lastmod>2026-09-15</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.8</priority>
   </url>
   <url>
     <loc>https://wcstack.github.io/signals/</loc>
-    <lastmod>2026-09-12</lastmod>
+    <lastmod>2026-09-15</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.8</priority>
   </url>