Conversation
…ovels markazriwayat.com serves no novel content on any route: direct requests get a Cloudflare challenge and the origin behind it only returns a "Coming Soon" placeholder with a theme 404 on every deeper path. There is nothing left to parse, so no code change can repair this source. Rename the plugin to the repository's `*.broken.ts` convention, which excludes it from production compilation and reports it as broken in the manifest build, while retaining the source. No BLACKLIST.json entry: that file holds owner takedowns, not downtime. The plugin's header now points readers at Galaxy Novels (galaxynovels.com), which the same operators announce on their Coming Soon page as their affiliated successor site and which already ships as the `galaxynovels` plugin. AI-authored change (pi coding agent). Not human-reviewed.
A '*.broken.ts' rename deliberately parks an unrecoverable source outside production compilation, but the live-check workflow still targeted 'plugins/**/*.ts' including the parked file, so the parked source failed the PR by design (ref lnreader#2522). Exclude 'plugins/**/*.broken.ts' from the workflow's changed-files trigger (same as the existing multisrc-generated exclusion) and short-circuit scripts/live-check-plugin.js to INCONCLUSIVE for '*.broken.ts' paths so manual and workflow_dispatch runs skip them too. Healthy plugins are unaffected and still run the full check. AI-authored change (pi coding agent). Not human-reviewed.
Contributor
Author
|
Pushed d35f06a for this head: the live check now skips a parked |
This was referenced Sep 24, 2026
Open
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Disposition of the fifth source left unverified by #2529. Related to #2522 — deliberately no closing keyword, since this removes rather than repairs:
markazriwayat.comserves no novel content on any route. Direct requests hit a Cloudflare challenge, behind which sits only a Hostinger "Coming Soon" placeholder and a theme 404 page. There is nothing left to parse.plugins/arabic/Markazriwayat.ts→plugins/arabic/Markazriwayat.broken.ts, the repo's documented convention for an unavailable source (excluded from production compilation, source retained). The header comment names the successor: the operators' own Coming Soon page announces Galaxy Novels (galaxynovels.com) as their affiliated site, already shipped here as thegalaxynovelsplugin.*.broken.tssources (workflow target exclusion plus an INCONCLUSIVE short-circuit inscripts/live-check-plugin.js, documented indocs/testing.md), since checking them can only fail by design.BLACKLIST.json(owner-takedown entries, not downtime). No version bump, per the chore: Source Cleanup #1977 retirement precedent.Verification
build:compileexits 0 with no*markaz*in output; the manifest reports the source broken and carries zeromarkazriwayatids. Lint (2 errors / 10 warnings) and format findings are identical before and after — all pre-existing in untouched files. No live check is possible: the site serves no content, which is the reason for the PR.Left untouched deliberately: generated
keys.json/ issue-template keys (rewritten by workflow after release) and the icon asset, matching other parked plugins. AI-authored change, no human review; the successor detail was confirmed via a second egress route.