Both onboarding failures we have actually seen happen before any git concept
would help: a partner cloned into ~/my-private-bucket, and a partner used the
SSH clone URL. The bucket mounts are mountpoint-s3, which implements no
rename(2) and no symlinks -- verified on the hub, `mv` returns "Function not
implemented" -- so git cannot operate there at all. That is a property of the
location, not a mistake, and the doc says so with the error text they saw.
The SSH failure is framed as "wrong address, not no access", which is the
misreading that sends people looking for permissions they already have.

Scope is deliberately three commands (clone, pull, stash) with commit/push
called out as things they will never need -- the repo is public and read-only
to them, so an attempt just produces a confusing credential prompt.

The issue section optimises for the maintainer's inbox: what to include, paste
text not screenshots, a snippet printing commit SHA + authorized buckets, and a
filter for the two non-bugs (AccessDenied, Tier 3) most likely to be filed.

README: clone command with the location warning inline at Quick start step 3,
since that is where the mistake happens; Getting help links out and repeats the
filter; repo layout lists both getting-started docs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>