Added a new package for the BoxLang Language

[lmajano]

• [√ ] I'm the package's author and/or maintainer.
• [ √] I have read [the docs][1].
• [ √] I have tagged a release with a [semver][2] version number.
• [ √] My package repo has a description and a README describing what it's for and how to use it.
• [ √] My package doesn't add context menu entries. *
• [√ ] My package doesn't add key bindings. **
• [ √] Any commands are available via the command palette.
• [ √] Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• [ √] If my package is a syntax it doesn't also add a color scheme. ***
• [ √] I use [.gitattributes][3] to exclude files from the package: images, test files, sublime-project/workspace.

My package is a comprehensive package for support for the BoxLang JVM Language.

There are no packages like it in Package Control. We are the authors of the language itself.

[lmajano]

All issues have been addressed

[github-actions]

This PR removes Tahcia Script Sync and adds BoxLang.

Review for BoxLang main-5d917a8-2026.05.27.11.05.25

• Repository is at https://github.com/ortus-boxlang/sublimetext-boxlang
• Common used command prefix is: boxlang.
• Tip of main is tagged with 1.0.2. ✅
• Package defines syntax settings. Consider adding an entry in 'Main.sublime-menu' and 'Default.sublime-commands' to help users find or customize them.

1 failure:

• 'Main.sublime-menu' has a 'Key Bindings' entry for Default.sublime-keymap, but 'args.user_file' is missing. Set it to '${packages}/User/Default (${platform}).sublime-keymap'.

2 warnings:

• Package defines '.sublime-settings' files but is missing 'Default.sublime-commands' to add a Command Palette entry to edit them.
• 'Main.sublime-menu' has no 'Settings' entry with 'args.base_file' set to '${packages}/BoxLang/BoxLang.sublime-settings'. Found: ${packages}/BoxLang/settings/BoxLang.sublime-settings

[lmajano]

this is using the old tag of 1.0.2, 1.0.3 is the latest and everything is now fixed

[braver]

You've got mixed indentation in your entry, I believe mostly on this line.

[braver]

Just some superficial stuff till I get around to a more thorough review:

• It would probably be a good idea to opt-in to the newer python runtime: example.
• You can use .gitattributes to exclude tests, agent specs, etc from the package as it's delivered to users.
• Note that messages are served as plain text. Raw markdown is pretty readable, but you have a lot of markup in there that would be better if simplified.
  • Related: users will see this only once and probably won't read all of it (especially if it's this much). Consider that users already installed the package so you don't have to sell it on them here. So focus on "getting started" stuff and then link to the README for more details.