Filesystem content-cache tests
Section titled “Filesystem content-cache tests”Inno.Adapter.Content.FileSystem.Tests checks the physical cache behind deployment content reads. It exercises real files and processes while preserving the content service’s independently retained readers.
Publication and integrity
Section titled “Publication and integrity”Concurrent preparation publishes one complete generation. Prior cancellation creates no cache directory; cancellation during copy discards the candidate and preserves the previous pointer. Source failure removes incomplete staging without replacing the last published content.
Complete validation repairs corrupt caches. A content change after preparation fails the read and releases its failed stream pin. A valid hit preserves the generation and avoids rereading source payloads.
Readers, waiting and retirement
Section titled “Readers, waiting and retirement”Independent processes publish one generation and pin it until both readers retire. Repair retains an older generation until its last stream closes. A writer lease bounds waiting and supports cancellation without mutating protected content.
Unknown ownership of an old generation is reported after the new content commits; it is not permission to delete the unknown owner or pretend the committed publication rolled back.
Run and maintain
Section titled “Run and maintain”Use the validation plan. A focused filesystem diagnostic is:
dotnet test backends/FileSystem/tests/Inno.Adapter.Content.FileSystem.Tests/Inno.Adapter.Content.FileSystem.Tests.csproj --configuration Debug --disable-build-servers -m:1 -nodeReuse:falseThe contract suite requires actual filesystem and child-process facilities. Fixtures own their temporary roots and release stream pins before cleanup. A cache pass is not platform packaging or device execution evidence.