ARCADIA-Studio/AGENTS.md

Cooperation through Gitea MCP

Use Gitea MCP to coordinate with other agents working on this project.

• Before starting or resuming work, read relevant issues, comments, pull requests, and project Wiki pages to understand current progress and decisions.
• Use issues and comments to communicate plans, identify who is handling work, ask questions, report blockers, and leave handoffs. Check existing work before creating duplicates.
• Identify yourself consistently in messages. Do not assume another agent has read a message or is currently running.
• Respect work already in progress. Coordinate overlapping changes and preserve other agents' edits.
• Create and update the common project Wiki with shared knowledge, architecture, setup instructions, and decisions that will help future work. Keep it accurate as the project changes.
• Record meaningful progress and results in Gitea so another agent can continue without access to your conversation. Include relevant commits, validation results, and next steps.
• Publish versioned Gitea releases at meaningful, working milestones so the user can see progress and try the application. Include runnable builds or appropriate distributable artifacts, concise release notes, launch instructions, known limitations, and what was verified. Mark unfinished versions as prereleases. Coordinate release ownership to avoid duplicates.
• Keep coordination concise and useful. Use the available MCP tools, and report access failures honestly.

Work autonomously within the user's requested scope and follow the project's existing conventions.

Gitea and harness maintenance

Keep Gitea resources and files under harness directory organized, accurate, and useful for other agents.

• As work progresses, consolidate duplicated information, update outdated guidance, close resolved or superseded issues, and remove obsolete temporary files. Perform maintenance when useful without letting it displace project work.
• Preserve a concise, durable record of what was done, decisions and their reasons, validation results, failed approaches, and remaining work. Link relevant issues, pull requests, commits, and releases so future agents can distinguish completed work from work that still needs attention and avoid repeating unsuccessful attempts.
• Prefer closing, marking as superseded, or archiving historical material over deleting it. Keep current instructions clearly separated from historical records, and link superseded guidance to its replacement.
• Before removing information or artifacts, check whether they contain unique knowledge, are referenced elsewhere, or are still needed by another agent. Preserve useful findings in the appropriate shared record first, update affected references, and coordinate cleanup that overlaps active work.
• Keep indexes and entrypoint documents concise and current so agents can quickly find authoritative guidance and relevant history.