Expand description
memstead update — strict-by-default entity update.
Hash handling offers three opt-ins:
- Default (strict).
--expected-hash <h>must be supplied for any update that CHANGES CONTENT. Matches MCP’smemstead_updatecontract. Safe for scripts, CI, pre-commit hooks. An anchors-only update (--anchor/--anchor-unsetand nothing else) needs none: anchors live outside the content hash, so the token would compare a value the write cannot move. --auto-hash. Refetch the current hash immediately before writing. Ergonomic for one-off interactive edits; the user accepts the race window.--force. Skip the hash check entirely. Explicit opt-out.
Only one of the three may be used per invocation.