alerts: Teams webhook fan-out (contract 0.14.0) + printedparts detail revision column

send_webhook(title,text) posts alerts to an optional webhook (Teams Incoming
Webhook / Workflow, or generic JSON) via alert_webhook_url + alert_webhook_format
settings; send_alert fans out to it alongside email; exposed on shopdb.api
(0.13.0->0.14.0, PLUGIN-HOOKS synced); low-stock posts on its custom-recipient
path too. Also: recent-transactions table shows the consumed print-file revision.

docs/PLUGIN-HOOKS.md

@@ -9,7 +9,7 @@ The contract is locked in [ADR-001](../docs/adr/ADR-001-asset-as-platform-contra
 The framework declares its contract version in `shopdb/__init__.py`:
 
 ```python
-__contract_version__ = '0.13.0'
+__contract_version__ = '0.14.0'
 ```
 
 Each plugin's `manifest.json` declares the range of contract versions it supports:
@@ -509,6 +509,10 @@ What `shopdb.api` exposes:
 - Mailer (0.12.0): `send_email(to, subject, html, text=None)` and
   `send_alert(subject, html, text=None)` - settings-first, no-op safe when
   email is unconfigured; send_alert targets the site's alert_recipients
+- `send_webhook(title, text)` (0.14.0) - POST an alert to the configured
+  `alert_webhook_url` (Teams Incoming Webhook / Workflow, or generic JSON via
+  the `alert_webhook_format` setting); best-effort, no-op when unset.
+  `send_alert` fans out to this automatically alongside email.
 
 ```python
 from shopdb.api import db, Asset, AssetType, success_response, paginate_query