docs(predictor): fix stale Structure block and document production en…

[SankeerthNara]

Summary

Fixes the stale Structure block in predictor/README.md (was still showing the old pre-rename kalshi-poc/ layout) and documents the production entrypoints, distinguishing the daily cron path from ad-hoc/debug scripts.

Fixes #195

Scope

• Module: predictor/ docs only
• Files touched: predictor/README.md
• Out of scope: no runtime, config, secrets, wallet, or deployment files touched

Verification

I ran:

diff <(git show origin/main:predictor/README.md) predictor/README.md

Result:

• Confirmed the diff is scoped to two sections: the Structure block and a new "Entrypoints de production vs ad-hoc" section. Nothing else in the file changed.
• Cross-checked the new Structure block against the actual predictor/ tree on main (src/, scripts/, data/, runs/, runs_backtest/, runs_learning/, tests/, docs/ and their real subfolders).
• Cross-checked the entrypoints table against .github/workflows/daily-trading.yml: the daily cron (18:00 UTC) actually runs two scripts in sequence — scripts/daily_run.py (learning capture: fetch_markets → forward_predict → score_forward) followed by scripts/daily_auto.py (paper-trading finalize/capture + manifest rebuild + commit/push). Documented both as production entrypoints rather than just daily_auto.py, since the workflow file shows daily_run.py is also part of the production loop, not ad-hoc.
• Verified live_run.py, forward_predict.py (standalone use), finalize_run.py, and backtest.py are not referenced by the cron workflow — confirmed as ad-hoc/debug.

Safety checklist

• I did not commit real .env files, private keys, wallet seeds, webhook URLs, API tokens, or private datasets.
• I kept the change scoped to the linked issue.
• I updated docs or tests when they are relevant.
• I explained any command I could not run locally.

Valuation notes

n/a - not submitted for valuation

[vercel]

@SankeerthNara is attempting to deploy a commit to the JSL's projects Team on Vercel.

A member of the Team first needs to authorize it.