Implement automatic date tracking for job start and finish times

[Copilot]

The jobs table contains date_started and date_finished columns that were never being updated. This PR implements automatic tracking of these timestamps during job lifecycle events.

Changes Made

Enhanced Job Status Updates (api/endpoints/job_update.py):

• Added logic to set date_started when job status changes to "pulled" (first time only)
• Added logic to set date_finished when job reaches terminal states ("finished" or "error") (first time only)
• Dates are only set if currently None to prevent overwriting

Comprehensive Test Coverage:

• Added tests verifying dates are set on appropriate status transitions
• Added tests ensuring dates are not overwritten once set
• Added tests confirming both terminal states trigger date_finished
• Added tests verifying non-triggering statuses don't affect dates

Job Lifecycle Timeline

queued → pulled → preprocessing → running → postprocessing → finished
  ↑        ↑                                                      ↑
created  started                                              finished

Benefits

• Performance Tracking: Enables measurement of job execution times
• Resource Planning: Helps understand job duration patterns
• SLA Monitoring: Supports tracking against service level agreements
• Analytics: Enables historical analysis of job performance
• Backward Compatible: Existing jobs continue to work unchanged

Example Usage

# After job is pulled by worker
update_job_status(JobUpdate(job_id=42, status=JobStates.pulled))
# → job.date_started is now set

# After job completes successfully  
update_job_status(JobUpdate(job_id=42, status=JobStates.finished))
# → job.date_finished is now set

# Calculate execution time
execution_time = job.date_finished - job.date_started

The implementation uses minimal, surgical changes focused only on the job status update endpoint while maintaining full backward compatibility.

Fixes #14.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[nolan1999]

please keep the current version

[Copilot]

Reverted the date_created field to use the original datetime.utcnow as requested in commit 5a937fd.

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
api
__init__.py	0	0	100%
database.py	13	4	69%	22–26
dependencies.py	51	21	59%	32–37, 59, 69, 78–97, 103–115
exceptions.py	9	2	78%	10, 18
main.py	24	3	88%	35, 45, 50
models.py	43	0	100%
settings.py	77	23	70%	15–18, 28–29, 65–69, 74, 78, 86, 95–101, 104–109, 112, 121
tags.py	1	0	100%
api/core
__init__.py	0	0	100%
aws.py	5	1	80%	7
filesystem.py	225	33	85%	35, 48, 51, 54, 59, 66, 72, 87, 90, 93, 96, 99, 109, 114, 194, 196–205, 219, 291, 348, 356–368, 379, 410
notifications.py	27	13	52%	14, 28–29, 32–52
api/crud
__init__.py	0	0	100%
job.py	71	4	94%	30, 56, 144–145
api/endpoints
__init__.py	0	0	100%
auth.py	65	49	25%	30–69, 79–106, 118–155
auth_get.py	14	2	86%	22, 39
files.py	52	6	88%	26–27, 42–43, 112, 128
job_update.py	29	2	93%	28, 45
jobs.py	34	2	94%	24, 88
api/schemas
__init__.py	0	0	100%
file.py	24	0	100%
job.py	116	9	92%	27, 33, 36, 42, 47, 76, 85, 91, 93
job_update.py	6	0	100%
token.py	4	0	100%
user.py	14	0	100%
TOTAL	904	174	81%

Tests	Skipped	Failures	Errors	Time
128	0 💤	0 ❌	0 🔥	11m 55s ⏱️