@stopnetic/js 0.0.2-pilot → 0.0.4-pilot

package/README.md

@@ -6,17 +6,54 @@ frontend build. No React/Vue/Angular dependency or version upgrade is required.
 The hosting server must run Node.js 22 or newer. This is an MIT-licensed pilot SDK;
 hosted production/provider validation is still required before paid rollout.
 
-Version **0.0.1-pilot is published** on npm. This repository prepares
-**0.0.2-pilot**, which adds a reusable browser/server setup for Netlify, Vercel
+Version **0.0.4-pilot is prepared locally; it is not published yet**. It adds
+complete copyable React Router, Angular Router/HttpClient, Vue Router, Svelte,
+Solid Router and plain JavaScript examples to the generated guide and package.
+Unchanged 0.0.2/0.0.3 guides migrate safely; custom edits require merging.
+Angular, React, Vue, Svelte, Solid and plain JavaScript share the browser/server
+contracts; no React dependency is required. See the
+[complete generated guide](dist/client-guide.md) for SSR, static builds, frameworks,
+client navigation, API protection and runtime restrictions.
+
+The currently published **0.0.3-pilot** includes the framework-independent
+server/browser setup, complete Node application wrapper and older-guide
+migration. Version 0.0.2 added the reusable browser/server setup for Netlify, Vercel
 and Node/Express, a browser access check and optional React boundary. It also
 normalizes public PEM formatting and rejects placeholder or reused installation
-keys as cookie secrets. The new version is not published yet. Install the
-currently published manual server pilot with:
+keys as cookie secrets. Install the published pilot with:
 
 ```sh
 npm install @stopnetic/js@pilot
 ```
 
+## Framework implementation examples
+
+The guide and `examples/frontend` contain complete, locally tested examples:
+
+| Frontend | Example |
+| --- | --- |
+| React | BrowserRouter, full-layout StopneticBoundary, Routes and effect-based API loading |
+| Angular | Route guard/service, layout signals, RouterOutlet and HttpClient |
+| Vue | Vue Router beforeEach/afterEach, gated App.vue and API loading |
+| Svelte | onMount, History API/popstate navigation and abort cleanup |
+| Solid | Router root, useLocation, reactive Show boundary and API loading |
+| Plain JavaScript | DOM rendering, checked navigation and API loading |
+
+Each example includes initial access, later navigation, verification redirect,
+pending/denied UI and cancellation. Backend page/API guards remain necessary.
+No framework library is added as a required SDK dependency. The generated guide
+embeds the source; use its file paths and helper instructions when copying it.
+The dashboard's frontend selector shows the same files. For maintenance, run
+`npm run build` in this SDK, then `npm run sync:guides` in dashboard.
+
+To rerun the frontend compilation/browser fixtures, build the SDK and run
+`node tests/prepare-framework-tests.mjs` in this directory. This packs the SDK
+and installs pinned test-only libraries inside ignored test-results. Then run
+`.venv/Scripts/python.exe integrations/javascript/tests/framework-browser-check.py`
+from the repository root. The Angular fixture uses an existing Angular install:
+`angular-guide-check.py <project-path>`; it copies source into the workspace,
+compiles the examples and tests browser/Node SSR without changing that project.
+
 For local testing, build and pack from this repository:
 
 ```sh
@@ -25,15 +62,20 @@ npm run build
 npm pack
 ```
 
-Install the resulting `stopnetic-js-0.0.2-pilot.tgz` into the website project using
+Install the resulting `stopnetic-js-0.0.4-pilot.tgz` into the website project using
 `npm install <absolute-path-to-tarball>`. The installed package has no Next.js or
 other runtime dependency. The build packages the same signed decision implementation
 as the Next.js adapter. Keep `@stopnetic/next` for its Next.js 16 guided installer.
 
 ## Reusable client/server setup (requires 0.0.2-pilot)
 
-Use the local tarball above until this version is published. Installing the current
-registry pilot (0.0.1) does not provide these new commands or subpath exports.
+Follow the [hosting guide](../../docs/javascript-hosting-guide.md) for the full
+Netlify, Vercel or Node procedure, server settings, page HTTP 404 enforcement,
+frontend/API wiring and diagnosis. The dashboard's Integration and Documentation
+pages offer the same provider choices and complete copyable page-guard examples.
+
+The published 0.0.2-pilot includes these commands and subpath exports.
+Older 0.0.1-pilot installations must upgrade before using them.
 
 Run setup at the app's package.json, choose hosting, and preview before writing:
 
@@ -67,7 +109,31 @@ and server functions; Vite alone does not provide the generated server endpoints
 For Node, use `node --env-file=.env.local your-server.mjs` or your existing
 server environment loader. Production credentials belong in runtime settings.
 
-### React Router
+### Shared browser startup and Node SSR
+
+The generated [framework-independent guide](src/client-guide.md) gives one
+browser entry that calls `checkAccess` before importing the application's
+existing bootstrap. Keep Angular's bootstrapApplication, React's createRoot,
+Vue's createApp, Svelte's mount, Solid's render or plain DOM startup unchanged
+in that bootstrap module. Use document links for server-checked navigation,
+or recheck target access in the client router. A browser-only check is UI behavior.
+
+For Node SSR use the generated Express helper before static files/rendering,
+or `createStopneticAppHandler` around a Fetch-style application entry (0.0.3).
+The wrapper handles access/verification control endpoints and guards pages and
+APIs before calling the renderer. It preserves context, streams and request
+bodies. Framework hooks with another signature still need their continuation
+adapted; accepting Request/Response does not make an Edge runtime supported.
+
+The guide includes Angular SSR/rendering and client router examples. Angular
+SSR compiled with the installed Angular 22 dependencies and served real HTML
+after verification in an isolated local fixture. That does not validate a live
+provider deployment. Netlify's automatic Angular SSR uses Edge; choose Node SSR,
+a Node gateway or a deliberate static build. Do not publish protected prerendered
+HTML. For other frameworks use the same Node server entry and verify their
+actual deployed runtime. React's boundary remains an optional convenience.
+
+### Optional React Router boundary
 
 The optional React entry uses Hooks. The core/browser modules need no React.
 Place this component inside BrowserRouter, wrapping your Routes:
@@ -119,6 +185,21 @@ content or an API authorization token. API wrappers independently check every
 request and preserve ordinary request bodies. Denials/outages return empty
 404/503 responses; approved data responses use `private, no-store`.
 
+For a real HTTP 404 on a Netlify SPA page, use the optional page-serving function
+in `examples/netlify-spa-pages.mjs` and follow
+[`docs/netlify-spa-page-requests.md`](../../docs/netlify-spa-page-requests.md).
+It checks signed access before reading the bundled entry HTML. The browser
+boundary alone cannot change the initial document's HTTP status. This example
+uses the published 0.0.2-pilot server helpers; the setup CLI does not install it
+automatically. Keep static bundles public and private data in guarded APIs.
+
+For Vercel page responses, the manual Node routing middleware in
+`examples/vercel-spa-middleware.mjs` checks pages before static HTML, using
+`@vercel/functions` and the existing SDK. The CLI's generated Vercel control
+function alone does not guard page documents. Follow the hosting guide for
+middleware, API/asset routing and SPA rewrite configuration. Local signed tests
+cover it; live Vercel deployment validation remains required.
+
 ### Node servers on other hosts
 
 Import `installStopnetic` from generated `stopnetic.server.mjs`, then call