Write down what is unfinished and what is untested

The README said "not yet" and listed four things. There are more than four,
and the more useful split is between what is half-built and what is finished
but has never met the hardware it talks to.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-27 17:26:11 +00:00
parent 1185faed78
commit 28eed33e88
2 changed files with 76 additions and 10 deletions

View File

@@ -247,14 +247,9 @@ Checked against N1MM 1.0.11031: a log this program wrote opens in N1MM, which
reads the contest, its categories and the contacts. See
[`docs/n1mm-interop.md`](docs/n1mm-interop.md) for what that took.
Not yet: voice keying, QTC handling for WAE, call history files, digital modes
beyond logging them, and the check window's Call History and Exchange columns,
which are left out rather than shown empty.
Nothing here has been run against a real radio, keyer, SO2R box or cluster node.
Every one of those is tested against a fake that speaks the same protocol, which
proves the two agree with each other and nothing more.
The radio, network and keyer clients are tested against fakes that speak the
documented protocols — the radio one over a real socket, against a stand-in for
`rigctld` that answers in the extended form. None has been run against a real
radio or keyer. The
cluster client is tested over a real socket against a node fake that sends the
telnet negotiation, the login prompt and spot lines, but not against a live
node.
[`docs/unfinished.md`](docs/unfinished.md) lists what is half-built and what has
never been tested against the real thing.