Release v0.4.0

Title: Local persistence foundation

Status: Completed

Milestone: V0 software companion foundation

Version architecture: Architecture for v0.4.0

Archived records

The release delivered six epics, E24 through E29, and seventeen PBIs, PBI-086 through PBI-102. The bug register closed empty for the fourth release running. No limitation was resolved, LIM-014 was narrowed by PBI-102, LIM-008 was reworded to cover the save location as the second client of one hosted location policy, LIM-015, LIM-016, and LIM-017 were opened, and twelve limitations carry forward.

Identifier continuity

Identifiers do not restart after this release. The next active epic, PBI, bug, and ADR identifiers continue from the highest identifiers used before or during this release.

PBI-102 was opened after PBI-101 and belongs to E24, so the highest PBI identifier does not sit in the last epic of the release.

Release evidence

Evidence for the release claims is recorded in evidence.md and in section 10.5 of the version architecture. The verified toolchain is recorded in both places. The exit criteria are ticked in section 7.4 of the milestones document.

The persistence claim is that a world survives a process boundary through a versioned payload the Core owns and a storage boundary the host owns, and that it does so only when an operator supplies a path. No automatic save, no automatic load, no save location policy, and no embedded storage is claimed. The embedded claim remains cross-compile evidence for the classic LILYGO T-Display as ESP-IDF esp32, now including the storage contract compiled with no implementation selected.

Notes

• ADRs remain in docs/adr/. ADR-012, ADR-013, and ADR-014 were accepted during this release.
• Version architecture remains in docs/arch/arch-v0.4.0.md.
• Active planning continues in the root planning documents, which continue at E30 and PBI-103.
• These files are historical records. Edit them only under the rules in section 9 of the release process.
• The archived files keep their rollover content unchanged. Only their relative link paths were re-pointed so they resolve from this directory, which section 9 permits as a broken link fix.
• The manual desktop rendering and interaction observation that LIM-011 carries was not repeated for this release. It is carried forward from v0.3.0, because nothing in the release touches rendering, the frontend, or input.
• No git tag or frozen branch was created when this archive was written. Tagging v0.4.0 and creating release-v0.4.0 remain maintainer steps under section 7 of the release process.