research(track-a): revalidate current-build auth session structure

[blakinio]

Terminal source disposition — superseded by coordinator promotion #569

Status: CLOSED UNMERGED AS SUPERSEDED.
Task: OTC-20260819-track-a-auth-session-current-build-static
Source head: 411d0e287d08406c682ef063fb3f3f61341d9295.

Coordinator review 4970802493 classified this source ACCEPT_WITH_EDITS with zero open material findings after repair.

Independent coordinator strict audit #568 re-fetched the exact current package and proved the complete QMeta invoke-switch control flow rather than accepting an executable-looking table alone:

audit head 4d377f8088e07e68f3680558212f16e532201f70
strict run 32239540646 = SUCCESS
artifact 9360231314
artifact SHA256 f81ab45076a2f31d7fa9bfc34793009a1a52347e4dd26ad6ce73225e274d12b7

Accepted exact-build facts:

TGameClient::onRequestLoginWithCredentials
  index 17 / METHOD / void(QString,QString) -> 0xd196f0

TGameClient::connectClientToGameserverWithExistingCredentials
  index 11 / METHOD -> 0xd19500

TLoginRequestUploader::loginSuccessful
  index 0 / SIGNAL -> signal activation dispatch target 0xd10200

TCharacterSelectionController::requestCharacterLogin
  index 0 / SIGNAL -> signal activation dispatch target 0xd52050

The two SIGNAL targets are not promoted as call-safe business implementations. Non-QMeta state-machine targets, field/password provenance, live object/thread provenance, helper call safety, login success, IN_GAME, and restart/relogin/session stability remain unresolved.

Source lifecycle text that described #555 as an unmerged Draft was corrected: current trusted fence authority is #555 merge 2e572789a2bc4b64c5e906c4515c15c625f6bc9e plus #561 closeout.

Clean promotion #569 was based on current main, remained behind_by=0, changed six documentation/evidence/archive paths, passed exact-head CI 32239950338, final review 4970837047, and squash-merged as:

fe5f17a3ea4fe9341fa3f4d2720a4186f3b8995d

Temporary audit #568 was closed unmerged as audit-only/consumed. No official-client execution, Synology/KasmVNC observation, credentials, login, process-memory access, GUI input or gameplay occurred during coordinator audit/promotion.

[blakinio]

Coordinator decision: ACCEPT_WITH_EDITS.

Independent strict current-build audit reproduced the exact package and required a full QMeta switch control-flow chain (cmp edx,max -> RIP table LEA -> movsxd [table+rdx*4] -> add base -> indirect jmp). It confirmed TGameClient::onRequestLoginWithCredentials index 17 -> 0xd196f0 and connectClientToGameserverWithExistingCredentials index 11 -> 0xd19500.

Required promotion edits:

1. TLoginRequestUploader::loginSuccessful index 0 / target 0xd10200 is a QMeta SIGNAL dispatch target (SIGNALS=8), not a call-safe business implementation.
2. TCharacterSelectionController::requestCharacterLogin index 0 / target 0xd52050 is likewise a QMeta SIGNAL dispatch target (SIGNALS=10).
3. Source lifecycle text saying #555 remains an independent Draft is stale. Current trusted fence provenance is merged #555 (2e572789a2bc4b64c5e906c4515c15c625f6bc9e) plus #561 closeout.

No live/login/credential/non-QMeta semantics are promoted. Open material findings after these bounded edits: 0.