v2.7.0

JAWATA v2.7.0 — the jawata release

GOJA is now JAWATA. Same engine, same tools, same license — a new, trademark-clean
name with its own home: jawata.org.

What renamed

• Product + launcher: the product is jawata, the runtime jar is jawata.jar
  (Jawata.app on macOS). Release bundles are jawata-<tag>-<platform>.
• Java namespace: every bundle and package moved org.goja.* → org.jawata.*;
  Goja* classes are now Jawata*.
• MCP registry name: io.github.haraldwegner/jawata.
• Repository: haraldwegner/goja-mcp → haraldwegner/jawata-mcp (GitHub redirects
  the old URLs).

Experience-store migration (schema v4)

Your knowledge store migrates automatically and loses nothing:

• Stored symbol anchors are rewritten in place — both the package half
  (org.goja.… → org.jawata.…) and the class-name half (…GojaServer#start →
  …JawataServer#start) — so every entry stays recallable by its new name.
• The store file moves from ~/.local/share/goja/ to ~/.local/share/jawata/
  (moved as-is, never wiped).
• A backup is written before the migration, as always.

Compatibility (one release only)

Existing setups keep working during the transition:

• Old goja.* system properties and GOJA_* environment variables are still read
  when the new jawata.* / JAWATA_* forms are absent.
• These legacy fallbacks are removed in the next release — switch your
  configuration to the jawata names now.

Heritage

Some early parts derive from pzalutski-pixel/javalens-mcp (MIT) — credit to Peter
Zalutski. The NOTICE attribution is unchanged.

Before upgrading

Stop any still-running old goja.jar residents before the first jawata start
(pgrep -af goja.jar) — a surviving old process holds the store open during the
migration and can leave the automatic pre-migration backup empty. The store data
itself migrates correctly either way.