Should assets referenced in templates be fingerprinted during production builds?

[NullVoxPopuli]

Potentially related issues:

• Duplication of app.css in meta assets #622
• app.css is in dist folder once with and once without fingerprint #954
• Compatibility with broccoli-asset-rev functionality (asset fingerprinting, assetMap.json manifest) #755
• Asset Import Spec emberjs/rfcs#763

I have this PR (and this simpler example)
Which isn't anything new, both before and after the use of css' @import and usage of <link> tags in components, my style paths are not correctly transformed during the production build, leading to 404s in production.

Things I've tried to see if I was maybe just formatting the paths incorrectly:

<style>
  @import "/assets/tailwind.css";
</style>
<link rel="stylesheet" href="/assets/tailwind.css">

with and without leading /

console.log({ a: '/assets/tailwind.css', b: 'assets/tailwind.css' });

my production build output (dist/assets):

If I were to debug embroider looking for where we expect transformation to happen, but maybe there is just a bug, how/where would I look?
(is that even implemented atm?, I don't recall seeing any code that transforms all templates looking for assets, but I could have missed it)