ci: add Gitea Actions workflow and Docker Compose test runner; add test image\n\ngovernance: encode CI/containers rules in system prompts and AGENTS templates; update proposal and docs

meta/AGENTS.seed.llm.md

@@ -15,3 +15,5 @@
 - Planning/Architecture: Plan via Questions→Proposal→Plan; maintain global architecture/module map; implement module-by-module; avoid refactors unless assumptions change and plans/docs are updated.
  
 - Clean Roots: Keep project root minimal; use `docs/`, `templates/`, `prompts/`, `scripts/`, etc.; avoid ad-hoc root files.
+ 
+- CI/Containers: Use Gitea Actions with local parity via Docker Compose; do work in containers; host for git/tea + Docker orchestration; dependencies via Docker; explicit names; cleanup.

meta/AGENTS.seed.md

@@ -75,3 +75,10 @@ Customize this AGENTS.md to fit your project specifics while preserving the one-
 ## Clean Repository Roots
 - Keep the project root minimal and tidy. Prefer directories over many files at root.
 - Place docs, templates, prompts, and scripts under dedicated subdirectories.
+
+## CI and Containers (Gitea + Docker)
+- Use Gitea Actions for CI (`.gitea/workflows/`).
+- Ensure local parity with Docker Compose; provide scripts to run the same CI tasks locally.
+- Perform work inside containers where appropriate; use host for git/tea and Docker orchestration only.
+- Manage dependencies via container images; avoid host-level installs.
+- Use explicit container/network names; clean up containers, networks, and volumes.