feat: Implement NotifyPanelComponent with unit tests and mock API service

- Added NotifyPanelComponent for managing notification channels and rules.
- Implemented reactive forms for channel and rule management.
- Created unit tests for NotifyPanelComponent to validate functionality.
- Developed MockNotifyApiService to simulate API interactions for testing.
- Added mock data for channels, rules, and deliveries to facilitate testing.
- Introduced RuntimeEventFactoryTests to ensure correct event creation with build ID.

docs/ops/zastava-runtime-operations.md

@@ -129,3 +129,32 @@ It aligns with `Sprint 12 – Runtime Guardrails` and assumes components consume
 - Grafana dashboard JSON: `docs/ops/zastava-runtime-grafana-dashboard.json`.
 - Add both to the monitoring repo (`ops/monitoring/zastava`) and reference them in
   the Offline Kit manifest.
+
+## 7. Build-id correlation & symbol retrieval
+
+Runtime events emitted by Observer now include `process.buildId` (from the ELF
+`NT_GNU_BUILD_ID` note) and Scanner `/policy/runtime` surfaces the most recent
+`buildIds` list per digest. Operators can use these hashes to locate debug
+artifacts during incident response:
+
+1. Capture the hash from CLI/webhook/Scanner API (example:
+   `5f0c7c3cb4d9f8a4f1c1d5c6b7e8f90123456789`).
+2. Derive the path: `<hash[0:2]>/<hash[2:]>` under the debug store, e.g.
+   `/var/opt/debug/.build-id/5f/0c7c3cb4d9f8a4f1c1d5c6b7e8f90123456789.debug`.
+3. If the file is missing, rehydrate it from Offline Kit bundles or the
+   `debug-store` object bucket (mirror of release artefacts). Use:
+   ```sh
+   oras cp oci://registry.internal/debug-store:latest . --include \
+     "5f/0c7c3cb4d9f8a4f1c1d5c6b7e8f90123456789.debug"
+   ```
+4. Attach the `.debug` file in `gdb`/`lldb` or feed it to `eu-unstrip` when
+   preparing symbolized traces.
+5. For musl-based images, expect shorter build-id footprints. Missing hashes in
+   runtime events indicate stripped binaries without the GNU note—schedule a
+   rebuild with `-Wl,--build-id` enabled or add the binary to the debug-store
+   allowlist so the scanner can surface a fallback symbol package.
+
+Monitor `scanner.policy.runtime` responses for the `buildIds` field; absence of
+data after ZASTAVA-OBS-17-005 implies containers launched before the Observer
+upgrade or non-ELF entrypoints (static scripts). Re-run the workload or restart
+Observer to trigger a fresh capture if symbol parity is required.