Update docs and add release artifacts

docs/bible/10-decisions.md

@@ -111,4 +111,94 @@ Top-level `README.md` and `CLAUDE.md` must remain minimal pointers/instructions.
 
 ---
 
+## ADL-009 — Redfish analysis is performed from raw snapshot replay (unified tunnel)
+
+**Date:** 2026-02-24
+**Context:** Live Redfish collection and raw export re-analysis used different parsing paths,
+which caused drift and made bug fixes difficult to validate consistently.
+**Decision:** Redfish live collection must produce a `raw_payloads.redfish_tree` snapshot first,
+then run the same replay analyzer used for imported raw exports.
+**Consequences:**
+- Same `redfish_tree` input produces the same parsed result in live and offline modes.
+- Debugging parser issues can be done against exported raw bundles without live BMC access.
+- Snapshot completeness becomes critical; collector seeds/limits are part of analyzer correctness.
+
+---
+
+## ADL-010 — Raw export is a self-contained re-analysis package (not a final result dump)
+
+**Date:** 2026-02-24
+**Context:** Exporting only normalized `AnalysisResult` loses raw source fidelity and prevents
+future parser improvements from being applied to already collected data.
+**Decision:** `Export Raw Data` produces a self-contained raw package (JSON or ZIP bundle)
+that the application can reopen and re-analyze. Parsed data in the package is optional and not
+the source of truth on import.
+**Consequences:**
+- Re-opening an export always re-runs analysis from raw source (`redfish_tree` or uploaded file bytes).
+- Raw bundles include collection context and diagnostics for debugging (`collect.log`, `parser_fields.json`).
+- Endpoint compatibility is preserved (`/api/export/json`) while actual payload format may be a bundle.
+
+---
+
+## ADL-011 — Redfish snapshot crawler is bounded, prioritized, and failure-tolerant
+
+**Date:** 2026-02-24
+**Context:** Full Redfish trees on modern GPU systems are large, noisy, and contain many
+vendor-specific or non-fetchable links. Unbounded crawling and naive queue design caused hangs
+and incomplete snapshots.
+**Decision:** Use a bounded snapshot crawler with:
+- explicit document cap (`LOGPILE_REDFISH_SNAPSHOT_MAX_DOCS`)
+- priority seed paths (PCIe/Fabrics/Firmware/Storage/PowerSubsystem/ThermalSubsystem)
+- normalized `@odata.id` paths (strip `#fragment`)
+- noisy expected error filtering (404/405/410/501 hidden from UI)
+- queue capacity sized to crawl cap to avoid producer/consumer deadlock
+**Consequences:**
+- Snapshot collection remains stable on large BMC trees.
+- Most high-value inventory paths are reached before the cap.
+- UI progress remains useful while debug logs retain low-level fetch failures.
+
+---
+
+## ADL-012 — Vendor-specific storage inventory probing is allowed as fallback
+
+**Date:** 2026-02-24
+**Context:** Some Supermicro BMCs expose empty standard `Storage/.../Drives` collections while
+real disk inventory exists under vendor-specific `Disk.Bay` endpoints and enclosure links.
+**Decision:** When standard drive collections are empty, collector/replay may probe vendor-style
+`.../Drives/Disk.Bay.*` endpoints and follow `Storage.Links.Enclosures[*]` to recover physical drives.
+**Consequences:**
+- Higher storage inventory coverage on Supermicro HBA/HA-RAID/MRVL/NVMe backplane implementations.
+- Replay must mirror the same probing behavior to preserve deterministic results.
+- Probing remains bounded (finite candidate set) to avoid runaway requests.
+
+---
+
+## ADL-013 — PowerSubsystem is preferred over legacy Power on newer Redfish implementations
+
+**Date:** 2026-02-24
+**Context:** X14+/newer Redfish implementations increasingly expose authoritative PSU data in
+`PowerSubsystem/PowerSupplies`, while legacy `/Power` may be incomplete or schema-shifted.
+**Decision:** Prefer `Chassis/*/PowerSubsystem/PowerSupplies` as the primary PSU source and use
+legacy `Chassis/*/Power` as fallback.
+**Consequences:**
+- Better compatibility with newer BMC firmware generations.
+- Legacy systems remain supported without special-case collector selection.
+- Snapshot priority seeds must include `PowerSubsystem` resources.
+
+---
+
+## ADL-014 — Threshold logic lives on the server; UI reflects status only
+
+**Date:** 2026-02-24
+**Context:** Duplicating threshold math in frontend and backend creates drift and inconsistent
+highlighting (e.g. PSU mains voltage range checks).
+**Decision:** Business threshold evaluation (e.g. PSU voltage nominal range) must be computed on
+the server; frontend only renders status/flags returned by the API.
+**Consequences:**
+- Single source of truth for threshold policies.
+- UI can evolve visually without re-implementing domain logic.
+- API payloads may carry richer status semantics over time.
+
+---
+
 <!-- Add new decisions below this line using the format above -->