workspace git still routes local checkouts through stale remote state

[chubes4]

Summary

After Extra-Chill/data-machine-code#719 fixed local fallback for workspace read/list/grep operations, workspace git still appears to prefer stale remote workspace state for a local checkout and fails before using the local workspace registry.

Reproduction

On the local Intelligence Studio site with Data Machine Code 0.47.126 active:

studio wp datamachine-code workspace show data-machine

resolves the local checkout correctly:

Name:     data-machine
Path:     /Users/chubes/Developer/data-machine
Branch:   HEAD
Remote:   https://github.com/Extra-Chill/data-machine.git
Latest:   66f56c05 Require bundled Agents API runtime (#2599)
Freshness: detached
Dirty:    no

But:

studio wp datamachine-code workspace git status data-machine

fails with:

Error: Remote workspace repository "data-machine" is not registered. Call workspace_clone first.

Expected behavior

For a repo that exists in the local workspace registry, workspace git status data-machine should use the local checkout or fall back locally when the remote backend reports repo not registered, matching the behavior fixed for read/list/grep in #719.

Why this matters

This blocks the intended safe local workflow after installing DMC 0.47.126: update /Users/chubes/Developer/data-machine through the DMC wrapper rather than bypassing with raw git.

AI assistance

• AI assistance: Yes
• Tool(s): OpenCode (GPT-5.5)
• Used for: Reproducing the routing failure and drafting this issue with command evidence.