@isomorph.ai/cli 0.7.3 → 0.7.5

package/dist/packages/harbour-cli/src/agent-setup.js

@@ -109,7 +109,7 @@ Rules live beside this file: \`core.md\` before the first edit; \`integrations.m
 ## Getting ready
 
 - No \`.isomorph/\` yet: \`isomorph init --app-root .\` (empty folder → starter; an existing app → three choices to relay). Node 22+, no Docker.
-- Sign-in (company systems and shipping only): \`isomorph connect <work-email>\` (refused? run the command it prints), then \`isomorph login\` — the browser opens and the person finishes there (their one step; say so).
+- Sign-in, only when a command answers \`CONFIG_REQUIRED\` or \`AUTH_REQUIRED\` (most machines already are): \`isomorph connect <work-email>\`, then \`isomorph login\` — the browser opens and the person finishes there (their one step; say so).
 
 ## Intent → command
 
@@ -118,7 +118,7 @@ Rules live beside this file: \`core.md\` before the first edit; \`integrations.m
 | "run it", "show me" | \`isomorph dev --app-root . --detach --json\`; give them \`result.origin\` (the first start takes a minute or two). Locally they are a fixture user. |
 | "check it", "is it ready?" | \`isomorph check --app-root . --json\` (the output is the report). Failures in the app's code are yours: fix and re-check until clean, after every change and before every ship, unasked and never offered as a choice. |
 | "does it work?" (and before reporting anything as working) | open the dev link in your own browser, press the control you built or changed, read what the app shows; a green \`isomorph check\` is not that proof (fixtures answer AI and company systems). A Send in development is real: reuse explicit authorization or ask once. No browser: say the button is untested. |
-| "I need Slack / Gmail / the warehouse" | read \`integrations.md\` beside this skill first; then, in the same turn: catalog, call only what it lists (literals), submit the request yourself, say READY or PENDING in one line. |
+| "I need Slack / Gmail / the warehouse" | read \`integrations.md\` beside this skill first; then: catalog, write the call (literals only), \`isomorph check\`, then submit the request; say READY or PENDING in one line. |
 | "summarise", "draft", "AI" | read \`ai.md\` beside this skill first; then one call behind a control they press. |
 | "ship it", "let my team try it" | show the person the three values in \`.isomorph/app.json\` (name, description, audience — "only you" when empty) and correct the file as they say; then \`isomorph deploy --app-root . --json\` (it runs the checks when needed and refuses once naming every blocker and its fix: relay that line; the app works meanwhile). Give them \`result.deployment.protectedUrl\`. \`--session-notes\`: what cost you time in Isomorph, or \`""\`. |
 | "make it live" | only after they have tried the preview: \`isomorph promote --operation <ref> --app-root . --confirm-tested --json\`. Report the production link, or that operator approval is pending. |

package/dist/packages/harbour-cli/src/config.js

@@ -87,6 +87,15 @@ export async function connect(startUrl, path = configPath(), fetchImpl = fetch)
         .catch((error) => { throw new CliError("PLATFORM_UNREACHABLE", `Isomorph at ${url.host} could not be reached: ${transportFailure(error)}.`); });
     const body = await response.json().catch(() => undefined);
     if (!response.ok && isRecord(body) && typeof body.error_description === "string") {
+        // A person in two companies who is already connected to one of them is
+        // not asking a question: every builder on a connected machine ran
+        // `connect <email>` on the skill's say-so and got this refusal (bench,
+        // 9 of 21 builds). The saved connection stands; a start link switches.
+        if (body.error === "tenant_ambiguous" && Array.isArray(body.tenants)) {
+            const saved = await loadConfig(path).catch(() => undefined);
+            if (saved && body.tenants.some(tenant => isRecord(tenant) && tenant.tenantId === saved.tenantId))
+                return saved;
+        }
         // The server's sentence already names the fix. Its links are printed without
         // their scheme: the failure printer strips every full URL (output.ts), and
         // `connect` accepts a link without one. `tenants` (with the full links) rides

package/dist/packages/harbour-cli/src/guide.js

@@ -67,7 +67,7 @@ Never guess a connection, channel, table, view, mailbox or column: a guess is re
 
 ## Request
 
-\`isomorph integrations request <connection> --reason "<why>" --app-root . --json\` files the one request IT approves once for every environment (\`isomorph dev\` and \`isomorph deploy\` file it too); submit it yourself, in the same turn. \`isomorph integrations status --app-root . --json\`: READY, use it; PENDING, say "IT has to approve this; the app works meanwhile". \`RESOURCE_NOT_APPROVED\`: IT adds the channel, view or mailbox in the console (Controls & integrations); then run the same request again.
+\`isomorph integrations request <connection> --reason "<why>" --app-root . --json\` files the one request IT approves once for every environment; run it once \`isomorph check\` has read the call (\`dev\`/\`deploy\` file it too). \`isomorph integrations status --app-root . --json\`: READY, use it; PENDING, say "IT has to approve this; the app works meanwhile". \`RESOURCE_NOT_APPROVED\`: IT adds the channel, view or mailbox in the console (Controls & integrations); then run the same request again.
 
 ## Consent
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@isomorph.ai/cli",
-  "version": "0.7.3",
+  "version": "0.7.5",
   "description": "Isomorph development kit CLI",
   "type": "module",
   "bin": {