docs: fix broken intra-doc links under -D warnings

buffa-codegen/src/context.rs

@@ -12,7 +12,7 @@ use crate::CodeGenConfig;
 ///
 /// See `DESIGN.md` → "Generated code layout" for the full layout. The name
 /// is checked against proto package segments and message-module names by
-/// [`crate::validate_file`]; a collision is a hard error.
+/// `validate_file`; a collision is a hard error.
 pub const SENTINEL_MOD: &str = "__buffa";
 
 /// A Rust type path split at the target-package boundary.

buffa-codegen/src/lib.rs

@@ -888,7 +888,7 @@ fn format_tokens(tokens: TokenStream, source: &str) -> Result<String, CodeGenErr
 /// e.g., `"google.protobuf"` → `"google.protobuf.mod.rs"`. The unnamed
 /// package uses the [`SENTINEL_MOD`](context::SENTINEL_MOD) name as its
 /// filename stem — `package __buffa;` is already rejected by
-/// [`validate_file`], so the unnamed-package stitcher cannot
+/// `validate_file`, so the unnamed-package stitcher cannot
 /// collide with any real package's.
 pub fn package_to_mod_filename(package: &str) -> String {
     if package.is_empty() {

buffa/src/extension.rs

@@ -51,9 +51,9 @@
 //! # JSON
 //!
 //! Extension fields serialize as `"[pkg.ext]"` keys in proto3 JSON. This
-//! requires a populated [`TypeRegistry`](crate::type_registry::TypeRegistry)
-//! — see the [`type_registry`](crate::type_registry) module. Without a
-//! registry, extension bytes stay in `__buffa_unknown_fields` and are silently
+//! requires a populated `TypeRegistry` — see the `type_registry` module
+//! (available under the `json` or `text` feature). Without a registry,
+//! extension bytes stay in `__buffa_unknown_fields` and are silently
 //! dropped from JSON output.
 //!
 //! # Presence semantics