v0.3.0

0.3.0 (2026-07-05)

⚠ BREAKING CHANGES

• piyaz_project/task/edge/query/context/analyze are removed; the MCP surface is now piyaz_workspace/search/get/create/edit/link/map/activity. Once this deploys to prod, plugins still on 0.2.x call the removed tools and their skills carry stale prompts against the old surface. Users must update their plugin to 0.3.0.
• the 0002 migration drops the legacy history JSONB columns from tasks and projects, which the activity-log backfill reads. Self-hosters must run scripts/backfill-activity-events.sql (as service_role) while on v0.2.0, before upgrading to v0.3.0 and running bun run db:migrate. The backfill script ships only in v0.2.0 and is removed in v0.3.0, so it cannot be run after upgrading; instances already backfilled on v0.2.0 need no extra step.

Features

• Add email sender resolver and capability detection (#166) (a16f912)
• build Notes data layer (#172) (8fa6c8d)
• Create Notes DB schema, indexes, and RLS migration (#169) (ec14217)
• Define EmailSender interface and email message types (#152) (bcec3ef)
• Implement LogSender dev email transport (#164) (c930a4f)
• redesign mcp surface as 8 ref-first tools (#170) (576d2bd)
• wire notes workspace view (#173) (25effee)

Bug Fixes

• require double-click to edit inline fields (#165) (699dc58)

Documentation

• rewrite README (#171) (90c4a7f)

Code Refactoring

• drop legacy history JSONB columns (#168) (ed8de04)

v0.2.0

0.2.0 (2026-06-28)

Features

• attributed activity log for tasks and projects (#133) (1553505)

Bug Fixes

• harden composer behaviour in sub-stages (#156) (41a1f5e)
• let migrator create cross-schema fks to piyaz_auth (#162) (628fb2c)