31aec05f99
Derive validated same-run visit artifact capabilities in the runner and pass them to OpenCode and Pi clients. Permit supported file tools to read completed prior visits and write only the current visit, preserving workspace, secret, database, and shell restrictions.\n\nChecked packaged templates and authoring skill references: neither needs updating in this item; docs/notes/scoped-artifact-access.md records the shared documentation staleness for the docs-fold writer.
954 B
954 B
Scoped stage artifact access
What this item changed
The server now derives one exact artifact capability for an OpenCode or Pi model-stage visit: its own directory is writable when the edit tool is present, and its own plus completed earlier visit directories in the same run are readable when a file-reading tool is present. No artifact root, sibling, future visit, other run, traversal path, or symlink escape is granted. The scope is empty if the runner cannot validate its artifact root.
Pi retains its lease and explicit extension policy; unrestricted shell remains outside this file-tool boundary and is not an OS sandbox.
Shared documents this change makes stale
docs/stage-artifacts.mdandinternal/author/skill/references/operations.mdshould explain that model-stage artifact directories are usable by the supported file tools only within the exact same-run visit scope, not as a general external-directory permission.