Since v0.2.0, bcdb can load a Business Central export into a running container in seconds, without needing the schema to match first. Getting the defaults safe took locking myself out of my own admin login.

394 commits and 351 merged pull requests since September 3, from implementation and review agents running against AL Runner continuously since Saturday. What came out of it: a Windows cross-check that caught a real BC-on-Linux gap, a first honest measurement of test coverage against Microsoft's own test suite, and one hang bug traced to a report running 101,000 extra times.

Why I built a separate test suite that runs against a real BC service tier instead of AL Runner's in-memory emulator: 101 merged PRs and 566 AL files identifying exact AL language behavior, so AL Runner has a known-correct answer to match and I find out fast if Microsoft ever changes that behavior.

v2.4.0 through v2.10.0: you can now hydrate the runner's in-memory database from a real BC backup and test against actual Cronus data, breakpoint debugging is back, coverage can now be attributed per test for mutation testing, and one change that fails runs the old runner used to let through.

A command-line tool and .NET library that decode a BC .bak or .bacpac file directly — no SQL Server, no restore, no service tier — verified page-for-page against a real restore.