The checks engine, the path and the cards: me-web? 0.1 reads the connection

MeWeb.Core runs seven checks concurrently and reports each as it settles:
online or behind a login page, this connection, the public IPv4 and IPv6
seen from v4./v6.meweb, the provider from a built-in map, the router
(UPnP IGD, NAT-PMP and PCP, read-only), address sharing (router WAN
against the echo, TTL hops only as a hint), and the history kept on the
device. The app draws the path from this device to the internet and lights
it node by node, with a card per check and a sheet listing every host it
contacts.

The provider map is iptoasn's table compressed to 2.1 MB by
tools/knowledge.cs and built before every app release; eleven Italian
provider profiles carry each fact with who said it, the source and the
month. The server gains a download page (en, it) and /download/{platform}
from the latest Gitea release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB

data/isps/it-windtre.json

@@ -0,0 +1,19 @@
+{
+  "name": "WindTre",
+  "country": "IT",
+  "asns": [
+    1267
+  ],
+  "ipv4": {
+    "value": "public-dynamic",
+    "basis": "users",
+    "source": "https://forum.fibra.click/d/45987",
+    "date": "2025-03"
+  },
+  "publicAddress": {
+    "value": "none",
+    "basis": "users",
+    "source": "https://forum.fibra.click/d/45987",
+    "date": "2023-11"
+  }
+}