What the agent runs asked for: page lines, m0 new ., a board template, skills

[codetalcott]

The follow-ups the agent usability runs asked for (docs/notes/agent-usability-runs.md): the lines each page lacked, three changes to m0, and the two skills. The record is docs/notes/what-the-agent-runs-asked-for.md; SPEC N27 (amended) and N52 (new); DECISIONS D66.

Pages

• Both quickstarts serve on --host 127.0.0.1 and say the default is every interface.
• The Python quickstart says libpython comes from PATH's python3, what publish() does with a line break and what its return value means, and that a form post meets Django's CSRF check.
• The home page and the Mojo overview point an agent at llms.txt and each page's .md twin.
• The Mojo overview maps the API to its pages and drops "no form library".
• The views page gives reply and reply.problem's four arguments, and Datastar 1.0's rule that an action's answer applies only on a 200 (read off the 1.0.4 bundle).
• The host and views pages say where a send from a view reaches.
• The scaffold's AGENTS.md names the host and views pages by URL before the installed source.

m0

• m0 new . writes the empty current directory, named for it.
• The printed next step serves on 127.0.0.1.
• --template board: a list every tab shares whose sender is a view. A POST appends and publishes the whole board through the state's DatastarStream, then answers a 200 signal patch that empties the poster's input. Every stateful view is on_loop=True; the list is one process (max_workers() -> 1, D66: ViewsApp does not forward sse_peer_frame).
• Fixed: live's stream was refused 409 behind a handler pool (--blocking-threads), because its stream view was not on_loop and its handler answered only stateless loop routes.

Skills

skills/m0serve/SKILL.md and skills/m0/SKILL.md, in this public repository so they change with the product. scripts/agent_runs.py run --plugin-dir loads a plugin into each session and records its version and file hash.

Gates

• smoke-scaffold: all four templates. board and live are served behind --blocking-threads 2, and every template's new phase covers m0 new ..
• smoke-m0-wheel (45 unit tests), check-templates, smoke-quickstart-mojo and check-docs pass.
• smoke-quickstart passes all 15 blocks once the second page's process count is adjusted for a launchd m0serve on this machine; unadjusted, it fails on that count alone, as recorded before.
• sabotage-scaffold: all 14 new rules caught, each run once:
  • board: a post reaches no stream; the post, the stream and the document each off the loop; a message rendered raw; a late stream sent nothing; the poster's input not emptied; the docstring's backticks; the template's own test; smoke.sh's status.
  • live: the stream off the loop; the handler answering only stateless loop routes.
  • m0 new: the current directory refused; the next command binding every interface.

Measured: the Python track with the m0serve skill loaded met the contract five of five in 8 tool calls (median; range 7–10), against 13 (13–15) without it, at $0.27 a session against $0.37. Not measured yet: the doc lines reach an agent once the site deploys, and the m0 changes once an m0 release publishes them, so the Mojo track waits for that release.

🤖 Generated with Claude Code