Skip to content

Sync accepted task lifecycle to TarkovTracker - #216

Draft
joshsmithxrm wants to merge 5 commits into
the-hideout:masterfrom
joshsmithxrm:reeve/dispatch-tm-active-20260812-1708-b1e6
Draft

Sync accepted task lifecycle to TarkovTracker#216
joshsmithxrm wants to merge 5 commits into
the-hideout:masterfrom
joshsmithxrm:reeve/dispatch-tm-active-20260812-1708-b1e6

Conversation

@joshsmithxrm

Copy link
Copy Markdown

Summary

  • forward ordinary task-start events as explicit active Tracker writes
  • preserve deterministic lifecycle ordering and coalesce historical replay safely
  • bind writes to the validated profile, mode, token, and endpoint generation
  • prevent superseded token or endpoint state from authorizing later writes
  • add a focused lifecycle/safety harness and run it in build workflows

Why

TarkovMonitor already detects task-start events, but the current integration cannot persist ordinary acceptance distinctly. Once TarkovTracker supports explicit active state, Monitor should forward starts without falling back to ambiguous uncompleted writes.

Historical replay also needs deterministic ordering and coalescing so a replay cannot produce the wrong terminal state or unnecessary API writes.

Dependency

This draft depends on the additive Tracker lifecycle contract proposed in tarkovtracker-org/TarkovTracker#715. It must not deploy before that API support is available; unsupported servers receive no ambiguous fallback write.

Safety and compatibility

  • validates supported mode-specific .org tokens before writes
  • keeps profile/mode isolation across live and historical events
  • binds authorization to the validated endpoint generation and exact client
  • invalidates pending writes on token/profile/endpoint replacement
  • serializes and generation-checks token persistence so stale settings cannot return after restart
  • retains existing completed/failed synchronization behavior

Validation

  • focused lifecycle, deduplication, ordering, replay, mode-isolation, compatibility, and authorization tests
  • deterministic token/profile/endpoint concurrency coverage
  • stale and in-flight token-persistence ordering coverage, including restart reconstruction
  • git diff --check

The focused harness passes locally. The complete application build still needs CI confirmation because the development environment did not have the repository-pinned .NET SDK and dependency restore available.

Invalidate pending profile validation when tokens change, bind write authorization to the tracker endpoint generation, and add regression coverage for token replacement and endpoint redirection.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant