You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Phase 2c dropped the `watches.fetch_config` JSONB column. The InfoSpec v1 JSON Schema doesn't yet model the knobs it replaced — `headers`, `ignore_patterns`, `viewport_width`, `viewport_height`, browser fetcher hints, etc. Watcher currently fail-fasts (or silently ignores) operator attempts to set them.
Audit the pre-Phase-2c `fetch_config` shape (see legacy migration files for the exact JSON). Inventory of fields that need to come back: at minimum `headers`, `ignore_patterns`, `viewport_width`, `viewport_height`, `render` (for the future Playwright fetcher).
Extend the InfoSpec v1 JSON Schema's `target.fetch` block to accept these. Keep field-level defaults at the consumer (per design doc decision §5: "DEFAULT_FETCH_RENDER = False" etc.).
Wire each knob through Watcher's fetcher / extractor:
Context
Phase 2c dropped the `watches.fetch_config` JSONB column. The InfoSpec v1 JSON Schema doesn't yet model the knobs it replaced — `headers`, `ignore_patterns`, `viewport_width`, `viewport_height`, browser fetcher hints, etc. Watcher currently fail-fasts (or silently ignores) operator attempts to set them.
Listed under "Open follow-ups (deferred)" in docs/plans/2026-05-04-watcher-phase2c-cutover-plan.md wrap-up.
What to do
References