A bare <PACKAGE NAME="Developer" /> only adds the package's RELEASED
plugins, so half of them (the STABLE ones) were missing and Configure
showed Developer unticked. The project window wasn't configured at all.
- CodeBrowser: insert ghidra/codebrowser-developer.xml, which lists the
STABLE plugins explicitly, into the default CodeBrowser.tool in
Public_Release.jar.
- Project window: it has no default config to patch, so ship
ghidra/FrontEndTool.xml in the user settings with its three
Developer plugins.
- Pre-creating the settings dir makes Ghidra show its user agreement;
ghidra/preferences sets USER_AGREEMENT=ACCEPT, the value Ghidra
writes by itself on a fresh start.
Verified by closing Ghidra cleanly: it rewrites FrontEndTool.xml from
the loaded plugins and kept all three Developer plugins.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
