Skip to content

Latest commit

 

History

History
43 lines (32 loc) · 2.07 KB

README.md

File metadata and controls

43 lines (32 loc) · 2.07 KB

Files and artifacts plugin

@rho-workspace/plugin-files 0.4.0 is an independently packed npm plugin.

Public entries: Files, fileLimits, collectArtifacts, verifyArtifacts.

Scoped byte snapshots, digests, declared resource storage, bounded reads, completion inventory verification and restore.

The pure ./contract entry exports this owner's JSON schema without importing its implementation or native/parser dependencies.

Selected services: None. Type validators are supplied explicitly by selected providers.

No CSV parsing, chart calculation, media decoding or object preview.

The package depends on @rho-workspace/plugin-contracts 0.4.0 for generic envelopes and service ports and ordinary file primitives; that package contains no capability implementation. Service ports do not install or start other plugins. Rho explicitly selects and connects providers. plugin describes this package and its selected-service requirements. View descriptors, where present, remain UI-unavailable; action/view contract versions remain 0.2.0 independently of the package version.

# From the Rho-plugins source checkout
npm ci
npm run build
npm pack --workspace plugins/files --ignore-scripts

Use the repository's pack:plugins command to produce the contracts tarball and selected plugin tarballs together. Both explicit R examples are separate consumers and are excluded from every plugin artifact. No UI work is included.

Selected source folders

Files 0.4.1 exports ProjectPaths(root, sources) as an optional, finite file-path port. The application supplies already authorized {id, root, name} folders; references use @<id>/<relative-path>. Resolution rechecks the canonical folder, containment, symlinks and internal source state. Overlapping aliases normalize to one reference. The fifth Files constructor argument accepts this port; without it, the existing single-root behavior remains. sourceFile exposes the same resolver to selected consumers such as saved-script planning. Source bytes stay in place; immutable snapshots and metadata remain in the owner state under root.