fonline-tla: Instructions file for Codex

FOnline: The Life After — Agent Instructions

Read this project guide fully, then the task's owning documents. Human entry: README.md; full index: Docs/README.md. .github/copilot-instructions.md points here; do not maintain competing instruction bodies.

Start and authority

1. Confirm checkout, branch, requested outcome and dirty files. Inspect the project and Engine/ independently; preserve user and other-agent edits. Re-anchor from the plan, current source and diff after a handoff or compaction.
2. Read owners, validators and callers before designing a change. Requirements establish intended behavior; source establishes current behavior. Historical logs, summaries and worker reports are evidence, not new action authority.
3. Carry the authorized scope through implementation and verification. Resolve routine choices from source; ask for material missing requirements or actions outside scope. If a required source is unavailable, report it and wait before synthesizing conclusions.
4. Before non-trivial implementation, write a plan in Docs/Plans/, including plans produced by workflow skills. Update its scope, steps, decisions, acceptance and actual verification results as work proceeds. Update affected documentation alongside the changes; do not defer plans or docs to the final handoff. Follow the working procedure.
5. Put private task logs, screenshots, scripts, dumps, drafts and worker inputs in ignored Workspace/<task-id>/. Standard tool outputs keep their owning paths; permanent delegation history follows the governing launcher procedure. Maintained guides belong under Docs/; keep task reports out of the repository root.

• No git add, commit, push, merge, destructive Git operation, publication or deployment without explicit action authority. Prepare reviewable local edits; “prepare for commit” does not mean create a commit. Past permissions do not authorize a new task. Never revert work you did not make.
• Stay on the requested project branch/worktree. Engine-only branch/history instructions apply only to Engine. Normal Engine updates keep its master branch; do not detach or move the project branch incidentally.
• Chat with the owner in Russian unless requested otherwise. General project/ agent docs and native C++ stay English; keep existing documents in their own language (Docs/ScriptStyle.md is Russian). Script comments and module headers are Russian; translate existing English comments when touching the module. Serialized metadata, IDs, text keys and identifiers stay English.
• Do not read credentials for unrelated maintenance or copy secrets/raw private sessions into source, chat or reports. The base config's public development channel pair is for local use; production keys remain host-owned.