Play Framework

docs: address PF-80 follow-up issues — tailwind regen + CLI test docs

Three issues surfaced while implementing PF-80; this commit closes the loop
on each.

Issue 1 (HTML test reports): already resolved by PF-80. The orphan
tests-results/html/index.html reference was in the test-in-nb target which
PF-80 deleted. No further action needed.

Issue 2 (tailwind/ directory state): not dead — it's the active build
source for play-tailwind.css that ships with `play new` apps and the
docviewer module. Many framework + module templates still consume it
(welcome_en.html, tags/{404,500}.html, all crud + console module views).
PF-77's strip of errors/{404,500}.html left a few orphan classes in the
generated CSS, but those classes are still used elsewhere so the CSS isn't
broken — just slightly stale until the next regen.

The actual gap was documentation: nothing told developers WHEN to run
build-css.sh or what regenerating produces. Fixed by:
- Expanded build-css.sh header comment to cover when to regen, what the
  outputs are, and where to download the standalone Tailwind v4 binary.
- New "Tailwind CSS pipeline" section in CLAUDE.md explaining the
  source/output structure, the manual regen step, and the no-auto-CI
  consequence.

Issue 3 (`play test` / `play auto-test` CLI): verified independent of the
deleted samples-and-tests-related ant targets. The Python CLI commands
have zero samples-and-tests references; the testrunner module rebuilds
cleanly (play-testrunner.jar regenerated); `play help` lists both
commands. End-to-end Selenium-driven verification is out of scope here.

The doc gap was that CLAUDE.md's "Testing Patterns" section conflated
framework-internal tests (ant unittest / integration-test / cli-test) with
end-user app testing (play test / play auto-test against an app the
developer wrote). Fixed by splitting the section into two subsections
making the distinction explicit, and noting that play test/auto-test are
NOT part of the ant test pipeline.

Verified
- ant test still passes end-to-end (no functional changes; only docs)
- modules/testrunner/build.xml builds play-testrunner.jar cleanly
- framework/tailwindcss confirmed in .gitignore (per the new doc claim)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>