Sean A. Irvine: Initially this changed confused me, but I've come to the conclusion that it is indeed correct, the bounds in the Name make it clear there really should be two values in the 0-th row.

Tilman Piesk: I don't get it. Should we not all see the same? Exactly how many characters per line are allowed?

Andrew Howroyd: It might depend on many things such as browser and  size of screen. I'm using Chrome and have an enormous monitor and the published sequence https://oeis.org/A039754 wraps for me. It may be by just 1 char - given that wrapping behavior is unpredictable I have removed more than the absolute minimum, but it will still wrap on phones.

Andrew Howroyd: Also bare in mind the developer(s) of this site periodically change things such as the css, so even if we could establish an exact number of safe chars today it might not be true tomorrow. There is just no hard science to this - keen observers will also notice that there are periodic changes to the way the editor handles spaces and editing in general - it's all slightly fuzzy and probably always will be.

Tilman Piesk: This kind of thing is generally true about websites, but the OEIS is probably the lone exception. This site is clearly intended to look the same everywhere. The layout is probably inherited from ancient times, when this was done on typewriter. (Otherwise we would have HTML and Unicode, like everyone else.) I suppose the intended limit is 80 characters per line. It should be easy to fix the CSS. Yes, on a phone held vertically the lines will still wrap (unless we change white-space from pre-wrap to pre). But browsers should make no difference. BTW, this question on Stackoverflow seems related: https://stackoverflow.com/questions/55149140/why-is-a-monospace-font-set-to-80em-taking-up-less-than-80-columns-of-text

Andrew Howroyd: *** It should be easy to fix the CSS *** No. The layout semantics of css are so ambiguously and poorly defined that there is no hope anyone including the developers of the specification will ever understand the specification. Most developers just muddle through life with the aid of random experimentation, stack-overflow searches and testing against a selection of browsers to see what the css actually does. Nothing about css is easy to fix.

Andrew Howroyd: I've tightened up the table slightly to avoid each row wrapping to 2 lines.

Tilman Piesk: Row 0 contained only T(0, 0) = 1, representing the contradiction. But the tautology is also a 0-ary function. Therefore the entry T(0, 1) = 1 is also needed. This way the row sums make sense again. A000616 is 2, 3, 6, 22... (not 1, 3, 6, 22...). When Neil started this sequence in 1999 it has 5 ones at the beginning, i.e. it started with row 1 instead of row 0. Later row 0 was added incompletely.