fix(linux): add missing yaze_gfx_render dependency to yaze_gfx_debug

Fixes linker error on Linux where yaze_gfx_debug.a (performance_dashboard.cc)
was calling AtlasRenderer::Get() and AtlasRenderer::GetStats() but wasn't
linking against yaze_gfx_render which contains atlas_renderer.cc.

Root cause: yaze_gfx_debug was only linking to yaze_gfx_types and
yaze_gfx_resource, missing the yaze_gfx_render dependency.

This also fixes the undefined reference errors for HttpServer methods
which were already properly included in the agent.cmake source list.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

docs/internal/agents/gh-actions-remote.md

@@ -0,0 +1,45 @@
+# GitHub Actions Remote Workflow Documentation
+
+This document describes how to trigger GitHub Actions workflows remotely, specifically focusing on the `ci.yml` workflow and its custom inputs.
+
+## Triggering `ci.yml` Remotely
+
+The `ci.yml` workflow can be triggered manually via the GitHub UI or programmatically using the GitHub API (or `gh` CLI) thanks to the `workflow_dispatch` event.
+
+### Inputs
+
+The `workflow_dispatch` event for `ci.yml` supports the following custom inputs:
+
+- **`build_type`**:
+  - **Description**: Specifies the CMake build type.
+  - **Type**: `choice`
+  - **Options**: `Debug`, `Release`, `RelWithDebInfo`
+  - **Default**: `RelWithDebInfo`
+
+- **`run_sanitizers`**:
+  - **Description**: A boolean flag to enable or disable memory sanitizer runs.
+  - **Type**: `boolean`
+  - **Default**: `false`
+
+- **`upload_artifacts`**:
+  - **Description**: A boolean flag to enable or disable uploading build artifacts.
+  - **Type**: `boolean`
+  - **Default**: `false`
+
+- **`enable_http_api_tests`**:
+  - **Description**: **(NEW)** A boolean flag to enable or disable an additional step that runs HTTP API tests after the build. When set to `true`, a script (`scripts/agents/test-http-api.sh`) will be executed to validate the HTTP server (checking if the port is up and the health endpoint responds).
+  - **Type**: `boolean`
+  - **Default**: `false`
+
+### Example Usage (GitHub CLI)
+
+To trigger the `ci.yml` workflow with custom inputs using the `gh` CLI:
+
+```bash
+gh workflow run ci.yml -f build_type=Release -f enable_http_api_tests=true
+```
+
+This command will:
+- Trigger the `ci.yml` workflow.
+- Set the `build_type` to `Release`.
+- Enable the HTTP API tests.

docs/internal/agents/initiative-template.md

@@ -0,0 +1,45 @@
+# AI Initiative Template
+
+Use this template when kicking off a sizable AI-driven effort (infrastructure, editor refactor,
+automation tooling, etc.). Keep the filled-out document alongside other planning notes and reference
+it from the coordination board.
+
+```
+# <Initiative Title>
+
+## Summary
+- Lead agent/persona:
+- Supporting agents:
+- Problem statement:
+- Success metrics:
+
+## Scope
+- In scope:
+- Out of scope:
+- Dependencies / upstream projects:
+
+## Risks & Mitigations
+- Risk 1 – mitigation
+- Risk 2 – mitigation
+
+## Testing & Validation
+- Required test targets:
+- ROM/test data requirements:
+- Manual validation steps (if any):
+
+## Documentation Impact
+- Public docs to update:
+- Internal docs/templates to update:
+- Coordination board entry link:
+- Helper scripts to use/log: `scripts/agents/smoke-build.sh`, `scripts/agents/run-tests.sh`, `scripts/agents/run-gh-workflow.sh`
+
+## Timeline / Checkpoints
+- Milestone 1 (description, ETA)
+- Milestone 2 (description, ETA)
+```
+
+After filling in the template:
+1. Check the coordination board for conflicts before starting work.
+2. Link the initiative file from your board entries so other agents can find details without copying
+   sections into multiple docs.
+3. Archive or mark the initiative as complete when the success metrics are met.

docs/internal/agents/personas.md

@@ -0,0 +1,15 @@
+# Agent Personas
+
+Use these canonical identifiers when updating the
+[coordination board](coordination-board.md) or referencing responsibilities in other documents.
+
+| Agent ID        | Primary Focus                                          | Notes |
+|-----------------|--------------------------------------------------------|-------|
+| `CLAUDE_CORE`   | Core editor/engine refactors, renderer work, SDL/ImGui | Use when Claude tackles gameplay/editor features. |
+| `CLAUDE_AIINF`  | AI infrastructure (`z3ed`, agents, gRPC automation)    | Coordinates closely with Gemini automation agents. |
+| `CLAUDE_DOCS`   | Documentation, onboarding guides, product notes        | Keep docs synced with code changes and proposals. |
+| `GEMINI_AUTOM`  | Automation/testing/CLI improvements, CI integrations   | Handles scripting-heavy or test harness tasks. |
+| `CODEX`         | Codex CLI assistant / overseer                         | Default persona; also monitors docs/build coordination when noted. |
+
+Add new rows as additional personas are created. Every new persona must follow the protocol in
+`AGENTS.md` and post updates to the coordination board before starting work.