@microteia/console 2.7.2 → 2.10.0

package/lib/index.js

@@ -10,6 +10,7 @@ import { connect } from './console/connect.js';
 import { unpack } from './console/unpack.js';
 import { deploy } from './console/deploy.js';
 import { provision } from './console/provision.js';
+import { exportCatalog } from './console/exportCatalog.js';
 import { pluginInit } from './console/pluginWorkspace.js';
 import { versionReport } from './console/versions.js';
 import { newerThan } from './console/channel.js';
@@ -37,18 +38,25 @@ const COMMANDS = [
     },
     {
         name: 'deploy',
-        usage: 'microteia deploy [--only rules,indexes,functions,hosting] [--delay <seconds>] [--prune]',
+        usage: 'microteia deploy [--only rules,indexes,functions,hosting] [--delay <seconds>] [--prune] [--all]',
         summary: 'Publish the package that is in place to the connected Firebase project.',
         audience: 'office',
         execute: deploy,
     },
     {
         name: 'provision',
-        usage: 'microteia provision [--prune] [--delay <seconds>]',
+        usage: 'microteia provision [--prune] [--delay <seconds>] [--all]',
         summary: 'Give the installed extensions the Cloud Functions and indexes they ask for.',
         audience: 'office',
         execute: provision,
     },
+    {
+        name: 'export-catalog',
+        usage: 'microteia export-catalog --tenant <tenantId> [--output <path>]',
+        summary: 'Write what an office has — screens, lists, extensions — for the authoring tools to read.',
+        audience: 'office',
+        execute: exportCatalog,
+    },
     {
         name: 'plugin-init',
         usage: 'microteia plugin-init [--dir <path>] [--force]',

package/lib/kernel/manifest.d.ts

@@ -44,6 +44,16 @@ export interface KernelManifest {
     baselineIndexes: FirestoreIndexSpec[];
     /** Ausente nos pacotes anteriores a 7.51.0, que não conheciam a verificação de alcance. */
     callables?: string[];
+    /**
+     * Os pontos de extensão que fazem efeito ANTES do login. É contra esta lista que o `deploy` decide
+     * se um pacote carimbado tem o que fazer no boot — carimbar um que não contribua para nenhum deles
+     * o carregaria sem efeito, e quem o carimbou acreditaria que está no ar.
+     *
+     * Ela é DERIVADA do kernel e viaja no manifesto justamente para o Console não a conhecer de cor: o
+     * Console é versionado separadamente, e uma cópia aqui passaria a descrever o contrato de outra
+     * versão em silêncio. Ausente nos pacotes anteriores às extensões carimbadas.
+     */
+    preLoginPoints?: string[];
     backendParameters: BackendParameter[];
     manualPrerequisites: KernelPrerequisite[];
     /**
@@ -135,4 +145,10 @@ export declare const callableFunctionNames: (source: string) => string[];
 export declare const declaredParametersIn: (source: string) => BackendParameter[];
 /** Comparação de versão suficiente para `minimumCliVersion`: três números, sem pré-lançamento. */
 export declare const compareVersions: (left: string, right: string) => number;
+/**
+ * Os pontos que valem antes do login, lidos de `domain/schema/plugin/preLoginPoints.ts`. Lista vazia é
+ * recusada em vez de aceita: um pacote sem nenhum ponto pré-login recusaria todo carimbo, e a causa
+ * (o parser não achou nada) não teria nada a ver com o sintoma.
+ */
+export declare const parsePreLoginPoints: (source: string) => string[];
 export declare const parseKernelVersion: (source: string) => string;

package/lib/kernel/manifest.js

@@ -137,6 +137,22 @@ export const compareVersions = (left, right) => {
     }
     return 0;
 };
+/**
+ * Os pontos que valem antes do login, lidos de `domain/schema/plugin/preLoginPoints.ts`. Lista vazia é
+ * recusada em vez de aceita: um pacote sem nenhum ponto pré-login recusaria todo carimbo, e a causa
+ * (o parser não achou nada) não teria nada a ver com o sintoma.
+ */
+export const parsePreLoginPoints = (source) => {
+    const block = source.match(/PRE_LOGIN_POINTS[^=]*=\s*\[([^\]]*)\]/);
+    if (block === null) {
+        throw new Error('PRE_LOGIN_POINTS not found in domain/schema/plugin/preLoginPoints.ts');
+    }
+    const points = [...block[1].matchAll(/'([^']+)'/g)].map((match) => match[1]);
+    if (points.length === 0) {
+        throw new Error('PRE_LOGIN_POINTS is empty in domain/schema/plugin/preLoginPoints.ts');
+    }
+    return points;
+};
 export const parseKernelVersion = (source) => {
     const match = source.match(/KERNEL_VERSION\s*=\s*'([^']+)'/);
     if (match === null)

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.7.2";
+export declare const CLI_VERSION = "2.10.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.7.2';
+export const CLI_VERSION = '2.10.0';

package/lib/vendor/exampleSources.js

@@ -31,7 +31,9 @@ export const EXAMPLE_SOURCES = {
  * extensão tem a sua pasta — aqui elas moram num diretório comum, com um nível a mais.
  */
 export const rewriteImports = (source) => source.replace(/from '(\.[^']*)'/g, (match, specifier) => {
-    if (/(^|\/)contributionBuilders$/.test(specifier) || specifier.includes('domain/')) {
+    if (/(^|\/)contributionBuilders$/.test(specifier)
+        || specifier.includes('domain/')
+        || specifier.includes('sdk/')) {
         return "from '@microteia/sdk'";
     }
     // `./views/<plugin>/Nome.tsx?raw` -> `./views/Nome.tsx?raw`
@@ -44,8 +46,10 @@ const HEADER = (id) => `// Example: a Microteia first-party extension, as SOURCE
 //
 //     npx microteia-plugin build ${id}/plugin.ts
 //
-// The only difference from how it is written inside Microteia is the import path: there it reaches into
-// the kernel tree, here everything comes from '@microteia/sdk'.
+// Two things differ from how you would write the same extension. The imports: inside Microteia they
+// reach into the kernel tree, here everything comes from '@microteia/sdk'. And the view sources: these
+// travel as TEXT and are merged by 'mergeViewSources', because the platform bundles them; you point at
+// the files with 'sourceFile' and the compiler merges them for you. See AUTHORING.md, section 7.
 
 `;
 /**

package/lib/vendor/installationDocs.js

@@ -90,10 +90,11 @@ const commandRows = () => [
     '|---|---|',
     '| `microteia unpack --version <latest\\|x.y.z>` | Downloads a platform version, verifies it, and puts it in place. Touches no Firebase — safe any time |',
     '| `microteia unpack --kernel <pkg>.tgz` | The same, from a file you already have — for a machine with no access to the catalog |',
-    '| `microteia deploy [--only …] [--prune]` | Publishes what is in place: `rules`, `indexes`, `functions`, `hosting`. `--prune` also deletes functions left behind in a region this version no longer uses |',
-    '| `microteia provision [--prune]` | Gives installed extensions the functions and indexes they ask for |',
+    '| `microteia deploy [--only …] [--prune] [--all]` | Publishes what is in place: `rules`, `indexes`, `functions`, `hosting`. A Cloud Function the project already runs with this exact code is not deployed again; `--all` deploys every one of them anyway. `--prune` also deletes functions left behind in a region this version no longer uses |',
+    '| `microteia provision [--prune] [--all]` | Gives installed extensions the functions and indexes they ask for |',
     '| `microteia connect --project <id>` | Binds this installation to a Firebase project you own |',
     '| `microteia plugin-init` | Prepares `extensions/` for authoring in TypeScript |',
+    '| `microteia export-catalog --tenant <id>` | Writes what an office has — screens, lists, installed extensions — into `extensions/`, so the authoring tools can see it. Reads only; with no `--tenant` it lists the offices. The file is a snapshot and is git-ignored: it carries names the office typed |',
 ].join('\n');
 /**
  * O documento técnico. SOBREPOSTO a cada `unpack`, e por isso é onde o detalhe que acompanha a versão
@@ -145,6 +146,23 @@ it is what makes an upgrade trustworthy, and the reason your files are elsewhere
 
 ${commandRows()}
 
+### Signing in before there is an organization
+
+The sign-in screen runs above the organization: there is no tenant there, so nothing an organization
+installed can reach it. That is why \`login.extensions\` in \`microteia.yaml\` exists — it lists compiled
+extension packages that \`deploy\` stamps into the site itself, and it is how a corporate SSO, or your own
+mark on the sign-in screen, gets there.
+
+Two things follow, and both are deliberate:
+
+- **Nothing stamped runs JavaScript.** The packages load untrusted, so only declarations apply. That is
+  what lets you put an SSO live without anyone reviewing code.
+- **Stamping is not installing.** A stamped package applies before sign-in only; inside the organization
+  what applies is what the organization installed, from the Extensions screen. To have both, do both.
+
+\`deploy\` refuses a package that contributes to nothing which works before sign-in, rather than stamping
+it: it would load with no effect, and you would believe it was live.
+
 \`unpack\` and \`deploy\` are separate so that taking a new version does not oblige you to publish
 everything, and so that there is a moment between the two to fill in a setting the new version asks for.
 
@@ -179,6 +197,19 @@ carry that setting.
 
 An empty line means "not configured". A feature that needs it stays off rather than failing halfway.
 
+## 3.1 Why a deploy is usually much faster than the first one
+
+Firebase stamps every Cloud Function with what it was built from — the whole source directory, the
+resolved environment variables, and the secret versions. \`microteia deploy\` reads those stamps, deploys
+one reference function, and compares: a function whose stamp comes back unchanged is byte-for-byte what
+the project already runs, and is left alone. It is the same comparison \`firebase deploy\` makes when it
+deploys in bulk, which is why a version that only changed the application's screens finishes in minutes
+instead of publishing every function again.
+
+What the stamp does not see is configuration changed **outside** this installation — memory, timeout,
+concurrency or invoker policy edited in the Google console. \`microteia deploy --all\` deploys everything
+regardless, and is the answer for that.
+
 ## 4. Your own Cloud Functions
 
 Two places, answering two different questions:

package/lib/vendor/pack.js

@@ -4,7 +4,7 @@ import { flagValue, hasFlag } from '../shared/args.js';
 import { repoRoot } from '../shared/paths.js';
 import { run } from '../shared/run.js';
 import { blank, bullets, heading, info, step, success } from '../shared/ui.js';
-import { DEFAULT_FUNCTIONS_REGION, KERNEL_COMPONENTS, KERNEL_DISTRIBUTION_ID, MANUAL_PREREQUISITES, MINIMUM_CLI_VERSION, REQUIRED_NODE_VERSION, callableFunctionNames, declaredParametersIn, exportedFunctionNames, parseKernelVersion, } from '../kernel/manifest.js';
+import { DEFAULT_FUNCTIONS_REGION, KERNEL_COMPONENTS, KERNEL_DISTRIBUTION_ID, MANUAL_PREREQUISITES, MINIMUM_CLI_VERSION, REQUIRED_NODE_VERSION, callableFunctionNames, declaredParametersIn, exportedFunctionNames, parseKernelVersion, parsePreLoginPoints, } from '../kernel/manifest.js';
 import { digestOfFile } from '../shared/digest.js';
 import { kernelTarballName } from '../kernel/channel.js';
 import { baselineFunctionsOf, baselineIndexesOf, claimProblems, claimsFromTemplates, } from '../kernel/backendShape.js';
@@ -123,6 +123,7 @@ export const pack = async (args) => {
      */
     const changelog = await readChangelog(root, KERNEL_CHANGELOG, version);
     const kernelVersion = parseKernelVersion(await readFile(join(root, 'src/domain/schema/plugin/kernelVersion.ts'), 'utf8'));
+    const preLoginPoints = parsePreLoginPoints(await readFile(join(root, 'src/domain/schema/plugin/preLoginPoints.ts'), 'utf8'));
     const functionNames = exportedFunctionNames(await readFile(join(root, 'functions/src/index.ts'), 'utf8'));
     const scan = await scanBackendSources(join(root, 'functions/src'));
     const backendParameters = scan.parameters;
@@ -225,6 +226,7 @@ export const pack = async (args) => {
         baselineFunctions,
         baselineIndexes,
         callables,
+        preLoginPoints,
         backendParameters,
         manualPrerequisites: MANUAL_PREREQUISITES,
         sdk,

package/package.json

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