Local native builds reuse stale jars and ignore ARCADEDB_TAG #9

A local native build (scripts/build.sh darwin/arm64 ... → scripts/build-native.sh) packages whatever jars are already in src/arcadedb_embedded/jars. It doesn't pull arcadedata/arcadedb:${ARCADEDB_TAG:-latest} again. As a result:

• once latest moves to a new snapshot, local wheels keep the old engine until the jars are replaced by hand;
• setting ARCADEDB_TAG has no effect on what gets bundled.

CI isn't affected: download-jars always fetches fresh jars.

Proposed fix: refresh the jars directory from the image when no explicit jars dir is passed, or at least warn when the bundled engine version differs from the tag's.

Found in the final review of the move from ArcadeData/arcadedb (#1).

🤖 Generated with Claude Code