Classify runtime logs for TeamSpace migration

[robertDouglass]

Summary

• Add a deterministic runtime run.events.jsonl classifier for TeamSpace launch migration planning.
• Document that runtime logs are local side logs at launch, not TeamSpace status authority and not direct import payloads.
• Add fixtures/tests covering runtime side-log classification and status-authority boundaries.

Testing

• uv run pytest tests/test_teamspace_migration.py tests/test_events.py tests/test_contract_parity.py -q
  Result: 11 passed.
• uv run ruff check src/spec_kitty_runtime/teamspace_migration.py tests/test_teamspace_migration.py
• uv run mypy --strict --follow-imports=skip src/spec_kitty_runtime/teamspace_migration.py
• git diff --check

Follow-ups

• Full strict mypy still exposes existing unrelated runtime package baseline errors. Tracked in Clear runtime strict mypy baseline exposed by TeamSpace migration helper #18.

Refs Priivacy-ai/spec-kitty#920.

[robertDouglass]

Cross-repo TeamSpace migration PR set:

• CLI repair/dry-run: Add TeamSpace mission-state repair and dry-run spec-kitty#980
• SaaS ingress hardening: Priivacy-ai/spec-kitty-saas#150
• Runtime side-log boundary: Classify runtime logs for TeamSpace migration #19
• Tracker egress guardrails: Priivacy-ai/spec-kitty-tracker#14

Recorded follow-ups:

• Publish spec-kitty-events 5.0.0: Publish spec-kitty-events 5.0.0 for TeamSpace migration consumers spec-kitty-events#20
• Replace CLI temporary Git dependency: Tighten spec-kitty-events dependency after 5.0.0 PyPI release spec-kitty#978
• Replace SaaS temporary Git source: Priivacy-ai/spec-kitty-saas#149
• Clear runtime strict mypy baseline: Clear runtime strict mypy baseline exposed by TeamSpace migration helper #18
• Coordinate actual large mission-state repair commits: Coordinate the actual mission-state repair commit across active repositories spec-kitty#979