From 9460f01c976c555081ba4e10345904721ff505a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Padez?= Date: Fri, 21 Aug 2026 03:39:01 +0000 Subject: [PATCH] the frontend convention is panels.ts and layout.ts, not Router.tsx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The reference plugin named web/Router.tsx as the way to ship a frontend. Discovery checks for web/panels.ts and web/layout.ts by those exact names and refuses a web/ directory missing either — so anyone following the example would have written a plugin the platform rejects. Co-Authored-By: Claude Opus 5 --- manifest.ts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/manifest.ts b/manifest.ts index 26ded1e..1076bc0 100644 --- a/manifest.ts +++ b/manifest.ts @@ -9,7 +9,8 @@ import type { PluginManifest } from '@@/plugins/manifest'; // api/router.ts exports `router`; mounted at /api/example // db/schema.ts tables, if it had any (every name prefixed `example_`) // sidecar/index.ts a process, if it needed one (.mjs instead means node) -// web/Router.tsx a frontend, if it had one +// web/panels.ts panels, if it had a frontend — REQUIRED with web/, and checked by name +// web/layout.ts how they are arranged — also required with web/ // // `appName` is not declared anywhere: it is the directory name, so the id cannot disagree with where the // code sits.