Phase 1: Windows log collection + full-text search

Extends the agent, ingest, storage, api, and web with Windows Event
Log/ETW sourcing and Tantivy-backed free-text search, per the approved
Phase 1 plan.

- CLAUDE.md: materialized on disk (never existed as a file before) with
  a new Phase 1 "done looks like" section.
- agent: Windows Event Log (EvtSubscribe) and ETW sources, Windows
  service wrapper (install/uninstall/run-service), both feature- and
  target_os-gated so Linux builds/tests/clippy stay unaffected. Also
  fixed two pre-existing Phase 0 clippy gaps (dead-code on
  default-features-only builds, a type-inference edge case) found while
  testing every feature combination properly for the first time.
  UNVERIFIED on real Windows -- no Windows toolchain existed anywhere in
  the build environment; flagged prominently in three places.
- proto/ingest: new record_id field, assigned once server-side in
  ingest's gRPC front end so ClickHouse and Tantivy agree on the same ID
  for the same record.
- storage: record_id column + bloom filter index, verified against a
  live ClickHouse.
- search: new service, Tantivy index, rskafka consumer as an independent
  second consumer group on the same Redpanda topic ingest already reads.
- api/web: new /search endpoint and page, sharing the query page's
  result-table shape and component.
- hack/windows-fixture: sends realistic Windows-shaped data straight to
  ingest, so the pipeline's handling of it is verifiable without a
  Windows host.

Verified end-to-end on the live docker-compose stack: the same record_id
comes back from both /query and /search for the same log line, including
for windows-fixture's synthetic Windows Event Log data. Real bugs found
and fixed along the way: api/Dockerfile missing proto/ in its build
context, search's logs being completely silent (RUST_LOG gap), and
search/target/ missing from .gitignore/.dockerignore.

search/src/config.rs

@@ -0,0 +1,44 @@
+use anyhow::{Context, Result};
+use std::path::PathBuf;
+use std::time::Duration;
+
+/// All via environment variables, same convention as /ingest and /api —
+/// no config file format for this service either.
+pub struct Config {
+    pub grpc_listen_addr: String,
+    pub redpanda_brokers: Vec<String>,
+    pub redpanda_topic: String,
+    pub index_path: PathBuf,
+    pub offsets_path: PathBuf,
+    pub commit_interval: Duration,
+}
+
+impl Config {
+    pub fn load() -> Result<Self> {
+        let commit_interval_ms: u64 = getenv("COMMIT_INTERVAL_MS", "2000")
+            .parse()
+            .context("COMMIT_INTERVAL_MS must be a number")?;
+
+        Ok(Self {
+            // Rust's SocketAddr parser needs a full address, unlike Go's
+            // net package (ingest/api's ":PORT" convention won't parse
+            // here).
+            grpc_listen_addr: getenv("GRPC_LISTEN_ADDR", "0.0.0.0:50052"),
+            redpanda_brokers: getenv("REDPANDA_BROKERS", "localhost:9092")
+                .split(',')
+                .map(str::to_string)
+                .collect(),
+            redpanda_topic: getenv("REDPANDA_TOPIC", "sentry.logs.raw"),
+            index_path: PathBuf::from(getenv("INDEX_PATH", "/var/lib/sentry-search/index")),
+            offsets_path: PathBuf::from(getenv(
+                "OFFSETS_PATH",
+                "/var/lib/sentry-search/offsets.json",
+            )),
+            commit_interval: Duration::from_millis(commit_interval_ms),
+        })
+    }
+}
+
+fn getenv(key: &str, fallback: &str) -> String {
+    std::env::var(key).unwrap_or_else(|_| fallback.to_string())
+}