feat: add trace_id filter for run events

[Gsbreddy]

• Introduced a new trace_id parameter across the API, CLI, and SDK to filter run events based on the exact match of RunEvent.request.trace_id.
• Updated relevant functions in storage.py, operations.py, and routes/read.py to handle the new filter.
• Enhanced CLI commands and documentation to include the --trace-id option for listing runs.
• Added tests to verify the functionality of the trace_id filter in both HTTP and CLI contexts.

This update improves the forensics capabilities of the FlightDeck platform by allowing users to filter events more precisely based on trace identifiers.

Summary

Why

Changes

Validation

Run the same checks as CI (see .github/workflows/ci.yml) before opening / updating the PR. Cursor loads .cursor/rules/flightdeck-ci-artifacts.mdc as a short reminder for static/ + schemas/ gates.

• uv sync --frozen --extra dev
• uv run python -m ruff check src tests
• uv run python -m pytest
• uv run python scripts/generate_schemas.py then git diff --exit-code schemas/ (if models/schemas touched)
• cd web && npm ci && npm run build && cd .. && git diff --exit-code src/flightdeck/server/static/ (if web/ sources, Vite config, or web/ deps / lockfile change the production bundle)
• cd web && npx playwright install chromium && npm run test:e2e (if web/ changed)
• uv run flightdeck-quickstart-verify
• uv run flightdeck --help

With pip / venv only, use python -m … equivalents from DEVELOPMENT.md.

Schema / Storage Impact

• None
• Schema change
• Storage change

Risk

Review

• Requested review from maintainers (CODEOWNERS → @flightdeckdev/maintainers on the org repo). On a fork, GitHub may not auto-request; use Reviewers on the PR.
• PR is small and scoped (see AGENTS.md); linked issue or release note intent noted if helpful.

Notes