Add the call-log-classifier lambda

[huydhn]

Stack from ghstack (oldest at bottom):

• Update the architecture doc for the log upload path #8597
• Stop re-implementing the log upload in backfill_events.py #8596
• Move log backfill off the public API Gateway endpoint #8595
• Add the log uploader bot #8594
• Add the deploy workflow for the log uploader lambdas #8593
• -> Add the call-log-classifier lambda #8592
• Add the gha-log-uploader lambda #8591

Impact: none yet -- no S3 notification points at this function
Risk: low

What

A small lambda that triggers log classification when a job log lands in
s3://ossci-raw-job-status/log/. It maps the S3 key to a repo (log/<id> is
pytorch/pytorch, log/<owner>/<repo>/<id> names its own) and asynchronously
invokes log_classifier.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
torchci	Ignored		Aug 20, 2026 7:36pm

[huydhn]

Superseded: the classifier invoke is folded into gha-log-uploader (#8591). The tail this split was meant to avoid came from invoking the classifier synchronously, not from doing it in the same function -- InvocationType: "Event" fixes it without a second lambda, an S3 notification, or re-parsing the repo and job id back out of the S3 key.

[huydhn]

No need to review this change