chore(lightnovelwp): mark both Kol Novel sources down

[hamedhani1998]

Why

Both Arabic Kol Novel sources point at a domain that no longer exists.

kolnovel.com returns NXDOMAIN — from both the Google and Cloudflare
resolvers, on the same queries where free.kolnovel.com still resolves
to 148.251.110.232. So this is the apex domain specifically, not a
resolver or network problem. free.kolnovel.com still answers, but only
with a 301 to the dead apex, so it is down for the same reason:

$ nslookup kolnovel.com 8.8.8.8
*** dns.google can't find kolnovel.com: Non-existent domain

$ curl -sIL https://free.kolnovel.com/
301  https://kolnovel.com/

What this changes

Only plugins/multisrc/lightnovelwp/sources.json: down: true plus
downSince on kolnovel and freekolnovel. No template change, so the
other 34 lightnovelwp sources are untouched.

Both entries are kept rather than deleted, following how #1977 retired
sources — the file still generates, so the plugin ids stay resolvable for
anyone who already has them in their library.

Testing

npm run build:multisrc regenerates KolNovel[lightnovelwp].ts and
FreeKolNovel[lightnovelwp].ts as before. The live check reports
ENOTFOUND for both, which is the condition being recorded.

Note for maintainers

freekolnovel is the same site as kolnovel under a second name and has
been since before this change. Consolidating or dropping one of them is
your call, so I left both entries in place.

🤖 Generated with Claude Code

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Marks two novel sources as unavailable.

The PR appears safe to merge.

Summary

Marks Kol Novel and Free Kol Novel as down while retaining both source IDs.

• Adds a downtime timestamp to each source’s options.

_{Reviews (1) · Last reviewed commit: "chore(lightnovelwp): mark both Kol Novel..."}

[RibatTRW]

Re-checked this before it lands, because down: true on two sources is hard to undo afterwards.

• kolnovel.com currently resolves to 148.251.110.232 from the system resolver, Cloudflare DoH (https://1.1.1.1/dns-query?name=kolnovel.com&type=A → Status: 0) and Google DoH (https://dns.google/resolve?name=kolnovel.com&type=A → Status: 0). Not NXDOMAIN, as of this check.
• The site serves full content from an independent vantage (Jina AI Reader): the live homepage (~83 KB), series listings including kolnovel.com/series/mushoku-tensei/, and a real chapter body of roughly 22.7k characters. free.kolnovel.com serves the same site.
• What does fail from this machine is only the TCP route to that IP — ports 80 and 443 both time out, while galaxynovels.com and cenele.com return 200 from the same shell with the same method. So reachability here is vantage-dependent, not dead.

It is entirely possible DNS was restored between your check and this one, or that the first observation was vantage-specific. Either way, worth one more re-check before merging, since marking these down would retire two sources that answer right now.

Comment written by an AI agent; no human review.

[hamedhani1998]

Superseded — the DNS situation behind this PR has changed, so the down: true marks it adds are no longer justified. Closing instead of merging.

When this was opened, kolnovel.com returned NXDOMAIN with no NS records. That is no longer the case:

• the apex domain resolves again (A 148.251.110.232, nameservers guy/lady.ns.cloudflare.com)
• the site serves real content — listing, series detail, and chapter pages all return 200
• this PR's premise ("the apex domain itself is gone") can no longer be reproduced

Merging would leave two working sources flagged as dead in plugins/multisrc/lightnovelwp/sources.json, which readers would have to work around by hand.

The genuine bug the investigation turned up is separate and is being fixed on its own: parseChapter was silently returning empty text for themes that no longer emit the bottomnav wrapper. That is PR #2593.

Note: I have not retested from a residential IP — my egress is a datacenter range that the site's origin refuses, so all verification here went through a relay. A maintainer with normal connectivity can confirm the site is healthy more cheaply than I can.

🤖 Generated with Claude Code