Azeroth Navigator 0.5.0 — hardening developer preview

Azeroth Navigator 0.5.0 — hardening developer preview

Windows x64 developer prerelease. This increment adds recovery, responsive planning,
diagnostics and bounded content tooling. Focused gameplay and recorded-client
acceptance remain incomplete; real playable content coverage is still missing.

Changes since 0.4.0

• Database startup checks run in the background. Corruption or interrupted restore
  exposes recovery controls. Inspect an explicitly selected compatible backup,
  retain its validated identity, and restore while preserving original database
  files. Restore waits for active operations and stops the watcher. Future,
  inconsistent, extra-schema or oversized candidates are refused. Pending-marker
  cleanup failures remain visible. See docs/compatibility/DATABASE_RECOVERY.md.
• Solo and joint calculations capture immutable inputs, compute outside the store
  lock, show actual phase/work counts and support cooperative cancellation. Changed
  snapshots, membership, revisions or stale inputs prevent successful publication.
  Navigation and editing suppress obsolete replies; cancellation retains only
  prior same-input advice. Jobs have bounded active/retained counts, result bytes,
  compute time and polling. These limits are not a hard deadline for operating
  system I/O or queued command latency.
• Dense Atlas views search all pins while rendering at most200 matching pins per
  page. Counts, page controls, keyboard traversal and selection remain explicit.
  Narrow layouts and enlarged text retain schematic fallback and navigation.
  Primary navigation wraps with visible keyboard focus. Synthetic browser and
  Rust/Lua measurements are documented; ordinary Windows/native performance is
  not inferred from them.
• Local diagnostics requires explicit preview or create-new file export. It
  includes allowlisted versions, build/context coverage, distinct capture/field
  freshness and bounded foreground operation codes/timing/import attempts. Installed
  addon version and unavailable capabilities stay unknown. Successful duplicate
  imports count as attempts; watcher and historical-process statistics are excluded.
  Reports exclude raw personal exports, paths, identities, tokens and chat.
  Recovery-only startup keeps diagnostics reachable. No upload is performed.
• CLI doctor reports pinned requirements and explicitly selected path kinds without
  reading their contents or executing detected tools. Content pack build/verification
  uses typed registered sources, bounded canonical staging and integrity checks;
  existing output is preserved. Distribution eligibility describes declared metadata,
  not authenticity or proof of permission. See docs/data/CONTENT_PACK.md.
• Synthetic planner replay runs existing application services against bounded
  fixture/demo input, retaining exact contexts, logical participant mappings and
  observation states. It does not replay personal databases or live telemetry.
  See docs/data/PLANNER_REPLAY.md for examples and limits.

Compatibility and limitations

Exchange schemas, addon transports, dataset identities and database schema8 remain
unchanged. Package versions and synthetic producer metadata increment to0.5.0;
Atlas PNG bytes remain unchanged. Recovery requires compatible validated backups,
with documented512MiB/file and typed document/count limits. Native interactive
replacement, file permissions and installer focus/DPI/multimonitor workflows remain
separate acceptance work.

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 and restricted-context checks remain unverified.
The reference atlas70205 context is not relabeled as compatible with70338.

Real quest/acquisition catalogs, role weights, party messaging, agreed joint addon
export and a verified Deadmines package are still missing. Automatic clustering,
route-derived acquisition, preparation/Today/Settings and the scoped ordinary
reference-window experiment remain later engineering work. Official Forever API
availability is unverified; hosted community infrastructure remains deferred.

Files and verification boundary

Expected tag-built files: AzerothNavigator-0.5.0-x64-setup.exe,
AzerothNavigator-addon-0.5.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 and PR/tag
runs. Mocked browsers and package builds do not establish native interaction or
live gameplay acceptance.