docs(api,mcp): tool counts, changelog backfill, version-header honesty, lazy auth, endpoint map (#1929)

Brings the developer-facing API and MCP docs back in line with origin/main
(audit 2026-08-26). Docs only; no runtime behaviour changes.

- Tool counts: the server registers 153 tools; docs said 90+/100+/120.
  All now say "150+" (connect-claude, gnubok-mcp README, plugin README,
  mcp-server rules, CLAUDE.md, registry entry with refreshed updatedAt).
  Not derived from the tools array: lib/ must not import @/extensions/.
- REST changelog: backfilled the additive 2026-08 changes (#1909 report
  date ranges + PDFs, #1864 POST /companies, #1773 vat-declarations,
  #1405 PATCH settings, #1724/#1788 customer personal_number, #1809
  cash_account_id filter). API version date unchanged.
- Version headers: Gnubok-Deprecation is planned, not emitted; the
  Gnubok-Version request header is not read today (version.ts comment,
  versioning page, conventions overlay, regenerated skills/accounted-api).
- connect-claude Path A documents lazy auth (connector works before an
  account exists; sign-in on the first company-scoped call).
- MCP server README: real Anthropic SDK call sites, real resource URIs,
  pending-operations widget, public-tools/tasks/origin-guard/pii-guard.
  Rules file gains Lazy auth + feedback/tasks paragraphs.
- api-routes endpoint map regenerated from the filesystem (560 routes,
  55 families incl. v1, agent, reconciliation account-keyed, dimensions,
  peppol, rot-rut, webshop-orders, mileage, billing, skatteverket,
  receipt-hunt).
- gnubok-mcp/accounted-mcp: /settings?tab=api is the pre-redesign URL;
  now /settings/api (README + help hints, no version bump).

Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

lib/api/v1/version.ts

@@ -1,11 +1,14 @@
 /**
  * The current API version date.
  *
- * Echoed in every response's `meta.api_version` and accepted as the optional
- * `Gnubok-Version` request header for future date-pinned breaking changes.
+ * Echoed in every response's `meta.api_version` and stamped as the
+ * `Gnubok-Version` response header (with-api-v1.ts). A `Gnubok-Version`
+ * REQUEST header is reserved for future date-pinned breaking changes: nothing
+ * reads it today, every request gets the current version.
  *
- * Bump this when shipping a breaking change inside v1; older versions are
- * preserved as long as integrators pin to them via the header.
+ * Bump this only for a breaking change inside v1 (additive changes never bump
+ * it); that is also when request pinning gets wired so integrators can keep
+ * the older shape.
  */
 export const API_V1_VERSION = '2026-05-12'