feat: complete bark battle playable demo

docs/agents/domain.md

@@ -0,0 +1,36 @@
+# Domain Docs
+
+How the engineering skills should consume this repo's domain documentation when exploring the codebase.
+
+## Layout
+
+This repo uses a **single-context** layout for Matt Pocock engineering skills:
+
+- `CONTEXT.md` at the repo root, when present, is the primary domain glossary/context file.
+- `docs/adr/`, when present, contains architecture decision records.
+- If either path does not exist, proceed silently; do not block the task just to create it.
+
+## Before exploring, read these
+
+1. Root `CONTEXT.md`, if present.
+2. Relevant ADRs under `docs/adr/`, if present.
+3. Existing project context that predates this setup:
+   - `.hermes/README.md`
+   - `.hermes/shared-memory/project-overview.md`
+   - `.hermes/shared-memory/team-conventions.md`
+   - `.hermes/shared-memory/development-workflow.md`
+   - `.hermes/shared-memory/decision-log.md`
+   - `.hermes/shared-memory/pitfalls.md`
+   - Relevant files under `docs/technical/`, `docs/prd/`, `docs/design/`, and `docs/experience/`
+
+Follow `AGENTS.md` when it is more specific than this file. If older docs conflict with current code or newer technical docs, treat current code and newer docs as authoritative and update stale docs when the task requires it.
+
+## Use the glossary's vocabulary
+
+When your output names a domain concept in an issue title, refactor proposal, diagnosis, test name, or implementation plan, use the term as defined in `CONTEXT.md` when available. Do not drift to synonyms the glossary explicitly avoids.
+
+If the concept you need is not in the glossary yet, either use the established vocabulary from `.hermes/shared-memory/` and `docs/`, or note the gap for a future documentation pass.
+
+## Flag ADR conflicts
+
+If your output contradicts an existing ADR, surface it explicitly rather than silently overriding it.

docs/agents/issue-tracker.md

@@ -0,0 +1,35 @@
+# Issue tracker: Gitea
+
+Issues and PRDs for this repo live as issues in the self-hosted Gitea remote:
+
+- Remote: `http://82.157.175.59:3000/GenarrativeAI/Genarrative.git`
+- Tracker type: Gitea Issues
+
+## Conventions
+
+- Prefer the Gitea `tea` CLI when it is installed and configured for this host.
+- Do not use GitHub `gh` or GitLab `glab` for this repo unless the repository is explicitly migrated to those platforms.
+- If `tea` is unavailable, use the Gitea Web UI or Gitea REST API for the same operations.
+
+## Common operations with `tea`
+
+Exact flags can vary by `tea` version. Run `tea issues --help` or `tea issue --help` before using a command in a new environment.
+
+- Create an issue: `tea issues create --title "..." --body "..."`
+- Read an issue: `tea issues view <number>`
+- List issues: `tea issues list`
+- Comment on an issue: use the installed `tea` issue comment command shown by `tea issues --help`; if unavailable, use the Gitea Web UI or REST API.
+- Apply labels: use the installed `tea` issue update/edit command shown by `tea issues --help`; if unavailable, use the Gitea Web UI or REST API.
+- Close an issue: use the installed `tea` issue close/update command shown by `tea issues --help`; if unavailable, use the Gitea Web UI or REST API.
+
+## When a skill says "publish to the issue tracker"
+
+Create a Gitea issue in `GenarrativeAI/Genarrative` with the requested title, body, labels, and links back to any relevant docs or branch.
+
+## When a skill says "fetch the relevant ticket"
+
+Read the Gitea issue body and comments/notes for the referenced issue number. Include labels and current open/closed state in the working context.
+
+## Authentication
+
+Use the locally configured Gitea credentials for the current developer. Do not commit tokens, cookies, `.env`, or local credential files.

docs/agents/triage-labels.md

@@ -0,0 +1,15 @@
+# Triage Labels
+
+The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's Gitea issue tracker.
+
+| Label in mattpocock/skills | Label in our tracker | Meaning                                  |
+| -------------------------- | -------------------- | ---------------------------------------- |
+| `needs-triage`             | `needs-triage`       | Maintainer needs to evaluate this issue  |
+| `needs-info`               | `needs-info`         | Waiting on reporter for more information |
+| `ready-for-agent`          | `ready-for-agent`    | Fully specified, ready for an AFK agent  |
+| `ready-for-human`          | `ready-for-human`    | Requires human implementation            |
+| `wontfix`                  | `wontfix`            | Will not be actioned                     |
+
+When a skill mentions a role, use the corresponding Gitea label string from this table.
+
+If the Gitea repository later adopts Chinese labels or a different naming scheme, edit the right-hand column here rather than letting skills create duplicate labels.