v0.4.3

Added

• config/source-registry.md — source values, host patterns, ATS probe providers, browser-required sources such as Djinni/LinkedIn, and URL-to-Source derivation rules.
• migrations/0.4.3.md — seeds config/source-registry.md for existing workspaces that already completed 0.4.2, and adds source-registry references to protected strategy/sources.md and config/tracker-schema.md.
• Health checks for source-registry drift: scripts/check-workspace.js now verifies that configured ATS providers match scripts/ats-probe.js and that Djinni has both browser-required and source-derivation policy.

Changed

• job-tracker:find, job-tracker:import, and job-tracker:verify read config/source-registry.md instead of hardcoding provider/source policy in skill files.
• scripts/ats-probe.js now reads provider IDs, discovery feed templates, default keywords, and default locations from config/source-registry.md; JavaScript keeps only provider-specific payload normalization.
• strategy/sources.md, config/tracker-schema.md, config/browser-patterns.md, and config/agent-instructions.md now delegate source values and browser-required source policy to config/source-registry.md.
• job-tracker:verify liveness strategy clarified: Browser MCP on the direct job URL is the primary liveness check for tracked roles; scripts/ats-probe.js and ATS board APIs are discovery surfaces only and must not be used as the closing signal for a specific tracked job ID.