Skip to content

ci: prove official Tibia login without OCR on Synology - #48

Closed
blakinio wants to merge 138 commits into
mainfrom
ci/OTC-20260727-tibia-linux-runner-analysis
Closed

ci: prove official Tibia login without OCR on Synology#48
blakinio wants to merge 138 commits into
mainfrom
ci/OTC-20260727-tibia-linux-runner-analysis

Conversation

@blakinio

@blakinio blakinio commented Jul 26, 2026

Copy link
Copy Markdown
Owner

Operational continuation of OTC-20260727-tibia-linux-runner-analysis for OTCLIENT-TIBIA-RE.

Canonical repository/runtime

All new programme work, findings, checkpoints, tools and handovers belong in blakinio/otclient. Historical Oteryn Platform reports/runners/containers are read-only evidence only.

The active runtime is being migrated to the dedicated OTClient Synology runner:

runner_name: synology-otclient-01
migration_selector: [self-hosted, otclient, synology]
post_deploy_selector: [self-hosted, Linux, X64, otclient, tibia-re, synology]
persistent_state: /home/runner/_work/_otclient_tibia_re_state
runner_infra: PR #280

Commit eb5e3a0151014f07f8c0b66ecf32f2686a418179 replaces the old [self-hosted, oteryn-staging] Docker-container bootstrap with a direct dedicated-runner bootstrap. It no longer requires Docker, an Oteryn-owned container, or /var/lib/oteryn-staging-state/**.

Canonical acceptance run 31679097113, job 94380204633, is currently queued awaiting a matching dedicated OTClient runner. The migration record is persisted at docs/agents/reports/OTCLIENT-20260813-dedicated-runner-migration.md.

Research objective

Continue official Linux Tibia client analysis without OCR/Tesseract, building deterministic structural state reads, protocol/action evidence, OTBM reconstruction inputs and a reusable non-GDB runtime bridge. Structural world/GameState evidence remains required for IN_GAME and action success claims.

Safety/ownership boundaries

  • repository writes remain confined to blakinio/otclient task-owned paths;
  • no new programme execution on oteryn-staging, oteryn-synology-staging or oteryn-tibia-client-analysis;
  • no proprietary Tibia binaries/assets committed;
  • never print/persist credentials or secret-bearing session values;
  • no OCR/Tesseract for semantic proof;
  • no owner-funded Codex/OpenAI API/paid AI quota without separate explicit authorization;
  • all material continuation state must be persisted or indexed in blakinio/otclient before return/rotation.

This remains a draft operational PR while live runtime evidence is being collected and the dedicated-runner migration is awaiting Synology deployment/acceptance proof.

@blakinio blakinio removed the state:stalled No meaningful update within the configured threshold label Aug 12, 2026

Copy link
Copy Markdown
Owner Author

Migration checkpoint (2026-08-13): PR #284 (feat/OTC-20260813-tibia-global-login-lab) is now the canonical active implementation lane for the official-Tibia OTClient compatibility investigation. PR #48 is retained only as historical runtime evidence/migration input while the proven userspace-WARP/asset/login components are verified in #284. Do not start new runtime work here. Once the required migrated components are proven in #284, this PR should be closed as superseded. Durable task state: docs/agents/tasks/active/OTC-20260813-tibia-global-login-lab.md.

@blakinio

Copy link
Copy Markdown
Owner Author

Closing this execution lane as historical evidence for OTCLIENT-TIBIA-RE. Per the repository owner directive, PR #284 is the canonical active implementation lane for running our OTClient against official Tibia; #48 must not consume the dedicated Synology runner during that investigation.

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

Labels

programme:infrastructure Infrastructure programme

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant