Home shell productization batch: message center, What's-new on release data, update-reminder & updater popup restyle

apps/web/src/App.tsx

@@ -134,6 +134,7 @@ import {
   listProjects,
   listTemplates,
   deleteTemplate,
+  duplicatePluginAsProject,
   patchProject,
   resolvedWorkspaceContextForWrite,
 } from './state/projects';
@@ -3266,19 +3267,53 @@ function AppInner() {
   } else if (route.kind === 'community') {
     appMain = (
       <CommunityView
-        onRemixTemplate={({ prompt }) => {
-          // Remix drops the user straight into a running project instead of
-          // just prefilling Home's composer: create a project seeded with
-          // this template's prompt (the same auto-send-on-mount path Home's
-          // own submit uses) and navigate into it (keep in sync with the
-          // EntryShell-embedded community tab).
-          void handleCreateProject({
-            name: summarizeProjectNameFromPrompt(prompt) || t('common.untitled'),
-            skillId: null,
-            designSystemId: null,
-            metadata: { kind: 'other', nameSource: 'prompt' },
-            pendingPrompt: prompt,
-          });
+        onRemixTemplate={({ templateId, prompt }) => {
+          // Remix carries the template's PROJECT along, not just its prompt:
+          // duplicate the plugin's example artifact into a fresh project,
+          // seed the composer with the template prompt, then open it on the
+          // copied entry file (keep in sync with the EntryShell-embedded
+          // community tab). Templates without a duplicable artifact fall
+          // back to the old prompt-only project.
+          void (async () => {
+            const name = summarizeProjectNameFromPrompt(prompt) || t('common.untitled');
+            try {
+              // One resolved authority for BOTH requests: the create binds the
+              // copied project to this workspace, and the seed patch is then
+              // authorized against that same binding. A headerless create is
+              // read by the daemon as a legacy caller and leaves the project
+              // bound to no workspace at all, which is what kept remixed
+              // projects out of the member's own 草稿 list.
+              const writeContext = resolvedWorkspaceContextForWrite(workspaceContextState);
+              const result = await duplicatePluginAsProject(templateId, { name }, writeContext);
+              const seeded = await patchProject(
+                result.projectId,
+                { pendingPrompt: prompt },
+                writeContext,
+              );
+              if (!seeded) {
+                // The project itself exists and is bound — only the prompt seed
+                // was refused. Keep the user on it (retrying through the catch
+                // below would leave the copy orphaned and create a second,
+                // empty project) and surface the dropped seed instead of
+                // discarding it silently.
+                console.error('Community remix: could not seed the template prompt.');
+              }
+              navigate({
+                kind: 'project',
+                projectId: result.projectId,
+                conversationId: result.conversationId,
+                fileName: result.relPath,
+              });
+            } catch {
+              await handleCreateProject({
+                name,
+                skillId: null,
+                designSystemId: null,
+                metadata: { kind: 'other', nameSource: 'prompt' },
+                pendingPrompt: prompt,
+              });
+            }
+          })();
         }}
         onUsePrompt={(prompt) => {
           // Seed the Home composer with the template's starting prompt, then hand