The account handle changed from notplants.bsky.social to notplants.net and every https://tangled.org/notplants.bsky.social/* URL stopped resolving. This crate's own dependencies still pointed at the old handle, so `cargo build` failed for anyone without a warm ~/.cargo/git cache: a fresh clone, a fresh container, or CI. Cargo.toml:13-14 atproto-identity, atproto-oauth Cargo.lock:117,136,168 atproto-dasl, atproto-identity, atproto-oauth THREE lock entries, not two. atproto-dasl is transitive: it appears in the lock and in neither manifest line, so a manifest-driven sweep misses it. The lock must change too -- an ordinary build re-resolves given network access, but every --locked build fails, and a fix that passes today and fails later is worse than failing now. HOST SUBSTITUTION ONLY. 14b07d9ba9ad4431257b169ed7d22a595962b814 was fetched BY SHA from the new handle into an empty bare repository and is present, so every pin keeps its sha and only the host changes. Nothing is re-resolved and no version moves. Both URLs were checked from one machine at one moment: the bsky.social URL fails, the notplants.net URL resolves. The DID form (tangled.org/did:plc:3nogfd4smhmbrv4wo6kl7zg2/lichen-atproto-crates) also resolves and is immune to future handle changes; that is the operator's call at release time and the fix is the same shape either way. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UE7RGDcciKwciLSmTDZkcz