feat(cli): add lightning job logs

[ethanwharris]

Problem

deployment and sandbox have a logs CLI command, but job doesn't. So to read a job's logs from the CLI you have to drop to the raw REST endpoint (lightning api /v1/projects/<id>/jobs/<job_id>/download-logs, then fetch the signed URL). The lightning-jobs skill documents exactly this workaround. Surfaced by an agentic audit of the platform's agent-facing surface.

Change

Adds lightning job logs [NAME] [--teamspace owner/teamspace], mirroring job inspect: it resolves the job via _JobAndMMTAction().job(...) and prints Job.logs.

Job.logs raises a RuntimeError while the job is pending/running, so the command guards on job.status and prints a friendly "logs are only available once it reaches a terminal state (Completed/Failed/Stopped)" message (a ClickException) instead of a raw traceback.

Verification

Live-verified against prod lightning.ai on a real CPU_SMALL job:

$ lightning job logs audit-joblogs-test --teamspace <org>/<ts>   # while Pending
Error: Job 'audit-joblogs-test' is Pending; logs are only available once it reaches a terminal state (...)

$ lightning job logs audit-joblogs-test --teamspace <org>/<ts>   # after completion
LOGZ-MARKER-12345
42

Unit tests (tests/cli/job/test_logs.py) cover the help text, the jobs alias, and both the terminal (prints logs) and non-terminal (clean error, no raw RuntimeError) branches. Full tests/cli/job/ suite passes (42).

Follow-up

Once this ships, the lightning-jobs skill's "Raw API fallback" can point job logs at this command instead of the download-logs endpoint.

🤖 Generated with Claude Code