@microteia/console 2.25.0 → 2.28.0

package/CONSOLE-VERSIONS.md

@@ -22,6 +22,22 @@
 - fix(command): what was broken, and what it did to whoever hit it.
 -->
 
+#### [2.28.0] — 2026-10-13
+
+- feat(examples): the Console ships `business-days` as authoring source — a collection the kernel reads without knowing its name (`time.business.calendar`), and a code view that edits data no field type describes.
+
+#### [2.27.0] — 2026-10-13
+
+- feat(examples): the Console ships `document-example` as authoring source — a `document.template` contribution (Markdown, with `{{#each}}`/`{{#if}}` and a child-record `dataset`) over two screens addressed by `sourceId`.
+
+#### [2.26.1] — 2026-10-12
+
+- fix(connect): the "enable the Firestore TTL policy on auditLogs.expiresAt" prerequisite is gone from `connect` and from `MICROTEIA.md`. The policy is declared — `"ttl": true` in a `fieldOverride` of `firestore.indexes.json` — and the `firebase deploy --only firestore:indexes` that `deploy` runs applies it; the step asked the organization to redo by hand what the deploy had already done. The same holds for every TTL the kernel declares (`workflow_trigger_marks.expiresAt` too).
+
+#### [2.26.0] — 2026-10-09
+
+- feat(plugin-init): the organization's namespace is required — `--namespace com.acme`, or asked for when there is a terminal — validated before anything is written, and recorded in the seed `package.json` under `microteia.namespace`. `--force` reuses the one already recorded. The SDK derives every extension id in the directory from it.
+
 #### [2.25.0] — 2026-10-07
 
 - feat(examples): the Console ships `record-tab-example` as authoring source — a tab inside another screen's record, as code and as Widget DSL, and a list locked to the open record.

package/README.md

@@ -1,4 +1,4 @@
-# Microteia Console 2.25.0
+# Microteia Console 2.28.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/pluginWorkspace.js

@@ -1,11 +1,12 @@
 import { access, mkdir, readFile, writeFile } from 'node:fs/promises';
 import { dirname, join, relative, resolve } from 'node:path';
+import { createInterface } from 'node:readline/promises';
 import { flagValue, hasFlag } from '../shared/args.js';
 import { blank, bullets, heading, info, success, warn } from '../shared/ui.js';
 import { run } from '../shared/run.js';
 import { ENVIRONMENT_FILE, readEnvironment } from './environment.js';
 import { WORKSPACE_DIR } from './workspace.js';
-import { SDK_TARBALL, workspacePackageJson } from '../vendor/pluginWorkspaceTemplates.js';
+import { SDK_TARBALL, isValidNamespace, workspacePackageJson } from '../vendor/pluginWorkspaceTemplates.js';
 /**
  * `microteia plugin-init` — prepara `extensions/`, onde o escritório escreve extensão em TypeScript.
  *
@@ -107,6 +108,45 @@ export const refreshAuthoringWorkspace = async (root, officeName) => {
         return false;
     }
 };
+/** O que um `--force` anterior deixou gravado: reescrever a semente não é motivo para perguntar de novo. */
+const existingNamespace = async (directory) => {
+    try {
+        const pkg = JSON.parse(await readFile(join(directory, 'package.json'), 'utf8'));
+        const value = pkg.microteia?.namespace;
+        return typeof value === 'string' && isValidNamespace(value) ? value : null;
+    }
+    catch {
+        return null;
+    }
+};
+/**
+ * O namespace é OBRIGATÓRIO, e não tem padrão: qualquer padrão seria um prefixo que não é do escritório,
+ * e o id que nasce dele é permanente. Sem terminal, só a flag responde.
+ */
+const resolveNamespace = async (args, directory) => {
+    const given = flagValue(args, 'namespace') ?? await existingNamespace(directory) ?? await askNamespace();
+    const namespace = given.trim();
+    if (!isValidNamespace(namespace)) {
+        throw new Error(`"${namespace}" is not a valid namespace. Use reverse-DNS, lowercase, from a domain your organization`
+            + ' controls — for example: --namespace com.acme');
+    }
+    return namespace;
+};
+const askNamespace = async () => {
+    if (!process.stdin.isTTY) {
+        throw new Error('A namespace is required: every extension written in this directory is named below it, and its ids\n'
+            + 'are permanent. Pass it with --namespace, for example: microteia plugin-init --namespace com.acme');
+    }
+    info('Every extension written here is named below a namespace — the reverse-DNS of a domain your');
+    info('organization controls, like com.acme. Its ids are permanent, so choose one that is yours.');
+    const rl = createInterface({ input: process.stdin, output: process.stdout });
+    try {
+        return (await rl.question('namespace: ')).trim();
+    }
+    finally {
+        rl.close();
+    }
+};
 export const pluginInit = async (args) => {
     const file = resolve(flagValue(args, 'file') ?? join(process.cwd(), ENVIRONMENT_FILE));
     const root = dirname(file);
@@ -120,17 +160,19 @@ export const pluginInit = async (args) => {
     }
     const sdk = await locateSdk(root);
     const installDir = join(root, WORKSPACE_DIR, 'install');
+    const namespace = await resolveNamespace(args, directory);
     heading(`Extension authoring for "${environment.project.name}"`);
     await mkdir(directory, { recursive: true });
     // O caminho do tarball é relativo, para que o diretório continue válido se a instalação inteira for
     // movida — o que acontece assim que alguém a versiona num repositório do escritório.
-    await writeFile(join(directory, 'package.json'), workspacePackageJson(environment.environment.id, relative(directory, sdk.path)));
-    success('wrote the seed package.json');
+    await writeFile(join(directory, 'package.json'), workspacePackageJson(environment.environment.id, relative(directory, sdk.path), namespace));
+    success(`wrote the seed package.json (namespace ${namespace})`);
     blank();
     info('Installing @microteia/sdk and writing the guides...');
     await syncAuthoringWorkspace(directory, sdk.path, installDir, environment.project.name);
     blank();
     info(`Extension authoring ready in ${relative(root, directory)}/ (kernel contract ${sdk.kernelVersion}).`);
+    info(`Every extension created there is ${namespace}.<name> — recorded in package.json, under microteia.namespace.`);
     bullets([
         `cd ${relative(process.cwd(), directory) || '.'}`,
         'npm run create',

package/lib/index.js

@@ -59,7 +59,7 @@ const COMMANDS = [
     },
     {
         name: 'plugin-init',
-        usage: 'microteia plugin-init [--dir <path>] [--force]',
+        usage: 'microteia plugin-init --namespace <com.acme> [--dir <path>] [--force]',
         summary: 'Prepare "extensions/", to author extensions in TypeScript in your editor.',
         audience: 'office',
         execute: pluginInit,

package/lib/kernel/manifest.js

@@ -91,13 +91,6 @@ export const MANUAL_PREREQUISITES = [
             + 'with the credential it was given and refuses everything else.',
         optional: true,
     },
-    {
-        id: 'audit-ttl',
-        title: 'Enable the Firestore TTL policy on auditLogs.expiresAt',
-        detail: 'Firestore console, TTL, collection auditLogs, field expiresAt. It cannot be declared in code or '
-            + 'rules. Without it audit logs are never expired and grow without bound.',
-        optional: false,
-    },
 ];
 /**
  * Os nomes das Cloud Functions saem de `functions/src/index.ts`, a mesma fonte e o mesmo parse que

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.25.0";
+export declare const CLI_VERSION = "2.28.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.25.0';
+export const CLI_VERSION = '2.28.0';

package/lib/vendor/exampleSources.js

@@ -35,6 +35,7 @@ export const EXAMPLE_SOURCES = {
     agent: 'agent.ts',
     brasil: 'brasil.ts',
     calendar: 'calendar.ts',
+    'business-days': 'businessDays.ts',
     dashboard: 'dashboard.ts',
     'locale-pt-br': 'localePtBr',
     news: 'news.ts',
@@ -50,6 +51,7 @@ export const EXAMPLE_SOURCES = {
     'command-example': 'examples/command-example',
     'settings-example': 'examples/settings-example',
     'record-tab-example': 'examples/record-tab-example',
+    'document-example': 'examples/document-example',
 };
 /**
  * Os exemplos que existem SÓ para ser lidos — os que não estão no catálogo embutido.

package/lib/vendor/pluginWorkspaceTemplates.d.ts

@@ -16,4 +16,5 @@ export declare const SDK_TARBALL = "microteia-sdk.tgz";
  * duplicá-los aqui era exatamente o problema. O `sync` os acrescenta logo depois do `npm install`, e o
  * segundo `npm install` os instala.
  */
-export declare const workspacePackageJson: (officeName: string, sdkPath: string) => string;
+export declare const workspacePackageJson: (officeName: string, sdkPath: string, namespace: string) => string;
+export declare const isValidNamespace: (value: string) => boolean;

package/lib/vendor/pluginWorkspaceTemplates.js

@@ -16,7 +16,7 @@ export const SDK_TARBALL = 'microteia-sdk.tgz';
  * duplicá-los aqui era exatamente o problema. O `sync` os acrescenta logo depois do `npm install`, e o
  * segundo `npm install` os instala.
  */
-export const workspacePackageJson = (officeName, sdkPath) => JSON.stringify({
+export const workspacePackageJson = (officeName, sdkPath, namespace) => JSON.stringify({
     name: `${officeName}-extensions`,
     version: '0.0.0',
     private: true,
@@ -26,4 +26,14 @@ export const workspacePackageJson = (officeName, sdkPath) => JSON.stringify({
         // traz o SDK novo é `npm run sdk:refresh` — ou o `microteia unpack`, que o faz sozinho.
         '@microteia/sdk': `file:${sdkPath}`,
     },
+    // O prefixo de todo id escrito neste diretório. É o SDK que o lê (`microteia-plugin create`, o MCP);
+    // o Console só o recebe de quem roda o `plugin-init`, que é a única pessoa que pode decidi-lo.
+    microteia: { namespace },
 }, null, 2) + '\n';
+/**
+ * O formato de id de extensão (`isValidPluginId`, no domínio) — repetido porque o Console não importa
+ * o kernel, e conferir ANTES de escrever a semente é o que evita um `--force` só para corrigir um erro
+ * de digitação. `pluginWorkspaceTemplates.test.ts` prende os dois um ao outro.
+ */
+const NAMESPACE_PATTERN = /^[a-z][a-z0-9]*(\.[a-z][a-z0-9-]*)+$/;
+export const isValidNamespace = (value) => NAMESPACE_PATTERN.test(value);

package/package.json

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