Always analyze and understand configuration and testing patterns before making changes

Before modifying utility, configuration, workspace behavior, or responding to related review feedback, inspect the current implementation, schema, call sites, loading and validation paths, related tests, documentation, compatibility conventions, and relevant recent commits or review context. For configuration, verify file-based and string/remote loading, validation, inheritance/override semantics, security constraints, error messages, and backward compatibility, including slash-containing workspace paths. Distinguish actual legacy behavior from deliberately supported current contracts when intent is ambiguous. Preserve established error messages and semantics unless the requested change requires otherwise, then add focused regression coverage for required distinctions and edge cases.