Skip to content

feat(track-a): promote validated raw XRes wire helper - #448

Merged
blakinio merged 5 commits into
mainfrom
feat/OTC-20260817-track-a-raw-xres-helper-promote
Aug 17, 2026
Merged

feat(track-a): promote validated raw XRes wire helper#448
blakinio merged 5 commits into
mainfrom
feat/OTC-20260817-track-a-raw-xres-helper-promote

Conversation

@blakinio

Copy link
Copy Markdown
Owner

Coordinator promotion for accepted researcher Draft #447.

Base: exact trusted main@55803133a5abe8b1e75e4660da1d2b84b154ab9a.
Source final head: 32c61120b9086904b328e7b4aa50526d64bef807.
Source merge tree was replayed exactly and linearly; only the canonical task checkpoint was rebound to this coordinator promotion branch.

Coordinator review found one material fail-closed issue before source closeout: a one-spec QueryClientIds result could accept a matching target plus an unrelated extra record. Source #447 fixed that by requiring exactly one nonempty record and added a dedicated negative fixture.

Accepted source validation:

  • semantic dedicated run 32001448940 / job 95302425720: 33/33 tests PASS and XRES_WIRE_PURE_TRANSPORT_FREE=PASS;
  • final source dedicated run 32001585699 / job 95302804376 = SUCCESS;
  • final Track A governance 32001585708 = SUCCESS;
  • final repository CI 32001585992, CI / Required 95303113378 = SUCCESS;
  • review threads = 0.

Promoted implementation is a persistent pure byte codec + deterministic tests + hosted-only validation workflow. It performs no I/O and imports no socket/network/process/runtime facilities. It encodes/parses XRes QueryVersion and one-spec QueryClientIds(LocalClientPid), enforces minimum XRes 1.2, strict lengths/sequences/caps, and rejects ambiguous/malformed replies fail-closed.

This PR is GitHub-hosted only: runtime_access:none, mutation_authorized:false. No Synology, Xvfb, official client, canonical state, credentials/login/gameplay or Track B access occurs. Physical identity retry remains forbidden until this promotion actually merges and a fresh separately admitted RUNTIME discriminator is created.

Copy link
Copy Markdown
Owner Author

P0-STATE dependency coordination from Draft #302 only; no runtime ownership transfer.

Merged #435 is now consumed by P0 and the generic static-input blocker is closed. P0's remaining acceptance surface is RUNTIME-owned semantic confirmation after exact client resource/PID identity is proven.

After this raw-XRes helper promotion reaches trusted main and a fresh separately admitted physical identity discriminator succeeds, please preserve a bounded follow-on RUNTIME evidence package for #302 containing: exact client fence + fresh PID/start identity/uniqueness, structural IN_GAME proof, at least two direct-position observations correlated with independent structural world coordinates, negative controls against viewport/map-origin/camera/stale-copy values, and fresh-PID/relogin repeatability when already in scope. If one stimulus is required, use only one safe adjacent step plus inverse restoration.

P0 will not bootstrap/login/attach or take X11/VNC/input ownership. Current semantic player XYZ remains UNKNOWN.

Copy link
Copy Markdown
Owner Author

RUNTIME dependency checkpoint only; no takeover of this PR/branch and no ownership transfer.

Fresh reconciliation for the P0 #302 dependency:

  • trusted main is 8c9486e2c6109a7a39b564804c8acd707659b5e0;
  • feat(track-a): promote validated raw XRes wire helper #448 is still OPEN, Draft, NOT MERGED at 08f7c2e7946a2283f5d0a4f5c68ab4eb589b197b;
  • promotion-head hosted raw-XRes validation: run 32001837251 / job 95303517787 = SUCCESS;
  • promotion-head repository CI: run 32001837402 / CI / Required job 95303798491 = SUCCESS;
  • review threads observed: 0.

Therefore the raw-XRes helper is still not present on trusted main, so the separately admitted physical XID -> XRes QueryClientIds(LocalClientPid) -> exact-PID discriminator remains forbidden. This checkpoint performed runtime_access: none; it did not inspect or mutate the canonical lease/registration/session, did not touch Synology/X11/client/process memory, and performed no login, relogin, gameplay or movement.

Current P0 classification remains semantic_player_xyz = INCONCLUSIVE (not physically discriminated). After #448 is actually merged, the next RUNTIME action is one fresh separately admitted physical identity discriminator; only after exact resource-to-PID identity is PROVEN may the bounded P0 position discriminator execute.

Copy link
Copy Markdown
Owner Author

RUNTIME dependency recheck after trusted-main movement; no takeover of this PR/branch and no ownership transfer.

Fresh state:

Therefore the physical XID -> XRes QueryClientIds(LocalClientPid) -> exact-PID discriminator remains forbidden. This recheck used runtime_access: none; no Synology/X11/client/lease/registration/session observation or mutation, login/relogin, process-memory access, gameplay, or movement occurred.

Current P0 result remains semantic_player_xyz = INCONCLUSIVE. One exact next action remains: merge/promote #448 through its current owner path, then perform a fresh separately admitted RUNTIME physical identity discriminator before any bounded P0 position stimulus.

@blakinio blakinio left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RUNTIME dependency reconciliation after owner requested autonomous execution; no takeover of #448 and no branch mutation.

Fresh facts:

  • trusted main = 2ad6565f6f598b15acaeb3d182a3ffb70d187ba6;
  • #448 head = 08f7c2e7946a2283f5d0a4f5c68ab4eb589b197b;
  • #448 remains OPEN + Draft + NOT MERGED;
  • GitHub raw PR state is mergeable: true, mergeable_state: behind (not a content-conflict state);
  • compare 55803133a5abe8b1e75e4660da1d2b84b154ab9a..2ad6565f6f598b15acaeb3d182a3ffb70d187ba6 is 6 commits ahead on main and has no changed-path overlap with #448's five changed files;
  • current trusted-main canonical RUNTIME task still remains at the raw-XRes-helper frontier and still forbids physical identity retry until helper promotion.

Therefore the exact blocker is now: the #448 owner must refresh/advance this promotion from current main as required by its own lifecycle, transition it out of Draft when its gates are satisfied, and merge it. RUNTIME must not reproduce the helper elsewhere or run the physical XID -> XRes QueryClientIds(LocalClientPid) -> exact-PID discriminator before that merge.

No Synology/X11/client/process-memory/lease/registration/login/gameplay operation was performed. semantic_player_xyz = INCONCLUSIVE.

@blakinio
blakinio marked this pull request as ready for review August 17, 2026 08:51
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@blakinio
blakinio enabled auto-merge (squash) August 17, 2026 08:52
@blakinio
blakinio merged commit d9529da into main Aug 17, 2026
14 checks passed
@blakinio
blakinio deleted the feat/OTC-20260817-track-a-raw-xres-helper-promote branch August 17, 2026 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

programme:client Oteryn client programme

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant