Decisions needing owner input
Independent documentation/build work can continue while these decisions remain open. Do not infer approval from the owner’s absence.
| Decision | Current safe default | What needs input |
|---|---|---|
| Appliance lifecycle migration | Preserve adapter and working application branch; leave draft PR 2925 unchanged | Whether to keep a minimal upstream test-port improvement or replace the runner without source patches |
| Matching agent tools and access | Document verified Playwright setup and inventory gaps | Which additional integrations are essential and their credential owners |
| Fresh-machine rebuild | Explain known prerequisites and preserve scripts; no full rebuild claim | A disposable machine or explicit maintenance window for rehearsal |
| Task restoration and off-LAN validation | Controlled AC return passed; browser restart remains manual | A coordinated window, required tasks and human recovery access |
| Maintenance cadence and retention | Backlog only | Frequency, space thresholds and data-retention policy |
| Where the test bed scripts live | They stay in the appliance repository checkout under claude-notes/2026-10-05-test-bed/, an untracked folder on the Mac; this site links to them | Whether the run, measure and receiver scripts and the personal build script should move into a tracked place (this repository’s tooling, or a branch of the application repository) |
| Build server address | DHCP with a router reservation for its MAC; scripts and the appliance use 192.168.1.12 | Whether to prove the reservation by leaving the box off past the 24 h lease, or give it a static address |
| Power at home | Both machines come back by themselves; a run in progress is lost | Whether a UPS or a scheduled run window is worth it, after the 6 October loss |
The two test bed machines were added on 6 October through the contribution checklist; the feedback on the checklist from that contribution is in its pull request.
Public website access was approved on 6 October. Implementation and verified deployment status are recorded in website publishing.