Repair or retire the code-janitor post #102

New issue

Open

opened 2026-08-10 20:08:59 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-10 20:08:59 +00:00

Collaborator

Context

src/pages/posts/code-janitor.md is dated 2019-07-27. It was considered for promotion and syndication and explicitly excluded. It remains live and noindex at its current URL, which is fine as a resting state, but it carries defects that are worth resolving either way.

Defects

Dead link. The post says the benefits of a requirements bot are "described in another post". That URL returns HTTP 404, verified 2026-08-10. No requirements-maint file exists under src/pages/posts/. The post's central promise resolves to nothing. Note the path uses /post/ singular, while current posts live under /posts/, so this is Gatsby-era rot.
Broken sentence. "Community member's PRs should be reviewed all be reviewed at least every 7 days" appears to be a half-finished edit.
Stale front matter. The file carries path: "/posts/code-janitor", a Gatsby-era key that nothing in the Eleventy config reads. pages.11tydata.js computes permalinks from filePathStem.
Typos. "pratices", "developes", "minizes", "continously".

Decision needed

Three viable paths, Kai's call.

Repair. Fix the sentence, typos, and stale key, and either drop the dead link or replace it with a plain-text mention of the idea. Cheapest option and leaves a clean archive.
Retire. Remove the post. Cleanest, but breaks any inbound link and loses a 2019 artifact.
Leave. Accept the defects on a dark, noindex page nobody is routed to.

Repair is the recommended default. The post is not promoted, but it is publicly reachable and carries Kai's name.

Acceptance criteria

Whichever path is chosen, the dead coilysiren.me/post/requirements-maint link no longer ships.
If repaired, the post keeps its current URL and its noindex status. It is not promoted.
If retired, confirm no other page or feed links to it first.
ward exec build and ward exec pre-commit-all pass.

Non-goals

Writing the missing requirements-maint post.
Promoting code-janitor into the syndication set. That was decided against.

## Context `src/pages/posts/code-janitor.md` is dated 2019-07-27. It was considered for promotion and syndication and explicitly excluded. It remains live and `noindex` at its current URL, which is fine as a resting state, but it carries defects that are worth resolving either way. ## Defects * **Dead link.** The post says the benefits of a requirements bot are "described in [another post](https://coilysiren.me/post/requirements-maint)". That URL returns HTTP 404, verified 2026-08-10. No `requirements-maint` file exists under `src/pages/posts/`. The post's central promise resolves to nothing. Note the path uses `/post/` singular, while current posts live under `/posts/`, so this is Gatsby-era rot. * **Broken sentence.** "Community member's PRs should be reviewed all be reviewed at least every 7 days" appears to be a half-finished edit. * **Stale front matter.** The file carries `path: "/posts/code-janitor"`, a Gatsby-era key that nothing in the Eleventy config reads. `pages.11tydata.js` computes permalinks from `filePathStem`. * **Typos.** "pratices", "developes", "minizes", "continously". ## Decision needed Three viable paths, Kai's call. * **Repair.** Fix the sentence, typos, and stale key, and either drop the dead link or replace it with a plain-text mention of the idea. Cheapest option and leaves a clean archive. * **Retire.** Remove the post. Cleanest, but breaks any inbound link and loses a 2019 artifact. * **Leave.** Accept the defects on a dark, `noindex` page nobody is routed to. Repair is the recommended default. The post is not promoted, but it is publicly reachable and carries Kai's name. ## Acceptance criteria * Whichever path is chosen, the dead `coilysiren.me/post/requirements-maint` link no longer ships. * If repaired, the post keeps its current URL and its `noindex` status. It is not promoted. * If retired, confirm no other page or feed links to it first. * `ward exec build` and `ward exec pre-commit-all` pass. ## Non-goals * Writing the missing `requirements-maint` post. * Promoting `code-janitor` into the syndication set. That was decided against.

coilyco-ops added the

priority

autonomy

async-consult

labels

2026-08-10 20:09:51 +00:00

coilyco-ops added the

role/creator

label

2026-08-25 08:12:23 +00:00