COMMUNITY RAIDERS — CONTRIBUTOR / AGENT CONTEXT Updated: 2026-10-26 Source edition: a8bf2e0ef34b5911e0dfa48fe87beb23fba0d323 Private canonical repository: https://github.com/JacobN23/communityraiders This public, curated context summarizes the verified source edition. It is not a credential, deployment approval, repository invitation or substitute for reading the current checkout and its AGENTS.md. Repository/infrastructure access is managed separately by the owner. Never place tokens, bearer URLs, real user records or database exports into documentation or agent messages. READ FIRST /guide/architecture — service ownership and boundaries /guide/identity — creator session, website player, Extension JWT and overlay /guide/player-data — account-wide appearance versus community-owned gameplay /guide/api — registered routes, actual request schemas and response limitations /api-contract.json — curated machine-readable contract generated from routes /project-context.json — structured guide edition and pinned source map SYSTEM MAP One FastAPI service owns persistent identity, community scope and accepted inventory/progression state. SQLite transactions enforce ownership and revision checks. Normal HTML/JS owns dashboard/panel controls; self-hosted Phaser renders accepted state. Browsers and chat messages never grant items, XP or authority. One player can have one raider per community, with separate inventory/equipment and XP. Physical appearance and base clothing are shared across that account. Selecting a community or following a code does not confer creator/admin rights. Website and native Twitch Extension identities are distinct; creator OAuth is not a viewer Extension JWT. Never add a public fake-login or fake-JWT shortcut. Raiderville codes discover server-owned rooms. Verified Twitch identity resolves the correct community raider and persistent association. Presence uses HTTP snapshots, a controller lease and server-accepted movement. Room state is not combat simulation; current actors move as composed still artwork. CURRENT SOURCE Creator/player sign-in, associated-community browser and expiring streamer presence; shared male/female neutral appearance and validated outfit options; owned-equipment validation; native panel/browser visual preview; community-bound campsite rooms, code join, shared presence, movement and visual campfire/GM tags. GM designation is visual only. Twitch live/presence flags are separate facts. NOT ACTIVE CURRENT-MAIN GAMEPLAY Goblin battler/chat transport, new directional walking and worn-knight armor are local proofs awaiting integration. Bot authorization code is present but setup is disabled by default and does not activate transport or retain chat tokens. No claim of working automatic combat/rewards, PvP, dungeons, upgrade editor or premium entitlements follows from these docs. Check their actual branch/status with the owner before depending on them. CONTRIBUTING Read the current code and /guide/contributing. Work on a scoped branch, preserve other contributors' edits, validate wrong identity/community and repeated/stale requests, then provide actual browser/render evidence for affected surfaces. Use the existing charcoal, fine bronze and original Emberpixel art contracts. The player-art skill is a working kit; structural tests do not prove artistic acceptance or compatibility with female/guarded/walking/equipped combinations. Never silently replace an unsupported saved look with a fixed default sprite. CHECKS python -m pytest node --test tests/*.test.mjs (expand paths explicitly where the shell requires) python scripts/package_extension.py Container test target: docker build --target test -t community-raiders-test . docker run --rm community-raiders-test RELEASE Main is the deployment branch. A push can trigger production automatically. Keep unfinished features out of a release. Source publication, new access grants, secrets, live chat activation and data deletion are distinct actions; this context does not authorize any of them. Use current owner instructions and the existing project pipeline. Verify exact deployed revision/health and affected routes. See the full guides and their pinned source anchors for implementation details. No private source files or production records are embedded in this context.