docs(court-docket): clarify bridge route is read-back, not dead code

Separated adversarial review flagged POST /scrape/court-docket as
apparently-dead/confusing since its handler no longer triggers a live
scrape. It's intentionally kept at the same route -- the contract changed
(reads the latest pushed result instead of triggering a scrape) but the
route and response shape didn't, so existing callers don't need to change.
Clarified in the route's own comment.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016RuqeURZ1b7NB74U2nqqSS

Author: chitcommit

src/routes/bridge/scrape.ts

@@ -9,7 +9,12 @@ export const scrapeRoutes = new Hono<{ Bindings: Env; Variables: AuthVariables }
 
 // ── ChittyScrape ─────────────────────────────────────────────
 
-/** Trigger court docket scrape */
+/**
+ * Read the latest pushed court docket result for a case.
+ * Kept as POST /court-docket (not renamed/removed) for existing callers --
+ * the endpoint's contract changed (read-back, not trigger-a-scrape) but its
+ * shape and route didn't, so nothing calling this needs to change.
+ */
 scrapeRoutes.post('/court-docket', async (c) => {
   const scrape = scrapeClient(c.env);
   if (!scrape) return c.json({ error: 'ChittyScrape not configured' }, 503);