ServerKit is a lightweight, modern server control panel for managing web applications, databases, and services on your VPS or dedicated server. Built with Python/Flask backend and React frontend.
Python astracloudflarecontrol-panelcyberpaneldnsfablehosting-control-panelhosting-panelkimi-k3server-managementserverkitubuntu-web-panelwebserver
docs: WP extraction complete — core data seam, Tier C status
Juan Denisb159c7a5bdf5
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.mdindex 92bc045a..6686d9f5 100644--- a/docs/ARCHITECTURE.md+++ b/docs/ARCHITECTURE.md@@ -278,7 +278,6 @@ Source lives in this repo under `builtin-extensions/`:| Slug | Class | Notes ||---|---|---|-| `serverkit-wordpress` | Flagship, in-place | Seeded only if the setup wizard selects it || `serverkit-cloudflare-ops` | Flagship, in-place | Route-only, no sidebar entry || `serverkit-ftp` | Copy-installed builtin | Auto-installs on upgrade || `serverkit-cloud-provision` | Copy-installed builtin | Auto-installs on upgrade |@@ -288,6 +287,12 @@ Source lives in this repo under `builtin-extensions/`:| `serverkit-git` | Marketplace one-click | Frontend-only, no backend || `serverkit-localkit` | Marketplace one-click | Backend-only, no frontend |+> `serverkit-wordpress` left the tree in plan 52 Phase 5: it is a standalone+> repo distributed through the registry (like `serverkit-k8s`/`serverkit-tramo`),+> offered during onboarding from the bundled registry index. Its database+> schema stays core forever — the **core data seam** (plan 52 D1, see+> EXTENSIONS.md "Data models & policy").+### Standalone extension reposThese have their own repos and install from the registry as versioned,diff --git a/docs/CORE_SLIM.md b/docs/CORE_SLIM.mdindex 9a6a0cd8..e93f35b6 100644--- a/docs/CORE_SLIM.md+++ b/docs/CORE_SLIM.md@@ -64,14 +64,14 @@ host import map. Anything else a page uses today from `core` (charts via**bundled into the extension** or first **promoted into the SDK**. Workflows(`@xyflow/react`) and any chart-heavy page are the ones this bites.-### Tier C — WordPress (largest, last)--| Extension | Surface | Why last |-|---|---|---|-| `serverkit-wordpress` | `WordPressDetail` + project + sub-tabs (backend already a flagship) | Biggest UI, deep **tab-group** wiring, many sub-components and its own sub-router. Move only after Tier B has proven the tab-group + multi-component migration on `serverkit-git`. |--WordPress backend is already an in-place flagship; the frontend stays core until-Tier B de-risks the tab-group extraction.+### Tier C — WordPress ✅ DONE (plan 52 Phases 4-5, 2026-08-05)++`serverkit-wordpress` is fully extracted: Phase 4 moved the frontend (5 pages,+40 components, 3 SCSS files) into the extension and onto the `serverkit-sdk`+surface; Phase 5 took it out of the tree into the standalone+`serverkit-wordpress` repo as a runtime-ESM bundle (SDK 1.2.0). It distributes+through the registry and is offered during onboarding from the bundled index+entry; its schema stays core via the documented core data seam (D1).## Per-page migration checklistdiff --git a/docs/EXTENSIONS.md b/docs/EXTENSIONS.mdindex 8fcb0263..1f9b5279 100644--- a/docs/EXTENSIONS.md+++ b/docs/EXTENSIONS.md@@ -430,6 +430,28 @@ def register(ctx):semantics); the choice is passed to the `uninstall` hook (`func(plugin, purge=...)`)and, on purge, drops the `ext_<slug>_*` tables.+### The core data seam (extension uses CORE tables)++The `ext_<slug>_*` mechanism is for extension-owned schema. The deliberate+exception — **core data seam** (plan 52 D1) — is an extension whose tables are+core Alembic-managed because they carry live data that predates the extraction+and are entangled with core features. Canonical example: **serverkit-wordpress**+— `WordPressSite`, `WordPressVulnerability`, `WordPressUpdateRun`,+`WordPressReport` live in `app/models/wordpress_site.py` (core migrations own+their lifecycle) and the standalone extension imports them:++```python+from app.models.wordpress_site import WordPressSite+```++Rules of the seam: the extension never creates/migrates those tables (no+`models` entry for them, no `ext_` rename); core never imports the extension —+it reaches it through a lazy bridge (`app.services.wordpress_bridge`) or+`get_installed_extension_attr`, and through registration seams the extension+fills (`core_hooks`). Absent extension = feature absent, gracefully. The same+seam covers `StatusPage`, `Tunnel`/`ExposedService`, and `CloudServer` (owned+by their respective extensions' features but schema-core).+## Background jobs & schedulesDeclare handlers and recurring jobs in the manifest; they wire into the Jobs SDK@@ -456,10 +478,10 @@ boot** while your extension is active (so it must be idempotent):Core keeps the engine; your extension supplies the entry. An extension that isabsent/disabled at boot never registers, so its target types, event types, andtemplate cards simply don't exist — that is the intended graceful degradation-(plan 52 D4), not an error. Reference implementation:-`builtin-extensions/serverkit-wordpress/backend/core_hooks.py` (the-`wordpress_site` backup kind, the `wordpress.*` event types, and the-`wordpress`/`wordpress-external-db` template provider).+(plan 52 D4), not an error. Reference implementation: the `serverkit-wordpress`+repo's `backend/core_hooks.py` (the `wordpress_site` backup kind, the+`wordpress.*` event types, and the `wordpress`/`wordpress-external-db` template+provider).## Config (`config_schema`)diff --git a/docs/EXTRACTION_WORDPRESS_AUDIT.md b/docs/EXTRACTION_WORDPRESS_AUDIT.mdindex 85a95baf..d699816f 100644--- a/docs/EXTRACTION_WORDPRESS_AUDIT.md+++ b/docs/EXTRACTION_WORDPRESS_AUDIT.md@@ -1,27 +1,14 @@# WordPress extraction — boundary audit (Phase 5, #37)-**Status:** Audit complete; **backend extraction (#38) SHIPPED** — the WordPress-backend now lives in `builtin-extensions/serverkit-wordpress/` as a bundled,-default-installed flagship (D4), loaded via an importlib bridge. See the Phase 5-section of `docs/plans/12_EXTENSIONS_PLATFORM_PLAN.md` for the shipped scope and-deviations (models stay core; event-catalog + Fail2ban WP filter kept core as-two-speed items). The **frontend UI has moved into the extension** (plan 52-Phase 4, 2026-08-05): the 5 pages, the `components/wordpress/` tree (40 files)-and the three `wordpress*.scss` stylesheets now live in-`builtin-extensions/serverkit-wordpress/frontend/`, still baked into the host-build via `sync-builtin-frontends.mjs` + the build-time glob (D6 intermediate-state; styles compile through the extension's own module graph, `main.scss`-no longer imports them). Residual core wiring removed: `App.jsx` title-fallbacks and the `sidebarItems.js` preset literals. Deep imports were-rewritten to the `serverkit-sdk` surface (which gained TabGroupLayout, Modal,-ConfirmDialog, Spinner/EmptyState/SkeletonBoundary/Skeleton, the ui/* form-primitives, useConfirm/useTabParam/useTopbarActions, and the format/time-utils); a handful of host-internal imports remain as `@/` alias imports,-safe under the baked glob. Leaving the tree entirely (runtime-ESM bundle) is-Phase 5.-**Verdict:** extractable, but WordPress has **real core hooks** that must be-inverted/guarded first. WordPress ships as a bundled, default-installed,-uninstallable extension (D4) — never a marketplace hunt.+**Status:** ✅ EXTRACTED (plan 52 Phase 5, 2026-08-05). WordPress lives in the+standalone `serverkit-wordpress` repo (backend + runtime-ESM frontend ++extension-owned tests + first-party release pipeline) and distributes through+the registry; the setup wizard offers it from the bundled index entry. Its+schema stays core forever via the documented **core data seam** (D1 — see+EXTENSIONS.md "Data models & policy"). This audit remains as the historical+boundary record.+**Verdict (historical):** extractable, but WordPress had **real core hooks**+that were inverted/guarded first (plan 52 Phase 3, the `core_hooks` seam).---