2.2 KiB
purpur-fantasy-stick agent entrypoint
Canonical engineering guidance and technical/process documents are in the private SoMC OKF wiki.
Stories, acceptance criteria, status and evidence belong in Kaneo Social Minecraft, with subjects [purpur-fantasy-stick] Descriptive title (no US-### or FS-* prefix). Use the configured authenticated kaneo MCP server per Kaneo access and migration; report unavailable access rather than creating local story copies. OpenProject is read-only history.
Before work, read the sibling ../somc-okf/index.md, ../somc-okf/processes/index.md, ../somc-okf/projects/purpur-fantasy-stick/index.md, that project's engineering.md, and relevant Kaneo tickets with subject prefix [purpur-fantasy-stick]. Follow the parent workspace AGENTS.md when present. Do not invent defaults for explicitly unresolved gameplay or recovery decisions.
For standalone checkouts, obtain access to the project page and development process. Do not create a parallel knowledge bundle. Source builds do not require private wiki access.
Follow the full development process and development cycle for approvals, test-first/full-suite verification, required Gitea PR checks/reviews and merge, and merged-tree verification before ticket completion. Never push source main directly. GitOps preparation is separately approved and committed locally without pushing. Only Do release authorizes a reviewed production push.
Use Java 25 and the declared Purpur API. Run ./gradlew clean check jar. Preserve runtime identity, persistent namespaces, and unrelated player/plugin state. Never expose release credentials in arguments, output, or Git.