Module operations keep subprojects consistent with files on disk

[sdercolin]

Follow-up to #114, based on testing feedback: renaming a subproject did not rename the corresponding folder/files, leaving the project inconsistent with the disk.

Principle

Module management operations must keep subprojects consistent with the files/directories on disk, in the same way the project constructor builds them — import (name-based module matching), export, and label reloading all depend on that correspondence. Operations that change files on disk are dangerous and get a double confirmation.

Core changes

• File.moveTo(target) added to the scripting File API (creates parent dirs, throws if target exists) + docs/file-api.md. Available to plugins too.
• ModuleOperation.confirmation (localized message): when declared, the app shows a common confirmation dialog after the parameter dialog and before running the scripts (the "double confirm").
• ModuleOperation.irreversible (boolean): when true, the undo history is cleared after the operation is applied, because undoing the project to a state inconsistent with renamed/deleted files is not safe (per discussion). Kept separate from confirmation so a labeler can define a confirmed-but-undoable operation (e.g. removing a TextGrid tier, which only affects the file on export). A failed or cancelled operation leaves both project and history untouched. No serialVersion bump — v3 is unreleased.
• Auto-reload label watching follows automatically: the watcher re-registers on current-module change and resolves rawFilePath fresh, so it tracks the moved raw label file.

Bundled labelers (rename/remove are now confirmed + irreversible)

• utau-singer (v27): rename moves the subproject folder (updates sampleDirectory/rawFilePath); remove deletes the folder recursively. Both are blocked for the root subproject (its folder is the root sample directory) and for folders that contain other subprojects' folders (per discussion: error-and-block rather than cascade). Rename/add now sort the module list by name, matching constructor ordering.
• nnsvs (v15) / diffsinger (v4): rename moves the wav and lab files and updates every entry's sample reference; remove deletes the wav and lab files. Both validate that target file names are free on disk before touching anything.

All scripts validate fully before performing any disk operation, so a rejected operation never leaves partial changes.

Docs & tests

• labeler-development.md: confirmation/irreversible fields, the disk-consistency principle, and the undo-history behavior.
• Tests run the real scripts and assert the disk state: file/folder moves and deletions, stray-target and duplicate-name rejections, nested-subproject and root-subproject blocking (UTAU), and the undo-history behavior of irreversible vs reversible vs failed operations (AppStateModuleOperationTest).

A follow-up PR in vlabeler-textgrid will add a confirmation (not irreversible) to its remove operation and forbid changing the wav prefix on rename.

🤖 Generated with Claude Code