codeboarding 0.13.4__tar.gz → 0.13.6__tar.gz

{codeboarding-0.13.4/codeboarding.egg-info → codeboarding-0.13.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codeboarding
-Version: 0.13.4
+Version: 0.13.6
 Summary: Interactive Diagrams for Code
 Author: CodeBoarding Team
 License-Expression: MIT

{codeboarding-0.13.4 → codeboarding-0.13.6}/README.md

@@ -104,6 +104,7 @@ On first run, CodeBoarding creates `~/.codeboarding/config.toml`. Set one provid
 ```toml
 [provider]
 # openai_api_key            = "sk-..."
+# openai_base_url           = "https://api.example.com/v1"  # any OpenAI-compatible gateway
 # anthropic_api_key         = "sk-ant-..."
 # google_api_key            = "AIza..."
 # vercel_api_key            = "vck_..."
@@ -118,6 +119,8 @@ On first run, CodeBoarding creates `~/.codeboarding/config.toml`. Set one provid
 # parsing_model = "gemini-3-flash"
 ```
 
+`openai_base_url` points CodeBoarding at any OpenAI-compatible gateway. Set the gateway API key as `openai_api_key`, then choose its model IDs with `agent_model` and `parsing_model`. The equivalent shell variables are `OPENAI_BASE_URL`, `OPENAI_API_KEY`, `AGENT_MODEL`, and `PARSING_MODEL`.
+
 Shell environment variables such as `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, `GOOGLE_API_KEY`, and `OLLAMA_BASE_URL` take precedence over the config file. For private repositories, set `GITHUB_TOKEN` in your environment.
 
 ## Common commands

{codeboarding-0.13.4 → codeboarding-0.13.6}/agents/agent_responses.py

@@ -5,7 +5,6 @@ import logging
 from abc import abstractmethod
 from collections.abc import Hashable
 from enum import StrEnum
-from pathlib import PurePosixPath
 from typing import TYPE_CHECKING, get_origin
 
 from pydantic import BaseModel, Field
@@ -377,14 +376,6 @@ class Relation(LLMBaseModel):
     def edge_count(self) -> int:
         return len(self.all_edges)
 
-    def analysis_dump(self) -> dict:
-        data = self.model_dump(exclude_none=True)
-        data["src_id"] = self.src_id
-        data["dst_id"] = self.dst_id
-        data["edge_count"] = self.edge_count
-        data["is_static"] = self.is_static
-        return data
-
 
 class ClustersComponent(LLMBaseModel):
     """A grouped component from cluster analysis - may contain multiple clusters."""
@@ -529,10 +520,6 @@ class AnalysisInsights(LLMBaseModel):
         relations = "\n".join(cr.llm_str() for cr in self.components_relations)
         return title + body + relations
 
-    def file_to_component(self) -> dict[str, str]:
-        """Build file path -> component_id mapping from root components."""
-        return {str(PurePosixPath(fg.file_path)): c.component_id for c in self.components for fg in c.file_methods}
-
 
 class ComponentArchitecture(LLMBaseModel):
     """Component-only architecture before relation discovery."""
@@ -697,75 +684,6 @@ def index_components_by_id(
     return {c.component_id: c for c in iter_components(root_analysis, sub_analyses) if c.component_id}
 
 
-class CFGComponent(LLMBaseModel):
-    """A component derived from control flow graph analysis."""
-
-    name: str = Field(description="Name of the abstract component")
-    description: str = Field(description="One paragraph explaining the component.")
-    referenced_source: list[str] = Field(
-        description="List of the qualified names of the methods and classes that are within this component."
-    )
-
-    def llm_str(self):
-        n = f"**Component:** `{self.name}`"
-        d = f"   - *Description*: {self.description}"
-        qn = ""
-        if self.referenced_source:
-            qn += "   - *Related Classes/Methods*: "
-            qn += ", ".join(f"`{q}`" for q in self.referenced_source)
-        return "\n".join([n, d, qn]).strip()
-
-
-class CFGAnalysisInsights(LLMBaseModel):
-    """Insights from control flow graph analysis including components and relations."""
-
-    components: list[CFGComponent] = Field(description="List of components identified in the CFG.")
-    components_relations: list[Relation] = Field(description="List of relations among the components in the CFG.")
-
-    def llm_str(self):
-        if not self.components:
-            return "No abstract components found in the CFG."
-        title = "# Abstract Components Overview from CFG\n"
-        body = "\n".join(ac.llm_str() for ac in self.components)
-        relations = "\n".join(cr.llm_str() for cr in self.components_relations)
-        return title + body + relations
-
-
-class ExpandComponent(LLMBaseModel):
-    """Decision on whether to expand a component with reasoning."""
-
-    should_expand: bool = Field(description="Whether the component should be expanded in detail or not.")
-    reason: str = Field(description="Reasoning behind the decision to expand or not.")
-
-    def llm_str(self):
-        return f"- *Should Expand:* {self.should_expand}\n- *Reason:* {self.reason}"
-
-
-class ValidationInsights(LLMBaseModel):
-    """Validation results with status and additional information."""
-
-    is_valid: bool = Field(description="Indicates whether the validation results in valid or not.")
-    additional_info: str | None = Field(
-        default=None,
-        description="Any additional information or context related to the validation.",
-    )
-
-    def llm_str(self):
-        return f"**Feedback Information:**\n{self.additional_info}"
-
-
-class UpdateAnalysis(LLMBaseModel):
-    """Feedback on how much a diagram needs updating."""
-
-    update_degree: int = Field(
-        description="Degree to which the diagram needs update. 0 means no update, 10 means complete update."
-    )
-    feedback: str = Field(description="Feedback provided on the analysis.")
-
-    def llm_str(self):
-        return f"**Feedback:**\n{self.feedback}"
-
-
 class MetaAnalysisInsights(LLMBaseModel):
     """Insights from analyzing project metadata including type, domain, and architecture."""
 
@@ -881,20 +799,3 @@ class ScopeUpdateDecision(LLMBaseModel):
         if not self.operations:
             return "No scope operations."
         return "\n".join(operation.llm_str() for operation in self.operations)
-
-
-class FilePath(LLMBaseModel):
-    """File path with optional line range reference."""
-
-    file_path: str = Field(description="Full file path for the reference")
-    start_line: int | None = Field(
-        default=None,
-        description="Starting line number in the file for the reference (if applicable).",
-    )
-    end_line: int | None = Field(
-        default=None,
-        description="Ending line number in the file for the reference (if applicable).",
-    )
-
-    def llm_str(self):
-        return f"`{self.file_path}`: ({self.start_line}:{self.end_line})"

{codeboarding-0.13.4 → codeboarding-0.13.6}/agents/prompts/claude_prompts.py

@@ -115,51 +115,6 @@ Complex subsystems (multiple interacting modules): CONSIDER expansion
 
 Provide clear reasoning based on architectural complexity."""
 
-VALIDATOR_SYSTEM_MESSAGE = """You validate architectural analysis quality.
-
-<instructions>
-1. Review analysis structure and component definitions first
-2. If component validity is questionable, you MUST use getClassHierarchy
-3. Assess component clarity, relationship accuracy, source references, and overall coherence
-4. Verify source file references are accurate and meaningful
-5. Ensure component naming reflects the actual code structure
-</instructions>
-
-<thinking>
-Validation criteria:
-- Component clarity and responsibility definition
-- Valid source file references
-- Appropriate relationship mapping
-- Meaningful component naming with code references
-</thinking>"""
-
-COMPONENT_VALIDATION_COMPONENT = """Review component structure for clarity and validity.
-
-Analysis to validate:
-{analysis}
-
-Validation requirements:
-- Component clarity and purpose definition
-- Source file completeness and relevance
-- Responsibilities are well-defined
-- Component naming appropriateness
-
-Output:
-Provide validation assessment without tool usage."""
-
-RELATIONSHIPS_VALIDATION = """Validate component relationships and interactions.
-
-Relationships to validate:
-{analysis}
-
-Validation requirements:
-- Relationship clarity and necessity
-- Maximum 2 relationships per component pair (avoid relations in which we have sends/returns i.e. ComponentA sends a message to ComponentB and ComponentB returns result to ComponentA)
-- Logical consistency of interactions
-- Appropriate relationship descriptions
-
-Output:
-Conclude with VALID or INVALID assessment and specific reasoning."""
 
 SYSTEM_META_ANALYSIS_MESSAGE = """You extract architectural metadata from projects.
 
@@ -289,15 +244,6 @@ class ClaudePromptFactory(AbstractPromptFactory):
     def get_expansion_prompt(self) -> str:
         return EXPANSION_PROMPT
 
-    def get_validator_system_message(self) -> str:
-        return VALIDATOR_SYSTEM_MESSAGE
-
-    def get_component_validation_component(self) -> str:
-        return COMPONENT_VALIDATION_COMPONENT
-
-    def get_relationships_validation(self) -> str:
-        return RELATIONSHIPS_VALIDATION
-
     def get_system_meta_analysis_message(self) -> str:
         return SYSTEM_META_ANALYSIS_MESSAGE
 

{codeboarding-0.13.4 → codeboarding-0.13.6}/agents/prompts/deepseek_prompts.py

@@ -114,48 +114,6 @@ Evaluate component expansion necessity for: {component}
 # Output
 Provide clear reasoning for expansion decision based on architectural complexity."""
 
-VALIDATOR_SYSTEM_MESSAGE = """You are a software architecture expert.
-
-# Task
-Validate analysis quality.
-
-# Instructions (execute in order)
-1. Review analysis structure and component definitions.
-2. Use getClassHierarchy if component validity is questionable.
-
-# Validation criteria
-- Component clarity and responsibility definition
-- Valid source file references
-- Appropriate relationship mapping
-- Meaningful component naming with code references"""
-
-COMPONENT_VALIDATION_COMPONENT = """# Task
-Validate component analysis.
-
-# Analysis
-{analysis}
-
-# Instructions (execute in order)
-1. Assess component clarity and purpose definition.
-2. Verify source file completeness and relevance.
-3. Confirm responsibilities are well-defined.
-
-# Output
-Provide validation assessment without additional tool usage."""
-
-RELATIONSHIPS_VALIDATION = """# Task
-Validate component relationships.
-
-# Analysis
-{analysis}
-
-# Instructions (execute in order)
-1. Check relationship clarity and necessity.
-2. Verify max 2 relationships per component pair (avoid bidirectional relations like ComponentA sends message to ComponentB and ComponentB returns result to ComponentA).
-3. Assess relationship logical consistency.
-
-# Output
-Conclude with VALID or INVALID assessment and specific reasoning."""
 
 SYSTEM_META_ANALYSIS_MESSAGE = """You are a senior software architect.
 
@@ -295,15 +253,6 @@ class DeepSeekPromptFactory(AbstractPromptFactory):
     def get_expansion_prompt(self) -> str:
         return EXPANSION_PROMPT
 
-    def get_validator_system_message(self) -> str:
-        return VALIDATOR_SYSTEM_MESSAGE
-
-    def get_component_validation_component(self) -> str:
-        return COMPONENT_VALIDATION_COMPONENT
-
-    def get_relationships_validation(self) -> str:
-        return RELATIONSHIPS_VALIDATION
-
     def get_system_meta_analysis_message(self) -> str:
         return SYSTEM_META_ANALYSIS_MESSAGE
 

{codeboarding-0.13.4 → codeboarding-0.13.6}/agents/prompts/gemini_flash_prompts.py

@@ -96,39 +96,6 @@ Instructions:
 Output:
 Provide clear reasoning for expansion decision based on architectural complexity."""
 
-VALIDATOR_SYSTEM_MESSAGE = """You are a software architecture expert validating analysis quality.
-
-Instructions:
-1. Review analysis structure and component definitions
-2. Use getClassHierarchy if component validity is questionable
-
-Validation criteria:
-- Component clarity and responsibility definition
-- Valid source file references
-- Appropriate relationship mapping
-- Meaningful component naming with code references"""
-
-COMPONENT_VALIDATION_COMPONENT = """Validate component analysis:
-{analysis}
-
-Instructions:
-1. Assess component clarity and purpose definition
-2. Verify source file completeness and relevance
-3. Confirm responsibilities are well-defined
-
-Output:
-Provide validation assessment without additional tool usage."""
-
-RELATIONSHIPS_VALIDATION = """Validate component relationships:
-{analysis}
-
-Instructions:
-1. Check relationship clarity and necessity
-2. Verify max 2 relationships per component pair (avoid relations in which we have sends/returns i.e. ComponentA sends a message to ComponentB and ComponentB returns result to ComponentA)
-3. Assess relationship logical consistency
-
-Output:
-Conclude with VALID or INVALID assessment and specific reasoning."""
 
 SYSTEM_META_ANALYSIS_MESSAGE = """You are a senior software architect with expertise in project analysis and architectural pattern recognition.
 
@@ -259,15 +226,6 @@ class GeminiFlashPromptFactory(AbstractPromptFactory):
     def get_expansion_prompt(self) -> str:
         return EXPANSION_PROMPT
 
-    def get_validator_system_message(self) -> str:
-        return VALIDATOR_SYSTEM_MESSAGE
-
-    def get_component_validation_component(self) -> str:
-        return COMPONENT_VALIDATION_COMPONENT
-
-    def get_relationships_validation(self) -> str:
-        return RELATIONSHIPS_VALIDATION
-
     def get_system_meta_analysis_message(self) -> str:
         return SYSTEM_META_ANALYSIS_MESSAGE
 

{codeboarding-0.13.4 → codeboarding-0.13.6}/agents/prompts/glm_prompts.py

@@ -122,52 +122,6 @@ REQUIRED STEPS (execute in order):
 REQUIRED OUTPUT:
 MUST provide clear reasoning for expansion decision based on architectural complexity."""
 
-VALIDATOR_SYSTEM_MESSAGE = """You are a software architecture quality validator. STRICTLY follow these rules:
-
-MANDATORY TASK:
-Validate analysis quality.
-
-REQUIRED STEPS (execute in order):
-1. Review analysis structure and component definitions.
-2. Use getClassHierarchy ONLY if component validity is questionable.
-
-VALIDATION CRITERIA (MUST check):
-- Component clarity and responsibility definition
-- Valid source file references
-- Appropriate relationship mapping
-- Meaningful component naming with code references"""
-
-COMPONENT_VALIDATION_COMPONENT = """You are an analysis quality reviewer. STRICTLY follow these rules:
-
-MANDATORY TASK:
-Validate component analysis.
-
-Analysis to validate:
-{analysis}
-
-REQUIRED STEPS (execute in order):
-1. Assess component clarity and purpose definition.
-2. Verify source file completeness and relevance.
-3. Confirm responsibilities are well-defined.
-
-REQUIRED OUTPUT:
-MUST provide validation assessment without additional tool usage."""
-
-RELATIONSHIPS_VALIDATION = """You are a relationship correctness validator. STRICTLY follow these rules:
-
-MANDATORY TASK:
-Validate component relationships.
-
-Analysis to validate:
-{analysis}
-
-REQUIRED STEPS (execute in order):
-1. Check relationship clarity and necessity.
-2. Verify max 2 relationships per component pair (STRICTLY avoid bidirectional relations like ComponentA sends message to ComponentB and ComponentB returns result to ComponentA).
-3. Assess relationship logical consistency.
-
-REQUIRED OUTPUT:
-MUST conclude with VALID or INVALID assessment and specific reasoning."""
 
 SYSTEM_META_ANALYSIS_MESSAGE = """You are a senior software architect. STRICTLY follow these rules:
 
@@ -316,15 +270,6 @@ class GLMPromptFactory(AbstractPromptFactory):
     def get_expansion_prompt(self) -> str:
         return EXPANSION_PROMPT
 
-    def get_validator_system_message(self) -> str:
-        return VALIDATOR_SYSTEM_MESSAGE
-
-    def get_component_validation_component(self) -> str:
-        return COMPONENT_VALIDATION_COMPONENT
-
-    def get_relationships_validation(self) -> str:
-        return RELATIONSHIPS_VALIDATION
-
     def get_system_meta_analysis_message(self) -> str:
         return SYSTEM_META_ANALYSIS_MESSAGE
 

{codeboarding-0.13.4 → codeboarding-0.13.6}/agents/prompts/gpt_prompts.py

@@ -104,90 +104,6 @@ EXPANSION_PROMPT = """Expand the architectural analysis with additional detail.
 
 **Goal:** Deeper architectural insights while maintaining overall coherence."""
 
-VALIDATOR_SYSTEM_MESSAGE = """You are a software architecture validation expert.
-
-**Role:** Validate architectural analysis for accuracy, completeness, and clarity.
-
-**Validation Criteria:**
-1. **Accuracy:** All components and relationships are correctly identified
-2. **Completeness:** No critical components or relationships are missing
-3. **Clarity:** Documentation is clear and understandable
-4. **Consistency:** Analysis follows stated architectural patterns
-5. **Diagram Suitability:** Components and relationships are suitable for visualization
-
-**Approach:**
-- Systematically review each component
-- Verify relationships and data flow
-- Check source file references
-- Validate against project type patterns
-- Assess documentation clarity
-
-**Output:** Detailed validation feedback with specific improvement suggestions."""
-
-COMPONENT_VALIDATION_COMPONENT = """Validate component definition and structure.
-
-**Validation Checklist:**
-
-1. **Component Identity:**
-   - [ ] Clear, descriptive name
-   - [ ] Distinct responsibility
-   - [ ] Well-defined boundary
-
-2. **Component Content:**
-   - [ ] Accurate description
-   - [ ] Complete responsibility list
-   - [ ] Valid source file references
-   - [ ] Appropriate abstraction level
-
-3. **Relationships:**
-   - [ ] All relationships are valid
-   - [ ] Relationship types are appropriate
-   - [ ] No missing critical relationships
-   - [ ] No redundant relationships (max 2 per pair (avoid relations in which we have sends/returns i.e. ComponentA sends a message to ComponentB and ComponentB returns result to ComponentA))
-
-4. **Documentation Quality:**
-   - [ ] Clear for new developers
-   - [ ] Suitable for diagram visualization
-   - [ ] Follows project type patterns
-
-**Instructions:**
-- Review each checklist item
-- Provide specific feedback for any issues
-- Suggest improvements where needed
-
-**Output:** Validation results with actionable feedback."""
-
-RELATIONSHIPS_VALIDATION = """Validate component relationships for accuracy and completeness.
-
-**Relationship Validation Criteria:**
-
-1. **Accuracy:**
-   - [ ] Relationship type is correct (dependency, composition, inheritance, etc.)
-   - [ ] Direction is accurate (source -> target)
-   - [ ] Both components exist in the analysis
-
-2. **Completeness:**
-   - [ ] All critical relationships are documented
-   - [ ] No orphaned components (unless intentional)
-   - [ ] Relationship strength/importance is appropriate
-
-3. **Quality:**
-   - [ ] Maximum 2 relationships per component pair (avoid relations in which we have sends/returns i.e. ComponentA sends a message to ComponentB and ComponentB returns result to ComponentA)
-   - [ ] Relationships support diagram clarity
-   - [ ] Relationship descriptions are clear
-
-4. **Consistency:**
-   - [ ] Relationships align with project type patterns
-   - [ ] Relationships are correctly represented
-   - [ ] No contradictory relationships
-
-**Instructions:**
-- Validate all relationships against criteria
-- Identify missing relationships
-- Flag inappropriate or redundant relationships
-- Suggest improvements
-
-**Output:** Relationship validation report with specific feedback."""
 
 SYSTEM_META_ANALYSIS_MESSAGE = """You are performing meta-analysis on software project characteristics.
 
@@ -372,15 +288,6 @@ class GPTPromptFactory(AbstractPromptFactory):
     def get_expansion_prompt(self) -> str:
         return EXPANSION_PROMPT
 
-    def get_validator_system_message(self) -> str:
-        return VALIDATOR_SYSTEM_MESSAGE
-
-    def get_component_validation_component(self) -> str:
-        return COMPONENT_VALIDATION_COMPONENT
-
-    def get_relationships_validation(self) -> str:
-        return RELATIONSHIPS_VALIDATION
-
     def get_system_meta_analysis_message(self) -> str:
         return SYSTEM_META_ANALYSIS_MESSAGE
 

{codeboarding-0.13.4 → codeboarding-0.13.6}/agents/prompts/kimi_prompts.py

@@ -110,52 +110,6 @@ Think aloud first (reasoning), then decide:
 Output:
 Provide clear reasoning for expansion decision based on architectural complexity."""
 
-VALIDATOR_SYSTEM_MESSAGE = """You are Kimi, an AI assistant created by Moonshot AI.
-
-Task: Validate analysis quality.
-
-Use tools proactively to verify facts:
-
-1. Review analysis structure and component definitions.
-2. Use getClassHierarchy if component validity is questionable.
-
-Validation criteria:
-- Component clarity and responsibility definition
-- Valid source file references
-- Appropriate relationship mapping
-- Meaningful component naming with code references"""
-
-COMPONENT_VALIDATION_COMPONENT = """You are Kimi, an AI assistant created by Moonshot AI.
-
-Task: Validate component analysis.
-
-Analysis:
-{analysis}
-
-Reason step-by-step:
-
-1. Assess component clarity and purpose definition.
-2. Verify source file completeness and relevance.
-3. Confirm responsibilities are well-defined.
-
-Output:
-Provide validation assessment without additional tool usage."""
-
-RELATIONSHIPS_VALIDATION = """You are Kimi, an AI assistant created by Moonshot AI.
-
-Task: Validate component relationships.
-
-Analysis:
-{analysis}
-
-Think carefully, then verify:
-
-1. Check relationship clarity and necessity.
-2. Verify max 2 relationships per component pair (avoid relations in which we have sends/returns i.e. ComponentA sends a message to ComponentB and ComponentB returns result to ComponentA).
-3. Assess relationship logical consistency.
-
-Output:
-Conclude with VALID or INVALID assessment and specific reasoning."""
 
 SYSTEM_META_ANALYSIS_MESSAGE = """You are Kimi, an AI assistant created by Moonshot AI.
 
@@ -298,15 +252,6 @@ class KimiPromptFactory(AbstractPromptFactory):
     def get_expansion_prompt(self) -> str:
         return EXPANSION_PROMPT
 
-    def get_validator_system_message(self) -> str:
-        return VALIDATOR_SYSTEM_MESSAGE
-
-    def get_component_validation_component(self) -> str:
-        return COMPONENT_VALIDATION_COMPONENT
-
-    def get_relationships_validation(self) -> str:
-        return RELATIONSHIPS_VALIDATION
-
     def get_system_meta_analysis_message(self) -> str:
         return SYSTEM_META_ANALYSIS_MESSAGE
 

{codeboarding-0.13.4 → codeboarding-0.13.6}/agents/prompts/prompt_factory.py

@@ -89,18 +89,6 @@ class PromptFactory:
         else:
             raise AttributeError(f"Prompt method '{method_name}' not found in factory")
 
-    def get_all_prompts(self) -> dict[str, str]:
-        prompts = {}
-        for method_name in dir(self._prompt_factory):
-            if method_name.startswith("get_") and not method_name.startswith("_"):
-                try:
-                    prompt_value = getattr(self._prompt_factory, method_name)()
-                    constant_name = method_name[4:].upper()
-                    prompts[constant_name] = prompt_value
-                except Exception:
-                    continue
-        return prompts
-
 
 # Global factory instance - will be initialized by configuration
 _global_factory: PromptFactory | None = None

{codeboarding-0.13.4 → codeboarding-0.13.6}/agents/validation.py

@@ -46,7 +46,6 @@ class ValidationContext:
     cfg_graphs: dict[str, CallGraph] = field(default_factory=dict)  # For edge checking
     expected_files: set[str] = field(default_factory=set)
     valid_component_names: set[str] = field(default_factory=set)  # For file classification validation
-    existing_component_ids: set[str] = field(default_factory=set)  # For incremental ID-based routing validation
     repo_dir: str | None = None  # For path normalization
     static_analysis: StaticAnalysisResults | None = None  # For qualified name validation
     llm_cluster_analysis: ClusterAnalysis | None = None  # For group name coverage validation
@@ -511,34 +510,3 @@ def _cluster_sets_have_edge(
             if src_cluster in src_set and dst_cluster in dst_set:
                 return True
     return False
-
-
-def _check_edge_between_cluster_sets(
-    src_cluster_ids: list[int],
-    dst_cluster_ids: list[int],
-    cluster_results: dict[str, ClusterResult],
-    cfg_graphs: dict[str, CallGraph],
-    cluster_edge_lookup: dict[str, set[tuple[int, int]]] | None = None,
-) -> bool:
-    """
-    Check if there's an edge between any pair of clusters from two sets.
-
-    Args:
-        src_cluster_ids: Source cluster IDs
-        dst_cluster_ids: Destination cluster IDs
-        cluster_results: dict mapping language -> ClusterResult
-        cfg_graphs: dict mapping language -> CallGraph
-        cluster_edge_lookup: Optional precomputed (src_cluster, dst_cluster) edges per language
-
-    Returns:
-        True if any edge exists between the cluster sets
-    """
-    if not src_cluster_ids or not dst_cluster_ids:
-        return False
-
-    if cluster_edge_lookup is None:
-        cluster_edge_lookup = _build_cluster_edge_lookup(cluster_results, cfg_graphs)
-
-    return _cluster_sets_have_edge(src_cluster_ids, dst_cluster_ids, cluster_edge_lookup) or _cluster_sets_have_edge(
-        dst_cluster_ids, src_cluster_ids, cluster_edge_lookup
-    )

{codeboarding-0.13.4 → codeboarding-0.13.6/codeboarding.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codeboarding
-Version: 0.13.4
+Version: 0.13.6
 Summary: Interactive Diagrams for Code
 Author: CodeBoarding Team
 License-Expression: MIT

{codeboarding-0.13.4 → codeboarding-0.13.6}/codeboarding.egg-info/SOURCES.txt

@@ -160,7 +160,9 @@ static_analyzer/engine/hierarchy_builder.py
 static_analyzer/engine/language_adapter.py
 static_analyzer/engine/lsp_client.py
 static_analyzer/engine/lsp_constants.py
+static_analyzer/engine/lsp_recycler.py
 static_analyzer/engine/models.py
+static_analyzer/engine/process_memory.py
 static_analyzer/engine/progress.py
 static_analyzer/engine/protocols.py
 static_analyzer/engine/result_converter.py

{codeboarding-0.13.4 → codeboarding-0.13.6}/diagram_analysis/cluster_snapshot.py

@@ -84,7 +84,7 @@ def _entries_from_cfg_cache(
 
 
 def snapshot_from_cluster_results(cluster_results: dict[str, ClusterResult]) -> ClusterSnapshot:
-    """Build a snapshot directly from cluster results (test helper).
+    """Convert lightweight ``ClusterResult`` fixtures into snapshots for tests.
 
     ``member_files`` is left empty since ``ClusterResult`` has no per-qname
     file map; tests needing diff-scoping must populate it manually.