Skip to content

Tracker: Post-session review findings + commit plan (2026-05-27) #522

@tayebmokni

Description

@tayebmokni

Context

A long admin-sweep session (2026-05-27) found and partially fixed dozens of bugs while signing in as `admin@dextra.com` and walking every admin page. A subsequent multi-agent code review found regressions in the work itself plus a deeper architectural gap (the public site at `apps/web` is a hardcoded marketing landing — not driven by admin config).

This tracker organizes the follow-up work. Do REVERTs first; the regressions are security-sensitive.

REVERT first

FIX-FORWARD (in order)

Verdict on "is this a CMS yet?"

From the multi-agent review: NO. Public marketing site is fully hardcoded React. Admin Settings tab persists nothing (`/api/v1/settings` returns 404). Only the `[...slug]` post route flows admin → public.

P0 path forward in ~one week: items #495#502 + #505#506 = stack functions as a basic CMS.
P0+P1 in ~two weeks: + #508#513 = admin config actually drives the public site.

"If you had ONE WEEK, ship the P0 list. If two weeks, P0+P1. Beyond that, this isn't shippable to a paying user yet."

Metadata

Metadata

Assignees

No one assigned

    Labels

    phase:P1-cms-corePhase 1 — CMS Corepriority:P0Critical — blocks the phasetype:designArchitectural discussion or ADR

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions