Skip to content

research(track-a): recover world minimap static semantics - #545

Closed
blakinio wants to merge 8 commits into
mainfrom
research/OTC-20260819-track-a-world-minimap-static-g0
Closed

research(track-a): recover world minimap static semantics#545
blakinio wants to merge 8 commits into
mainfrom
research/OTC-20260819-track-a-world-minimap-static-g0

Conversation

@blakinio

@blakinio blakinio commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Terminal source disposition — 2026-08-19

CLOSED UNMERGED AS SUPERSEDED.

This Draft was the bounded source researcher package for TIBIA-RE-WORLD-MINIMAP / OTC-20260819-track-a-world-minimap-static-g0.

Source exact head 55034d31a3cfd55c597f463c97ebf97065192c8b passed:

  • Track A governance 32194785639 = SUCCESS;
  • CI 32194785866 = SUCCESS;
  • changed paths = exactly 3 source task/report/evidence paths;
  • review threads = 0.

Fresh independent coordinator audit review 4969045959 classified the source ACCEPT_WITH_EDITS and found one material evidence defect:

WM-MINIMAP-AUD-001 — the producer's relative jump-table heuristic does not prove its emitted per-method target=... direct=true addresses. The retained artifact gives identical reported targets to unrelated metaobjects, so those per-method destinations are not admissible exact code-entry facts.

Corrected promotion PR #551 independently revalidated artifact 9345368809 (ZIP SHA-256 c3c32ad9ce527e5ff7d469ae41914f3802fb55d465a993c8dbb32be2840e9755), preserved exact public-package/QMeta/class-method/string evidence, rejected the target-address claims, kept F11/F12 as bounded static PARTIAL, F13 as PARTIAL, and left F08/F10 blocked. PR #536 shared matrix paths were not modified.

Promotion #551 exact head a86713c0f79190710cd437ed3b550ccaf7652436 passed CI 32223365501 = SUCCESS, promotion review 4969069217 reported 0 open material findings, and #551 squash-merged as 6071b237d70a11ab10e5050cc23730162b0e7e0b.

This source Draft must not be merged after its corrected promotion has landed. No runtime/login/credentials/gameplay/client mutation occurred in the source or promotion; E2E is NOT_APPLICABLE for this runtime_access:none static slice.

@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.

Fresh independent coordinator audit on exact source head 55034d31a3cfd55c597f463c97ebf97065192c8b.

Classification: ACCEPT_WITH_EDITS for the bounded static F11/F12/F13 package; source Draft must not merge as-is.

Independent evidence checks:

  • downloaded workflow artifact 9345368809; local SHA-256 exactly c3c32ad9ce527e5ff7d469ae41914f3802fb55d465a993c8dbb32be2840e9755, matching GitHub artifact digest;
  • artifact contains exactly fence.txt, minimap-qmeta.txt, minimap-strings.txt; no raw client binary;
  • fence values match the retained current public package fingerprint: packed 1fc26d66..., unpacked ed5469b9..., size 52109920, CURRENT_PACKAGE_FENCE=PASS;
  • raw QMeta/string evidence independently supports the dedicated class/method ownership and persistence/action-name surfaces needed to move F11/F12 from NOT_STARTED to bounded static PARTIAL; F13 remains PARTIAL.

Material finding WM-MINIMAP-AUD-001 (MEDIUM, high confidence): the producer's jump-table heuristic does not prove the emitted target=... direct=true addresses. It selects a candidate table whenever all computed entries are executable, but unrelated metaobjects receive identical targets. Examples from the retained artifact: TMinimapMarkerStorage methods 0..4 and TMinimapTileStorage methods 0..4 map to the same five addresses; TMinimapVisibleArea::restoreZoomLevelFromOptions, TMinimapProtocolMessageHandler::handleCyclopediaMapDataMessage, and TMinimapTileManager::{publishGameAction,handleGameAction} all map to 0xde15a0. Those coincidences falsify the claim that these are exact per-method static-metacall destinations.

Required edit before promotion: retain class/method names, QMeta/static-metacall ownership, strings, package fence and conservative F11/F12/F13 status; remove or explicitly downgrade all per-method target addresses/directness as heuristic-unverified. Do not promote formulas/data layout/runtime semantics. F08/F10 stay blocked and #536 remains untouched.

Open material findings after source review: 1 until corrected promotion is produced. E2E remains NOT_APPLICABLE for this static runtime_access:none slice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant