@stackbone/cli 0.3.2 → 0.3.3

package/migrations/0046_runtime_identity_control_plane.sql

@@ -0,0 +1,28 @@
+-- 0046_runtime_identity_control_plane.sql — the identity the CONTROL PLANE knows
+-- this box by (STA-594).
+--
+-- A box mints its own installation id on first boot (0033) and that value is
+-- entirely its own: nobody outside the container picks it. The control plane
+-- separately keeps an installation row, with its own id, for the same box. The
+-- box never knew that second id, so it could not check a token minted for it.
+--
+-- It learns the pair during registration — the one moment both sides are
+-- connected, mutually authenticated and cannot disagree — and keeps it here.
+--
+-- WHY A SEPARATE TABLE instead of two more columns on `runtime_identity`.
+-- The box's own installation id namespaces its Connect grants and its storage
+-- keys, so overwriting it orphans live OAuth grants with no visible error at
+-- all. Two tables share no writable column, which makes "the learned value never
+-- touches the minted one" a property of the schema rather than a discipline the
+-- next UPDATE's column list has to remember.
+--
+-- One row, like `runtime_identity` (0033) and `workspace_settings` (0029): this
+-- describes THE runtime, not a collection of anything. NO seed — the row's
+-- absence is exactly what "nobody has told this box what it answers for" means,
+-- and that absence is what the boot log reports.
+CREATE TABLE IF NOT EXISTS stackbone_platform.runtime_control_plane_identity (
+    id              int         PRIMARY KEY DEFAULT 1 CHECK (id = 1),
+    installation_id uuid        NOT NULL,
+    organization_id uuid        NOT NULL,
+    learned_at      timestamptz NOT NULL DEFAULT now()
+);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stackbone/cli",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "license": "UNLICENSED",
   "type": "module",
   "bin": {