@indigoai-us/hq-cli 5.122.0 → 5.122.1

package/CHANGELOG.md

@@ -2,8 +2,17 @@
 
 ## [Unreleased]
 
+## [5.122.1] — 2026-09-19
+
 ### Fixed
 
+- `hq cloud provision company` no longer silently accepts a server-suffixed
+  slug. When another owner already holds the requested name, the vault assigns
+  `<slug>-<tag>` and used to write local config as if the original name had
+  been granted — sync then cannot push, because it looks for a folder matching
+  the cloud slug. Provision now fails before writing, and retires the
+  just-created entity so it does not leave a suffixed orphan.
+
 - Work Mesh now keeps the company you selected when its session context is
   acknowledged or recovered after a restart. Mesh activity stays attached to
   the right company instead of being held for missing attribution.

package/dist/commands/cloud-provision.js

@@ -513,6 +513,52 @@ export async function provisionCompany(options) {
         createdEntity = true;
         log(`created vault entity uid=${entity.uid}`);
     }
+    // hq-pro auto-suffixes a company slug when another owner already holds the
+    // bare name (`<slug>-<ownerTag>`). `/entity/check-slug/me` only looks at the
+    // caller's namespace, so it reports "available" and we POST; the server then
+    // returns a different slug. Writing companies/<requested>/.hq/config.json
+    // with the requested slug (or syncing with --company <assigned>) leaves the
+    // local folder and the cloud slug pointing at two different paths — share()
+    // derives syncRoot from ctx.slug, so the company can never be pushed.
+    // Fail before any local write. Retire a just-created entity so we do not
+    // leave a suffixed orphan.
+    if (entity.slug !== options.slug) {
+        const assigned = entity.slug || "(missing)";
+        let retired = false;
+        if (createdEntity) {
+            try {
+                await vaultClient.softDeleteCompany(entity.uid);
+                retired = true;
+                log(`retired vault entity uid=${entity.uid} — assigned slug ${assigned} differs from requested ${options.slug}`);
+            }
+            catch (err) {
+                const msg = err instanceof Error ? err.message : String(err);
+                log(`failed to retire mismatched vault entity uid=${entity.uid}: ${msg}`);
+            }
+        }
+        const retireNote = retired
+            ? `The just-created entity ${entity.uid} was retired.`
+            : createdEntity
+                ? `Retire entity ${entity.uid} with \`hq cloud retire company\`, then retry after the original slug is free.`
+                : `Existing entity ${entity.uid} was not modified.`;
+        throw new ProvisionError(1, `Cloud assigned slug "${assigned}" instead of requested "${options.slug}". ` +
+            `Local folder is companies/${options.slug}; sync derives the company folder from the cloud slug, so this company cannot be pushed. ` +
+            `${retireNote} Ask an admin to release the original slug, or rename the local folder to "${assigned}" and re-run.`, {
+            ok: false,
+            company_slug: options.slug,
+            cloud_uid: entity.uid,
+            bucket_name: entity.bucketName ?? "",
+            vault_api_url: options.vaultApiUrl,
+            kms_key_id: entity.kmsKeyId ?? null,
+            created_entity: createdEntity,
+            manifest_patched: false,
+            config_written: false,
+            initial_sync: {
+                ok: false,
+                error: `assigned slug "${assigned}" differs from requested "${options.slug}"`,
+            },
+        });
+    }
     if (!entity.bucketName) {
         // Vault returned an entity without a bucket — this would happen if the
         // provisioning Lambda asynchronously failed. We have a `cloud_uid` but

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@indigoai-us/hq-cli",
-  "version": "5.122.0",
+  "version": "5.122.1",
   "description": "HQ by Indigo management CLI \u2014 modules and cloud sync",
   "main": "dist/index.js",
   "bin": {