HAKCD v0.1.29 — Hardware Review Workflow (Phase V9)

Phase V9 — Hardware Review Workflow

Scaffolds tools/hardware_review/ as the human-in-the-loop gate every visual
asset must pass before claiming art_status='final'.

What landed

• tools/hardware_review/README.md — workflow spec (6 sections: overview,
  layout, capture script, hardware photo requirements, PASS/FAIL/WIP rubric,
  v0.2.0 build-blocking rule)
• tools/hardware_review/capture_screenshots.sh — Simulator capture driver
  with manual-protocol fallback (Linux Simulator does not expose scriptable
  capture in SDK 3.0.6)
• tools/hardware_review/per_version_template.md — per-release signoff
  template (table + scene-level review + overall verdict)
• tools/hardware_review/v0.1.29/{simulator,device}/ — first-version capture
  directories ready to populate

Workflow

sideload -> capture (9-scene minimum) -> photograph (arm's length, finger for
scale, no flash glare) -> sign off in SIGNOFF.md against commit SHA with
reviewer handle + ISO date + per-asset PASS/FAIL/WIP verdict.

Scenes captured per session

TitleScene, BedroomScene, ComputerScene, ModemScene, PhoneScene,
PlaygroundScene, LockpickScene, TysonScene, CoinVaultScene.

Blocking rule (activates at v0.2.0)

Once visual_spec.lua exists AND validate_visuals.sh checks human_reviewed +
art_status AND pdxinfo version >= 0.2.0: build FAILS if any
priority='critical' asset has human_reviewed != true OR
art_status == 'placeholder'. Until then, validator warns only.

Scope

pdxinfo bump + docs/scripts only. No .lua, no asset, no validator, no
Makefile changes. V3 owns the validator extension.