docs(backlog): record United Way BC as not crawlable, with the evidence - #95
Conversation
Third of the orgs deferred in the 2026-07-29 round, and the only one that turned out worse than the deferral assumed rather than better. The belief was that its listing lacked dates and would need a fetch per event; in fact there is no event date anywhere server-side, so the second fetch would not help either. Filed as a documented dead end rather than an open task, same disposition as Burnaby Public Library in #84 — with the evidence attached so the next scoping round can see why instead of re-deriving it: no date field on the WP REST event type (acf empty, only post timestamps), no date on the detail page, JSON-LD that is Yoast WebPage rather than Event, and a browser User-Agent returning byte-identical HTML — so it is genuinely client-rendered, not UA-gated. Only a headless browser would recover the dates, which this crawler deliberately avoids. Also notes the robots.txt AI-crawler opt-out as an independent reason, and the two-command re-test for whoever wants to check whether it has changed. Adds Capilano's borderline case to the relevance-filter entry alongside NVCL's, explicitly labelled a weak case rather than a second data point — the filter correctly catches Capilano's one on-mission event, so the only near-miss there is a generic "New Student Orientation" that relevance.ts avoids on purpose. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 22 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Docs-only. Closes out the third deferred org from the 2026-07-29 round.
United Way BC — dead end, not a backlog item
It was deferred on the belief its listing lacked dates and would need a fetch per event. Re-checked 2026-08-02, and the reality is worse than that: there is no event date anywhere server-side, so a second fetch wouldn't help. Same disposition as Burnaby PL in #84 — documented dead end, no adapter.
Evidence recorded so nobody re-scopes it:
/wp-json/wp/v2/eventacfis[], onlydate/date_gmt/modified(WordPress post timestamps)Date/WhenlabelWebPage(datePublished/dateModified) — notEventrobots.txt*, but disallowsClaudeBot,GPTBot,anthropic-ai,Google-Extended,CCBotOnly a headless browser would recover the dates, which this crawler deliberately avoids. The robots opt-out doesn't bind
UnifyEventsBot/1.0, but it signals intent — an independent reason not to pursue it.The entry includes the two-command re-test (
curl .../wp-json/wp/v2/event, check for a date field) for whoever wants to see whether it's changed.Also: Capilano's borderline case, labelled honestly
Added to the existing relevance-filter entry — but explicitly as a weak case, not a second data point. Capilano's genuinely on-mission item (
Fall 2026 New International Student Orientation) is caught, viainternational student. The only near-miss is a genericFall 2026 Term Commences / New Student Orientation, whichrelevance.tsavoids on purpose (its header notes a bareorientationterm would catch West Van's "Recording Studio Orientation").So the filter is working correctly there. It's recorded so the eventual pass sees the borderline shape — NVCL's MS Office sessions remain the strong evidence.
No code paths touched.
🤖 Generated with Claude Code