Upstream sync — 2026-10-30

• Upstream: https://github.com/Ephemeral-AI-Lab/layerfs
• Mirrored: 56 open items (39 issues + 17 PRs)
• PRs are mirrored as issues because code/branches are not copied.
• Only exact-topic Excalidraw scenes are linked as comments.

Filters

• All synced
• Store / Remote / Lore
• Join-stall / FUSE
• Agent OS / Git

Store / Remote / Lore

• [upstream issue #506] Store backends (SQLite + PostgreSQL) and remote storage (MinIO first): first integration phase #16 — [upstream issue Store backends (SQLite + PostgreSQL) and remote storage (MinIO first): first integration phase Ephemeral-AI-Lab/layerfs#506] Store backends (SQLite + PostgreSQL) and remote storage (MinIO first): first integration phase
  upstream: Store backends (SQLite + PostgreSQL) and remote storage (MinIO first): first integration phase Ephemeral-AI-Lab/layerfs#506
• [upstream pr #507] #506: Store backends (SQLite + PostgreSQL) and remote Store files (MinIO first) #48 — [upstream pr #506: Store backends (SQLite + PostgreSQL) and remote Store files (MinIO first) Ephemeral-AI-Lab/layerfs#507] Store backends (SQLite + PostgreSQL) and remote storage (MinIO first): first integration phase Ephemeral-AI-Lab/layerfs#506: Store backends (SQLite + PostgreSQL) and remote Store files (MinIO first)
  upstream: #506: Store backends (SQLite + PostgreSQL) and remote Store files (MinIO first) Ephemeral-AI-Lab/layerfs#507
• [upstream issue #509] #506 Stores: one link per Store, connections bind to providers only #14 — [upstream issue #506 Stores: one link per Store, connections bind to providers only Ephemeral-AI-Lab/layerfs#509] Store backends (SQLite + PostgreSQL) and remote storage (MinIO first): first integration phase Ephemeral-AI-Lab/layerfs#506 Stores: one link per Store, connections bind to providers only
  upstream: #506 Stores: one link per Store, connections bind to providers only Ephemeral-AI-Lab/layerfs#509
• [upstream issue #510] #506 Live view: browse a Store in S3 without loading it #13 — [upstream issue #506 Live view: browse a Store in S3 without loading it Ephemeral-AI-Lab/layerfs#510] Store backends (SQLite + PostgreSQL) and remote storage (MinIO first): first integration phase Ephemeral-AI-Lab/layerfs#506 Live view: browse a Store in S3 without loading it
  upstream: #506 Live view: browse a Store in S3 without loading it Ephemeral-AI-Lab/layerfs#510
• [upstream issue #511] Remove, delete, prune and compact: branch.remove, project.delete, branch.prune, store.compact #12 — [upstream issue Remove, delete, prune and compact: branch.remove, project.delete, branch.prune, store.compact Ephemeral-AI-Lab/layerfs#511] Remove, delete, prune and compact: branch.remove, project.delete, branch.prune, store.compact
  upstream: Remove, delete, prune and compact: branch.remove, project.delete, branch.prune, store.compact Ephemeral-AI-Lab/layerfs#511
• [upstream pr #495] feat(persistence): export a Store's changed rows as bundles for replicas #53 — [upstream pr feat(persistence): export a Store's changed rows as bundles for replicas Ephemeral-AI-Lab/layerfs#495] feat(persistence): export a Store's changed rows as bundles for replicas
  upstream: feat(persistence): export a Store's changed rows as bundles for replicas Ephemeral-AI-Lab/layerfs#495
• [upstream issue #485] A read-only Store open (StoreService and SDK) for readers that must never write #20 — [upstream issue A read-only Store open (StoreService and SDK) for readers that must never write Ephemeral-AI-Lab/layerfs#485] A read-only Store open (StoreService and SDK) for readers that must never write
  upstream: A read-only Store open (StoreService and SDK) for readers that must never write Ephemeral-AI-Lab/layerfs#485
• [upstream pr #519] Open a Store read-only from StoreService and the SDK #45 — [upstream pr Open a Store read-only from StoreService and the SDK Ephemeral-AI-Lab/layerfs#519] Open a Store read-only from StoreService and the SDK
  upstream: Open a Store read-only from StoreService and the SDK Ephemeral-AI-Lab/layerfs#519
• [upstream issue #420] PostgreSQL compatibility for the global storage #36 — [upstream issue PostgreSQL compatibility for the global storage Ephemeral-AI-Lab/layerfs#420] PostgreSQL compatibility for the global storage
  upstream: PostgreSQL compatibility for the global storage Ephemeral-AI-Lab/layerfs#420

Sandbox / Mount / FUSE

• dsh-layerfs 0.1.0 on OrbStack (kernel 7.0.14): 8/10 scenario runs stop at workspace.unmount (TeardownCustody stage Join) #1 — dsh-layerfs 0.1.0 on OrbStack (kernel 7.0.14): 8/10 scenario runs stop at workspace.unmount (TeardownCustody stage Join)
  upstream: dsh-layerfs 0.1.0 on OrbStack (kernel 7.0.14): 8/10 scripted scenarios stop at workspace.unmount (stage Join); Docker Desktop 4.22.0 cannot create Sandboxes (API 1.43 < 1.54) Ephemeral-AI-Lab/layerfs#466
• [upstream issue #460] FUSE readers remain blocked after successful unmount: independent reproducer and Linux comparison (related to #426) #26 — [upstream issue FUSE readers remain blocked after successful unmount: independent reproducer and Linux comparison (related to #426) Ephemeral-AI-Lab/layerfs#460] FUSE readers remain blocked after successful unmount: independent reproducer and Linux comparison (related to Workspace mounted while its Sandbox starts cannot be unmounted (TeardownCustody { stage: Join }) and stays wedged Ephemeral-AI-Lab/layerfs#426)
  upstream: FUSE readers remain blocked after successful unmount: independent reproducer and Linux comparison (related to #426) Ephemeral-AI-Lab/layerfs#460
• [upstream pr #497] fix(fuse): bound the receive-loop join by a 1 s grace (#426, #460) #61 — [upstream pr fix(fuse): bound the receive-loop join by a 1 s grace (#426, #460) Ephemeral-AI-Lab/layerfs#497] fix(fuse): bound the receive-loop join by a 1 s grace (Workspace mounted while its Sandbox starts cannot be unmounted (TeardownCustody { stage: Join }) and stays wedged Ephemeral-AI-Lab/layerfs#426, FUSE readers remain blocked after successful unmount: independent reproducer and Linux comparison (related to #426) Ephemeral-AI-Lab/layerfs#460)
  upstream: fix(fuse): bound the receive-loop join by a 1 s grace (#426, #460) Ephemeral-AI-Lab/layerfs#497
• [draft] Design: workspace.exec runs in the container's initial mount namespace #3 — [draft] Design: workspace.exec runs in the container's initial mount namespace
  upstream: feat(sandbox): run workspace.exec in the daemon's mount namespace (ns-exec helper) Ephemeral-AI-Lab/layerfs#499
• [draft] Observability: count and expose unmount Join stalls #2 — [draft] Observability: count and expose unmount Join stalls
  upstream: feat(daemon): expose the unmount abort outcome in telemetry Ephemeral-AI-Lab/layerfs#501
• [upstream issue #502] macOS/OrbStack: sandbox.create fails with Connection refused after daemon LISTEN on LayerFS main (#500) #17 — [upstream issue macOS/OrbStack: sandbox.create fails with Connection refused after daemon LISTEN on LayerFS main (#500) Ephemeral-AI-Lab/layerfs#502] macOS/OrbStack: sandbox.create fails with Connection refused after daemon LISTEN on LayerFS main (fix(daemon): integrate stalled unmount recovery with exact abort custody (#496) Ephemeral-AI-Lab/layerfs#500)
  upstream: macOS/OrbStack: sandbox.create fails with Connection refused after daemon LISTEN on LayerFS main (#500) Ephemeral-AI-Lab/layerfs#502
• [upstream issue #508] Sandbox control calls hang behind Workspace storage scans; binding waits without bound #15 — [upstream issue Sandbox control calls hang behind Workspace storage scans; binding waits without bound Ephemeral-AI-Lab/layerfs#508] Sandbox control calls hang behind Workspace storage scans; binding waits without bound
  upstream: Sandbox control calls hang behind Workspace storage scans; binding waits without bound Ephemeral-AI-Lab/layerfs#508
• [upstream issue #512] Sandbox backends: which agent sandboxes can replace LayerFS's Docker container? Local stand-ins first #11 — [upstream issue Sandbox backends: which agent sandboxes can replace LayerFS's Docker container? Local stand-ins first Ephemeral-AI-Lab/layerfs#512] Sandbox backends: which agent sandboxes can replace LayerFS's Docker container? Local stand-ins first
  upstream: Sandbox backends: which agent sandboxes can replace LayerFS's Docker container? Local stand-ins first Ephemeral-AI-Lab/layerfs#512
• [upstream issue #516] Sandbox backends: twelve-cell speed comparison, Docker vs the no-Docker VM route (sub-issue of #512) #8 — [upstream issue Sandbox backends: twelve-cell speed comparison, Docker vs the no-Docker VM route (sub-issue of #512) Ephemeral-AI-Lab/layerfs#516] Sandbox backends: twelve-cell speed comparison, Docker vs the no-Docker VM route (sub-issue of Sandbox backends: which agent sandboxes can replace LayerFS's Docker container? Local stand-ins first Ephemeral-AI-Lab/layerfs#512)
  upstream: Sandbox backends: twelve-cell speed comparison, Docker vs the no-Docker VM route (sub-issue of #512) Ephemeral-AI-Lab/layerfs#516
• [upstream pr #515] docs(512): propose a VM Sandbox backend (Sandboxes as namespaces in one VM per Store) #47 — [upstream pr docs(512): propose a VM Sandbox backend (Sandboxes as namespaces in one VM per Store) Ephemeral-AI-Lab/layerfs#515] docs(512): propose a VM Sandbox backend (Sandboxes as namespaces in one VM per Store)
  upstream: docs(512): propose a VM Sandbox backend (Sandboxes as namespaces in one VM per Store) Ephemeral-AI-Lab/layerfs#515
• [upstream pr #498] feat(sandbox): 统一 Sandbox provider 接口，收编 Docker / Linux 原生 / macOS 原生（B1/B2/B3，叠在 #427 上） #52 — [upstream pr feat(sandbox): 用具体的 Runtime enum 统一 Docker / Linux 原生 / macOS 原生，并新增 Linux namespaces 后端（B1/B2/B3，按 #515，叠在 #427 上） Ephemeral-AI-Lab/layerfs#498] feat(sandbox): 统一 Sandbox provider 接口，收编 Docker / Linux 原生 / macOS 原生（B1/B2/B3，叠在 feat: macOS 原生适配——daemon 内置 loopback NFSv3 导出，普通用户 mount_nfs 挂载 Workspace（无 Docker / 无 macFUSE / 无 root） Ephemeral-AI-Lab/layerfs#427 上）
  upstream: feat(sandbox): 用具体的 Runtime enum 统一 Docker / Linux 原生 / macOS 原生，并新增 Linux namespaces 后端（B1/B2/B3，按 #515，叠在 #427 上） Ephemeral-AI-Lab/layerfs#498
• [upstream pr #427] feat: macOS 原生适配——daemon 内置 loopback NFSv3 导出，普通用户 mount_nfs 挂载 Workspace（无 Docker / 无 macFUSE / 无 root） #57 — [upstream pr feat: macOS 原生适配——daemon 内置 loopback NFSv3 导出，普通用户 mount_nfs 挂载 Workspace（无 Docker / 无 macFUSE / 无 root） Ephemeral-AI-Lab/layerfs#427] feat: macOS 原生适配——daemon 内置 loopback NFSv3 导出，普通用户 mount_nfs 挂载 Workspace（无 Docker / 无 macFUSE / 无 root）
  upstream: feat: macOS 原生适配——daemon 内置 loopback NFSv3 导出，普通用户 mount_nfs 挂载 Workspace（无 Docker / 无 macFUSE / 无 root） Ephemeral-AI-Lab/layerfs#427
• [upstream pr #452] Windows-native Store route: Store engine and SDK Store face on native Windows #56 — [upstream pr Windows-native Store route: Store engine and SDK Store face on native Windows Ephemeral-AI-Lab/layerfs#452] Windows-native Store route: Store engine and SDK Store face on native Windows
  upstream: Windows-native Store route: Store engine and SDK Store face on native Windows Ephemeral-AI-Lab/layerfs#452

Merge / Branch / correctness

• [upstream issue #517] merge: a changed span over the diff-table budget (~1023 lines) silently drops the other branch's change inside it — Merged, not Conflict #7 — [upstream issue merge: a changed span over the diff-table budget (~1023 lines) silently drops the other branch's change inside it — Merged, not Conflict Ephemeral-AI-Lab/layerfs#517] merge: a changed span over the diff-table budget (~1023 lines) silently drops the other branch's change inside it — Merged, not Conflict
  upstream: merge: a changed span over the diff-table budget (~1023 lines) silently drops the other branch's change inside it — Merged, not Conflict Ephemeral-AI-Lab/layerfs#517
• [upstream issue #487] Merge into an existing Branch, or a guarded head move to a merge result #18 — [upstream issue Merge into an existing Branch, or a guarded head move to a merge result Ephemeral-AI-Lab/layerfs#487] Merge into an existing Branch, or a guarded head move to a merge result
  upstream: Merge into an existing Branch, or a guarded head move to a merge result Ephemeral-AI-Lab/layerfs#487
• [upstream issue #462] workspace.unmount is refused "Dirty: 0 uncommitted change(s)" (empty changed) for a Workspace whose only changes are touched directories or removed files, while workspace.commit answers UpToDate #24 — [upstream issue workspace.unmount is refused "Dirty: 0 uncommitted change(s)" (empty changed) for a Workspace whose only changes are touched directories or removed files, while workspace.commit answers UpToDate Ephemeral-AI-Lab/layerfs#462] workspace.unmount is refused "Dirty: 0 uncommitted change(s)" (empty changed) for a Workspace whose only changes are touched directories or removed files, while workspace.commit answers UpToDate
  upstream: workspace.unmount is refused "Dirty: 0 uncommitted change(s)" (empty changed) for a Workspace whose only changes are touched directories or removed files, while workspace.commit answers UpToDate Ephemeral-AI-Lab/layerfs#462
• [upstream issue #379] A Commit refused for disk Capacity leaves its packs in the Store, and every later write is refused Capacity #42 — [upstream issue A Commit refused for disk Capacity leaves its packs in the Store, and every later write is refused Capacity Ephemeral-AI-Lab/layerfs#379] A Commit refused for disk Capacity leaves its packs in the Store, and every later write is refused Capacity
  upstream: A Commit refused for disk Capacity leaves its packs in the Store, and every later write is refused Capacity Ephemeral-AI-Lab/layerfs#379

SDK / API / CLI

• [upstream issue #417] JS SDK: no way to read a binary file back (fs.read refuses it as Binary) #37 — [upstream issue JS SDK: no way to read a binary file back (fs.read refuses it as Binary) Ephemeral-AI-Lab/layerfs#417] JS SDK: no way to read a binary file back (fs.read refuses it as Binary)
  upstream: JS SDK: no way to read a binary file back (fs.read refuses it as Binary) Ephemeral-AI-Lab/layerfs#417
• [upstream pr #492] feat(#417): read a file's raw bytes in bounded windows #54 — [upstream pr feat(#417): read a file's raw bytes in bounded windows Ephemeral-AI-Lab/layerfs#492] feat(JS SDK: no way to read a binary file back (fs.read refuses it as Binary) Ephemeral-AI-Lab/layerfs#417): read a file's raw bytes in bounded windows
  upstream: feat(#417): read a file's raw bytes in bounded windows Ephemeral-AI-Lab/layerfs#492
• [upstream issue #486] JS SDK: mtime and nlink in fs.stat, and mode, mtime and nlink in fs.list entries #19 — [upstream issue JS SDK: mtime and nlink in fs.stat, and mode, mtime and nlink in fs.list entries Ephemeral-AI-Lab/layerfs#486] JS SDK: mtime and nlink in fs.stat, and mode, mtime and nlink in fs.list entries
  upstream: JS SDK: mtime and nlink in fs.stat, and mode, mtime and nlink in fs.list entries Ephemeral-AI-Lab/layerfs#486
• [upstream pr #518] Report mtime and nlink from fs.stat, and mode, mtime and nlink from fs.list #46 — [upstream pr Report mtime and nlink from fs.stat, and mode, mtime and nlink from fs.list Ephemeral-AI-Lab/layerfs#518] Report mtime and nlink from fs.stat, and mode, mtime and nlink from fs.list
  upstream: Report mtime and nlink from fs.stat, and mode, mtime and nlink from fs.list Ephemeral-AI-Lab/layerfs#518
• [upstream issue #484] JS SDK: accept configuration as constructor options instead of only LAYERFS_* environment variables #21 — [upstream issue JS SDK: accept configuration as constructor options instead of only LAYERFS_* environment variables Ephemeral-AI-Lab/layerfs#484] JS SDK: accept configuration as constructor options instead of only LAYERFS_* environment variables
  upstream: JS SDK: accept configuration as constructor options instead of only LAYERFS_* environment variables Ephemeral-AI-Lab/layerfs#484
• [upstream issue #483] JS SDK: a streaming export of a Branch's tree at a Commit, with metadata #22 — [upstream issue JS SDK: a streaming export of a Branch's tree at a Commit, with metadata Ephemeral-AI-Lab/layerfs#483] JS SDK: a streaming export of a Branch's tree at a Commit, with metadata
  upstream: JS SDK: a streaming export of a Branch's tree at a Commit, with metadata Ephemeral-AI-Lab/layerfs#483
• [upstream issue #513] cli: layerfs init is structurally broken on the macOS worker route (MODULE_NOT_FOUND without env; "Store destination exists" with it) #10 — [upstream issue cli: layerfs init is structurally broken on the macOS worker route (MODULE_NOT_FOUND without env; "Store destination exists" with it) Ephemeral-AI-Lab/layerfs#513] cli: layerfs init is structurally broken on the macOS worker route (MODULE_NOT_FOUND without env; "Store destination exists" with it)
  upstream: cli: layerfs init is structurally broken on the macOS worker route (MODULE_NOT_FOUND without env; "Store destination exists" with it) Ephemeral-AI-Lab/layerfs#513
• [upstream issue #456] macos: agents need LAYERFS_STORE_PATH but the docs say it's linux only #28 — [upstream issue macos: agents need LAYERFS_STORE_PATH but the docs say it's linux only Ephemeral-AI-Lab/layerfs#456] macos: agents need LAYERFS_STORE_PATH but the docs say it's linux only
  upstream: macos: agents need LAYERFS_STORE_PATH but the docs say it's linux only Ephemeral-AI-Lab/layerfs#456

Agent / OS / Git

• [upstream issue #514] Question: a Git-centred repo on LayerFS — how should main track origin/main, and how should Branches reach Git? #9 — [upstream issue Question: a Git-centred repo on LayerFS — how should main track origin/main, and how should Branches reach Git? Ephemeral-AI-Lab/layerfs#514] Question: a Git-centred repo on LayerFS — how should main track origin/main, and how should Branches reach Git?
  upstream: Question: a Git-centred repo on LayerFS — how should main track origin/main, and how should Branches reach Git? Ephemeral-AI-Lab/layerfs#514
• [upstream issue #446] LayerFS 2.0 roadmap #31 — [upstream issue LayerFS 2.0 roadmap Ephemeral-AI-Lab/layerfs#446] LayerFS 2.0 roadmap
  upstream: LayerFS 2.0 roadmap Ephemeral-AI-Lab/layerfs#446
• [upstream issue #454] [提案] Windows 原生透明 Workspace：跨平台文件系统语义与挂载架构解耦 #29 — [upstream issue [提案] Windows 原生透明 Workspace：跨平台文件系统语义与挂载架构解耦 Ephemeral-AI-Lab/layerfs#454] [提案] Windows 原生透明 Workspace：跨平台文件系统语义与挂载架构解耦
  upstream: [提案] Windows 原生透明 Workspace：跨平台文件系统语义与挂载架构解耦 Ephemeral-AI-Lab/layerfs#454

Plugins / docs / process

• [upstream issue #450] OpenCode integration #30 — [upstream issue OpenCode integration Ephemeral-AI-Lab/layerfs#450] OpenCode integration
  upstream: OpenCode integration Ephemeral-AI-Lab/layerfs#450
• [upstream issue #482] ZCode Desktop integration #23 — [upstream issue ZCode Desktop integration Ephemeral-AI-Lab/layerfs#482] ZCode Desktop integration
  upstream: ZCode Desktop integration Ephemeral-AI-Lab/layerfs#482
• [upstream issue #406] dsh: support packaged desktop and out-of-tree plugin installation #39 — [upstream issue dsh: support packaged desktop and out-of-tree plugin installation Ephemeral-AI-Lab/layerfs#406] dsh: support packaged desktop and out-of-tree plugin installation
  upstream: dsh: support packaged desktop and out-of-tree plugin installation Ephemeral-AI-Lab/layerfs#406
• [upstream issue #392] 讨论：重建一套“平时安静、出现问题才报红”的 CI #40 — [upstream issue 讨论：重建一套“平时安静、出现问题才报红”的 CI Ephemeral-AI-Lab/layerfs#392] 讨论：重建一套“平时安静、出现问题才报红”的 CI
  upstream: 讨论：重建一套“平时安静、出现问题才报红”的 CI Ephemeral-AI-Lab/layerfs#392
• [upstream issue #365] Benchmark bundle: pjdfstest, fsx, fsstress, smallfile, mdtest, fio on the SDK route (v1.0.0) #43 — [upstream issue Benchmark bundle: pjdfstest, fsx, fsstress, smallfile, mdtest, fio on the SDK route (v1.0.0) Ephemeral-AI-Lab/layerfs#365] Benchmark bundle: pjdfstest, fsx, fsstress, smallfile, mdtest, fio on the SDK route (v1.0.0)
  upstream: Benchmark bundle: pjdfstest, fsx, fsstress, smallfile, mdtest, fio on the SDK route (v1.0.0) Ephemeral-AI-Lab/layerfs#365
• [upstream issue #362] Benchmark baseline: 39 Sandbox cost cases at issue359-impl 2d84fe1bb (2026-10-18) #44 — [upstream issue Benchmark baseline: 39 Sandbox cost cases at issue359-impl 2d84fe1bb (2026-10-18) Ephemeral-AI-Lab/layerfs#362] Benchmark baseline: 39 Sandbox cost cases at issue359-impl 2d84fe1 (2026-10-18)
  upstream: Benchmark baseline: 39 Sandbox cost cases at issue359-impl 2d84fe1bb (2026-10-18) Ephemeral-AI-Lab/layerfs#362
• [upstream issue #423] Sandbox containers keep scratch files written outside the Workspace #33 — [upstream issue Sandbox containers keep scratch files written outside the Workspace Ephemeral-AI-Lab/layerfs#423] Sandbox containers keep scratch files written outside the Workspace
  upstream: Sandbox containers keep scratch files written outside the Workspace Ephemeral-AI-Lab/layerfs#423
• [upstream issue #422] An abandoned Workspace keeps its Sandbox container running forever #34 — [upstream issue An abandoned Workspace keeps its Sandbox container running forever Ephemeral-AI-Lab/layerfs#422] An abandoned Workspace keeps its Sandbox container running forever
  upstream: An abandoned Workspace keeps its Sandbox container running forever Ephemeral-AI-Lab/layerfs#422
• [upstream issue #411] layerfs rm/compact: retire Branches and reclaim unreachable Store history #38 — [upstream issue layerfs rm/compact: retire Branches and reclaim unreachable Store history Ephemeral-AI-Lab/layerfs#411] layerfs rm/compact: retire Branches and reclaim unreachable Store history
  upstream: layerfs rm/compact: retire Branches and reclaim unreachable Store history Ephemeral-AI-Lab/layerfs#411

Other

• [upstream issue #461] RFC: LoopX × LayerFS demo and outcome/cost evaluation for multi-agent engineering exploration #25 — [upstream issue RFC: LoopX × LayerFS demo and outcome/cost evaluation for multi-agent engineering exploration Ephemeral-AI-Lab/layerfs#461] RFC: LoopX × LayerFS demo and outcome/cost evaluation for multi-agent engineering exploration
• [upstream issue #458] Question: is a client kill during workspace.exec meant to leave the orphan running and the mount Busy for ~90 s? If so, could the docs say so? #27 — [upstream issue Question: is a client kill during workspace.exec meant to leave the orphan running and the mount Busy for ~90 s? If so, could the docs say so? Ephemeral-AI-Lab/layerfs#458] Question: is a client kill during workspace.exec meant to leave the orphan running and the mount Busy for ~90 s? If so, could the docs say so?
• [upstream issue #425] Proposal: share the WSL2 Windows route with non-dsh adapters (we'd implement and maintain it) #32 — [upstream issue Proposal: share the WSL2 Windows route with non-dsh adapters (we'd implement and maintain it) Ephemeral-AI-Lab/layerfs#425] Proposal: share the WSL2 Windows route with non-dsh adapters (we'd implement and maintain it)
• [upstream issue #421] Sandwave: 为Layerfs专门设计的一套UI界面 #35 — [upstream issue Sandwave: 为Layerfs专门设计的一套UI界面 Ephemeral-AI-Lab/layerfs#421] Sandwave: 为Layerfs专门设计的一套UI界面
• [upstream issue #380] DSH Linux on WSL2 Docker Desktop: engine volume paths are not host-visible; configured volumes does not reach Store #41 — [upstream issue DSH Linux on WSL2 Docker Desktop: engine volume paths are not host-visible; configured volumes does not reach Store Ephemeral-AI-Lab/layerfs#380] DSH Linux on WSL2 Docker Desktop: engine volume paths are not host-visible; configured volumes does not reach Store
• [upstream pr #505] Area P batch 1: P2, P14, P1, P7, P8 and commit cost accounting fix #49 — [upstream pr Area P batch 1: P2, P14, P1, P7, P8 and commit cost accounting fix Ephemeral-AI-Lab/layerfs#505] Area P batch 1: P2, P14, P1, P7, P8 and commit cost accounting fix
• [upstream pr #504] Use VecDeque for Sandbox log tails #50 — [upstream pr Use VecDeque for Sandbox log tails Ephemeral-AI-Lab/layerfs#504] Use VecDeque for Sandbox log tails
• [upstream pr #503] fix(runtime): preserve peer worker temporary directories #51 — [upstream pr fix(runtime): preserve peer worker temporary directories Ephemeral-AI-Lab/layerfs#503] fix(runtime): preserve peer worker temporary directories
• [upstream pr #403] feat(macos): add native macOS support across Store, FUSE-T, Sandbox, SDK, and DSH #58 — [upstream pr feat(macos): add native macOS support across Store, FUSE-T, Sandbox, SDK, and DSH Ephemeral-AI-Lab/layerfs#403] feat(macos): add native macOS support across Store, FUSE-T, Sandbox, SDK, and DSH
• [upstream pr #382] LayerFS × Pi: Pi on a LayerFS Branch, on Linux and macOS (shared port/) #59 — [upstream pr LayerFS × Pi: Pi on a LayerFS Branch, on Linux and macOS (shared port/) Ephemeral-AI-Lab/layerfs#382] LayerFS × Pi: Pi on a LayerFS Branch, on Linux and macOS (shared port/)