Use spec-prod for gh-pages publication

[himorin]

as title, to make things simple.

[himorin]

@nigelmegitt @gkatsev this PR is what I've mentioned (using echidna for streamlined publication to /TR/ as CRD, as well as pushing to github.io) during last call at:
https://www.w3.org/2026/03/12-tt-minutes.html#107e

It seems I need to update some, llike w3cid or deleting more (like what format.py is for - could not find any relevant use and I may need to read and understand script...), so let me prepare in parallel to 2w CfC period in TTWG.

[gkatsev]

Looks like format.py is used to format the index.bs file a bit. Like making sure the line-length isn't too long.
Looks like it was written from python 2 but seems to work with python 3 with minimal changes. I'll open a PR for it and we can see if we want to keep it.

[himorin]

@gkatsev thank you really much for investigation.
hrm, if it is something to fix and update bikeshed source itself, I somehow wonder if we could have it as check against PR to point potential point to be fixed rather than run as offline/online tooling as automatical fixup. I observe some lint tool running at some other repositories, and I always encounter difficulty to check and track root point of certain changes, e.g. diff over large amount of time may contain normative changes with overrided lint commit.

[gkatsev]

yeah, I agree that it's a bit annoying, though, hopefully if things are maintained as clean it helps not have large changes in a single commit. Though, it is possible to hide commits from blame, so, we can always do a fixup in a PR and add that commit to the exclude.

Also, I do agree that if bikeshed has a build-in formatter, it would be nice to use that.

[himorin]

closing per #546
note, format.py discussion may be followed up in other issue.