zeekayandHanzo Dev fef77e0d02 chore: remove the orphans the gs/abs/oss rip left behind ...

Second pass on 657c0c6. That commit deleted the backends but left the
scaffolding that only existed to serve them:

- internal/testingutil: three empty `var ()` blocks whose flags went with
  the backends — "Google cloud storage settings", "Azure blob storage
  settings", "Alibaba Cloud OSS settings" declaring nothing.
- replica_url_test.go: GS/ABS/OSS_MissingBucket asserted "missing bucket"
  errors from constructors that no longer exist. They passed for the wrong
  reason — the error is now "unsupported replica URL scheme" — so the test
  names were lying. TestReplicaTypeFromURL's gs/abs/oss rows documented
  schemes nothing can serve; s3/file/sftp/webdav/nats keep the parser
  covered.
- tests/integration/helpers.go: the abs:// arm of the config-path check
  can never be taken.
- docs: llms.txt and .claude/agents/replica-client-developer.md pointed at
  gs/replica_client.go and abs/replica_client.go, files that are gone;
  VFS.md, PROVIDER_COMPATIBILITY.md, ARCHITECTURE.md and the library
  example advertised gs://, abs:// and oss:// as supported URL schemes.
  webdav was live the whole time and missing from every list — added.
- `-integration gcs|abs|oss` recipes in PATTERNS.md, the skills guide and
  two .claude commands invoked flags with no backend behind them.

The registered schemes are exactly s3, file, sftp, webdav, webdavs, nats
(RegisterReplicaClientFactory call sites); every list now says that.

go build ./... and go vet ./... green; URL tests pass. go.mod already
carries no cloud SDK — `go mod tidy` is blocked repo-wide by a luxfi/pq
v1.0.3 moved-tag checksum, unrelated to this change, so go.mod is
untouched.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-27 14:45:04 -07:00

..

library

chore: remove the orphans the gs/abs/oss rip left behind

2026-07-27 14:45:04 -07:00