Fix Ci Failures

Classify the failure type:

• Build failure: code does not compile or bundle
• Test failure: one or more tests fail
• Lint failure: code style or static analysis violations
• Dependency failure: packages cannot be resolved or installed
• Infrastructure failure: runner issues, timeouts, resource limits

Apply the appropriate fix by stack:

Go common fixes:

• Missing dependency: go mod tidy
• Compilation error: fix type errors, undefined references in reported file:line
• Test failure: run go test ./... locally, fix assertions
• Lint: golangci-lint run --fix ./... then fix remaining issues manually

TypeScript/Vue common fixes:

• Type error: fix type annotations at the reported file:line
• Module not found: npm install or add missing dependency
• Build failure: check tsconfig.json paths, Vue component imports
• Test failure: run npx vitest run locally, update snapshots if needed with npx vitest run -u
• Lint: npx eslint . --ext .ts,.tsx,.vue --fix

PHP common fixes:

• Class not found: composer dump-autoload or fix namespace/path
• Dependency conflict: composer update --with-all-dependencies
• Test failure: run vendor/bin/phpunit locally, fix assertions
• PHPStan errors: fix type annotations, add PHPDoc types, or adjust baseline

Verify the fix locally:

• Run the same commands that CI runs (check the workflow YAML)
• Ensure all steps pass: build, lint, test

Push the fix and monitor:

• Commit and push the fix
• Watch the CI run: gh run watch
• If it fails again, re-read logs and iterate