Plugin Status

The current production build does not expose plugin capabilities. The Worker rejects /api/plugins/*, the control panel has no plugin upload entry, and GET /api/v1 does not advertise a plugin runtime.

Working Alternatives

• Adjust the original status page visuals only: develop a CSS theme.
• Fully rewrite the public page layout: develop a Canvas theme.
• Provide an extra panel on a separate domain: build an alternate frontend against the public v1 API and have the deployer configure an exact DEVELOPER_API_ORIGINS allowlist.

Do not build or distribute type: "plugin" ZIPs, and do not rely on /api/plugins/upload, plugin manifests or plugin message protocols from older tutorials; those interfaces were never part of current production capabilities.

An old nstatus-extension-v1 schema in a theme manifest or the legacy x-extension-sha256 upload header does not imply plugin support either. The Worker still requires type: "theme", and Canvas themes can only declare status:read.

Alternate frontends only read the credential-free public API. Do not ask for admin sessions, passwords, TOTP, the Agent master token or node scoped tokens, and do not accept executable script uploads.