RELEASE RECORD / 17 OCTOBER 2026
Bunker Evolved.
Release 1.0.
Released after the project owner completed the original → Bunker → original update cycle on an FM-1 and confirmed working audio and controls. The released firmware is byte-for-byte identical to the hardware-tested build.
Chrome editor 0.1
The new editor is a separate website component. It has 49,337 host assertions against the actual C handler and DOM interaction checks; physical USB acceptance and browser visual QA remain pending. It requires no additional firmware flash. Scope and architecture →
Package identity
| Release | Bunker Evolved 1.0 · 17 October 2026 |
|---|---|
| Internal build label | BE 1.0-RC2 (retained in the tested firmware) |
| Device identity | FM-1_7100002 |
| Package size | 610,090 bytes |
| SHA-256 | db0b50d0ae9c3bfccee76e3b93de09fffa55389169278a0c5899dad9c79e6bb8 |
Release 1.0 promotes the tested build without recompiling or changing its bytes. Its startup label still contains RC2. If you already run FM-1_7100002, you have this exact release and do not need to flash again.
Verified, with clear boundaries
- Owner hardware acceptance, 17 October 2026: Bunker → original, original → Bunker, then Bunker → original completed. Audio and controls worked. This is a report from one FM-1, not independent certification or a test of every board revision.
- 19 defined native regression suites; additional Bunker panel and library checks.
- GROW: 3,309,372 assertions across all keys, scales and styles, including undo and persistence.
- One-hour simulated-audio stress run: 3,606.5 seconds, at most eight voices. Additional 1,202.5 seconds with ASan and selected UBSan checks.
- C and WebAssembly rendering match bit for bit for 88,200 stereo frames.
- Modelled RC1 ↔ RC2 loader tests preserve protected boot and user regions. Browser update protocol tests cover malformed requests, disconnects, completion identity and retry.
Host tests cannot establish physical USB reliability, chip CPU headroom, battery behaviour or power-loss recovery. The owner’s normal original-firmware round trip is now recorded. Original V15 remains the documented installer baseline; the owner did not separately record the stock version string.
Detailed report and limitations →Installing from original firmware
The direct route is original FM-1 firmware → Bunker Evolved using the same M-UPGRADE-compatible MIDI protocol. The owner has completed this route and the return to original firmware. AMB-1 is not an intermediate requirement. Original V15 is the documented baseline. If an older original version does not enter update mode, use the manufacturer's supported updater to reach V15 first.
Back up data with tools appropriate to the firmware currently installed. Bunker's backup button supports compatible Bunker builds; it does not export proprietary stock or AMB music. Review the recovery guide before writing.