chore: scaffold Astro project and configure agent skills

Initial commit: Astro minimal template (Node >= 22.12), agent docs
(AGENTS.md/CLAUDE.md/QWEN.md), and docs/agents setup for the Gitea
issue tracker via the tea CLI, triage labels, and domain docs.

QWEN.md

@@ -0,0 +1,27 @@
+# QWEN.md
+
+This file provides guidance to Qwen Code when working with code in this repository.
+
+## Project Overview
+
+`php-node-renderer-playground` is an **early-stage playground/experiment repository** with no source code yet. The working tree contains only this file and `.mcp.json`, and the git repository has no commits.
+
+Based on the project name, the intended purpose is exploring **PHP and Node.js rendering** — e.g., how PHP and Node renderers can interoperate, share rendering logic, or be combined for server-side rendering. Nothing has been implemented yet; treat this repo as a blank slate.
+
+## Tools & Configuration
+
+- **`.mcp.json`** — Configures an MCP server for the **Astro docs** (`https://mcp.docs.astro.build/mcp`). The `mcp__Astro_docs__search_astro_docs_1e828ud` tool is available to search official Astro framework documentation. This suggests Astro (or a similar Node-based renderer) is a likely candidate for the rendering experiments. Use it when questions about Astro's rendering, SSR, or SSG behavior come up.
+
+## Building and Running
+
+No build, run, or test commands exist yet. The project has not been scaffolded.
+
+- TODO: Once the stack is chosen (e.g., a PHP runtime + Node/Astro renderer), document the setup and key commands here (install, dev server, build, test).
+- Until then, do not assume any toolchain (composer, npm, etc.) is present — verify against files in the repo before recommending commands.
+
+## Development Conventions
+
+No conventions established yet. When code is added:
+
+- Follow the conventions of whichever frameworks are chosen (e.g., Astro conventions for any Node/SSR side; PSR-12 for PHP if PHP is introduced).
+- Keep the playground nature in mind: this repo is for experiments, so prefer small, self-contained examples over full application scaffolding.