templates: jmap, dav, karakeep, ttrss for personal-service projects

jmap and ttrss are custom images (mysources.co.uk/michal/{jmap-mcp,ttrss-mcp});
dav-mcp and @karakeep/mcp run on the node runner. Health checks are real
backend calls. Applied live 2026-09-30; these seeds keep the next mcpd
image rebuild from reverting them.

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

templates/ttrss.yaml

@@ -0,0 +1,26 @@
+name: ttrss
+version: "1.0.0"
+description: Tiny Tiny RSS — feeds, headlines, article content, read/star state, subscribe
+dockerImage: "mysources.co.uk/michal/ttrss-mcp:1.0.0"
+transport: STDIO
+repositoryUrl: https://mysources.co.uk/michal/ttrss-mcp
+# No command: the image's entrypoint IS the MCP server. Custom server; the
+# public tt-rss MCPs only take a pre-made session id and die when it expires.
+# This one logs in with user/password and re-logs-in on NOT_LOGGED_IN.
+healthCheck:
+  # A real getCategories call: a pass proves URL, login, and that the
+  # user's "Enable API access" preference is on.
+  tool: list_categories
+  arguments: {}
+  intervalSeconds: 60
+  timeoutSeconds: 10
+env:
+  - name: TTRSS_URL
+    description: Full API endpoint (e.g. http://ttrss.ttrss.svc.cluster.local/api/)
+    required: true
+  - name: TTRSS_USER
+    description: tt-rss user with "Enable API access" set in preferences
+    required: true
+  - name: TTRSS_PASSWORD
+    description: That user's password
+    required: true