Add CI: shellcheck, Python syntax, manifest and compose validation

[divyanshus2404]

What this does

The repository has no continuous integration. Every PR (including the agent integrations already open) is checked only by manual review, if at all. This adds a lightweight GitHub Actions workflow that runs on each pull request and on pushes to main.

Four jobs, each verified green against the current tree:

Job	Checks	Guards against
shell	shellcheck -S error over every tracked *.sh / *.command	broken installer / entrypoint scripts
python	py_compile over all tracked *.py (blocking) + ruff (informational)	an agent or node that will not import
manifests	every ai-agents/*/plugin.json and service-providers/*/provider.json parses and has its required fields	malformed plugins landing unnoticed
compose	docker-compose*.yml is well-formed YAML, tolerating Compose's !override / !reset tags	a broken compose file

Verified locally against the current tree

• shellcheck -S error: 6 scripts, 0 errors
• py_compile: 137 Python files, 0 syntax errors
• manifest validator: 47 manifests, 0 errors, 2 warnings (below)
• compose validator: 3 files, 0 errors

So the workflow is green on merge, not red-on-arrival.

Two existing issues surfaced (as warnings, non-blocking)

The manifest validator flags these without failing CI, so they are visible but do not block:

• ai-agents/upwork/plugin.json declares no entrypoint
• ai-agents/apollo.io/plugin.json has plugin_id: "apollo" — directory/id mismatch

Notes

• shellcheck runs at -S error because the existing scripts are clean at that severity but carry style-level warnings (49 at default). The threshold can be tightened to warning once those are cleaned up.
• ruff is informational (continue-on-error) so existing style does not block, while still surfacing suggestions.
• The validators live in .github/scripts/ and can be run locally: python3 .github/scripts/validate_plugins.py.

This is intentionally a fast, dependency-light first layer. A natural next step is a stack smoke-test (docker compose up, assert the app answers) — that would catch runtime regressions the static checks cannot.

🤖 Generated with Claude Code