`git config get --type=path` results in segmentation fault on value starting with `:(optional)`

What did you do before the bug happened? (Steps to reproduce your issue) git -c 'section.key-path=/nonexistent' config get --show-origin --show-scope --all --type=path 'section.key-path' git -c 'section.key-path=:(optional)/nonexistent' config get --show-origin --show-scope --all --type=path 'section.key-path'

What did you expect to happen? (Expected behavior)

1st command outputs "command command line: C:/Program Files/Git/nonexistent"; 2nd command outputs nothing, $?=1;

What happened instead? (Actual behavior)

1st command outputs "command command line: C:/Program Files/Git/nonexistent"; 2nd command outputs "Segmentation fault", $?=139;

What's different between what you expected and what actually happened?

Anything else you want to add:

Please review the rest of the bug report below. You can delete any lines you don't wish to share.

[System Info]
git version:
git version 2.52.0.windows.1
cpu: x86_64
built from commit: 2912d8e9b8253723974b7baf1c890273b1a1c5bd
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
rust: disabled
feature: fsmonitor--daemon
libcurl: 8.17.0
OpenSSL: OpenSSL 3.5.4 30 Sep 2025
zlib: 1.3.1
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1
uname: Windows 10.0 26200
compiler info: gnuc: 15.2
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe

[Enabled Hooks] not run from a git repository - no hooks to show