Compress always-on contracts and restore pagination fields

The always-on set is paid by every session, so it gets the tightest
form: git-sync-check shrinks to its procedural core, testing-policy
moves the table-test example to README.md and folds the agent
instructions into the rules, go-code-style inlines the error-wrapping
example. Per-session read cost drops from 403 to 336 lines.

Also restore the pagination response fields in table-management: the
previous dedup replaced them with a reference to go-api, which the
table router line does not load.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

rules/patterns/table-management/contract.md

@@ -91,7 +91,8 @@ Canonical mapping:
 ## Pagination Rules
 
 - Pagination is server-side. Never load all rows and paginate client-side.
-- Query parameters and list response metadata follow the `go-api` contract.
+- Query parameters carry page state (`?page=2&per_page=50`); the response includes
+  `total_count`, `page`, `per_page`, `total_pages` (shape per the `go-api` contract).
 - `page` is 1-based; `per_page` defaults to a fixed project constant (e.g. 50) and may be
   changed from a fixed set (25 / 50 / 100).
 - Display: "Showing 51–100 of 342" — always show the range and total.