feat(paths): support the XDG Base Directory specification via the ?state path token

[line0]

Companion to arch1t3cht/Aegisub#160, which adds a ?state path token and moves Aegisub's own logs, autosaves and recovered files there. This points DependencyControl's paths at the matching XDG locations, while degrading cleanly on every Aegisub that predates the token.

Where files go

setting	before	after	rationale
paths.log	?user/log	?state/log	follows Aegisub's own logs
paths.cache	?user/cache	?local/cache	XDG cache home
paths.config	?user/config	unchanged	already XDG config home

Installed scripts stay under ?user/automation/…, since the PR leaves Path/Automation/* pointing there.

Only Windows and XDG-mode Linux see a real relocation — elsewhere ?state and ?local resolve to the same directory as ?user.

Backwards compatibility

An Aegisub without ?state returns the token verbatim from decode_path, which would leave a literal ?state/log directory next to the working directory. PathOps probes each token once and substitutes a fallback (?state → ?user) when the running build can't resolve it, so a path setting naming ?state works on every version and no config migration is needed.

Files an earlier release left in the old locations are swept on startup. Identification is by content, not location: log files matching the name Logger gives DepCtrl's own, and cache entries in a directory holding an index that decodes. Aegisub's own logs shared the old log directory and are untouched, as is any file the sweep can't identify. Directories are only removed when the sweep emptied them, and the sweep is self-extinguishing — one directory probe once the location is gone.

Along the way

• New DependencyControl.PathOps — path composition, validation and token resolution, with no filesystem access. joinPath, pathSegments, getTempDir, validateFullPath and the path constants moved out of FileOps, which keeps deprecated re-exports. The split was forced by the dependency graph: FileOps requires Logger, so nothing at or below Logger could reach its path helpers — which is why Logger was hand-building log paths with a raw /.
• getNamespacedPath moved to Domain, joining getAutomationDir and getTestDir as the third namespace-to-path mapping.
• validateFullPath → PathOps.resolveFullPath, now returning the absolute directory instead of a device plus a fragment relative to it. The old dir was unusable alone on both platforms, which is why its only consumer concatenated the pair straight back together.

Breaking

FileOps.getAttributes drops dev from its info table and its dir is now absolute. The type shipped in 0.7.0 nine days ago and nothing outside FileOps read it. FileOps.validateFullPath keeps its old four-value shape, deprecated.

Both packages bump to 0.9.0.

Testing

Full suite green (4 packages). New coverage: 8 tests for token fallback, 5 for cache-artifact recognition, 6 for the legacy sweep, plus assertions pinning the legacy shape the deprecated shim still has to produce. Feed validates against schema v0.4.0; types and docs generate with 0 warnings.

Deferred

UNC paths are rejected by resolveFullPath — ^[A-Za-z]:[/\] never matches \server\share, and the separator-collapsing gsub mangles the leading \ first. Internal-only fix, no API impact, so it's left for its own PR; worth deciding there whether feed-supplied install paths should be allowed to be UNC.

🤖 Generated with Claude Code

[github-actions]

Test results — macos-latest ✅1084 · ubuntu-latest ✅1084 · windows-latest ✅1081

Summary

Tests 📝	Passed ✅	Failed ❌	Skipped ⏭️	Other ❓	Flaky 🍂	Duration ⏱️
3252	3249	0	3	0	0	1m 8s

_{🎉 No failed tests in this run.}

Github Test Reporter by CTRF 💚

🔄 This comment has been updated