Merge pull request 'development' (#372) from development into main

Reviewed-on: #372

.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Project management plugins with Gitea and NetBox integrations",
-    "version": "5.7.1"
+    "version": "5.6.0"
   },
   "plugins": [
     {
@@ -155,7 +155,7 @@
     },
     {
       "name": "data-platform",
-      "version": "1.3.0",
+      "version": "1.2.0",
       "description": "Data engineering tools with pandas, PostgreSQL/PostGIS, and dbt integration",
       "source": "./plugins/data-platform",
       "author": {

CHANGELOG.md

@@ -4,34 +4,6 @@ All notable changes to the Leo Claude Marketplace will be documented in this fil
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
-## [5.7.1] - 2026-02-02
-
-### Added
-- **contract-validator**: New `validate_workflow_integration` MCP tool — validates domain plugins expose required advisory interfaces (gate command, review command, advisory agent)
-- **contract-validator**: New `MISSING_INTEGRATION` issue type for workflow integration validation
-
-### Fixed
-- `scripts/setup.sh` banner version updated from v5.1.0 to v5.7.1
-
-### Reverted
-- **marketplace.json**: Removed `integrates_with` field — Claude Code schema does not support custom plugin fields (causes marketplace load failure)
-
----
-
-## [5.7.0] - 2026-02-02
-
-### Added
-- **data-platform**: New `data-advisor` agent for data integrity, schema, and dbt compliance validation
-- **data-platform**: New `data-integrity-audit.md` skill defining audit rules, severity levels, and scanning strategies
-- **data-platform**: New `/data-gate` command for binary pass/fail data integrity gates (projman integration)
-- **data-platform**: New `/data-review` command for comprehensive data integrity audits
-
-### Changed
-- Domain Advisory Pattern now fully operational for both Viz and Data domains
-- projman orchestrator `Domain/Data` gates now resolve to live `/data-gate` command (previously fell through to "gate unavailable" warning)
-
----
-
 ## [5.6.0] - 2026-02-01
 
 ### Added

README.md

@@ -1,4 +1,4 @@
-# Leo Claude Marketplace - v5.7.1
+# Leo Claude Marketplace - v5.6.0
 
 A collection of Claude Code plugins for project management, infrastructure automation, and development workflows.
 
@@ -153,7 +153,7 @@ The marketplace supports cross-plugin domain advisory integration:
 | Domain | Plugin | Gate Command |
 |--------|--------|--------------|
 | Visualization | viz-platform | `/design-gate` |
-| Data | data-platform | `/data-gate` |
+| Data (planned) | data-platform | `/data-gate` |
 
 ## MCP Servers
 
@@ -215,7 +215,7 @@ Cross-plugin compatibility validation tools.
 | Category | Tools |
 |----------|-------|
 | Parse | `parse_plugin_interface`, `parse_claude_md_agents` |
-| Validation | `validate_compatibility`, `validate_agent_refs`, `validate_data_flow`, `validate_workflow_integration` |
+| Validation | `validate_compatibility`, `validate_agent_refs`, `validate_data_flow` |
 | Report | `generate_compatibility_report`, `list_issues` |
 
 ## Installation

docs/COMMANDS-CHEATSHEET.md

@@ -92,11 +92,7 @@ Quick reference for all commands in the Leo Claude Marketplace.
 | **viz-platform** | `/chart-export` | | X | Export charts to PNG, SVG, PDF via kaleido |
 | **viz-platform** | `/accessibility-check` | | X | Color blind validation (WCAG contrast ratios) |
 | **viz-platform** | `/breakpoints` | | X | Configure responsive layout breakpoints |
-| **viz-platform** | `/design-review` | | X | Detailed design system audits |
-| **viz-platform** | `/design-gate` | | X | Binary pass/fail design system validation gates |
 | **viz-platform** | *SessionStart hook* | X | | Checks DMC version (non-blocking warning) |
-| **data-platform** | `/data-review` | | X | Comprehensive data integrity audits |
-| **data-platform** | `/data-gate` | | X | Binary pass/fail data integrity gates |
 | **contract-validator** | `/validate-contracts` | | X | Full marketplace compatibility validation |
 | **contract-validator** | `/check-agent` | | X | Validate single agent definition |
 | **contract-validator** | `/list-interfaces` | | X | Show all plugin interfaces |
@@ -298,4 +294,4 @@ Ensure credentials are configured in `~/.config/claude/gitea.env`, `~/.config/cl
 
 ---
 
-*Last Updated: 2026-02-02*
+*Last Updated: 2026-01-30*

docs/CONFIGURATION.md

@@ -398,7 +398,6 @@ PR_REVIEW_AUTO_SUBMIT=false
 | **code-sentinel** | None | None | None needed |
 | **project-hygiene** | None | None | None needed |
 | **claude-config-maintainer** | None | None | None needed |
-| **contract-validator** | None | None | `/initial-setup` |
 
 ---
 

mcp-servers/contract-validator/mcp_server/server.py

@@ -131,24 +131,6 @@ class ContractValidatorMCPServer:
                         "required": ["agent_name", "claude_md_path"]
                     }
                 ),
-                Tool(
-                    name="validate_workflow_integration",
-                    description="Validate that a domain plugin exposes the required advisory interfaces (gate command, review command, advisory agent) expected by projman's domain-consultation skill",
-                    inputSchema={
-                        "type": "object",
-                        "properties": {
-                            "plugin_path": {
-                                "type": "string",
-                                "description": "Path to the domain plugin directory"
-                            },
-                            "domain_label": {
-                                "type": "string",
-                                "description": "The Domain/* label it claims to handle, e.g. Domain/Viz"
-                            }
-                        },
-                        "required": ["plugin_path", "domain_label"]
-                    }
-                ),
                 # Report tools (to be implemented in #188)
                 Tool(
                     name="generate_compatibility_report",
@@ -216,8 +198,6 @@ class ContractValidatorMCPServer:
                     result = await self._validate_agent_refs(**arguments)
                 elif name == "validate_data_flow":
                     result = await self._validate_data_flow(**arguments)
-                elif name == "validate_workflow_integration":
-                    result = await self._validate_workflow_integration(**arguments)
                 elif name == "generate_compatibility_report":
                     result = await self._generate_compatibility_report(**arguments)
                 elif name == "list_issues":
@@ -261,10 +241,6 @@ class ContractValidatorMCPServer:
         """Validate agent data flow"""
         return await self.validation_tools.validate_data_flow(agent_name, claude_md_path)
 
-    async def _validate_workflow_integration(self, plugin_path: str, domain_label: str) -> dict:
-        """Validate domain plugin exposes required advisory interfaces"""
-        return await self.validation_tools.validate_workflow_integration(plugin_path, domain_label)
-
     # Report tool implementations (Issue #188)
 
     async def _generate_compatibility_report(self, marketplace_path: str, format: str = "markdown") -> dict:

mcp-servers/contract-validator/mcp_server/validation_tools.py

@@ -26,7 +26,6 @@ class IssueType(str, Enum):
     OPTIONAL_DEPENDENCY = "optional_dependency"
     UNDECLARED_OUTPUT = "undeclared_output"
     INVALID_SEQUENCE = "invalid_sequence"
-    MISSING_INTEGRATION = "missing_integration"
 
 
 class ValidationIssue(BaseModel):
@@ -66,17 +65,6 @@ class DataFlowResult(BaseModel):
     issues: list[ValidationIssue] = []
 
 
-class WorkflowIntegrationResult(BaseModel):
-    """Result of workflow integration validation for domain plugins"""
-    plugin_name: str
-    domain_label: str
-    valid: bool
-    gate_command_found: bool
-    review_command_found: bool
-    advisory_agent_found: bool
-    issues: list[ValidationIssue] = []
-
-
 class ValidationTools:
     """Tools for validating plugin compatibility and agent references"""
 
@@ -348,107 +336,3 @@ class ValidationTools:
         )
 
         return result.model_dump()
-
-    async def validate_workflow_integration(self, plugin_path: str, domain_label: str) -> dict:
-        """
-        Validate that a domain plugin exposes required advisory interfaces.
-
-        Checks for:
-        - Gate command (e.g., /design-gate, /data-gate) - REQUIRED
-        - Review command (e.g., /design-review, /data-review) - recommended
-        - Advisory agent referencing the domain label - recommended
-
-        Args:
-            plugin_path: Path to the domain plugin directory
-            domain_label: The Domain/* label it claims to handle (e.g., Domain/Viz)
-
-        Returns:
-            Validation result with found interfaces and issues
-        """
-        plugin_path_obj = Path(plugin_path)
-        issues = []
-
-        # Extract plugin name from path
-        plugin_name = plugin_path_obj.name
-        if not plugin_path_obj.exists():
-            return {
-                "error": f"Plugin directory not found: {plugin_path}",
-                "plugin_path": plugin_path,
-                "domain_label": domain_label
-            }
-
-        # Extract domain short name from label (e.g., "Domain/Viz" -> "viz", "Domain/Data" -> "data")
-        domain_short = domain_label.split("/")[-1].lower() if "/" in domain_label else domain_label.lower()
-
-        # Check for gate command
-        commands_dir = plugin_path_obj / "commands"
-        gate_command_found = False
-        gate_patterns = ["pass", "fail", "PASS", "FAIL", "Binary pass/fail", "gate"]
-
-        if commands_dir.exists():
-            for cmd_file in commands_dir.glob("*.md"):
-                if "gate" in cmd_file.name.lower():
-                    # Verify it's actually a gate command by checking content
-                    content = cmd_file.read_text()
-                    if any(pattern in content for pattern in gate_patterns):
-                        gate_command_found = True
-                        break
-
-        if not gate_command_found:
-            issues.append(ValidationIssue(
-                severity=IssueSeverity.ERROR,
-                issue_type=IssueType.MISSING_INTEGRATION,
-                message=f"Plugin '{plugin_name}' lacks a gate command for domain '{domain_label}'",
-                location=str(commands_dir),
-                suggestion=f"Create commands/{domain_short}-gate.md with binary PASS/FAIL output"
-            ))
-
-        # Check for review command
-        review_command_found = False
-        if commands_dir.exists():
-            for cmd_file in commands_dir.glob("*.md"):
-                if "review" in cmd_file.name.lower() and "gate" not in cmd_file.name.lower():
-                    review_command_found = True
-                    break
-
-        if not review_command_found:
-            issues.append(ValidationIssue(
-                severity=IssueSeverity.WARNING,
-                issue_type=IssueType.MISSING_INTEGRATION,
-                message=f"Plugin '{plugin_name}' lacks a review command for domain '{domain_label}'",
-                location=str(commands_dir),
-                suggestion=f"Create commands/{domain_short}-review.md for detailed audits"
-            ))
-
-        # Check for advisory agent
-        agents_dir = plugin_path_obj / "agents"
-        advisory_agent_found = False
-
-        if agents_dir.exists():
-            for agent_file in agents_dir.glob("*.md"):
-                content = agent_file.read_text()
-                # Check if agent references the domain label or gate command
-                if domain_label in content or f"{domain_short}-gate" in content.lower() or "advisor" in agent_file.name.lower() or "reviewer" in agent_file.name.lower():
-                    advisory_agent_found = True
-                    break
-
-        if not advisory_agent_found:
-            issues.append(ValidationIssue(
-                severity=IssueSeverity.WARNING,
-                issue_type=IssueType.MISSING_INTEGRATION,
-                message=f"Plugin '{plugin_name}' lacks an advisory agent for domain '{domain_label}'",
-                location=str(agents_dir) if agents_dir.exists() else str(plugin_path_obj),
-                suggestion=f"Create agents/{domain_short}-advisor.md referencing '{domain_label}'"
-            ))
-
-        result = WorkflowIntegrationResult(
-            plugin_name=plugin_name,
-            domain_label=domain_label,
-            valid=gate_command_found,  # Only gate is required for validity
-            gate_command_found=gate_command_found,
-            review_command_found=review_command_found,
-            advisory_agent_found=advisory_agent_found,
-            issues=issues
-        )
-
-        return result.model_dump()

mcp-servers/contract-validator/tests/test_validation_tools.py

@@ -254,153 +254,3 @@ async def test_validate_data_flow_missing_producer(validation_tools, tmp_path):
     # Should have warning about missing producer
     warning_issues = [i for i in result["issues"] if i["severity"].value == "warning"]
     assert len(warning_issues) > 0
-
-
-# --- Workflow Integration Tests ---
-
-@pytest.fixture
-def domain_plugin_complete(tmp_path):
-    """Create a complete domain plugin with gate, review, and advisory agent"""
-    plugin_dir = tmp_path / "viz-platform"
-    plugin_dir.mkdir()
-    (plugin_dir / ".claude-plugin").mkdir()
-    (plugin_dir / "commands").mkdir()
-    (plugin_dir / "agents").mkdir()
-
-    # Gate command with PASS/FAIL pattern
-    gate_cmd = plugin_dir / "commands" / "design-gate.md"
-    gate_cmd.write_text("""# /design-gate
-
-Binary pass/fail validation gate for design system compliance.
-
-## Output
-
-- **PASS**: All design system checks passed
-- **FAIL**: Design system violations detected
-""")
-
-    # Review command
-    review_cmd = plugin_dir / "commands" / "design-review.md"
-    review_cmd.write_text("""# /design-review
-
-Comprehensive design system audit.
-""")
-
-    # Advisory agent
-    agent = plugin_dir / "agents" / "design-reviewer.md"
-    agent.write_text("""# design-reviewer
-
-Design system compliance auditor.
-
-Handles issues with `Domain/Viz` label.
-""")
-
-    return str(plugin_dir)
-
-
-@pytest.fixture
-def domain_plugin_missing_gate(tmp_path):
-    """Create domain plugin with review and agent but no gate command"""
-    plugin_dir = tmp_path / "data-platform"
-    plugin_dir.mkdir()
-    (plugin_dir / ".claude-plugin").mkdir()
-    (plugin_dir / "commands").mkdir()
-    (plugin_dir / "agents").mkdir()
-
-    # Review command (but no gate)
-    review_cmd = plugin_dir / "commands" / "data-review.md"
-    review_cmd.write_text("""# /data-review
-
-Data integrity audit.
-""")
-
-    # Advisory agent
-    agent = plugin_dir / "agents" / "data-advisor.md"
-    agent.write_text("""# data-advisor
-
-Data integrity advisor for Domain/Data issues.
-""")
-
-    return str(plugin_dir)
-
-
-@pytest.fixture
-def domain_plugin_minimal(tmp_path):
-    """Create minimal plugin with no commands or agents"""
-    plugin_dir = tmp_path / "minimal-plugin"
-    plugin_dir.mkdir()
-    (plugin_dir / ".claude-plugin").mkdir()
-
-    readme = plugin_dir / "README.md"
-    readme.write_text("# Minimal Plugin\n\nNo commands or agents.")
-
-    return str(plugin_dir)
-
-
-@pytest.mark.asyncio
-async def test_validate_workflow_integration_complete(validation_tools, domain_plugin_complete):
-    """Test complete domain plugin returns valid with all interfaces found"""
-    result = await validation_tools.validate_workflow_integration(
-        domain_plugin_complete,
-        "Domain/Viz"
-    )
-
-    assert "error" not in result
-    assert result["valid"] is True
-    assert result["gate_command_found"] is True
-    assert result["review_command_found"] is True
-    assert result["advisory_agent_found"] is True
-    assert len(result["issues"]) == 0
-
-
-@pytest.mark.asyncio
-async def test_validate_workflow_integration_missing_gate(validation_tools, domain_plugin_missing_gate):
-    """Test plugin missing gate command returns invalid with ERROR"""
-    result = await validation_tools.validate_workflow_integration(
-        domain_plugin_missing_gate,
-        "Domain/Data"
-    )
-
-    assert "error" not in result
-    assert result["valid"] is False
-    assert result["gate_command_found"] is False
-    assert result["review_command_found"] is True
-    assert result["advisory_agent_found"] is True
-
-    # Should have one ERROR for missing gate
-    error_issues = [i for i in result["issues"] if i["severity"].value == "error"]
-    assert len(error_issues) == 1
-    assert "gate" in error_issues[0]["message"].lower()
-
-
-@pytest.mark.asyncio
-async def test_validate_workflow_integration_minimal(validation_tools, domain_plugin_minimal):
-    """Test minimal plugin returns invalid with multiple issues"""
-    result = await validation_tools.validate_workflow_integration(
-        domain_plugin_minimal,
-        "Domain/Test"
-    )
-
-    assert "error" not in result
-    assert result["valid"] is False
-    assert result["gate_command_found"] is False
-    assert result["review_command_found"] is False
-    assert result["advisory_agent_found"] is False
-
-    # Should have one ERROR (gate) and two WARNINGs (review, agent)
-    error_issues = [i for i in result["issues"] if i["severity"].value == "error"]
-    warning_issues = [i for i in result["issues"] if i["severity"].value == "warning"]
-    assert len(error_issues) == 1
-    assert len(warning_issues) == 2
-
-
-@pytest.mark.asyncio
-async def test_validate_workflow_integration_nonexistent_plugin(validation_tools, tmp_path):
-    """Test error when plugin directory doesn't exist"""
-    result = await validation_tools.validate_workflow_integration(
-        str(tmp_path / "nonexistent"),
-        "Domain/Test"
-    )
-
-    assert "error" in result
-    assert "not found" in result["error"].lower()

plugins/contract-validator/commands/validate-contracts.md

@@ -30,7 +30,6 @@
    - Use `validate_compatibility` for pairwise checks
    - Use `validate_agent_refs` for CLAUDE.md agents
    - Use `validate_data_flow` for data sequences
-   - Use `validate_workflow_integration` for domain plugin advisory interfaces
 
 5. **Generate report**:
    - Use `generate_compatibility_report` for full report

plugins/contract-validator/skills/mcp-tools-reference.md

@@ -16,7 +16,6 @@ Available MCP tools for contract-validator operations.
 | `validate_compatibility` | Check two plugins for conflicts |
 | `validate_agent_refs` | Check agent tool references exist |
 | `validate_data_flow` | Verify data flow through agent sequence |
-| `validate_workflow_integration` | Check domain plugin exposes required advisory interfaces |
 
 ### Report Tools
 | Tool | Description |
@@ -54,13 +53,6 @@ Available MCP tools for contract-validator operations.
 3. Build Mermaid diagram from results
 ```
 
-### Workflow Integration Check
-```
-1. validate_workflow_integration(plugin_path, domain_label)  # Check single domain plugin
-2. For each domain in domain-consultation.md detection rules:
-     validate_workflow_integration(domain_plugin_path, domain_label)
-```
-
 ## Error Handling
 
 If MCP tools fail:

plugins/contract-validator/skills/validation-rules.md

@@ -30,13 +30,6 @@ Rules for validating plugin compatibility and agent definitions.
 3. Check for orphaned data references
 4. Ensure required data is available at each step
 
-### Workflow Integration Checks
-1. Gate command exists in plugin's commands/ directory
-2. Gate command produces binary PASS/FAIL output
-3. Review command exists (WARNING if missing, not ERROR)
-4. Advisory agent exists referencing the domain label
-- Severity: ERROR for missing gate, WARNING for missing review/agent
-
 ## Severity Levels
 
 | Level | Meaning | Action |
@@ -53,8 +46,6 @@ Rules for validating plugin compatibility and agent definitions.
 | Data flow gap | Producer not called before consumer | Reorder workflow steps |
 | Name conflict | Two plugins use same command | Rename one command |
 | Orphan reference | Data produced but never consumed | Remove or use the data |
-| Missing gate command | Domain plugin lacks /X-gate command | Create commands/{domain}-gate.md |
-| Missing advisory agent | Domain plugin has no reviewer agent | Create agents/{domain}-advisor.md |
 
 ## MCP Tools
 
@@ -63,5 +54,4 @@ Rules for validating plugin compatibility and agent definitions.
 | `validate_compatibility` | Check two plugins for conflicts |
 | `validate_agent_refs` | Check agent tool references |
 | `validate_data_flow` | Verify data flow sequences |
-| `validate_workflow_integration` | Check domain plugin advisory interfaces |
 | `list_issues` | Filter issues by severity or type |

plugins/data-platform/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "data-platform",
-  "version": "1.3.0",
+  "version": "1.1.0",
   "description": "Data engineering tools with pandas, PostgreSQL/PostGIS, and dbt integration",
   "author": {
     "name": "Leo Miranda",

plugins/data-platform/agents/data-advisor.md

@@ -1,320 +0,0 @@
----
-agent: data-advisor
-description: Reviews code for data integrity, schema validity, and dbt compliance using data-platform MCP tools
-triggers:
-  - /data-review command
-  - /data-gate command
-  - projman orchestrator domain gate
----
-
-# Data Advisor Agent
-
-You are a strict data integrity auditor. Your role is to review code for proper schema usage, dbt compliance, lineage integrity, and data quality standards.
-
-## Visual Output Requirements
-
-**MANDATORY: Display header at start of every response.**
-
-```
-+----------------------------------------------------------------------+
-|  DATA-PLATFORM - Data Advisor                                         |
-|  [Target Path]                                                        |
-+----------------------------------------------------------------------+
-```
-
-## Trigger Conditions
-
-Activate this agent when:
-- User runs `/data-review <path>`
-- User runs `/data-gate <path>`
-- Projman orchestrator requests data domain gate check
-- Code review includes database operations, dbt models, or data pipelines
-
-## Skills to Load
-
-- skills/data-integrity-audit.md
-- skills/mcp-tools-reference.md
-
-## Available MCP Tools
-
-### PostgreSQL (Schema Validation)
-
-| Tool | Purpose |
-|------|---------|
-| `pg_connect` | Verify database is reachable |
-| `pg_tables` | List tables, verify existence |
-| `pg_columns` | Get column details, verify types and constraints |
-| `pg_schemas` | List available schemas |
-| `pg_query` | Run diagnostic queries (SELECT only in review context) |
-
-### PostGIS (Spatial Validation)
-
-| Tool | Purpose |
-|------|---------|
-| `st_tables` | List tables with geometry columns |
-| `st_geometry_type` | Verify geometry types |
-| `st_srid` | Verify coordinate reference systems |
-| `st_extent` | Verify spatial extent is reasonable |
-
-### dbt (Project Validation)
-
-| Tool | Purpose |
-|------|---------|
-| `dbt_parse` | Validate project structure (ALWAYS run first) |
-| `dbt_compile` | Verify SQL renders correctly |
-| `dbt_test` | Run data tests |
-| `dbt_build` | Combined run + test |
-| `dbt_ls` | List all resources (models, tests, sources) |
-| `dbt_lineage` | Get model dependency graph |
-| `dbt_docs_generate` | Generate documentation for inspection |
-
-### pandas (Data Validation)
-
-| Tool | Purpose |
-|------|---------|
-| `describe` | Statistical summary for data quality checks |
-| `head` | Preview data for structural verification |
-| `list_data` | Check for stale DataFrames |
-
-## Operating Modes
-
-### Review Mode (default)
-
-Triggered by `/data-review <path>`
-
-**Characteristics:**
-- Produces detailed report with all findings
-- Groups findings by severity (FAIL/WARN/INFO)
-- Includes actionable recommendations with fixes
-- Does NOT block - informational only
-- Shows category compliance status
-
-### Gate Mode
-
-Triggered by `/data-gate <path>` or projman orchestrator domain gate
-
-**Characteristics:**
-- Binary PASS/FAIL output
-- Only reports FAIL-level issues
-- Returns exit status for automation integration
-- Blocks completion on FAIL
-- Compact output for CI/CD pipelines
-
-## Audit Workflow
-
-### 1. Receive Target Path
-
-Accept file or directory path from command invocation.
-
-### 2. Determine Scope
-
-Analyze target to identify what type of data work is present:
-
-| Pattern | Type | Checks to Run |
-|---------|------|---------------|
-| `dbt_project.yml` present | dbt project | Full dbt validation |
-| `*.sql` files in dbt path | dbt models | Model compilation, lineage |
-| `*.py` with `pg_query`/`pg_execute` | Database operations | Schema validation |
-| `schema.yml` files | dbt schemas | Schema drift detection |
-| Migration files (`*_migration.sql`) | Schema changes | Full PostgreSQL + dbt checks |
-
-### 3. Run Database Checks (if applicable)
-
-```
-1. pg_connect → verify database reachable
-   If fails: WARN, continue with file-based checks
-
-2. pg_tables → verify expected tables exist
-   If missing: FAIL
-
-3. pg_columns on affected tables → verify types
-   If mismatch: FAIL
-```
-
-### 4. Run dbt Checks (if applicable)
-
-```
-1. dbt_parse → validate project
-   If fails: FAIL immediately (project broken)
-
-2. dbt_ls → catalog all resources
-   Record models, tests, sources
-
-3. dbt_lineage on target models → check integrity
-   Orphaned refs: FAIL
-
-4. dbt_compile on target models → verify SQL
-   Compilation errors: FAIL
-
-5. dbt_test --select <targets> → run tests
-   Test failures: FAIL
-
-6. Cross-reference tests → models without tests
-   Missing tests: WARN
-```
-
-### 5. Run PostGIS Checks (if applicable)
-
-```
-1. st_tables → list spatial tables
-   If none found: skip PostGIS checks
-
-2. st_srid → verify SRID correct
-   Unexpected SRID: FAIL
-
-3. st_geometry_type → verify expected types
-   Wrong type: WARN
-
-4. st_extent → sanity check bounding box
-   Unreasonable extent: FAIL
-```
-
-### 6. Scan Python Code (manual patterns)
-
-For Python files with database operations:
-
-| Pattern | Issue | Severity |
-|---------|-------|----------|
-| `f"SELECT * FROM {table}"` | SQL injection risk | WARN |
-| `f"INSERT INTO {table}"` | Unparameterized mutation | WARN |
-| `pg_execute` without WHERE in DELETE/UPDATE | Dangerous mutation | WARN |
-| Hardcoded connection strings | Credential exposure | WARN |
-
-### 7. Generate Report
-
-Output format depends on operating mode (see templates in `skills/data-integrity-audit.md`).
-
-## Report Formats
-
-### Gate Mode Output
-
-**PASS:**
-```
-DATA GATE: PASS
-No blocking data integrity violations found.
-```
-
-**FAIL:**
-```
-DATA GATE: FAIL
-
-Blocking Issues (2):
-1. dbt/models/staging/stg_census.sql - Compilation error: column 'census_yr' not found
-   Fix: Column was renamed to 'census_year' in source table. Update model.
-
-2. portfolio_app/toronto/loaders/census.py:67 - References table 'census_raw' which does not exist
-   Fix: Table was renamed to 'census_demographics' in migration 003.
-
-Run /data-review for full audit report.
-```
-
-### Review Mode Output
-
-```
-+----------------------------------------------------------------------+
-|  DATA-PLATFORM - Data Integrity Audit                                 |
-|  /path/to/project                                                     |
-+----------------------------------------------------------------------+
-
-Target: /path/to/project
-Scope: 12 files scanned, 8 models checked, 3 tables verified
-
-FINDINGS
-
-FAIL (2)
-  1. [dbt/models/staging/stg_census.sql] Compilation error
-     Error: column 'census_yr' does not exist
-     Fix: Column was renamed to 'census_year'. Update SELECT clause.
-
-  2. [portfolio_app/loaders/census.py:67] Missing table reference
-     Error: Table 'census_raw' does not exist
-     Fix: Table renamed to 'census_demographics' in migration 003.
-
-WARN (3)
-  1. [dbt/models/marts/dim_neighbourhoods.sql] Missing dbt test
-     Issue: No unique test on neighbourhood_id
-     Suggestion: Add unique test to schema.yml
-
-  2. [portfolio_app/toronto/queries.py:45] Hardcoded SQL
-     Issue: f"SELECT * FROM {table_name}" without parameterization
-     Suggestion: Use parameterized queries
-
-  3. [dbt/models/staging/stg_legacy.sql] Orphaned model
-     Issue: No downstream consumers or exposures
-     Suggestion: Remove if unused or add to exposure
-
-INFO (1)
-  1. [dbt/models/marts/fct_demographics.sql] Documentation gap
-     Note: Model description missing in schema.yml
-     Suggestion: Add description for discoverability
-
-SUMMARY
-  Schema:   2 issues
-  Lineage:  Intact
-  dbt:      1 failure
-  PostGIS:  Not applicable
-
-VERDICT: FAIL (2 blocking issues)
-```
-
-## Severity Definitions
-
-| Level | Criteria | Action Required |
-|-------|----------|-----------------|
-| **FAIL** | dbt parse/compile fails, missing tables/columns, type mismatches, broken lineage, invalid SRID | Must fix before completion |
-| **WARN** | Missing tests, hardcoded SQL, schema drift, orphaned models | Should fix |
-| **INFO** | Documentation gaps, optimization opportunities | Consider for improvement |
-
-## Error Handling
-
-| Error | Response |
-|-------|----------|
-| Database not reachable | WARN: "PostgreSQL unavailable, skipping schema checks" - continue |
-| No dbt_project.yml | Skip dbt checks silently - not an error |
-| No PostGIS tables | Skip PostGIS checks silently - not an error |
-| MCP tool fails | WARN: "Tool {name} failed: {error}" - continue with remaining |
-| Empty path | PASS: "No data artifacts found in target path" |
-| Invalid path | Error: "Path not found: {path}" |
-
-## Integration with projman
-
-When called as a domain gate by projman orchestrator:
-
-1. Receive path from orchestrator (changed files for the issue)
-2. Determine what type of data work changed
-3. Run audit in gate mode
-4. Return structured result:
-   ```
-   Gate: data
-   Status: PASS | FAIL
-   Blocking: N issues
-   Summary: Brief description
-   ```
-5. Orchestrator decides whether to proceed based on gate status
-
-## Example Interactions
-
-**User**: `/data-review dbt/models/staging/`
-**Agent**:
-1. Scans all .sql files in staging/
-2. Runs dbt_parse to validate project
-3. Runs dbt_compile on each model
-4. Checks lineage for orphaned refs
-5. Cross-references test coverage
-6. Returns detailed report
-
-**User**: `/data-gate portfolio_app/toronto/`
-**Agent**:
-1. Scans for Python files with pg_query/pg_execute
-2. Checks if referenced tables exist
-3. Validates column types
-4. Returns PASS if clean, FAIL with blocking issues if not
-5. Compact output for automation
-
-## Communication Style
-
-Technical and precise. Report findings with exact locations, specific violations, and actionable fixes:
-
-- "Table `census_demographics` column `population` is `varchar(50)` in PostgreSQL but referenced as `integer` in `stg_census.sql` line 14. This will cause a runtime cast error."
-- "Model `dim_neighbourhoods` has no `unique` test on `neighbourhood_id`. Add to `schema.yml` to prevent duplicates."
-- "Spatial extent for `toronto_boundaries` shows global coordinates (-180 to 180). Expected Toronto bbox (~-79.6 to -79.1 longitude). Likely missing ST_Transform or wrong SRID on import."

plugins/data-platform/commands/data-gate.md

@@ -1,104 +0,0 @@
----
-description: Data integrity compliance gate (pass/fail) for sprint execution
-arguments:
-  - name: path
-    description: File or directory to validate
-    required: true
----
-
-# /data-gate
-
-Binary pass/fail validation for data integrity compliance. Used by projman orchestrator during sprint execution to gate issue completion.
-
-## Usage
-
-```
-/data-gate <path>
-```
-
-**Examples:**
-```
-/data-gate ./dbt/models/staging/
-/data-gate ./portfolio_app/toronto/parsers/
-/data-gate ./dbt/
-```
-
-## What It Does
-
-1. **Activates** the `data-advisor` agent in gate mode
-2. **Loads** the `skills/data-integrity-audit.md` skill
-3. **Determines scope** from target path:
-   - dbt project directory: full dbt validation (parse, compile, test, lineage)
-   - Python files with database operations: schema validation
-   - SQL files: dbt model validation
-   - Mixed: all applicable checks
-4. **Checks only FAIL-level violations:**
-   - dbt parse failures (project broken)
-   - dbt compilation errors (SQL invalid)
-   - Missing tables/columns referenced in code
-   - Data type mismatches that cause runtime errors
-   - Broken lineage (orphaned model references)
-   - PostGIS SRID mismatches
-5. **Returns binary result:**
-   - `PASS` - No blocking violations found
-   - `FAIL` - One or more blocking violations
-
-## Output
-
-### On PASS
-```
-DATA GATE: PASS
-No blocking data integrity violations found.
-```
-
-### On FAIL
-```
-DATA GATE: FAIL
-
-Blocking Issues (2):
-1. dbt/models/staging/stg_census.sql - Compilation error: column 'census_yr' not found
-   Fix: Column was renamed to 'census_year' in source table. Update model.
-
-2. portfolio_app/toronto/loaders/census.py:67 - References table 'census_raw' which does not exist
-   Fix: Table was renamed to 'census_demographics' in migration 003.
-
-Run /data-review for full audit report.
-```
-
-## Integration with projman
-
-This command is automatically invoked by the projman orchestrator when:
-
-1. An issue has the `Domain/Data` label
-2. The orchestrator is about to mark the issue as complete
-3. The orchestrator passes the path of changed files
-
-**Gate behavior:**
-- PASS: Issue can be marked complete
-- FAIL: Issue stays open, blocker comment added with failure details
-
-## Differences from /data-review
-
-| Aspect | /data-gate | /data-review |
-|--------|------------|--------------|
-| Output | Binary PASS/FAIL | Detailed report with all severities |
-| Severity | FAIL only | FAIL + WARN + INFO |
-| Purpose | Automation gate | Human review |
-| Verbosity | Minimal | Comprehensive |
-| Speed | Skips INFO checks | Full scan |
-
-## When to Use
-
-- **Sprint execution**: Automatic quality gates via projman
-- **CI/CD pipelines**: Automated data integrity checks
-- **Quick validation**: Fast pass/fail without full report
-- **Pre-merge checks**: Verify data changes before integration
-
-For detailed findings including warnings and suggestions, use `/data-review` instead.
-
-## Requirements
-
-- data-platform MCP server must be running
-- For dbt checks: dbt project must be configured (auto-detected via `dbt_project.yml`)
-- For PostgreSQL checks: connection configured in `~/.config/claude/postgres.env`
-- If database or dbt unavailable: applicable checks skipped with warning (non-blocking degradation)

plugins/data-platform/commands/data-review.md

@@ -1,149 +0,0 @@
----
-description: Audit data integrity, schema validity, and dbt compliance
-arguments:
-  - name: path
-    description: File, directory, or dbt project to audit
-    required: true
----
-
-# /data-review
-
-Comprehensive data integrity audit producing a detailed report with findings at all severity levels. For human review and standalone codebase auditing.
-
-## Usage
-
-```
-/data-review <path>
-```
-
-**Examples:**
-```
-/data-review ./dbt/
-/data-review ./portfolio_app/toronto/
-/data-review ./dbt/models/marts/
-```
-
-## What It Does
-
-1. **Activates** the `data-advisor` agent in review mode
-2. **Scans target path** to determine scope:
-   - Identifies dbt project files (.sql models, schema.yml, sources.yml)
-   - Identifies Python files with database operations
-   - Identifies migration files
-   - Identifies PostGIS usage
-3. **Runs all check categories:**
-   - Schema validity (PostgreSQL tables, columns, types)
-   - dbt project health (parse, compile, test, lineage)
-   - PostGIS compliance (SRID, geometry types, extent)
-   - Data type consistency
-   - Code patterns (unsafe SQL, hardcoded queries)
-4. **Produces detailed report** with all severity levels (FAIL, WARN, INFO)
-5. **Provides actionable recommendations** for each finding
-
-## Output Format
-
-```
-+----------------------------------------------------------------------+
-|  DATA-PLATFORM - Data Integrity Audit                                 |
-|  /path/to/project                                                     |
-+----------------------------------------------------------------------+
-
-Target: /path/to/project
-Scope: N files scanned, N models checked, N tables verified
-
-FINDINGS
-
-FAIL (N)
-  1. [location] violation description
-     Fix: actionable fix
-
-WARN (N)
-  1. [location] warning description
-     Suggestion: improvement suggestion
-
-INFO (N)
-  1. [location] info description
-     Note: context
-
-SUMMARY
-  Schema:   Valid | N issues
-  Lineage:  Intact | N orphaned
-  dbt:      Passes | N failures
-  PostGIS:  Valid | N issues | Not applicable
-
-VERDICT: PASS | FAIL (N blocking issues)
-```
-
-## When to Use
-
-### Before Sprint Planning
-Audit data layer health to identify tech debt and inform sprint scope.
-```
-/data-review ./dbt/
-```
-
-### During Code Review
-Get detailed data integrity findings alongside code review comments.
-```
-/data-review ./dbt/models/staging/stg_new_source.sql
-```
-
-### After Migrations
-Verify schema changes didn't break anything downstream.
-```
-/data-review ./migrations/
-```
-
-### Periodic Health Checks
-Regular data infrastructure audits for proactive maintenance.
-```
-/data-review ./data_pipeline/
-```
-
-### New Project Onboarding
-Understand the current state of data architecture.
-```
-/data-review .
-```
-
-## Severity Levels
-
-| Level | Meaning | Gate Impact |
-|-------|---------|-------------|
-| **FAIL** | Blocking issues that will cause runtime errors | Would block `/data-gate` |
-| **WARN** | Quality issues that should be addressed | Does not block gate |
-| **INFO** | Suggestions for improvement | Does not block gate |
-
-## Differences from /data-gate
-
-`/data-review` gives you the full picture. `/data-gate` gives the orchestrator a yes/no.
-
-| Aspect | /data-gate | /data-review |
-|--------|------------|--------------|
-| Output | Binary PASS/FAIL | Detailed report |
-| Severity | FAIL only | FAIL + WARN + INFO |
-| Purpose | Automation | Human review |
-| Verbosity | Minimal | Comprehensive |
-| Speed | Fast (skips INFO) | Thorough |
-
-Use `/data-review` when you want to understand.
-Use `/data-gate` when you want to automate.
-
-## Requirements
-
-- data-platform MCP server must be running
-- For dbt checks: dbt project must be configured (auto-detected via `dbt_project.yml`)
-- For PostgreSQL checks: connection configured in `~/.config/claude/postgres.env`
-
-**Graceful degradation:** If database or dbt unavailable, applicable checks are skipped with a note in the report rather than failing entirely.
-
-## Skills Used
-
-- `skills/data-integrity-audit.md` - Audit rules and patterns
-- `skills/mcp-tools-reference.md` - MCP tool reference
-
-## Related Commands
-
-- `/data-gate` - Binary pass/fail for automation
-- `/lineage` - Visualize dbt model dependencies
-- `/schema` - Explore database schema

plugins/data-platform/skills/data-integrity-audit.md

@@ -1,307 +0,0 @@
----
-name: data-integrity-audit
-description: Rules and patterns for auditing data integrity, schema validity, and dbt compliance
----
-
-# Data Integrity Audit
-
-## Purpose
-
-Defines what "data valid" means for the data-platform domain. This skill is loaded by the `data-advisor` agent for both review and gate modes during sprint execution and standalone audits.
-
----
-
-## What to Check
-
-| Check Category | What It Validates | MCP Tools Used |
-|----------------|-------------------|----------------|
-| **Schema Validity** | Tables exist, columns have correct types, constraints present, no orphaned columns | `pg_tables`, `pg_columns`, `pg_schemas` |
-| **dbt Project Health** | Project parses without errors, models compile, tests defined for critical models | `dbt_parse`, `dbt_compile`, `dbt_test`, `dbt_ls` |
-| **Lineage Integrity** | No orphaned models (referenced but missing), no circular dependencies, upstream sources exist | `dbt_lineage`, `dbt_ls` |
-| **Data Type Consistency** | DataFrame dtypes match expected schema, no silent type coercion, date formats consistent | `describe`, `head`, `pg_columns` |
-| **PostGIS Compliance** | Spatial tables have correct SRID, geometry types match expectations, extent is reasonable | `st_tables`, `st_geometry_type`, `st_srid`, `st_extent` |
-| **Query Safety** | SELECT queries used for reads (not raw SQL for mutations), parameterized patterns | Code review - manual pattern check |
-
----
-
-## Common Violations
-
-### FAIL-Level Violations (Block Gate)
-
-| Violation | Detection Method | Example |
-|-----------|-----------------|---------|
-| dbt parse failure | `dbt_parse` returns error | Project YAML invalid, missing ref targets |
-| dbt compilation error | `dbt_compile` fails | SQL syntax error, undefined column reference |
-| Missing table/column | `pg_tables`, `pg_columns` lookup | Code references `census_raw` but table doesn't exist |
-| Type mismatch | Compare `pg_columns` vs dbt schema | Column is `varchar` in DB but model expects `integer` |
-| Broken lineage | `dbt_lineage` shows orphaned refs | Model references `stg_old_format` which doesn't exist |
-| PostGIS SRID mismatch | `st_srid` returns unexpected value | Geometry column has SRID 0 instead of 4326 |
-| Unreasonable spatial extent | `st_extent` returns global bbox | Toronto data shows coordinates in China |
-
-### WARN-Level Violations (Report, Don't Block)
-
-| Violation | Detection Method | Example |
-|-----------|-----------------|---------|
-| Missing dbt tests | `dbt_ls` shows model without test | `dim_customers` has no `unique` test on `customer_id` |
-| Undocumented columns | dbt schema.yml missing descriptions | Model columns have no documentation |
-| Schema drift | `pg_columns` vs dbt schema.yml | Column exists in DB but not in dbt YAML |
-| Hardcoded SQL | Scan Python for string concatenation | `f"SELECT * FROM {table}"` without parameterization |
-| Orphaned model | `dbt_lineage` shows no downstream | `stg_legacy` has no consumers and no exposure |
-
-### INFO-Level Violations (Suggestions Only)
-
-| Violation | Detection Method | Example |
-|-----------|-----------------|---------|
-| Missing indexes | Query pattern suggests need | Frequent filter on non-indexed column |
-| Documentation gaps | dbt docs incomplete | Missing model description |
-| Unused models | `dbt_ls` vs actual queries | Model exists but never selected |
-| Optimization opportunity | `describe` shows data patterns | Column has low cardinality, could be enum |
-
----
-
-## Severity Classification
-
-| Severity | When to Apply | Gate Behavior |
-|----------|--------------|---------------|
-| **FAIL** | Broken lineage, models that won't compile, missing tables/columns, data type mismatches that cause runtime errors, invalid SRID | Blocks issue completion |
-| **WARN** | Missing dbt tests, undocumented columns, schema drift, hardcoded SQL, orphaned models | Does NOT block gate, included in review report |
-| **INFO** | Optimization opportunities, documentation gaps, unused models | Review report only |
-
-### Severity Decision Tree
-
-```
-Is the dbt project broken (parse/compile fails)?
-  YES -> FAIL
-  NO -> Does code reference non-existent tables/columns?
-    YES -> FAIL
-    NO -> Would this cause a runtime error?
-      YES -> FAIL
-      NO -> Does it violate data quality standards?
-        YES -> WARN
-        NO -> Is it an optimization/documentation suggestion?
-          YES -> INFO
-          NO -> Not a violation
-```
-
----
-
-## Scanning Strategy
-
-### For dbt Projects
-
-1. **Parse validation** (ALWAYS FIRST)
-   ```
-   dbt_parse → if fails, immediate FAIL (project is broken)
-   ```
-
-2. **Catalog resources**
-   ```
-   dbt_ls → list all models, tests, sources, exposures
-   ```
-
-3. **Lineage check**
-   ```
-   dbt_lineage on changed models → check upstream/downstream integrity
-   ```
-
-4. **Compilation check**
-   ```
-   dbt_compile on changed models → verify SQL renders correctly
-   ```
-
-5. **Test execution**
-   ```
-   dbt_test --select <changed_models> → verify tests pass
-   ```
-
-6. **Test coverage audit**
-   ```
-   Cross-reference dbt_ls tests against model list → flag models without tests (WARN)
-   ```
-
-### For PostgreSQL Schema Changes
-
-1. **Table verification**
-   ```
-   pg_tables → verify expected tables exist
-   ```
-
-2. **Column validation**
-   ```
-   pg_columns on affected tables → verify types match expectations
-   ```
-
-3. **Schema comparison**
-   ```
-   Compare pg_columns output against dbt schema.yml → flag drift
-   ```
-
-### For PostGIS/Spatial Data
-
-1. **Spatial table scan**
-   ```
-   st_tables → list tables with geometry columns
-   ```
-
-2. **SRID validation**
-   ```
-   st_srid → verify SRID is correct for expected region
-   Expected: 4326 (WGS84) for GPS data, local projections for regional data
-   ```
-
-3. **Geometry type check**
-   ```
-   st_geometry_type → verify expected types (Point, Polygon, etc.)
-   ```
-
-4. **Extent sanity check**
-   ```
-   st_extent → verify bounding box is reasonable for expected region
-   Toronto data should be ~(-79.6 to -79.1, 43.6 to 43.9)
-   ```
-
-### For DataFrame/pandas Operations
-
-1. **Data quality check**
-   ```
-   describe → check for unexpected nulls, type issues, outliers
-   ```
-
-2. **Structure verification**
-   ```
-   head → verify data structure matches expectations
-   ```
-
-3. **Memory management**
-   ```
-   list_data → verify no stale DataFrames from previous failed runs
-   ```
-
-### For Python Code (Manual Scan)
-
-1. **SQL injection patterns**
-   - Scan for f-strings with table/column names
-   - Check for string concatenation in queries
-   - Look for `.format()` calls with SQL
-
-2. **Mutation safety**
-   - `pg_execute` usage should be intentional, not accidental
-   - Verify DELETE/UPDATE have WHERE clauses
-
-3. **Credential exposure**
-   - No hardcoded connection strings
-   - No credentials in code (check for `.env` usage)
-
----
-
-## Report Templates
-
-### Gate Mode (Compact)
-
-```
-DATA GATE: PASS
-No blocking data integrity violations found.
-```
-
-or
-
-```
-DATA GATE: FAIL
-
-Blocking Issues (N):
-1. <location> - <violation description>
-   Fix: <actionable fix>
-
-2. <location> - <violation description>
-   Fix: <actionable fix>
-
-Run /data-review for full audit report.
-```
-
-### Review Mode (Detailed)
-
-```
-+----------------------------------------------------------------------+
-|  DATA-PLATFORM - Data Integrity Audit                                 |
-|  [Target Path]                                                        |
-+----------------------------------------------------------------------+
-
-Target: <scanned path or project>
-Scope: N files scanned, N models checked, N tables verified
-
-FINDINGS
-
-FAIL (N)
-  1. [location] violation description
-     Fix: actionable fix
-
-  2. [location] violation description
-     Fix: actionable fix
-
-WARN (N)
-  1. [location] warning description
-     Suggestion: improvement suggestion
-
-  2. [location] warning description
-     Suggestion: improvement suggestion
-
-INFO (N)
-  1. [location] info description
-     Note: context
-
-SUMMARY
-  Schema:   Valid | N issues
-  Lineage:  Intact | N orphaned
-  dbt:      Passes | N failures
-  PostGIS:  Valid | N issues | Not applicable
-
-VERDICT: PASS | FAIL (N blocking issues)
-```
-
----
-
-## Skip Patterns
-
-Do not flag violations in:
-
-- `**/tests/**` - Test files may have intentional violations
-- `**/__pycache__/**` - Compiled files
-- `**/fixtures/**` - Test fixtures
-- `**/.scratch/**` - Temporary working files
-- Files with `# noqa: data-audit` comment
-- Migration files marked as historical
-
----
-
-## Error Handling
-
-| Scenario | Behavior |
-|----------|----------|
-| Database not reachable (`pg_connect` fails) | WARN, skip PostgreSQL checks, continue with file-based |
-| dbt not configured (no `dbt_project.yml`) | Skip dbt checks entirely, not an error |
-| No PostGIS tables found | Skip PostGIS checks, not an error |
-| MCP tool call fails | Report as WARN with tool name, continue with remaining checks |
-| No data files in scanned path | Report "No data artifacts found" - PASS (nothing to fail) |
-| Empty directory | Report "No files found in path" - PASS |
-
----
-
-## Integration Notes
-
-### projman Orchestrator
-
-When called as a domain gate:
-1. Orchestrator detects `Domain/Data` label on issue
-2. Orchestrator identifies changed files
-3. Orchestrator invokes `/data-gate <path>`
-4. Agent runs gate mode scan
-5. Returns PASS/FAIL to orchestrator
-6. Orchestrator decides whether to complete issue
-
-### Standalone Usage
-
-For manual audits:
-1. User runs `/data-review <path>`
-2. Agent runs full review mode scan
-3. Returns detailed report with all severity levels
-4. User decides on actions

scripts/setup.sh

@@ -278,7 +278,7 @@ print_report() {
 # --- Main ---
 main() {
     echo "=============================================="
-    echo "  Leo Claude Marketplace Setup (v5.7.1)"
+    echo "  Leo Claude Marketplace Setup (v5.1.0)"
     echo "=============================================="
     echo ""