Add soft constraint analysis (unresolved/resolved SoC constraints) to scheduling job results

.claude/agents/api-backward-compatibility-specialist.md

@@ -0,0 +1,21 @@
+---
+name: api-backward-compatibility-specialist
+description: Protects users and integrators by ensuring API changes are backwards compatible, properly versioned, and well-documented
+---
+
+# Agent: API & Backward Compatibility Specialist
+
+This is a thin Claude Code pointer file. Agent logic is maintained once, for both Claude Code
+and GitHub Copilot, in the `.github` folder:
+
+- **`.github/agents/api-backward-compatibility-specialist.md`** — the full agent definition: role, scope, review checklist,
+  domain knowledge, interaction rules, and self-improvement notes. Read this file in full before
+  acting as this agent. When agent behavior needs to change, edit that file, not this one.
+- **`.github/instructions/`** — project-wide conventions shared by every agent (atomic commits,
+  changelog entries, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing,
+  timezone awareness, UI terminology).
+- **`.github/workflows/copilot-setup-steps.yml`** — the reference environment setup (system
+  packages, Python/uv setup, database, environment variables) used for GitHub Copilot's cloud
+  agents. Claude Code agents run in their own sandboxed environment, not this one, so treat this
+  file as a reference for expected dependencies and services rather than a script to execute
+  verbatim.

.claude/agents/architecture-domain-specialist.md

@@ -0,0 +1,21 @@
+---
+name: architecture-domain-specialist
+description: Guards domain model, invariants, and architecture to maintain model clarity and prevent erosion of core principles
+---
+
+# Agent: Architecture & Domain Specialist
+
+This is a thin Claude Code pointer file. Agent logic is maintained once, for both Claude Code
+and GitHub Copilot, in the `.github` folder:
+
+- **`.github/agents/architecture-domain-specialist.md`** — the full agent definition: role, scope, review checklist,
+  domain knowledge, interaction rules, and self-improvement notes. Read this file in full before
+  acting as this agent. When agent behavior needs to change, edit that file, not this one.
+- **`.github/instructions/`** — project-wide conventions shared by every agent (atomic commits,
+  changelog entries, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing,
+  timezone awareness, UI terminology).
+- **`.github/workflows/copilot-setup-steps.yml`** — the reference environment setup (system
+  packages, Python/uv setup, database, environment variables) used for GitHub Copilot's cloud
+  agents. Claude Code agents run in their own sandboxed environment, not this one, so treat this
+  file as a reference for expected dependencies and services rather than a script to execute
+  verbatim.

.claude/agents/coordinator.md

@@ -0,0 +1,21 @@
+---
+name: coordinator
+description: Meta-agent that manages agent lifecycle, enforces structural standards, and maintains coherence across the agent system
+---
+
+# Agent: Coordinator
+
+This is a thin Claude Code pointer file. Agent logic is maintained once, for both Claude Code
+and GitHub Copilot, in the `.github` folder:
+
+- **`.github/agents/coordinator.md`** — the full agent definition: role, scope, review checklist,
+  domain knowledge, interaction rules, and self-improvement notes. Read this file in full before
+  acting as this agent. When agent behavior needs to change, edit that file, not this one.
+- **`.github/instructions/`** — project-wide conventions shared by every agent (atomic commits,
+  changelog entries, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing,
+  timezone awareness, UI terminology).
+- **`.github/workflows/copilot-setup-steps.yml`** — the reference environment setup (system
+  packages, Python/uv setup, database, environment variables) used for GitHub Copilot's cloud
+  agents. Claude Code agents run in their own sandboxed environment, not this one, so treat this
+  file as a reference for expected dependencies and services rather than a script to execute
+  verbatim.

.claude/agents/data-time-semantics-specialist.md

@@ -0,0 +1,21 @@
+---
+name: data-time-semantics-specialist
+description: Prevents subtle bugs in time handling, units, and data semantics with focus on timezone-aware operations and unit conversions
+---
+
+# Agent: Data & Time Semantics Specialist
+
+This is a thin Claude Code pointer file. Agent logic is maintained once, for both Claude Code
+and GitHub Copilot, in the `.github` folder:
+
+- **`.github/agents/data-time-semantics-specialist.md`** — the full agent definition: role, scope, review checklist,
+  domain knowledge, interaction rules, and self-improvement notes. Read this file in full before
+  acting as this agent. When agent behavior needs to change, edit that file, not this one.
+- **`.github/instructions/`** — project-wide conventions shared by every agent (atomic commits,
+  changelog entries, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing,
+  timezone awareness, UI terminology).
+- **`.github/workflows/copilot-setup-steps.yml`** — the reference environment setup (system
+  packages, Python/uv setup, database, environment variables) used for GitHub Copilot's cloud
+  agents. Claude Code agents run in their own sandboxed environment, not this one, so treat this
+  file as a reference for expected dependencies and services rather than a script to execute
+  verbatim.

.claude/agents/documentation-developer-experience-specialist.md

@@ -0,0 +1,21 @@
+---
+name: documentation-developer-experience-specialist
+description: Ensures excellent documentation, clear error messages, and smooth developer workflows to keep FlexMeasures accessible
+---
+
+# Agent: Documentation & Developer Experience Specialist
+
+This is a thin Claude Code pointer file. Agent logic is maintained once, for both Claude Code
+and GitHub Copilot, in the `.github` folder:
+
+- **`.github/agents/documentation-developer-experience-specialist.md`** — the full agent definition: role, scope, review checklist,
+  domain knowledge, interaction rules, and self-improvement notes. Read this file in full before
+  acting as this agent. When agent behavior needs to change, edit that file, not this one.
+- **`.github/instructions/`** — project-wide conventions shared by every agent (atomic commits,
+  changelog entries, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing,
+  timezone awareness, UI terminology).
+- **`.github/workflows/copilot-setup-steps.yml`** — the reference environment setup (system
+  packages, Python/uv setup, database, environment variables) used for GitHub Copilot's cloud
+  agents. Claude Code agents run in their own sandboxed environment, not this one, so treat this
+  file as a reference for expected dependencies and services rather than a script to execute
+  verbatim.

.claude/agents/performance-scalability-specialist.md

@@ -0,0 +1,21 @@
+---
+name: performance-scalability-specialist
+description: Identifies performance bottlenecks, inefficient algorithms, and scalability issues to keep FlexMeasures fast under load
+---
+
+# Agent: Performance & Scalability Specialist
+
+This is a thin Claude Code pointer file. Agent logic is maintained once, for both Claude Code
+and GitHub Copilot, in the `.github` folder:
+
+- **`.github/agents/performance-scalability-specialist.md`** — the full agent definition: role, scope, review checklist,
+  domain knowledge, interaction rules, and self-improvement notes. Read this file in full before
+  acting as this agent. When agent behavior needs to change, edit that file, not this one.
+- **`.github/instructions/`** — project-wide conventions shared by every agent (atomic commits,
+  changelog entries, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing,
+  timezone awareness, UI terminology).
+- **`.github/workflows/copilot-setup-steps.yml`** — the reference environment setup (system
+  packages, Python/uv setup, database, environment variables) used for GitHub Copilot's cloud
+  agents. Claude Code agents run in their own sandboxed environment, not this one, so treat this
+  file as a reference for expected dependencies and services rather than a script to execute
+  verbatim.

.claude/agents/test-specialist.md

@@ -0,0 +1,21 @@
+---
+name: test-specialist
+description: Focuses on test coverage, quality, and testing best practices without modifying production code
+---
+
+# Agent: Test Specialist
+
+This is a thin Claude Code pointer file. Agent logic is maintained once, for both Claude Code
+and GitHub Copilot, in the `.github` folder:
+
+- **`.github/agents/test-specialist.md`** — the full agent definition: role, scope, review checklist,
+  domain knowledge, interaction rules, and self-improvement notes. Read this file in full before
+  acting as this agent. When agent behavior needs to change, edit that file, not this one.
+- **`.github/instructions/`** — project-wide conventions shared by every agent (atomic commits,
+  changelog entries, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing,
+  timezone awareness, UI terminology).
+- **`.github/workflows/copilot-setup-steps.yml`** — the reference environment setup (system
+  packages, Python/uv setup, database, environment variables) used for GitHub Copilot's cloud
+  agents. Claude Code agents run in their own sandboxed environment, not this one, so treat this
+  file as a reference for expected dependencies and services rather than a script to execute
+  verbatim.

.claude/agents/tooling-ci-specialist.md

@@ -0,0 +1,21 @@
+---
+name: tooling-ci-specialist
+description: Reviews GitHub Actions workflows, pre-commit hooks, and CI/CD pipelines to ensure automation reliability
+---
+
+# Agent: Tooling & CI Specialist
+
+This is a thin Claude Code pointer file. Agent logic is maintained once, for both Claude Code
+and GitHub Copilot, in the `.github` folder:
+
+- **`.github/agents/tooling-ci-specialist.md`** — the full agent definition: role, scope, review checklist,
+  domain knowledge, interaction rules, and self-improvement notes. Read this file in full before
+  acting as this agent. When agent behavior needs to change, edit that file, not this one.
+- **`.github/instructions/`** — project-wide conventions shared by every agent (atomic commits,
+  changelog entries, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing,
+  timezone awareness, UI terminology).
+- **`.github/workflows/copilot-setup-steps.yml`** — the reference environment setup (system
+  packages, Python/uv setup, database, environment variables) used for GitHub Copilot's cloud
+  agents. Claude Code agents run in their own sandboxed environment, not this one, so treat this
+  file as a reference for expected dependencies and services rather than a script to execute
+  verbatim.

.claude/agents/ui-specialist.md

@@ -0,0 +1,21 @@
+---
+name: ui-specialist
+description: Guards UI consistency, permission patterns, JavaScript interaction patterns, and template quality in the FlexMeasures web interface
+---
+
+# Agent: UI Specialist
+
+This is a thin Claude Code pointer file. Agent logic is maintained once, for both Claude Code
+and GitHub Copilot, in the `.github` folder:
+
+- **`.github/agents/ui-specialist.md`** — the full agent definition: role, scope, review checklist,
+  domain knowledge, interaction rules, and self-improvement notes. Read this file in full before
+  acting as this agent. When agent behavior needs to change, edit that file, not this one.
+- **`.github/instructions/`** — project-wide conventions shared by every agent (atomic commits,
+  changelog entries, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing,
+  timezone awareness, UI terminology).
+- **`.github/workflows/copilot-setup-steps.yml`** — the reference environment setup (system
+  packages, Python/uv setup, database, environment variables) used for GitHub Copilot's cloud
+  agents. Claude Code agents run in their own sandboxed environment, not this one, so treat this
+  file as a reference for expected dependencies and services rather than a script to execute
+  verbatim.

.github/agents/api-backward-compatibility-specialist.md

@@ -219,6 +219,65 @@ value = params.get("sensor_to_save")
 - **Architecture Specialist**: Enforces "schema as source of truth" invariant
 - **API Specialist**: Verifies API documentation matches format
 
+#### Data Format Mismatch Pattern
+
+**Problem** (PR #2072 - Constraint Analysis):
+
+Data transformations between API layers can silently use incompatible key types:
+- Layer 1 produces asset-keyed results
+- Layer 2 expects sensor-keyed results
+- No schema validation catches the mismatch
+- Silent data corruption in API response
+
+**Manifestation**:
+```python
+# Layer 1: Produces asset_id keyed dict
+results = {asset_id: [values]}  # ✅ Correct
+
+# Layer 2: Function assumes sensor_id keys
+def _sensor_keyed_to_asset_keyed(sensor_keyed_results):  # ❌ Misleading name
+    # Actually receives asset-keyed data
+    # Treats asset_ids as sensor_ids
+    # Returns corrupted mapping
+```
+
+**Prevention Checklist**:
+
+1. **Function naming must indicate format**: Use clear names like `_asset_keyed_to_list()` not `_transform_results()`
+2. **Marshmallow schemas for transforms**: Add explicit response schemas, don't rely on inline OpenAPI:
+   ```python
+   class ConstraintAnalysisResponseSchema(Schema):
+       """Validates end-to-end data format"""
+       asset_id = fields.Int(required=True)
+       data = fields.Nested(ConstraintDataSchema, many=True)
+   ```
+3. **Integration tests verify data flow**: Test that end-to-end transformations preserve data semantics:
+   ```python
+   def test_constraint_analysis_returns_asset_keyed_results():
+       result = constraint_analysis_transform(asset_data)
+       assert all(isinstance(k, int) for k in result.keys()), "Keys must be asset IDs"
+       # NOT just: assert result is not None
+   ```
+4. **Document key types in docstrings**: Be explicit about what each layer expects/produces:
+   ```python
+   def analyze_constraints(data):
+       """Transform constraint results.
+
+       Args:
+           data: asset_id -> constraint_list mapping
+
+       Returns:
+           dict: asset_id -> formatted_constraints mapping (keys are asset IDs, not sensor IDs)
+       """
+   ```
+
+**Why This Matters for Backward Compatibility**:
+- Silent data corruption breaks client contracts subtly
+- Clients may succeed but get wrong data
+- Testing may pass with mismatched formats if tests don't validate keys
+- Makes it hard to reason about what the API actually returns
+- Requires coordination with clients to fix (breaking change)
+
 ### CLI Command Changes
 
 - [ ] **Argument changes**: Adding required args breaks scripts