fix(integrations): declare LingmaIntegration multi_install_safe#3654
Merged
Conversation
LingmaIntegration writes only to its isolated, static root .lingma/skills, disjoint from every other integration, yet never declared multi_install_safe — inheriting the IntegrationBase default False and leaving `specify integration status` in a permanent unsafe-multi-install ERROR state when lingma is co-installed alongside another agent. Add `multi_install_safe = True`, mirroring the structurally-identical trae/zcode SkillsIntegrations and the kiro-cli github#3471 fix. The parametrized registry isolation contracts auto-include lingma and pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Declares Lingma safe for co-installation because it writes exclusively under .lingma/skills.
Changes:
- Sets
LingmaIntegration.multi_install_safetoTrue. - Adds a regression test for the declaration.
Show a summary per file
| File | Description |
|---|---|
src/specify_cli/integrations/lingma/__init__.py |
Enables safe multi-install behavior. |
tests/integrations/test_integration_lingma.py |
Guards the safety declaration. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Medium
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
LingmaIntegrationwrites only to its isolated, static root.lingma/skills— disjoint from every other integration — yet never declaredmulti_install_safe, so it inherited theIntegrationBasedefaultFalse.Why it matters
Like the merged kiro-cli fix #3471, an isolated-but-undeclared integration leaves
specify integration statusin a permanentunsafe-multi-installERROR state when lingma is co-installed alongside another agent, with no acknowledgment path.traeandzcode— structurally identicalSkillsIntegrations (IDE,install_url=None,requires_cli=False, only a--skillsoption) — both declare the flag.Fix
Add
multi_install_safe = True, mirroringtrae/zcodeand the kiro-cli #3471 precedent.Tests
test_integration_lingma.py::TestLingmaIntegration::test_multi_install_safe(fails before the fix). The parametrized registry isolation contracts auto-include lingma once the flag is set and pass —.lingma/skillsis isolated and its manifest disjoint.ruffclean.AI-assisted: authored with Claude Code. Verified
.lingma/is unique across all integrations and the isolation contracts pass with the flag set.