Move at-risk to experimental

[kenchris]

"at risk" in spec means it can be removed at CR stage and then go to REC directly.

Features not marked as "at risk" and removed at CR require to do another CR before REC

In this case removing seems appropriate as we will have no "at risk" features in the spec.

---

Preview | Diff

[anssiko]

I believe it is recommended to not rely on script-based manipulation of text content, but remove the text. IIRC W3C's publication rules checker does not like custom scripts that manipulate text content. @himorin to confirm.

[kenchris]

This is now using a respec plugin, so I guess this will work :-)

[kenchris]

Seems to work @anssiko https://github.com/w3c/compute-pressure/actions/runs/11952638521/job/33318791234?pr=300 This is using a respec preprocess hook

[kenchris]

This seems to work fine and an improvement on what we have today (existing custom code) so going to merge

[anssiko]

Using the ReSpec preprocessing hook (as in this PR) to remove content before HTML generation allows the generated https://www.w3.org/TR/compute-pressure/ to pass W3C's publication rules checker.

And only the ED accepts an URL parameter to turn the experimental features on: https://w3c.github.io/compute-pressure/?experimental=1, e.g. in this PR "thermals" PressureSource.

@himorin to flag any issues in this approach, but I think this should be fine.