v0.5.0 — memory relations + ready work + restructured web UI

Memory relations, a ready-work view, and a restructured web UI.

Relations & ready work

• related-to links between memories (mem.py link <id> <other>...) — a gotcha ↔ the decision that caused it, a status ↔ its todos. Shown both ways in the web UI as clickable chips.
• blocked-by on todos (mem.py block <todo> <blocker>...) + mem.py ready — lists todos with no open blocker (a blocker frees its dependents when superseded). Injection annotates blocked todos; the per-project page splits ready vs blocked.
• Linking is deliberate, never keyword-auto-guessed (that only produces noise).

Web UI, restructured

• index.php is now a dashboard (system status, stat cards, health, recent activity); the memories list moved to memories.php (filters, FTS, grouped table, bulk, AJAX CRUD).
• projects.php — every project at a glance (active count, open todos, current status), each card opening its per-project page.
• New Memories and Projects stat cards; the rest deep-link into the list with a filter.
• One shared top bar identical on every page (current section highlighted) + breadcrumbs everywhere.

Config

• MEM_UI_LANG (a local instance can default the UI to Romanian), a robust mem.py hint path (correct as a standalone repo or a monorepo subfolder), and an optional gitignored .mem-local.env for per-machine settings (MEM_PHP, etc.).

Both parsers (Python mem.py + PHP web UI) stay in lockstep — tests/conformance.py covers the new related-to / blocked-by fields.