Say what else is in the file, and offer the running example

[onatozmenn]

The site has had pin moves and no content since v0.2.3, and the language has
had four releases in that time. This is what measuring the gap turned up.

Seven commands the site never mentions

Counted across every page:

mentioned	not mentioned
deed check, deed run, deed explain	deed test, deed fmt, deed fix, deed build, deed doc, deed lsp, deed debug, deed mcp

The install page's lede says "the compiler, the formatter, the test runner and
the language server are all in it", which was the whole list when it was
written and is now four of eight things. It also shows one of the four.

• The lede says what is in the file today.
• A table under the first program lists all eleven commands with a line each,
  shortened from deed --help, so the source is the binary describing itself.
• deed mcp gets a second sentence. The argument this language rests on is
  that most code is no longer typed out by a person; a site that never mentions
  the agent surface is not making that argument.

transfer.deed was not in the picker

It is the program every design document works through, the one the README opens
with, and it carries three tests, so the Test button works for it. The picker's
rule is "programs a person would recognise, not one feature at a time" — a
ledger with an effect, a handler, a contract and a refinement in it is on the
right side of that line, and counter was already there. Oversight, not
judgement.

Thirteen becomes fourteen in the three places that count it, and
examples/index.json is regenerated rather than edited.

$ node tools/examples.mjs
29 examples at v0.2.6, 14 in the picker: 1 the page can start, 28 it can only check and test.
$ node tools/check.mjs
70 files, every link resolves, and v0.2.6 loaded and answered about all 29 examples.

Checked and found current, so untouched: the one-clause transcript still
matches cargo test -p deed-driver --test demo line for line, and play.js
renders every kind the pinned artifact emits.