[twwwy]

Hardware record for the Sample Locks 0.1.8-experimental draft (sdk/drafts/pattern-sample-locks/TESTING.md). Documentation only: no code, package or version change.

@repeat98, this answers your third point for 0.1.8: lock two patterns, save, reload, power cycle, both locks return; then Clear one, save, reload, it stays clear.

Results (MKII, OS 1.40C, flashed public base 9b3ba417…, package 3e13c46f…)

• With the 20 kept modules plus Sample Locks, on a freshly power-cycled unit:
  • FUNC+PART showed both rows, before and after AED SLICE use.
  • Lock on two patterns, then save and reload: passed.
  • Keep verified 21 saved and 21 live.
  • After a physical power cycle the exact set returned (cold start, set identity 38436efb…) and both patterns' locks returned.
  • Clear on one pattern, then save and reload: it stayed clear.
• Before that power cycle, the rows did not appear in three trials after a long session. Throughout, the shared status word carried Beat Slicer's tick signature, even when the base reported Beat Slicer removed. Taking Beat Slicer out showed the rows. The emulator on the same base and packages never reproduced it. Cause not found; also left as a finding on the agent board.

Panel results are as the author reported them. USB readings (inventory, set identities, self-test, status word) were observed by the session.

Not covered

Audio, MKI, maximum-size edits, live-recording refusal and playback-running Apply on this base. The stack/interrupt and benchmark points from your reply are not in this PR.

Guides

Three gaps, not fixed here because a module PR stays to the module; they'd go in a separate Docs: PR to docs/OCTATRACK_DRIVING.md if wanted:

• After a long-held trial, rollback on the trial's own connection can fail with "enter was not confirmed". A fresh connection rolls back cleanly.
• A whole-set offer refused at verify gives its reason only in the self-test record's refusal field: RUNTIME_IN_USE (7) when a project track uses a module being removed.
• The draft's capture_emulator.py calls stdbuf, which macOS lacks; its ot_emu builds are Linux-only, so it runs in the toolchain container.

🤖 Generated with Claude Code