On this page
Roadmap¶
Where MageObsidian has been, and where it goes next. Every milestone links to its changelog entry; what is planned carries no date until it is being built.
- The 2.0.0 cut 2.0.0
The whole stack was cut to 2.0.0 together: Vue islands, critical CSS, the optional Twig engine and the developer workflow.
- Storefront 3.x 3.0.0
The storefront line: a one-page checkout layout, a typed event bus with optimistic UI, and islands that hydrate over server-rendered markup.
- Cacheable checkout
August 2026: the checkout page is served from the full-page cache and its private data is filled in afterwards.
- Verified parity
The parity register was measured against Magento Open Source 2.4.9, entry by entry, with a test behind every covered one.
- 4.0 stable 4.0.0
The first stable release, with the framework and the storefront each released under one version. Storefront 4.0.1 followed the same day as a hotfix.
- 4.1: Luma parity complete 4.1.0
Every Luma screen the parity register tracks is covered by a test or resolved, with none left open. Also Subresource Integrity on payment pages, forms that follow the store configuration and in-store pickup, and the full verification suite running on Open Source, Mage-OS and Adobe Commerce.
- NextWider compatibility
More platforms and versions verified by the same matrix run, once they are measured.
Now, next, later¶
Now
Magento Open Source and Mage-OS 2.4.7 to 2.4.9, installed from Packagist and checked by the matrix run.
6 of 6 platforms verified (2026-10-06)Next
The full verification suite runs on Adobe Commerce 2.4.9: 659 tests passed on 2026-10-13, and every failure has a known cause. Still to do: the compatibility matrix, Cloud, payment gateways and Commerce-only features.
Verifying a real gateway through the payment extension point, which today is exercised only by a purpose-built probe.
Later
Provider-hosted video backgrounds and server-rendered Page Builder content types. They come from the comparison with other frontends, not from Luma, and stay blocked by decision until there is a way to do them well.
A page of stores running MageObsidian in production.
API and configuration reference generated from the code instead of written by hand.
What has been verified¶
Measured with the private verification harness, on the
theme-default / theme-base pair. The registers are measured against Magento Open Source 2.4.9;
the end-to-end rows name their platform. Each row carries the date it was measured:
| Register | Figure | Measured |
|---|---|---|
| Luma screens and handles | 457: all 322 that apply are done (312 covered by a test, 10 resolved); 135 out of scope | 2026-10-12 |
| Store settings Luma honours (functional audit) | 43: 39 resolved, 4 out of scope | 2026-10-12 |
| Gaps against other frontends (competitive audit) | 14: 10 resolved, 2 out of scope, 2 blocked by decision | 2026-10-12 |
| Security audit | 9: 4 covered, 5 resolved | 2026-10-12 |
| Performance audit | 6: 2 covered, 3 resolved, 1 out of scope | 2026-10-12 |
| Page layouts | 15 entries, 13 covered by an executed test, 2 out of scope | 2026-09-22 |
| End-to-end suite, Magento Open Source 2.4.9 | 682 passed, every failure with a known cause | 2026-10-13 |
| End-to-end suite, Mage-OS 3.1.0 | 672 passed, every failure with a known cause | 2026-10-13 |
| End-to-end suite, Adobe Commerce 2.4.9 | 659 passed, every failure with a known cause | 2026-10-13 |
| Build engine unit tests | 403 | 2026-10-13 |
| Harness unit tests | 383 | 2026-10-13 |
The first five rows are the parity register, 529 entries in all, split by where each entry came from. Each entry is in one of four states:
- Covered — a test ran and observed the behaviour on that platform. A declaration in a theme never counts as coverage on its own.
- Resolved — a gap an audit found (functional, competitive, security or performance) that has since been closed.
- Blocked — kept open on purpose, by the owner's decision; Known scope says why.
- Out of scope — not a screen to replace, or one decided against, each with its reason: item renderers that feed another screen, screens consolidated into one, the PayPal and Payment Services screens; Known scope lists them by family.
What these figures leave out is on Known scope.
Nothing on this page is a delivery promise; the versioning policy is.