Azeroth Navigator 0.6.0

Azeroth Navigator 0.6.0 — route and preparation developer preview

Windows x64 developer prerelease. This increment adds conservative objective
clustering, route-derived acquisition, agreed local-party exports and preparation
and compatibility views. Focused gameplay acceptance remains incomplete.

Changes since 0.5.0

• Solo and joint planning can group compatible objectives at an explicitly declared
  common node, count inbound travel once and retain original objectives and singleton
  alternatives. Rewards and memberships remain disjoint. Joint utility uses the
  minimum member summed utility; no shared-kill savings are inferred.
• Gear can inspect acquisition opportunities along an authoritative recalculated
  route. Explicit source/node/leg associations produce conservative directed detour
  cost within the residual session budget. Finite attempts, prerequisites, group
  assumptions and unknown costs remain visible. Opportunities are evaluated
  independently; combined acquisition scheduling is not implemented.
• An explicitly selected recipient can export an agreed local-party plan after all
  recorded local acceptances. The export preserves original joint choices, recipient
  applicability and full cohort provenance. Changed snapshots, membership, content,
  field freshness or agreement prevent publication. This is local consent, not a
  verified in-game party messaging feature.
• Dungeons displays imported-character or local-party preparation, condition and
  quest gaps, declared rewards, route requirements and manual checklists. Advanced
  local package input is bounded and explicitly unverified. No verified Deadmines
  package, real role model or consumable ownership is supplied.
• Compatibility consolidates exact build/context, declared content coverage, policy
  states and sanitized historical diagnostic evidence. API presence remains distinct
  from readable values. The historical 0.5.0 inventory is hash-bound to its dataset;
  no reference build is relabeled as the observed client.
• An optional ordinary reference window displays imported snapshot state with
  separate capture and field ages. Show/hide and always-on-top are explicit desktop
  controls. The reference webview can call only the read-only reference command;
  main retains its management controls. Exclusive fullscreen is unsupported;
  borderless, focus, DPI and multiple-monitor behavior remain unverified. The normal
  desktop view remains available, and the Lua HUD remains the live guidance surface.
• Planning publication now holds a database read reservation through final validation
  and handoff, preventing another process from changing captured state in that gap.
  Solo export identity includes the actual result and snapshot content, and export
  expiry accounts for finite typed-field deadlines. Unavailable inputs remain distinct.

Compatibility and limitations

Exchange schemas, addon transports, dataset identities and database schema8 remain
unchanged. Package versions and synthetic producer metadata increment to0.6.0;
Atlas PNG bytes retain their existing hashes. Imports remain bounded data and no
addon socket, game process access or input automation is introduced.

The only recorded live build is Forever1.60.1.70338/interface16001. Existing user
reports cover level12 and limited clock/reload behavior. Consolidated quest,
equipment, position, plan/session, restricted-context and installed-version checks
remain unverified. The reference atlas70205 context is not compatible by inference.
Real playable quest/acquisition catalogs, role weights, permitted party messaging,
combat-log formats and a verified Deadmines package still require evidence.

Today/Settings, durable content revocation and bounded local submission/moderation
foundations remain ready follow-up engineering. Gear/acquisition explanation
presentation also needs an ordinary readable view. Official Forever API availability
is unverified; community hosting remains deferred. A developer-preview tag does not
satisfy the focused-release prerequisite for world expansion.

Files and verification boundary

Expected tag-built files: AzerothNavigator-0.6.0-x64-setup.exe,
AzerothNavigator-addon-0.6.0.zip, SHA256SUMS.txt, SOURCE_COMMIT.txt and
CANDIDATE_NOTES.md. The installer retains its existing unsigned distribution.
Checksums establish byte integrity; source metadata identifies the packaged commit.

Publication requires reviewed task PRs, all nine applicable hosted jobs on exact
updated heads and merged main, then downloaded tag assets verified for checksums,
source/version, release notes and every addon source/license byte. Actual checks
and failed attempts are recorded in the preparation/release handoffs. Hosted
Windows compilation and silent installation/start/uninstallation establish build
and packaging smoke evidence; mocked browsers do not establish native reference
window interaction or recorded-client gameplay acceptance.

Versioned source preparation passed746 portable Rust tests (one existing ignored
asset generator), strict Clippy/fmt,152 desktop tests and30 mocked Chromium flows.
Contract/transport checks passed73/33fixtures; content validation returned0errors
and3explicit coverage gaps. Actual Atlas regeneration preserved all four PNG
hashes. See docs/handoffs/2026-10-14-v0.6.0-release.md for source-locked evidence;
final hosted and downloaded-asset gates still apply before publication.