fix(pipeline): reject undated FCC rows and track record freshness

The old liveness tests assumed a successful fetch meant current complaint data; that assertion was wrong for a stalled cursor. The release-drift fixture also never exercised the importer's actual ok/error statuses. Updated both contracts and regenerated the signed feed after the FCC catch-up import.

Author: SysAdminDoc

.gitignore

@@ -14,6 +14,8 @@ local.properties
 *.apk.sha256
 *.aab
 *.aab.sha256
+*.md
+!README.md
 *.jks
 *.keystore
 *.pem

CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to CallShield will be documented in this file.
 
 ## Unreleased
 
+- The FCC import now ignores complaints with no issue date or a future date.
+  Its saved cursor advances to a valid complaint, and the weekly source check
+  uses the newest complaint date so an empty fetch can't hide a stalled feed.
+  Release checks now recognise the importer's success and failure statuses.
+- A catch-up import processed 500,000 FCC complaints and refreshed evidence on
+  7,638 existing numbers. The database still holds 51,806 numbers (feed v46).
+
 ## v1.8.1 (2026-09-25)
 
 ### Protection

README.md

@@ -30,7 +30,7 @@
 
 ---
 
-CallShield blocks spam calls and texts using a **15+ layer on-device detection engine** with a gradient-boosted tree ML scorer, bounded campaign and churn evidence, conservative carrier identity metadata signals, an RCS notification filter, and real-time caller ID. Its 51,755-number database sits alongside a trending-numbers feed the app checks every 30 minutes. There are no accounts or tracking.
+CallShield blocks spam calls and texts using a **15+ layer on-device detection engine** with a gradient-boosted tree ML scorer, bounded campaign and churn evidence, conservative carrier identity metadata signals, an RCS notification filter, and real-time caller ID. Its 51,806-number database sits alongside a trending-numbers feed the app checks every 30 minutes. There are no accounts or tracking.
 
 The database keeps `data/spam_numbers.json` as a stable legacy GitHub-raw
 endpoint for older clients, while current builds bundle a hash manifest and
@@ -315,7 +315,10 @@ can decay or remove only that community-only contribution. FTC and FCC runs
 persist bounded high-water cursors in `data/source-cursors.json`, which the
 importer creates on its first run. They keep caller-ID and callback-business
 evidence as separate roles, and don't promote unverified complaint-only rows
-without independent caller corroboration.
+without independent caller corroboration. The importer leaves out complaints
+with missing or future dates. `data/source-freshness.json` records the newest
+complaint date, and the weekly check flags an FTC or FCC feed when that date
+falls outside its freshness window.
 
 The importer also accepts a carrier-authorized Nomorobo IRS callback-scam CSV
 feed without embedding credentials in the app. Pass the HTTPS URL with

data/README.md

@@ -11,7 +11,7 @@ This directory contains the spam number database that the CallShield app pulls f
 - `spam_model_weights.json`: Versioned on-device GBT and logistic fallback weights
 - `source-manifest.json`: Feed access, license, geography, attribution, and parser contract
 - `source-snapshot.json`: Per-run source health, checksum, accepted/rejected counts, and failures
-- `source-freshness.json`: Each upstream source's last successful import, kept across runs. The weekly liveness workflow checks daily and weekly sources against `stale_after_days`. A source with an `import_flag` in the manifest only imports with that flag, so it's checked once it has been imported and the failure message names the flag
+- `source-freshness.json`: Each upstream source's last successful import and the newest complaint date for FTC and FCC. The weekly liveness check compares complaint dates, rather than fetch times, with `stale_after_days`. A source with an `import_flag` in the manifest is checked once it has been imported, and the failure message names the flag
 - `spam_domains_approved.json`: Optional maintainer approval input for domain candidates
 - `spam_domains_review.json`: Generated domain candidates awaiting approval
 - `not_spam_review.json`: Generated community false-positive review candidates

data/source-cursors.json

@@ -2,8 +2,8 @@
   "schema_version": 1,
   "sources": {
     "fcc_complaints": {
-      "timestamp": "9999-12-15T00:00:00.000",
-      "id": "46486"
+      "timestamp": "2026-09-26T00:00:00.000",
+      "id": "9140121"
     }
   }
 }

data/source-freshness.json

@@ -1,8 +1,11 @@
 {
-  "schema_version": 1,
+  "schema_version": 2,
   "last_success": {
-    "community_reports": "2026-09-25T17:33:14+00:00",
-    "fcc_complaints": "2026-09-25T17:33:14+00:00",
+    "community_reports": "2026-09-26T00:59:25+00:00",
+    "fcc_complaints": "2026-09-26T00:59:25+00:00",
     "saracroche_prefixes": "2026-09-25T17:33:14+00:00"
+  },
+  "newest_record_date": {
+    "fcc_complaints": "2026-09-26"
   }
 }