[Smartdevs17]

Closes #852
Closes #853
Closes #854
Closes #856

Summary

• feat(testing): Add fault injection E2E test suite covering agent crashes, payment failures, and network partitions #852: Fault injection e2e suite (tests/e2e/fault-injection.test.ts): agent crash/retry, capability-unavailable terminal failure, malformed output recovery, Horizon outage recovery, escrow release failure → distinct payment_failed status, orphaned-escrow reconciliation remediation, SSE reconnect with Last-Event-ID (no duplicates), idempotent task creation. Run via npm run test:fault (excluded from standard e2e run).
• feat(observability): Extend Grafana dashboard to cover full stack — payments, agent health, DAG timings, and gas usage #853: Grafana dashboards — 39 panels in 6 rows (Task Execution, Payments, Agents, Workflows, System Health, Cost & Gas), provisioned Prometheus datasource + dashboard auto-load, prometheus.yml scrape config, wasm-sizes cost table panel.
• feat(security): Add automated SAST, dependency audit, secret scanning, and container security scanning to CI #854: Security CI — security-audit (npm audit high), secret-scan (trufflehog), container-scan (trivy) jobs in ci.yml; new codeql.yml (JS/TS + Rust); docs/SECURITY_CHECKLIST.md; docs/THREAT_MODEL.md §7 release gating.
• feat(observability): Implement end-to-end OpenTelemetry distributed tracing from browser to Stellar transaction #856: Distributed tracing — W3C traceparent propagated in Venice HTTP calls and Stellar escrow memo (28-byte truncation), env-driven sampling rate + OTLP endpoint (OTEL_SAMPLING_RATE, OTEL_EXPORTER_ENDPOINT), frontend trace context, OTel Collector in compose (monitoring profile), operator guide §13.

[vercel]

@Smartdevs17 is attempting to deploy a commit to the Jaja's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.