…about themselves

The `ask-me` promise said "your lead sees what the team understands, never who
replied". Both halves were false.

X was the team's AGGREGATE, and it is not the upper bound any more: a lead sees what
each NAMED person understands, as a split. Y was "who replied", which is inferable —
credit for a demonstrated answer exists only where that person's graded row does, so a
non-zero figure beside a login says they replied.

The server statement was corrected already; the CLI's three copies of it were not. This
aligns them, quoting the server rather than paraphrasing it:

  "Your lead sees what each person understands, never how much anyone took part.
   'Did not answer' and 'was not asked' are the same thing here, because neither one
   was recorded."

That version is checkable. Participation volume genuinely is not measured anywhere, and
the collapse of "did not answer" into "was not asked" is what makes the not-an-exam
claim falsifiable rather than reassuring.

The README is the sharpest case: it says the statement "comes from the server that
enforces it, so it cannot drift from the behaviour it describes the way a README can" —
and then its own one-line outline had drifted. So the three copies are now pinned
against each other by `promiseWording.test.ts`, which asserts the claim as a SHAPE (so
punctuation may differ), bans both retired wordings by name, and carries a negative
control proving the pattern rejects the old sentence and accepts the new one. Without
that control, a regex matching nothing would pass every assertion in the file.

Mutation-tested, 5 mutants, all killed: README reverted · ask-me.md reverted · fixture
reverted · README drops the sentence entirely · the falsifiable half dropped from the
fixture.

A false privacy promise is worst exactly here — at a consent moment, in the text someone
reads while being asked to supply data about themselves — and it is the easiest kind for
a reader to discover.

Version 0.19.0 → 0.19.1 via the lockstep script; test floor raised 723 → 729.

REVIEWER [low] — the fixture comment calls the server "the only place this statement is
authoritative", and nothing in this repo checks the copy against it. The test pins the
three copies TO EACH OTHER, so all three can be consistently stale — a smaller version of
the failure this change fixes, where the README asserted the server was authoritative
while its own outline had drifted.

The alignment was verified by hand for this change (the fixture string and the server's
are byte-identical, 171 characters, same quoting), but that check lives in a terminal and
this repo cannot import from the private one.

So the limitation is now stated in the file header, along with what it would cost to
close it: fetching the live --promise output in CI means a network call and a signed-in
session on every run, which is worse than a documented manual step.