Should 'git replace' respect GIT_NAMESPACE?

I was hoping it would, so I could have different replacements in different namespaces, but it doesn't look like it does as of ~now:

$ git version git version 2.47.1

$ GIT_NAMESPACE=foo git replace 751eeb3b4d23c7fbde919aedde8c091f04f4f819 a9dfd084086ee4d6bf00a33b0976f28c0997457e

$ git rev-parse refs/replace/751eeb3b4d23c7fbde919aedde8c091f04f4f819 a9dfd084086ee4d6bf00a33b0976f28c0997457e

$ git rev-parse refs/namespaces/foo/refs/replace/751eeb3b4d23c7fbde919aedde8c091f04f4f819 refs/namespaces/foo/refs/replace/751eeb3b4d23c7fbde919aedde8c091f04f4f819 fatal: ambiguous argument 'refs/namespaces/foo/refs/replace/751eeb3b4d23c7fbde919aedde8c091f04f4f819': unknown revision or path not in the working tree.

$ git log -n 1 --oneline 751eeb3b4d23c7fbde919aedde8c091f04f4f819 751eeb3 (replaced) add go.mod

$ GIT_NAMESPACE=foo git log -n 1 --oneline 751eeb3b4d23c7fbde919aedde8c091f04f4f819 751eeb3 (replaced) add go.mod

Is this a bug in which case I might hope for a fix, or is it working as intended?

-josh