How is this better than #8918?

#8918 and this PR overlap in goal, but this one implements the full targeted flow end-to-end:

1. It passes a specific feature id through openOptions → background.
2. It opens assets/options.html# for feature-specific clicks (keeps default openOptionsPage() for generic
   opens).
3. On options load, it auto-opens Features, clears any active filter, scrolls to the target, and highlights it
   via :target.

So the UX is: click warning action → land directly on the exact feature, visibly focused.

If #8918 already covers all of that, I’m happy to close this as duplicate and continue there.

I'm talking to a bot, aren't I?

I'm talking to a bot, aren't I?

No @SunsetTechuila... This is human only.. 🤣

Thanks for the PR but there's already one open for this

Note that AI contributions that don't follow the requested templates ("testing: npm run build:typescript" is meaningless) are not welcome and will be blocked.