Phase 2 beta verification — 2026-08-23

Beta runs merge commit 83eecba1

• Check 1. Backend deployment for 83eecba1 succeeded and is the active Cloud Run revision.
• Check 2. Frontend deployment for the same commit is ACTIVE with all five components healthy.

SP-609 — De-branded tenant shell

A single static bundle must serve every tenant, with no SkillPixel branding baked into the served HTML.

• Check 3. curl https://historyclass.beta.skillpixel.vn/ returns the tenant-neutral static shell. The served document carries the HTML comment “Tenant-neutral: one bundle serves every tenant…” and contains zero case-insensitive matches for “SkillPixel”.
• Check 4. The runbook browser console check on the rendered page returns tenant-specific metadata with no SkillPixel body text:

  {
    "title": "HistoryClass - Nền tảng học tập",
    "description": "Khám phá các khoá học được xuất bản bởi HistoryClass.",
    "ogSiteName": "HistoryClass",
    "hasSkillPixelBodyText": false
  }

SP-557 — Banner management

• Check 5. GET /api/v1/banners with header X-Tenant-Host: beta.skillpixel.vn returns 200.
• Check 6. GET /api/v1/banners/admin with a platform-admin token returns 200.
• The admin surface at /admin/marketing renders the banner list in a clean browser: three banners with active and default badges, together with the add and reorder controls. The screen is also reachable on the HistoryClass host.

SP-610 — Landing strategy from tenant configuration

• Check 7. GET /api/v1/tenant/bootstrap with X-Tenant-Host: historyclass.beta.skillpixel.vn returns 200:

  {
    "slug": "historyclass",
    "is_default": false,
    "landing_strategy": null,
    "seo.site_name": "HistoryClass"
  }

• Check 8. Default-tenant bootstrap with X-Tenant-Host: beta.skillpixel.vn returns 200 with is_default: true and site name SkillPixel.
• Check 9. An unknown host returns 400.
• Check 10. The default landing page is unchanged.

Observation O1. No landing.strategy platform-config entry exists on beta for HistoryClass: GET /platform/config/effective returns null. The frontend therefore uses its deterministic fallback, under which non-default tenants render shared-template. This behaviour is correct by design. The product decision — a bespoke historyclass page versus the shared template — remains open, and either outcome requires an explicit configuration row.

SP-611 — Shared landing template

• The HistoryClass landing page renders the hero with the title “HistoryClass” and the call to action “Khám phá khoá học”, a featured-courses section containing three courses, a tenant-branded header and footer, and the brown theme colours drawn from the tenant branding record. Desktop and mobile evidence appear in figures 01 and 02.
• The announcement block is not configured on beta — the tenants.landing JSON contains no announcement — so no announcement is shown. This is the expected result.

SP-476 — Managed subdomain activation gate

• Check 11. A throwaway tenant gate-check-beta-verify was created via POST /platform/tenants/ → 201, status PROVISIONED.
• Check 12. PATCH of the status to ACTIVE returns 409 and enumerates every missing prerequisite rather than only the first:

  Tenant cannot be activated: an active or verified managed
  subdomain is required; a tenant admin membership is required

• Check 13. The throwaway tenant was deleted afterwards via DELETE with the confirmation slug → 204.
• HistoryClass itself has been ACTIVE since 2026-07-16, from the earlier rehearsal, with an ACTIVE and verified primary managed subdomain historyclass.beta.skillpixel.vn. The domain serves correctly over HTTPS through Cloudflare.

SP-612 — Staff invitations backend

All checks were executed against tenant HistoryClass, 7c1e9f42-3b6a-4d58-9e10-2f4c8a7b5d31.

• Check 14. POST invitation for npkhang99@gmail.com with role INSTRUCTOR returns 201, status PENDING, expiry 2026-08-29 (seven days). The response carries the one-time token.
• Check 15. A duplicate invitation for the same address returns 409, “A pending invitation already exists for this email”.
• Check 16. POST invitation for curoa99@gmail.com with role STUDENT returns 201.
• Check 17. Revoking that invitation returns 200 with status REVOKED.
• Check 18. Accepting with a bogus token returns 404, “Invitation not found”.
• Check 19. Accepting the revoked token returns 409, “Invitation has been revoked”.
• Check 20. Accepting the valid token while signed in as the invitee npkhang99@gmail.com returns 200 with status ACCEPTED. The platform membership list then shows npkhang99@gmail.com with exactly ["INSTRUCTOR"], and /users/me on the HistoryClass host returns tenant_roles: ["INSTRUCTOR"].
• Invitation e-mail delivery is fire-and-forget after commit, with failures logged. Missing e-mail infrastructure — Phase 3, SP-614 — therefore cannot fail the API. This matches the design.

SP-613 — Staff invitations user interface

• Check 21. The tenant-admin screen /admin/invitations on HistoryClass shows the sidebar entry “Lời mời nhân sự”, the invite form with e-mail, role and send, and the table listing curoa99 as REVOKED and npkhang99 as PENDING with resend and revoke actions.
• Check 22. The platform-admin surface — lms-admin staging on Vercel — shows an Invitations tab for tenant HistoryClass listing both invitations with role, status, expiry and inviter, plus a send-invite form.
• Check 23. The accept page in the signed-out state presents a card asking the visitor to sign in, “Đăng nhập để nhận lời mời”.
• Check 24. The accept page, opened while signed in as a different account, shows “Sai tài khoản”, names the signed-in e-mail address, and offers a sign-out-and-switch action.
• Both accept-page states are fully tenant-branded.

No cross-tenant leakage, no errors since the deployment

• Hot tables — courses, chapters, lessons, questions — partition cleanly across the default tenant and HistoryClass. Zero default-tenant rows were created after the deployment cutoff of 2026-08-22T17:30Z.
• tenant_default_fallback_write has zero occurrences in Cloud Run logs over the last seven days. This is the SP-478 Gate C metric. The gate's own seven-day window started 2026-08-20, so the gate completes on 2026-08-27.
• tenant_non_default_request markers are present with the correct tenant identifier and hostname for HistoryClass traffic, on both bootstrap and courses requests.
• Zero Cloud Run log entries at severity ERROR or above since the deployment.

Tenant and domain table state

Two invitation history rows; everything else restored

• HistoryClass invitations. npkhang99@gmail.com remains as an ACCEPTED history row and curoa99@gmail.com as a REVOKED history row. The membership created by the accepted invitation was deleted afterwards, and memberships were restored to the original two administrators.
• Throwaway tenant. gate-check-beta-verify was created for the activation-gate check and deleted afterwards.
• Untouched. No configuration, branding, banner or domain rows were changed.