Sync accepted task lifecycle to TarkovTracker - #216
Draft
joshsmithxrm wants to merge 5 commits into
Draft
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
activeTracker writesWhy
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
.orgtokens before writesValidation
git diff --checkThe 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.