feat(serve): name the investigation tools the loop runs without, once at startup

[Smana]

Fixes #467.

Why

lore investigate tells the user which evidence backends are off. lore serve never did: it announces at Info everything it turned on (the ledger, the rate limit, the coalescer, the debounce, the watcher, the poller), so an in-cluster install missing its evidence backends looked identical in the logs to one that has them all. The minimal Helm profile wires neither metrics.url nor logs.url, and was indistinguishable from a misconfigured full one.

What

One line, next to the other pure-config startup notices:

INFO running without tools=["metrics (query_metrics)","logs (query_logs)"]

It reuses disabledTools, the CLI's pure function over config, so the two commands cannot disagree about what counts as off.

The issue's open questions, decided

• Info, not Warn. It fires on every boot of a deliberately-minimal install, and a warning that fires on purpose is tuned out.
• It fires even when intentional. The log is where someone looks when investigations seem thin, and an Info line costs nothing.
• Scope stays what disabledTools covers: metrics, logs, the catalog. Widening to flows, cloud and the forge is a change to disabledTools, and then both commands get it. Left as a follow-up rather than smuggled in.

Pinned

The same way the recall-decay warning is: RunServe must call disabledTools directly in its own body, not in a closure the incident path runs, exactly once, bind the result, and pass it to .Info in the same statement. The shared assertion matched callees by their *Warning suffix, which this notice deliberately lacks, so it now matches through a name-agnostic callName, and warningCallName is that plus the suffix filter. The existing pins are unchanged.

Verified

TDD: the pin failed first against the unmodified serve.go (verified after fixing the suffix mismatch, with the edited file set aside), then passed. Full gate: go build, go vet, gofmt -l clean, go test ./..., hack/lint.sh at 0 issues. One unrelated flake surfaced under load, TestRunRetriesReindexOnAPinnedRevision in internal/catalog; it passes three times in a row alone.