imperal-sdk 4.2.3__tar.gz → 4.2.4__tar.gz

{imperal_sdk-4.2.3 → imperal_sdk-4.2.4}/CHANGELOG.md

@@ -2,6 +2,30 @@
 
 All notable changes to `imperal-sdk` are documented here.
 
+## 4.2.4 — 2026-05-13
+
+**EXT-SECRETS-V1 — unconditional synthetic Secrets panel**
+
+In v4.2.3 the synthetic Secrets panel was registered conditionally on the
+first `@ext.secret(...)` call, which meant extensions that did not declare
+secrets had no menu entry — leaving end-users without a discoverable place
+to manage credentials when developers later add declarations.
+
+This release flips the registration to **unconditional**: every Extension
+instance auto-registers the synthetic `secrets` panel in `__init__` (slot
+`right`, title `Secrets`, icon `KeyRound`). When the manifest has zero
+declared secrets, the panel renders an empty state with developer guidance
+(`@ext.secret(...)` code example + link to docs). When declarations exist,
+it renders one card per secret with `is_set` status + Manage button.
+
+### Migration notes
+
+- **No code changes required**. Bump your ext's SDK pin to `>= 4.2.4` and
+  redeploy via Dev Portal — the Secrets tab appears automatically.
+- Extensions that genuinely never need credentials still get the tab; this
+  is intentional for UX consistency. Federal V32 contract still requires
+  `@ext.secret` for any real credential access at runtime.
+
 ## 4.2.3 — 2026-05-13
 
 **EXT-SECRETS-V1 UX polish — synthetic `secrets` panel auto-injected**

{imperal_sdk-4.2.3 → imperal_sdk-4.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: imperal-sdk
-Version: 4.2.3
+Version: 4.2.4
 Summary: SDK for building Imperal Cloud extensions
 Author: Valentin Scerbacov, Imperal, Inc.
 License-Expression: AGPL-3.0-or-later

{imperal_sdk-4.2.3 → imperal_sdk-4.2.4}/src/imperal_sdk/__init__.py

@@ -39,7 +39,7 @@ from imperal_sdk.secrets import (
     SecretValueTooLarge, SecretDeclarationConflict,
 )
 
-__version__ = "4.2.3"
+__version__ = "4.2.4"
 
 __all__ = [
     # Core

{imperal_sdk-4.2.3 → imperal_sdk-4.2.4}/src/imperal_sdk/extension.py

@@ -142,6 +142,36 @@ class Extension:
         # EXT-SECRETS-V1 (v4.2.2) — declared secrets emitted into manifest.secrets[]
         self._secrets: dict[str, "SecretSpec"] = {}
 
+        # EXT-SECRETS-V1 (v4.2.4) — auto-register synthetic 'secrets' panel
+        # unconditionally for every Extension. Empty state (no @ext.secret
+        # declared) renders developer guidance with code example. Federal
+        # contract enforced platform-side regardless of UI presence.
+        self._auto_register_secrets_panel()
+
+    def _auto_register_secrets_panel(self) -> None:
+        """Register the platform-provided 'secrets' panel.
+
+        Idempotent — only registers once per Extension instance. Slot
+        defaults to 'right' (least-used by typical extensions, lowest
+        collision risk with deploy-sync logic that keeps one panel per slot).
+        """
+        if "secrets" in self._panels:
+            return
+        try:
+            from imperal_sdk.secrets.panel_handler import (
+                builtin_secrets_panel_handler,
+            )
+        except Exception:
+            # If secrets package import fails, don't break Extension init.
+            return
+        self.panel(
+            "secrets",
+            slot="right",
+            title="Secrets",
+            icon="KeyRound",
+            refresh="manual",
+        )(builtin_secrets_panel_handler)
+
     def secret(
         self,
         name: str,
@@ -195,32 +225,10 @@ class Extension:
             )
         self._secrets[name] = spec
 
-        # EXT-SECRETS-V1 (v4.2.3): auto-register synthetic 'secrets' panel
-        # on first @ext.secret call so the Secrets tab appears alongside
-        # the extension's own tabs without the author writing panel code.
-        # The handler is shipped in imperal_sdk.secrets.panel_handler.
-        # Subsequent @ext.secret calls are no-ops here — registration is
-        # idempotent.
-        #
-        # Slot choice: ``right`` is defensively chosen. Most extensions
-        # use ``left`` (sidebar nav) and ``center`` (main content); ``right``
-        # is rarely-used so the synthetic Secrets tab is least likely to be
-        # overwritten by the deploy-sync logic in imperal-ext-developer
-        # which currently keeps only one panel per slot. If your extension
-        # already uses ``right``, your panel wins; users can still reach
-        # the Secrets UI via the chat-top ribbon and at /ext/{ext_id}/secrets.
-        if "secrets" not in self._panels:
-            from imperal_sdk.secrets.panel_handler import (
-                builtin_secrets_panel_handler,
-            )
-            # Call self.panel(...) the same way an extension author would.
-            self.panel(
-                "secrets",
-                slot="right",
-                title="Secrets",
-                icon="KeyRound",
-                refresh="manual",
-            )(builtin_secrets_panel_handler)
+        # EXT-SECRETS-V1 (v4.2.4): synthetic Secrets panel is now registered
+        # unconditionally in Extension.__init__ via _auto_register_secrets_panel.
+        # This call site is a no-op safety net for older bytecode paths.
+        self._auto_register_secrets_panel()
 
         def _decorator(target):
             return target  # syntactic anchor only — decorator is a no-op wrapper