Always update tests for workspace behavior changes

When changing workspace parsing, resolution, configuration, discovery, CLI output, or publish workflows, inspect the existing resolution flow and add focused regression tests with the implementation. Cover exact values and errors for absent configuration, invalid external output, legacy-compatible names, empty lists, listing and active-workspace selection, valid/unknown/invalid/ambiguous/overlapping glob inputs, version gates, and concrete paths resolved relative to the config file. Test traversal/prototype-key rejection where relevant. Mock dependencies explicitly, restore mocks after each test, preserve unrelated working-tree changes, place tests in corresponding existing test files, and run focused Craft tests after each change.