Build San José Legistar decision pipeline - #302
Draft
ThatXliner wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
13 tasks
ThatXliner
force-pushed
the
codex/issue-282-legistar-pipeline
branch
from
August 20, 2026 03:57
e361dff to
646fae6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #282
Summary
Privacy decision
Public-comment letters remain relevant as official records, but they may expose names, signatures, home/contact details, or sensitive personal circumstances. In v1 they are link-only: the scraper does not download, OCR, index, or summarize their contents, and the API strips attachment names while returning generic official links and an aggregate count.
Migration note
Migration
0012_tough_stone_men.sqlintentionally drops the five legacylegistar_*cache tables. They have no ingestion or application consumer today, and issue scope explicitly allows replacing them. The migration was generated with Drizzle, replayed from scratch against PostgreSQL 17, checked withdrizzle-kit check, and enables RLS on all nine replacement tables.Validation
pnpm typecheckpnpm lintpnpm formatpnpm db:checkpnpm --filter @acme/api test(22 passing)pnpm --filter @acme/scraper test(135 passing)pnpm --filter @acme/scraper buildDeliberately quality-gated follow-ups
The PR does not publish uncited AI summaries. Approved-minutes fallback with page citations, the OCR worker and measured validation set, agenda-specific participation extraction, official GIS address resolution, cited AI explanations, and extraction of San José policy into a jurisdiction profile before enabling a second city remain explicit follow-ups rather than silent or inferred production behavior.