Skip to content

Releases: Laymer/Navzeroth

Azeroth Navigator 1.0.0-rc.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 11:36
fcf48ea

Azeroth Navigator 1.0.0-rc.1 — development prerelease

This is an unsigned development prerelease, not a stable release or an
acceptance candidate. The rc.1 name does not establish playable-content
completeness, live-client acceptance or ordinary-Windows acceptance. Candidate
and stable readiness remain false. Stable 1.0.0 publication is outside this release.

Included capabilities

The Windows desktop imports bounded addon snapshots and sessions, preserves their
exact edition/build identity, and exposes the Planner, Atlas, Gear, Party,
Dungeons, Sessions and recovery workflows. Demonstrations and automated tests use
labelled synthetic fixtures; they are not evidence that those workflows have
complete verified game content.

Local research now has durable preparation, cancellation and unchanged-source
resume; explicit locale/resource choices; optional selected-installation metadata
change detection; bounded cache/addon/guide input staging; revision-bound local
media previews; provenance-aware gameplay fact and tooltip research; and explicit
research-reference selection, comparison and rollback. Imported Lua is inert data.
Unknown, unsupported, restricted, stale, false and zero remain distinct.
Research references never authorize playable advice. There is no live desktop
bridge, game memory access, packet decoding or input automation.

The addon offers manual capture/export, plan import/HUD controls and manual
session recording inside the permitted addon environment. Desktop state is an
imported snapshot, not live game state. Admission of an API or build is not proof
that a field is readable in every context.

This continuation also repairs concurrent private lifecycle-index initialization and migration, atomically
reserves test directories, bounds native startup readiness, preserves sanitized
IPC error codes, and verifies SemVer upgrade ordering. The strict 90% executable
line gate applies to each Rust and TS/TSX file, including native aggregation and
missing-file detection.

Exact development support and evidence

Component Admitted tuple Evidence boundary
Experimental addon Forever 1.60.1 / 70338 / 16001 Historical limited operator observations; no current-release acceptance claim.
Experimental addon Forever 1.60.1 / 70374 / 16001 Recorded development capture/session observations remain revision-scoped, not RC acceptance.
Experimental addon Forever 1.60.1 / 70425 / 16001 and 1.60.1 / 70450 / 16001 Development admission only; no recorded live-addon acceptance on these builds.
Local extraction wow_classic_beta, version 1.60.1, builds 70374, 70425, 70450 Exact metadata and supported layouts only; unsupported tables/locales remain explicit. Private static research receipts do not prove playable content.

Neighbouring builds are not silently admitted. Existing 70425/70450 extraction
and cache receipts are retained without reopening game files. Hosted Windows
installation, native IPC/picker, upgrade and downgrade-refusal checks are synthetic
regression evidence. They do not substitute for an operator on ordinary Windows
hardware or a recorded live client.

Under ADR 0006, the stable target is the first verified stable live build after
launch. Historical 70374 target labels do not freeze that future target. The planned
Human levels 1–20 slice still needs its launch class list, complete independently
reviewed content, permissions, models and candidate-bound live/Windows evidence.
Ordinary-Windows performance, content permissions, launch-target evidence and live
acceptance remain explicit gaps. See the version-specific readiness blocker receipt.

Install, upgrade and remove

The release contains exactly these five files:

  • AzerothNavigator-1.0.0-rc.1-x64-setup.exe
  • AzerothNavigator-addon-1.0.0-rc.1.zip
  • CANDIDATE_NOTES.md
  • SOURCE_COMMIT.txt
  • SHA256SUMS.txt

No playable content pack, private client files, exports, caches, catalogs, guides
or extracted images are included. Dependency notices and retained dependency
sources are bundled with the application; an empty release-material selection
produces no material ZIP or material manifests.

Download only from the project's verified release page. In PowerShell, compare
Get-FileHash .\AzerothNavigator-1.0.0-rc.1-x64-setup.exe -Algorithm SHA256 and
Get-FileHash .\AzerothNavigator-addon-1.0.0-rc.1.zip -Algorithm SHA256 with their
exact entries in SHA256SUMS.txt. The manifest covers the four payload files;
matching hashes verify integrity, not publisher identity.

The installer and application are unsigned: no Authenticode publisher identity
is claimed. SmartScreen may warn. Stable-release signing requirements remain in
force. The per-user installer targets %LOCALAPPDATA%\Azeroth Navigator; missing
WebView2 may require Microsoft's runtime bootstrapper and network access.

Before upgrading from 0.9.2, use Backup and recovery → Create consistent backup
and retain the private backup outside the installation and application-data folders.
Then close the application. Install the RC over it and inspect the imported data and
research selections. Older writers refuse newer private-index schemas; do not
bypass downgrade refusal or overwrite a database to force an old executable to run.

Close WoW before addon changes. Back up the existing addon and SavedVariables,
then extract the ZIP's AzerothNavigator folder into the actual client's
Interface\AddOns directory. The optional addon helper requires explicit folder
selection and retains ownership/running-game checks. Never send personal exports
to the repository.

Remove the desktop through Windows Installed apps. Retained application data and
backups are separate from the executable; delete them only if you intend to lose
that state. Remove only the owned addon folder with WoW closed; SavedVariables
removal is a separate, explicit choice. See the Windows and
addon guides for detailed paths and preservation behaviour.

Retained evidence

The private extraction lifecycle receipt
and cache development receipt
remain revision-scoped; no game files were reopened for this release. The
synthetic WSL performance report retains its
original source, samples and platform. It is not an RC measurement on ordinary
Windows hardware. The release handoff
records actual verification and publication state.

Azeroth Navigator 0.9.2

Pre-release

Choose a tag to compare

@github-actions github-actions released this 17 Oct 11:34
3b19812

Navzeroth 0.9.2 — in-game addon window and desktop redesign

Developer prerelease for Windows. Version 0.9.2 follows the published 0.9.1 local-data
research preview. It adds an in-game addon window, a redesigned desktop interface and
much stronger end-to-end and native Windows regression checks. It is not complete
playable content and not a 1.0.0 candidate.

Changes since published 0.9.1

  • In-game addon window. /anav opens one window that exposes the addon features
    through buttons and fields, with a tooltip on every control. A minimap button and an
    Options > AddOns page open the same window. The window adds no event, timer, reload,
    clipboard access or socket bridge; observations stay inside the permitted addon
    environment and desktop state remains imported snapshots. Three window keys were
    added to the saved settings without changing db_version; a 0.9.1 addon drops them
    when it next merges the table. See the addon window guide.
  • Build 70425 development admission, UNVERIFIED. The addon adapters admit
    1.60.1.70425 / interface 16001 for development capture only, because the owner's
    installation metadata reports it. No addon run on that build is recorded. The release
    target stays Forever 1.60.1 / 70374 / interface 16001 and every live acceptance row
    stays bound to 70374. See build capabilities.
  • WoW-inspired desktop redesign. A new design system (tokens, shared primitives,
    contextual help tips, themed #reference page) and a two-group application shell.
    Every screen moved onto it. It bundles unmodified Inter (4.1) and Cinzel with their
    SIL OFL notices; see apps/desktop/THIRD_PARTY.md. Default, high-contrast and
    forced-colours modes have tested contrast pairs, including a composite bound over
    the backdrop. The interface is original and not affiliated with Blizzard Entertainment.
  • Original-art backdrop. An inline SVG backdrop drawn for this project; no game
    art is used.
  • Settings refresh fix. The 60-second refresh no longer unmounts the Settings form
    and discards unsaved edits; a dirty draft is kept against the revision it was made
    from, so saving over a changed store still fails the revision check.
  • End-to-end harness. A Rust harness runs the full addon on builds 70374 and 70338
    through capture, export, desktop import, plan binding and refusal cases, and checks
    that the desktop command map equals the registered Tauri handlers.
  • Native Windows smoke and upgrade checks. The hosted package job drives the
    installed app through real WebView2 and Tauri IPC and upgrades from the published
    0.9.1 setup. These are hosted-runner regression checks only.

Downloads

Download AzerothNavigator-0.9.2-x64-setup.exe, AzerothNavigator-addon-0.9.2.zip,
CANDIDATE_NOTES.md, SOURCE_COMMIT.txt and SHA256SUMS.txt. Verify the checksum
entries before installation. Follow the repository Windows and addon installation
guides; close WoW and keep private backups before updating the addon. The installer
is unsigned.

Limits and remaining work

Unverified for this release:

  • WebView2 visuals of the redesign (checked in Chromium, not by eye on Windows).
  • Screen-reader behaviour of the help tips and live announcements.
  • The addon window, minimap button, taint and keyboard focus on a live client.
  • The unsigned installer under Windows SmartScreen.
  • Anything on build 70425 beyond its recorded installation metadata.

Stable readiness is unchanged: stable and candidate readiness remain false, with the
blockers release-readiness reports (66, the same count as at 0.9.1; see the
0.9.2 release handoff). Preview
publication is permitted and is distinct from stable readiness. No playable content
pack, private client data or catalogs are included. Local-data output remains
research-only. Complete licensed content, independent inventories, objective and
advancement bindings and frozen-candidate live and interactive Windows acceptance
remain required for 1.0.0.

Azeroth Navigator 0.9.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Oct 11:58
92f3f51

Navzeroth 0.9.1 — private local-data research preview

Developer prerelease for Windows. Version 0.9.1 includes the prepared 0.9.0
foundations and the subsequently merged private local-data workflow. Version
0.9.0 was not published; this release supersedes that interrupted publication.

Changes since published 0.8.1

  • Content v2 contracts, typed model/dungeon/acquisition/eligibility consumers,
    bounded catalogs, indexing, pagination and compatible storage foundations.
  • Retained offline source builds with provenance and cross-platform parity.
    The admitted scopes provide 1,685 reference facts, with zero verified
    target-usable gameplay facts; all nine 70374 inventories remain unknown.
  • Experimental 70374 addon support, copyable exports, guarded quest-completion
    reads and manual quest-turn-in session recording. Desktop state remains
    imported snapshots; observations remain inside the permitted addon.
  • Private local installation inspection, read-only local CASC extraction,
    isolated resource-limited workers, bounded WDC research decoding and immutable
    private catalogs. CLI verification/coverage and desktop inventory controls
    preserve missing, unsupported, invalid and unknown dispositions.
  • Pinned native/parser sources, metadata and third-party notices are retained.
    Private game files, extracted tables and catalogs are not release assets.

Downloads

Download AzerothNavigator-0.9.1-x64-setup.exe,
AzerothNavigator-addon-0.9.1.zip, CANDIDATE_NOTES.md, SOURCE_COMMIT.txt and
SHA256SUMS.txt. Verify all four checksum entries before installation.
Follow the repository Windows/addon installation guides; close WoW and retain
private backups before updating the addon.

Limits and remaining work

This is a developer preview, not complete playable content or 1.0.0 acceptance.
Local-data output is research-only and does not activate gameplay content.
The measured development extraction used 70425/enUS; it is not 70374 content
or acceptance. Cache/hotfix/media support, gameplay projections, durable jobs,
settings and full private-inventory release integration remain unfinished.
See docs/data/LOCAL_EXTRACTION.md for supported commands and explicit gaps.

The full target remains Forever 1.60.1 / 70374 / interface 16001. Complete licensed
content, independent inventories, objective/advancement bindings and frozen-candidate
live/interactive Windows acceptance remain required. Hosted packaging smoke tests
and synthetic tests do not establish operator acceptance. No playable content pack
or private client data is included. Existing stable-release gates are unchanged.

Release verification

Source commit: 92f3f512a68481163e3d44600e3938d07592af4e. All PR and resulting-main CI, Windows packaging and source-parity checks passed. The tag workflow passed installation, first-start and uninstall smoke tests. All five draft downloads match the verified tag artifacts; checksums, source marker, notes and all 21 addon files were verified.

Verification record · Tag packaging.

Azeroth Navigator 0.8.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 18:02
d11853e

Azeroth Navigator 0.8.1 — local content-pack repair preview

Developer prerelease for Windows. Desktop data remains imported snapshot state;
permitted game observations remain inside the informational Lua addon.

Changes

  • Local content-pack parsing accepts the schema1 typed explicit empty
    payload.map_embeddings array as equivalent to its omitted default. The exception
    changes only comparison shape after validation; unknown/duplicate/future/malformed
    fields remain refused and original input bytes stay unchanged.
  • Existing Forever sources now have a typed schema1 registry sidecar derived from
    recorded source declarations. Unknown licenses/revisions and date-only retrieval
    times remain unknown; the owner's composite-only assertion remains conditional
    and does not grant third-party permissions.
  • The existing Forever directory can be built and verified as a local_reference
    pack. It remains distribution-ineligible and is not a release asset. Historical
    reference70205/16001, forever-atlas-r1, producer0.1 and all imagery bytes remain
    unchanged; the registry is the sole intentional content addition.

Assets

AzerothNavigator-0.8.1-x64-setup.exe, AzerothNavigator-addon-0.8.1.zip,
CANDIDATE_NOTES.md, SOURCE_COMMIT.txt and SHA256SUMS.txt. Verify the checksum manifest
and exact source metadata before using these developer artifacts.

Evidence limits and next audit

These repairs establish bounded local preparation behavior, not new redistribution
rights, verified playable records or native/live acceptance. Real catalogs, four
role models, verified Deadmines records, complete comparable sessions, recorded70338
field/event/restriction/plan/HUD/taint evidence and actual party message formats
remain missing or unverified. Native focus/hit-testing/DPI/monitor/installation/
performance acceptance and official Forever endpoint/auth/terms evidence remain
unverified. World expansion stays focused-release/evidence gated; hosting is deferred.
After actual publication, re-audit the released tag before claiming that all ready
engineering is exhausted. External prerequisites remain explicit and unmet.

Azeroth Navigator 0.8.0

Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 16:48
db8530f

Azeroth Navigator 0.8.0 — route and display controls preview

Developer prerelease for Windows. Desktop character data remains imported snapshot
state; game observations remain inside the permitted informational Lua addon.

Changes

  • Route inspection provides keyboard hop selection, complete tail pagination and
    one exact map/floor/instance frame at a time. Fit selected or same-frame route
    endpoints without inventing roads, positions or floor connections. Changed original
    planning provenance invalidates selection and late replies; gaps stay explicit.
  • Explicit addon HUD size/font/contrast/reset commands use bounded local preferences
    and a conservative recorded-build, method and actual boolean combat gate. Deferred
    application refreshes the plan evaluation. Movement is saved only from a successful
    permitted point observation; session-only movement survives routine refreshes.
  • The ordinary reference window has an opt-in focused-main Ctrl+Shift+F8 shortcut
    and explicit requested interactive/pass-through control. Receipts distinguish
    dispatch from actual queried visibility/topmost; no unsupported interaction-mode
    observation is invented. The reference webview remains read-only.
  • Main headings wrap at narrow widths and increased text size, preserving content
    and semantics rather than clipping or reducing the user's chosen font size.

Assets

AzerothNavigator-0.8.0-x64-setup.exe, AzerothNavigator-addon-0.8.0.zip,
CANDIDATE_NOTES.md, SOURCE_COMMIT.txt and SHA256SUMS.txt. Verify the checksum manifest
and exact source metadata before using these developer artifacts.

Evidence limits and next iteration

Synthetic frame/clock/gate checks and command-mocked browser flows establish bounded
engineering behavior, not interactive Windows, screen-reader or gameplay acceptance.
Actual recorded70338 UI restrictions, taint, focus/action-bar interference, movement,
font/contrast readability and reload/display behavior remain unverified. Native
window focus/hit testing, DPI, multiple displays, installation and ordinary hardware
performance remain unverified; exclusive fullscreen is outside the reference-window
experiment. No game input hook or gameplay automation is introduced.

Schemas, storage10 and dataset identities are unchanged. Historical Forever
reference70205/16001, revision forever-atlas-r1 and its0.1 producer remain historical;
they are not relabeled as70338. Real catalogs, role models, source permissions,
recorded-client field/event/plan/session checks, actual party message capabilities,
complete sessions and official Forever API support remain missing or unverified.
World expansion stays evidence-gated and remote hosting remains deferred. Reaudit
the actual published source before claiming no further ready engineering remains.

The next parallel iteration addresses two audited engineering gaps: local content
pack comparison must accept the typed explicit empty map_embeddings array, and the
existing Forever source declarations need a typed sources.json sidecar. These tasks
preserve schema1 and recorded source policies; unknown redistribution rights remain
blocked. This preview does not claim that all ready implementation work is exhausted.

Azeroth Navigator 0.7.0

Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 15:14
035f28e

Azeroth Navigator 0.7.0 — local intent and content governance preview

Developer prerelease for Windows. Desktop character data remains imported snapshot
state; game observations remain inside the permitted informational Lua addon.

Changes

  • Today and Settings persist bounded explicit local choices and accessibility
    preferences. Pin successful server-owned planning jobs without consuming reports;
    stale or restored advice is clearly historical. Saved export-file choices fill
    Imports inputs only after an explicit click.
  • Durable quarantine/revocation blocks activation and safely falls back to a
    validated previously activated eligible revision or clears active content.
  • Opted-in local observation review supports CAS decisions, withdrawal tombstones
    and terminal revocation. Accepted-record local export requires current declared
    field/transformation permissions; local acceptance grants no source rights or
    confidence and performs no upload.
  • Gear and route acquisition views show exact fixed-point contributions, model
    assumptions, eligibility gaps and bounded traces with readable typed reasons.
  • Schema 10 preserves registered 256-byte source identities. Typed backup recovery
    retains settings, queue states and revision counters; restored plan references
    cannot authenticate their own locally guarded publication.

Assets

AzerothNavigator-0.7.0-x64-setup.exe, AzerothNavigator-addon-0.7.0.zip,
CANDIDATE_NOTES.md, SOURCE_COMMIT.txt and SHA256SUMS.txt. Verify the checksum manifest
and exact source metadata before using these developer artifacts.

Evidence limits and next iteration

Portable/native compilation, synthetic models and mocked browser checks do not
establish gameplay or interactive Windows acceptance. Real catalogs, role models,
source permissions, recorded-client field/event/combat checks, actual party message
capabilities, complete sessions and official Forever API support remain missing or
unverified. Native focus, display, installation and performance acceptance remain
unverified. Historical reference 70205 data is not relabeled as client 70338.

The next parallel engineering batch addresses route-segment selection/fit controls,
HUD resize/font/contrast preferences and optional focused-desktop reference shortcut
and interaction controls. World expansion stays gated by focused-release evidence;
remote hosting remains deferred under the approved local-first scope.

Azeroth Navigator 0.6.0

Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 12:49
739a822

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.

Azeroth Navigator 0.5.0 — hardening developer preview

Choose a tag to compare

@github-actions github-actions released this 14 Oct 10:42
f525911

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.

Azeroth Navigator 0.4.0

Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 07:17
2d5de64

Azeroth Navigator 0.4.0 — joint guidance developer preview

Windows x64 developer prerelease. This increment adds local guidance workflows;
full focused-release and recorded-client acceptance remain incomplete. This is
not a claim that real quest, item, route or Deadmines coverage is available.

Changes since 0.3.0

  • Manual joint planning checks each participant's imported snapshot, eligibility,
    transport requirements and declared utility. Every selected objective must be
    ready and benefit every member; priority uses the minimum member contribution.
    Hard exclusions, time budget and stopping route remain explicit. Origins,
    objective locations, utilities and durations are operator assumptions.
  • Bounded persisted local proposals require explicit acceptance from every member,
    including the proposer. Compare-and-swap revisions prevent stale replacement or
    lost acceptance. Changes to membership, snapshots, content or freshness invalidate
    agreement and expose per-member imported observation differences. Declarations
    are local operator records, not authenticated remote consent or game messaging.
    Failed reads remain unknown and disable changes until a successful refresh.
  • Reminder inspection has persisted controls, explicit presentation acknowledgment,
    hide/restore and profile preferences. Unchanged outcomes remain deduplicated.
    Real rule delivery requires exact-build verified evidence, no conflicts and a
    matching verified source revision. Missing durability/bag/training inputs remain
    visible gaps. The optional bag checklist records a manual declaration only.
  • Sessions supports explicit comparable-condition annotations and conditional
    estimate comparison. It revalidates retained events against their analytics and
    requires complete observed activity, session start and a terminal matching quest
    turn-in. Gaps, unclassified/inferred time, incompatible contexts and incomplete
    associations are excluded. Median/range/sample counts and a documented-baseline
    blend remain inspectable; estimates are not automatically replaced.

Compatibility and data

Exchange schemas, addon text transports and dataset identities remain unchanged.
Database migrations 6–8 add reminders, calibration annotations and local proposals;
existing snapshots, content, parties and immutable sessions remain preserved.
Use a compatible backup when downgrading to an older database schema. Installation
and removal details remain in docs/compatibility/WINDOWS_INSTALL.md.

The only recorded live build is Forever 1.60.1.70338 / interface 16001. Existing
user reports cover level 12 and limited trusted-age/reload flows. Consolidated
quest/equipment/position/plan/session and restricted-context checks remain unverified.
The reference atlas's 70205 context is not relabeled as compatible with 70338.

No verified playable quest/acquisition catalog, real role weights, party messaging,
joint addon export, Deadmines package or full gameplay acceptance is supplied here.
Current manual recorder output is normally unclassified and therefore does not
qualify as a complete measured calibration sample. Native interaction, multi-monitor
behavior and representative performance remain separate acceptance work.

Release files and verification boundary

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

Publication requires all task PRs to be merged, the exact main revision to pass
hosted CI/Windows packaging, and downloaded tag assets to pass checksum,
source/version and readable addon source/license verification. Actual source-locked
checks, reviews and publication evidence are recorded in the release handoff and
GitHub PR/tag runs; no native/live results are inferred from mocked browser tests.

Azeroth Navigator 0.3.0

Pre-release

Choose a tag to compare

@github-actions github-actions released this 13 Oct 16:52
1924a84

Azeroth Navigator v0.3.0

Windows x64 developer-preview prerelease. Delivers manual addon observations
and plan controls, Gear comparisons, Sessions recording/history and Planner route
inspection. New client bindings remain experimental on Forever 1.60.1.70338 /
interface 16001. Full focused-release and live-game acceptance are incomplete.

Downloads and installation

Downloads:

  • AzerothNavigator-0.3.0-x64-setup.exe — per-user desktop installer with addon/helper.
  • AzerothNavigator-addon-0.3.0.zip — readable Lua addon and BSD-3-Clause license.
  • SHA256SUMS.txt — integrity hashes for the installer, addon, notes and source record.
  • SOURCE_COMMIT.txt — exact packaged source SHA.
  • CANDIDATE_NOTES.md — this version's notes, also included in the checksum list.

Verify hashes before installation. The release assets below are built from tag v0.3.0; CI artifacts have limited
retention. The installer is unsigned unless a signing command
is configured. WebView2 may require a one-time download; installed offline workflows
need no API credentials.

Windows install/update/remove and
addon installation. Back up desktop data and
SavedVariables before upgrading. SQLite upgrades existing v4 stores to v5, retaining
snapshots, content and parties while adding immutable session history. Downgrades to
an older application may require restoring a compatible database backup. Close the
game before updating the addon. Keep personal exports private.

Changes since v0.2.0

  • Bounded, guarded manual quest-log reads capture accepted quests and readable
    completion flags. Headers/malformed IDs are diagnosed; partial or oversized reads
    preserve the previous export. Missing quests do not prove turn-in/history.
  • Manual equipment capture records readable item identity in numeric inventory
    slots. Missing links remain unknown; variants/instances/modifiers stay unknown.
    Position probes diagnose readability without inventing location/map/floor identity.
  • Explicit plan paste/import, show/hide/clear and conservative HUD. Failed replacement
    retains the loaded plan. Expiry, uncertain age, missing dependency checks and
    revalidation remain visible. Plans are runtime-only and reload clears them.
  • Acquisition-aware Gear services and screen: current/theoretical/equip-eligible/
    obtainable comparisons, score explanations and conditional practical estimates.
    Weights, categories, proficiencies, slot relationships and effort are manual.
    Practical results require a complete baseline and evaluate one acquisition-backed
    upgrade at a time. Synthetic examples stay labelled; no real tables are invented.
  • Separate bounded ANAVSESSION1: local transport and immutable session history.
    Exact context/fixture scope, duplicate idempotence, atomic conflict/capacity refusal
    and explicit deletion preserve history. Maximum 128 sessions per profile; no pruning.
  • Explicit opt-in session start/sample/pause/resume/stop/export commands. No background
    sampling. Running spans default to unclassified; pauses are gaps. Monotonic reset
    and bounds stop recording; UTC drift warns/revokes UTC trust while sampling continues.
    Manual stop does not claim game logout. Reload never resumes an old timeline.
  • Sessions screen imports text/selected files and shows coverage, unclassified spans,
    gaps, observed progression and clock uncertainty separately. Same-profile refresh
    now preserves pending import successes/errors and refreshes resulting history.
  • Planner route inspection includes selected legs and the final stopping route.
    Exact-dataset endpoint links are schematic, not road geometry; incompatible spaces
    and missing transforms retain the ordered route with explicit gaps.
  • Changed snapshots/dataset revisions invalidate calculations. Minute refresh preserves
    manual Gear/Planner inputs; superseded responses cannot restore old results.

Manual addon workflow

Choose one anonymous profile ID per character; capture explicitly:

/anavdiag snapshot anonymous-one

Save through reload/logout, then use desktop Imports with global AzerothNavigatorDB
and key snapshot_export. Clock trust requires explicit comparison/confirmation;
reload revokes it. Cached captures retain their original timestamp and are labelled.

Export a compatible desktop plan, run /anavplan paste, paste the text and press
Import. Use /anavplan status, show, hide or clear. Missing authored objective
mappings never complete or advance a step. Capture replacement requires revalidation.

For Sessions:

/anavsession start anonymous-one
/anavsession sample
/anavsession pause
/anavsession resume
/anavsession stop
/anavsession export

Export a stopped recording before reload. Save through reload/logout, then import
session_export from AzerothNavigatorDB under the matching desktop profile.
SavedVariables are parsed as bounded literals, never executed. Failed export retains
previous successful bytes; new recordings get independent runtime identities.

Verification and remaining gates

Baseline 0.3.0-rc.1 has a completed
integration audit.
v0.3.0 passed 550 portable Rust tests (one existing ignored), 90 desktop unit tests
and nine mocked Chromium workflows, plus fmt/Clippy, schema/type/fixture/content
checks and Lua lint. All nine post-merge main checks passed. Tag packaging passed
Windows build/helper, installed-version/license, first-start and uninstall checks.
Downloaded release assets match the verified tag workflow artifacts exactly.
Hosted install/first-start/uninstall smoke and command-mock browser checks remain
separate from native user interaction and actual game behavior.

Earlier user reports cover one correct level 12 import and trusted/uncertain capture
age behavior, under limited recorded conditions. No new live quest, equipment, plan
paste/HUD or session evidence is supplied. Run the
v0.3.0 live checklist on the recorded build.

Real playable content, validated quest-stage mappings, verified road geometry,
joint planning, party messaging, calibration, representative live performance,
interactive native dialogs and bare-machine setup remain unverified or deferred.
No memory access, injection, packet decoding, input automation or addon socket bridge.
External LFS imagery is not packaged; bundled demonstration imagery is synthetic.
The existing Linux GTK transitive advisory remains recorded in STATUS; no dependency
upgrade is part of this release preparation. Schemas/SavedVariables layout remain v1;
local SQLite schema is v5. Missing environment checks are not counted as passed gates.

BSD-3-Clause. License. Report reproducible issues with sanitized
diagnostics.

Published package verification

Tag v0.3.0 identifies commit 1924a844c6878f818c59be6e252419e5d8775825. SOURCE_COMMIT.txt exactly matches
that commit. All four SHA256 entries, ZIP integrity, all 19 addon source files and
entries, root/addon license equality, committed packaged notes and installer PE
framing were verified. The draft release downloads match those verified bytes.

Release preparation and review,
post-merge main CI,
post-merge Windows packaging,
and tag packaging/draft-release workflow.

File SHA256
AzerothNavigator-0.3.0-x64-setup.exe 8df6962fef9c8f83f60e6e99bca9278206133b7ff5fe4e2a8294e48f184d5285
AzerothNavigator-addon-0.3.0.zip ffe287466c59d85146919e35e881b58d73ef11ee2c3b4cccf1dbd4d38b64b533
CANDIDATE_NOTES.md 8dc2b8150f41203e502ec55cb2fcfadd3cd51aea456eedb01de007903bba7051
SOURCE_COMMIT.txt 397a19ee9d1c43c83a963e4af95bc73389bb8fe9b993aacbbb1573db09595a19