Some checks failed
CI / Frontend Lint (pull_request) Failing after 1m13s
CI / Frontend Type Check (pull_request) Failing after 7s
CI / Frontend Build (pull_request) Failing after 7s
CI / Frontend E2E Tests (pull_request) Failing after 7s
CI / Orchestrator Build (pull_request) Failing after 7s
CI / Contracts Compile (pull_request) Failing after 6s
CI / Contracts Test (pull_request) Failing after 6s
Code Quality / SonarQube Analysis (pull_request) Failing after 7s
Code Quality / Code Quality Checks (pull_request) Failing after 10s
Security Scan / Dependency Vulnerability Scan (pull_request) Failing after 3s
Security Scan / OWASP ZAP Scan (pull_request) Failing after 6s
A prior merge landed with seven unresolved `<<<<<<< HEAD` lines (each sitting directly after a `steps:` line) and no matching `=======` / `>>>>>>>` counterparts, so GitHub Actions (and any other YAML parser) cannot load the workflow. Removing the orphan markers is a safe no-op for the intended workflow definition. Verified the file parses as valid YAML after the change and all seven jobs (frontend-lint, frontend-type-check, frontend-build, frontend-e2e, orchestrator-build, contracts-compile, contracts-test) are still defined. Co-Authored-By: Nakamoto, S <defi@defi-oracle.io>