v0.3.1
Fixed
workspace_rootresolution no longer silently falls back to the filesystem root,$HOME, or an unrelated directory when an MCP client doesn't report roots (or the server process has an unrelated cwd). Auto-detected roots must now contain a.gitor.dmxmarker, or resolution fails loudly instead of guessing — previously this could cause loop state files to be written outside the intended project, with job folder names sometimes wrong or incomplete (e.g.maininstead of the actual ticket/branch).setup_ide_rules(the/dmx-initbootstrap call) still succeeds on brand-new, marker-less projects — the marker check above is skipped for this pre-.git/.dmxcall specifically.- Explicit
workspace_rootarguments must now be an absolute path (~is expanded); relative values are rejected instead of being silently resolved against the server process's cwd.
Full Changelog: v0.3.0...v0.3.1