@microteia/console 2.23.0 → 2.24.0

package/CONSOLE-VERSIONS.md

@@ -22,6 +22,10 @@
 - fix(command): what was broken, and what it did to whoever hit it.
 -->
 
+#### [2.24.0] — 2026-10-07
+
+- feat(export-catalog): each screen in `installed-catalog.json` now carries its `sourceId`. The snapshot only had the installed key, which may have been disambiguated on install, so an extension that adds a tab to another's record detail (`record:<sourceId>`) could not be checked against the installation. Older snapshots simply lack the field.
+
 #### [2.23.0] — 2026-10-07
 
 - fix(provision): `microteia provision` run on its own now probes the deployed stamps itself instead of concluding that nothing changed. It could only compare stamps with the map `deploy` hands it, and running alone — the path of anyone who has just swapped kernels with `unpack` — there was no map: `outdatedByStamp` drew no conclusion, the function stayed out of the queue, and the record said "applied" because it genuinely was running, from the previous package. An office upgraded this way kept serving an extension's old Cloud Function with nothing anywhere saying so; the symptom surfaced in the client, not in the Console. The queue is now everything the installed extensions claim, and `deployFunctionsThatChanged` — the same probe `deploy` uses — decides what actually goes up: one reference function per stamp, and the rest left alone when it comes back unchanged. What the probe skips counts as satisfied, or a complete installation would stay "pending" forever.

package/README.md

@@ -1,4 +1,4 @@
-# Microteia Console 2.23.0
+# Microteia Console 2.24.0
 
 Installs and updates Microteia in a Firebase project you own. It has no npm dependencies of its own —
 what it needs are command-line tools that are already on the machine, listed at the bottom.

package/lib/console/exportCatalog.d.ts

@@ -58,6 +58,11 @@ export interface CatalogFieldExport {
 }
 export interface CatalogScreenExport {
     key: string;
+    /**
+     * O id UNIVERSAL da tela. A chave acima é a instalada, que pode ter sido desambiguada; é pelo
+     * `sourceId` que uma extensão endereça a tela de outra (`record:<sourceId>`).
+     */
+    sourceId?: string;
     collection?: string;
     titleSingular: string;
     titlePlural?: string;

package/lib/console/exportCatalog.js

@@ -121,6 +121,7 @@ const screenExport = (document) => {
     const fields = Array.isArray(data.fields) ? data.fields : [];
     return {
         key: document.id,
+        ...(text(data.sourceId) === undefined ? {} : { sourceId: text(data.sourceId) }),
         ...(text(data.dataCollection) === undefined ? {} : { collection: text(data.dataCollection) }),
         titleSingular: text(data.titleSingular) ?? document.id,
         ...(text(data.titlePlural) === undefined ? {} : { titlePlural: text(data.titlePlural) }),

package/lib/shared/paths.d.ts

@@ -87,4 +87,4 @@ export declare const consoleRoot: string;
  * de código nunca chegou a quem instala. Este bloco fica sendo o que ele já era antes de crescer: a
  * política de semver da ferramenta, mais o registro do que motivou as versões até a `2.5.0`.
  */
-export declare const CLI_VERSION = "2.23.0";
+export declare const CLI_VERSION = "2.24.0";

package/lib/shared/paths.js

@@ -94,4 +94,4 @@ export const consoleRoot = resolve(here, '..', '..');
  * de código nunca chegou a quem instala. Este bloco fica sendo o que ele já era antes de crescer: a
  * política de semver da ferramenta, mais o registro do que motivou as versões até a `2.5.0`.
  */
-export const CLI_VERSION = '2.23.0';
+export const CLI_VERSION = '2.24.0';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@microteia/console",
-  "version": "2.23.0",
+  "version": "2.24.0",
   "description": "Install and update Microteia in a Firebase project you own.",
   "license": "UNLICENSED",
   "type": "module",