Feature request: support SSH shorthand for private repos (e.g. owner/repo/path)

[sergioazos]

Problem

When installing packages from private repositories, the shorthand syntax fails even when SSH is properly configured:

# ❌ fails for private repos — APM tries HTTPS even with SSH configured
apm install Azos-Seguros/my-private-repo/skills/my-skill

# Error: not accessible or doesn't exist

The only workaround today is to use the verbose object format in apm.yml:

dependencies:
  apm:
  - git: git@github.com:Azos-Seguros/my-private-repo.git
    path: skills/my-skill

This works, but it's a much worse developer experience compared to the simple shorthand.

Expected behavior

APM should detect that the user has SSH configured for GitHub (via ~/.ssh/config or ssh-agent) and fall back to SSH when HTTPS authentication fails for the shorthand format:

# ✅ should work when SSH is configured
apm install Azos-Seguros/my-private-repo/skills/my-skill

Alternatively, a flag could help:

apm install Azos-Seguros/my-private-repo/skills/my-skill --ssh

Why it matters

Many teams and organizations use SSH exclusively for GitHub authentication (no PAT tokens). Requiring the object format in apm.yml for every private package defeats the simplicity that makes APM compelling — especially when onboarding teams that already have SSH set up.

Environment

• APM version: 0.8.0
• OS: macOS
• Auth: SSH via keyring (git operations protocol: ssh), no GITHUB_CLI_PAT / GITHUB_TOKEN set
• ssh -T git@github.com authenticates successfully

[sergio-sisternes-epam]

Triage: accepted

This is a valid DX gap -- the shorthand syntax (owner/repo/path) should work for SSH-authenticated users without requiring the verbose git: object format.

Clarification on related work: PR #665 (fixing #661) preserves ssh:// URLs with custom ports for Bitbucket Datacenter, but it addresses a different problem -- it fixes explicit ssh:// URLs that were being silently converted to HTTPS. This issue (#328) is about making the shorthand syntax (owner/repo/path) fall back to SSH when HTTPS auth fails, or supporting a --ssh flag. That gap remains open.

[danielmeppiel]

Cross-link: this request is subsumed by #778 ("Transport Selection v1"), which will let shorthand owner/repo try SSH when configured (git config insteadOf rewrite, APM_GIT_PROTOCOL=ssh env, or --ssh flag) without requiring the verbose git: object form. The verbose workaround documented here remains valid until #778 ships.