Safe mutation
Edit
Use edit workflows for remote wiki page corrections, redactions, leakage cleanup, and multi-node repair after reading the current node revision.
Common commands
Use these as entry examples. Add --canister-id, --identity-mode, or workspace database config when the target environment requires it.
kinic-vfs-cli --database-id <database-id> read-node --path /Knowledge/page.md --json
kinic-vfs-cli --database-id <database-id> edit-node --path /Knowledge/page.md --old-text before --new-text after --expected-etag <etag> --json
kinic-vfs-cli --database-id <database-id> read-node --path /Knowledge/page.md --jsonSafety
- Use expected_etag for replacements.
- Do not add shim, fallback, or old-format rescue behavior.
- Stop and report conflicts when the node content no longer matches the planned edit.
Responsibilities
- Read the current node and etag before changing existing content.
- Keep edits scoped to the requested paths and preserve source-backed claims.
- Verify the stored node after mutation.