Skip to content

Commit 757481c

Browse files
committed
docs(changelog): note tier-1 bugfixes, perf, and quality work
1 parent 5ba0fa4 commit 757481c

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

CHANGELOG.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,21 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/).
66

77
## [Unreleased]
88

9+
### Added
10+
11+
- `omnifs dev` and `omnifs up` now thread the session's preopened provider paths into the runtime container launch, so providers that require host-path access (such as the db provider's SQLite database directory) are bound into the container.
12+
13+
### Changed
14+
15+
- Lower latency and memory churn on the read and listing hot paths: `read_file` now does a single canonical-object lookup per call, a projection that materializes many objects commits its object-cache writes in one redb transaction instead of one fsync per object, and object leaf-set merges and non-exhaustive directory-listing merges are no longer quadratic in the size of the object or directory. Observable results are unchanged.
16+
- Internal code-quality pass across the host, SDK, CLI, and providers. No behavior change.
17+
18+
### Fixed
19+
20+
- FUSE now preserves a learned exact file size across later cached-metadata refreshes. A full-deferred read can learn a file's size before a refresh revisits the same inode; the refresh previously reset the size to the unknown-size sentinel, so stat-based tools (`ls -l`, `wc -c`, `du`) reported an unknown size after the content had already been materialized. The learned size is now kept when the refresh still describes the same content identity.
21+
- Negative-lookup ("not found") cache entries no longer grow without bound. Tombstones were garbage-collected, but expired negative entries lingered until their exact path was read again or invalidated, accumulating indefinitely on long-running mounts with many failed lookups. They are now swept alongside the tombstone GC.
22+
- The arXiv provider no longer aborts on a JSON encode failure. Pretty-JSON serialization is now a single shared SDK helper with one non-panicking failure policy.
23+
924
## [0.2.1] - 2026-06-08
1025

1126
### Fixed

0 commit comments

Comments
 (0)