research(track-a): determine server-delivered worldmap extent - #473
Merged
blakinio merged 16 commits intoAug 17, 2026
Merged
Conversation
blakinio
marked this pull request as ready for review
August 17, 2026 11:12
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
blakinio
deleted the
research/OTC-20260817-track-a-worldmap-server-delivery-extent
branch
August 17, 2026 11:14
blakinio
added a commit
that referenced
this pull request
Aug 17, 2026
Move the completed server-delivered worldmap extent task from active to archive after #473 merged with exact-head CI/governance success and audit PASS.
This was referenced Aug 17, 2026
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.
Objective
Resolve the server-delivered-map-extent acceptance added to
OTCLIENT-TIBIA-RE-WORLDMAP-MUTATION-DESIGNv1.1.0 without repeating completed mutation-design/runtime predecessors.Static result
These are direct evidence-bounded results, not claims of impossibility. Exact-client evidence proves normal gameplay map payload families are server->client, while the complete 160-name client->server generated-message census contains no separately named aware/range/extent/viewport/fullmap/fielddata/width/height message. Exact generic outbound field semantics were not recovered, so the control model remains
UNKNOWN.Evidence
15.32.df7b29, size51965216, SHA-256e6c244bd39fe2e0632f6f000efd3147164696efa8e901718668e0442325ff7fe;32022209943, job95364071999, artifact9285763750— 349 generated names, 160 client->server, 189 server->client;32022973229, job95366330613, artifact9286040543— exactCoordinate{x,y,z:uint32}recovered; targetExtent/generic outbound/map-delivery descriptors not recovered;MATERIAL_FINDINGS=0, one stale-checkpoint finding resolved before audit.Durable report:
docs/agents/reports/OTCLIENT-20260817-worldmap-server-delivery-extent.md.Task:
docs/agents/tasks/active/OTC-20260817-track-a-worldmap-server-delivery-extent.md.Runtime discriminator
The report defines one separately authorized causal physical experiment comparing the exact baseline against the already-designed first
[19,14]mutation while measuring authoritative inbound map envelope before Storage, outbound generic-message serialization, and Storage/render/picker separately. This PR does not execute that experiment.Safety / cleanup
EXECUTION_CLASS=github_hosted,RUNTIME_ACCESS=none. No official-client byte mutation, no login/runtime/Synology fallback, no owner-funded Codex/OpenAI API/paid AI quota, no third-party OTClient behavior promoted as official-server proof, and no raw proprietary client bytes committed. The temporary branch-only evidence workflow was removed before closeout.Base:
main@f99ec371bafd0b9dbccb8fd6f4c8a3137e7d963b.