Thank you for being patient! We're working hard on resolving the issue
tento-app-bundle defines and validates deployment bundle layouts. It lets a
bundle author describe required files and folders once, then build or validate
that hierarchy through generated typed builders.
bundle! declares a typed bundle schema.BundleBuilder, BundleEntry, and EntryKind build output directories.ContentSource describes whether an entry is copied, symlinked, generated,
or empty.FileNode, FolderNode, and FileType represent validated bundle nodes.Validator plus validate_* and load_* functions implement schema checks.ValidationError and BuildError are the error types callers should surface.The crate owns filesystem shape and validation only. It does not decide what an
app bundle means operationally, how a server is deployed, or which files should
be generated. Deployment orchestration belongs in callers such as scripts or
tento-deploy.
Use the macro for stable bundle contracts. Prefer adding schema entries over letting callers manually copy paths with ad hoc shell logic.