A credibility pass over ee5690e..HEAD: traffic.py parses each request once and counts visits one way, the deploy notes and skills agree with the scripts, and a few edit leftovers in the hall are tidied

traffic.py gives identical counts before and after over 41 days of the
host's access logs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GwFKMuQnPAEHJ5yA1q4orh

.claude/skills/hnefatafl-visitors/SKILL.md

@@ -17,9 +17,12 @@ spills into the next UTC day. Run yesterday too when the hour is early.
 
 - **as of / live sockets / rooms touched in the last hour**: the "right
   now" line. One socket at a quiet hour is Eric.
-- **traffic**: Caddy's access log for the day, bots split out by user
-  agent, page requests by page (hall, rules, guide) and room links opened,
-  referrers and campaign tags.
+- **traffic**: Caddy's access log for the day, people and bots apart. A
+  bot is known by its user agent, or by its address: scanners ask for
+  paths no game serves, monitors come back all day and never play. Then
+  page requests by page (hall, rules, guide), rooms opened from the site
+  ("rooms opened here"), room links opened, the apps a link was previewed
+  in ("shared on"), referrers and campaign tags.
 - **players today / NEW today**: names seated in rooms created today;
   NEW means the name's first room ever is today.
 - **rooms today**: one line each: time, code, humans vs bots, empty