Sam & Claude
6bade5d04e
Consolidates the operator-USB work into main now that the AMD ASUS hardware-evidence collection is closed and Codex is parked. Brings the live-session hardware lane (XInput/libinput touchpad guard, internal audio + resolver bootstrap, hw-report with gated public upload, operator-USB branding) and the config-only XFCE panel polish (Pass 1 + Pass 2: branded Whisker PNG, xkb text mode, panel 40px, systray square-icons). Conflict: doc/LLM-PROVIDER-HARNESS.md was evolved on both sides. Resolved as a union with no content lost — the xfce-side harness/provider/fabric restructure is the base, and main's two unique blocks (Verifying Key Cleanup flow, the 2D Platform x Harness matrix + populate/add procedures) are preserved. The doc owner may later dedupe the overlap between the two 1D matrices and the 2D matrix. Verification debt stays explicit and open (not closed by this merge): XFCE visual-polish confirmation and the next rebuilt-image hardware retest, per doc/XFCE-PANEL-BUGS-HANDOFF.md and PLAN-OPERATOR-USB-NEXT.md. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
67 lines
2.1 KiB
Markdown
67 lines
2.1 KiB
Markdown
# Zed Vulkan Handoff
|
|
|
|
**From:** Pi ISO Developer
|
|
**Date:** 20.maj.2026
|
|
**Status:** IN-PROGRESS — AMD Vulkan proof recorded; Intel and Zed policy remain open
|
|
|
|
## Deletion Criteria
|
|
|
|
- [ ] Latest operator USB image boots to SDDM/XFCE on Intel hardware.
|
|
- [ ] `vulkaninfo --summary` succeeds on Intel hardware and output is recorded.
|
|
- [x] Latest operator USB image boots to SDDM/XFCE on AMD/Ryzen hardware.
|
|
- [x] `vulkaninfo --summary` succeeds on AMD/Ryzen hardware and output is
|
|
recorded in `doc/AMD-ASUS-XFCE-LIVE-USB-FINDINGS.md`.
|
|
- [ ] Operator decides Zed telemetry / AI-provider default posture before any
|
|
move from disk-install extras to live rootfs.
|
|
|
|
## Tasks
|
|
|
|
- [x] Keep baseline live editor stack lightweight: Mousepad + Geany + Micro.
|
|
- [x] Add `vulkan-tools` to the live image so Codex ISO Builder can test Vulkan without
|
|
installing extra packages.
|
|
- [x] Park `zed-editor` in `pkg-list-disk-install-extras.txt`, not live rootfs.
|
|
- [ ] Codex ISO Builder: run Intel Vulkan check:
|
|
|
|
```sh
|
|
vulkaninfo --summary
|
|
```
|
|
|
|
- [x] Codex ISO Builder / Operator: AMD/Ryzen Vulkan check passed on ASUS ZenBook UX325UA:
|
|
|
|
```text
|
|
AMD Radeon Graphics (RADV RENOIR)
|
|
Mesa 24.1.7
|
|
```
|
|
|
|
- [ ] Codex ISO Builder: if `vulkaninfo --summary` fails, capture:
|
|
|
|
```sh
|
|
pciconf -lv | grep -B3 -A4 -E 'VGA|display'
|
|
kldstat | grep -E 'drm|i915|amdgpu|radeon'
|
|
ls -l /dev/dri
|
|
dmesg | tail -120
|
|
```
|
|
|
|
## Results (fill in when done)
|
|
|
|
- Build: pending
|
|
- Tests: partial hardware proof recorded
|
|
- Intel Vulkan: pending
|
|
- AMD/Ryzen Vulkan: pass — RADV RENOIR shown by `vulkaninfo --summary`
|
|
- Bugs found: none for AMD Vulkan path
|
|
|
|
## Open Questions
|
|
|
|
- Should Zed Assistant be disabled by default, pointed at the same provider keys
|
|
as `pi`/`codex`, or left unconfigured for installed systems only?
|
|
- Is Zed worth live-rootfs size after Vulkan proof, or should it remain a
|
|
disk-install/offline-repo extra?
|
|
|
|
## Delete After
|
|
|
|
Delete this file after both Intel and AMD Vulkan results are recorded and the
|
|
Zed telemetry / AI-provider posture is decided:
|
|
|
|
```sh
|
|
git rm doc/ZED-VULKAN-HANDOFF.md
|
|
```
|