Add an EBNF like WikiText description to the dev edition

[pmario]

I always wanted to have a EBNF like TW wikitext description.

So I told Claude Code to add one to the dev edition.

[netlify]

✅ Deploy Preview for tiddlywiki-previews ready!

Name	Link
🔨 Latest commit	ba991c0
🔍 Latest deploy log	https://app.netlify.com/projects/tiddlywiki-previews/deploys/69dd3a4695704e0008f4b848
😎 Deploy Preview	https://deploy-preview-9805--tiddlywiki-previews.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

Confirmed: pmario has already signed the Contributor License Agreement (see contributing.md)

[github-actions]

⚠️ Change Note Status

This PR appears to contain code changes but doesn't include a change note.

Please add a change note by creating a .tid file in editions/tw5.com/tiddlers/releasenotes/<version>/

📚 Documentation: Release Notes and Changes

💡 Note: If this is a documentation-only change, you can ignore this message.

[Jermolene]

Hi @pmario this looks promising. How might we go about verifying that it is accurate and complete?

[pmario]

Hihi, I did think about that too. At the moment it is EBNF-like, for documentation purposes.
Eg: Detailed character definitions are missing for "terminal" definitions. They are prose text atm.

That's the final prompt, where it asked about tone in question no. 4

My command was this:

Wikitext EBNF is ok. Then it could be EBNF - Pragmas to make them shorter
ad 4) tone: more prose, so humans can understand it. -- IMO we can refine it later anyway. 
Would it make sense to split that work into several processes. you have beads that would allow you to manage several workers. 
any questions left?

(I wanted it to use several workers, to see if I really need a new "management system" like GasTown)

So we would need to re-define it, concatenate them all together and give the result to a parser generator.

The interesting point is, in the dev session I am seeing, it pointed out most of the inconsistencies, that makes debugging difficult. ...

Our parser is context sensitive. eg: {{{ .. }}} needs to be parsed before {{ .. }} to avoid "confusion". ... I think it even points that out somewhere

Our \pragma rules will definitely make problems. I don't think EBNF can define that, so a parser generator can use it properly.

[pmario]

Just a test

I did add railroad diagrams, but they would need much more work to be useful.