Repository navigation
Support reusable flat UnixFS inputs and incremental node capabilities - #75
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Flat repository imports need lossless path bindings while each directory manifest retains only immediate child names and types. This adds runtime-owned flat labels (including real
@payloadnames), reusable chunked file serialization with authenticated file mode, and narrow in-process Node API build/apply/snapshot capabilities. Readers distinguish literal paths from internal payload projections; interactive staging keeps its canonical path policy.Validation: full
GOWORK=offtests, vet and build passed. A new facade regression reproduced reserved-name read failures before the fix and now passes. A fresh independent review reported no actionable findings. No replay workload or accounting policy is added to the runtime.Companion Core capability: DeWebProtocol/malt-core#224. Gateway persistence and evaluator adoption follow separately.