Say what the clients are without implying one exists

[iderex]

Depends on the landing page issue and on #5.

The first sentence the project says about itself is about clients, not plugins.
The page served today says it:

curl -sS https://flowfin.dev/ | grep -o -i 'native Clients'
native Clients

and the organisation profile leads with one genuinely native client per platform
sharing a core. No such client exists to install. The organisation holds twelve
plugin repositories and no client repository:

gh repo list Flowfin --limit 60 --json name --jq '[.[].name|select(startswith("jellyfin-plugin-")|not)]'
["hub","lab","site","core",".github"]
gh api repos/Flowfin/core/releases --jq 'length'
0

Run 2026-08-08. The shared core has no release either, so a reader who arrives
because of that first sentence has nothing to download and no page telling them
so.

This milestone builds an honest table for the plugins. The same honesty is owed
to the larger claim on the same page, and the plan does not currently mention it
anywhere.

What this issue settles. The landing page says what the clients are meant to be
and states that none is released, in the same place it says what Flowfin is,
rather than leaving a reader to discover it by looking for a download that is not
there. No client appears in the state table, because the table is rows from the
roster and a client is not a roster row today.

The sentence is rendered from a value rather than typed into the template. A
claim about whether something is available that lives in prose is a claim
somebody has to remember to change, and the day it stops being true is the day
nobody is looking at that paragraph. Setting the value is what changes the page.

The forward case is stated rather than left open. When a client becomes something
a person can install, it stops being a sentence and becomes a row, which means a
roster entry with its kind named, and the schema in #20 is where that field
lands. Until then the site carries no state word for it, because the three state
words mean something about a plugin repository and there is nothing for them to
be computed from here.

The comparison against the organisation profile in #25 covers the table. This
sentence sits outside the table, so either the comparison is widened to cover it
or this issue records why it cannot, rather than leaving the largest claim on
both pages as the one thing nothing compares.

Done when

The landing page states what the clients are and that none is released today;
that statement renders from a value in the data rather than from words in the
template, shown by a test that flips the value and sees the page change; the
state table contains only rows the roster carries; and either #25's comparison
covers the client sentence or this issue records the reason it does not.

[iderex]

Three of the four clauses are landed on 51c1b13, and the fourth clause is
recorded here because this is where the done-when asks for it.

The page says what the clients are and that none is released, and it says it
from a value rather than from words:

go run . build | grep clients
read data/clients.json (none-released)
grep -o -E '<p>The clients[^<]*</p>' dist/index.html
<p>The clients this project means to build are one genuinely native client per platform, sharing a core between them. None of them is released, so there is nothing here to download and no page describing one as though there were.</p>

Both run 2026-08-16 against 51c1b13. The suite flips the value and asserts
that exactly that changes on the page; with the composition made to ignore the
value the case fails. Both runs of that pair are in #164 with the edit that
produced the red one.

On the clause about #25, and the answer is that its comparison does not cover
the client sentence and cannot be widened to.

What #25 compares is a table against a table: the rows the build renders from
the roster, in the Markdown the organisation profile expects, against what that
profile publishes today. A difference is a row on one side that the other does
not carry, or two rows that disagree. The client sentence is not a row and has
no counterpart on the other side, so there is nothing for that comparison to
put beside it. Widening it would mean either inventing a row for something the
roster does not carry, which is the drift this milestone exists against, or
comparing prose on one page against prose on another, which is a different
check from the one #25 builds.

There is also nothing to compare the sentence against. The claim is about
software that does not exist, and a repository that does not publish it cannot
disagree with a sentence saying so:

gh repo list Flowfin --limit 60 --json name --jq '[.[].name|select(startswith("jellyfin-plugin-")|not)]'
["site","lab","core",".github","hub"]
gh api repos/Flowfin/core/releases --jq 'length'
0

Both run 2026-08-16.

What keeps the claim honest instead is that it is a value the build refuses
rather than a sentence somebody rereads. It is refused when it says nothing
about what the clients are, when it declares an availability outside the two,
when it says nothing is released and still names somewhere to get one, and when
it says something is released and names nowhere. A tree that loses the file
altogether is refused by name by the invariant verb, because the page it would
otherwise produce leads with what this project is and says nothing about the
clients at all.

The day a client becomes something a person can install it stops being a
sentence and becomes a roster row with its kind named, which is the forward
case this issue already states. On that day #25's comparison reaches it as a
row like any other and the sentence is retired rather than widened.

What is left is the clause asking that the state table contain only rows the
roster carries. No produced page carries a state table and this tree carries no
roster to build one from:

go run . build | grep '^wrote'
wrote dist/index.html (2384 bytes)
wrote dist/privacy/index.html (4199 bytes, 2 checked, 3 promised, 2 residual)
wrote dist/legal/index.html (3489 bytes, 0 of 3 answered)
wrote dist/404.html (2051 bytes, 1 way(s) onward)
wrote dist/.well-known/security.txt (379 bytes)
wrote dist/sitemap.xml (259 bytes, 3 address(es) listed)
wrote dist/robots.txt (216 bytes, 1 sitemap(s) named)
git ls-files data/
data/clients.json
data/design-tokens.json
data/publisher.json
data/security-contact.json

Both run 2026-08-16 against 51c1b13. Reporting that clause as satisfied would
be reporting a comparison nothing made, so it stays open on that clause alone.
The table is #26 and #28, and what those wait on is entry 6 of #7.

[iderex]

Reopened. The merge of #164 closed this, against the text of that pull request, which says under its own ## Closes heading that it does not close it and gives the clause that is not met. The platform read the number and not the negation, which is the same way #12 was closed in August and had to be reopened.

The done-when still has its clause about the state table, and the comment above measures that no produced page carries one and that this tree carries no roster to build one from.