#34778 [Bug]: git-subdir path validation rejects dot-prefixed segments (e.g. .claude/skills/...)
### Check for existing issues
- [x] I have searched the existing issues and checked that my issue is not a duplicate.
### What happened?
`POST /claude-code/plugins` returns 400 when the git-subdir path starts with a dot:
``` { "detail": { "error": "git-subdir 'path' must be a relative path of the form 'segment/segment' (alphanumeric, dots, hyphens, underscores only)" } } ```
The error message lists dots as valid characters, but the actual regex (_VALID_GIT_SUBDIR_PATH_RE) requires each segment to start with [a-zA-Z0-9], so a leading dot is never accepted.
**What I expected to happen** Dot-prefixed segments are accepted. Directories like .claude/ are conventional (same as .git/, .github/) and a reasonable caller expects them to work given the advertised character set.
### Steps to Reproduce
1. Run LiteLLM proxy v1.91.0 2. POST /claude-code/plugins with a git-subdir source whose path starts with a dot: ``` { "name": "my-skill", "source_type": "git-subdir", "url": "https://github.com/org/repo.git", "path": ".claude/skills/my-skill" } ``` 3. Receive 400: "git-subdir 'path' must be a relative path of the form 'segment/segment'"
### Relevant log output
```shel…