@chidchanun/bcp 0.2.4 → 0.2.5

package/README.md

@@ -2,13 +2,13 @@
 
 BCP Framework is a React full-stack framework for file-based routing, SSR, SPA navigation, server data loading, guarded application flows, API routes, authentication, database access, validation, uploads, storage and standalone Node.js production deployment.
 
-> **Development target:** `0.2.4 — Application Packaging`
+> **Development target:** `0.2.5 — Authentication Platform v2`
 >
-> `0.2.4` is an unreleased development target until local validation, RC checks, tagging and npm publication complete.
+> `0.2.5` is an unreleased development target until local validation, RC checks, tagging and npm publication complete.
 
 ## 0.2 platform
 
-`0.2.0` established the Framework Platform baseline, `0.2.1` added the Documentation Platform, `0.2.2` added Configuration & Environment v2, `0.2.3` added Database Platform v2, and `0.2.4` adds deployment-oriented application packaging without intentionally removing the existing public application model.
+`0.2.0` established the Framework Platform baseline, `0.2.1` added the Documentation Platform, `0.2.2` added Configuration & Environment v2, `0.2.3` added Database Platform v2, `0.2.4` added Application Packaging, and `0.2.5` adds optional revocable authentication sessions and guest-aware route guards without intentionally removing the existing stateless JWT-cookie model.
 
 Machine-readable platform contracts:
 
@@ -31,8 +31,8 @@ docs/api-manifest.json
 | Routing | Static, dynamic, catch-all, optional catch-all and route groups |
 | Server data | Route `loader.ts`, request-scoped server APIs |
 | Mutations | Route-owned `actions.ts` and `<Form>` |
-| Authorization | `guard.ts`, `requireAuth()`, `requireRole()` |
-| Authentication | JWT cookie sessions and auth helpers |
+| Authorization | `guard.ts`, `requireAuth()`, `requireGuest()`, `requireRole()` |
+| Authentication | JWT cookie sessions, optional server-side session stores, revocation, logout-all, idle timeout and rotation |
 | Middleware | Middleware System v2 with onion execution |
 | Validation | Typed validators and structured validation errors |
 | Error handling | HTTP error helpers and consistent error responses |
@@ -181,12 +181,6 @@ Create a fresh production build and convert it into a deployment-oriented packag
 bcp package
 ```
 
-Framework-repository development can also run:
-
-```bash
-npm run package
-```
-
 Output:
 
 ```text
@@ -206,30 +200,81 @@ Output:
 └─ README.md
 ```
 
-The package layer:
+The package layer creates production-only dependency metadata, deployment/environment manifests, SHA-256 file integrity metadata and a Node 24 Alpine Docker starter.
+
+Read more:
 
-- runs a fresh `bcp build` before packaging,
-- strips application `devDependencies` from the deployment package,
-- derives a production-only npm v3 lock graph when safe,
-- records `npm ci --omit=dev` when the production lock is available,
-- falls back explicitly to `npm install --omit=dev` when a safe lock cannot be produced,
-- writes deployment/runtime metadata,
-- records environment variable names without copying `.env` values,
-- creates SHA-256 file integrity metadata,
-- generates a Node 24 Alpine Docker starter.
+- [Application Packaging](docs/application-packaging.md)
+- [Deployment](docs/deployment.md)
 
-The current package target is:
+## Authentication Platform v2 — 0.2.5
 
-```text
-standalone-node
+The existing stateless JWT-cookie mode remains available:
+
+```ts
+import {
+    auth,
+    login,
+    logout,
+} from "bcp/auth";
+```
+
+Applications that need centralized revocation can add a server-side session store:
+
+```ts
+import {
+    createAuth,
+    createMemoryAuthSessionStore,
+} from "bcp/auth";
+
+const sessionStore =
+    createMemoryAuthSessionStore();
+
+export const appAuth =
+    createAuth({
+        store:
+            sessionStore,
+        idleTimeout:
+            60 * 30,
+    });
+```
+
+With a store configured, authentication requires both a valid signed JWT cookie and an active `sid` record.
+
+New lifecycle APIs:
+
+```ts
+await appAuth.logout();
+await appAuth.logoutAll();
+await appAuth.revokeSession(sid);
+await appAuth.revokeUserSessions(userId);
+await appAuth.rotateSession();
+```
+
+`idleTimeout` is enforced only when a server-side store is configured. BCP rejects the option in stateless-only mode rather than silently pretending to enforce inactivity expiration.
+
+Guest-only login/register routes can use:
+
+```ts
+import {
+    createGuestGuard,
+} from "bcp/auth";
+
+export const guard =
+    createGuestGuard({
+        redirectTo:
+            "/dashboard",
+    });
 ```
 
-Native executable, desktop, Android and iOS packaging remain later roadmap work.
+The built-in memory session store is intended for development/tests and process-local prototypes. Production applications running multiple processes or containers should implement `AuthSessionStore` with shared durable storage such as Redis or a database.
 
 Read more:
 
-- [Application Packaging](docs/application-packaging.md)
-- [Deployment](docs/deployment.md)
+- [Authentication](docs/authentication.md)
+- [Auth Session Stores](docs/auth-session-store.md)
+- [Auth Route Guards](docs/auth-route-guards.md)
+- [JWT Sessions](docs/session-auth.md)
 
 ## Public entrypoints
 
@@ -337,16 +382,6 @@ npm run build
 npm run start
 ```
 
-Output:
-
-```text
-.bcp-framework/build/
-├─ client/
-├─ public/
-└─ server/
-   └─ server.mjs
-```
-
 Deployment package:
 
 ```bash
@@ -369,12 +404,6 @@ docs/api-manifest.json
 
 The manifests provide navigation order, routes, Markdown sources, version/release state, public entrypoints and API guide ownership.
 
-Read more:
-
-- [Documentation Source Map](docs/README.md)
-- [Documentation Platform](docs/documentation-platform.md)
-- [Application Packaging](docs/application-packaging.md)
-
 ## Release validation
 
 Framework releases must pass:
@@ -389,7 +418,7 @@ npm run test:e2e
 npm run rc:check
 ```
 
-`0.2.4` adds Application Packaging unit and prepared-package smoke checks covering production dependency metadata, production lock pruning, environment-value exclusion, deployment metadata and the `bcp package` CLI surface.
+`0.2.5` adds Authentication Platform v2 unit and prepared-package smoke checks covering session-store registration, revocation, logout-all, idle timeout, rotation and guest guards.
 
 Do not tag or publish until the final release commit passes the complete RC sequence.
 
@@ -408,12 +437,13 @@ Do not tag or publish until the final release commit passes the complete RC sequ
 | `0.2.2` | Configuration & Environment v2 |
 | `0.2.3` | Database Platform v2 |
 | `0.2.4` | Application Packaging |
+| `0.2.5` | Authentication Platform v2 |
 
 ## Roadmap
 
-`0.2.4 — Application Packaging` establishes the deployment artifact contract for the existing standalone Node.js runtime.
+`0.2.5 — Authentication Platform v2` establishes optional revocable server-side auth state while preserving the original stateless JWT-cookie path.
 
-The next planned framework milestone can build on this package contract without changing the current Node.js deployment model. Native `.exe`, desktop and mobile compilation remain later roadmap work.
+A later security/authorization milestone can build on this session contract for broader permission and security policy features. Native `.exe`, desktop and mobile compilation remain later roadmap work.
 
 ## License
 

package/docs/README.md

@@ -2,9 +2,9 @@
 
 The `docs/` directory is the documentation source of truth for BCP Framework and is organized for **`bcp-docs-web`**.
 
-> **Documentation target:** BCP Framework `0.2.2`
+> **Documentation target:** BCP Framework `0.2.5 — Authentication Platform v2`
 >
-> **Release state:** unreleased development target. Do not label `0.2.2` as published until RC validation, tagging and npm publication complete.
+> **Release state:** unreleased development target until RC validation, tagging and npm publication complete.
 
 ## Documentation architecture
 
@@ -41,32 +41,73 @@ manifest-driven sync
 
 Framework source and tests remain authoritative for runtime behavior.
 
-## 0.2.2 — Configuration & Environment v2
+## Current 0.2.x milestones
 
-`0.2.2` adds an optional typed application environment schema while preserving the established framework configuration precedence.
+| Version | Milestone |
+| --- | --- |
+| `0.2.0` | Framework Platform |
+| `0.2.1` | Documentation Platform |
+| `0.2.2` | Configuration & Environment v2 |
+| `0.2.3` | Database Platform v2 |
+| `0.2.4` | Application Packaging |
+| `0.2.5` | Authentication Platform v2 |
+
+## 0.2.5 — Authentication Platform v2
+
+`0.2.5` keeps stateless signed JWT-cookie authentication as the default and adds optional server-side session state for revocation and inactivity policy.
 
 New/updated documentation sources:
 
 | Source | Purpose |
 | --- | --- |
-| `environment-validation.md` | `bcp.environment.*`, validation rules, CLI checks and secret/public boundaries |
-| `configuration.md` | Framework configuration precedence and diagnostics workflow |
-| `platform-manifest.json` | Declares typed environment/config diagnostics capabilities |
-| `api-manifest.json` | Maps `bcp/config` to configuration and environment guides |
-| `releases/0.2.2.md` | Configuration & Environment v2 release notes |
+| `authentication.md` | Auth core, revocation, logout-all, rotation and idle timeout |
+| `auth-session-store.md` | `AuthSessionStore`, memory adapter and production-store guidance |
+| `auth-route-guards.md` | Auth, guest and role route guards |
+| `api-reference.md` | Public Authentication Platform v2 exports |
+| `platform-manifest.json` | Authentication v2 capability flags |
+| `api-manifest.json` | `bcp/auth` guide ownership |
+| `releases/0.2.5.md` | Authentication Platform v2 release notes |
 
-Primary command:
+Primary public entrypoint:
 
-```bash
-bcp config check
+```ts
+import {
+    auth,
+    createAuth,
+    createMemoryAuthSessionStore,
+    login,
+    logout,
+    logoutAll,
+    requireAuth,
+    requireGuest,
+    requireRole,
+} from "bcp/auth";
 ```
 
-JSON diagnostics:
+## Authentication security model
 
-```bash
-bcp config check --json
+Default mode:
+
+```text
+signed HttpOnly JWT cookie
+      ↓
+signature + expiry validation
+      ↓
+authenticated session
 ```
 
+Optional revocable mode:
+
+```text
+signed HttpOnly JWT cookie
+      +
+server-side sid store
+      ↓
+revocable authenticated session
+```
+
+The built-in memory store is intended for development/tests. Multi-process production systems should implement `AuthSessionStore` using shared durable storage.
+
 ## Update rule
 
 When framework behavior or public surface changes:
@@ -103,76 +144,24 @@ Important current routes:
 
 | Website route | Markdown source |
 | --- | --- |
-| `/docs/configuration` | `configuration.md` |
-| `/docs/environment-validation` | `environment-validation.md` |
-| `/docs/platform-contract` | `platform-contract.md` |
-| `/docs/documentation-platform` | `documentation-platform.md` |
-| `/docs/migration-0.2` | `migration-0.2.md` |
+| `/docs/authentication` | `authentication.md` |
+| `/docs/auth-session-store` | `auth-session-store.md` |
+| `/docs/auth-route-guards` | `auth-route-guards.md` |
+| `/docs/application-packaging` | `application-packaging.md` |
+| `/docs/database` | `database.md` |
 | `/docs/api-reference` | `api-reference.md` |
-| `/releases/0.2.2` | `releases/0.2.2.md` |
+| `/releases/0.2.5` | `releases/0.2.5.md` |
 
 Every route/source pair is validated by unit tests.
 
-## Configuration source model
-
-Framework settings:
-
-```text
-bcp.config.ts
-bcp.config.mts
-bcp.config.js
-bcp.config.mjs
-```
-
-Application environment schema:
-
-```text
-bcp.environment.ts
-bcp.environment.mts
-bcp.environment.js
-bcp.environment.mjs
-```
-
-Only one file from each convention may exist at a time.
-
-The environment schema is optional. Existing applications without `bcp.environment.*` continue to use the previous environment-loading behavior.
-
-Configuration precedence remains:
-
-```text
-CLI override
-    ↓
-BCP_* environment
-    ↓
-bcp.config.*
-    ↓
-framework defaults
-```
-
-See [Environment Validation](environment-validation.md).
-
-## Environment security boundary
-
-`BCP_PUBLIC_*` values may be embedded into browser bundles. They must never contain credentials/private secrets.
-
-A variable declared with:
-
-```ts
-secret: true
-```
-
-must not use the `BCP_PUBLIC_` prefix. The configuration validator treats that combination as an error.
-
-`secret: true` is validation/tooling metadata and does not encrypt a value.
-
 ## Platform manifest
 
-`docs/platform-manifest.json` describes the supported framework baseline, including:
+`docs/platform-manifest.json` describes:
 
 ```text
 framework version/release state
 Node/React/runtime baseline
-production build target
+production build/package target
 public package entrypoints
 CLI command families
 capability flags
@@ -180,14 +169,6 @@ previous-baseline compatibility intent
 documentation contract files
 ```
 
-`0.2.2` declares the additional capabilities:
-
-```text
-typedEnvironmentSchema
-configurationDiagnostics
-configCheckCli
-```
-
 The supported production target remains:
 
 ```text
@@ -196,7 +177,7 @@ standalone-node
 
 ## API manifest
 
-`docs/api-manifest.json` describes the public package entrypoints documentation tooling may present as supported API surfaces.
+`docs/api-manifest.json` describes public package entrypoints documentation tooling may present as supported APIs.
 
 Current entrypoints:
 
@@ -214,13 +195,6 @@ bcp/server-only
 bcp/middleware
 ```
 
-`bcp/config` owns both:
-
-```text
-/docs/configuration
-/docs/environment-validation
-```
-
 The API-manifest entrypoint set must match the platform public-entrypoint set exactly.
 
 ## bcp-docs-web synchronization
@@ -241,14 +215,6 @@ load referenced Markdown
 synchronize CMS/search/navigation
 ```
 
-Examples from the docs-web project:
-
-```powershell
-npm run docs:sync -- --dry-run
-npm run docs:sync -- --publish-new
-npm run docs:sync -- --ref=v0.2.1
-```
-
 ## Source conventions
 
 - one H1 per Markdown page,
@@ -263,7 +229,7 @@ npm run docs:sync -- --ref=v0.2.1
 
 ## Release validation
 
-Before publishing `0.2.2`:
+Before publishing `0.2.5`:
 
 ```bash
 npm run typecheck
@@ -274,16 +240,17 @@ npm run test:e2e
 npm run rc:check
 ```
 
-Configuration & Environment v2 validation covers:
-
-- typed environment rules/defaults,
-- project `bcp.environment.*` loading,
-- public/secret safety boundary,
-- production diagnostics,
-- `bcp config check` CLI parsing,
-- dev schema watching,
-- public `bcp/config` exports,
-- prepared npm package files,
+Authentication Platform v2 validation covers:
+
+- stateless JWT backward compatibility,
+- session-store registration and lookup,
+- session revocation,
+- logout-all,
+- idle timeout,
+- rotation with old-session revocation,
+- guest route guards,
+- public `bcp/auth` exports,
+- prepared npm package contents,
 - docs/platform/API version parity.
 
 The final release tag must point to the exact commit that passed the complete RC sequence.
@@ -304,19 +271,3 @@ release notes
 ```
 
 `bcp-docs-web` remains the presentation/search/navigation layer for this content.
-
-## Next direction
-
-Planned next milestone:
-
-```text
-0.2.3 — Database Platform v2
-```
-
-Focus:
-
-- database adapter contract,
-- PostgreSQL support,
-- SQLite support,
-- connection lifecycle improvements,
-- provider-consistent migration workflows.

package/docs/api-manifest.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "framework": "bcp",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "releaseState": "unreleased",
   "coverage": "public-entrypoints",
   "entrypoints": [
@@ -85,9 +85,10 @@
       "source": "packages/client/src/auth.ts",
       "environment": "server",
       "route": "/docs/api-reference#bcp-auth",
-      "summary": "Authentication, login/logout/session rotation and route authorization guards.",
+      "summary": "Authentication Platform v2 with JWT cookies, optional revocable session stores, idle timeout, logout-all and auth/guest/role route guards.",
       "guides": [
         "/docs/authentication",
+        "/docs/auth-session-store",
         "/docs/auth-route-guards",
         "/docs/session-auth"
       ]

package/docs/api-reference.md

@@ -164,25 +164,45 @@ Related guides: [Database](database.md), [Database Migrations](database-migratio
 
 ## `bcp/auth`
 
-Authentication and authorization APIs.
+Server-only Authentication Platform v2 APIs.
 
 ```ts
 import {
     auth,
     createAuth,
     createAuthGuard,
+    createGuestGuard,
+    createMemoryAuthSessionStore,
     createRoleGuard,
     getGuardAuth,
     getSession,
     login,
     logout,
+    logoutAll,
     requireAuth,
+    requireGuest,
     requireRole,
+    revokeSession,
+    revokeUserSessions,
     rotateSession,
+    type AuthApi,
+    type AuthLoginOptions,
+    type AuthOptions,
+    type AuthSession,
+    type AuthSessionStore,
+    type AuthSessionStoreRecord,
+    type AuthUser,
+    type MemoryAuthSessionStore,
 } from "bcp/auth";
 ```
 
-Related guides: [Authentication](authentication.md), [Auth Route Guards](auth-route-guards.md), [JWT Sessions](session-auth.md).
+The default mode remains stateless signed JWT-cookie authentication.
+
+Configure `AuthOptions.store` to enable server-side session revocation and `idleTimeout`. `createMemoryAuthSessionStore()` is provided for development/testing; production multi-instance applications should implement `AuthSessionStore` with shared durable storage.
+
+`logoutAll()`, `revokeSession()`, and `revokeUserSessions()` require server-side session state. `requireGuest()` / `createGuestGuard()` support login/register routes that should redirect already-authenticated users.
+
+Related guides: [Authentication](authentication.md), [Auth Session Stores](auth-session-store.md), [Auth Route Guards](auth-route-guards.md), [JWT Sessions](session-auth.md).
 
 ## `bcp/server`