Skip to content

Bug: workspace hash changed from MD5 to SHA256 between versions, silently breaking @memory for existing users #128

@tcconnally

Description

@tcconnally

Users upgrading from older Perseus versions (pre-v1.0.3) will find @memory silently returning 'No Mnēmē narrative found' because the workspace hash algorithm changed from MD5 to SHA256. Existing narrative files are stored under the MD5-based filename (e.g. faafba882994.md) but Perseus now expects SHA256 (e.g. a7b1f892fc76.md).

Steps to reproduce:

  1. Have a Perseus install with a narrative created under an older version
  2. Upgrade to v1.0.3+
  3. Run perseus memory show → 'No Mnēmē narrative found'
  4. Run @memory in a render → same error

Expected

Migration guide or automatic detection/migration of old hash-named files

Actual

Silent failure with unhelpful error message

Workaround

Manually compute SHA256 hash of workspace path and copy the narrative file to the new name, update frontmatter workspace_hash field.

Suggested fix

On startup/memory commands, check for MD5-named files and either auto-migrate or emit a specific 'legacy narrative found, run perseus memory migrate' message.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions