Skip to content

Azeroth Navigator 0.4.0

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 07:17
· 1513 commits to main since this release
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.