docs: list the tag and file hooks in the pre-commit guide

- The hook table gains check-files (CC302-CC304) and check-tag (CC401),
  pre-push hooks since 2.16.0 that the README already sends readers here
  for.
- check-message and the App run CC001-CC016 since 2.18.0, not CC001-CC013.
- A note says pre-commit runs no hook for a push that creates a ref without
  new commits, so a tag pushed on its own after its commit is never checked.

Checked with pre-commit 4.6.2 at rev v2.18.3: check-files rejected a 4 KB
file over max_size = "1KB", check-tag rejected release-2.0 pushed with its
commit, and release-1.0 pushed alone on an already-pushed commit ran no hook.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013rE6bouKaJvsRyKA4tjqCb

Author: claude

docs/guides/github-app.md

@@ -47,7 +47,7 @@ way everywhere:
 
 ### Which rules
 
-The App runs the commit message, author and branch rules — [CC001–CC013](../rules.md#commit-message-rules),
+The App runs the commit message, author and branch rules — [CC001–CC016](../rules.md#commit-message-rules),
 [CC101–CC102](../rules.md#author-rules) and [CC201–CC202](../rules.md#branch-rules) —
 with the commit's own branch as the branch under test. One thing it does not
 do: the push, file and tag rules ([CC301–CC304](../rules.md#push-rules),

docs/guides/pre-commit.md

@@ -36,18 +36,24 @@ That is it. The next malformed commit message is rejected before it exists.
 
 | Hook ID | Stage | Rules |
 |---|---|---|
-| `check-message` | `commit-msg` | [CC001–CC013](../rules.md#commit-message-rules) |
+| `check-message` | `commit-msg` | [CC001–CC016](../rules.md#commit-message-rules) |
 | `check-branch` | `pre-commit` | [CC201–CC202](../rules.md#branch-rules) |
 | `check-author-name` | `pre-commit` | [CC101](../rules.md#cc101) |
 | `check-author-email` | `pre-commit` | [CC102](../rules.md#cc102) |
 | `check-no-force-push` | `pre-push` | [CC301](../rules.md#cc301) |
+| `check-files` | `pre-push` | [CC302–CC304](../rules.md#push-rules) |
+| `check-tag` | `pre-push` | [CC401](../rules.md#cc401) |
 
-`check-no-force-push` also needs its own install:
+The three `pre-push` hooks need their own install too:
 
 ```console
 $ pre-commit install --hook-type pre-push
 ```
 
+pre-commit runs no hook for a push that creates a ref without carrying new
+commits. So a new tag pushed on its own, when the commit it points at is
+already on the remote, is never seen by `check-tag`.
+
 ## Configuring without a TOML file
 
 Options can be passed as hook arguments, which keeps everything in one file: