docs: fix the four rustdoc link errors that fail ci / Docs

`ci / Docs` runs rustdoc with `-D warnings`; four link defects in `trash-core`
were errors under it, so `cargo doc` refused to document the crate (exit 101).
All four predate this branch — the job only started running here.

- windows.rs:34 and :141 — `[`Error`]` is ambiguous: the crate has both an
  `Error` enum and thiserror's `Error` derive macro. Disambiguated to
  `[`enum@Error`]`, rustdoc's own suggested form; both still link.
- windows.rs:94 — the `NameLengthTooLarge` doc linked `MAX_V2_NAME_CHARS`,
  a crate-private const. Demoted to a code span and the value (32768) stated
  inline, so a reader gets the cap without a link to something unreachable.
  The const stays private.
- linux.rs:42 — `[8]` is a footnote reference to the trash-spec, but markdown
  reads it as a reference link. Backticked.

No `#![allow(rustdoc::...)]` anywhere; no item's visibility changed.

Control (revert -> fail -> restore), same commit, same command
`RUSTDOCFLAGS="-D warnings" cargo doc --no-deps --workspace --all-features`:
  with fix     -> exit 0
  fix reverted -> exit 101, 4 errors
  restored     -> exit 0
`cargo fmt --check` clean.

Only `ci / Docs` was in scope; no other check was touched.

Author: h4x0r

trash-core/src/linux.rs

@@ -39,7 +39,7 @@
 //!   carries **no timezone** — it is naive *local* time, so it is decoded into a
 //!   [`NaiveDateTime`] and must never be treated as UTC.
 //! * If `Path=` or `DeletionDate=` appears more than once, the **first**
-//!   occurrence wins (spec footnote [8]).
+//!   occurrence wins (spec footnote `[8]`).
 //!
 //! [`trash-forensic`]: https://docs.rs/trash-forensic
 

trash-core/src/windows.rs

@@ -31,7 +31,7 @@
 //! followed by the variable-length UTF-16LE path at offset 28.
 //!
 //! All integers are read through bounds-checked helpers: `$I` bytes are treated
-//! as attacker-controlled, so a truncated or hostile file yields an [`Error`],
+//! as attacker-controlled, so a truncated or hostile file yields an [`enum@Error`],
 //! never a panic.
 //!
 //! [`trash-forensic`]: https://docs.rs/trash-forensic
@@ -91,7 +91,8 @@ pub enum Error {
         needed: usize,
     },
 
-    /// The version-2 name-length field exceeds [`MAX_V2_NAME_CHARS`] — rejected
+    /// The version-2 name-length field exceeds the crate-private
+    /// `MAX_V2_NAME_CHARS` cap (32768) — rejected
     /// before allocating to defend against a hostile length.
     #[error("$I v2 name length {chars} chars exceeds cap {MAX_V2_NAME_CHARS}")]
     NameLengthTooLarge {
@@ -138,7 +139,7 @@ pub struct RecycleBinIndex {
 ///
 /// # Errors
 ///
-/// Returns [`Error`] when the data is truncated, carries an unsupported version,
+/// Returns [`enum@Error`] when the data is truncated, carries an unsupported version,
 /// or (version 2) declares a filename length that overflows the buffer or the
 /// safety cap. Never panics on hostile input.
 pub fn parse_index(data: &[u8]) -> Result<RecycleBinIndex, Error> {