Azeroth Navigator is a Rust, Tauri/React desktop companion with a Lua addon for World of Warcraft: Forever. Desktop character state comes from explicitly imported snapshots; live game observations remain inside the permitted addon environment. Synthetic fixtures are always labelled.
The current build is the 0.9.2 developer preview (published 2026-10-17; the previous build is 0.9.1). It contains tested engineering foundations, but no verified playable quest, item, acquisition or travel catalog. Interactive Windows and complete live-game acceptance remain unverified. See the release notes, preparation record and the 0.9.2 publication evidence.
The v1.0.0 target (ADR 0006) is a declared slice (Human, levels 1-20, Elwynn Forest, Westfall, Redridge Mountains and the Deadmines) on the first stable live WoW Forever build after the 4 Nov 2026 launch, with Windows desktop support; see TODO.md. The earlier target was Forever 1.60.1.70374. The user reports that build and interface 16001 on Windows 11, out of combat, with pre-version-bump 0.8.1 diagnostics reporting no errors; source-identified development captures now verify quest completion flags and one opt-in turn-in/export flow. These limited observations do not establish full compatibility or frozen-candidate acceptance. Missing mandatory content, source permissions or real acceptance evidence blocks v1.0.0 publication. Acceptance candidates also require complete licensed content and static validation; see the v1 release process.
- Download the Windows installer,
SHA256SUMS.txt,SOURCE_COMMIT.txtand notes from the linked 0.9.2 release. Check the installer hash before running it. - Follow Windows installation, including the separate, explicit addon installation into the client-selected AddOns folder.
- Use addon setup to record the actual client
build. The snapshot, clock, position, plan and recording adapters admit
1.60.1.70338and1.60.1.70374, and for development capture only (UNVERIFIED)1.60.1.70425, each with interface16001, experimentally./anavopens the in-game window described in the addon window guide. Selectable exports and opt-in quest-turn-in recording are included. Full live acceptance remains required. A matching TOC interface alone does not establish compatibility. - Imported profiles remain local. The browser demo and bundled reference imagery are synthetic; they do not establish game-content coverage. Keep personal SavedVariables and backups private.
| Identity | Current evidence |
|---|---|
| Application/addon 0.9.2 | Published developer preview; hashes and hosted Windows results are in the publication record |
| Forever 1.60.1.70338 / interface 16001 | Limited user-reported diagnostic, level and clock-age flows; other bindings and full live acceptance remain unverified |
| Reference atlas 1.60.1.70205 | Historical content identity; imagery rights incomplete and local pack distribution-ineligible |
| Forever 1.60.1.70374 / interface 16001 | Frozen v1 target; source-identified development capture/turn-in checks, with full acceptance still unverified |
| Forever 1.60.1.70425 / interface 16001 | Development capture only, UNVERIFIED: installation metadata, no addon-run evidence; never the 1.0 target |
| Forever 1.60.1.70450 / interface 16001 | Current source only (after 0.9.2): development capture, UNVERIFIED; installation metadata and owner-reported interface, no addon-run evidence; never the 1.0 target |
Current source includes a bounded QuestieDB raw-table staging adapter and versioned release checks. Staging preserves partial facts and reports unsupported corrections. The pinned source audit accepts neither QuestieDB nor historical CMaNGOS for shipped assets (CMaNGOS classic-db is now admitted for the data generators, ADR 0006 §14). Unknown content inventory, source rights, real class/role models and live/Windows acceptance continue to block v1.0.0.
Claude Code 1.0.0 execution prompt — detailed continuation steps and release gates.
Repository identity gallery — planned after the verified 1.0.0 release.
Read AGENTS.md, STATUS, the latest relevant handoff, and the implementation plan before changing code. DOMAIN describes types and boundaries; exchange contracts describe the bounded data formats.
SQLite character-snapshot storage and import ordering; bounded ANAV1/SavedVariables parsing; optional watcher for one selected file; Today/Imports/Atlas screens; reference pin search/layers/keyboard navigation; travel, eligibility, clustering and bounded planning; Gear/acquisition comparisons; local parties and guarded joint plan export; reminders and local proposals; Sessions history/analytics; content revisions with activation/rollback and local review dispositions; database backup/recovery; Settings and a read-only desktop reference window. The addon has guarded manual capture, bounded plan import, runtime HUD controls and opt-in manual session recording. Rust/Lua synthetic tests cover predicate and gear parity.
Playable catalogs, documented real class/role models and complete duo/session acceptance remain prerequisites. Party messaging, combat-log analysis, official API access and hosted distribution remain explicitly deferred or blocked. See the task ledger for individual dispositions.
The source pipeline rebuilds a uniform,
provenance-bearing knowledge catalog offline from retained licensed inputs.
After provisioning the Rust toolchain/dependencies, run
./scripts/Build-SourceKnowledge.ps1 in PowerShell 7. Reliability ranks before
trusted freshness; different builds and unresolved coverage remain explicit.
This research catalog does not establish complete Forever content.
Use the pinned Rust toolchain, Node version and pnpm version in the repository.
On Linux, source ~/.cargo/env if Cargo is not on PATH (adapt for your
installation). The native Linux shell additionally needs Tauri GTK/WebKit packages;
the portable checks exclude that shell. Hosted CI compiles it on Windows.
cargo fmt --all --check
cargo clippy --locked --workspace --all-targets --exclude azeroth-desktop -- -D warnings
cargo test --locked --workspace --exclude azeroth-desktop
cargo run --locked -p azeroth-cli -- validate-fixtures
cargo run --locked -p azeroth-cli -- validate-content --input content/forever --json
cargo run --locked -p azeroth-cli -- export-schemas --output schemas/v1
pnpm install --frozen-lockfile
pnpm contracts:types
pnpm contracts:check
pnpm --dir apps/desktop typecheck
pnpm --dir apps/desktop lint
pnpm --dir apps/desktop test:unit
pnpm --dir apps/desktop build
pnpm --dir apps/desktop exec playwright install chromium
pnpm --dir apps/desktop test:e2eThe browser tests mock command adapters and verify UI behavior. For the labelled
browser demo run pnpm --dir apps/desktop dev; for the native shell run
pnpm --dir apps/desktop tauri dev with platform prerequisites installed.
Native Rust checks are cargo clippy --locked -p azeroth-desktop --all-targets -- -D warnings
and cargo test --locked -p azeroth-desktop.
The CLI accepts doctor, export-schemas, prepare-atlas, validate-fixtures,
validate-content, build-content, verify-pack, release-readiness,
stage-questiedb and bounded synthetic
replay --fixture <file>. Replay format/examples/limits are documented in
PLANNER_REPLAY.md.
The local-data workflow inspects explicitly selected
installations and extracts supported local archive tables into private research
catalogs. Compatibility > Local Data provides resource review, progress/cancellation
and paginated inventory inspection. Research decoding does not establish playable
availability; gameplay projections and the full private-release redesign remain
unfinished. localdata.md records the complete implementation contract.
cargo run --locked -p azeroth-cli -- doctor --json reports this binary's version,
OS/architecture, pinned development requirements and tool presence on PATH. Presence
is not runtime-version verification, and missing development tools do not prevent
using the packaged desktop. Optional --saved-variables <file>, --addons <dir>
and --content <dir> inspect only explicitly selected path kinds. Unselected paths
stay unselected; invalid selections return a nonzero exit code. The command does
not read their contents, scan account directories, run detected tools, or print
selected paths. Native prerequisites and live-client compatibility remain unverified.
Content validation has bounded regular-file/directory discovery, deterministic
JSON/human reports and separate nonfatal gaps. See coverage.
Content packs require a typed sources.json sidecar and registered evidence/image
sources. They preserve exact dataset identities and verified PNG bytes, refuse
overwrite, and report declared distribution eligibility separately from gaps.
See local reference pack format. Real Forever content
has a typed registry and can be built and verified as a local_reference pack in
0.9.2, but its recorded source rights remain incomplete and
distribution_eligible=false. It is not a release asset or a playable-content pack.
scripts\windows\Build-Windows.ps1 builds the per-user NSIS installer and the addon
package on Windows; the Windows package workflow builds, smoke-installs and uploads
them, and drafts (never publishes) a GitHub release for a version tag. Installing,
updating and removing the application and addon:
WINDOWS_INSTALL.md.
The full-content v1 publication gates and required content/source assets are in the
v1 release process.
Code signing policy: free code signing provided by SignPath.io, certificate by SignPath Foundation, once the project's application is approved; until then installers are unsigned. Roles, privacy statement and setup: CODE_SIGNING.md.
Owner-supplied imagery under content/forever/atlas/ uses Git LFS and separate
usage terms in its NOTICE; it is not covered by the repository BSD-3-Clause license.
See sources. CI keeps committed LFS pointers and never
fetches imagery. Its pointer check is:
cargo run --locked -p azeroth-cli -- prepare-atlas --manifest content/forever/atlas/eastern-kingdoms/atlas.manifest.json --content-root content/forever --check-pointerThis command deliberately fails on materialized images. To prepare owner-supplied
imagery, omit --check-pointer. Do not commit personal exports or secrets.
Generated world data under data-generators/ comes from Wowhead, CMaNGOS
classic-db and wago.tools (Blizzard Entertainment client data), produced by data
generators based on work by NotInTheBand (TALOD), used with permission. Credits,
licences and terms are in data-generators/NOTICE.md;
the admission decision is ADR 0006 §14 and the
format is WORLD_DATA.md. Navzeroth is not endorsed by
TALOD, Wowhead, CMaNGOS, wago.tools or Blizzard Entertainment.
CI checks Rust formatting, locked Rust and frozen pnpm/contracts on Linux/Windows,
Lua static/parity checks, explicit fixture/content validation, native Windows shell
compilation and mocked Chromium desktop workflows. Cache hits never skip checks.
PR CI targets main; stacked branches can dispatch ci.yml explicitly. Hand-offs
record actual local/hosted checks, checked revisions, reviews and limitations.
CI itself produces no release; native packages come from the Windows package workflow.