The one thing I would add to each swatch is where the number came from. A value read out of a palette table and a value sampled from a screenshot are not the same number, and the difference is invisible.
I ran into this today on something unrelated. A page painted #0b0d14, and macOS screencapture wrote rgb(8,13,16) into the file, because the capture lands in the display's colour space rather than sRGB. Handing that same hex to a video encoder gave a third answer, rgb(9,11,17), this time from the yuv conversion. I had to ask for #0a0f13 to get back the value the page had actually painted.
So any swatch sampled from a screenshot of a running install is drifted by a few levels, silently, and a CRT is a further step away again. One line per entry saying "documented VGA palette" or "sampled from a VM" would make this citable rather than just lovely to scroll, and it would settle the Windows 98 teal question in the sibling comment.
“In most computer display systems, images are encoded with a gamma of about 0.45 and decoded with the reciprocal gamma of 2.2. A notable exception, until the release of Mac OS X 10.6 (Snow Leopard) in September 2009, were Macintosh computers, which encoded with a gamma of 0.55 and decoded with a gamma of 1.8”
I ran into this today on something unrelated. A page painted #0b0d14, and macOS screencapture wrote rgb(8,13,16) into the file, because the capture lands in the display's colour space rather than sRGB. Handing that same hex to a video encoder gave a third answer, rgb(9,11,17), this time from the yuv conversion. I had to ask for #0a0f13 to get back the value the page had actually painted.
So any swatch sampled from a screenshot of a running install is drifted by a few levels, silently, and a CRT is a further step away again. One line per entry saying "documented VGA palette" or "sampled from a VM" would make this citable rather than just lovely to scroll, and it would settle the Windows 98 teal question in the sibling comment.