v0.30.0

What's New in v0.30.0

Features

• Project-scoped orchestration — each Project can now have its own durable Project Orchestrator for focused coordination, while the Portfolio Orchestrator continues to oversee unassigned work and can explicitly elevate into a Project when cross-project visibility is needed. Project Orchestrators are created automatically after the first completed Project thread or directly from Settings. (#474)
• Independent coordination routing — wakeups, schedules, notes, and proposed replies stay with their owning Project or Portfolio coordination bucket, reducing unrelated context and preventing cross-project coordination mistakes. (#474)
• Clear Project and Portfolio identity — Settings, Agent Dashboard, Kanban, and thread badges now distinguish Project Orchestrators from the Portfolio Orchestrator. (#474)

Improvements

• Project deletion now preserves ordinary threads, pins affected schedules to the former effective working directory, and safely removes Project-owned coordination state.
• Orchestrator retirement and archive persistence are rollback-safe, and startup repair cleans stale references and orphaned heartbeats.
• Coordination tools enforce Project ownership and provenance for manager notes and proposed replies.
• The public guide now documents creation, coordination boundaries, schedules, deletion behavior, and updated agent tools. (docs #55)

Notes

• Projects are an operational coordination boundary, not a vault, filesystem, tool, MCP-server, skill, or secret security boundary.
• Existing unassigned threads continue to be coordinated by the Portfolio Orchestrator.
• No migration steps or breaking configuration changes are required.
• Minimum supported Obsidian version remains 1.0.0.