LFX Insights reads a BigQuery table the AWS batch plane no longer writes #143

Problem

LFX Insights gets its OpenSSF Scorecard data only from the BigQuery table openssf.scorecardcron.scorecard-v2_latest (scorecardSql.ts). Nothing has written to that table since the weekly scan moved to the AWS batch plane. That plane doesn't port the BigQuery transfer jobs (cron/k8s/README.md, provision-cron-aws task 7.3), and no AWS-era run has a .transfer_complete marker. So every score LFX shows is frozen at the last GCP-era run, and repos added to the inventory since then will never appear.

There is an older gap as well. That table only ever covered repos listed in cron/internal/data/projects.csv. Results published from scorecard-action reach api.scorecard.dev but never the table (#97). That's why LFX shows finos/git-proxy with no score, even though it publishes current results.

Because of the first problem, adding git-proxy to the inventory (#140) won't make it appear in LFX on its own.

To track down

• Confirm the date of the latest partition in scorecard-v2, to establish how stale LFX's data is.
• Decide how the public dataset is published from the AWS plane: restore a BigQuery load, or publish elsewhere and have LFX switch to that.
• Decide whether Action-published results should be merged into that dataset (Feature: Add Scorecard GitHub Action results to the BigQuery database #97), or whether LFX should fall back to api.scorecard.dev for repos the dataset doesn't cover.
• Find out who to coordinate with on the LFX Insights side, and tell them the table is stale.