@chidchanun/bcp 0.2.8 → 0.2.9

package/README.md

@@ -1,14 +1,14 @@
 # BCP Framework
 
-BCP Framework is a React full-stack framework for file-based routing, SSR, SPA navigation, server data loading, guarded application flows, API routes, authentication, authorization, database access, background jobs, observability, validation, uploads, storage and standalone Node.js production deployment.
+BCP Framework is a React full-stack framework for file-based routing, SSR, SPA navigation, server data loading, guarded application flows, API routes, authentication, authorization, database access, background jobs, recurring scheduling, observability, validation, uploads, storage and standalone Node.js production deployment.
 
-> **Development target:** `0.2.8 — Background Jobs Platform`
+> **Development target:** `0.2.9 — Job Scheduling Platform`
 >
-> `0.2.8` is an unreleased development target until local validation, RC checks, tagging and npm publication complete.
+> `0.2.9` 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, `0.2.4` added Application Packaging, `0.2.5` added Authentication Platform v2, `0.2.6` added Authorization & Security v2, `0.2.7` added Observability Platform v2, and `0.2.8` adds a provider-neutral background-job queue/worker contract with delayed work, retry/backoff, cancellation and process-local reference storage.
+`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, `0.2.5` added Authentication Platform v2, `0.2.6` added Authorization & Security v2, `0.2.7` added Observability Platform v2, `0.2.8` added Background Jobs Platform, and `0.2.9` adds recurring interval/UTC-cron scheduling with lease-aware shared-store contracts.
 
 Machine-readable platform contracts:
 
@@ -36,6 +36,7 @@ docs/api-manifest.json
 | Request security | Same-origin validation and signed CSRF tokens for unsafe mutations |
 | Middleware | Middleware System v2 with onion execution |
 | Background jobs | Adapter contract, in-memory queue, delayed jobs, retries/backoff, cancellation and concurrent workers |
+| Scheduling | Recurring interval jobs, UTC cron, schedule-store leases and deterministic scheduled run IDs |
 | Observability | Structured logs, counters/gauges/histograms, Prometheus output, request metrics and health/readiness checks |
 | Validation | Typed validators and structured validation errors |
 | Error handling | HTTP error helpers and consistent error responses |
@@ -274,24 +275,6 @@ import {
     authorize,
     defineAuthorizationPolicy,
 } from "bcp/auth";
-
-const updateProject =
-    defineAuthorizationPolicy(
-        ({
-            user,
-            resource,
-        }) =>
-            resource.ownerId ===
-            user.id
-    );
-
-await authorize(
-    updateProject,
-    {
-        user,
-        resource: project,
-    }
-);
 ```
 
 Request-security helpers are exposed from `bcp/server`:
@@ -308,48 +291,12 @@ Read more: [Authorization & Security v2](docs/authorization-security.md)
 
 ## Observability Platform v2 — 0.2.7
 
-Create one application metrics registry:
-
 ```ts
 import {
+    createHealthRegistry,
     createMetricsRegistry,
-} from "bcp/observability";
-
-export const metrics =
-    createMetricsRegistry();
-```
-
-Supported metric types:
-
-```text
-counter
-gauge
-histogram
-```
-
-Expose Prometheus-compatible text:
-
-```ts
-import {
     createMetricsResponse,
 } from "bcp/observability";
-
-export function GET() {
-    return createMetricsResponse(
-        metrics
-    );
-}
-```
-
-Health/readiness registry:
-
-```ts
-import {
-    createHealthRegistry,
-} from "bcp/observability";
-
-export const health =
-    createHealthRegistry();
 ```
 
 Read more: [Observability Platform v2](docs/observability.md)
@@ -405,16 +352,75 @@ const worker =
         concurrency: 4,
         pollIntervalMs: 250,
     });
+```
 
-// graceful shutdown
-await worker.stop();
+The default memory adapter is process-local. Durable multi-process deployments should implement `JobQueueAdapter` against shared infrastructure.
+
+Read more: [Background Jobs Platform](docs/background-jobs.md)
+
+## Job Scheduling Platform — 0.2.9
+
+Create a scheduler on top of the same queue:
+
+```ts
+import {
+    createJobScheduler,
+} from "bcp/jobs";
+
+export const scheduler =
+    createJobScheduler({
+        queue: jobs,
+    });
 ```
 
-The default in-memory adapter is process-local and is intended for development/tests/prototypes. Durable multi-process deployments should implement `JobQueueAdapter` against shared infrastructure. Adapter `reserve()` must atomically claim work.
+Interval schedule:
+
+```ts
+await scheduler.schedule(
+    "cache.cleanup",
+    {},
+    {
+        id: "cache-cleanup",
+        everyMs: 5 * 60 * 1000,
+    }
+);
+```
 
-Retry behavior is configurable with fixed or callback-based backoff. The default is capped exponential backoff. Jobs can also be cancelled and inspected with `get()` / `list()`.
+UTC cron schedule:
 
-Read more: [Background Jobs Platform](docs/background-jobs.md)
+```ts
+await scheduler.schedule(
+    "report.weekday",
+    {},
+    {
+        cron: "30 9 * * 1-5",
+    }
+);
+```
+
+Supported cron shape:
+
+```text
+minute hour day-of-month month day-of-week
+```
+
+The scheduler runner polls due schedules and enqueues normal BCP jobs:
+
+```ts
+const scheduleRunner =
+    scheduler.start({
+        pollIntervalMs: 1_000,
+        leaseMs: 30_000,
+    });
+
+// graceful shutdown
+await scheduleRunner.stop();
+await scheduler.close();
+```
+
+The built-in `createMemoryJobScheduleStore()` is process-local. Multi-instance production deployments should implement a shared `JobScheduleStore` whose `acquireDue()` operation atomically claims schedules with lease ownership/expiry. Scheduled occurrences also use deterministic queue ids for duplicate protection.
+
+Read more: [Job Scheduling Platform](docs/job-scheduling.md)
 
 ## Public entrypoints
 
@@ -495,7 +501,7 @@ React SSR
 Hydration / SPA navigation
 
 Operational side channels:
-background jobs + structured logs + metrics + health/readiness
+background jobs + scheduler + structured logs + metrics + health/readiness
 ```
 
 ## Production build
@@ -541,7 +547,7 @@ npm run test:e2e
 npm run rc:check
 ```
 
-`0.2.8` adds Background Jobs Platform unit and prepared-package smoke checks covering delayed work, retries/backoff, cancellation, worker concurrency, server-only boundaries and the public `bcp/jobs` package surface.
+`0.2.9` adds Job Scheduling Platform unit and prepared-package smoke checks covering interval schedules, UTC cron parsing, standard day matching, schedule-store leases, deterministic scheduled run ids, retry propagation and lifecycle validation.
 
 Do not tag or publish until the final release commit passes the complete RC sequence.
 
@@ -564,12 +570,13 @@ Do not tag or publish until the final release commit passes the complete RC sequ
 | `0.2.6` | Authorization & Security v2 |
 | `0.2.7` | Observability Platform v2 |
 | `0.2.8` | Background Jobs Platform |
+| `0.2.9` | Job Scheduling Platform |
 
 ## Roadmap
 
-`0.2.8 — Background Jobs Platform` establishes a provider-neutral queue/worker contract on top of the existing server runtime and lifecycle model.
+`0.2.9 — Job Scheduling Platform` establishes recurring scheduling and the durable schedule-store contract on top of the provider-neutral queue introduced in `0.2.8`.
 
-Later `0.2.x` work can add durable queue providers, recurring schedules, distributed leases or workflow orchestration without changing the base enqueue/worker contract. Native `.exe`, desktop and mobile compilation remain later roadmap work.
+Future work can add first-party durable queue/schedule adapters, dead-letter queues or workflow orchestration without changing the base queue and scheduler contracts. Native `.exe`, desktop and mobile compilation remain later roadmap work.
 
 ## License
 

package/docs/README.md

@@ -2,7 +2,7 @@
 
 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.8 — Background Jobs Platform`
+> **Documentation target:** BCP Framework `0.2.9 — Job Scheduling Platform`
 >
 > **Release state:** unreleased development target until RC validation, tagging and npm publication complete.
 
@@ -21,24 +21,6 @@ docs/api-manifest.json
   -> public package entrypoints, source ownership and guide mapping
 ```
 
-Markdown files under `docs/` remain the authored documentation content.
-
-Recommended flow:
-
-```text
-framework source/tests
-        ↓
-      docs/
-        ├─ Markdown content
-        ├─ docs-web-manifest.json
-        ├─ platform-manifest.json
-        └─ api-manifest.json
-        ↓
-manifest-driven sync
-        ↓
-    bcp-docs-web
-```
-
 Framework source and tests remain authoritative for runtime behavior.
 
 ## Current 0.2.x milestones
@@ -54,49 +36,52 @@ Framework source and tests remain authoritative for runtime behavior.
 | `0.2.6` | Authorization & Security v2 |
 | `0.2.7` | Observability Platform v2 |
 | `0.2.8` | Background Jobs Platform |
+| `0.2.9` | Job Scheduling Platform |
 
-## 0.2.8 — Background Jobs Platform
+## 0.2.9 — Job Scheduling Platform
 
-`0.2.8` adds a server-only provider-neutral queue/worker layer without adding a third-party queue dependency.
+`0.2.9` extends `bcp/jobs` with recurring interval jobs, dependency-free UTC cron schedules, scheduler runners, deterministic scheduled occurrence IDs and a lease-aware `JobScheduleStore` contract.
 
 New/updated documentation sources:
 
 | Source | Purpose |
 | --- | --- |
-| `background-jobs.md` | Queue contract, memory adapter, delay, retries, workers and production guidance |
-| `api-reference.md` | Public `bcp/jobs` exports |
-| `platform-manifest.json` | Background Jobs capability flags and public entrypoint |
+| `background-jobs.md` | Base queue/worker contract from `0.2.8` |
+| `job-scheduling.md` | Interval/cron schedules, leases and durable schedule-store guidance |
+| `api-reference.md` | Public queue + scheduler APIs under `bcp/jobs` |
+| `platform-manifest.json` | Job Scheduling capability flags |
 | `api-manifest.json` | `bcp/jobs` guide ownership |
-| `docs-web-manifest.json` | Background Jobs navigation and `0.2.8` release route |
-| `releases/0.2.8.md` | Background Jobs Platform release notes |
+| `docs-web-manifest.json` | Scheduling navigation and `0.2.9` release route |
+| `releases/0.2.9.md` | Job Scheduling Platform release notes |
 
-Primary APIs:
+Primary scheduling APIs:
 
 ```ts
 import {
-    createJobQueue,
-    createMemoryJobQueueAdapter,
+    createJobScheduler,
+    createMemoryJobScheduleStore,
+    nextCronTime,
+    nextScheduleTime,
 } from "bcp/jobs";
 ```
 
 Runtime model:
 
 ```text
-web/API/action
+recurring schedule
     |
-    | enqueue
     v
-JobQueueAdapter
+JobScheduleStore.acquireDue()
     |
+    | lease + deterministic run id
     v
-worker loop(s)
+JobQueueAdapter.enqueue()
     |
-    +-> success
-    +-> retry/backoff
-    +-> failed/cancelled
+    v
+queue worker(s)
 ```
 
-The built-in memory adapter is process-local and not durable. Multi-process/container production deployments should implement `JobQueueAdapter` against shared durable infrastructure.
+The built-in schedule store and queue are process-local. Multi-process/container production deployments should implement shared durable `JobScheduleStore` and `JobQueueAdapter` contracts.
 
 ## Update rule
 
@@ -115,21 +100,6 @@ When framework behavior or public surface changes:
 
 `docs/docs-web-manifest.json` is the authoritative ordered navigation contract.
 
-Current sections:
-
-```text
-Getting Started
-Routing & Data
-Authentication & Authorization
-Database
-Runtime & Infrastructure
-Storage & Uploads
-Developer Experience
-Platform & Compatibility
-API Reference
-Releases
-```
-
 Important current routes:
 
 | Website route | Markdown source |
@@ -138,40 +108,17 @@ Important current routes:
 | `/docs/authorization-security` | `authorization-security.md` |
 | `/docs/observability` | `observability.md` |
 | `/docs/background-jobs` | `background-jobs.md` |
-| `/docs/development-logging` | `development-logging.md` |
+| `/docs/job-scheduling` | `job-scheduling.md` |
 | `/docs/application-packaging` | `application-packaging.md` |
 | `/docs/database` | `database.md` |
 | `/docs/api-reference` | `api-reference.md` |
-| `/releases/0.2.8` | `releases/0.2.8.md` |
+| `/releases/0.2.9` | `releases/0.2.9.md` |
 
 Every route/source pair is validated by unit tests.
 
-## Platform manifest
-
-`docs/platform-manifest.json` describes:
-
-```text
-framework version/release state
-Node/React/runtime baseline
-production build/package target
-public package entrypoints
-CLI command families
-capability flags
-previous-baseline compatibility intent
-documentation contract files
-```
+## Public entrypoints
 
-The supported production target remains:
-
-```text
-standalone-node
-```
-
-## API manifest
-
-`docs/api-manifest.json` describes public package entrypoints documentation tooling may present as supported APIs.
-
-Current entrypoints:
+Current documented entrypoints:
 
 ```text
 bcp
@@ -191,39 +138,9 @@ bcp/middleware
 
 The API-manifest entrypoint set must match the platform public-entrypoint set exactly.
 
-## bcp-docs-web synchronization
-
-The docs website sync loads the manifests before Markdown content:
-
-```text
-selected framework ref
-        ↓
-docs-web-manifest.json
-platform-manifest.json
-api-manifest.json
-        ↓
-validate version/release/API parity
-        ↓
-load referenced Markdown
-        ↓
-synchronize CMS/search/navigation
-```
-
-## Source conventions
-
-- one H1 per Markdown page,
-- stable heading hierarchy,
-- fenced code blocks with language tags,
-- relative links between docs,
-- exact public API names,
-- clear stable/RC/roadmap labels,
-- security limitations next to affected APIs,
-- no framework-internal module presented as public API,
-- no secrets/runtime `.env` values in public documentation metadata.
-
 ## Release validation
 
-Before publishing `0.2.8`:
+Before publishing `0.2.9`:
 
 ```bash
 npm run typecheck
@@ -234,15 +151,16 @@ npm run test:e2e
 npm run rc:check
 ```
 
-Background Jobs Platform validation covers:
+Job Scheduling Platform validation covers:
 
-- immediate and delayed jobs,
-- retry/backoff behavior,
-- terminal success/failure/cancellation states,
-- duplicate job IDs,
-- worker concurrency and graceful stop,
-- public `bcp/jobs` exports,
-- server-only browser/client boundaries,
+- interval scheduling,
+- five-field UTC cron parsing,
+- standard day-of-month/day-of-week behavior,
+- schedule-store leasing,
+- deterministic scheduled run IDs,
+- retry-limit propagation into queue jobs,
+- schedule inspection/removal,
+- scheduler configuration validation,
 - prepared npm package contents,
 - docs/platform/API version parity.
 
@@ -250,17 +168,4 @@ The final release tag must point to the exact commit that passed the complete RC
 
 ## Repository authority
 
-The framework repository remains authoritative for:
-
-```text
-source
-public exports
-tests
-Markdown docs
-docs-web manifest
-platform manifest
-API manifest
-release notes
-```
-
-`bcp-docs-web` remains the presentation/search/navigation layer for this content.
+The framework repository remains authoritative for source, public exports, tests, Markdown docs, manifests and release notes. `bcp-docs-web` remains the presentation/search/navigation layer.

package/docs/api-manifest.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "framework": "bcp",
-  "version": "0.2.8",
+  "version": "0.2.9",
   "releaseState": "unreleased",
   "coverage": "public-entrypoints",
   "entrypoints": [
@@ -99,9 +99,10 @@
       "source": "packages/client/src/jobs.ts",
       "environment": "server",
       "route": "/docs/api-reference#bcp-jobs",
-      "summary": "Background job queue contract with in-memory adapter, delayed jobs, retry/backoff, cancellation and concurrent workers.",
+      "summary": "Background job queues plus recurring interval/cron scheduling, schedule-store leases and worker lifecycle APIs.",
       "guides": [
         "/docs/background-jobs",
+        "/docs/job-scheduling",
         "/docs/observability"
       ]
     },