CSS Snapshot naming, transition requests, and always being a FIRST Public Note

/TR/CSS is a redirect to the current snapshot.

The actual snapshot is published as /TR/year/NOTE-css-year-fulldate whose latest version is /TR/css-year and is a First Public Note, which means it has no History and no previous version. Also we never publish another version. And we have to do a transition request each time, and can't use the automatic publishing system. (I tried, but failed)

If instead we published the snapshot as /TR/year/NOTE-css-fulldate with a latest version as /TR/css then in all subsequent years we would have a previous version /TR/lastyear/NOTE-css-lastyeardate which would mean we would only need to do a document transition once and in all subsequent years we would use the automatic publishing system.

Besides being easier and avoiding jumping through some publishing hoops, this would also be more accurate because it is indeed a set of revisions of basically the same document. It just has a yearly cadence. The entire point of the transition request for First anything is because it is a brand new thing.

Start by comparing the current /TR/year/NOTE-css-year-fulldate and /TR/css-year naming with the proposed /TR/year/NOTE-css-fulldate and /TR/css scheme. Read the linked Echidna limitations and transition-request discussion first. Done means the yearly snapshots are treated as revisions, with one initial transition and automatic publishing thereafter.