v0.3.4

v0.3.4: Wider Private-Directory Guidance

A small maintenance release that extends an existing safety diagnostic to more memory-related directories and documents speaker-selection behavior that was already shipping.

Fixed

• Owner-owned Unix directories with unsafe group/other permissions now get the same exact-path "restrict to mode 0700" guidance across all memory-owned locations, not just the primary data directory. This includes the managed Dolt cache and version directories, cold-probe and installation destinations, and private server (lifecycle) directories. As before, Kuru never changes permissions automatically, and links or foreign-owned paths still receive no such guidance (@replygirl, #29).
• Test-only fix: two MCP malformed-peer regression tests could flake because cleanup could reap the peer before a fixture completion marker was written. The tests now wait deterministically and verify the full initialize transcript; no production behavior changed (@replygirl, #30).

Documentation

• The frameworks and architecture docs now describe the existing "who speaks" tie-break rules in full: explicit targeting and active focus take precedence, then highest activation, then continuity of the previous speaker, and only a remaining tie falls back to each framework's authored part order (Self, Connection, Desire, or Continuity first). These fallbacks are recorded as mode-authored-order or stable-id-order in the selection event and grant no supervisory authority to the chosen part (@replygirl, #29).
• Memory documentation now consistently refers to "memory-owned directories" to reflect the broadened scope of the private-directory check.

This release has no breaking changes.