fix(site): the footer went on promising a check that had been deleted #9

Merged

jlxq0 merged 1 commit from site-claims into main

2026-08-26 05:49:18 +00:00

jlxq0 commented

2026-08-26 05:15:39 +00:00

Owner

The claim gate went in #7. Two sentences in root.html.heex did not go with it and so kept advertising it, in the present tense, on every page of a public marketing site — the footer paragraph ("the build fails if a page claims more than they say") and the <meta name="description"> telling every crawler the site is generated from the project's own test status.

That is #8's failure mode arriving through #8's own removal, twenty-four hours later.

Also corrects the comment above @features in capabilities.ex, which still described the claim!/1 gate in the present tense while the moduledoc three screens above already said it was gone.

The test

One test, five routes, asserting no page advertises the removed check. It cannot tell whether a capability card is true — that is #8, and #8 says plainly that a replacement has to read Forgejo rather than a file. This asserts only that the site does not claim a guarantee it no longer has.

Verified by removal, both sentences, one at a time. The footer paragraph back: red, naming ~r/build fails if/i. The meta description back: red, naming ~r/generated from the project's own (test status|criteria)/i. Both gone: green. mix ci exits 0, 17 passed.

Cross-engine reviewed by Codex, three questions: whether the regex set has a false negative against phrasing still in the tree (no), whether any other file in lib/ or priv/ still asserts the gate in the present tense (no — the rest are past tense or say outright that nothing checks), and whether the shortened meta description is malformed (no, 48 characters, valid).

Refs #7, #8

The claim gate went in #7. Two sentences in `root.html.heex` did not go with it and so kept advertising it, in the present tense, on every page of a public marketing site — the footer paragraph (*"the build fails if a page claims more than they say"*) and the `<meta name="description">` telling every crawler the site is generated from the project's own test status. That is #8's failure mode arriving through #8's own removal, twenty-four hours later. Also corrects the comment above `@features` in `capabilities.ex`, which still described the `claim!/1` gate in the present tense while the moduledoc three screens above already said it was gone. ## The test One test, five routes, asserting no page advertises the removed check. It cannot tell whether a capability card is **true** — that is #8, and #8 says plainly that a replacement has to read Forgejo rather than a file. This asserts only that the site does not claim a guarantee it no longer has. **Verified by removal, both sentences, one at a time.** The footer paragraph back: red, naming `~r/build fails if/i`. The meta description back: red, naming `~r/generated from the project's own (test status|criteria)/i`. Both gone: green. `mix ci` exits 0, 17 passed. Cross-engine reviewed by Codex, three questions: whether the regex set has a false negative against phrasing still in the tree (no), whether any other file in `lib/` or `priv/` still asserts the gate in the present tense (no — the rest are past tense or say outright that nothing checks), and whether the shortened meta description is malformed (no, 48 characters, valid). Refs #7, #8

jlxq0 added this to the v1.0 milestone

2026-08-26 05:15:39 +00:00

jlxq0 added 1 commit

2026-08-26 05:15:39 +00:00

fix(site): the footer went on promising a check that had been deleted

CI / Quality gate (pull_request) Successful in 34s

Details

CI / Build and push image (pull_request) Has been skipped

Details

d2c727d5d7

The claim gate went in #7 — `EltrixSite.Status.claim!/1`, `status.json` and
the `/status` page, all removed with `GOAL.md` in eltrix_server#26. Two
sentences in `root.html.heex` were not part of that removal and so kept
asserting it, in the present tense, on every page of a public marketing site:

  "The capability statuses on this site are generated from the project's own
   criteria, and the build fails if a page claims more than they say."

and the `<meta name="description">`, which told every crawler and every link
preview that the site is generated from the project's own test status.

That is #8's failure mode arriving through #8's own removal. #8 exists because
the previous site advertised an Admin API, a Helm chart, Redis caching and
read-replica routing that did not exist — nothing malicious, somebody wrote a
roadmap in the present tense and nothing could tell. Twenty-four hours after
the mechanism that prevented it was deleted, the site was advertising the
mechanism.

Also corrects the comment above `@features` in `capabilities.ex`, which still
described the `claim!/1` gate in the present tense. The moduledoc three
screens above it already says the gate is gone, which is how a reader gets to
believe both.

The test asserts only that no page advertises the removed check, on all five
routes. It cannot tell whether a capability card is *true* — that is #8, and
#8 says plainly it needs Forgejo rather than a file. Both removed sentences
were reintroduced one at a time and the test named the right pattern each
time; it is green with them gone and red with either back.

Refs #7, #8