refactor: model message schemas after IRC RFC 1459/2812

Replace c2s/s2c/s2s taxonomy with IRC-native structure:
- schema/commands/ — IRC command schemas (PRIVMSG, NOTICE, JOIN, PART,
  QUIT, NICK, TOPIC, MODE, KICK, PING, PONG)
- schema/numerics/ — IRC numeric reply codes (001-004, 322-323, 332,
  353, 366, 372-376, 401, 403, 433, 442, 482)
- schema/message.json — base envelope mapping IRC wire format to JSON

Messages use 'command' field with IRC command names or 3-digit numeric
codes. 'body' is a string (IRC trailing parameter), not object/array.
'from'/'to' map to IRC prefix and first parameter.

Federation uses the same IRC commands (no custom RELAY/LINK/SYNC).

Update README message format, command tables, and examples to match.

schema/numerics/004.json

@@ -0,0 +1,39 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://git.eeqj.de/sneak/chat/schema/numerics/004.json",
+  "title": "004 RPL_MYINFO",
+  "description": "Server info (name, version, available modes). RFC 2812 \u00a75.1.",
+  "$ref": "../message.json",
+  "properties": {
+    "command": {
+      "const": "004"
+    },
+    "to": {
+      "type": "string"
+    },
+    "params": {
+      "type": "array",
+      "items": {
+        "type": "string"
+      },
+      "description": "[server_name, version, user_modes, channel_modes]."
+    }
+  },
+  "required": [
+    "command",
+    "to",
+    "params"
+  ],
+  "examples": [
+    {
+      "command": "004",
+      "to": "alice",
+      "params": [
+        "chat.example.com",
+        "0.1.0",
+        "o",
+        "imnst+ov"
+      ]
+    }
+  ]
+}