fix(codegen): Two remaining gaps blocking a clean regeneration

[sugyan]

Summary

Follow-up to #342. That PR got lexgen parsing the current lexicons, but regenerating atrium-api against them still doesn't come out CI-clean. Two codegen gaps remain — both are pre-existing bugs newly triggered by lexicons that landed upstream, and both must be fixed before a regeneration can go green.

Changes

Skip empty descriptions. app.bsky.ageassurance.defs carries "description": "", which generated a bare /// and tripped clippy::empty_docs. CI runs with RUSTFLAGS: "-D warnings", so this alone fails the build. Empty descriptions are now treated the same as missing ones, for both the per-item #[doc] and the schema-level #![doc].

Generate Collection impls for camelCase record NSIDs. generate_modules rebuilt the NSID from the snake_case'd file stem, so a record whose NSID leaf is camelCase never matched its own schema and got no Collection impl. Every record so far had a single-word leaf (profile, status, listitem, …), so this went unnoticed until app.bsky.actor.contentVisibilityDeclaration.

This one is not cosmetic: KnownRecord is built from schema ids and does gain the variant, so bsky-sdk's create_record match gets an arm it cannot satisfy — atrium_api::app::bsky::actor::ContentVisibilityDeclaration simply doesn't exist. The whole workspace fails to build.

Verification

Generated against bluesky-social/atproto@5c3b7c9c8 (402 lexicons) with the codegen before and after this PR. The output diff is exactly 11 lines — the empty /// disappearing and the new Collection impl appearing — and nothing else moved:

--- a/app/bsky/actor.rs
+++ b/app/bsky/actor.rs
+pub struct ContentVisibilityDeclaration;
+impl crate::types::Collection for ContentVisibilityDeclaration {
+    const NSID: &'static str = "app.bsky.actor.contentVisibilityDeclaration";
+    type Record = content_visibility_declaration::Record;
+}

--- a/app/bsky/ageassurance/defs.rs
+++ b/app/bsky/ageassurance/defs.rs
-///

All 20 in-namespace records get a Collection impl (was 19).

With these fixes plus the downstream catch-up, cargo check --workspace --all-features --all-targets and cargo test --workspace --all-features both pass on a full regeneration. That regeneration will follow as a separate PR.

🤖 Generated with Claude Code