BIP 394 gives the rawtr() descriptor, used in Bitcoin Core since version 24.0, a specification of its own
The Bitcoin Improvement Proposals repository merged BIP 394 on 6 November. It specifies the rawtr() output script descriptor, a way for wallets to describe a Pay-to-Taproot output by its output key directly, without the internal key and script tree that the existing tr() descriptor from BIP 386 requires. The proposal is written by the author using the handle jeanpablojp, has Draft status and builds on BIP 341 and BIP 380.
A Taproot output key is normally derived from an internal key and an optional script tree. tr() takes those two inputs and computes the output key, which leaves no way to describe an output whose internal structure is unknown, for example a key received from another party or one whose holder does not want to reveal the script tree. rawtr(KEY) fills that gap: it can only be used at the top level, takes a single key, applies no BIP 341 tweak, and produces the script OP_1 followed by the key. As with tr(), keys must be x-only; compressed keys are converted and uncompressed ones are rejected.
The expression is not new in practice. According to the BIP, Bitcoin Core has implemented it since version 24.0, and BIP 390 already allows musig() inside rawtr() in its test vectors. The motivation for writing it down is that its absence has already produced divergence outside Bitcoin Core: rust-miniscript renders such outputs as rawtr_not_supported_yet(KEY) and cannot parse them back, while bdk-ffi's descriptor tests describe rawtr() as BIP 386, which actually specifies tr().
The proposal includes a security note. If the private key for the output key is known, the output can be spent through the key path, but nothing in a rawtr() descriptor proves that the key does not also commit to a script tree. Software that imports such a descriptor from an untrusted source should therefore warn that other spending paths may exist. The test vectors, generated with Bitcoin Core, include a case using the same key as the first tr() vector of BIP 386 to show that rawtr() leaves the key unchanged where tr() tweaks it.

What it means
For wallet developers this turns a Bitcoin Core behaviour into a shared standard, which should let libraries such as rust-miniscript parse and round-trip these descriptors consistently. The warning about hidden script paths matters for anyone importing watch-only descriptors from someone else.