## Summary Fix `snapcraft init` when the current directory name is longer than the snap name limit. When the project name is derived automatically from the directory, Snapcraft now: - truncates it to the maximum snap name length - removes a trailing hyphen after truncation - validates the normalized name before project initialization Explicit names passed with `--name` keep the existing strict validation behaviour. Closes #6093. ## Why Today, `snapcraft init` fails if the current working directory name is longer than 40 characters, even though other Craft tools initialize successfully in equivalent cases. This change keeps the special handling limited to directory-derived names and avoids changing the contract for explicit `--name` values. ## Implementation - add `MAX_SNAP_NAME_LENGTH` - add `_normalize_snap_name()` for directory-derived names - add `_validate_snap_name()` to centralize snap-specific validation, including the 40-character limit - override `validate_project_name(..., use_default=True)` so only directory-derived names are normalized - keep `initialise_project()` strict for explicit project names - preserve exception chaining for the reserved `snap/` directory path error ## Tests Added or updated tests to cover: - explicit invalid names still failing in the init service - normalization helper behaviour: - truncation - trailing hyphen removal - `snapcraft init` succeeding when the current directory name is too long - `snapcraft init --name <long-name>` still failing and not creating `snap/snapcraft.yaml` Also updated the fake provider test double to implement `list_instances()` with the current provider interface so the unit tests remain compatible.