dev

[Brad-Edwards]

• Fix corrupted TLS config
• Fix ReDos
• Fix environ load fail causes fallback to lost telemetry
• Fix tests fail to check collectors properly
• Fix stranded ssh sessions
• Create test coverage for ts
• Update serena config
• Generate coverage for SonarCloud
• Fix SonarCloud duplicate indexing of MCP test files
• Add mgh workflow skill
• Upgrade CI actions to Node.js 24 and migrate SonarCloud scanner
• ADR catchup
• Notebook UI for range ops
• Fix CI SonarCloud failure: install web deps for API tests
• Improve test coveragE
• Harden web UI: logging, di, sse, docker security
• Run svelte-kit sync before web frontend tests
• Add missing dependencies and update skills
• Coverage, security rating, pydantic v2.11 deprecation
• Fix security hotspots
• rewrite lcov paths and add store tests
• Remove user controlled data from log statements
• Add in browser terminal access
• Review and security review fixes
• Add interactive scenario workbench UI
• Address implementation issues
• Remediate cross-origin vulns
• Fix code issues and test failures
• Update skill based on usage
• Migrate to OTEL integration for interop
• Fix review issues for security, unused, imports, span_id, consistency
• Move Grafana creds to .env
• Fix TS telemetry tests failing because no OTel collector
• Update docs re kill switch
• Fixes from code review
• Add egress controls on Docker networks to reudce risks of range escape
• Fix potential breaking lab change and security risks
• Add deployment backend abstraction layer
• Fixes after review
• Add research/ to .gitignore
• Enable tailscale deployment
• Fix ssh commands for deploy
• Update deployment profile
• Use shallow git clone to avoid large downloads
• Update serena config
• Fix deploy breaks on target without gh cli

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[sonarqubecloud]

Quality Gate passed

Issues
38 New issues
0 Accepted issues

Measures
0 Security Hotspots
94.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud