Escape from Arulco v0.1.1 - Development Paused Checkpoint

Escape from Arulco v0.1.1 - Development Paused Checkpoint

v0.1.1 freezes the current native Escape from Arulco framework after a final input,
inventory, interaction-window and verification pass. It is a fragile-tested early
alpha, not a finished campaign. Active development is paused after this release.

Read PROJECT_STATUS.md in the package or repository for the complete technical
report, known problems, scope boundary and possible restart plan.

Main changes since v0.1.0

One persistent interaction anchor

• Replaced hover-owned environment/action lists with a movable, closable and
  position-persistent INTERACTION / TARGET anchor.
• Plain F binds the exact character, item, structure or terrain relation to this
  anchor. RMB retains the transient radial menu and MMB cycles valid actions.
• Character categories and world actions dispatch through the existing canonical
  action registry rather than a second gameplay implementation.
• Added bounded hover binding lifetime so an object-derived quick icon remains
  clickable while the pointer crosses from the world sprite to the icon.

Explicit movement ownership

• Added a persisted DIRECT/CLASSIC movement switch to the expanded multitool.
• DIRECT owns WASD/Shift/Q/E and prevents an ordinary empty-world click from leaking
  into vanilla click pathing while retaining selection, double-click and world drag.
• CLASSIC yields ground LMB pathing to JA2 for squad/companion-style commands while
  retaining OS0 key suppression.
• Merely hovering a floating OS0 window no longer pauses WASD or hands the keyboard
  back to legacy UI. Real modals and physical interactions remain deliberate owners.

Inventory, inspector and cancellation hardening

• Separated retained Inspector snapshots from short-lived hover action bindings, so
  its title bar and close control remain usable.
• Added window-chrome transfer ownership: a held item can cross, drag or close a
  managed window without dropping into the world behind it.
• Refreshed inventory transfer affordances on the same event that creates the native
  item pointer, eliminating one-frame stale/empty overlays.
• Hardened Escape, carry and pending-action cancellation so the matching release
  cannot become a late move, drop or action in vanilla JA2.
• Revalidated soldier, structure and item identities when indices are reused or a
  sector transition invalidates transient objects.

Framework and verification

• Kept OS0 CONTROL entirely inside the tactical engine and removed the discarded
  external browser/server bridge.
• Added/expanded native core smoke coverage and local build/runtime verification.
• Added the early native RTS command/state foundation without claiming a completed
  RTS campaign or AI-companion layer.
• Fixed touched GCC 16/string_theory conversion paths and removed obsolete creator
  rendering code.

Validation

• Complete registered automated suite: 234/234 tests passed in 78 suites.
• Native OS0 core smoke: 7/7 groups passed.
• Windows MinGW64/Ninja RelWithDebInfo release game build: passed.
• Package gate rebuilds the tagged source, includes required runtime DLLs, source-owned
  externalized data, test/report documents and SHA-256 sidecar, and excludes original
  Jagged Alliance 2 data.

Known problems and honest limits

• The complete manual playtest matrix has not been certified on this final package.
• Some legacy UI transitions, maps, resolutions, zoom states and unusual drag/release
  sequences may still glitch despite the new ownership contracts.
• Original map assets are not comprehensively classified or interactive.
• Movement remains JA2 tile/path/animation based, not continuous analog movement.
• Carry is transactional lift/drag presentation, not rigid-body physics.
• The tutorial can be NOT REACHED on a map without a recognizable container.
• Experimental saves from every historical alpha are not guaranteed compatible.
• JA2 1.13, multiplayer/co-op, finished AI companions, general physics and a complete
  RTS/campaign economy are not implemented.

Installation

1. Extract the complete ZIP to a writable folder outside the original JA2 directory.
2. Run START_PLAYTEST.cmd.
3. Select a legally installed JA2 or JA2 Gold directory and correct language.
4. Follow PLAYTESTING.md and report PASS, FAIL or NOT REACHED.

The archive does not contain original Jagged Alliance 2 data. Windows x64 and a legal
JA2 installation are required.

Development pause

This release is a preservation checkpoint. The repository remains public for testing,
feedback and future study, but no active development or support schedule is promised.
The project is paused to prevent further feature layering until the legacy integration,
manual QA and long-term engine direction are deliberately reassessed.

Package checksum

SHA-256: 005848B6A036C36D1D8DB8FB0C272A1359F4970BBF19A20EBEE39036BFD416B2