Der RegistryClient ist das Rückgrat des Mod-Systems. Wenn ein User tb -c CloudM ModManager install mymod ausführt, ist der RegistryClient derjenige, der:
1. Den Registry-Server kontaktiert
2. Paket-Metadaten validiert
3. Den Download durchführt
4. Die Integrität verifiziert (SHA-256 Checksum)
5. Das Paket entpackt und installiert
sequenceDiagram
participant U as User (tb CLI)
participant MM as ModManager
participant RC as RegistryClient
participant R as Registry Server
participant FS as Local Filesystem
U→>MM: install "mymod"
MM→>RC: get_package_info("mymod")
RC→>R: GET /api/package/mymod
R-->>RC: PackageDetail (versions, checksum)
RC→>R: GET /download/mymod/1.2.3
R-->>RC: .tbz2 archive
RC→>RC: verify_checksum(SHA-256)
RC→>FS: extract to toolboxv2/mods/mymod/
RC-->>MM: Success + install_path
MM-->>U: "mymod 1.2.3 installed"
Checksum mismatch: If download is corrupted, DownloadError is raised. Registry caches are versioned — clearing local cache (~/.local/share/ToolBoxV2/.cache/registry/) fixes stale-state issues.
Auth token expiry: Tokens expire. Re-login or use set_auth_token with a fresh token.
Circular dependencies: get_dependencies detects cycles and raises RegistryError.