Panic "byte index 5 is not a char boundary" in oxc_semantic/src/jsdoc/parser/jsdoc_tag.rs when fixing file

[qarmin]

File content(at the bottom should be attached raw, not formatted file - github removes some non-printable characters, so copying from here may not work):

/**
 * @param {A}�a
 */
const foo = (a) => {
};

command

timeout -v 100 oxlint -D all -D nursery --import-plugin --jsdoc-plugin --jest-plugin --vitest-plugin --jsx-a11y-plugin --nextjs-plugin --react-perf-plugin TEST___FILE.ts --fix

App was compiled with nightly rust compiler to be able to use address sanitizer
On Ubuntu 24.04, the commands to compile were:

rustup default nightly
rustup component add rust-src --toolchain nightly-x86_64-unknown-linux-gnu
rustup component add llvm-tools-preview --toolchain nightly-x86_64-unknown-linux-gnu

export RUST_BACKTRACE=1
export ASAN_SYMBOLIZER_PATH=$(which llvm-symbolizer-18)
export ASAN_OPTIONS=symbolize=1
RUSTFLAGS="-Zsanitizer=address" cargo +nightly build --target x86_64-unknown-linux-gnu

cause this

thread '<unnamed>' panicked at crates/oxc_semantic/src/jsdoc/parser/jsdoc_tag.rs:143:39:
byte index 5 is not a char boundary; it is inside '\u{83}' (bytes 4..6) of ` {A}�a
 `
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

##### Automatic Fuzzer note, output status "None", output signal "Some(6)"

compressed.zip