Further, since the initial cost of cutting too deep is loss of resilience, it's easy to go beyond the point of no return without noticing.
So you DO accept that an original PC with a Hercules card running DOS was a hardware accelerated GUI.
If the website and company won't delete the user, then the user will have to delete the website and the company. Significant legal restrictions may apply.
More specifically, in a little over 40 years, nobody has successfully made a 'does-it-all' GUI in spite of trying. Since it's not there now, and I see no evidence that it'll be there in the near future, the point stands: if you want to have full use the computer, you'll have to use CLI because there is no turing complete GUI.
AppleScript is very much text rather than graphical in nature. More specifically, it is a scripting language that sends events to objects. Those objects may happen to be represented by graphics for the user but that is orthogonal to the scripting. And, as you say, it's not an interactive interface.
The specific comparison is any existing GUI shell vs BASH (or similar).
In principle, perhaps but in practice, nobody has ever managed it in a GUI, certainly not in a form anyone would willingly use.
The Breeze Card uses the MIFARE smart-card system from Dutch company NXP Semiconductors, a spin-off from Philips. The disposable, single-use, cards are using on the MIFARE Ultralight while the multiple-use plastic cards are the MIFARE Classic cards. There have been many concerns about the security of the system, mainly caused by the poor encryption method used for the cards. See Security of MIFARE Classic (http://en.wikipedia.org/wiki/MIFARE#Security_of_MIFARE_Classic) for details.
Most people would not consider an xterm open on a bare X window to be a GUI unless there were things like a drag and drop file manager available. They would consider that to be a CLI.
If you disagree, then you will also accept that the original IBM PC with a Hercules card was a hardware accelerated GUI.
IBM believed it could cut every corner and go the cheap labor route and nobody would notice while their profits soared. They are wrong.
You got an extra zero in there, right? As in 7 years sounds about right?
I know some authors protest that seven years is too long, and the majority of income is made in the first three years and after five it would be advantageous to have the works available in the public domain (but the publishers don't want the competition from previously released works), but I think that varies from author to author, so doing a compromise of seven seems reasonable - we can experiment with shortening it further after having seen what happen when we cut it to seven.
UML is a text format. CASE tools tended to let you drag blocks of text around. Googeling shows little more than mapping words onto alternative glyphs that are then organized exactly as words would be in a text file. By that definition, a conventional C program using clever macros so you could program in Chinese would count.
The one thing they all have in common is that they eventually resort to text written on the graphical elements somewhere. None of them actually exploit any innate expressiveness of the graphical display.
They also aren't self hosted for the simple reason that actually writing something that complex with such clumsy tools is impractical.
But more to the point, none of that is a shell. They have GUIs but they are not GUIs.
Perhaps someone will eventually figure out some way to manage it, but thus far, nobody has. Not even to the point of being able to tell the computer "see this group of files named as report-MMDDYY? Make them YYYYMMDD-report.txt".
Upon more thought I believe it may be posable but I doubt it will be practical.
//GO.SYSIN DD *, DOODAH, DOODAH