@zerotal/monitor 1.8.0 → 1.9.0

package/CHANGELOG.md

@@ -8,6 +8,28 @@ follows the Zerotal monorepo's unified versioning.
 
 ## [Unreleased]
 
+## [1.9.0] — 2026-08-29
+
+### Added
+
+- **The snapshot shape is documented.** **Export JSON** hands you a `MonitorSnapshot` — the whole
+  panel for a range, as data — and none of the forty-odd row types it is built from was named
+  anywhere. `docs/monitor.md` now maps every field to its row type, which is what you need to
+  post one somewhere, diff two of them, or drive an alerting integration off it rather than off
+  the built-in thresholds.
+
+- **Section contributions can be typed.** `MonitorSection`, `MonitorSectionData`, `MonitorStat`,
+  `MonitorTable`, `MonitorTableColumn` and `MonitorRow` are documented. Declaring the host's
+  shape locally stays the recommended path — it is what keeps a contributing package free of any
+  dependency on the monitor — but a large `resolve` is better served by a typo in a column key
+  being a compile error than a blank cell.
+
+### Changed
+
+- **INTERNAL: `MonitorLayout`, `MonitorPage` and `MonitorPanelHost` are marked `@internal`.**
+  The panel's own shell. Still exported, still working; a contributor pushes a section into the
+  host binding rather than constructing any of them.
+
 ## [1.6.0] — 2026-08-15
 
 ### Fixed

package/api-surface.md

@@ -314,11 +314,6 @@ interface MonitorConfigShape = {
   zerotalVersion?: string
 }
 
-interface MonitorPanelHost = {
-  enabled: (id: string) => boolean
-  section: (section: MonitorSection) => void
-}
-
 interface MonitorSection = {
   group?: string
   icon?: string

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zerotal/monitor",
-  "version": "1.8.0",
+  "version": "1.9.0",
   "license": "MIT",
   "maturity": "stable",
   "private": false,
@@ -30,14 +30,14 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@zerotal/core": "1.8.0",
-    "@zerotal/flow-ui": "1.8.0",
-    "@zerotal/flow": "1.8.0"
+    "@zerotal/core": "1.9.0",
+    "@zerotal/flow-ui": "1.9.0",
+    "@zerotal/flow": "1.9.0"
   },
   "devDependencies": {
-    "@zerotal/queue": "1.8.0",
-    "@zerotal/scheduler": "1.8.0",
-    "@zerotal/telemetry": "1.8.0"
+    "@zerotal/queue": "1.9.0",
+    "@zerotal/scheduler": "1.9.0",
+    "@zerotal/telemetry": "1.9.0"
   },
   "peerDependencies": {
     "@zerotal/queue": "^1.0.0",

package/src/panel.ts

@@ -99,6 +99,8 @@ export interface MonitorSection {
  *
  * Contributors should declare their own minimal copy of the members they use
  * rather than importing this type, so they depend on this package not at all.
+ *
+ * @internal
  */
 export interface MonitorPanelHost {
   /**

package/src/ui/MonitorLayout.tsx

@@ -31,6 +31,7 @@ const MONITOR_TOKENS = `
 }
 `.trim();
 
+/** @internal */
 export class MonitorLayout extends Layout {
   static override get head(): string {
     return flowUiHead("Zerotal · Monitor", { tokensCss: MONITOR_TOKENS });

package/src/ui/MonitorPage.tsx

@@ -121,6 +121,8 @@ const FEED_PER_PAGE = 12;
  * `super-panel.html` built on Flow. Eight tabs (Overview, Requests,
  * Exceptions, Queues, Mail, Database, Cache, System) render from a live
  * {@link MonitorSnapshot}; interactions round-trip over the Flow WebSocket.
+ *
+ * @internal
  */
 export class MonitorPage extends Component {
   static layout = MonitorLayout;