@mercury-fw/cli 0.36.0 → 0.37.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @mercury-fw/cli
 
+## 0.37.0
+
+### Minor Changes
+
+- fbaa7aa: The admin panel is gone.
+
+  - Breaking, `@mercury-fw/core`: `composeMercury` no longer returns `startAdmin`, and `ADMIN_PANEL_ENABLED`/`ADMIN_PANEL_PORT` do nothing. An existing app removes the two lines of its `src/index.ts` that start and stop it (`const adminServer = app.startAdmin();` and `adminServer?.stop();`).
+  - New apps don't start it.
+  - What it showed is in the HTTP surface's read routes, scoped to the caller, and in `mfw vault` / `mfw memory` for the operator.
+
+### Patch Changes
+
+- Updated dependencies [fbaa7aa]
+  - @mercury-fw/core@0.37.0
+  - @mercury-fw/utils@0.37.0
+
 ## 0.36.0
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mercury-fw/cli",
-  "version": "0.36.0",
+  "version": "0.37.0",
   "type": "module",
   "license": "MIT",
   "repository": {
@@ -41,8 +41,8 @@
   "comment:shape": "The Mercury CLI (`mfw`). `mfw create <dir>` writes a new Mercury app from the template. The framework packages move in lockstep with it, so a new app gets them at the CLI's own version; plugins and channels at the registry's latest. The plugin and channel packages are devDependencies only for the catalog test. `main(argv)` is exported for create-mercury-agent.",
   "dependencies": {
     "@clack/prompts": "^1.8.1",
-    "@mercury-fw/core": "0.36.0",
-    "@mercury-fw/utils": "0.36.0",
+    "@mercury-fw/core": "0.37.0",
+    "@mercury-fw/utils": "0.37.0",
     "commander": "^15.0.0"
   },
   "devDependencies": {
@@ -50,7 +50,7 @@
     "@mercury-fw/channel-http": "0.4.0",
     "@mercury-fw/auth-oidc": "0.1.0",
     "@mercury-fw/auth-static": "0.1.0",
-    "@mercury-fw/formatter": "0.36.0",
+    "@mercury-fw/formatter": "0.37.0",
     "@mercury-fw/plugin-atlassian-admin": "0.1.2",
     "@mercury-fw/plugin-bitbucket": "0.1.2",
     "@mercury-fw/plugin-jira": "0.4.3",

package/template/src/index.ts.tpl

@@ -1,7 +1,7 @@
 /**
  * Service entrypoint: builds the app with `composeMercury`, fed
  * `mercury.config.ts`, and starts what a long-running service runs: the
- * declared channels, the admin panel (when enabled) and the memory crons.
+ * declared channels and the memory crons.
  * Headless; the interactive terminal is `bun run repl` (`repl.ts`).
  *
  * Stays alive on the channels' background resources and the cron intervals,
@@ -18,7 +18,6 @@ for (const { name, provider } of loadedChannels) {
   console.error(`[channel] ${name} started`);
 }
 
-const adminServer = app.startAdmin();
 const crons = app.startCrons();
 console.error("[service] up — channels and crons started; waiting for SIGINT/SIGTERM");
 
@@ -31,7 +30,6 @@ async function shutdown(signal: string): Promise<void> {
   shuttingDown = true;
   console.error(`[shutdown] ${signal} received, releasing subsystems`);
   crons.stop();
-  adminServer?.stop();
   for (const { name, provider } of loadedChannels) {
     await provider.stop?.();
     console.error(`[shutdown] channel ${name} stopped`);

package/template/src/repl.ts.tpl

@@ -1,8 +1,8 @@
 /**
  * Dev REPL entrypoint (`bun run repl`): boots the same app the service runs and
  * opens an interactive terminal on it. For trying things out and debugging, not
- * a channel: no user identity (nothing goes to per-user memory), no channels,
- * crons or admin panel.
+ * a channel: no user identity (nothing goes to per-user memory), no channels
+ * or crons.
  */
 import { composeMercury, createTerminalProvider } from "@mercury-fw/core";
 import mercuryConfig from "../mercury.config.ts";