v0.9.8

adOmnia 0.9.8 - Complete local log investigations

This release turns Log Inspector from an importer into a complete, local-first
investigation workspace. A developer can collect evidence from files, running
containers and adOmnia traffic, follow one request across services, reproduce it,
and hand a redacted offline package to a colleague.

Investigation workflow

• Add, remove, disable, rename and reload multiple sources without replacing the
  current session. Repeated inputs are detected and deduplication remains explicit.
• Inspect correlated requests as a service waterfall, pair request and response
  payloads across separate rows, compare calls, open surrounding source lines and
  group recurring errors without losing the original events.
• Search with typed expressions such as
  duration_ms > 1000 AND (status = 500 OR status = 502), including parentheses,
  AND/OR/NOT, exact equality, numeric comparisons, ranges, null/missing tests
  and array paths. Invalid syntax is reported instead of silently coercing types.
• Promote discovered fields to stable table columns, resize and reorder them, and
  save independent presets for each detected log format.

Persistence and evidence

• Investigation sessions are saved locally in a versioned IndexedDB format.
  Metadata and large source contents are stored separately; query, layout,
  selection, bookmarks and notes are restored when adOmnia reopens.
• A selected chain can be previewed and exported as a redacted JSON evidence
  package or Markdown summary with timeline, payloads, original rows, sources,
  filters and notes. Hidden UI fields are distinguished from values actually
  removed by redaction.

From logs to development

• Build an editable Composer request from an observed call without automatically
  sending it. Missing host values use the active environment through {{baseUrl}}.
• Propose Flow steps, verified response-to-request mappings and Mock Server
  fixtures from a correlated chain; ambiguous value coincidences stay labelled.
• Jump between Log Inspector, Browser Debug, Composer history and proxy traffic
  using correlation and trace headers.
• Parse Java, Go, JavaScript and Python stack frames, map them to explicitly chosen
  local repositories and open the resolved file and line safely.
• Validate observed request and response payloads against OpenAPI schemas already
  present in adOmnia collections, with JSONPath-level violations.

Live and large inputs

• Tail local files with rotation handling or stream kubectl logs, oc logs and
  docker logs into the same bounded, stoppable investigation session.
• Index oversized logs on disk in the Go sidecar and query them incrementally with
  pagination, time budgets and cancellation instead of loading the full file into
  browser memory.

Fixes

• A .log dropped inside Log Inspector is now owned only by that panel. It no
  longer bubbles into the global collection importer, so the supported file does
  not produce a false “Unsupported file” notification or a duplicate native drop.

Compatibility and privacy

• Existing Log Inspector preferences remain backward compatible as new column and
  session fields are added.
• Sessions, indexes, source mappings and evidence generation remain local. No
  telemetry or cloud service is introduced.

Verification

• 443 frontend tests across 91 files.
• Frontend TypeScript compilation and production build.
• Go build and complete backend test suite.