2 commits

Author	SHA1	Message	Date
Light1YT	1ea8d0b721	fix(freshness): calibrate kn staleness thresholds to weekly cadence ... kn (DOM.РФ ЖК) is scheduled WEEKLY (settings.scrape_kn_cron='15 4 * * mon'), but its freshness thresholds were fresh_days=2 / stale_days=5 — so the monitor flagged kn "stale" every Wed-Sun by design, a guaranteed weekly false-positive that would desensitize the team to the GlitchTip alert. The freshness monitor (#1904) caught this on its first prod run (06-26 09:00 MSK: "kn [stale, 3.9d]"). Recalibrate to weekly cadence (mirror objective 7/14): fresh_days=8 (full week + Monday-run completion buffer), stale_days=14 (alert only after ~two missed Mondays). +regression test pinning kn stays fresh through the week. Refs #73	2026-06-26 11:20:02 +05:00
Light1YT	d38417d8af	feat(admin): freshness endpoint (#73) + README Forgejo refresh (#83) + migrations doc (#72) ... #73: GET /admin/scrape/freshness — last_success/age/freshness/status для 5 источников (kn/objective/nspd/nspd_geo/cadastre) + overall_status (worst по critical). Prod-verified имена таблиц, FILTER/COALESCE корректны, CAST(:d AS interval). +4 теста. #83: README — GitHub→Forgejo CI/CD, секция 6 subagents, ссылки перемаплены. #72: docs/Schema_Migrations_vs_Alembic.md — _schema_migrations паттерн (не Alembic), рекомендация снести пустой alembic-скелет (отдельный PR). Closes #73 Closes #83 Closes #72	2026-06-13 18:25:32 +00:00