Silksong!

That point absolutely still stands.
It's just strange that since the 4a, the 2 smallest phones Google released were both not in the a series.

The only A series Pixel phone smaller than the Pixel 8 was the Pixel 4a.

They also usually assume a lot about the users' knowledge of the domain of the program itself.

In my experience, many programs' man/help is very brief, often a sentence or less per command/flag, with 2 or more terms that don't mean anything to the uninitiated. Also, even when I think I know all the words, the descriptions are not nearly precise enough to confidently infer what exactly the program is going to do.
Disclaimers for potentially dangerous/irreversible actions are also often lacking.

Which is why I almost always look for an article that explains a command using examples, instead of trying to divine what the manual authors had in mind.

win + space to switch between keyboard languages
win + tab to open the desktop switcher
win + ctrl + t (if you have PowerToys installed) to prevent other apps from stealing focus from your window

I use the tiles to "pin" programs that I use semi-regularly and can't be bothered remembering the name of. Or that share an inconveniently long prefix with the name of another program. Or that I have multiple versions of installed, with a specific version I usually need.

I don't like pinning such programs to the task bar because they add unnecessary clutter while not in use.

It does and you can safely ignore us.
Just two pendants nitpicking people's spelling on the internet.

!corsicanguppy appeared to imply your spelling of "till" to be incorrect and that the "correct" spelling is "'til". I pointed them to a dictionary describing the word with the spelling you used and the meaning you intended.
Both comments are inconsequential to your point, and to anything, really.!<

till

That's quite interesting.

Although it would need access to an already configured and fully functional environment to actually run this.
I don't think we're quite at the point yet where it's able to find the correct script, pass it to the appropriate environment and report the correct answer back to the user.
And I would expect that when integration with external systems like compilers/interpreters is added, extra care would be taken to limit the allocated resources.

Also, when it does become capable of running code itself, how do you know, for a particular prompt, what it ran or if it ran anything at all, and whether it reported the correct answer?

Congrats, you've just discovered internet memes.

Bonus: good tests can also serve as technical documentation.

Though I have to disagree with the notion that documentation is as important or more so than code.
Documentation is certainly near the top of the list and often undervalued. I've worked on a project where documentation was lacking and it was painful to say the least.
Without documentation, changing or adding features can be a nightmare. Investigating bugs and offering support is also very difficult. But without code, you have nothing. No product, no users, no value.

There are (inferior) substitutes for documentation: specialized team knowledge, general technical expertise. These alternative pools of knowledge can be leveraged to create and improve documentation incrementally.
There's no replacement for the actual functionality of your applications.