@forgecart/cli 2.202609190800.0 → 2.202609211011.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@forgecart/cli",
-  "version": "2.202609190800.0",
+  "version": "2.202609211011.0",
   "type": "module",
   "description": "CLI for scaffolding and operating ForgeCart channel storefronts",
   "bin": {

package/templates/storefront/src/app/{__forge_beacon → %5F%5Fforge_beacon}/route.ts

@@ -12,6 +12,15 @@
  * answers 404 here and forwards nothing — the whole beacon path ships only in the
  * in-pod dev-server. Request access keeps it out of any static prerender so it
  * behaves identically under `next dev` and a dev build.
+ *
+ * Folder name: `%5F%5Fforge_beacon` is URL-encoded `__forge_beacon`. The App Router
+ * treats a folder whose name starts with `_` as PRIVATE and leaves it out of routing
+ * entirely, so the literal spelling this route shipped with answered the not-found
+ * page to every POST — silently, because the client swallows delivery failures by
+ * design (#2103). The `%5F` escape is Next's documented way to serve a URL segment
+ * that really starts with an underscore, and only the FOLDER may change: the URL is
+ * a contract with the in-pod receiver (`StorefrontBeaconService`'s `BEACON_PATH`),
+ * which this template's server half (`src/instrumentation.ts`) posts to as well.
  */
 
 const BEACON_PORT = process.env.FORGE_BEACON_PORT ?? '3002';