1. Login failure
The login is failing because you haven't bought Minecraft for those accounts. When you buy Minecraft it will be listed as one of your games in your account when you log in on Mojang.com, but until then you don't have a Minecraft login, you just have a login to a website that doesn't do anything except tell you that you haven't bought any games to use it with yet. You can still play in offline mode, since Mojang is not so obtuse as to require you be always-online in order to play Minecraft, unlike some other game publishers. However...
2. Server connection failure
When you connect to a server it will check if your account has a Minecraft registration too, and will drop the connection if not. So there are two times your login is checked for Minecraft access: once when you start the game, and once when you start multiplayer.
Fixing the server connection
The server's behaviour can be modified by editing server.properties and setting the line:
online-mode=true
to false instead. The players wanting to connect then pick a name to use consistently (since the server won't enforce identities to match what it has saved in its world files) and "try" to log into the game with that, let it fail, then play offline. Since the server is set to offline mode too, it will allow them to connect under that name.
The problem with this is that anyone can connect – make sure that the server isn't exposed to the internet, and the worst of the complications will be avoided.
The more likely problem though is that you'll have a bit of a headache migrating the kids' work once they have full accounts, since it's likely that the names they pick won't be available to choose once Minecraft is added to the Mojang account (which is when you can pick an official profile name for use in Minecraft). If there are name changes, then you'll have to either walk the child through the idea of losing their inventory and location on the server (blocks they placed will still be there), or you'll have to fiddle with NBT editors to transfer the inventory and location from the old name to the new one in the server's save files. Not hard, either one, but a stumbling block to be aware of.
The real solution here is to register a Mojang account for each child and purchase Minecraft for each account. I understand the desire to test it all out first, but if they already like Minecraft in single player, there aren't really any surprises that come with multiplayer that should change their or your mind. The advantage here is:
You'll immediately get the names that they'll be sticking with (consult and choose wisely, for children are fickle!) and can avoid identity issues in the server's save files.
You'll be able to set custom skins for their avatars, which children inordinately enjoy, in my experience. These are kinda nice in single player, but since they're readily visible in multiplayer they become more relevant when playing with others.
Fewer steps in logging in and connecting to multiplayer where mistakes could happen (a registered account can be remembered with it's password, making logins one-click), which for younger kids can be a bit of a headache-saver for you.
My kid has had an account for a year or so now and loves playing with other people, even if it's only to make random block stacks and randomly-enchanted gear in Creative mode. But then, that's 5-year-olds for you.
I believe you are referring to the permission nodes that are integrated into Bukkit already, such as /say, /plugin, /help, /stop, etc. You can find them all on the Bukkit Wiki, in a nice, organized table.
Best Answer
Well, if your script is capable to send commands to the server (via RCON or similar), then you just need to send them all one by one.
However that could be really slow and not quite good. Because your script cannot have "back checks", the server will just make the command (or won't) and script won't have any info how (and when) it finished. So you will need to call the next command when you will be sure the previous one is completed. That can be really painful to construct (and if server lags, you need to probably manually check where it finished or start over again).
There is also another possible solution, but it needs some changes to your server. If you know anything about Bukkit/spigot servers capable running server-only plugins, then it will be easy for you, otherwise you should study something about it. The thing is that there are already well-developed tools for mass changes in worlds, but you need Spigot server to run them.
That tool is WorldEdit, which is kind of superior in large scale building and changing of blocks. However it is not comfortable with commands from console, it is mainly built as ingame (player position dependant) tool.
BUT it can run SCRIPTS , you also are able to write your own scripts, so then you just need to call them and automatic creations are no problem. All you nee to know for writing those scripts is JavaScript.
This plugin is well updated and have quite good documentation, you can try it. It will be definetly better than sending thousands of commands to your server directly.