[EraPartner]

Requested by EraPartner · project thread

What

New docs/guides/service-setup/ with an index and one guide per service kind (13). Each guide covers:

1. What to enable on the service.
2. Which credential to create, using the narrowest one the service offers. Examples: a Bitcoin rpcauth user with an rpcwhitelist of exactly the methods Watchman calls, an Alby Hub readonly token, a read-only SNMP community limited to the subtrees Watchman walks, SNMPv3 for Synology, and non-admin SSH users with restrict,from= keys.
3. What to enter in each Watchman form field.
4. How to check that it works, and a troubleshooting table based on the error strings in the code.

Every "what Watchman reads" list was taken from the service code (apps/backend/src/domain/services/*, bootstrap/registerServices.ts, config/schemas/fieldMetadata.ts).

Doc drift fixed along the way

• integrations/adguard.md: removed the claim about "protection toggle control" (Watchman is read-only, ADR-032).
• integrations/homebridge.md: the health probe is statusPath (/api/status/server-information), not /api/status/homebridge.
• integrations/bitcoin.md: removed "optionally through Tor" (no proxy support in code). Marked zmqRawtxEndpoint as stored but unused.
• guides/index.md: rebuilt the broken guide table.
• components/use-service-health.md: rewritten from apps/frontend/src/hooks/useServiceHealth.ts. It described useAdGuardProtectionToggle and useClearCache hooks that don't exist, and old signatures. (api/adguard.md and components/optimized-service-card.md also mention them, but they are already marked superseded/deprecated, so I left them.)

Links

Each integration page links to its guide. The guides are also linked from integrations/index.md, guides/index.md, INDEX.md and getting-started.md. I added a CHANGELOG entry.

Decisions (picked per the project's best-option rule)

Decision	Choice	Why
Where the guides live	A new docs/guides/service-setup/ folder, not new sections in docs/integrations/*	The integration pages are developer reference. Users need short step-by-step pages. Each guide and integration page link to each other.
Claims I couldn't test (third-party config syntax, permissions)	Marked inline with [!warning] Unverified	There was no live service and limited network access. Project rule: never overstate.
Test connection	Documented as fixed: OK when the service answers, Failed: <reason> when it doesn't	#146 (merged) makes the editor read snapshot.reachable (apps/frontend/src/lib/connectionTest.ts). The earlier "known issue" callout is removed.

Bugs found, not fixed here (reported to the bug threads)

• Test connection showed OK for a down service: fixed in fix(frontend): UI bug pass (enable toggle, test result, detail sheet, nav, errors) #146.
• The SSH client (infra/ssh/) does no host-key verification. This affects Mac Mini and Raspberry Pi.
• Roon: node-roon-api's persisted-state location is never set (unverified whether the pairing token survives restarts).

Validation

• Docs-only change, so CI doesn't run (paths-ignore: docs/**, *.md).
• A local script checked that the new and changed pages have the required frontmatter fields (title, type, status, date, tags, description, aliases) and that every docs/ wikilink in the new guides resolves: 0 problems.
• Rebased onto main at f0a6fd2 (fix(frontend): UI bug pass (enable toggle, test result, detail sheet, nav, errors) #146).
• Prettier isn't available in the cloud environment, so it wasn't run.
• No OpenAPI, PlantUML or flow-visualizer changes are needed: there are no behaviour, API or architecture changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_018QJtaHZGu52MpwGvKuHP8x