Skip to content

💫 Toolkit to help you get started with SDD or any other process!

fix(integrations): declare kiro-cli multi-install safe (#3471) (#3485)

Noor ul ain0acb5c6461e4
diff --git a/src/specify_cli/integrations/kiro_cli/__init__.py b/src/specify_cli/integrations/kiro_cli/__init__.py
index 0b8348af7..37f743d5c 100644
--- a/src/specify_cli/integrations/kiro_cli/__init__.py
+++ b/src/specify_cli/integrations/kiro_cli/__init__.py
@@ -27,3 +27,10 @@ class KiroCliIntegration(MarkdownIntegration):
"args": _KIRO_ARG_FALLBACK,
"extension": ".md",
}
+
+ # Kiro CLI keeps everything under a static, isolated agent root
+ # (``.kiro/`` with commands in ``.kiro/prompts``) that no other
+ # integration writes to, so it is safe to install alongside others
+ # (issue #3471). The registry's multi-install-safe contract tests
+ # enforce that isolation for every integration setting this flag.
+ multi_install_safe = True
diff --git a/tests/integrations/test_registry.py b/tests/integrations/test_registry.py
index d3049b426..13d496892 100644
--- a/tests/integrations/test_registry.py
+++ b/tests/integrations/test_registry.py
@@ -272,6 +272,20 @@ class TestMultiInstallSafeContracts:
f"these files: {sorted(overlap)}"
)
+ def test_kiro_cli_is_declared_multi_install_safe(self):
+ """kiro-cli confines itself to an isolated ``.kiro/`` root that no
+ other integration touches, so it must be declared multi-install safe
+ (issue #3471).
+
+ Before the fix, co-installing kiro-cli alongside another integration
+ left ``specify integration status`` permanently in ERROR
+ (``unsafe-multi-install``) with no way to acknowledge it. The
+ parametrized isolation/manifest contracts above already exercise
+ kiro-cli once the flag is set; this pins the declaration itself so a
+ future edit cannot silently drop it and reintroduce the error.
+ """
+ assert INTEGRATION_REGISTRY["kiro-cli"].multi_install_safe is True
+
class TestCatalogParity:
"""The discovery catalog must list every registered integration."""