One durable reviewer journey
Seeded roles execute ordinary sessions through draft, review, immutable publication, public preview, suggestion apply, and bounded reset.
Flagship · Full-stack product engineering
2.0 release candidate · external gates pendingAutoBlog CMS
A repository-complete editorial release candidate built around database sessions, workspace authorization, immutable revisions, conflict-safe editing, durable jobs, and bounded media/AI operations.
Engineering thesis
A credible CMS is a workflow system.
The flagship journey spans authenticated access, workspace-derived policy, drafting, immutable revisions, optimistic concurrency, review, publication, and recovery. AI assistance and media processing are protected external failure domains rather than privileged shortcuts.
The same application logic must serve local review, automated tests, and configured deployment environments.
Verified candidate evidence
What the repository proves
Session-derived authorization
Five-role RBAC, workspace isolation, origin checks, quotas, negative route tests, and constrained media boundaries.
Revision and concurrency semantics
Append-only history, optimistic version preconditions, HTTP 409 conflicts, leased publication jobs, and idempotent recovery.
Measured application surface
19 unit, 25 integration, 10 E2E, 6 accessibility, 5 visual, 2 performance tests, and 6 Lighthouse reports.
Release boundary
Repository complete; public release externally gated.
- Historical MongoDB, Cloudinary, and Gemini credentials require provider-owner rotation before v2 release.
- The public runtime still requires durable remote libSQL, a one-minute scheduler, unique secrets, and anonymous demo access.
- The protected candidate remains draft PR #3; no hosted v2, release, or production-readiness claim is promoted prematurely.