Expose public test and benchmark results to polling clients

[msaroufim]

Summary

• include persisted per-row result data in owner-only submission details for public test and benchmark runs
• keep secret, leaderboard, and profile result payloads omitted
• verify accepted background jobs continue after their request task is cancelled

Root cause

Background submissions persist detailed run results, but GET /user/submissions/{id} filtered those fields out. Polling clients therefore received only pass/score summaries and could not render individual test or benchmark rows.

Impact

This is an additive API response change with no database migration. Existing consumers can ignore the optional field. Secret validation details and potentially large profile payloads remain protected.

Validation

• uv run --extra dev ruff check . --exclude examples/ --line-length 120
• uv run --extra dev pytest tests/test_admin_api.py tests/test_background_submission_manager.py -q (67 passed)
• broader non-Docker suite (164 passed, 14 deselected)

Companion CLI: gpu-mode/popcorn-cli#74.

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
src/libkernelbot
utils.py
Project Total

This report was generated by python-coverage-comment-action