docs(track-a): preserve official-client viewport feasibility research

[blakinio]

Objective

Persist the 2026-08-16 exact-client investigation into whether the official native Linux Tibia client can load/render a larger world-map tile area than the currently observed geometry.

Scope

Documentation/evidence only. No client binary mutation, live runtime access, credentials, proprietary assets, workflow changes, Track B changes, or owner-funded AI/API use.

Evidence boundary

• exact researched client: 15.32.df7b29, size 51965216, SHA-256 e6c244bd39fe2e0632f6f000efd3147164696efa8e901718668e0442325ff7fe;
• static exact-binary run 31892019505, artifact 9248797952, digest sha256:04835ab0bac7ffc43e161e8b2118c90a3d2197f7011385a6758cd7706c93a584;
• historical reversible structural-movement run 31806312967, job 94785974126, artifact 9221332209, digest sha256:bd4be5b2f9d6cebf19fff6bdfa3677ad57c00ae4a376987f32b42e8a27907a4a.

The report preserves exact static evidence for TWorldMapExtent, TWorldMapSubfieldExtent, TWorldMapStorage, TWorldMapViewport, TWorldMapCamera, TWorldmapProtocolMessageHandler, TWorldMapRenderProvider, onCameraViewportChanged and TMapScaleFactor.

Claim boundary

The result is feasibility evidence, not an implemented patch. Larger map load/render is classified as a high-confidence derived research direction. Exact fields/patch sites, fixed allocations, parser/server awareness constraints, maximum safe dimensions and concrete 26x20/32x24/36x28 support remain UNKNOWN/NOT_PROVEN.

The observed 18x14 interpretation is explicitly classified as DERIVED_FROM_OBSERVED_JOB_LOG because the downloadable historical movement artifact retains XWD frames but not the raw TSV/job-log rows.

Runtime boundary

runtime_access: none
mutation_authorized: false

Authority comes from the trusted main governance. This PR does not consume pending PR #324 as authority and does not touch PR #300 coordinator-owned paths, PR #303 runtime surfaces or PR #324 governance paths.

Audit / E2E

Fresh validator-role review of the exact diff and primary GitHub evidence found one material checkpoint issue (OTC325-AUD-001): the initial task record used non-canonical v2 delivery fields and referenced pending PR #324 too strongly. It is fixed in the current branch; no material research finding changed.

E2E: NOT_APPLICABLE — documentation/evidence-only checkpoint; no executable or user-facing runtime behavior changed.

No review threads, requested changes, duplicate task PRs, secrets, proprietary client bytes or private captures were found.

Validation

Required repository CI must pass on the final exact head before merge. Post-merge archival/ownership release remains part of this same task per repository closeout policy.

Task: OTC-20260816-official-client-map-viewport-feasibility.

[chatgpt-codex-connector]

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]

Coordinator disposition: CLOSED_SUPERSEDED / NO MERGE.

The research content is accepted and preserved byte-for-byte in fresh-current-main replacement PR #365. This old branch predates the mandatory post-PR-331 Track A hybrid routing/admission fields, so it is not promoted directly from its stale base. Replacement #365 reuses exact report/evidence blob SHAs and changes only task governance/lifecycle metadata.

No research finding is rejected by this supersession; claim strength remains unchanged.