# ArchiveBeast™ Adaptive Capture Layout Green

## Changed

- Updated the capture library viewer to adapt panes by artifact components instead of assuming every capture has a PNG companion.
- DesktopBeast-style captures with a real PNG companion keep the three-pane layout:
  - capture list / metadata
  - visual companion preview
  - Markdown preview
- BrowserBeast™ v1.0 Freeware Markdown-first captures collapse the visual companion pane when no PNG exists and use a two-pane layout:
  - capture list / metadata
  - Markdown capture viewer
- Disabled image actions when the selected capture has no visual companion, with neutral tooltip language instead of a missing-file failure.
- Updated Browser capture parsing so BrowserBeast™ metadata is displayed from Markdown headers and Evidence Envelope fields:
  - status from `Capture Status` or `capture_status`
  - time from `Captured`, `created_at`, or file timestamp fallback
  - source from `Source` or `source_url`
  - OCR shown as `Browser text capture` when BrowserBeast™ has no OCR fields
- Added companion-file parsing for future captures that list PNG companions in the Evidence Envelope.

## Verified

- Built the WPF project with the bundled local .NET SDK:
  - `..\.dotnet-sdk\dotnet.exe build DataBeastDesktop.Spike001.csproj --no-restore`
- Build result: succeeded.
- Expected warning: NuGet vulnerability metadata could not be fetched because network access is restricted.

## Remaining Placeholders / Notes

- BrowserBeast™ v1.0 Freeware remains Markdown-first. No PNG companion capture was added.
- Future BrowserBeast™ Pro captures can use the three-pane layout automatically if a real PNG companion exists.
- Historical source identifiers still carry `DataBeastDesktop.Spike001`; public-facing app/package language now uses DesktopBeast™ EA Beta.

## Non-Actions

- No BrowserBeast™ Pro work started.
- No DesktopBeast™ polish started.
- No Cloudflare DNS touched.
- No deployment performed.

