release: v0.14.0 [skip ci]

## Summary

Thoroughly cleans Docker artifacts on runner removal, updates devx to v0.9.11, fixes Makefile checkmake graceful skip, and comprehensive docs rewrite.

Molecule tests fail due to pre-existing Docker infrastructure issue (Docker socket not available in CI runners).

Closes GRM-75

.ansible-lint

@@ -0,0 +1,10 @@
+# Ansible-lint configuration
+exclude_paths:
+  - .venv/
+  - .cache/
+  - molecule/
+  - .molecule/
+  - .pytest_cache/
+skip_list:
+  # Rootless Docker uses `systemctl --user` which the systemd module doesn't support
+  - command-instead-of-module

.badges/coverage.svg

@@ -1,20 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="104" height="20" role="img"
-  aria-label="coverage: 100%">
-  <title>coverage: 100%</title>
-  <linearGradient id="s" x2="0" y2="100%">
-    <stop offset="0" stop-color="#fff" stop-opacity=".7"/>
-    <stop offset=".1" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset=".9" stop-color="#000" stop-opacity=".3"/>
-    <stop offset="1" stop-color="#bbb" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r"><rect width="104" height="20" rx="3" fill="#fff"/></clipPath>
-  <g clip-path="url(#r)">
-    <rect width="66" height="20" fill="#555"/>
-    <rect x="66" width="38" height="20" fill="#4c1"/>
-    <rect width="104" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,DejaVu Sans,sans-serif" font-size="11">
-    <text x="33" y="14">coverage</text>
-    <text x="85" y="14">100%</text>
-  </g>
-</svg>

.badges/docs.svg

@@ -1,20 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="76" height="20" role="img"
-  aria-label="docs: 100%">
-  <title>docs: 100%</title>
-  <linearGradient id="s" x2="0" y2="100%">
-    <stop offset="0" stop-color="#fff" stop-opacity=".7"/>
-    <stop offset=".1" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset=".9" stop-color="#000" stop-opacity=".3"/>
-    <stop offset="1" stop-color="#bbb" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r"><rect width="76" height="20" rx="3" fill="#fff"/></clipPath>
-  <g clip-path="url(#r)">
-    <rect width="38" height="20" fill="#555"/>
-    <rect x="38" width="38" height="20" fill="#4c1"/>
-    <rect width="76" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,DejaVu Sans,sans-serif" font-size="11">
-    <text x="19" y="14">docs</text>
-    <text x="57" y="14">100%</text>
-  </g>
-</svg>

.badges/python.svg

@@ -1,20 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="90" height="20" role="img"
-  aria-label="python: 3.12">
-  <title>python: 3.12</title>
-  <linearGradient id="s" x2="0" y2="100%">
-    <stop offset="0" stop-color="#fff" stop-opacity=".7"/>
-    <stop offset=".1" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset=".9" stop-color="#000" stop-opacity=".3"/>
-    <stop offset="1" stop-color="#bbb" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r"><rect width="90" height="20" rx="3" fill="#fff"/></clipPath>
-  <g clip-path="url(#r)">
-    <rect width="52" height="20" fill="#555"/>
-    <rect x="52" width="38" height="20" fill="#007ec6"/>
-    <rect width="90" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,DejaVu Sans,sans-serif" font-size="11">
-    <text x="26" y="14">python</text>
-    <text x="71" y="14">3.12</text>
-  </g>
-</svg>

.badges/quality.svg

@@ -1,20 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="124" height="20" role="img"
-  aria-label="code quality: A">
-  <title>code quality: A</title>
-  <linearGradient id="s" x2="0" y2="100%">
-    <stop offset="0" stop-color="#fff" stop-opacity=".7"/>
-    <stop offset=".1" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset=".9" stop-color="#000" stop-opacity=".3"/>
-    <stop offset="1" stop-color="#bbb" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r"><rect width="124" height="20" rx="3" fill="#fff"/></clipPath>
-  <g clip-path="url(#r)">
-    <rect width="94" height="20" fill="#555"/>
-    <rect x="94" width="30" height="20" fill="#4c1"/>
-    <rect width="124" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,DejaVu Sans,sans-serif" font-size="11">
-    <text x="47" y="14">code quality</text>
-    <text x="109" y="14">A</text>
-  </g>
-</svg>

.badges/tests.svg

@@ -1,20 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="132" height="20" role="img"
-  aria-label="tests: 243 passing">
-  <title>tests: 243 passing</title>
-  <linearGradient id="s" x2="0" y2="100%">
-    <stop offset="0" stop-color="#fff" stop-opacity=".7"/>
-    <stop offset=".1" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset=".9" stop-color="#000" stop-opacity=".3"/>
-    <stop offset="1" stop-color="#bbb" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r"><rect width="132" height="20" rx="3" fill="#fff"/></clipPath>
-  <g clip-path="url(#r)">
-    <rect width="45" height="20" fill="#555"/>
-    <rect x="45" width="87" height="20" fill="#4c1"/>
-    <rect width="132" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,DejaVu Sans,sans-serif" font-size="11">
-    <text x="22" y="14">tests</text>
-    <text x="88" y="14">243 passing</text>
-  </g>
-</svg>

.badges/version.svg

@@ -1,20 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="118" height="20" role="img"
-  aria-label="version: v0.21.0">
-  <title>version: v0.21.0</title>
-  <linearGradient id="s" x2="0" y2="100%">
-    <stop offset="0" stop-color="#fff" stop-opacity=".7"/>
-    <stop offset=".1" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset=".9" stop-color="#000" stop-opacity=".3"/>
-    <stop offset="1" stop-color="#bbb" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r"><rect width="118" height="20" rx="3" fill="#fff"/></clipPath>
-  <g clip-path="url(#r)">
-    <rect width="59" height="20" fill="#555"/>
-    <rect x="59" width="59" height="20" fill="#007ec6"/>
-    <rect width="118" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,DejaVu Sans,sans-serif" font-size="11">
-    <text x="29" y="14">version</text>
-    <text x="88" y="14">v0.21.0</text>
-  </g>
-</svg>

.checkmake.ini

@@ -0,0 +1,4 @@
+[checkmake]
+# Disable the phony rule which flags common .PHONY placement patterns
+# as it produces false positives for standard Makefile layouts
+disable=maxbodylength

.devin/agents/ci-investigator/AGENT.md

@@ -0,0 +1,184 @@
+---
+name: ci-investigator
+description: Investigates CI failures in the grm repo by fetching job logs via Gitea MCP, identifying root cause across quality/molecule-tests/release/publish/wiki-sync jobs, and validating fixes locally.
+model: glm-5.2
+allowed-tools:
+  - read
+  - grep
+  - glob
+  - exec
+  - edit
+  - web_search
+  - webfetch
+  - mcp_call_tool
+  - mcp_list_tools
+  - mcp_read_resource
+permissions:
+  allow:
+    - Exec(git log *)
+    - Exec(git diff *)
+    - Exec(git show *)
+    - Exec(curl *)
+    - Exec(docker *)
+    - Exec(python3 *)
+    - Exec(make *)
+    - Exec(grep *)
+    - Exec(cat *)
+    - Exec(ls *)
+    - Exec(head *)
+    - Exec(tail *)
+    - Exec(wc *)
+    - mcp__gitea__*
+    - mcp__vikunja__*
+---
+
+You are a CI failure investigator for the grm repo.
+
+## Working Directory
+
+The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first:
+```bash
+cd /home/emo/dev/ideas/oblachno/grm
+```
+
+## CI Job Dependency Graph
+
+**ci.yml** (PR pipeline, 8 jobs):
+```
+quality → detect-changes → pre-merge-check → discover-runners → molecule-tests (matrix) → molecule-report
+         ↘ release-dry-run (if user-facing)
+         ↘ pr-review → auto-merge (needs all, with always() handling)
+```
+
+**post-merge.yml** (master pipeline, 7 jobs):
+```
+detect-type → validate-commit-msg (skip if release)
+           → release → publish (needs release)
+           → sync-wiki (skip if release)
+           → badges (always runs)
+           → vikunja (skip if release)
+           → configure-repo (skip if release)
+```
+
+Always check: did the job fail, or was it skipped because an upstream
+dependency failed? Skipped jobs are not the root cause.
+
+## Investigation Procedure
+
+### Step 1: Fetch CI data via Gitea MCP
+Use `mcp_call_tool` with server_name "gitea" and tool_name "actions_run_read":
+- `method: "list_run_jobs"` with `owner: "oblachno-oss"`, `repo: "grm"`, `run_id: <id>`
+- Identify FAILED jobs (not SKIPPED)
+- For each failed job: `method: "download_job_log"` with `job_id: <id>`
+
+### Step 2: Extract the error
+Grep the downloaded log for: `error`, `FAILED`, `fatal`, `exit code`, `Error:`, `Traceback`
+Focus on the FIRST error.
+
+### Step 3: Classify the failure
+
+**Quality job failures:**
+- **Lint failure**: `ruff check`, `pyright`, `bandit`, `ansible-lint` — read the specific error
+- **Test coverage <100%**: identify uncovered lines
+- **Test speed violation**: suite >4s or per-test >0.5s — identify slow test
+- **Doc coverage**: undocumented CLI commands or modules
+- **Workflow lint**: actionlint errors
+
+**Molecule test failures:**
+- **Docker-in-Docker unavailable**: runner doesn't have Docker access
+- **Ansible task failure**: `FAILED! =>` — identify the task and role
+- **Platform-specific failure**: one OS fails (e.g. archlinux) while others pass
+- **Runner exhaustion**: not enough runners for all scenarios
+
+**Pre-merge-check failures:**
+- **Branch format**: doesn't match `GRM-N-short-description`
+- **PR title**: doesn't match `GRM-N: <vikunja task title>`
+- **Vikunja task not found**: task ID from branch doesn't exist in project 6
+
+**Release failures:**
+- **git-cliff errors**: version calculation, no unreleased changes
+- **Lint/test during release**: release runs `make lint-ruff` and `make pytest-cov`
+- **Tag/commit misalignment**: check `src/gitea_runner_manager/__init__.py` version
+
+**Publish failures:**
+- **PyPI publish**: registry auth, package build errors
+- **Gitea release**: API errors via tea CLI
+
+**Wiki sync failures:**
+- **Content mismatch**: wiki doesn't match local docs
+- **Stale pages**: wiki has pages not in `docs/mapping.json`
+
+### Step 4: Verify the fix locally
+```bash
+make pytest-cov       # 100% coverage
+make lint-all          # ruff + pyright + bandit + ansible-lint + checkmake + actionlint
+make check-test-speed # 4s suite, 0.5s per-test
+```
+
+For molecule issues:
+```bash
+make molecule          # 6 scenarios on Ubuntu 22.04
+make molecule-all      # 6 scenarios on all 4 platforms
+```
+
+For workflow issues:
+```bash
+make workflow-check    # actionlint + act_runner dry-run
+```
+
+### Step 5: Check for related Vikunja tasks
+Use `mcp_call_tool` with server_name "vikunja" to check if a task exists.
+CI auto-creates Gitea issues via `notify_failure`.
+
+### Step 6: Report
+1. **Root cause**: the specific error and why it occurred
+2. **Evidence**: log excerpts, local verification results
+3. **Affected files**: file paths and line numbers
+4. **Suggested fix**: specific code change with rationale
+5. **Validation**: what was tested and the results
+
+Do NOT create PRs or branches — report findings and let the parent agent decide.
+
+## Feedback Reporting
+
+When you encounter a concrete issue with a tool, workflow, or process
+that would benefit from further investigation, create a Gitea issue
+in the `oblachno-oss/grm` repo.
+
+### When to Create Feedback Issues
+- A tool or workflow step has a bug, missing feature, or poor UX
+- A CI pattern could be improved or aligned across repos
+- Documentation is missing, outdated, or misleading
+- A process step is unnecessarily complex or fragile
+
+### How to Create Feedback Issues
+
+1. **Deduplicate first**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "list_issues", with `labels: "feedback"`, `owner: "oblachno-oss"`,
+   `repo: "grm"`. Check if an open issue already covers the same topic.
+   Do NOT create duplicates.
+
+2. **Create the issue**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "issue_write", method "create_issue", `owner: "oblachno-oss"`,
+   `repo: "grm"`:
+   - **Title**: `[feedback] <category>: <short description>`
+   - **Labels**: `feedback` + one of: `tooling`, `ci-improvement`,
+     `doc-improvement`, `workflow-improvement`
+   - **Body** must include these sections:
+     ```
+     **Context**: What task you were performing, which repo
+     **Tool/Workflow**: The specific tool or workflow step involved
+     **Issue**: What went wrong or could be improved
+     **Reproduction**: Steps to reproduce (if applicable)
+     **Affected files**: File paths and line numbers
+     **Suggested investigation**: What an agent should look into
+     **Reported by**: <subagent profile name>
+     ```
+
+3. **Report back**: Include the issue URL in your report to the parent agent.
+
+### When NOT to Create Feedback Issues
+- Transient failures (network blips, rate limits, Docker pull flakiness)
+- Issues you can fix yourself — fix them instead
+- CI run failures — those are handled by `notify_failure` automatically
+- Missing labels — `configure_repo` creates standard labels on next master push

.devin/agents/dep-upgrader/AGENT.md

@@ -0,0 +1,151 @@
+---
+name: dep-upgrader
+description: Researches and applies Python/Ansible dependency upgrades in pyproject.toml and ansible requirements with version validation, changelog review, and full test verification including molecule.
+model: glm-5.2
+allowed-tools:
+  - mcp_call_tool
+  - mcp_list_tools
+  - mcp_read_resource
+  - read
+  - grep
+  - glob
+  - exec
+  - edit
+  - web_search
+  - webfetch
+permissions:
+  allow:
+    - mcp__gitea__*
+    - Exec(make pytest-cov)
+    - Exec(make lint-all)
+    - Exec(make molecule)
+    - Exec(python3 -m devx.tools.check_test_speed *)
+    - Exec(python3 -m devx.tools.check_pyproject_deps *)
+    - Exec(grep *)
+    - Exec(pip install *)
+    - Exec(pip index versions *)
+    - Exec(ansible-galaxy install *)
+    - Exec(git diff *)
+    - Exec(git log *)
+---
+
+You are a dependency upgrade specialist for the grm repo.
+
+## Working Directory
+
+The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first.
+
+## Dependency Reference Locations
+
+- **Python deps**: `pyproject.toml` — `[project] dependencies` and `[project.optional-dependencies]`
+- **Ansible deps**: `ansible/requirements.yml` — galaxy collections and roles
+- **Dep documentation**: Each pyproject.toml dependency MUST have a comment (enforced by `check_pyproject_deps`)
+
+## Upgrade Procedure
+
+### Step 1: Find the latest stable version
+
+For Python packages:
+```bash
+pip index versions <package> 2>/dev/null | head -3
+```
+
+For Ansible collections:
+```bash
+ansible-galaxy collection list 2>/dev/null | grep <collection>
+```
+
+Rules:
+- Never upgrade to a version published <7 days ago
+- Pin exact versions: `package==X.Y.Z`
+- For Ansible collections: `community.docker:==3.10.2`
+
+### Step 2: Review breaking changes
+Read the changelog/release notes. Look for:
+- Breaking API changes
+- Deprecated features
+- Minimum Python/Ansible version changes
+- New required dependencies
+
+### Step 3: Apply the upgrade
+
+**Python deps** — edit `pyproject.toml`:
+Each dependency line MUST have a trailing comment:
+```toml
+"ruff==0.12.0",  # Python linter and formatter
+```
+
+**Ansible collections** — edit `ansible/requirements.yml`:
+```yaml
+collections:
+  - name: community.docker
+    version: "==3.10.2"
+```
+
+### Step 4: Install and verify
+```bash
+pip install -e .[dev]                    # reinstall with new deps
+ansible-galaxy install -r ansible/requirements.yml  # update collections
+make pytest-cov                          # 100% coverage
+make lint-all                            # ruff + pyright + bandit + ansible-lint + checkmake + actionlint
+python3 -m devx.tools.check_pyproject_deps
+python3 -m devx.tools.check_test_speed --max-seconds 4 --max-single-seconds 0.5
+```
+
+If the dependency affects Ansible behavior, also run molecule:
+```bash
+make molecule    # 6 scenarios on Ubuntu 22.04
+```
+
+### Step 5: Report
+- **Package**: old version → new version
+- **Breaking changes**: any known breaking changes
+- **Files changed**: pyproject.toml, requirements.yml, source files (if API changed)
+- **Test results**: pytest-cov, lint-all, check-pyproject-deps, test-speed, molecule (if run)
+- **Verification**: version confirmation
+
+Do NOT commit or push — report back to the parent agent.
+
+## Feedback Reporting
+
+When you encounter a concrete issue with a tool, workflow, or process
+that would benefit from further investigation, create a Gitea issue
+in the `oblachno-oss/grm` repo.
+
+### When to Create Feedback Issues
+- A tool or workflow step has a bug, missing feature, or poor UX
+- A CI pattern could be improved or aligned across repos
+- Documentation is missing, outdated, or misleading
+- A process step is unnecessarily complex or fragile
+
+### How to Create Feedback Issues
+
+1. **Deduplicate first**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "list_issues", with `labels: "feedback"`, `owner: "oblachno-oss"`,
+   `repo: "grm"`. Check if an open issue already covers the same topic.
+   Do NOT create duplicates.
+
+2. **Create the issue**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "issue_write", method "create_issue", `owner: "oblachno-oss"`,
+   `repo: "grm"`:
+   - **Title**: `[feedback] <category>: <short description>`
+   - **Labels**: `feedback` + one of: `tooling`, `ci-improvement`,
+     `doc-improvement`, `workflow-improvement`
+   - **Body** must include these sections:
+     ```
+     **Context**: What task you were performing, which repo
+     **Tool/Workflow**: The specific tool or workflow step involved
+     **Issue**: What went wrong or could be improved
+     **Reproduction**: Steps to reproduce (if applicable)
+     **Affected files**: File paths and line numbers
+     **Suggested investigation**: What an agent should look into
+     **Reported by**: <subagent profile name>
+     ```
+
+3. **Report back**: Include the issue URL in your report to the parent agent.
+
+### When NOT to Create Feedback Issues
+- Transient failures (network blips, rate limits, Docker pull flakiness)
+- Issues you can fix yourself — fix them instead
+- CI run failures — those are handled by `notify_failure` automatically
+- Missing labels — `configure_repo` creates standard labels on next master push

.devin/agents/doc-syncer/AGENT.md

@@ -0,0 +1,134 @@
+---
+name: doc-syncer
+description: Handles documentation coverage, doc structure linting, and wiki sync for the grm repo. Detects missing docs, fixes broken links, updates mapping.json, and debugs wiki sync failures.
+model: glm-5.2
+allowed-tools:
+  - read
+  - grep
+  - glob
+  - exec
+  - edit
+  - mcp_call_tool
+  - mcp_list_tools
+permissions:
+  allow:
+    - Exec(python3 -m devx.ci.doc_coverage *)
+    - Exec(python3 -m devx.ci.lint_docs *)
+    - Exec(python3 -m devx.ci.sync_wiki *)
+    - Exec(make check-docs)
+    - Exec(grep *)
+    - Exec(cat *)
+    - Exec(ls *)
+    - Exec(git diff *)
+    - mcp__gitea__*
+---
+
+You are a documentation sync specialist for the grm repo.
+
+## Working Directory
+
+The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first.
+
+## Documentation Structure
+
+```
+docs/
+├── index.md              # Wiki homepage
+├── mapping.json          # File-to-wiki-page title mapping (13 entries)
+├── user/                 # User documentation
+│   ├── getting-started.md
+│   ├── installation.md
+│   ├── cli-commands.md
+│   ├── troubleshooting.md
+│   └── faq.md
+└── tech/                 # Technical documentation
+    ├── architecture.md
+    ├── development-setup.md
+    ├── ci-cd-workflow.md
+    ├── testing-strategy.md
+    ├── decision-log.md
+    └── contributing.md
+```
+
+## Procedure
+
+### Step 1: Check documentation coverage
+```bash
+python3 -m devx.ci.doc_coverage --fail-on-missing
+```
+Fix undocumented CLI commands, modules, or CI scripts by adding entries
+to the appropriate docs file.
+
+### Step 2: Lint documentation structure
+```bash
+python3 -m devx.ci.lint_docs --root .
+```
+Fix: broken internal links, heading hierarchy skips, TODO/FIXME markers,
+trailing whitespace.
+
+### Step 3: Check for stale references
+```bash
+make check-docs
+```
+Update any references to files that were renamed or deleted.
+
+### Step 4: Verify wiki sync (if investigating a sync failure)
+```bash
+python3 -m devx.ci.sync_wiki --repo oblachno-oss/grm --strict
+```
+Check `docs/mapping.json` — every docs file should have a mapping entry.
+If adding a new docs file, add it to mapping.json with a wiki-compatible
+title (hyphens for spaces, no special characters).
+
+### Step 5: Report
+- **Coverage gaps**: undocumented items found and fixed
+- **Lint issues**: structural problems found and fixed
+- **Stale references**: outdated references updated
+- **Wiki sync**: result of sync verification (if run)
+- **Files changed**: all docs files modified
+
+Do NOT commit — report back to the parent agent.
+
+## Feedback Reporting
+
+When you encounter a concrete issue with a tool, workflow, or process
+that would benefit from further investigation, create a Gitea issue
+in the `oblachno-oss/grm` repo.
+
+### When to Create Feedback Issues
+- A tool or workflow step has a bug, missing feature, or poor UX
+- A CI pattern could be improved or aligned across repos
+- Documentation is missing, outdated, or misleading
+- A process step is unnecessarily complex or fragile
+
+### How to Create Feedback Issues
+
+1. **Deduplicate first**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "list_issues", with `labels: "feedback"`, `owner: "oblachno-oss"`,
+   `repo: "grm"`. Check if an open issue already covers the same topic.
+   Do NOT create duplicates.
+
+2. **Create the issue**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "issue_write", method "create_issue", `owner: "oblachno-oss"`,
+   `repo: "grm"`:
+   - **Title**: `[feedback] <category>: <short description>`
+   - **Labels**: `feedback` + one of: `tooling`, `ci-improvement`,
+     `doc-improvement`, `workflow-improvement`
+   - **Body** must include these sections:
+     ```
+     **Context**: What task you were performing, which repo
+     **Tool/Workflow**: The specific tool or workflow step involved
+     **Issue**: What went wrong or could be improved
+     **Reproduction**: Steps to reproduce (if applicable)
+     **Affected files**: File paths and line numbers
+     **Suggested investigation**: What an agent should look into
+     **Reported by**: <subagent profile name>
+     ```
+
+3. **Report back**: Include the issue URL in your report to the parent agent.
+
+### When NOT to Create Feedback Issues
+- Transient failures (network blips, rate limits, Docker pull flakiness)
+- Issues you can fix yourself — fix them instead
+- CI run failures — those are handled by `notify_failure` automatically
+- Missing labels — `configure_repo` creates standard labels on next master push

.devin/agents/molecule-runner/AGENT.md

@@ -0,0 +1,154 @@
+---
+name: molecule-runner
+description: Runs molecule test scenarios for the gitea-runner Ansible role and reports pass/fail with logs. Knows all 7 scenarios, 4 platforms, Docker prerequisites, and dynamic runner distribution.
+model: glm-5.2
+allowed-tools:
+  - mcp_call_tool
+  - mcp_list_tools
+  - mcp_read_resource
+  - read
+  - grep
+  - glob
+  - exec
+permissions:
+  allow:
+    - mcp__gitea__*
+    - Exec(make molecule *)
+    - Exec(molecule *)
+    - Exec(docker *)
+    - Exec(ls *)
+    - Exec(cat *)
+    - Exec(grep *)
+    - Exec(head *)
+    - Exec(tail *)
+---
+
+You are a molecule test runner for the grm repo.
+
+## Working Directory
+
+The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first.
+
+## Available Scenarios (7 total)
+
+| Scenario | Purpose | Makefile target |
+|----------|---------|-----------------|
+| default | Basic runner installation | `make molecule` (included) |
+| multi-instance | 2 runners on same host | `make molecule` (included) |
+| lifecycle | stop/disable/enable/start | `make molecule` (included) |
+| template-content | Rendered template verification | `make molecule` (included) |
+| deregister | Runner cleanup | `make molecule` (included) |
+| update | Binary update | `make molecule` (included) |
+| remove | Full removal (destroys container) | CI only (not in `make molecule`) |
+
+**Platforms** (4): ubuntu-2204, ubuntu-2404, debian-12, archlinux
+Platform list defined in `devx.molecule.platforms` (single source of truth).
+
+**Note**: `make molecule` runs 6 scenarios (excludes `remove`).
+`make molecule-all` runs 6 scenarios on all 4 platforms.
+CI discovers all 7 scenarios via `devx.molecule.distribute_molecule`.
+
+## Molecule Weights (for LPT distribution)
+
+Configured in `pyproject.toml` `[tool.devx.molecule.weights]`:
+```
+multi-instance = 8, lifecycle = 6, update = 5, default = 4,
+deregister = 3, remove = 3, template-content = 2
+```
+
+## Docker Prerequisites
+
+```bash
+docker info > /dev/null 2>&1 && echo "Docker ready" || echo "Docker not available"
+```
+
+If Docker is not running, report immediately — do not attempt to start it.
+
+## Running Tests
+
+When given a scenario name or "all":
+1. Verify Docker is running
+2. Run the appropriate make target
+3. Capture full output (do not truncate)
+4. Parse results
+
+For a single scenario:
+```bash
+molecule test -s <scenario>
+```
+
+For all scenarios on one platform:
+```bash
+make molecule
+```
+
+For all scenarios on all platforms:
+```bash
+make molecule-all
+```
+
+## Known Issues
+
+- `ansible-lint` may warn about `command-instead-of-module` for `systemctl --user`
+  calls — this is expected (systemd module doesn't support user services) and
+  skipped in `.ansible-lint`
+- Molecule Docker driver may print "Event loop is closed" warnings on interrupt — harmless
+
+## Reporting
+
+Report:
+- **PASSED**: scenario name, platform, duration
+- **FAILED**: scenario name, platform, the failing Ansible task, error message, file:line
+- **SKIPPED**: if Docker was unavailable
+
+For failures, extract:
+- The Ansible task: `TASK [gitea-runner : task_name]` followed by `FAILED!`
+- The error detail: the `msg` field in the JSON output
+- The molecule verify step: look for `VERIFY` section
+- Platform-specific failures: note if only one OS failed
+
+Do NOT attempt to fix failures — report them with enough detail for the parent agent.
+
+## Feedback Reporting
+
+When you encounter a concrete issue with a tool, workflow, or process
+that would benefit from further investigation, create a Gitea issue
+in the `oblachno-oss/grm` repo.
+
+### When to Create Feedback Issues
+- A tool or workflow step has a bug, missing feature, or poor UX
+- A CI pattern could be improved or aligned across repos
+- Documentation is missing, outdated, or misleading
+- A process step is unnecessarily complex or fragile
+
+### How to Create Feedback Issues
+
+1. **Deduplicate first**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "list_issues", with `labels: "feedback"`, `owner: "oblachno-oss"`,
+   `repo: "grm"`. Check if an open issue already covers the same topic.
+   Do NOT create duplicates.
+
+2. **Create the issue**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "issue_write", method "create_issue", `owner: "oblachno-oss"`,
+   `repo: "grm"`:
+   - **Title**: `[feedback] <category>: <short description>`
+   - **Labels**: `feedback` + one of: `tooling`, `ci-improvement`,
+     `doc-improvement`, `workflow-improvement`
+   - **Body** must include these sections:
+     ```
+     **Context**: What task you were performing, which repo
+     **Tool/Workflow**: The specific tool or workflow step involved
+     **Issue**: What went wrong or could be improved
+     **Reproduction**: Steps to reproduce (if applicable)
+     **Affected files**: File paths and line numbers
+     **Suggested investigation**: What an agent should look into
+     **Reported by**: <subagent profile name>
+     ```
+
+3. **Report back**: Include the issue URL in your report to the parent agent.
+
+### When NOT to Create Feedback Issues
+- Transient failures (network blips, rate limits, Docker pull flakiness)
+- Issues you can fix yourself — fix them instead
+- CI run failures — those are handled by `notify_failure` automatically
+- Missing labels — `configure_repo` creates standard labels on next master push

.devin/agents/workflow-validator/AGENT.md

@@ -0,0 +1,150 @@
+---
+name: workflow-validator
+description: Validates Gitea Actions workflow YAML files for the grm repo using actionlint and act_runner dry-run. Fixes syntax errors, job dependency issues, and molecule distribution matrix problems.
+model: glm-5.2
+allowed-tools:
+  - mcp_call_tool
+  - mcp_list_tools
+  - mcp_read_resource
+  - read
+  - grep
+  - glob
+  - exec
+  - edit
+permissions:
+  allow:
+    - mcp__gitea__*
+    - Exec(make workflow-lint)
+    - Exec(make workflow-dryrun)
+    - Exec(make workflow-check)
+    - Exec(make install-tools)
+    - Exec(actionlint *)
+    - Exec(act_runner *)
+    - Exec(cat *)
+    - Exec(grep *)
+    - Exec(git diff *)
+---
+
+You are a Gitea Actions workflow validator for the grm repo.
+
+## Working Directory
+
+The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first.
+
+## Key Files
+
+- `.gitea/workflows/ci.yml` — PR pipeline (quality, detect-changes, pre-merge-check, discover-runners, molecule-tests, molecule-report, release-dry-run, pr-review, auto-merge)
+- `.gitea/workflows/post-merge.yml` — master pipeline (detect-type, validate-commit-msg, release, publish, sync-wiki, badges, vikunja, configure-repo)
+- `.gitea/actionlint.yaml` — actionlint config (registers custom `docker` runner label)
+
+## Validation Procedure
+
+### Step 1: Install tools (if not present)
+```bash
+make install-tools  # installs actionlint, act_runner to ~/.local/bin
+```
+
+### Step 2: Static lint with actionlint
+```bash
+make workflow-lint
+```
+Fix any: syntax errors, invalid expressions, unknown keys, shellcheck issues,
+undefined variables, unknown actions, job dependency issues.
+
+### Step 3: Dry-run with act_runner
+```bash
+make workflow-dryrun
+```
+Fix any: image not found, circular dependencies, step ordering issues,
+matrix expansion problems.
+
+### Step 4: Full check
+```bash
+make workflow-check
+```
+
+## GRM-Specific Workflow Concerns
+
+**Molecule test distribution:**
+The `molecule-tests` job uses a matrix `[1, 2, 3, 4, 5, 6, 7, 8, 9, 10]`
+with `max-parallel: 3`. Runners beyond the discovered count skip via
+`--skip-if-excess`. The `discover-runners` job queries the Gitea API
+for available runners.
+
+If the matrix is too small, some scenarios won't run. If too large,
+excess runners skip (no harm). The default 10 slots should be enough.
+
+**Path filtering:**
+Molecule tests only run when `ansible/` or `.ansible-lint` files change.
+The `detect-changes` job sets `ansible-changed` output. If this is false,
+molecule-tests is skipped — this is expected behavior.
+
+**auto-merge and always():**
+```yaml
+auto-merge:
+  needs: [quality, detect-changes, pre-merge-check, pr-review, molecule-tests]
+  if: >-
+    always() &&
+    github.event_name == 'pull_request' &&
+    needs.quality.result == 'success' &&
+    needs.pre-merge-check.result == 'success' &&
+    needs.pr-review.result == 'success' &&
+    (needs.molecule-tests.result == 'success' || needs.molecule-tests.result == 'skipped')
+```
+
+**Gitea Actions limitations (1.26.x):**
+- No `fromJSON()` in matrix context
+- `concurrency` blocks can cause stuck jobs
+- `GITHUB_OUTPUT` for step outputs
+
+## Report
+- **actionlint results**: pass/fail per workflow file, specific errors
+- **dry-run results**: pass/fail per workflow, job dependency issues
+- **Files changed**: if any workflow YAML was modified
+- **Verification**: re-run results after fixes
+
+Do NOT commit — report back to the parent agent.
+
+## Feedback Reporting
+
+When you encounter a concrete issue with a tool, workflow, or process
+that would benefit from further investigation, create a Gitea issue
+in the `oblachno-oss/grm` repo.
+
+### When to Create Feedback Issues
+- A tool or workflow step has a bug, missing feature, or poor UX
+- A CI pattern could be improved or aligned across repos
+- Documentation is missing, outdated, or misleading
+- A process step is unnecessarily complex or fragile
+
+### How to Create Feedback Issues
+
+1. **Deduplicate first**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "list_issues", with `labels: "feedback"`, `owner: "oblachno-oss"`,
+   `repo: "grm"`. Check if an open issue already covers the same topic.
+   Do NOT create duplicates.
+
+2. **Create the issue**: Use `mcp_call_tool` with server_name "gitea",
+   tool_name "issue_write", method "create_issue", `owner: "oblachno-oss"`,
+   `repo: "grm"`:
+   - **Title**: `[feedback] <category>: <short description>`
+   - **Labels**: `feedback` + one of: `tooling`, `ci-improvement`,
+     `doc-improvement`, `workflow-improvement`
+   - **Body** must include these sections:
+     ```
+     **Context**: What task you were performing, which repo
+     **Tool/Workflow**: The specific tool or workflow step involved
+     **Issue**: What went wrong or could be improved
+     **Reproduction**: Steps to reproduce (if applicable)
+     **Affected files**: File paths and line numbers
+     **Suggested investigation**: What an agent should look into
+     **Reported by**: <subagent profile name>
+     ```
+
+3. **Report back**: Include the issue URL in your report to the parent agent.
+
+### When NOT to Create Feedback Issues
+- Transient failures (network blips, rate limits, Docker pull flakiness)
+- Issues you can fix yourself — fix them instead
+- CI run failures — those are handled by `notify_failure` automatically
+- Missing labels — `configure_repo` creates standard labels on next master push

.devin/skills/devx-workflow/SKILL.md

@@ -0,0 +1,38 @@
+# devx-workflow
+
+Quick reference for devx tools when working on this repo.
+
+## PR Workflow (use these, not raw git/tea/MCP)
+
+| Task | Command |
+|------|---------|
+| Create Vikunja task | `make create-task -- --title "..." --description "..."` |
+| Create PR | `make create-pr` |
+| Push + create PR | `make push-with-pr` |
+| Check CI status | `make devx-pr-status` or `make devx-pr-status PR=42 WAIT=1` |
+| Fetch CI failure logs | `make devx-pr-logs` or `make devx-pr-logs PR=42 JOB=quality TAIL=50` |
+| Add ready-to-merge label | `make devx-pr-label` or `make devx-pr-label PR=42` |
+| Post PR review | `make devx-pr-review PR=42 EVENT=APPROVE BODY="..." CHECKLIST=1,2,3,4,5,6,7,8,9,10,11,12,13` |
+| Rebase current branch | `make rebase` |
+| Rebase PR via API | `make pr-rebase` or `make pr-rebase PR=42` |
+
+## Auto-merge Behavior
+
+When the `ready-to-merge` label is added and all CI checks pass:
+1. Auto-merge validates PR title format (`GRM-N: <vikunja task title>`)
+2. If branch is behind master, auto-merge **rebases via Gitea API** automatically
+3. The rebase triggers a new CI run; the next auto-merge attempt merges
+4. No manual rebase needed unless the API rebase fails
+
+## Pre-merge Check
+
+CI runs a `pre-merge-check` job early (after quality + detect-changes)
+that validates branch format, PR title, and Vikunja task match.
+This fails fast before expensive molecule tests run.
+
+## Key Rules
+
+- Never manually merge via API — always use auto-merge with `ready-to-merge` label
+- Branch naming: `GRM-N-short-description` (N = Vikunja task ID)
+- Commit format: conventional commits (`feat:`, `fix:`, `docs:`, etc.)
+- PR title: `GRM-N: <vikunja task title>` (auto-derived by `make create-pr`)

.env.example

@@ -0,0 +1,63 @@
+# Gitea instance URL (used for runner registration and API validation)
+GITEA_URL=https://git.example.com
+
+# Runner registration token from Gitea.
+# Three levels are available:
+#   Instance-level:  Site Administration → Actions → Runners → Create Registration Token
+#   Org-level:       Organization → Settings → Actions → Runners → Create Registration Token
+#   Repo-level:      Repository → Settings → Actions → Runners → Create Registration Token
+GITEA_REGISTRATION_TOKEN=your-registration-token
+
+# Gitea admin API token for optional post-install API checks (informational only).
+# The integration test primarily verifies the runner by checking:
+#   1. The .runner registration file exists and is valid
+#   2. The container/service is running
+# If set, API checks are performed as a bonus but do NOT affect pass/fail.
+# Required scopes: read:user, read:repository, read:admin (or just "admin")
+# Generate token at: Settings → Applications → Generate New Token
+# CI_GITEA_TOKEN=your-admin-api-token
+
+# Integration test API retries (optional, default: 3).
+# Number of times to retry API checks waiting for runner to appear.
+# GITEA_INTEGRATION_RETRIES=3
+
+# Default SSH user for remote hosts (optional, overrides --user)
+# GITEA_RUNNER_USER=ubuntu
+
+# Repository for grm trigger-workflow (optional, default: oblachno-oss/grm)
+# GRM_REPO=oblachno-oss/grm
+
+# Default SSH private key path (optional, overrides --key)
+# GITEA_RUNNER_KEY=~/.ssh/id_ed25519
+
+# Default runner labels for Gitea Actions (optional, overrides --labels)
+# Format: <label>:<docker-image>[:<command>]
+# Use an official Gitea runner image with Node.js, Python and Docker CLI.
+# Avoid bare OS images like alpine:latest because actions/checkout@v4 needs Node.
+# GITEA_RUNNER_LABELS=docker:docker://gitea/runner-images:ubuntu-latest
+
+# UI language for GRM console messages (optional, default: en)
+# Supported: en, bg, de, ru, zh, pl
+# GRM_LANG=en
+
+# Sudo password file for Ansible become operations (optional)
+# When set, GRM reads the sudo password from this file instead of prompting.
+# Priority: --become-password-file CLI flag > GRM_BECOME_PASSWORD_FILE > ANSIBLE_BECOME_PASSWORD_FILE
+# GRM_BECOME_PASSWORD_FILE=~/.grm-sudo-pass
+# ANSIBLE_BECOME_PASSWORD_FILE=~/.grm-sudo-pass
+
+# Gitea PyPI registry username (for private package access)
+# Used by PIP_INSTALL to configure PIP_EXTRA_INDEX_URL
+CI_GITEA_USERNAME=emil
+
+# Vikunja API token (required for `make create-task` dev workflow)
+# Generate at: Vikunja → Settings → API Tokens
+# VIKUNJA_TOKEN=your-vikunja-api-token
+
+# devx configuration (GRM-specific overrides)
+# Task prefix for Vikunja task IDs
+DEVX_TASK_PREFIX=GRM
+# Vikunja project ID for GRM
+DEVX_VIKUNJA_PROJECT_ID=6
+# Version file path (relative to repo root)
+DEVX_VERSION_FILE=src/gitea_runner_manager/__init__.py

.gitea/actionlint.yaml

@@ -0,0 +1,9 @@
+# actionlint configuration for Gitea Actions workflows
+# https://github.com/rhysd/actionlint/blob/main/docs/config.md
+#
+# Run: actionlint -config-file .gitea/actionlint.yaml .gitea/workflows/*.yml
+
+# Custom self-hosted runner labels used in runs-on
+self-hosted-runner:
+  labels:
+    - docker

.gitea/workflows/ci.yml

@@ -0,0 +1,330 @@
+name: CI
+
+on:
+  pull_request:
+    types: [opened, synchronize]
+  workflow_dispatch:
+
+env:
+  CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+  CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+
+jobs:
+  quality:
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-quality:latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=lint
+      - name: Lint all
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          export PATH="$HOME/.local/bin:$PATH"
+          make lint-all
+      - name: Unit tests with 100% coverage
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          make pytest-cov
+      - name: Documentation lint check
+        env:
+          PYTHONPATH: src
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          pip install --upgrade devx \
+            --index-url "https://${CI_GITEA_USERNAME}:${CI_GITEA_TOKEN}@git.oblachno.oblachno.fyi/api/packages/oblachno-oss/pypi/simple/" \
+            --no-deps
+          python3 -m devx.ci.lint_docs --root .
+      - name: Translation completeness check
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.check_translations --translations src/gitea_runner_manager/translations.json
+      - name: Check unit test speed
+        env:
+          PYTHONPATH: src
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.tools.check_test_speed --max-seconds 4 --max-single-seconds 0.5
+      - name: Dependency security scan
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          # Install pip in venv if missing (needed by pip-audit)
+          .venv/bin/python -m ensurepip 2>/dev/null || true
+          PIPAPI_PYTHON_LOCATION=$PWD/.venv/bin/python \
+            pip-audit --desc --skip-editable 2>&1 || true
+      - name: Workflow dry-run validation
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          export PATH="$HOME/.local/bin:$PATH"
+          # Best-effort: only runs if act_runner is installed
+          if command -v act_runner >/dev/null 2>&1; then
+            make workflow-dryrun
+          else
+            echo "act_runner not found — skipping workflow dry-run (static lint still passed)"
+          fi
+
+  release-dry-run:
+    needs: [quality, detect-changes]
+    if: needs.detect-changes.outputs.user-facing-changed == 'true'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-full:latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci,lint
+      - name: Release dry-run validation
+        env:
+          PYTHONPATH: src
+          DEVX_VERSION_FILE: src/gitea_runner_manager/__init__.py
+          DEVX_TASK_PREFIX: GRM
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          export PATH="$HOME/.local/bin:$PATH"
+          python3 -m devx.ci.release --dry-run
+
+  detect-changes:
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 10
+    outputs:
+      ansible-changed: ${{ steps.detect.outputs.ansible-changed }}
+      user-facing-changed: ${{ steps.detect.outputs.user-facing-changed }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci
+      - name: Detect changed paths
+        id: detect
+        env:
+          PYTHONPATH: src
+          DEVX_TASK_PREFIX: GRM
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.classify_changes \
+            --base "origin/master" \
+            --head "${{ github.event.pull_request.head.sha || github.sha }}" \
+            --github-output
+
+  pre-merge-check:
+    needs: [quality, detect-changes]
+    if: github.event_name == 'pull_request'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Set up environment
+        run: make setup-image EXTRAS=ci
+      - name: Validate auto-merge preconditions
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          VIKUNJA_TOKEN: ${{ secrets.VIKUNJA_TOKEN }}
+          DEVX_TASK_PREFIX: GRM
+          DEVX_VIKUNJA_PROJECT_ID: 6
+          HEAD_REF: ${{ github.head_ref }}
+          PR_TITLE: ${{ github.event.pull_request.title }}
+          REPOSITORY: ${{ github.repository }}
+          PR_NUMBER: ${{ github.event.number }}
+          PYTHONPATH: ${{ env.PYTHONPATH }}
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.check_auto_merge_ready \
+            --branch "$HEAD_REF" \
+            --pr-title "$PR_TITLE" \
+            --repo "$REPOSITORY" \
+            --pr-number "$PR_NUMBER"
+
+  discover-runners:
+    needs: [detect-changes]
+    if: needs.detect-changes.outputs.ansible-changed == 'true'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 10
+    outputs:
+      runner-count: ${{ steps.discover.outputs.runner-count }}
+      runner-indices: ${{ steps.discover.outputs.runner-indices }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci
+      - name: Discover available runners
+        id: discover
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          MOLECULE_RUNNERS: ${{ vars.MOLECULE_RUNNERS }}
+          PYTHONPATH: src
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.molecule.discover_runners \
+            --owner "${{ github.repository_owner }}" \
+            --repo "${{ github.event.repository.name }}" \
+            --github-output
+
+  molecule-tests:
+    needs: [quality, detect-changes, discover-runners]
+    if: needs.detect-changes.outputs.ansible-changed == 'true'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-full:latest
+    timeout-minutes: 10
+    strategy:
+      fail-fast: true
+      max-parallel: 3
+      matrix:
+        runner-index: [1, 2, 3, 4, 5, 6]
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci,molecule
+      - name: Install Ansible collections
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.tools.setup --skip-install --no-pre-commit --no-tea-login
+      - name: Discover assigned test pairs
+        env:
+          RUNNER_INDEX: ${{ matrix.runner-index }}
+          MAX_RUNNERS: ${{ needs.discover-runners.outputs.runner-count }}
+          PYTHONPATH: src
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.molecule.distribute_molecule \
+            --runner-index "$RUNNER_INDEX" \
+            --max-runners "$MAX_RUNNERS" \
+            --github-env --skip-if-excess
+      - name: Run molecule tests
+        if: env.SKIP != 'true'
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          if [ -z "$TEST_PAIRS" ]; then exit 0; fi
+          if ! python3 -c "import docker; docker.from_env().ping()" 2>/dev/null; then
+            echo "Docker not available in CI container — skipping molecule tests"
+            exit 0
+          fi
+          echo "$CI_GITEA_TOKEN" | docker login git.oblachno.oblachno.fyi -u "$CI_GITEA_USERNAME" --password-stdin
+          # shellcheck disable=SC2086 # intentional word splitting for argument expansion
+          python3 -m devx.molecule.molecule_ci_guard $TEST_PAIRS
+        env:
+          GITEA_URL: ${{ github.server_url }}
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+          RUN_ID: ${{ github.run_id }}
+          ANSIBLE_INJECT_INVOCATION: "1"
+          JOB_NAME: ${{ github.job }}
+          MATRIX_INDEX: ${{ matrix.runner-index }}
+          GITEA_REPOSITORY: ${{ github.repository }}
+          PYTHONPATH: src
+          DOCKER_HOST: unix:///var/run/docker.sock
+
+  pr-review:
+    if: github.event_name == 'pull_request'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 10
+    defaults:
+      run:
+        shell: bash
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci
+      - name: Run automated PR review
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+        run: |
+          set -euo pipefail
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.pr_review \
+            "${{ github.event.number }}" \
+            "${{ github.repository }}"
+
+  auto-merge:
+    # Auto-merge runs after all CI checks pass. It reads the task ID
+    # from the branch name, validates the PR title, and squash-merges.
+    # Uses always() so it evaluates even when molecule-tests is skipped
+    # (Gitea Actions skips dependent jobs of skipped jobs by default).
+    needs: [quality, detect-changes, pre-merge-check, pr-review, molecule-tests, release-dry-run]
+    if: >-
+      always() &&
+      github.event_name == 'pull_request' &&
+      needs.quality.result == 'success' &&
+      needs.pre-merge-check.result == 'success' &&
+      needs.pr-review.result == 'success' &&
+      (needs.molecule-tests.result == 'success' || needs.molecule-tests.result == 'skipped') &&
+      (needs.release-dry-run.result == 'success' || needs.release-dry-run.result == 'skipped')
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 10
+    defaults:
+      run:
+        shell: bash
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.CI_GITEA_TOKEN }}
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci
+      - name: Post approval review
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.REVIEW_GITEA_TOKEN }}
+          PR_NUMBER: ${{ github.event.number }}
+          REPOSITORY: ${{ github.repository }}
+          PYTHONPATH: src
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.pr_review \
+            "$PR_NUMBER" \
+            "$REPOSITORY" \
+            --event APPROVE \
+            --checklist-confirmed \
+            --checklist-categories 1,2,3,4,5,6,7,8,9,10,11,12,13 \
+            --body "Auto-approved: all CI checks passed (quality, molecule, pr-review, pre-merge-check)."
+      - name: Squash merge with task ID
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          VIKUNJA_TOKEN: ${{ secrets.VIKUNJA_TOKEN }}
+          PYTHONPATH: src
+          DEVX_TASK_PREFIX: GRM
+          DEVX_VIKUNJA_PROJECT_ID: 6
+          HEAD_REF: ${{ github.head_ref }}
+          PR_TITLE: ${{ github.event.pull_request.title }}
+          REPOSITORY: ${{ github.repository }}
+          PR_NUMBER: ${{ github.event.number }}
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.auto_merge \
+            "$HEAD_REF" \
+            "$PR_TITLE" \
+            "$REPOSITORY" \
+            "$PR_NUMBER"

.gitea/workflows/post-merge.yml

@@ -0,0 +1,320 @@
+name: Post-merge
+
+# Runs on every push to master. A single workflow with conditional jobs
+# for release, publish, wiki sync, badges, and Vikunja task updates.
+#
+# Job dependency graph:
+#
+#   detect-type ──┬── validate-commit-msg (skip if release commit)
+#                 ├── release (skip if release commit)
+#                 │   └── publish (needs release — builds & publishes to PyPI)
+#                 ├── badges (ALWAYS runs — even on release commits)
+#                 ├── configure-repo (independent — skip if release commit)
+#                 ├── sync-wiki (skip if release commit — runs for ALL merges)
+#                 └── vikunja (skip if release commit — runs for ALL merges)
+#
+# sync-wiki and vikunja run for ALL non-release commits, not just when
+# release succeeds. This ensures the wiki and task tracker are updated
+# even for infrastructure-only changes (docs, CI config, etc.).
+#
+# The badges job uses `if: always()` with no is-release condition so it
+# runs on every push to master, including release commits. This ensures
+# badges (tests, coverage, version, etc.) are always current.
+#
+# When release creates a "release: vX.Y.Z" commit and tag, the publish
+# job (which depends on release) builds and publishes the package to the
+# Gitea PyPI registry. The release commit's post-merge run still updates
+# badges (version badge picks up the new version). Other jobs skip.
+
+on:
+  push:
+    branches: [master]
+  workflow_dispatch:
+
+env:
+  CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+  CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+
+jobs:
+  detect-type:
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 10
+    outputs:
+      is-release: ${{ steps.check.outputs.is-release }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci
+      - name: Check if this is a release commit
+        id: check
+        env:
+          PYTHONPATH: src
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.detect_release_commit
+
+  validate-commit-msg:
+    needs: [detect-type]
+    if: needs.detect-type.outputs.is-release == 'false'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci
+      - name: Validate latest commit message
+        env:
+          PYTHONPATH: src
+          DEVX_TASK_PREFIX: GRM
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          git log -1 --format=%B > commit-msg.txt
+          python3 -m devx.ci.validate_commit_msg commit-msg.txt --branch master
+          rm -f commit-msg.txt
+
+  release:
+    needs: [detect-type]
+    if: needs.detect-type.outputs.is-release == 'false'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-full:latest
+    timeout-minutes: 15
+    outputs:
+      tag: ${{ steps.release-tag.outputs.tag }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.CI_GITEA_TOKEN }}
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci,lint
+      - name: Configure git
+        run: |
+          git config user.name "grm-ci-bot"
+          git config user.email "grm-ci-bot@oblachno.fyi"
+      - name: Run release
+        id: release-tag
+        env:
+          PYTHONPATH: src
+          DEVX_VERSION_FILE: src/gitea_runner_manager/__init__.py
+          DEVX_TASK_PREFIX: GRM
+          DEVX_VIKUNJA_PROJECT_ID: 6
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          export PATH="$HOME/.local/bin:$PATH"
+          python3 -m devx.ci.release
+      - name: Notify on failure
+        if: failure()
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          export PATH="$HOME/.local/bin:$PATH"
+          python3 -m devx.ci.notify_failure --auto-login \
+            --repo "${{ github.repository }}" \
+            --run-id "${{ github.run_id }}" \
+            --workflow "post-merge/release" \
+            --commit "${{ github.sha }}"
+
+  publish:
+    needs: [release]
+    if: needs.release.outputs.tag != ''
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-full:latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          ref: ${{ needs.release.outputs.tag }}
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci,lint
+      - name: Build and publish release
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          export PATH="$HOME/.local/bin:$PATH"
+          python3 -m devx.ci.publish \
+            "${{ needs.release.outputs.tag }}" \
+            "${{ github.repository }}" --auto-login
+      - name: Notify on failure
+        if: failure()
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          export PATH="$HOME/.local/bin:$PATH"
+          python3 -m devx.ci.notify_failure --auto-login \
+            --repo "${{ github.repository }}" \
+            --run-id "${{ github.run_id }}" \
+            --workflow "post-merge/publish" \
+            --commit "${{ github.sha }}"
+
+  sync-wiki:
+    needs: [detect-type]
+    if: needs.detect-type.outputs.is-release == 'false'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci
+      - name: Sync documentation to wiki
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.sync_wiki --repo "${{ github.repository }}" --strict
+      - name: Notify on failure
+        if: failure()
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+        run: |
+          export PATH="$HOME/.local/bin:$PATH"
+          python3 -m devx.ci.notify_failure --auto-login \
+            --repo "${{ github.repository }}" \
+            --run-id "${{ github.run_id }}" \
+            --workflow "post-merge/sync-wiki" \
+            --commit "${{ github.sha }}"
+
+  badges:
+    needs: [detect-type]
+    if: always()
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-quality:latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          ref: master
+          token: ${{ secrets.CI_GITEA_TOKEN }}
+      - name: Fetch latest master
+        run: |
+          git fetch origin master
+          git reset --hard origin/master
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=lint
+      - name: Generate and push badges
+        env:
+          PRE_COMMIT_ALLOW_NO_CONFIG: "1"
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.push_badges
+      - name: Notify on failure
+        if: failure()
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+        run: |
+          export PATH="$HOME/.local/bin:$PATH"
+          python3 -m devx.ci.notify_failure --auto-login \
+            --repo "${{ github.repository }}" \
+            --run-id "${{ github.run_id }}" \
+            --workflow "post-merge/badges" \
+            --commit "${{ github.sha }}"
+
+  vikunja:
+    needs: [detect-type]
+    if: needs.detect-type.outputs.is-release == 'false'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci
+      - name: Update Vikunja task
+        env:
+          VIKUNJA_TOKEN: ${{ secrets.VIKUNJA_TOKEN }}
+          PYTHONPATH: src
+          DEVX_TASK_PREFIX: GRM
+          DEVX_VIKUNJA_PROJECT_ID: 6
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.ci.post_merge --git-sha "${{ github.sha }}"
+      - name: Notify on failure
+        if: failure()
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+        run: |
+          export PATH="$HOME/.local/bin:$PATH"
+          python3 -m devx.ci.notify_failure --auto-login \
+            --repo "${{ github.repository }}" \
+            --run-id "${{ github.run_id }}" \
+            --workflow "post-merge/vikunja" \
+            --commit "${{ github.sha }}"
+
+  configure-repo:
+    needs: [detect-type]
+    if: needs.detect-type.outputs.is-release == 'false'
+    runs-on: docker
+    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up environment
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
+        run: make setup-image EXTRAS=ci
+      - name: Ensure branch protection and labels
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+          DEVX_REPO_NAME: grm
+          DEVX_REPO_OWNER: oblachno-oss
+          DEVX_STATUS_CHECKS: "CI / quality (pull_request),CI / molecule-tests (1) (pull_request),CI / molecule-tests (2) (pull_request),CI / molecule-tests (3) (pull_request)"
+        run: |
+          . .venv/bin/activate 2>/dev/null || true
+          python3 -m devx.tools.configure_repo
+      - name: Notify on failure
+        if: failure()
+        env:
+          CI_GITEA_TOKEN: ${{ secrets.CI_GITEA_TOKEN }}
+          PYTHONPATH: src
+        run: |
+          export PATH="$HOME/.local/bin:$PATH"
+          python3 -m devx.ci.notify_failure --auto-login \
+            --repo "${{ github.repository }}" \
+            --run-id "${{ github.run_id }}" \
+            --workflow "post-merge/configure-repo" \
+            --commit "${{ github.sha }}"

.gitignore

@@ -0,0 +1,43 @@
+# Environment
+.env
+.venv/
+venv/
+
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.egg-info/
+dist/
+build/
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# Ansible
+*.retry
+.molecule/
+
+# Coverage
+.coverage
+htmlcov/
+
+# Security scanner
+.bandit
+bandit-report.*
+
+# Misc
+*.log
+.DS_Store
+activate.sh
+activate.fish
+activate.zsh
+
+# Generated badges (CI pushes to badges branch)
+.badges/
+
+# Deprecated CI task tracking (branch name is the sole source of truth)
+.taskid

.pre-commit-config.yaml

@@ -0,0 +1,66 @@
+repos:
+  - repo: local
+    hooks:
+      - id: validate-commit-msg
+        name: validate commit message
+        entry: env PYTHONPATH=src .venv/bin/python -m devx.ci.validate_commit_msg
+        language: system
+        stages: [commit-msg]
+        pass_filenames: true
+
+      - id: lint-ruff
+        name: ruff lint
+        entry: make lint-ruff
+        language: system
+        types: [python]
+        pass_filenames: false
+        stages: [pre-commit]
+
+      - id: lint-format
+        name: ruff format check
+        entry: make lint-format
+        language: system
+        types: [python]
+        pass_filenames: false
+        stages: [pre-commit]
+
+      - id: typecheck
+        name: pyright type check
+        entry: make typecheck
+        language: system
+        types: [python]
+        pass_filenames: false
+        stages: [pre-commit]
+
+      - id: lint-bandit
+        name: bandit security scan
+        entry: make lint-bandit
+        language: system
+        types: [python]
+        pass_filenames: false
+        stages: [pre-commit]
+
+      - id: ansible-lint
+        name: ansible-lint
+        entry: make ansible-lint
+        language: system
+        types: [yaml]
+        pass_filenames: false
+        stages: [pre-commit]
+
+      - id: workflow-lint
+        name: actionlint (workflow YAML)
+        entry: make workflow-lint
+        language: system
+        files: ^\.gitea/workflows/
+        types: [yaml]
+        pass_filenames: false
+        stages: [pre-commit]
+
+      - id: pytest-cov
+        name: pytest with 100% coverage
+        entry: make pytest-cov
+        language: system
+        types: [python]
+        pass_filenames: false
+        stages: [pre-push]

.python-version

@@ -0,0 +1 @@
+3.12

AGENTS.md

@@ -0,0 +1,572 @@
+# AGENTS.md — Project Conventions for GRM
+
+## Build & Test Commands
+
+```bash
+make setup          # Create venv, install deps, set up hooks, install CI tools
+make install-tools  # Install actionlint, git-cliff, act_runner to ~/.local/bin
+make lint-all       # ruff + pyright + bandit + ansible-lint + checkmake + actionlint
+make pytest-cov     # Unit tests with 100% coverage enforcement
+make test-unit      # Unit tests without coverage
+make molecule       # All 6 scenarios on Ubuntu 22.04
+make molecule-all   # All 6 scenarios on all 4 supported OSes
+make test-all       # pytest-cov + molecule
+make workflow-lint  # Static lint of .gitea/workflows/*.yml (actionlint)
+make workflow-dryrun # Dry-run all workflows in Docker (act_runner exec --dryrun)
+make workflow-check # workflow-lint + workflow-dryrun
+```
+
+`make setup` automatically installs all development tools:
+- **Python deps** via `pip install -e .[dev]` (includes devx from Gitea PyPI registry, configured by `make configure-gitea-pypi`)
+- **Post-install setup** via `devx.tools.setup --skip-install` (ansible-galaxy, pre-commit hooks, tea CLI login)
+- **checkmake** via `devx.tools.install_checkmake` (Makefile linter)
+- **actionlint, git-cliff, act_runner, tea** via `devx.tools.install_tools` (CI/CD tools to ~/.local/bin)
+
+## Workflow Verification (Before Push)
+
+Workflow YAML files (`.gitea/workflows/*.yml`) are verified with two tools:
+
+1. **actionlint** — Static linter that catches syntax errors, invalid
+   expressions, unknown keys, type mismatches, and shellcheck issues.
+   Config: `.gitea/actionlint.yaml` (registers custom `docker` runner label).
+   Installed automatically by `make setup` via `devx.tools.install_tools`.
+
+2. **act_runner exec --dryrun** — Gitea's own runner in dry-run mode.
+   Validates job dependencies, step ordering, and Docker image selection
+   without starting containers. Installed automatically by `make setup`.
+
+Both run via `make workflow-check` and are part of `make lint-all`.
+The pre-commit hook runs actionlint automatically when workflow files change.
+The CI `quality` job runs `make setup` (which installs all tools) then `make lint-all`.
+CI also runs a best-effort `make workflow-dryrun` step (skipped if act_runner is not installed in the CI Docker image).
+
+## Architecture
+
+- **Python CLI** (`src/gitea_runner_manager/`) — Click-based CLI that delegates to Ansible
+- **Ansible Role** (`ansible/roles/gitea-runner/`) — Idempotent role for rootless Docker runner setup
+- **devx package** (installed from git) — Reusable CI/CD tools: auto-merge, post-merge, release, publishing, molecule distribution, PR reviews, failure notifications
+- **Versioning** (`cliff.toml`) — git-cliff configuration for automated semver versioning from conventional commits
+
+## PR Workflow (Mandatory)
+
+Every change to master goes through this workflow. No exceptions.
+
+### Branch Protection (Required Gitea Settings)
+
+Branch protection and labels are automatically configured by
+`devx.tools.configure_repo` (run as `python -m devx.tools.configure_repo`),
+which runs as a `configure-repo` job in
+the post-merge workflow on every push to master.
+
+The following rules are enforced for `master`:
+- **Require pull request**: No direct pushes to master
+- **Require approval review**: At least 1 `APPROVE` review before merge
+- **Require status checks**: CI quality + molecule tests must pass
+- **Block force pushes**: No history rewriting on master
+
+The auto-merge workflow enforces the APPROVE review check programmatically
+as a defense-in-depth measure, but branch protection is the primary gate.
+
+### 1. Create Vikunja Task
+Create a task in Vikunja project 6 via `make create-task -- --title "Task title" --description "<h2>...</h2>"` (requires `VIKUNJA_TOKEN` in `.env`). This prints the `GRM-N` identifier and next-step instructions.
+
+### 2. Create Branch
+```bash
+git checkout master && git pull
+git checkout -b GRM-N-short-description
+```
+
+### 3. Implement Changes
+- Write code following conventions below
+- Write/update tests (100% coverage required)
+- Update documentation (CHANGELOG, README, AGENTS.md as needed)
+
+### 4. Commit (Conventional Commits)
+Branch commits use conventional commit format (no `GRM-N:` prefix):
+```
+feat: add new feature
+fix: resolve bug
+docs: update README
+```
+
+### 5. Push and Create PR
+- Push: `git push -u origin HEAD` (pre-push hook validates Vikunja task existence via `devx.tools.pre_push_check`)
+- Create PR: `make create-pr` (creates a PR with title `GRM-N: <vikunja task title>`, auto-derived from the branch name and Vikunja task)
+- Or both in one step: `make push-with-pr`
+- PR body: summary of changes, `Closes GRM-N`
+- Add `ready-to-merge` label **only after review is complete**
+
+### 6. Review the PR (Mandatory — Before Adding ready-to-merge Label)
+
+**Review checklist:** Every PR is reviewed against 13 categories covering
+architecture, code quality, security, i18n, testing, performance,
+UX, documentation, workflow compliance, maintainability, resource
+management, backwards compatibility, and logging.
+
+**Automated review (CI `pr-review` job):** Every PR triggers an automated
+review via `devx.ci.pr_review` (run as `python -m devx.ci.pr_review`). This job posts a review with
+`COMMENT` (no issues) or `REQUEST_CHANGES` (issues found) based on
+the **[auto]** items in the checklist:
+
+- Architecture compliance (no subprocess in CLI, no hardcoded URLs)
+- Best practices (no `print()`, no bare `except`, no `TODO`/`FIXME`,
+  no functions > 50 lines)
+- Security (no hardcoded secrets, no `shell=True`, no `eval`/`exec`)
+- i18n (no raw strings in `click.echo()` without `_()` wrapper)
+- Resource management (no `open()` without `with`, no `Popen()` without cleanup)
+- Documentation (source changes must include doc updates)
+- Test coverage (source changes must include test updates)
+- Commit conventions (conventional commit format on PR commits)
+
+The automated review posts inline comments on specific lines and
+includes a summary of the checklist categories. The agent **must** address all
+`REQUEST_CHANGES` issues before proceeding.
+
+**Manual review (agent):** After the automated review passes, the agent
+must go through **every category** listed above and verify
+the **[manual]** items by reviewing the full diff
+(`git diff master...HEAD`).
+
+Post review comments using `devx.ci.pr_review` (run as `python -m devx.ci.pr_review`):
+```bash
+CI_GITEA_TOKEN=<token> python -m devx.ci.pr_review <pr_number> <owner/repo> \
+  --event REQUEST_CHANGES \
+  --body "Review summary"
+```
+
+### 7. Address Review Comments
+Fix each comment one by one, commit, and push. Re-review until satisfied.
+
+### 8. Approve and Merge
+Once all checklist items are verified and comments are addressed, post
+an approval review with `--checklist-confirmed` and `--checklist-categories`:
+```bash
+CI_GITEA_TOKEN=<token> python -m devx.ci.pr_review <pr_number> <owner/repo> \
+  --event APPROVE --checklist-confirmed \
+  --checklist-categories 1,2,3,4,5,6,7,8,9,10,11,12,13 \
+  --body "All 13 checklist categories verified. Architecture: <summary>. Security: <summary>. Tests: <summary>. Docs: <summary>."
+```
+
+The `--checklist-confirmed` flag is **required** for APPROVE events —
+it attests that the reviewer has gone through every checklist category.
+The `--checklist-categories` flag is also **required** — it must list at
+least 8 of the 13 category numbers, ensuring the reviewer actually
+checked each category rather than rubber-stamping. The review body must
+be substantive (> 50 characters) — trivial approvals like "LGTM" are
+rejected.
+
+Then add the `ready-to-merge` label. The auto-merge workflow will:
+1. **Validate** PR title format (`GRM-N: <vikunja task title>`) and match against Vikunja task title
+2. **Check** that at least one substantive APPROVE review exists (body > 20 chars or has inline comments)
+3. Wait for all CI checks to pass (including the `pr-review` job)
+4. Squash-merge with title: `GRM-N: <conventional commit message>`
+5. The post-merge workflow marks the Vikunja task as done
+6. The release workflow automatically versions, tags, and publishes (see below)
+
+**If the branch is behind master** (another PR merged first), auto-merge
+automatically rebases the PR's head branch via the Gitea API. This triggers
+a new CI run. The next auto-merge attempt will merge successfully.
+No manual rebase needed. To rebase manually: `make rebase` (local) or
+`make pr-rebase` (server-side via API).
+
+> **IMPORTANT**: Never manually merge PRs via the API. Always use the auto-merge
+> workflow by adding the `ready-to-merge` label. Manual merges bypass the
+> `GRM-N: <conventional>` format enforcement, producing incorrectly named commits.
+> The auto-merge script validates the PR title matches the Vikunja task ID
+> and conventional commit format before merging.
+
+### CI Path Filtering
+
+The CI workflow includes a `pre-merge-check` job (runs after quality +
+detect-changes) that validates branch format, PR title, and Vikunja task
+match. This fails fast before expensive molecule tests run.
+
+The CI workflow includes a `detect-changes` job that checks whether any files
+under `ansible/` or `.ansible-lint` have changed. If no Ansible files are
+changed, molecule tests are skipped — this prevents non-Ansible changes
+(e.g., Python scripts, workflow YAML, docs) from being blocked by molecule
+test infrastructure flakiness.
+
+### Dynamic Runner Discovery
+
+Molecule tests are distributed across available Gitea Actions runners
+dynamically via `devx.molecule.discover_runners`. The `discover-runners`
+job queries the Gitea API for runners at all levels (repo, org, instance)
+and generates a dynamic matrix. If the API can't see instance-level runners
+(no admin scope), it falls back to the `MOLECULE_RUNNERS` repo variable,
+then to a default of 3.
+
+**When adding/removing Gitea runners:**
+1. Repo/org-level runners are auto-detected via the API
+2. For instance-level runners, update the `MOLECULE_RUNNERS` repo variable
+3. The workflow automatically scales the matrix to match available runners
+
+### Automated Release Pipeline
+
+After a PR is merged to master, the **post-merge workflow**
+(`.gitea/workflows/post-merge.yml`) runs automatically. This single
+workflow consolidates release, wiki sync, badge generation, and
+Vikunja task updates:
+
+1. **detect-type** — Checks if the commit is a regular merge or a
+   release commit (`release: vX.Y.Z`). All subsequent jobs skip for
+   release commits (the `[skip ci]` tag also prevents re-triggering).
+
+2. **release** — Runs `devx.ci.release` which:
+   - **Checks for user-facing changes** via `devx.ci.classify_changes` — if only
+     workflow/infrastructure files changed (`.gitea/`, `docs/`, `tests/`,
+     `AGENTS.md`, `Makefile`, etc.), the release is **skipped entirely** — no version
+     bump, no tag, no publish. This prevents unnecessary releases for CI/docs-only changes.
+   - Uses **git-cliff** to calculate the next semver version from conventional commits
+   - Updates `__version__` in `src/gitea_runner_manager/__init__.py` (single source of truth)
+   - Updates `CHANGELOG.md` with the new version section
+   - **Runs `make lint-ruff` and `make pytest-cov`** to verify the release is healthy
+   - If lint or tests fail, **aborts immediately** — no commit, no tag
+   - Commits with `release: vX.Y.Z [skip ci]` prefix (the `[skip ci]` prevents
+     re-triggering post-merge on the release commit)
+   - Creates an annotated tag `vX.Y.Z` on the release commit
+   - Pushes both the commit and tag to master
+   - `--skip-tests` flag bypasses test verification (emergency use only, not recommended)
+   - Loops are prevented by `has_unreleased_changes` — after a release commit is tagged, the next run finds no unreleased changes and exits
+
+3. **sync-wiki** — Syncs documentation to the Gitea wiki. Runs for ALL
+   non-release commits (not just when release succeeds), so docs-only
+   changes still update the wiki.
+
+4. **badges** — Generates and pushes quality badge SVGs to the `badges` branch.
+   Uses `if: always()` so it runs on every push, including release commits.
+   The script fetches the latest master before generating badges to pick up
+   any release commits.
+
+5. **vikunja** — Marks the corresponding Vikunja task as done. Runs for ALL
+   non-release commits (not just when release succeeds), so infrastructure-only
+   changes still update the task tracker.
+
+6. **publish** — Runs after release succeeds (needs: release). Builds and
+   publishes the package to the Gitea PyPI registry. Gets the tag from the
+   release job's `tag` output.
+
+### Smart CI: User-Facing vs Workflow-Only Changes
+
+Not all changes require the full CI pipeline or a new release. The project
+classifies changes into two categories using `devx.ci.classify_changes`:
+
+**Classification strategy (safe-by-default):** Any file NOT in the explicit
+infrastructure allowlist is treated as user-facing. This prevents new file
+types from accidentally skipping releases. Classification is config-driven
+via `[tool.devx.classify]` in `pyproject.toml`.
+
+**Infrastructure paths** (no release needed):
+- `.gitea/**` — Gitea Actions workflows
+- `scripts/**` — Dev tools and CI/CD automation (not part of installed package)
+- `docs/**` — Documentation
+- `tests/**` — Test files
+- `AGENTS.md`, `README.md`, `CHANGELOG.md`, `TROUBLESHOOTING.md`, `CONTRIBUTING.md` — Project docs
+- `Makefile`, `cliff.toml`, `uv.lock` — Build tooling
+- `.pre-commit-config.yaml`, `.ansible-lint`, `.checkmake.ini` — Lint config (ruff config is in `pyproject.toml`)
+- `.env.example`, `.gitignore` — Config
+- `.devin/**` — Agent/CI tooling config
+- `hooks/**` — Git hooks
+- `activate.sh`, `activate.fish`, `activate.zsh` — Generated venv scripts
+
+**User-facing paths** (tool changes → release needed) — everything else:
+- `src/gitea_runner_manager/**` — Python CLI source (except `__init__.py`)
+- `ansible/**` — Ansible role
+- `pyproject.toml` — Package metadata
+- Any new file type not in the allowlist
+
+**devx module structure** (installed from git, not in this repo):
+- `devx.ci.*` — CI/CD automation (run by workflows): release, publish, auto_merge, classify_changes, detect_release_commit, push_badges, doc_coverage, sync_wiki, distribute_molecule, molecule_ci_guard, discover_runners, notify_failure, post_merge, pr_review, validate_commit_msg
+- `devx.tools.*` — Dev tools (run locally): check_test_speed, configure_repo, install_checkmake, install_tools, setup, generate_badges, create_task, create_pr, pr_status, pr_logs, pr_label, rebase, pr_rebase
+- `devx.molecule.*` — Molecule helpers: molecule_all, platforms, discover_runners, distribute_molecule, molecule_ci_guard
+- `devx.gitea_cli` — Tea CLI wrapper
+- `devx.i18n` — i18n translation system
+- `devx.config` — Shared configuration (DEVX_* env vars)
+- `devx.api_clients` — GiteaClient, VikunjaClient
+- `devx.exceptions` — APIError and other exceptions
+
+**CI behavior based on classification:**
+- **Molecule tests**: Only run when `ansible/` or `.ansible-lint` files change
+- **Release dry-run**: Only runs when user-facing files change
+- **Quality job** (lint, unit tests, coverage, doc-coverage): Always runs
+- **Release workflow**: Skips entirely when no user-facing files changed since last tag
+
+**AI agents must follow these rules:**
+- When working on workflow/CI/docs-only changes, use `ci:` or `docs:` commit prefixes
+- Do NOT bump the version or create tags for infrastructure-only changes
+- The `classify_changes` module enforces this automatically — no manual intervention needed
+
+## Source Code Separation and devx Integration
+
+The codebase enforces strict separation between the GRM tool and the devx package:
+
+### Directory Layout
+
+| Directory | Purpose | Release impact |
+|-----------|---------|----------------|
+| `src/gitea_runner_manager/` | User-facing GRM CLI tool | Changes trigger release |
+| `devx` package (installed from git) | Reusable CI/CD and dev tools | Not in this repo (no release impact) |
+| `ansible/` | Ansible role for runner setup | Changes trigger release |
+
+### Import Rules
+
+1. **`src/gitea_runner_manager/` NEVER imports from devx** — the GRM tool is self-contained
+2. **devx MAY import from `gitea_runner_manager`** — one-way dependency (devx uses the tool's API clients, config, i18n)
+3. **Cross-module imports within devx** are allowed (devx modules importing from other devx modules) and must be documented
+4. **`devx.gitea_cli`** is a shared wrapper around the `tea` CLI — devx modules import from it for Gitea API operations (issues, labels, PRs, releases, reviews)
+
+### tea CLI Integration
+
+The `tea` Gitea CLI tool is used for Gitea API interactions in devx. It is installed by `devx.tools.install_tools` and configured by `devx.tools.setup` (login profile from `.env` `CI_GITEA_TOKEN`).
+
+**`devx.gitea_cli`** — Python wrapper around `tea` CLI with JSON output parsing:
+- `TeaCLI.create_issue()` — Create issues with labels
+- `TeaCLI.list_labels()` / `TeaCLI.create_label()` / `TeaCLI.add_label()` — Label management
+- `TeaCLI.create_pr()` / `TeaCLI.merge_pr()` / `TeaCLI.review_pr()` — Pull request operations
+- `TeaCLI.create_release()` / `TeaCLI.list_releases()` — Release management
+- `TeaCLI.list_branches()` — Branch listing
+
+**Modules using tea (via `devx.gitea_cli`):**
+- `devx.ci.publish` — Creates Gitea releases via `tea releases create`
+- `devx.ci.notify_failure` — Creates issues via `tea issues create` (falls back to `GiteaClient` if tea not installed)
+- `devx.tools.configure_repo` — Creates labels via `tea labels create` (falls back to `GiteaClient` if tea fails; branch protection still uses `GiteaClient` since tea only supports basic protect/unprotect)
+
+**Operations still using `GiteaClient` (not supported by tea):**
+- PR reviews (`devx.ci.pr_review`) — tea v0.14.1 only supports interactive reviews
+- Wiki page management (`devx.ci.sync_wiki`)
+- Commit status checks (`devx.ci.auto_merge`)
+- Runner discovery (`devx.molecule.discover_runners`)
+- Branch protection with detailed config (`devx.tools.configure_repo`)
+- PR file/commit listing (`devx.ci.pr_review`)
+
+### PYTHONPATH Configuration
+
+Since devx is installed as a package (via `pip install` from git), it is importable directly. Workflows only need `PYTHONPATH=src` when a devx module imports from `gitea_runner_manager`:
+
+| PYTHONPATH | When to use | Example modules |
+|------------|-------------|-----------------|
+| `src` | Module imports from `gitea_runner_manager` | `devx.ci.auto_merge`, `devx.ci.pr_review`, `devx.ci.pr_review`, `devx.ci.sync_wiki`, `devx.ci.post_merge`, `devx.ci.classify_changes`, `devx.molecule.discover_runners`, `devx.ci.doc_coverage` |
+| (none) | Module has no GRM imports | `devx.ci.detect_release_commit`, `devx.molecule.distribute_molecule`, `devx.molecule.molecule_ci_guard`, `devx.ci.push_badges`, `devx.ci.validate_commit_msg` |
+
+**In workflows**, always use `env:` blocks (not inline `PYTHONPATH=value`):
+```yaml
+- name: Run module
+  env:
+    PYTHONPATH: src
+  run: python -m devx.ci.example
+```
+
+**Locally**, devx is installed as a package, so only `PYTHONPATH=src` is needed if importing from `gitea_runner_manager`.
+
+### Shared Constants
+
+`devx.molecule.platforms` is the single source of truth for the molecule
+platform matrix. Both `devx.molecule.distribute_molecule` (CI) and
+`devx.molecule.molecule_all` (dev tool) import `PLATFORMS` from it — this
+avoids dev tools importing directly from CI modules.
+
+2. **Publish job** (in `post-merge.yml`, needs: release):
+   - Runs after the release job creates a tag
+   - Gets the tag from `needs.release.outputs.tag`
+   - Builds the Python package
+   - Publishes to the Gitea PyPI registry
+   - Creates a Gitea release with git-cliff-generated release notes
+   - On failure, creates a Gitea issue via `devx.ci.notify_failure`
+
+### git-cliff Commit Preprocessing
+
+Merge commits on master have the format `GRM-N: <conventional commit>`. The
+`GRM-N: ` prefix is not a valid conventional commit prefix, so `cliff.toml`
+includes a `commit_preprocessors` entry that strips it before parsing. This
+ensures all merged work appears in the changelog.
+
+### Version Bumping Rules (git-cliff)
+
+| Commit type | Version bump |
+|-------------|-------------|
+| `feat:` | minor (0.X.0) |
+| `fix:` | patch (0.0.X) |
+| `feat!:` or `BREAKING CHANGE` | minor (pre-1.0: major would be 1.0.0) |
+| `chore:`, `ci:`, `docs:` | no bump (excluded by cliff.toml) |
+
+The version source is `__version__` in `src/gitea_runner_manager/__init__.py`, read by setuptools via `dynamic = ["version"]` in `pyproject.toml`. The release script only updates `__init__.py` — no need to touch `pyproject.toml`. `grm --version` reports this version.
+
+### Title Format Summary
+
+| What | Format | Example |
+|------|--------|---------|
+| Branch name | `GRM-N-short-description` | `GRM-33-add-pr-review-step` |
+| Branch commits | `<conventional commit>` | `feat: add review script` |
+| PR title | `GRM-N: <vikunja task title>` | `GRM-33: Add mandatory PR review step` |
+| Merge commit | `GRM-N: <conventional commit>` | `GRM-33: feat: add review script` |
+
+### Configuration
+
+The devx package is configured via `DEVX_*` environment variables:
+- `DEVX_TASK_PREFIX=GRM` — Prefix for Vikunja task identifiers
+- `DEVX_VIKUNJA_PROJECT_ID=6` — Vikunja project ID for task tracking
+- `DEVX_VERSION_FILE=src/gitea_runner_manager/__init__.py` — Path to the version source file
+
+Change classification is config-driven via `[tool.devx.classify]` in `pyproject.toml`, which defines the infrastructure and user-facing path patterns.
+
+## Key Conventions
+
+- Python 3.12+ required (ruff/pyright target `py312`)
+- 100% test coverage required (`--cov-fail-under=100`)
+- Conventional commits on feature branches (no `GRM-N:` prefix)
+- Branch names must include `GRM-N` task ID
+- Line length: 120 chars
+- Secrets are passed via temp JSON files, never on the command line (CWE-214)
+- CI triggers only on `opened` and `synchronize` PR events (not `labeled`)
+
+## Ansible Role Structure
+
+```
+main.yml → systemd_check → user_setup → rootless_docker → install_runner → prune → integration_test
+```
+
+- `install_runner.yml` handles: download, config, validate, register, service
+- `main.yml` handles: prune, integration_test (NOT install_runner — avoids duplicates)
+- `systemctl --user` tasks must be guarded by `docker_rootless_setup`
+- Template creation tasks are NOT guarded by `docker_rootless_setup` (they just create files)
+
+## Molecule Scenarios
+
+7 scenarios: `default`, `multi-instance`, `lifecycle`, `template-content`, `deregister`, `update`, `remove`
+4 platforms: `ubuntu-2204`, `ubuntu-2404`, `debian-12`, `archlinux`
+Platform list is defined in `devx.molecule.platforms` (single source of truth)
+
+Note: `make molecule` and `make molecule-all` run 6 scenarios (excluding `remove`, which destroys the test container). CI discovers all 7 scenarios via `devx.molecule.distribute_molecule`.
+
+## Known Issues
+
+- `ansible-lint` may warn about `command-instead-of-module` for `systemctl --user` calls — this is expected (systemd module doesn't support user services) and skipped in `.ansible-lint`
+- Molecule Docker driver may print "Event loop is closed" warnings on interrupt — harmless
+
+## Documentation-as-Code
+
+All documentation lives in `/docs/` and is synced to the Gitea wiki automatically.
+
+### Structure
+
+```
+docs/
+├── index.md              # Wiki homepage
+├── mapping.json          # File-to-wiki-page title mapping
+├── user/                 # User documentation
+│   ├── getting-started.md
+│   ├── installation.md
+│   ├── cli-commands.md
+│   ├── troubleshooting.md
+│   └── faq.md
+└── tech/                 # Technical documentation
+    ├── architecture.md
+    ├── development-setup.md
+    ├── ci-cd-workflow.md
+    ├── testing-strategy.md
+    ├── decision-log.md
+    └── contributing.md
+```
+
+### Wiki Sync
+
+- **On merge to master**: `sync-wiki.yml` workflow runs `devx.ci.sync_wiki` which pushes all `/docs/` content to the Gitea wiki via API
+- **On release tag**: Same sync runs, plus the wiki is tagged with the release version
+- `mapping.json` maps each file path to a wiki page title (e.g., `user/getting-started.md` → `Getting-Started`)
+- README.md is a lean entry point with links to the wiki — no detailed content
+
+### Documentation Coverage
+
+- `devx.ci.doc_coverage` checks that all CLI commands, Python modules, and CI scripts are documented
+- Runs as a CI step in the quality job with `--fail-on-missing` (blocks CI if docs are missing)
+- Enforced: 100% coverage for public CLI commands and major architectural components
+
+### Updating Documentation
+
+1. Edit files in `/docs/`
+2. If adding a new page, add it to `docs/mapping.json`
+3. Commit and create a PR (standard PR workflow)
+4. On merge, wiki is automatically synced
+
+## Subagent Delegation Policy
+
+Custom subagent profiles are defined in `.devin/agents/` (project-specific)
+and `~/.config/devin/agents/` (global, shared across repos). The agent MUST
+automatically delegate to the appropriate subagent based on the task —
+the user should not need to specify which profile to use.
+
+### Available Profiles
+
+**Global** (shared with infra and devx):
+
+| Profile | Location | Purpose |
+|---------|----------|---------|
+| `pr-reviewer` | `~/.config/devin/agents/` | 13-category PR checklist + quality gates |
+| `release-check` | `~/.config/devin/agents/` | Pre-merge readiness validation |
+
+**grm-specific** (in `.devin/agents/`):
+
+| Profile | Purpose |
+|---------|---------|
+| `ci-investigator` | Investigate CI failures (quality, molecule, release, publish, wiki sync) |
+| `molecule-runner` | Run 7 molecule scenarios across 4 platforms, report pass/fail |
+| `dep-upgrader` | Python + Ansible dependency upgrades with molecule verification |
+| `doc-syncer` | Doc coverage, doc linting, wiki sync for grm docs |
+| `workflow-validator` | actionlint + act_runner dry-run for grm workflows |
+
+### When to Delegate Automatically
+
+| Trigger | Profile | Mode |
+|---------|---------|------|
+| CI run failure (quality, molecule-tests, release, publish, sync-wiki) | `ci-investigator` | Background |
+| PR ready for review | `pr-reviewer` | Foreground |
+| Molecule tests need to run | `molecule-runner` | Background |
+| Dependency upgrade requested | `dep-upgrader` | Background |
+| Doc coverage failure or wiki sync issue | `doc-syncer` | Background |
+| Workflow YAML modified or validation needed | `workflow-validator` | Background |
+| Branch ready for merge | `release-check` | Foreground |
+
+### Delegation Rules
+
+1. **Auto-select the profile.** Do not ask the user which profile to use.
+2. **Background by default, foreground when blocking.**
+3. **Provide full context in the prompt** — subagents don't inherit conversation history.
+4. **One subagent per concern.** Chain: investigate → fix in main session → review.
+5. **Don't delegate trivial work** (<30s, <50 lines of context).
+6. **Compact after subagent returns.**
+7. **Never skip delegation to save time** — it keeps main context small.
+
+
+## Feedback Issue Handling
+
+Subagents create Gitea issues in the current repo when they encounter
+tool, workflow, or process issues that warrant follow-up. These issues
+use the `feedback` label plus a category label (`tooling`,
+`ci-improvement`, `doc-improvement`, `workflow-improvement`).
+
+Standard labels are created automatically by `configure_repo` (runs in
+post-merge on every master push). If a label does not exist yet, the
+subagent's issue creation will still succeed — labels can be added
+afterwards.
+
+### When a Subagent Reports a Feedback Issue URL
+
+1. **Acknowledge it** in your response to the user — mention the issue URL
+2. **Do NOT close or modify** the issue — it is for follow-up work
+3. **Do NOT create a PR** to address it unless the user explicitly asks
+4. If the user asks to address feedback, spawn a subagent to investigate
+   the issue and implement a fix
+
+### Creating Feedback Issues Manually
+
+As the parent agent, you can also create feedback issues directly using
+the Gitea MCP (`issue_write` with `create_issue` method). Follow the
+same format as subagents:
+
+- Title: `[feedback] <category>: <short description>`
+- Labels: `feedback` + category label
+- Body: include context, tool/workflow, issue, reproduction, affected
+  files, suggested investigation, and "Reported by: parent agent"
+
+Always deduplicate first via `list_issues` with `labels: "feedback"`.
+

CHANGELOG.md

@@ -0,0 +1,357 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [0.14.0] - 2026-07-01
+
+### Features
+
+- Bump devx to v0.30.0
+
+## [0.13.0] - 2026-07-01
+
+### Features
+
+- Bump devx to v0.29.1, upgrade molecule, ubuntu 26.04
+
+## [0.12.5] - 2026-06-30
+
+### Bug Fixes
+
+- Right-size molecule-tests matrix to [1-6]
+- Cast disk threshold to string in template-content verify assertion
+
+## [0.12.4] - 2026-06-29
+
+### Bug Fixes
+
+- Use hardcoded matrix array for Gitea 1.26 compatibility
+
+## [0.12.3] - 2026-06-29
+
+### Bug Fixes
+
+- Fix wiki link URLs, heading hierarchy, quote pip install vars
+- Improve runner service stability and deregistration
+
+## [0.12.2] - 2026-06-28
+
+### Bug Fixes
+
+- Bump devx to 0.26.3 (latest with pinned deps)
+
+## [0.12.1] - 2026-06-28
+
+### Bug Fixes
+
+- Add approval step to auto-merge workflow using REVIEW_GITEA_TOKEN
+
+## [0.12.0] - 2026-06-28
+
+### Features
+
+- Upgrade all dependencies, add trigger-workflow command
+
+## [0.11.1] - 2026-06-28
+
+### Bug Fixes
+
+- Makefile HOST/NAME requirement errors, add restart and list targets
+
+## [0.11.0] - 2026-06-28
+
+### Features
+
+- Unified --become-password-file, --verbose, --no-status, labels fix
+
+## [0.10.3] - 2026-06-27
+
+### Bug Fixes
+
+- Install hadolint on-the-fly in setup-image
+- Revert EXTRAS=ci default in setup-image
+- Add EXTRAS=ci to all setup-image calls, workflow-level CI_GITEA_TOKEN
+
+### Refactor
+
+- Remove hadolint on-the-fly install workaround
+- Use devx Makefile aliases, bump devx>=0.23.0
+
+## [0.10.2] - 2026-06-27
+
+### Bug Fixes
+
+- Setup-image configures Gitea PyPI registry and shows pip errors
+- Gate auto-merge on release-dry-run and unmask failures
+- Bump devx>=0.22.0 and remove REPO_TOKEN alias
+
+### Refactor
+
+- Rename REPO_TOKEN to CI_GITEA_TOKEN, consolidate env vars
+
+## [0.10.1] - 2026-06-27
+
+### Bug Fixes
+
+- Set PYTHONPATH=src in publish Install CI tools step
+
+### Refactor
+
+- Replace duplicated Makefile targets with devx.mak aliases
+- Consolidate publish.yml into post-merge.yml
+
+## [0.10.0] - 2026-06-26
+
+### Features
+
+- Adopt devx tools, devx.mak fragment, ci extra, remove legacy install-devx
+
+### Bug Fixes
+
+- Always run publish in post-merge (idempotent)
+
+## [0.9.0] - 2026-06-24
+
+### Features
+
+- Adopt devx v0.11.1 across Makefile and workflows
+- Add Polish as officially supported language
+
+## [0.8.1] - 2026-06-24
+
+### Bug Fixes
+
+- Repair publish workflow and add publish step to post-merge
+- Add build/twine to ci deps, activate venv in notify_failure
+
+## [0.8.0] - 2026-06-24
+
+### Features
+
+- Remove .taskid file, use branch name only for task ID
+
+### Bug Fixes
+
+- Add workflow_dispatch to publish workflow and update devx to 0.9.12
+
+## [0.7.0] - 2026-06-24
+
+### Features
+
+- Switch devx installation from git to Gitea PyPI registry
+- Adopt per-test timing quality gate from devx 0.7.0
+
+### Bug Fixes
+
+- Update devx to v0.4.2 and fix workflow env vars
+- Pin devx to v0.4.3 to fix post-merge workflow failures
+- Pin devx to v0.4.4 to fix validate-commit-msg and sync-wiki
+- Rewrite CHANGELOG with correct version ordering and missing sections
+- Lower test speed threshold to 4s and update devx to v0.8.2
+- Retrospective fixes for CI/CD friction
+- Replace stale badge SHA URLs with raw/branch/badges/
+
+## [0.6.4] - 2026-06-22
+
+### Bug Fixes
+
+- Update devx to v0.4.2 and fix workflow env vars
+- Pin devx to v0.4.3 to fix post-merge workflow failures
+- Pin devx to v0.4.4 to fix validate-commit-msg and sync-wiki
+
+## [0.6.3] - 2026-06-22
+
+### Bug Fixes
+
+- Add scripts/** to infrastructure classification config
+
+## [0.6.2] - 2026-06-22
+
+### Bug Fixes
+
+- Include lint extras in setup-ci and setup-release
+- Use commit SHA URLs for badges to bypass Gitea cache
+- Make sync-wiki and vikunja depend on release
+- Pin devx to v0.4.0, fix cliff.toml preprocessor, bump to v0.7.0
+
+### Refactor
+
+- Fully automate PR merge — no manual label/review needed
+- Require tea CLI everywhere, fail on missing Vikunja task
+- Separate GRM and CI translations with validation
+- Migrate from scripts/ to devx package
+
+## [0.6.1] - 2026-06-22
+
+### Bug Fixes
+
+- Badges always update on release commits + fix configure-repo PYTHONPATH
+- Enforce commit message convention on master with CI validation
+- Post-merge workflow failures (4 jobs)
+
+## [0.6.0] - 2026-06-22
+
+### Bug Fixes
+
+- Molecule-tests matrix runner-index renders as empty for 0
+- Use 1-based runner indices for Gitea Actions compatibility
+- Molecule-tests static matrix and role_dir path fix
+- Auto-merge label condition uses pull_request.labels
+- Revert review_pr.py to GiteaClient (tea v0.14.1 is interactive-only) (#70)
+
+### Revert
+
+- Remove v0.6.0 release (no user-facing changes)
+
+## [0.5.0] - 2026-06-22
+
+### Features
+
+- Enforce commit naming conventions and workflow discipline
+
+### Bug Fixes
+
+- Clean up infrastructure-only releases and fix release classification
+- Rewrite changelog and re-tag releases at user-facing milestones
+
+## [0.4.0] - 2026-06-21
+
+### Features
+
+- Replace inline workflow scripts with tested Python modules
+- User-friendly click errors with i18n in configure_repo
+- Bandit integration (#1)
+- Auto-delete branch after merge in configure_repo script
+- Add runner labels support and refactor i18n to JSON
+- Parallel molecule runner with kill-on-first-failure
+- Cross-runner molecule cancellation via Gitea API polling
+
+### Bug Fixes
+
+- Set runner_mode to binary in multi-instance converge
+- Skip systemd operations in lifecycle molecule when unavailable
+- Improve make setup with version guard, pre-push hooks and commit-msg validator
+- Enforce GRM-N: conventional on master commits and PR titles
+- Remove molecule tests from pre-push hooks
+- Resolve bandit security warnings in source code and tests
+- CI pipeline for rootless Docker runners
+- CI workflows for rootless runner compatibility
+- Vikunja task resolution pagination in post_merge.py
+- Use PUT instead of POST for Vikunja task comments
+- Parse pytest output with warnings in check_test_speed
+- Use systemd as container command for rootless molecule tests
+- Add Docker APT repository before installing docker-ce
+- Use deb822_repository for Docker APT repo (proper GPG handling)
+- Dearmor Docker GPG key with gpg --dearmor for apt_repository
+- Use bash for gpg dearmor (pipefail not available in sh)
+- Install curl, gpg, ca-certificates in molecule prepare
+- Separate apt update after adding Docker repo, use variable for repo string
+- Add apt source debug tasks, fix arch mapping for Docker repo
+- Fail-fast CI, write Docker apt source directly, fix arch mapping
+- Skip rootless Docker daemon startup in molecule tests
+- Gate all Docker-dependent tasks behind docker_rootless_setup
+- Catch TimeoutExpired in parallel runner wait loop
+- Stream molecule subprocess output to CI logs
+- Run molecule pairs sequentially within each CI runner
+- Guard all systemctl --user tasks with docker_rootless_setup
+- Guard handler systemctl --user calls with docker_rootless_setup
+- Make user_setup and download tasks idempotent
+- Use gnupg instead of gpg package name on Arch Linux
+- Add default(0) to gitea_runner_uid in environment blocks
+- Set runner_name in deregister verify.yml
+- Security, dead code, idempotence, and documentation cleanup
+- Use content_base64 for Gitea wiki API, add --verify flag (#33)
+- Wiki links, add --strict integrity check for wiki sync (#34)
+
+### Refactor
+
+- Standardise pre-commit hooks on make targets
+- Use http.HTTPStatus constants instead of magic numbers
+- Rework all scripts to use click and i18n
+- *(scripts)* Centralize constants, API clients, and HTTP status codes
+- Rootless Docker, fix auto-merge, molecule platform matrix
+
+## [0.3.2] - 2026-06-21
+
+### Features
+
+- Smart CI and release skipping for workflow-only changes
+
+### Bug Fixes
+
+- Set PYTHONPATH=. for release.py to find scripts.ci module (#32)
+
+### Refactor
+
+- Split CI scripts, fix release PYTHONPATH, dynamic runner discovery
+
+## [0.3.1] - 2026-06-21
+
+### Bug Fixes
+
+- Use correct Gitea 1.26 wiki API endpoints
+
+## [0.3.0] - 2026-06-21
+
+### Features
+
+- Implement documentation-as-code with wiki sync and doc-coverage
+
+## [0.2.2] - 2026-06-21
+
+### Bug Fixes
+
+- Bypass commit-msg hook for release commits
+- Enforce tests pass before tagging a release
+
+## [0.2.1] - 2026-06-21
+
+### Bug Fixes
+
+- Strip git-cliff header from CHANGELOG.md updates
+
+## [0.2.0] - 2026-06-18
+
+### Features
+
+- Parameterize all hardcoded configuration values as Ansible variables
+- Add GITEA_ADMIN_TOKEN support for integration test
+- Add AnsibleExecutor and i18n modules
+- Integrate AnsibleExecutor and i18n into CLI and RunnerManager
+- Add systemd template units and multi-instance Ansible support
+- Add lifecycle CLI commands and RunnerManager extensions
+- Add runner registry for simplified CLI UX
+- Add translated operation report for success and failure cases
+- Replace print() with stdlib logging module
+- Use click.echo() for user-facing messages with dual logging
+- Add colorized output for better visual feedback
+- Add --force flag to grm remove for unreachable runners
+- Make --ask-become-pass the default behavior
+
+### Bug Fixes
+
+- Resolve idempotence issues and testing infrastructure
+- Remove recursive variable definitions in install and update playbooks
+- Add timeout to runner registration to prevent indefinite hangs
+- Override Docker container entrypoint to bypass run.sh wrapper
+- Set Docker working dir to /data for .runner persistence
+- Make integration test conditional on admin API accessibility
+- Remove recursive var definitions from install-runner.yml
+- Convert runner config from TOML to YAML format
+- Rewrite integration test to verify .runner file and container health instead of unreliable API checks
+- Eliminate duplicate console output, restore GRM_LOG_LEVEL filtering
+- Make grm list retrieve runner status correctly
+
+### Refactor
+
+- Remove dead code and legacy artifacts
+- Migrate source terminology from act_runner to gitea_runner
+- Consolidate systemd checks and deduplicate role structure
+- Deduplicate CLI, remove dead code, move validation to business layer
+- Resolve_runner returns gitea_url, add --url CLI option, force remove improvements, code quality fixes
+
+## [0.1.0] - 2026-06-17
+
+### Features
+
+- Initial implementation of Gitea Runner Manager

CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# Contributing to GRM
+
+For the full contributing guide, see the [Contributing wiki page](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Contributing).
+
+Thank you for contributing to Gitea Runner Manager (GRM)!
+
+## Branch Naming
+
+All feature branches **must** include a `GRM-N` prefix corresponding to the Vikunja task identifier. Examples:
+
+- `GRM-19`
+- `GRM-19-fix-bug`
+- `GRM-42-add-update-command`
+
+The `GRM-N` prefix is mandatory — CI extracts it for merge messages and Vikunja updates.
+
+## Commit Format
+
+### Feature branches
+Use **conventional commits** on feature branches:
+
+```
+feat: add new command
+fix: resolve timeout issue
+chore: update dependencies
+docs: improve README
+```
+
+Allowed types: `feat`, `fix`, `chore`, `docs`, `style`, `refactor`, `perf`, `test`, `ci`, `build`, `revert`, `BREAKING CHANGE`.
+
+**Do NOT** include the `GRM-N:` prefix in commit messages on feature branches.
+
+### Master branch (squash merges)
+Squash commits on `master` must follow:
+
+```
+GRM-N: <conventional commit message>
+```
+
+Example: `GRM-24: fix: resolve molecule idempotence`.
+
+This format is enforced by the auto-merge workflow, which validates the PR title is a conventional commit before squash-merging and prepending the task ID.
+
+## Local Testing
+
+```bash
+make test-all    # Runs pytest-cov + molecule
+make lint-all    # Runs ruff, pyright, bandit, ansible-lint, checkmake
+make lint-bandit # Security scan with bandit
+make pytest-cov  # Unit tests with 100% coverage enforcement
+make molecule    # All 6 molecule scenarios
+```
+
+## Code Quality
+
+- **ruff**: Line length 120
+- **pyright**: Strict mode
+- **bandit**: Security scan for Python code (no high/medium severity issues)
+- **Test coverage**: 100% required
+- **ansible-lint**: For all Ansible content

LICENSE

@@ -0,0 +1,232 @@
+GNU GENERAL PUBLIC LICENSE
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+Preamble
+
+The GNU General Public License is a free, copyleft license for software and other kinds of works.
+
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
+
+To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
+
+Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
+
+For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
+
+Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
+
+Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+TERMS AND CONDITIONS
+
+0. Definitions.
+
+“This License” refers to version 3 of the GNU General Public License.
+
+“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+
+“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
+
+To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
+
+A “covered work” means either the unmodified Program or a work based on the Program.
+
+To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+
+To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+
+1. Source Code.
+The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
+
+A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+
+The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+
+The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+
+2. Basic Permissions.
+All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
+
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
+
+4. Conveying Verbatim Copies.
+You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+
+5. Conveying Modified Source Versions.
+You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+
+     a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
+
+     b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
+
+     c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
+
+     d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+
+6. Conveying Non-Source Forms.
+You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+
+     a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
+
+     b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
+
+     c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
+
+     d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
+
+     e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+
+A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+
+“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+
+7. Additional Terms.
+“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+
+     a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
+
+     b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
+
+     c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
+
+     d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
+
+     e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
+
+     f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+
+8. Termination.
+You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+
+9. Acceptance Not Required for Having Copies.
+You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+
+10. Automatic Licensing of Downstream Recipients.
+Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
+
+An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+
+11. Patents.
+A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.
+
+A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+
+In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+
+A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+
+12. No Surrender of Others' Freedom.
+If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+
+13. Use with the GNU Affero General Public License.
+Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
+
+14. Revised Versions of this License.
+The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+
+15. Disclaimer of Warranty.
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. Limitation of Liability.
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+17. Interpretation of Sections 15 and 16.
+If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
+
+     grm
+     Copyright (C) 2026  emil
+
+     This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.
+
+     You should have received a copy of the GNU General Public License along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
+
+     grm  Copyright (C) 2026  emil
+     This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+     This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.
+
+You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <https://www.gnu.org/licenses/>.
+
+The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <https://www.gnu.org/philosophy/why-not-lgpl.html>.

Makefile

@@ -0,0 +1,203 @@
+.PHONY: all setup setup-ci setup-quality setup-molecule setup-release setup-image install update lint ansible-lint makefile-lint lint-all lint-ruff lint-format lint-bandit lint-deps typecheck checkmake install-hooks test test-unit pytest-cov molecule molecule-all test-all clean workflow-lint workflow-dryrun workflow-check install-tools
+.PHONY: configure-gitea-pypi
+.PHONY: create-task create-pr push-with-pr git-push
+
+PYTHON := python3
+VENV := .venv
+BIN := $(VENV)/bin
+CHECKMAKE := $(shell command -v checkmake 2>/dev/null || echo $(HOME)/go/bin/checkmake)
+
+all: setup
+
+# --- devx.mak include (shared Makefile targets) -------------------------------
+# Set DEVX_PYTHON before including devx.mak so it uses the venv Python.
+DEVX_PYTHON := $(BIN)/python
+DEVX_VENV := $(VENV)
+DEVX_BIN := $(BIN)
+DEVX_COV_PKG := src/gitea_runner_manager
+DEVX_TEST_PATHS := tests/ scripts/tests/
+DEVX_LINT_PATHS := src/ scripts/ tests/
+
+# Include shared targets from devx package (create-task, create-pr, push-with-pr,
+# check-config, workflow-lint, lint-ruff, clean, venv, .env, activate-scripts,
+# install-hooks, install-tools, configure-gitea-pypi, checkmake, etc.)
+# Silent if devx not installed yet — run 'make setup' first.
+DEVX_MAK := $(shell $(BIN)/python -c \
+	"from pathlib import Path; import devx; print(Path(devx.__file__).parent / 'make' / 'devx.mak')" \
+	2>/dev/null)
+-include $(DEVX_MAK)
+
+# Full setup for local development (all deps, tools, collections, hooks)
+# devx is installed via pip install -e .[dev] (devx is in dev extra)
+setup: $(VENV)/bin/activate .env activate-scripts configure-gitea-pypi
+	@$(PIP_INSTALL) install -e '.[dev]'
+	@$(BIN)/python -m devx.tools.install_checkmake
+	@$(BIN)/python -m devx.tools.install_tools
+	@export PATH="$(HOME)/.local/bin:$$PATH"; \
+	$(BIN)/python -m devx.tools.setup --bin "$(BIN)" --skip-install
+
+# Lean setup for CI jobs that need pytest + lint tools + runtime deps
+# (detect-changes, discover-runners, pr-review, sync-wiki, badges)
+# badges job runs generate_badges.py which needs ruff, pyright, bandit
+setup-ci: $(VENV)/bin/activate .env configure-gitea-pypi
+	@$(PIP_INSTALL) install -e '.[ci,lint]'
+	@$(BIN)/python -m devx.tools.setup --bin "$(BIN)" --skip-install --no-ansible-collections --no-pre-commit --no-tea-login
+
+# Setup for the quality job (lint + test deps, actionlint tool)
+setup-quality: $(VENV)/bin/activate .env configure-gitea-pypi
+	@$(PIP_INSTALL) install -e '.[ci,lint]'
+	@$(BIN)/python -m devx.tools.install_tools
+	@export PATH="$(HOME)/.local/bin:$$PATH"; \
+	$(BIN)/python -m devx.tools.setup --bin "$(BIN)" --skip-install --no-ansible-collections --no-pre-commit --no-tea-login
+
+# Full setup for molecule testing (needs ansible, molecule, collections)
+setup-molecule: $(VENV)/bin/activate .env configure-gitea-pypi
+	@$(PIP_INSTALL) install -e '.[ci,molecule]'
+	@$(BIN)/python -m devx.tools.install_tools
+	@export PATH="$(HOME)/.local/bin:$$PATH"; \
+	$(BIN)/python -m devx.tools.setup --bin "$(BIN)" --skip-install --no-pre-commit --no-tea-login
+
+# Setup for release jobs (needs git-cliff, tea, and lint tools for release.py)
+setup-release: $(VENV)/bin/activate .env configure-gitea-pypi
+	@$(PIP_INSTALL) install -e '.[ci,lint]'
+	@$(BIN)/python -m devx.tools.install_tools --tool git-cliff --tool tea
+	@export PATH="$(HOME)/.local/bin:$$PATH"; \
+	$(BIN)/python -m devx.tools.setup --bin "$(BIN)" --skip-install --no-ansible-collections --no-pre-commit
+
+# Setup for pre-built image jobs (deps already in image, just link venv + install project)
+# Usage: make setup-image              (runtime deps only, devx from image)
+#        make setup-image EXTRAS=lint  (runtime + lint deps, e.g. ansible-lint)
+#        make setup-image EXTRAS=ci,lint (runtime + ci + lint deps, upgrades devx)
+# NOTE: Cannot alias to devx-setup-image because the venv must exist before
+# devx.mak can be included (chicken-and-egg). This standalone target creates
+# the venv symlink first, then installs the project.
+setup-image:
+	@if [ -d /opt/venv ]; then ln -sf /opt/venv .venv; . .venv/bin/activate; \
+		if [ -n "$$CI_GITEA_TOKEN" ]; then export PIP_EXTRA_INDEX_URL="https://$$CI_GITEA_USERNAME:$$CI_GITEA_TOKEN@git.oblachno.oblachno.fyi/api/packages/oblachno-oss/pypi/simple/"; fi; \
+		pip install -e .$(if $(EXTRAS),[$(EXTRAS)],); \
+	else echo "[setup-image] /opt/venv not found — falling back to setup-ci"; $(MAKE) setup-ci; fi
+
+# Helper: run pip install with Gitea registry configured
+# Usage: $(PIP_INSTALL) install -e '.[ci,lint]'
+PIP_INSTALL := if [ -z "$$CI_GITEA_TOKEN" ]; then . ./.env 2>/dev/null; fi; \
+	CI_GITEA_TOKEN="$$CI_GITEA_TOKEN"; \
+	if [ -n "$$CI_GITEA_TOKEN" ]; then export PIP_EXTRA_INDEX_URL="https://$$CI_GITEA_USERNAME:$$CI_GITEA_TOKEN@git.oblachno.oblachno.fyi/api/packages/oblachno-oss/pypi/simple/"; fi; \
+	$(BIN)/pip
+
+$(VENV)/bin/activate:
+	@python3 -c "import sys; v=sys.version_info; assert v >= (3, 12), f'Python 3.12+ required, found {v.major}.{v.minor}'; print(f'Python {v.major}.{v.minor}.{v.micro} OK')"
+	$(PYTHON) -m venv $(VENV)
+	$(BIN)/pip install --upgrade pip setuptools wheel
+
+.env:
+	@if [ ! -f .env ]; then \
+		cp .env.example .env; \
+		echo "Created .env from .env.example — please edit it with your credentials."; \
+	fi
+
+activate-scripts: $(VENV)/bin/activate
+	@test -f activate.sh || (echo '#!/usr/bin/env bash' > activate.sh && echo 'source "$$(cd "$$(dirname "$${BASH_SOURCE[0]}")" && pwd)/.venv/bin/activate"' >> activate.sh && chmod +x activate.sh)
+	@test -f activate.fish || (echo '#!/usr/bin/env fish' > activate.fish && echo 'set -l script_dir (dirname (status --current-filename))' >> activate.fish && echo 'source "$$script_dir/.venv/bin/activate.fish"' >> activate.fish && chmod +x activate.fish)
+	@test -f activate.zsh || (echo '#!/usr/bin/env zsh' > activate.zsh && echo '0="$${ZERO:-$${0:#$$ZSH_ARGZERO}}"' >> activate.zsh && echo '0="$${$${(M)0:#/*}:-$$PWD/$$0}"' >> activate.zsh && echo 'source "$${0:A:h}/.venv/bin/activate"' >> activate.zsh && chmod +x activate.zsh)
+
+install:
+	@if [ -z "$(HOST)" ]; then echo "HOST is required. Example: make install HOST=192.168.1.10"; exit 1; fi
+	$(BIN)/grm install $(HOST) $(if $(USER),--user $(USER),) $(if $(KEY),--key $(KEY),) $(if $(NAME),--name $(NAME),) $(if $(TOKEN),--token $(TOKEN),) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+update:
+	@if [ -z "$(HOST)" ]; then echo "HOST is required. Example: make update HOST=192.168.1.10"; exit 1; fi
+	$(BIN)/grm update $(HOST) $(if $(USER),--user $(USER),) $(if $(KEY),--key $(KEY),) $(if $(VERSION),--version $(VERSION),) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+start:
+	@if [ -z "$(NAME)" ]; then echo "NAME is required. Example: make start NAME=runner1"; exit 1; fi
+	$(BIN)/grm start $(NAME) $(if $(HOST),--host $(HOST),) $(if $(USER),--user $(USER),) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+stop:
+	@if [ -z "$(NAME)" ]; then echo "NAME is required. Example: make stop NAME=runner1"; exit 1; fi
+	$(BIN)/grm stop $(NAME) $(if $(HOST),--host $(HOST),) $(if $(USER),--user $(USER),) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+restart:
+	@if [ -z "$(NAME)" ]; then echo "NAME is required. Example: make restart NAME=runner1"; exit 1; fi
+	$(BIN)/grm restart $(NAME) $(if $(HOST),--host $(HOST),) $(if $(USER),--user $(USER),) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+enable:
+	@if [ -z "$(NAME)" ]; then echo "NAME is required. Example: make enable NAME=runner1"; exit 1; fi
+	$(BIN)/grm enable $(NAME) $(if $(HOST),--host $(HOST),) $(if $(USER),--user $(USER),) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+disable:
+	@if [ -z "$(NAME)" ]; then echo "NAME is required. Example: make disable NAME=runner1"; exit 1; fi
+	$(BIN)/grm disable $(NAME) $(if $(HOST),--host $(HOST),) $(if $(USER),--user $(USER),) $(if $(TOKEN),--token $(TOKEN),) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+status:
+	@if [ -z "$(NAME)" ]; then echo "NAME is required. Example: make status NAME=runner1"; exit 1; fi
+	$(BIN)/grm status $(NAME) $(if $(HOST),--host $(HOST),) $(if $(USER),--user $(USER),) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+remove:
+	@if [ -z "$(NAME)" ]; then echo "NAME is required. Example: make remove NAME=runner1"; exit 1; fi
+	$(BIN)/grm remove $(NAME) $(if $(HOST),--host $(HOST),) $(if $(USER),--user $(USER),) $(if $(TOKEN),--token $(TOKEN),) $(if $(FORCE),--force,) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+list:
+	$(BIN)/grm list $(if $(NO_STATUS),--no-status,) $(if $(ASK_BECOME_PASS),--ask-become-pass,)
+
+# --- Aliases to devx.mak targets ----------------------------------------------
+lint-ruff: devx-lint-ruff
+lint-format: devx-lint-format
+typecheck: devx-typecheck
+lint-bandit: devx-lint-bandit
+lint-deps: devx-lint-deps
+lint: devx-lint
+checkmake: devx-checkmake
+install-tools: devx-install-tools
+install-hooks: devx-install-hooks
+clean: devx-clean
+test-unit: devx-test-unit
+
+# Override devx-pytest-cov to cover both src/ and scripts/
+pytest-cov:
+	@$(BIN)/pytest $(DEVX_TEST_PATHS) -v --cov=src/gitea_runner_manager --cov=scripts --cov-report=term-missing --cov-fail-under=100
+workflow-lint: devx-workflow-lint
+workflow-dryrun: devx-workflow-dryrun
+workflow-check: devx-workflow-check
+
+configure-gitea-pypi:
+	@if [ -z "$$CI_GITEA_TOKEN" ]; then . ./.env 2>/dev/null; fi; \
+	CI_GITEA_TOKEN="$$CI_GITEA_TOKEN"; \
+	if [ -z "$$CI_GITEA_TOKEN" ]; then echo "[configure-gitea-pypi] CI_GITEA_TOKEN not set — skipping (devx must be on public PyPI)"; exit 0; fi; \
+	echo "[configure-gitea-pypi] Gitea PyPI registry configured (CI_GITEA_TOKEN present)."
+
+ansible-lint:
+	PATH="$(PWD)/$(BIN):$$PATH" $(BIN)/ansible-lint ansible/
+
+makefile-lint:
+	@if command -v $(CHECKMAKE) >/dev/null 2>&1 || [ -x "$(CHECKMAKE)" ]; then \
+		$(CHECKMAKE) Makefile; \
+	else \
+		echo "checkmake not found, skipping Makefile lint"; \
+	fi
+
+lint-all: lint ansible-lint makefile-lint workflow-lint
+
+test-integration:
+	$(BIN)/pytest tests/integration/ -v --no-cov
+
+MOLECULE := $(realpath $(BIN))/molecule
+MOLECULE_BASE := cd $(CURDIR)/ansible/roles/gitea-runner && ANSIBLE_ALLOW_BROKEN_CONDITIONALS=true ANSIBLE_INJECT_INVOCATION=1 $(MOLECULE)
+
+# Quick local test: Ubuntu 22.04 only, all scenarios
+molecule:
+	@set -e; for s in default multi-instance lifecycle template-content deregister update; do if [ "$$s" = "default" ]; then $(MOLECULE_BASE) test; else $(MOLECULE_BASE) test -s $$s; fi; done
+
+# All scenarios on all supported platforms (sequential; use CI matrix for parallel execution)
+molecule-all:
+	@$(BIN)/python -m devx.molecule.molecule_all --bin "$(BIN)"
+
+test: test-all
+
+test-all: pytest-cov molecule
+
+# --- Vikunja task and PR management (via devx.mak fragment) -------------------
+# Aliases for project-specific target names
+create-task: devx-create-task
+create-pr: devx-create-pr
+push-with-pr: devx-push-with-pr
+git-push: devx-push

README.md

@@ -0,0 +1,406 @@
+# Gitea Runner Manager (GRM)
+
+A lean command-line tool to automate the installation, configuration, and lifecycle management of Gitea Actions runners on Arch Linux, Ubuntu, and Debian hosts.
+
+Each runner runs in an isolated **rootless Docker** environment under a dedicated system user, enabling multiple runners to operate in parallel on the same host without conflicts. GRM handles the entire runner lifecycle — from initial installation and registration with Gitea, through start/stop/enable/disable operations, to clean removal with deregistration.
+
+> **Pronunciation:** GRM is short for *Gitea Runner Manager*, but say it like **ГРЪМ** (roughly "GRUM") — the Bulgarian word for **thunder**. An open-source project from **Oblachno** (облачно means *cloudy* in Bulgarian).
+
+[![CI](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions/workflows/ci.yml/badge.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+[![License: GPL-3.0](https://img.shields.io/badge/license-GPL--3.0-blue)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/src/branch/master/LICENSE)
+[![Coverage](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/coverage.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+[![Tests](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/tests.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+[![Docs](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/docs.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki)
+[![Code Quality](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/quality.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+[![Version](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/version.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/releases)
+[![Python](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/python.svg)](https://www.python.org/downloads/)
+
+## Why GRM?
+
+Managing Gitea Actions runners manually is tedious and error-prone: you need to create system users, set up rootless Docker, download and configure the runner binary, register it with Gitea, create systemd services, and set up Docker prune timers — all per runner instance. GRM automates this entire process with a single command, and ensures it is idempotent (safe to re-run).
+
+Key problems GRM solves:
+
+- **Isolation without root**: Each runner operates under a dedicated system user with its own rootless Docker daemon, so runners on the same host never interfere with each other or with the host's Docker installation.
+- **Reproducible setup**: The Ansible role is idempotent — running `grm install` twice produces zero changes on the second run, so it is safe for CI/CD pipelines and configuration management.
+- **Full lifecycle management**: Install, start, stop, enable (boot persistence), disable (deregister), update the binary, check status, and remove — all from one CLI.
+- **Local registry**: GRM stores connection metadata locally, so after installation you manage runners by name alone without repeating SSH credentials.
+
+## Features
+
+- **Rootless Docker isolation** — Each runner gets its own rootless Docker daemon under a dedicated system user (`grm-<name>`), with its own Docker socket at `/run/user/<UID>/docker.sock`.
+- **Multi-instance support** — Install and manage multiple isolated runners on the same host, each with independent users, data directories, and systemd user services.
+- **Idempotent Ansible role** — Safe to re-run; the role detects existing state and only applies changes when needed.
+- **Full lifecycle CLI** — `install`, `update`, `start`, `stop`, `enable`, `disable`, `status`, `remove`, `list` — all from a single `grm` command.
+- **Automatic integration testing** — Every installation runs an integration test that verifies the `.runner` registration file and systemd service state.
+- **Docker prune automation** — A systemd user timer automatically prunes old Docker images and volumes on a daily schedule.
+- **Local runner registry** — Connection details are stored in `~/.local/share/grm/runners.json`, so lifecycle commands work by runner name alone.
+- **Internationalisation** — Console messages support English, Bulgarian, German, Russian, Chinese, and Polish via the `GRM_LANG` environment variable.
+- **Security-conscious** — Secrets (registration tokens) are passed via temporary JSON files with `0600` permissions, never on the command line (CWE-214).
+- **Comprehensive CI/CD** — 100% test coverage, automated releases via conventional commits and git-cliff, Molecule tests across 4 OS platforms.
+
+## Quick Start
+
+```bash
+git clone https://git.oblachno.oblachno.fyi/oblachno-oss/grm.git
+cd grm
+git checkout $(git describe --tags --abbrev=0)  # Checkout latest stable release
+make setup
+cp .env.example .env  # Edit with your Gitea URL and tokens
+grm install 192.168.1.10 --user ubuntu --key ~/.ssh/id_ed25519 --name prod-runner
+```
+
+> **Important:** Always checkout the latest release tag before running `make setup`. The `master` branch may contain unreleased changes that are not yet stable. The command above automatically selects the most recent tagged release. To see all available releases, run `git tag --sort=-version:refname` or check the [releases page](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/releases).
+
+> **Tokens:** You need two tokens from your Gitea instance — a **registration token** to register runners, and an **admin API token** for optional post-install verification. See [Getting Started](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Getting-Started.-) for detailed setup instructions.
+
+## Prerequisites
+
+### On your local machine (where you run `grm`)
+
+- **Python 3.12+** — GRM targets Python 3.12 and requires it for development setup.
+- **Ansible** — Installed automatically by `make setup` (via pip). GRM delegates all remote operations to `ansible-playbook`.
+- **SSH access** — A private key that grants access to the target host(s) as a user with sudo privileges.
+
+### On the target host(s) (where runners will be installed)
+
+- **SSH server** — Reachable via the key specified with `--key`.
+- **Sudo access** — The SSH user must have sudo privileges for creating system users, installing packages, and configuring rootless Docker. By default, you will be prompted for the sudo password interactively. For automation, configure passwordless sudo and pass `--no-ask-become-pass`.
+- **Docker** — Installed automatically by the Ansible role (rootless mode). No pre-existing Docker installation is required.
+- **systemd** — Required for user services and lingering. All supported OSes ship with systemd.
+
+## Installation
+
+### Option 1: From source (recommended for full control)
+
+```bash
+git clone https://git.oblachno.oblachno.fyi/oblachno-oss/grm.git
+cd grm
+git checkout $(git describe --tags --abbrev=0)  # Latest stable release
+make setup
+source .venv/bin/activate
+```
+
+`make setup` performs the following:
+
+1. Verifies Python 3.12+ is installed
+2. Creates a virtualenv in `.venv`
+3. Installs all Python dependencies (including Ansible, Click, python-dotenv)
+4. Creates `.env` from `.env.example` if not present
+5. Installs development tools (actionlint, git-cliff, act_runner, checkmake)
+6. Sets up pre-commit hooks
+
+### Option 2: Via pip (for using GRM without the full repo)
+
+GRM is published to the Gitea PyPI registry at
+`https://git.oblachno.oblachno.fyi/api/packages/oblachno-oss/pypi/simple`.
+The registry is publicly readable — no authentication required to install.
+
+**Quick install (one-off):**
+
+```bash
+pip install gitea-runner-manager --index-url https://git.oblachno.oblachno.fyi/api/packages/oblachno-oss/pypi/simple
+```
+
+**Persistent configuration (recommended):**
+
+Add the registry to `~/.pip/pip.conf` so future `pip install` commands find
+GRM automatically:
+
+```ini
+[global]
+extra-index-url = https://git.oblachno.oblachno.fyi/api/packages/oblachno-oss/pypi/simple
+```
+
+Then install normally:
+
+```bash
+pip install gitea-runner-manager
+```
+
+This installs the `grm` CLI and its Python dependencies. The Ansible playbooks
+and role are bundled with the package, so `grm install` works out of the box.
+For development or access to Make targets, clone the repository (Option 1).
+
+### Post-install configuration
+
+After installation, create your `.env` file:
+
+```bash
+cp .env.example .env
+# Edit .env with your Gitea URL and registration token
+```
+
+See the [Configuration](#configuration) section below for details.
+
+## CLI Commands Overview
+
+GRM provides a single `grm` command with subcommands for the full runner lifecycle:
+
+| Command | Description |
+|---------|-------------|
+| `grm install <host>` | Install and configure a runner on a remote host |
+| `grm update <host>` | Update the Gitea Runner binary on a remote host |
+| `grm start <name>` | Start a registered runner |
+| `grm stop <name>` | Stop a registered runner |
+| `grm restart <name>` | Restart a runner (stop, prune Docker images, start) |
+| `grm enable <name>` | Enable a runner to start on boot |
+| `grm disable <name>` | Disable and deregister a runner |
+| `grm status <name>` | Check the status of a registered runner |
+| `grm remove <name>` | Remove a runner completely (with remote cleanup) |
+| `grm remove <name> --force` | Remove only the local registry entry (skip remote cleanup) |
+| `grm list` | List all registered runners with live status |
+| `grm list --no-status` | List registered runners without SSH status checks |
+| `grm health [name]` | Run health check (Docker, runner service, disk) on one or all runners |
+| `grm trigger-workflow <workflow_id>` | Trigger a Gitea Actions workflow via the API |
+| `grm trigger-workflow --list` | List available workflows in the repository |
+| `grm --version` | Show the installed version |
+
+All lifecycle commands (`start`, `stop`, `restart`, `enable`, `disable`, `status`, `remove`) work by runner name and pull connection details from the local registry. You can override any stored value with `--host`, `--user`, or `--key`.
+
+See the [CLI Commands](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/CLI-Commands.-) wiki page for full argument and option reference.
+
+## Configuration
+
+GRM reads configuration from a `.env` file in the current directory (loaded automatically via python-dotenv). You can also set environment variables directly.
+
+### Required variables
+
+| Variable | Description |
+|----------|-------------|
+| `GITEA_URL` | Your Gitea instance URL (e.g., `https://git.example.com`) |
+| `GITEA_REGISTRATION_TOKEN` | Runner registration token from Gitea (starts with `GR`) |
+
+### Optional variables
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `CI_GITEA_TOKEN` | — | Gitea admin API token for optional post-install API verification |
+| `GITEA_INTEGRATION_RETRIES` | `3` | Number of API check retries during integration test |
+| `GITEA_RUNNER_USER` | current login | Default SSH user (overrides `--user`) |
+| `GITEA_RUNNER_KEY` | — | Default SSH key path (overrides `--key`) |
+| `GITEA_RUNNER_LABELS` | — | Default runner labels (overrides `--labels`) |
+| `GRM_LANG` | `en` | UI language: `en`, `bg`, `de`, `ru`, `zh`, `pl` |
+| `GRM_LOG_LEVEL` | `INFO` | Console log level: `DEBUG`, `INFO`, `WARNING`, `ERROR`, `CRITICAL` |
+| `GRM_BECOME_PASSWORD_FILE` | — | Path to file containing sudo password (see [Sudo Password Handling](#sudo-password-handling)) |
+| `ANSIBLE_BECOME_PASSWORD_FILE` | — | Fallback sudo password file path (Ansible-native env var) |
+
+### Sudo Password Handling
+
+GRM delegates remote operations to Ansible, which uses `sudo` (become) on the target host. There are several ways to provide the sudo password, in priority order:
+
+1. **`--become-password-file <path>`** (CLI flag, global) — Read sudo password from a file. Works for all commands including `grm list`.
+2. **`GRM_BECOME_PASSWORD_FILE`** (env var) — Same as above, set in `.env` or environment.
+3. **`ANSIBLE_BECOME_PASSWORD_FILE`** (env var) — Fallback, Ansible-native env var.
+4. **Interactive prompt** — If none of the above are set, GRM prompts for the sudo password (hidden input).
+5. **Piped stdin** — When stdin is not a TTY, reads the first line: `echo 'password' | grm list`.
+6. **`--no-ask-become-pass`** — Skip sudo password entirely (use when the target user has passwordless sudo).
+
+For `grm list` specifically, the password is collected once and reused for all runner status checks via `--become-password-file`, avoiding stdin consumption issues when checking multiple runners.
+
+**Examples:**
+
+```bash
+# Interactive prompt (default)
+grm install 192.168.1.10 --user ubuntu
+
+# Password file (recommended for automation)
+echo 'my-sudo-pass' > ~/.grm-sudo-pass
+chmod 600 ~/.grm-sudo-pass
+grm --become-password-file ~/.grm-sudo-pass install 192.168.1.10 --user ubuntu
+
+# Env var (set in .env)
+GRM_BECOME_PASSWORD_FILE=~/.grm-sudo-pass
+grm list  # uses the file automatically
+
+# Piped stdin (for scripts)
+echo 'my-sudo-pass' | grm list
+
+# Passwordless sudo on target
+grm install 192.168.1.10 --user ubuntu --no-ask-become-pass
+```
+
+### Verbose Output
+
+Pass `-v` / `--verbose` (global flag, before the subcommand) to enable Ansible verbose mode (`-v`):
+
+```bash
+grm --verbose install 192.168.1.10 --user ubuntu
+grm -v status prod-runner
+```
+
+### Runner Labels
+
+Runner labels control which jobs a runner accepts. They are set at installation time:
+
+- **`--labels "docker:docker://alpine:latest"`** — Set specific labels.
+- **`--labels ""`** — Explicitly set **no labels** (overrides `GITEA_RUNNER_LABELS` env var).
+- **No `--labels` flag** — Uses `GITEA_RUNNER_LABELS` env var if set, otherwise the Ansible role default.
+
+```bash
+# Custom labels
+grm install 192.168.1.10 --user ubuntu --labels "docker:docker://alpine:latest,ubuntu-22.04:docker://ubuntu:22.04"
+
+# Explicitly no labels (overrides GITEA_RUNNER_LABELS env var)
+grm install 192.168.1.10 --user ubuntu --labels ""
+
+# Use GITEA_RUNNER_LABELS from .env (or role default if unset)
+grm install 192.168.1.10 --user ubuntu
+```
+
+### Getting tokens
+
+**Registration token** (required): Navigate to your Gitea instance:
+
+- **Instance-level**: Site Administration → Actions → Runners → Create Registration Token
+- **Organization-level**: Organization → Settings → Actions → Runners → Create Registration Token
+- **Repository-level**: Repository → Settings → Actions → Runners → Create Registration Token
+
+Use instance-level tokens for shared runners, and repo-level tokens for dedicated runners.
+
+**Admin API token** (optional): Settings → Applications → Generate New Token, with the `admin` scope (or at minimum: `read:user`, `read:repository`, `read:admin`). When set, GRM queries the Gitea API after installation to confirm the runner appears in the runner list. This is purely informational and does not affect pass/fail.
+
+## Multi-Instance Support
+
+One of GRM's core features is the ability to run multiple isolated runners on the same host. Each runner instance gets:
+
+- **Dedicated system user**: `grm-<name>` with its own home directory at `/home/grm-<name>/`
+- **Rootless Docker daemon**: Isolated Docker socket at `/run/user/<UID>/docker.sock`
+- **Data directory**: `/var/lib/gitea-runner/<name>/`
+- **Config directory**: `/etc/gitea-runner/<name>/`
+- **Systemd user service**: `gitea-runner.service` (independent start/stop/enable)
+- **Docker prune timer**: Per-instance daily cleanup
+
+```bash
+# Install two runners on the same host
+grm install 192.168.1.10 --user ubuntu --name workflow-runner
+grm install 192.168.1.10 --user ubuntu --name build-runner
+
+# Manage them independently by name
+grm stop workflow-runner
+grm status build-runner
+grm list
+```
+
+## Security Model
+
+GRM is designed with security as a first-class concern:
+
+- **Rootless Docker**: Each runner operates under a dedicated unprivileged system user. The Docker daemon runs in rootless mode, so containers never have root access to the host. User namespaces (`subuid`/`subgid`) are configured automatically.
+- **Dedicated users**: Each runner gets its own system user (`grm-<name>`) with lingering enabled, so the user's systemd services run without an active login session.
+- **Secret handling**: Registration tokens and admin tokens are never passed on the command line. They are written to temporary JSON files with `0600` permissions and passed to Ansible via `--extra-vars @tempfile`. The temp file is deleted immediately after execution. This prevents secrets from being visible in the process list (`ps aux`), addressing CWE-214.
+- **No shell injection**: The CLI never uses `shell=True` with subprocess. All Ansible commands are constructed as argument lists.
+- **Bandit security scan**: The CI pipeline runs Bandit on every PR to catch common Python security issues.
+
+## Supported Operating Systems
+
+GRM supports and tests the following operating systems:
+
+| OS | Versions | Package manager |
+|----|----------|-----------------|
+| Arch Linux | rolling | pacman |
+| Ubuntu | 22.04, 24.04 | apt |
+| Debian | 12 | apt |
+
+All supported OSes are tested in CI via Molecule scenarios on every PR that changes Ansible files. The platform matrix is defined in `devx.molecule.platforms` as the single source of truth.
+
+## Development Setup
+
+GRM uses a comprehensive development setup with 100% test coverage enforcement, multiple linters, and Molecule integration tests.
+
+### Quick development setup
+
+```bash
+git clone https://git.oblachno.oblachno.fyi/oblachno-oss/grm.git
+cd grm
+git checkout $(git describe --tags --abbrev=0)  # Latest stable release
+make setup
+source .venv/bin/activate
+```
+
+### Make targets
+
+| Target | Description |
+|--------|-------------|
+| `make setup` | Full setup: venv, deps, hooks, CI tools |
+| `make lint-all` | ruff + pyright + bandit + ansible-lint + checkmake + actionlint |
+| `make pytest-cov` | Unit tests with 100% coverage enforcement |
+| `make test-unit` | Unit tests without coverage |
+| `make molecule` | All 6 Molecule scenarios on Ubuntu 22.04 |
+| `make molecule-all` | All 6 scenarios on all 4 supported OSes |
+| `make test-all` | pytest-cov + molecule |
+| `make workflow-lint` | Static lint of workflow YAML (actionlint) |
+| `make workflow-dryrun` | Dry-run all workflows in Docker |
+| `make workflow-check` | workflow-lint + workflow-dryrun |
+
+See the [Development Setup](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Development-Setup.-) wiki page for full details.
+
+## Architecture Overview
+
+GRM consists of two layers:
+
+1. **Python CLI** (`src/gitea_runner_manager/`) — Built with Click, handles argument parsing, environment loading, i18n translations, and delegates to Ansible via the `ansible-playbook` subprocess. Secrets are passed via temporary JSON files to avoid exposure in the process list.
+
+2. **Ansible Role** (`ansible/roles/gitea-runner/`) — Idempotent role that creates a dedicated system user, sets up rootless Docker, installs the runner binary, creates a systemd user service, registers the runner with Gitea, and sets up a Docker prune timer.
+
+```
+grm install <host>
+  └── RunnerManager.install()
+      └── ansible-playbook ansible/install-runner.yml
+          └── role: gitea-runner
+              ├── user_setup.yml       (create per-runner system user + lingering)
+              ├── rootless_docker.yml  (rootless Docker setup under runner user)
+              ├── install_runner.yml   (download binary, config, register, service)
+              ├── prune.yml            (Docker prune timer)
+              └── integration_test.yml (validate service is active)
+```
+
+### Python modules
+
+| Module | Description |
+|--------|-------------|
+| `cli.py` | Click-based CLI entry point — defines all commands |
+| `runner_manager.py` | Ansible orchestration + registry integration |
+| `executor.py` | Ansible subprocess execution with log capture |
+| `registry.py` | Local JSON runner registry at `~/.local/share/grm/runners.json` |
+| `i18n.py` | Internationalisation (en, bg, de, ru, zh, pl) |
+| `exceptions.py` | Custom exceptions (`GRMError`, `AnsibleError`) |
+| `logging_config.py` | Logging to `~/.local/state/grm/logs/grm.log` |
+| `report.py` | Operation report tracking with step status |
+| `ui.py` | Colorised console output via Click |
+
+See the [Architecture](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Architecture) wiki page for the full component diagram and data flow.
+
+## Documentation
+
+Full documentation lives on the [**GRM Wiki**](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki).
+
+### User Documentation
+
+- [Getting Started](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Getting-Started.-) — Installation, quick start, token setup, first run
+- [Installation](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Installation) — Prerequisites, setup, multiple instances
+- [CLI Commands](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/CLI-Commands.-) — All commands with arguments and options
+- [Troubleshooting](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Troubleshooting) — Common issues and solutions
+- [FAQ](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/FAQ) — Frequently asked questions
+
+### Technical Documentation
+
+- [Architecture](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Architecture) — High-level design, component interactions, data flow
+- [Development Setup](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Development-Setup.-) — Environment setup, dependencies, local testing
+- [CI/CD Workflow](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/CI-CD-Workflow.-) — How CI works, release process, branch protection
+- [Testing Strategy](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Testing-Strategy.-) — Unit, integration, and Molecule tests
+- [Decision Log](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Decision-Log.-) — Key technical decisions and rationale
+- [Contributing Guide](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Contributing-Guide.-) — Coding standards, PR workflow, commit rules
+
+## Links
+
+- [Repository](https://git.oblachno.oblachno.fyi/oblachno-oss/grm)
+- [Releases](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/releases)
+- [Issues](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/issues)
+- [CI/CD Pipeline](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+- [Changelog](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/src/branch/master/CHANGELOG.md)
+- [Wiki](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki)
+
+## License
+
+GPL-3.0 — See [LICENSE](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/src/branch/master/LICENSE) for the full text.

TROUBLESHOOTING.md

@@ -0,0 +1,3 @@
+# Troubleshooting
+
+See the [Troubleshooting guide](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Troubleshooting) in the wiki.

ansible/disable-runner.yml

@@ -0,0 +1,44 @@
+---
+- name: Disable Gitea Actions runner
+  hosts: all
+  become: true
+  vars: {}
+  tasks:
+    - name: Include systemd availability check
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: systemd_check.yml
+
+    - name: Stop gitea-runner user service
+      ansible.builtin.command: systemctl --user stop gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+      when: systemd_available.stat.exists
+      changed_when: true
+
+    - name: Stop and disable healthcheck timer
+      ansible.builtin.command: systemctl --user stop --disable runner-healthcheck.timer
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+      when: systemd_available.stat.exists
+      changed_when: true
+      failed_when: false
+
+    - name: Include deregistration
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: deregister.yml
+      when: not skip_runner_registration | default(false)
+
+    - name: Disable gitea-runner user service
+      ansible.builtin.command: systemctl --user disable gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+      when: systemd_available.stat.exists
+      changed_when: true

ansible/enable-runner.yml

@@ -0,0 +1,28 @@
+---
+- name: Enable Gitea Actions runner
+  hosts: all
+  become: true
+  vars: {}
+  tasks:
+    - name: Include systemd availability check
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: systemd_check.yml
+
+    - name: Enable gitea-runner user service
+      ansible.builtin.command: systemctl --user enable gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+      when: systemd_available.stat.exists
+      changed_when: true
+
+    - name: Start gitea-runner user service
+      ansible.builtin.command: systemctl --user start gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+      when: systemd_available.stat.exists
+      changed_when: true

ansible/group_vars/all.yml

@@ -0,0 +1,3 @@
+---
+# Default variables for all hosts
+ansible_python_interpreter: /usr/bin/python3

ansible/install-runner.yml

@@ -0,0 +1,6 @@
+---
+- name: Install Gitea Actions runner
+  hosts: all
+  become: true
+  roles:
+    - role: gitea-runner

ansible/inventory.example

@@ -0,0 +1,13 @@
+# Gitea Runner Manager inventory example
+# Each line represents a target host for runner installation.
+#
+# Required variables per host:
+#   ansible_user                — SSH login user
+#   ansible_ssh_private_key_file — Path to SSH private key
+#
+# Optional variables per host:
+#   gitea_runner_version=1.0.8  — Runner binary version
+
+[runners]
+192.168.1.10 ansible_user=ubuntu ansible_ssh_private_key_file=~/.ssh/id_ed25519
+runner.example.com ansible_user=arch ansible_ssh_private_key_file=~/.ssh/id_ed25519

ansible/remove-runner.yml

@@ -0,0 +1,194 @@
+---
+- name: Remove Gitea Actions runner
+  hosts: all
+  become: true
+  vars: {}
+  tasks:
+    - name: Include systemd availability check
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: systemd_check.yml
+
+    - name: Get runner user UID
+      ansible.builtin.command: id -u "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      register: runner_uid_result
+      changed_when: false
+      failed_when: false
+
+    - name: Set runner UID fact
+      ansible.builtin.set_fact:
+        gitea_runner_uid: "{{ runner_uid_result.stdout }}"
+      when: runner_uid_result.rc == 0
+
+    - name: Stop gitea-runner user service
+      ansible.builtin.command: systemctl --user stop gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+      when: systemd_available.stat.exists
+      changed_when: true
+      failed_when: false
+
+    - name: Disable gitea-runner user service
+      ansible.builtin.command: systemctl --user disable gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+      when: systemd_available.stat.exists
+      changed_when: true
+      failed_when: false
+
+    - name: Force-remove all Docker containers (rootless)
+      ansible.builtin.shell: |
+        set -o pipefail
+        docker ps -aq 2>/dev/null | xargs -r docker rm -f 2>/dev/null || true
+      args:
+        executable: /bin/bash
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+        DOCKER_HOST: "unix:///run/user/{{ gitea_runner_uid | default('') }}/docker.sock"
+      changed_when: false
+      failed_when: false
+
+    - name: Prune all Docker images, volumes, and build cache (rootless)
+      ansible.builtin.command: docker system prune -af --volumes
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+        DOCKER_HOST: "unix:///run/user/{{ gitea_runner_uid | default('') }}/docker.sock"
+      changed_when: false
+      failed_when: false
+
+    - name: Stop rootless Docker daemon
+      ansible.builtin.command: systemctl --user stop docker
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+      changed_when: true
+      failed_when: false
+
+    - name: Include deregistration
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: deregister.yml
+      when: not skip_runner_registration | default(false)
+
+    - name: Stop and disable healthcheck timer
+      ansible.builtin.command: systemctl --user stop --disable runner-healthcheck.timer
+      become: true
+      become_user: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
+      when: systemd_available.stat.exists
+      changed_when: true
+      failed_when: false
+
+    - name: Remove docker-prune user service file
+      ansible.builtin.file:
+        path: "{{ gitea_runner_home | default('/home/grm-' ~ runner_name) }}/.config/systemd/user/docker-prune.service"
+        state: absent
+      failed_when: false
+
+    - name: Remove docker-prune user timer file
+      ansible.builtin.file:
+        path: "{{ gitea_runner_home | default('/home/grm-' ~ runner_name) }}/.config/systemd/user/docker-prune.timer"
+        state: absent
+      failed_when: false
+
+    - name: Remove healthcheck user service file
+      ansible.builtin.file:
+        path: "{{ gitea_runner_home | default('/home/grm-' ~ runner_name) }}/.config/systemd/user/runner-healthcheck.service"
+        state: absent
+      failed_when: false
+
+    - name: Remove healthcheck user timer file
+      ansible.builtin.file:
+        path: "{{ gitea_runner_home | default('/home/grm-' ~ runner_name) }}/.config/systemd/user/runner-healthcheck.timer"
+        state: absent
+      failed_when: false
+
+    - name: Remove healthcheck script
+      ansible.builtin.file:
+        path: "{{ gitea_runner_config_dir | default('/etc/gitea-runner/' ~ runner_name) }}/healthcheck.sh"
+        state: absent
+      failed_when: false
+
+    - name: Remove systemd user unit file
+      ansible.builtin.file:
+        path: "{{ gitea_runner_home | default('/home/grm-' ~ runner_name) }}/.config/systemd/user/gitea-runner.service"
+        state: absent
+      when: remove_systemd_template | default(true)
+
+    - name: Kill remaining processes of runner user
+      ansible.builtin.command: loginctl terminate-user "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      failed_when: false
+      changed_when: true
+
+    - name: Wait for processes to terminate
+      ansible.builtin.command: "pkill -u {{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      failed_when: false
+      changed_when: false
+
+    - name: Disable lingering for runner user
+      ansible.builtin.command: loginctl disable-linger "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+      failed_when: false
+      changed_when: true
+
+    - name: Remove runner user and home directory
+      ansible.builtin.user:
+        name: "{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}"
+        state: absent
+        remove: true
+      when: remove_runner_user | default(true)
+      failed_when: false
+
+    - name: Remove Docker data root when user is kept
+      ansible.builtin.file:
+        path: "{{ gitea_runner_home | default('/home/grm-' ~ runner_name) }}/.local/share/docker"
+        state: absent
+      when: not (remove_runner_user | default(true))
+      failed_when: false
+
+    - name: Remove act cache when user is kept
+      ansible.builtin.file:
+        path: "{{ gitea_runner_home | default('/home/grm-' ~ runner_name) }}/.cache/act"
+        state: absent
+      when: not (remove_runner_user | default(true))
+      failed_when: false
+
+    - name: Remove systemd user config dir when user is kept
+      ansible.builtin.file:
+        path: "{{ gitea_runner_home | default('/home/grm-' ~ runner_name) }}/.config/systemd/user"
+        state: absent
+      when: not (remove_runner_user | default(true))
+      failed_when: false
+
+    - name: Remove subuid entry for runner user
+      ansible.builtin.lineinfile:
+        path: /etc/subuid
+        regexp: "^{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}:"
+        state: absent
+      failed_when: false
+
+    - name: Remove subgid entry for runner user
+      ansible.builtin.lineinfile:
+        path: /etc/subgid
+        regexp: "^{{ gitea_runner_service_user | default('grm-' ~ runner_name) }}:"
+        state: absent
+      failed_when: false
+
+    - name: Remove runner data directory
+      ansible.builtin.file:
+        path: "{{ gitea_runner_data_dir | default('/var/lib/gitea-runner/' ~ runner_name) }}"
+        state: absent
+
+    - name: Remove runner config directory
+      ansible.builtin.file:
+        path: "{{ gitea_runner_config_dir | default('/etc/gitea-runner/' ~ runner_name) }}"
+        state: absent

ansible/requirements.yml

@@ -0,0 +1,7 @@
+collections:
+  - name: community.general
+    version: "==13.1.0"
+  - name: ansible.posix
+    version: "==2.2.0"
+  - name: community.docker
+    version: "==5.2.1"

ansible/restart-runner.yml

@@ -0,0 +1,48 @@
+---
+- name: Restart Gitea Actions runner (stop, prune images, start)
+  hosts: all
+  become: true
+  vars:
+    prune_images: true
+  tasks:
+    - name: Include systemd availability check
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: systemd_check.yml
+
+    - name: Resolve runner UID
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: resolve_uid.yml
+
+    - name: Stop gitea-runner user service
+      ansible.builtin.command: systemctl --user stop gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+      when: systemd_available.stat.exists
+      changed_when: true
+
+    - name: Prune stale runner images from rootless Docker
+      ansible.builtin.command:
+        cmd: python3 {{ playbook_dir }}/../scripts/prune_runner_images.py
+      become: true
+      become_user: "{{ gitea_runner_service_user }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+        DOCKER_HOST: "unix:///run/user/{{ gitea_runner_uid }}/docker.sock"
+      when:
+        - systemd_available.stat.exists
+        - prune_images | default(true)
+      changed_when: true
+      failed_when: false
+
+    - name: Start gitea-runner user service
+      ansible.builtin.command: systemctl --user start gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+      when: systemd_available.stat.exists
+      changed_when: true

ansible/roles/gitea-runner/defaults/main.yml

@@ -0,0 +1,55 @@
+---
+gitea_runner_version: "1.0.8"
+runner_labels: "docker,ubuntu-latest:docker://runner-images:ubuntu-26.04"
+skip_runner_registration: false
+
+# Per-runner user (rootless isolation)
+gitea_runner_user_prefix: "grm-"
+gitea_runner_base_home: "/home"
+gitea_runner_service_user: "{{ gitea_runner_user_prefix }}{{ runner_name }}"
+gitea_runner_home: "{{ gitea_runner_base_home }}/{{ gitea_runner_service_user }}"
+
+# Base paths (instance-scoped via runner_name)
+gitea_runner_base_data_dir: "/var/lib/gitea-runner"
+gitea_runner_base_config_dir: "/etc/gitea-runner"
+gitea_runner_data_dir: "{{ gitea_runner_base_data_dir }}/{{ runner_name }}"
+gitea_runner_config_dir: "{{ gitea_runner_base_config_dir }}/{{ runner_name }}"
+gitea_runner_binary_path: "/usr/local/bin/gitea_runner"
+
+# Prune configuration
+gitea_runner_prune_until: "24h"
+gitea_runner_prune_schedule: "daily"
+gitea_runner_prune_label: "gitea-runner=true"
+
+# Service configuration
+gitea_runner_service_restart_sec: "5"
+
+# Health check configuration
+gitea_runner_healthcheck_interval: "5min"
+gitea_runner_healthcheck_boot_delay: "2min"
+gitea_runner_healthcheck_disk_threshold: 85
+gitea_runner_healthcheck_script_path: "{{ gitea_runner_config_dir }}/healthcheck.sh"
+
+# Admin token for runner deregistration via Gitea API.
+# If not set, falls back to registration_token (which likely lacks admin scope).
+# Set this to a token with admin scope to enable automatic runner cleanup on removal.
+gitea_admin_token: ""
+
+# Removal defaults
+remove_systemd_template: true
+remove_runner_user: true
+
+# Runner configuration
+gitea_runner_log_level: "info"
+gitea_runner_container_label: "gitea-runner=true"
+gitea_runner_file: ".runner"
+
+# Docker installation (for rootless dependencies)
+docker_gpg_key_path: "/etc/apt/keyrings/docker.gpg"
+docker_apt_arch: "{{ 'amd64' if ansible_facts['architecture'] == 'x86_64' else ansible_facts['architecture'] }}"
+docker_apt_source_line: >-
+  deb [arch={{ docker_apt_arch }} signed-by={{ docker_gpg_key_path }}]
+  https://download.docker.com/linux/{{ ansible_facts['distribution'] | lower }}
+  {{ ansible_facts['distribution_release'] }} stable
+# Set to false in CI/molecule to skip rootless daemon startup (needs kernel userns)
+docker_rootless_setup: true

ansible/roles/gitea-runner/handlers/main.yml

@@ -0,0 +1,12 @@
+---
+- name: Restart gitea-runner
+  ansible.builtin.command: systemctl --user restart gitea-runner
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  changed_when: true
+  when:
+    - ansible_facts is defined
+    - ansible_facts['service_mgr'] | default('') == 'systemd'
+    - docker_rootless_setup

ansible/roles/gitea-runner/molecule/common/prepare.yml

@@ -0,0 +1,34 @@
+---
+- name: Prepare
+  hosts: all
+  become: true
+  tasks:
+    - name: Update apt cache
+      ansible.builtin.apt:
+        update_cache: true
+        cache_valid_time: 0
+      when: ansible_facts['os_family'] == 'Debian'
+
+    - name: Install prerequisites for rootless Docker role (Debian/Ubuntu)
+      ansible.builtin.apt:
+        name:
+          - curl
+          - gpg
+          - python3-debian
+          - ca-certificates
+        state: present
+      when: ansible_facts['os_family'] == 'Debian'
+
+    - name: Update pacman cache
+      community.general.pacman:
+        update_cache: true
+      when: ansible_facts['os_family'] == 'Archlinux'
+
+    - name: Install prerequisites for rootless Docker role (Arch Linux)
+      community.general.pacman:
+        name:
+          - curl
+          - gnupg
+          - ca-certificates
+        state: present
+      when: ansible_facts['os_family'] == 'Archlinux'

ansible/roles/gitea-runner/molecule/default/converge.yml

@@ -0,0 +1,12 @@
+---
+- name: Converge
+  hosts: all
+  become: true
+  vars:
+    gitea_url: "http://localhost:3000"
+    registration_token: "fake-token-for-testing"
+    runner_name: "molecule-test-runner"
+    skip_runner_registration: true
+    docker_rootless_setup: false
+  roles:
+    - role: gitea-runner

ansible/roles/gitea-runner/molecule/default/molecule.yml

@@ -0,0 +1,39 @@
+---
+driver:
+  name: docker
+
+platforms:
+  - name: ${MOLECULE_PLATFORM_NAME:-ubuntu-2204}
+    image: ${MOLECULE_PLATFORM_IMAGE:-ubuntu:26.04}
+    command: ${MOLECULE_PLATFORM_COMMAND:-sleep infinity}
+    volumes:
+      - /sys/fs/cgroup:/sys/fs/cgroup:rw
+    cgroupns_mode: host
+    privileged: true
+    pre_build_image: false
+
+provisioner:
+  name: ansible
+  playbooks:
+    converge: converge.yml
+    prepare: ../common/prepare.yml
+  env:
+    ANSIBLE_ROLES_PATH: "../../.."
+
+scenario:
+  test_sequence:
+    - dependency
+    - cleanup
+    - destroy
+    - syntax
+    - create
+    - prepare
+    - converge
+    - idempotence
+    - side_effect
+    - verify
+    - cleanup
+    - destroy
+
+verifier:
+  name: ansible

ansible/roles/gitea-runner/molecule/default/verify.yml

@@ -0,0 +1,116 @@
+---
+- name: Verify
+  hosts: all
+  become: true
+  vars:
+    runner_name: "molecule-test-runner"
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Check runner user exists
+      ansible.builtin.user:
+        name: "{{ gitea_runner_service_user }}"
+      register: user_info
+      check_mode: true
+
+    - name: Assert runner user exists
+      ansible.builtin.assert:
+        that:
+          - user_info.state == "present"
+        fail_msg: "Runner system user was not created"
+
+    - name: Check runner binary exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_binary_path }}"
+      register: binary_stat
+
+    - name: Assert runner binary exists
+      ansible.builtin.assert:
+        that:
+          - binary_stat.stat.exists
+        fail_msg: "Gitea runner binary is missing"
+
+    - name: Check systemd user service exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/gitea-runner.service"
+      register: service_stat
+
+    - name: Assert user service exists
+      ansible.builtin.assert:
+        that:
+          - service_stat.stat.exists
+        fail_msg: "Systemd user service is missing"
+
+    - name: Check instance data directory exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_data_dir }}"
+      register: data_dir_stat
+
+    - name: Assert instance data directory exists
+      ansible.builtin.assert:
+        that:
+          - data_dir_stat.stat.exists
+        fail_msg: "Instance data directory is missing"
+
+    - name: Check config file exists in config directory
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_config_dir }}/config.yaml"
+      register: config_stat
+
+    - name: Assert config file exists
+      ansible.builtin.assert:
+        that:
+          - config_stat.stat.exists
+        fail_msg: "Config file is missing"
+
+    - name: Check prune timer exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/docker-prune.timer"
+      register: timer_stat
+
+    - name: Assert prune timer exists
+      ansible.builtin.assert:
+        that:
+          - timer_stat.stat.exists
+        fail_msg: "Docker prune timer is missing"
+
+    - name: Check healthcheck script exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_healthcheck_script_path }}"
+      register: healthcheck_script_stat
+
+    - name: Assert healthcheck script exists
+      ansible.builtin.assert:
+        that:
+          - healthcheck_script_stat.stat.exists
+        fail_msg: "Healthcheck script is missing"
+
+    - name: Assert healthcheck script is executable
+      ansible.builtin.assert:
+        that:
+          - healthcheck_script_stat.stat.mode == "0755"
+        fail_msg: "Healthcheck script is not executable"
+
+    - name: Check healthcheck service exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/runner-healthcheck.service"
+      register: healthcheck_service_stat
+
+    - name: Assert healthcheck service exists
+      ansible.builtin.assert:
+        that:
+          - healthcheck_service_stat.stat.exists
+        fail_msg: "Healthcheck systemd service is missing"
+
+    - name: Check healthcheck timer exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/runner-healthcheck.timer"
+      register: healthcheck_timer_stat
+
+    - name: Assert healthcheck timer exists
+      ansible.builtin.assert:
+        that:
+          - healthcheck_timer_stat.stat.exists
+        fail_msg: "Healthcheck systemd timer is missing"

ansible/roles/gitea-runner/molecule/deregister/converge.yml

@@ -0,0 +1,12 @@
+---
+- name: Converge
+  hosts: all
+  become: true
+  vars:
+    gitea_url: "http://localhost:3000"
+    registration_token: "fake-token-for-testing"
+    runner_name: "deregister-test-runner"
+    skip_runner_registration: true
+    docker_rootless_setup: false
+  roles:
+    - role: gitea-runner

ansible/roles/gitea-runner/molecule/deregister/molecule.yml

@@ -0,0 +1,40 @@
+---
+driver:
+  name: docker
+
+platforms:
+  - name: ${MOLECULE_PLATFORM_NAME:-ubuntu-2204}
+    image: ${MOLECULE_PLATFORM_IMAGE:-ubuntu:26.04}
+    command: ${MOLECULE_PLATFORM_COMMAND:-sleep infinity}
+    volumes:
+      - /sys/fs/cgroup:/sys/fs/cgroup:rw
+    cgroupns_mode: host
+    privileged: true
+    pre_build_image: false
+
+provisioner:
+  name: ansible
+  playbooks:
+    converge: converge.yml
+    prepare: ../common/prepare.yml
+    side_effect: side_effect.yml
+  env:
+    ANSIBLE_ROLES_PATH: "../../.."
+
+scenario:
+  test_sequence:
+    - dependency
+    - cleanup
+    - destroy
+    - syntax
+    - create
+    - prepare
+    - converge
+    - idempotence
+    - side_effect
+    - verify
+    - cleanup
+    - destroy
+
+verifier:
+  name: ansible

ansible/roles/gitea-runner/molecule/deregister/side_effect.yml

@@ -0,0 +1,33 @@
+---
+- name: Create fake runner registration file
+  hosts: all
+  become: true
+  vars:
+    runner_name: "deregister-test-runner"
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Ensure fake .runner file exists
+      ansible.builtin.copy:
+        dest: "{{ gitea_runner_data_dir }}/.runner"
+        content: |
+          {"id": 1, "uuid": "test-uuid-1234", "name": "{{ runner_name }}", "address": "http://localhost:3000"}
+        owner: "{{ gitea_runner_service_user }}"
+        group: "{{ gitea_runner_service_user }}"
+        mode: "0644"
+
+- name: Deregister runner
+  hosts: all
+  become: true
+  vars:
+    runner_name: "deregister-test-runner"
+    registration_token: "fake-token-for-testing"
+    gitea_url: "http://localhost:3000"
+    skip_runner_registration: false
+  tasks:
+    - name: Include deregistration tasks
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: deregister.yml

ansible/roles/gitea-runner/molecule/deregister/verify.yml

@@ -0,0 +1,32 @@
+---
+- name: Verify
+  hosts: all
+  become: true
+  vars:
+    runner_name: "deregister-test-runner"
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Check registration file was removed
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_data_dir }}/.runner"
+      register: runner_file_stat
+
+    - name: Assert registration file no longer exists
+      ansible.builtin.assert:
+        that:
+          - not runner_file_stat.stat.exists
+        fail_msg: "Registration file (.runner) was not removed by deregistration"
+
+    - name: Check systemd user service still exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/gitea-runner.service"
+      register: service_stat
+
+    - name: Assert user service still exists after deregister
+      ansible.builtin.assert:
+        that:
+          - service_stat.stat.exists
+        fail_msg: "Systemd user service was incorrectly removed"

ansible/roles/gitea-runner/molecule/lifecycle/converge.yml

@@ -0,0 +1,12 @@
+---
+- name: Converge
+  hosts: all
+  become: true
+  vars:
+    gitea_url: "http://localhost:3000"
+    registration_token: "fake-token-for-testing"
+    runner_name: "lifecycle-test-runner"
+    skip_runner_registration: true
+    docker_rootless_setup: false
+  roles:
+    - role: gitea-runner

ansible/roles/gitea-runner/molecule/lifecycle/molecule.yml

@@ -0,0 +1,40 @@
+---
+driver:
+  name: docker
+
+platforms:
+  - name: ${MOLECULE_PLATFORM_NAME:-ubuntu-2204}
+    image: ${MOLECULE_PLATFORM_IMAGE:-ubuntu:26.04}
+    command: ${MOLECULE_PLATFORM_COMMAND:-sleep infinity}
+    volumes:
+      - /sys/fs/cgroup:/sys/fs/cgroup:rw
+    cgroupns_mode: host
+    privileged: true
+    pre_build_image: false
+
+provisioner:
+  name: ansible
+  playbooks:
+    converge: converge.yml
+    prepare: ../common/prepare.yml
+    side_effect: side_effect.yml
+  env:
+    ANSIBLE_ROLES_PATH: "../../.."
+
+scenario:
+  test_sequence:
+    - dependency
+    - cleanup
+    - destroy
+    - syntax
+    - create
+    - prepare
+    - converge
+    - idempotence
+    - side_effect
+    - verify
+    - cleanup
+    - destroy
+
+verifier:
+  name: ansible

ansible/roles/gitea-runner/molecule/lifecycle/side_effect.yml

@@ -0,0 +1,40 @@
+---
+- name: Stop runner instance
+  hosts: all
+  become: true
+  vars:
+    runner_name: "lifecycle-test-runner"
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Stop gitea-runner user service
+      ansible.builtin.command: "sudo -u {{ gitea_runner_service_user }} systemctl --user stop gitea-runner"
+      changed_when: true
+      failed_when: false
+
+    - name: Disable gitea-runner user service
+      ansible.builtin.command: "sudo -u {{ gitea_runner_service_user }} systemctl --user disable gitea-runner"
+      changed_when: true
+      failed_when: false
+
+- name: Re-enable and start runner
+  hosts: all
+  become: true
+  vars:
+    runner_name: "lifecycle-test-runner"
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Enable gitea-runner user service
+      ansible.builtin.command: "sudo -u {{ gitea_runner_service_user }} systemctl --user enable gitea-runner"
+      changed_when: true
+      failed_when: false
+
+    - name: Start gitea-runner user service
+      ansible.builtin.command: "sudo -u {{ gitea_runner_service_user }} systemctl --user start gitea-runner"
+      changed_when: true
+      failed_when: false

ansible/roles/gitea-runner/molecule/lifecycle/verify.yml

@@ -0,0 +1,32 @@
+---
+- name: Verify
+  hosts: all
+  become: true
+  vars:
+    runner_name: "lifecycle-test-runner"
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Check systemd user service exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/gitea-runner.service"
+      register: service_stat
+
+    - name: Assert user service exists
+      ansible.builtin.assert:
+        that:
+          - service_stat.stat.exists
+        fail_msg: "Systemd user service is missing"
+
+    - name: Check instance data directory exists after lifecycle
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_data_dir }}"
+      register: data_dir_stat
+
+    - name: Assert instance data directory exists
+      ansible.builtin.assert:
+        that:
+          - data_dir_stat.stat.exists
+        fail_msg: "Instance data directory is missing after lifecycle"

ansible/roles/gitea-runner/molecule/multi-instance/converge.yml

@@ -0,0 +1,24 @@
+---
+- name: Converge first runner instance
+  hosts: all
+  become: true
+  vars:
+    gitea_url: "http://localhost:3000"
+    registration_token: "fake-token-for-testing"
+    runner_name: "molecule-runner-a"
+    skip_runner_registration: true
+    docker_rootless_setup: false
+  roles:
+    - role: gitea-runner
+
+- name: Converge second runner instance
+  hosts: all
+  become: true
+  vars:
+    gitea_url: "http://localhost:3000"
+    registration_token: "fake-token-for-testing"
+    runner_name: "molecule-runner-b"
+    skip_runner_registration: true
+    docker_rootless_setup: false
+  roles:
+    - role: gitea-runner

ansible/roles/gitea-runner/molecule/multi-instance/molecule.yml

@@ -0,0 +1,39 @@
+---
+driver:
+  name: docker
+
+platforms:
+  - name: ${MOLECULE_PLATFORM_NAME:-ubuntu-2204}
+    image: ${MOLECULE_PLATFORM_IMAGE:-ubuntu:26.04}
+    command: ${MOLECULE_PLATFORM_COMMAND:-sleep infinity}
+    volumes:
+      - /sys/fs/cgroup:/sys/fs/cgroup:rw
+    cgroupns_mode: host
+    privileged: true
+    pre_build_image: false
+
+provisioner:
+  name: ansible
+  playbooks:
+    converge: converge.yml
+    prepare: ../common/prepare.yml
+  env:
+    ANSIBLE_ROLES_PATH: "../../.."
+
+scenario:
+  test_sequence:
+    - dependency
+    - cleanup
+    - destroy
+    - syntax
+    - create
+    - prepare
+    - converge
+    - idempotence
+    - side_effect
+    - verify
+    - cleanup
+    - destroy
+
+verifier:
+  name: ansible

ansible/roles/gitea-runner/molecule/multi-instance/verify.yml

@@ -0,0 +1,74 @@
+---
+- name: Verify
+  hosts: all
+  become: true
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Check first runner user exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_base_home }}/grm-molecule-runner-a"
+      register: home_a_stat
+
+    - name: Assert first runner user home exists
+      ansible.builtin.assert:
+        that:
+          - home_a_stat.stat.exists
+        fail_msg: "First runner user home is missing"
+
+    - name: Check second runner user exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_base_home }}/grm-molecule-runner-b"
+      register: home_b_stat
+
+    - name: Assert second runner user home exists
+      ansible.builtin.assert:
+        that:
+          - home_b_stat.stat.exists
+        fail_msg: "Second runner user home is missing"
+
+    - name: Check first instance data directory exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_base_data_dir }}/molecule-runner-a"
+      register: data_a_stat
+
+    - name: Assert first instance data directory exists
+      ansible.builtin.assert:
+        that:
+          - data_a_stat.stat.exists
+        fail_msg: "First instance data directory is missing"
+
+    - name: Check second instance data directory exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_base_data_dir }}/molecule-runner-b"
+      register: data_b_stat
+
+    - name: Assert second instance data directory exists
+      ansible.builtin.assert:
+        that:
+          - data_b_stat.stat.exists
+        fail_msg: "Second instance data directory is missing"
+
+    - name: Check first instance config exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_base_config_dir }}/molecule-runner-a/config.yaml"
+      register: config_a_stat
+
+    - name: Assert first instance config exists
+      ansible.builtin.assert:
+        that:
+          - config_a_stat.stat.exists
+        fail_msg: "First instance config file is missing"
+
+    - name: Check second instance config exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_base_config_dir }}/molecule-runner-b/config.yaml"
+      register: config_b_stat
+
+    - name: Assert second instance config exists
+      ansible.builtin.assert:
+        that:
+          - config_b_stat.stat.exists
+        fail_msg: "Second instance config file is missing"

ansible/roles/gitea-runner/molecule/remove/converge.yml

@@ -0,0 +1,12 @@
+---
+- name: Converge
+  hosts: all
+  become: true
+  vars:
+    gitea_url: "http://localhost:3000"
+    registration_token: "fake-token-for-testing"
+    runner_name: "remove-test-runner"
+    skip_runner_registration: true
+    docker_rootless_setup: false
+  roles:
+    - role: gitea-runner

ansible/roles/gitea-runner/molecule/remove/molecule.yml

@@ -0,0 +1,39 @@
+---
+driver:
+  name: docker
+
+platforms:
+  - name: ${MOLECULE_PLATFORM_NAME:-ubuntu-2204}
+    image: ${MOLECULE_PLATFORM_IMAGE:-ubuntu:26.04}
+    command: ${MOLECULE_PLATFORM_COMMAND:-sleep infinity}
+    volumes:
+      - /sys/fs/cgroup:/sys/fs/cgroup:rw
+    cgroupns_mode: host
+    privileged: true
+    pre_build_image: false
+
+provisioner:
+  name: ansible
+  playbooks:
+    converge: converge.yml
+    prepare: ../common/prepare.yml
+    side_effect: side_effect.yml
+  env:
+    ANSIBLE_ROLES_PATH: "../../.."
+
+scenario:
+  test_sequence:
+    - dependency
+    - cleanup
+    - destroy
+    - syntax
+    - create
+    - prepare
+    - converge
+    - side_effect
+    - verify
+    - cleanup
+    - destroy
+
+verifier:
+  name: ansible

ansible/roles/gitea-runner/molecule/remove/side_effect.yml

@@ -0,0 +1,8 @@
+---
+- name: Remove runner via remove-runner playbook
+  ansible.builtin.import_playbook: "../../../../remove-runner.yml"
+  vars:
+    runner_name: "remove-test-runner"
+    registration_token: "fake-token-for-testing"
+    gitea_url: "http://localhost:3000"
+    skip_runner_registration: true

ansible/roles/gitea-runner/molecule/remove/verify.yml

@@ -0,0 +1,147 @@
+---
+- name: Verify runner was fully removed
+  hosts: all
+  become: true
+  vars:
+    runner_name: "remove-test-runner"
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Check runner user is absent
+      ansible.builtin.getent:
+        database: passwd
+        key: "{{ gitea_runner_service_user }}"
+      register: user_check
+      failed_when: false
+
+    - name: Assert runner user is absent
+      ansible.builtin.assert:
+        that:
+          - user_check is failed or
+            gitea_runner_service_user not in (user_check.ansible_facts.getent_passwd | default({}))
+        fail_msg: "Runner user still exists after removal"
+
+    - name: Check runner home directory is absent
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}"
+      register: home_stat
+
+    - name: Assert runner home directory is absent
+      ansible.builtin.assert:
+        that:
+          - not home_stat.stat.exists
+        fail_msg: "Runner home directory still exists after removal"
+
+    - name: Check runner data directory is absent
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_data_dir }}"
+      register: data_stat
+
+    - name: Assert runner data directory is absent
+      ansible.builtin.assert:
+        that:
+          - not data_stat.stat.exists
+        fail_msg: "Runner data directory still exists after removal"
+
+    - name: Check runner config directory is absent
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_config_dir }}"
+      register: config_stat
+
+    - name: Assert runner config directory is absent
+      ansible.builtin.assert:
+        that:
+          - not config_stat.stat.exists
+        fail_msg: "Runner config directory still exists after removal"
+
+    - name: Check gitea-runner service unit is absent
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/gitea-runner.service"
+      register: service_stat
+
+    - name: Assert gitea-runner service unit is absent
+      ansible.builtin.assert:
+        that:
+          - not service_stat.stat.exists
+        fail_msg: "gitea-runner service unit still exists after removal"
+
+    - name: Check docker-prune service unit is absent
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/docker-prune.service"
+      register: prune_service_stat
+
+    - name: Assert docker-prune service unit is absent
+      ansible.builtin.assert:
+        that:
+          - not prune_service_stat.stat.exists
+        fail_msg: "docker-prune service unit still exists after removal"
+
+    - name: Check docker-prune timer unit is absent
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/docker-prune.timer"
+      register: prune_timer_stat
+
+    - name: Assert docker-prune timer unit is absent
+      ansible.builtin.assert:
+        that:
+          - not prune_timer_stat.stat.exists
+        fail_msg: "docker-prune timer unit still exists after removal"
+
+    - name: Check healthcheck service unit is absent
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/runner-healthcheck.service"
+      register: healthcheck_service_stat
+
+    - name: Assert healthcheck service unit is absent
+      ansible.builtin.assert:
+        that:
+          - not healthcheck_service_stat.stat.exists
+        fail_msg: "runner-healthcheck service unit still exists after removal"
+
+    - name: Check healthcheck timer unit is absent
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/runner-healthcheck.timer"
+      register: healthcheck_timer_stat
+
+    - name: Assert healthcheck timer unit is absent
+      ansible.builtin.assert:
+        that:
+          - not healthcheck_timer_stat.stat.exists
+        fail_msg: "runner-healthcheck timer unit still exists after removal"
+
+    - name: Check healthcheck script is absent
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_config_dir }}/healthcheck.sh"
+      register: healthcheck_script_stat
+
+    - name: Assert healthcheck script is absent
+      ansible.builtin.assert:
+        that:
+          - not healthcheck_script_stat.stat.exists
+        fail_msg: "healthcheck script still exists after removal"
+
+    - name: Check subuid entry is absent
+      ansible.builtin.command: "grep -c '^{{ gitea_runner_service_user }}:' /etc/subuid"
+      register: subuid_check
+      changed_when: false
+      failed_when: false
+
+    - name: Assert subuid entry is absent
+      ansible.builtin.assert:
+        that:
+          - subuid_check.rc != 0
+        fail_msg: "subuid entry still exists after removal"
+
+    - name: Check subgid entry is absent
+      ansible.builtin.command: "grep -c '^{{ gitea_runner_service_user }}:' /etc/subgid"
+      register: subgid_check
+      changed_when: false
+      failed_when: false
+
+    - name: Assert subgid entry is absent
+      ansible.builtin.assert:
+        that:
+          - subgid_check.rc != 0
+        fail_msg: "subgid entry still exists after removal"

ansible/roles/gitea-runner/molecule/template-content/converge.yml

@@ -0,0 +1,12 @@
+---
+- name: Converge
+  hosts: all
+  become: true
+  vars:
+    gitea_url: "http://localhost:3000"
+    registration_token: "fake-token-for-testing"
+    runner_name: "template-test-runner"
+    skip_runner_registration: true
+    docker_rootless_setup: false
+  roles:
+    - role: gitea-runner

ansible/roles/gitea-runner/molecule/template-content/molecule.yml

@@ -0,0 +1,39 @@
+---
+driver:
+  name: docker
+
+platforms:
+  - name: ${MOLECULE_PLATFORM_NAME:-ubuntu-2204}
+    image: ${MOLECULE_PLATFORM_IMAGE:-ubuntu:26.04}
+    command: ${MOLECULE_PLATFORM_COMMAND:-sleep infinity}
+    volumes:
+      - /sys/fs/cgroup:/sys/fs/cgroup:rw
+    cgroupns_mode: host
+    privileged: true
+    pre_build_image: false
+
+provisioner:
+  name: ansible
+  playbooks:
+    converge: converge.yml
+    prepare: ../common/prepare.yml
+  env:
+    ANSIBLE_ROLES_PATH: "../../.."
+
+scenario:
+  test_sequence:
+    - dependency
+    - cleanup
+    - destroy
+    - syntax
+    - create
+    - prepare
+    - converge
+    - idempotence
+    - side_effect
+    - verify
+    - cleanup
+    - destroy
+
+verifier:
+  name: ansible

ansible/roles/gitea-runner/molecule/template-content/verify.yml

@@ -0,0 +1,106 @@
+---
+- name: Verify
+  hosts: all
+  become: true
+  vars:
+    runner_name: "template-test-runner"
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Check systemd user service exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/gitea-runner.service"
+      register: service_stat
+
+    - name: Assert user service exists
+      ansible.builtin.assert:
+        that:
+          - service_stat.stat.exists
+        fail_msg: "Systemd user service is missing"
+
+    - name: Read rendered user service template
+      ansible.builtin.slurp:
+        src: "{{ gitea_runner_home }}/.config/systemd/user/gitea-runner.service"
+      register: service_template
+
+    - name: Assert user service template contains expected directives
+      ansible.builtin.assert:
+        that:
+          - "'Type=simple' in service_template.content | b64decode"
+          - "'ExecStart={{ gitea_runner_binary_path }}' in service_template.content | b64decode"
+          - "'Restart=always' in service_template.content | b64decode"
+          - "'Requires=docker.service' in service_template.content | b64decode"
+          - "'PartOf=docker.service' in service_template.content | b64decode"
+          - "'StartLimitBurst=10' in service_template.content | b64decode"
+          - "'DOCKER_HOST=unix:///run/user' in service_template.content | b64decode"
+          - "'XDG_RUNTIME_DIR=/run/user' in service_template.content | b64decode"
+        fail_msg: "User service template is missing expected directives"
+
+    - name: Read rendered prune service template
+      ansible.builtin.slurp:
+        src: "{{ gitea_runner_home }}/.config/systemd/user/docker-prune.service"
+      register: prune_service
+
+    - name: Assert prune service contains expected directives
+      ansible.builtin.assert:
+        that:
+          - "'Type=oneshot' in prune_service.content | b64decode"
+          - "'docker system prune' in prune_service.content | b64decode"
+          - "'docker volume prune' in prune_service.content | b64decode"
+        fail_msg: "Prune service template is missing expected directives"
+
+    - name: Read rendered prune timer template
+      ansible.builtin.slurp:
+        src: "{{ gitea_runner_home }}/.config/systemd/user/docker-prune.timer"
+      register: prune_timer
+
+    - name: Assert prune timer contains expected directives
+      ansible.builtin.assert:
+        that:
+          - "'OnCalendar={{ gitea_runner_prune_schedule }}' in prune_timer.content | b64decode"
+          - "'Persistent=true' in prune_timer.content | b64decode"
+        fail_msg: "Prune timer template is missing expected directives"
+
+    - name: Read rendered healthcheck service template
+      ansible.builtin.slurp:
+        src: "{{ gitea_runner_home }}/.config/systemd/user/runner-healthcheck.service"
+      register: healthcheck_service
+
+    - name: Assert healthcheck service contains expected directives
+      ansible.builtin.assert:
+        that:
+          - "'Type=oneshot' in healthcheck_service.content | b64decode"
+          - "'ExecStart={{ gitea_runner_healthcheck_script_path }}' in healthcheck_service.content | b64decode"
+          - "'DOCKER_HOST=unix:///run/user/' in healthcheck_service.content | b64decode"
+          - "'XDG_RUNTIME_DIR=/run/user/' in healthcheck_service.content | b64decode"
+        fail_msg: "Healthcheck service template is missing expected directives"
+
+    - name: Read rendered healthcheck timer template
+      ansible.builtin.slurp:
+        src: "{{ gitea_runner_home }}/.config/systemd/user/runner-healthcheck.timer"
+      register: healthcheck_timer
+
+    - name: Assert healthcheck timer contains expected directives
+      ansible.builtin.assert:
+        that:
+          - "'OnBootSec={{ gitea_runner_healthcheck_boot_delay }}' in healthcheck_timer.content | b64decode"
+          - "'OnUnitActiveSec={{ gitea_runner_healthcheck_interval }}' in healthcheck_timer.content | b64decode"
+          - "'Persistent=true' in healthcheck_timer.content | b64decode"
+        fail_msg: "Healthcheck timer template is missing expected directives"
+
+    - name: Read rendered healthcheck script
+      ansible.builtin.slurp:
+        src: "{{ gitea_runner_healthcheck_script_path }}"
+      register: healthcheck_script
+
+    - name: Assert healthcheck script contains expected content
+      ansible.builtin.assert:
+        that:
+          - "'docker info' in healthcheck_script.content | b64decode"
+          - "'systemctl --user restart docker.service' in healthcheck_script.content | b64decode"
+          - "'systemctl --user restart gitea-runner.service' in healthcheck_script.content | b64decode"
+          - "'docker system prune' in healthcheck_script.content | b64decode"
+          - "gitea_runner_healthcheck_disk_threshold | string in healthcheck_script.content | b64decode"
+        fail_msg: "Healthcheck script template is missing expected content"

ansible/roles/gitea-runner/molecule/update/converge.yml

@@ -0,0 +1,12 @@
+---
+- name: Converge
+  hosts: all
+  become: true
+  vars:
+    gitea_url: "http://localhost:3000"
+    registration_token: "fake-token-for-testing"
+    runner_name: "update-test-runner"
+    skip_runner_registration: true
+    docker_rootless_setup: false
+  roles:
+    - role: gitea-runner

ansible/roles/gitea-runner/molecule/update/molecule.yml

@@ -0,0 +1,40 @@
+---
+driver:
+  name: docker
+
+platforms:
+  - name: ${MOLECULE_PLATFORM_NAME:-ubuntu-2204}
+    image: ${MOLECULE_PLATFORM_IMAGE:-ubuntu:26.04}
+    command: ${MOLECULE_PLATFORM_COMMAND:-sleep infinity}
+    volumes:
+      - /sys/fs/cgroup:/sys/fs/cgroup:rw
+    cgroupns_mode: host
+    privileged: true
+    pre_build_image: false
+
+provisioner:
+  name: ansible
+  playbooks:
+    converge: converge.yml
+    prepare: ../common/prepare.yml
+    side_effect: side_effect.yml
+  env:
+    ANSIBLE_ROLES_PATH: "../../.."
+
+scenario:
+  test_sequence:
+    - dependency
+    - cleanup
+    - destroy
+    - syntax
+    - create
+    - prepare
+    - converge
+    - idempotence
+    - side_effect
+    - verify
+    - cleanup
+    - destroy
+
+verifier:
+  name: ansible

ansible/roles/gitea-runner/molecule/update/side_effect.yml

@@ -0,0 +1,11 @@
+---
+- name: Update runner
+  hosts: all
+  become: true
+  vars:
+    runner_name: "update-test-runner"
+  tasks:
+    - name: Include update tasks
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: update_runner.yml

ansible/roles/gitea-runner/molecule/update/verify.yml

@@ -0,0 +1,43 @@
+---
+- name: Verify
+  hosts: all
+  become: true
+  vars:
+    runner_name: "update-test-runner"
+  pre_tasks:
+    - name: Load role defaults
+      ansible.builtin.include_vars:
+        dir: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/defaults"
+  tasks:
+    - name: Check runner binary still exists after update
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_binary_path }}"
+      register: binary_stat
+
+    - name: Assert binary executable exists after update
+      ansible.builtin.assert:
+        that:
+          - binary_stat.stat.exists
+        fail_msg: "Runner binary missing after update"
+
+    - name: Check systemd user service still exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_home }}/.config/systemd/user/gitea-runner.service"
+      register: service_stat
+
+    - name: Assert user service exists after update
+      ansible.builtin.assert:
+        that:
+          - service_stat.stat.exists
+        fail_msg: "Systemd user service missing after update"
+
+    - name: Check instance data directory still exists
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_data_dir }}"
+      register: data_stat
+
+    - name: Assert data directory exists after update
+      ansible.builtin.assert:
+        that:
+          - data_stat.stat.exists
+        fail_msg: "Runner data directory missing after update"

ansible/roles/gitea-runner/tasks/deregister.yml

@@ -0,0 +1,58 @@
+---
+- name: Check if runner registration file exists
+  ansible.builtin.stat:
+    path: "{{ gitea_runner_data_dir }}/.runner"
+  register: runner_file_stat
+
+- name: Read runner registration file
+  ansible.builtin.slurp:
+    src: "{{ gitea_runner_data_dir }}/.runner"
+  register: runner_file_content
+  when: runner_file_stat.stat.exists | default(false) | bool
+
+- name: Parse runner registration data
+  ansible.builtin.set_fact:
+    runner_reg: >
+      {{ (runner_file_content.content | b64decode | from_json)
+      if (runner_file_content is defined and runner_file_content.content is defined)
+      else {} }}
+  when: runner_file_stat.stat.exists | default(false) | bool
+
+- name: Deregister runner from Gitea via API
+  ansible.builtin.command: >
+    curl -sf --connect-timeout 5 --max-time 10 -X DELETE
+    -H "Authorization: token {{ gitea_admin_token | default(registration_token) }}"
+    "{{ gitea_url }}/api/v1/admin/actions/runners/{{ runner_reg.id }}"
+  args:
+    chdir: "{{ gitea_runner_data_dir }}"
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default(0) }}"
+    DOCKER_HOST: "unix:///run/user/{{ gitea_runner_uid | default(0) }}/docker.sock"
+  when:
+    - runner_file_stat.stat.exists | default(false) | bool
+    - not skip_runner_registration
+    - runner_reg.id is defined
+  register: deregister_output
+  changed_when: deregister_output.rc == 0
+  failed_when: false
+
+- name: Warn if deregistration failed
+  ansible.builtin.debug:
+    msg: >-
+      WARNING: Runner deregistration from Gitea failed (rc={{ deregister_output.rc | default('N/A') }}).
+      The runner entry may remain in Gitea's admin UI as offline.
+      Use an admin token (gitea_admin_token var) to enable automatic cleanup,
+      or remove it manually from {{ gitea_url }}/-/admin/actions/runners
+  when:
+    - runner_file_stat.stat.exists | default(false) | bool
+    - not skip_runner_registration
+    - deregister_output is defined
+    - deregister_output.rc | default(1) != 0
+
+- name: Remove runner registration file
+  ansible.builtin.file:
+    path: "{{ gitea_runner_data_dir }}/.runner"
+    state: absent
+  when: runner_file_stat.stat.exists | default(false) | bool

ansible/roles/gitea-runner/tasks/download_gitea_runner.yml

@@ -0,0 +1,48 @@
+---
+- name: Get latest gitea_runner release info
+  ansible.builtin.uri:
+    url: https://gitea.com/api/v1/repos/gitea/runner/releases/latest
+    return_content: true
+    body_format: json
+    headers:
+      Accept: application/json
+  register: gitea_runner_release
+  when: gitea_runner_version | default('latest') == 'latest'
+  changed_when: false
+  retries: 3
+  delay: 5
+  until: gitea_runner_release is not failed
+
+- name: Set gitea_runner version from latest release
+  ansible.builtin.set_fact:
+    gitea_runner_version: "{{ gitea_runner_release.json.tag_name }}"
+  when: gitea_runner_version | default('latest') == 'latest'
+
+- name: Set gitea_runner download version (strip v prefix)
+  ansible.builtin.set_fact:
+    gitea_runner_download_version: "{{ gitea_runner_version | regex_replace('^v', '') }}"
+
+- name: Set gitea_runner download URL
+  ansible.builtin.set_fact:
+    gitea_runner_url: >-
+      {{ 'https://gitea.com/gitea/runner/releases/download/v' ~ gitea_runner_download_version
+      ~ '/gitea-runner-' ~ gitea_runner_download_version ~ '-linux-'
+      ~ (ansible_facts['architecture'] | regex_replace('x86_64', 'amd64')) }}
+
+- name: Ensure /usr/local/bin directory exists
+  ansible.builtin.file:
+    path: /usr/local/bin
+    state: directory
+    mode: "0755"
+
+- name: Download gitea_runner binary
+  ansible.builtin.get_url:
+    url: "{{ gitea_runner_url }}"
+    dest: "{{ gitea_runner_binary_path }}"
+    mode: "0755"
+    force: false
+  register: gitea_runner_download
+  notify: Restart gitea-runner
+  retries: 3
+  delay: 5
+  until: gitea_runner_download is not failed

ansible/roles/gitea-runner/tasks/healthcheck.yml

@@ -0,0 +1,46 @@
+---
+- name: Create healthcheck script
+  ansible.builtin.template:
+    src: runner-healthcheck.sh.j2
+    dest: "{{ gitea_runner_healthcheck_script_path }}"
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0755"
+
+- name: Create healthcheck user service file
+  ansible.builtin.template:
+    src: runner-healthcheck.service.j2
+    dest: "{{ gitea_runner_home }}/.config/systemd/user/runner-healthcheck.service"
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0644"
+
+- name: Create healthcheck user timer file
+  ansible.builtin.template:
+    src: runner-healthcheck.timer.j2
+    dest: "{{ gitea_runner_home }}/.config/systemd/user/runner-healthcheck.timer"
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0644"
+
+- name: Reload systemd user daemon for healthcheck timer
+  ansible.builtin.command: systemctl --user daemon-reload
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  changed_when: true
+  when:
+    - systemd_available.stat.exists
+    - docker_rootless_setup
+
+- name: Enable and start healthcheck user timer
+  ansible.builtin.command: systemctl --user enable --now runner-healthcheck.timer
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  changed_when: true
+  when:
+    - systemd_available.stat.exists
+    - docker_rootless_setup

ansible/roles/gitea-runner/tasks/install_runner.yml

@@ -0,0 +1,21 @@
+---
+- name: Include gitea_runner download
+  ansible.builtin.include_tasks: download_gitea_runner.yml
+
+- name: Create gitea_runner config file
+  ansible.builtin.template:
+    src: gitea-runner-config.yaml.j2
+    dest: "{{ gitea_runner_config_dir }}/config.yaml"
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0644"
+
+- name: Include validation
+  ansible.builtin.include_tasks: validate.yml
+
+- name: Include registration
+  ansible.builtin.include_tasks: register.yml
+  when: not skip_runner_registration
+
+- name: Include service setup
+  ansible.builtin.include_tasks: service.yml

ansible/roles/gitea-runner/tasks/integration_test.yml

@@ -0,0 +1,102 @@
+---
+- name: Check runner registration file exists
+  ansible.builtin.stat:
+    path: "{{ gitea_runner_data_dir }}/.runner"
+  register: runner_file_stat
+
+- name: Read runner registration file
+  ansible.builtin.slurp:
+    src: "{{ gitea_runner_data_dir }}/.runner"
+  register: runner_file_content
+  when: runner_file_stat.stat.exists | default(false) | bool
+
+- name: Parse runner registration data
+  ansible.builtin.set_fact:
+    runner_reg: >
+      {{ (runner_file_content.content | b64decode | from_json)
+      if (runner_file_content is defined and runner_file_content.content is defined)
+      else {} }}
+  when: runner_file_stat.stat.exists | default(false) | bool
+
+- name: Verify runner user service active
+  ansible.builtin.command: systemctl --user is-active gitea-runner
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  register: service_check
+  changed_when: false
+  when:
+    - systemd_available.stat.exists
+    - docker_rootless_setup
+
+- name: Validate runner installation
+  ansible.builtin.fail:
+    msg: >
+      Runner '{{ runner_name }}' is not properly installed:
+      {% if not (runner_file_stat.stat.exists | default(false)) %}
+      - Registration file (.runner) is missing. Registration may have failed.
+      {% endif %}
+      {% if docker_rootless_setup and not (service_check.stdout | default('') | trim) == 'active' %}
+      - Systemd user service is not active.
+      {% endif %}
+  when: >
+    not (runner_file_stat.stat.exists | default(false))
+    or (docker_rootless_setup and not (service_check.stdout | default('') | trim) == 'active')
+
+- name: Report runner status
+  ansible.builtin.debug:
+    msg: >
+      Runner '{{ runner_name }}' is installed and running.
+      Registered: {{ runner_file_stat.stat.exists | default(false) }}
+      {% if runner_reg.id is defined %}Runner ID: {{ runner_reg.id }}{% endif %}
+      {% if runner_reg.uuid is defined %}UUID: {{ runner_reg.uuid }}{% endif %}
+      {% if runner_reg.address is defined %}Gitea: {{ runner_reg.address }}{% endif %}
+      Service: {{ service_check.stdout | default('unknown') | trim }}
+
+- name: Optional Gitea API verification
+  when:
+    - gitea_url is defined
+    - gitea_admin_token is defined
+    - gitea_admin_token | length > 0
+  block:
+    - name: Check admin runners API
+      ansible.builtin.uri:
+        url: "{{ gitea_url }}/api/v1/admin/runners"
+        headers:
+          Authorization: "token {{ gitea_admin_token }}"
+        method: GET
+        status_code: [200, 401, 403, 404]
+        return_content: true
+        body_format: json
+      register: admin_api_response
+      ignore_errors: true
+
+    - name: Check repo runners API
+      ansible.builtin.uri:
+        url: "{{ gitea_url }}/api/v1/repos/{{ gitea_runner_test_repo | default('oblachno-oss/grm') }}/actions/runners"
+        headers:
+          Authorization: "token {{ gitea_admin_token }}"
+        method: GET
+        status_code: [200, 401, 403, 404]
+        return_content: true
+        body_format: json
+      register: repo_api_response
+      ignore_errors: true
+
+    - name: Report API status (informational only)
+      ansible.builtin.debug:
+        msg: >
+          API checks (informational only — not used for pass/fail):
+          Admin API: {{ admin_api_response.status | default('no response') }}.
+          Repo API: {{ repo_api_response.status | default('no response') }}.
+          {% if admin_api_response.json.runners | default([]) | selectattr('name', 'equalto', runner_name) | list | length > 0 %}
+          Runner found in admin API.
+          {% endif %}
+          {% if repo_api_response.json.runners | default([]) | selectattr('name', 'equalto', runner_name) | list | length > 0 %}
+          Runner found in repo API.
+          {% endif %}
+  rescue:
+    - name: API check failed
+      ansible.builtin.debug:
+        msg: "API verification skipped due to connection or permission error."

ansible/roles/gitea-runner/tasks/main.yml

@@ -0,0 +1,22 @@
+---
+- name: Include systemd availability check
+  ansible.builtin.include_tasks: systemd_check.yml
+
+- name: Include user setup
+  ansible.builtin.include_tasks: user_setup.yml
+
+- name: Include rootless Docker setup
+  ansible.builtin.include_tasks: rootless_docker.yml
+
+- name: Include runner install
+  ansible.builtin.include_tasks: install_runner.yml
+
+- name: Include prune setup
+  ansible.builtin.include_tasks: prune.yml
+
+- name: Include healthcheck setup
+  ansible.builtin.include_tasks: healthcheck.yml
+
+- name: Include integration test
+  ansible.builtin.include_tasks: integration_test.yml
+  when: not skip_runner_registration

ansible/roles/gitea-runner/tasks/prune.yml

@@ -0,0 +1,38 @@
+---
+- name: Create docker-prune user service file
+  ansible.builtin.template:
+    src: docker-prune.service.j2
+    dest: "{{ gitea_runner_home }}/.config/systemd/user/docker-prune.service"
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0644"
+
+- name: Create docker-prune user timer file
+  ansible.builtin.template:
+    src: docker-prune.timer.j2
+    dest: "{{ gitea_runner_home }}/.config/systemd/user/docker-prune.timer"
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0644"
+
+- name: Reload systemd user daemon for prune timer
+  ansible.builtin.command: systemctl --user daemon-reload
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  changed_when: true
+  when:
+    - systemd_available.stat.exists
+    - docker_rootless_setup
+
+- name: Enable and start docker-prune user timer
+  ansible.builtin.command: systemctl --user enable --now docker-prune.timer
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  changed_when: true
+  when:
+    - systemd_available.stat.exists
+    - docker_rootless_setup

ansible/roles/gitea-runner/tasks/register.yml

@@ -0,0 +1,33 @@
+---
+- name: Ensure work directory exists
+  ansible.builtin.file:
+    path: "{{ gitea_runner_data_dir }}"
+    state: directory
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0755"
+
+- name: Check if runner is already registered
+  ansible.builtin.stat:
+    path: "{{ gitea_runner_data_dir }}/.runner"
+  register: runner_registered
+
+- name: Register runner with Gitea
+  ansible.builtin.command: >
+    {{ gitea_runner_binary_path }} register
+    --token {{ registration_token }}
+    --name {{ runner_name }}
+    --instance {{ gitea_url }}
+    --labels {{ runner_labels }}
+    --no-interactive
+  args:
+    chdir: "{{ gitea_runner_data_dir }}"
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default(0) }}"
+    DOCKER_HOST: "unix:///run/user/{{ gitea_runner_uid | default(0) }}/docker.sock"
+  when: not runner_registered.stat.exists
+  register: register_output
+  changed_when: "'already exists' not in register_output.stdout | default('')"
+  timeout: 60

ansible/roles/gitea-runner/tasks/resolve_uid.yml

@@ -0,0 +1,25 @@
+---
+# Resolve runner identity facts for stop/start/status/restart playbooks.
+# These playbooks use include_role with tasks_from, which does NOT expose
+# role defaults to the playbook's task-level keywords (become_user, etc).
+# We set the facts explicitly here so they're available everywhere.
+
+- name: Resolve runner service user
+  ansible.builtin.set_fact:
+    gitea_runner_service_user: "{{ gitea_runner_user_prefix | default('grm-') }}{{ runner_name }}"
+    gitea_runner_base_data_dir: "/var/lib/gitea-runner"
+    gitea_runner_base_config_dir: "/etc/gitea-runner"
+
+- name: Resolve runner data and config dirs
+  ansible.builtin.set_fact:
+    gitea_runner_data_dir: "{{ gitea_runner_base_data_dir }}/{{ runner_name }}"
+    gitea_runner_config_dir: "{{ gitea_runner_base_config_dir }}/{{ runner_name }}"
+
+- name: Resolve runner service user UID
+  ansible.builtin.getent:
+    database: passwd
+    key: "{{ gitea_runner_service_user }}"
+
+- name: Set runner UID fact
+  ansible.builtin.set_fact:
+    gitea_runner_uid: "{{ getent_passwd[gitea_runner_service_user][1] }}"

ansible/roles/gitea-runner/tasks/rootless_docker.yml

@@ -0,0 +1,112 @@
+---
+- name: Ensure keyrings directory exists (Debian/Ubuntu)
+  ansible.builtin.file:
+    path: "/etc/apt/keyrings"
+    state: directory
+    mode: "0755"
+  when: ansible_facts['os_family'] == 'Debian'
+
+- name: Download and dearmor Docker GPG key (Debian/Ubuntu)
+  ansible.builtin.shell: |
+    set -o pipefail
+    curl -fsSL "https://download.docker.com/linux/{{ ansible_facts['distribution'] | lower }}/gpg" | gpg --dearmor --yes -o {{ docker_gpg_key_path }}
+  args:
+    creates: "{{ docker_gpg_key_path }}"
+    executable: /bin/bash
+  when: ansible_facts['os_family'] == 'Debian'
+
+- name: Add Docker APT repository (Debian/Ubuntu)
+  ansible.builtin.copy:
+    dest: /etc/apt/sources.list.d/docker.list
+    content: "{{ docker_apt_source_line }}\n"
+    mode: "0644"
+  register: docker_apt_repo
+  when: ansible_facts['os_family'] == 'Debian'
+
+- name: Update apt cache after adding Docker repo (Debian/Ubuntu)
+  ansible.builtin.apt:
+    update_cache: true
+  when:
+    - ansible_facts['os_family'] == 'Debian'
+    - docker_apt_repo is changed
+
+- name: Install rootless Docker dependencies (Debian/Ubuntu)
+  ansible.builtin.apt:
+    name:
+      - uidmap
+      - slirp4netns
+      - fuse-overlayfs
+      - docker-ce
+      - docker-ce-cli
+      - docker-ce-rootless-extras
+      - containerd.io
+      - docker-compose-plugin
+      - rsync
+    state: present
+  when: ansible_facts['os_family'] == 'Debian'
+
+- name: Update pacman cache (Arch Linux)
+  community.general.pacman:
+    update_cache: true
+  when: ansible_facts['os_family'] == 'Archlinux'
+  changed_when: false
+
+- name: Install rootless Docker dependencies (Arch Linux)
+  community.general.pacman:
+    name:
+      - docker
+      - docker-compose
+      - slirp4netns
+      - fuse-overlayfs
+      - rsync
+    state: present
+  when: ansible_facts['os_family'] == 'Archlinux'
+
+- name: Check if rootless Docker is already set up
+  ansible.builtin.stat:
+    path: "{{ gitea_runner_home }}/.config/systemd/user/docker.service"
+  register: rootless_docker_check
+
+- name: Set up rootless Docker for runner user
+  ansible.builtin.command: dockerd-rootless-setuptool.sh install
+  args:
+    creates: "{{ gitea_runner_home }}/.config/systemd/user/docker.service"
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  when:
+    - docker_rootless_setup
+    - not rootless_docker_check.stat.exists
+
+- name: Start rootless Docker daemon (systemd user service)
+  ansible.builtin.command: systemctl --user start docker
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  changed_when: true
+  when: docker_rootless_setup
+
+- name: Enable rootless Docker daemon (systemd user service)
+  ansible.builtin.command: systemctl --user enable docker
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  changed_when: true
+  when: docker_rootless_setup
+
+- name: Wait for rootless Docker daemon to be ready
+  ansible.builtin.command: docker version
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    DOCKER_HOST: "unix:///run/user/{{ gitea_runner_uid }}/docker.sock"
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  register: docker_ready
+  until: docker_ready.rc == 0
+  retries: 10
+  delay: 2
+  changed_when: false
+  when: docker_rootless_setup

ansible/roles/gitea-runner/tasks/service.yml

@@ -0,0 +1,30 @@
+---
+- name: Create systemd user service file
+  ansible.builtin.template:
+    src: gitea-runner-user.service.j2
+    dest: "{{ gitea_runner_home }}/.config/systemd/user/gitea-runner.service"
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0644"
+
+- name: Reload systemd user daemon
+  ansible.builtin.command: systemctl --user daemon-reload
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  changed_when: true
+  when:
+    - systemd_available.stat.exists
+    - docker_rootless_setup
+
+- name: Enable and start gitea-runner user service
+  ansible.builtin.command: systemctl --user enable --now gitea-runner
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  changed_when: true
+  when:
+    - systemd_available.stat.exists
+    - docker_rootless_setup

ansible/roles/gitea-runner/tasks/systemd_check.yml

@@ -0,0 +1,5 @@
+---
+- name: Check if systemd is available
+  ansible.builtin.stat:
+    path: /run/systemd/system
+  register: systemd_available

ansible/roles/gitea-runner/tasks/update_runner.yml

@@ -0,0 +1,14 @@
+---
+- name: Include gitea_runner download
+  ansible.builtin.include_tasks: download_gitea_runner.yml
+
+- name: Restart gitea-runner user service
+  ansible.builtin.command: systemctl --user restart gitea-runner
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  when:
+    - systemd_available.stat.exists | default(false) | bool
+    - docker_rootless_setup
+  changed_when: true

ansible/roles/gitea-runner/tasks/user_setup.yml

@@ -0,0 +1,71 @@
+---
+- name: Create per-runner system user
+  ansible.builtin.user:
+    name: "{{ gitea_runner_service_user }}"
+    home: "{{ gitea_runner_home }}"
+    shell: /bin/bash
+    system: true
+    create_home: true
+  register: runner_user
+
+- name: Set runner UID fact
+  ansible.builtin.set_fact:
+    gitea_runner_uid: "{{ runner_user.uid }}"
+
+- name: Check if lingering is already enabled
+  ansible.builtin.stat:
+    path: "/var/lib/systemd/linger/{{ gitea_runner_service_user }}"
+  register: linger_stat
+
+- name: Enable lingering for runner user
+  ansible.builtin.command: loginctl enable-linger {{ gitea_runner_service_user }}
+  changed_when: not linger_stat.stat.exists
+  when: systemd_available.stat.exists
+
+- name: Ensure subuid entry for runner user
+  ansible.builtin.lineinfile:
+    path: /etc/subuid
+    regexp: "^{{ gitea_runner_service_user }}:"
+    line: "{{ gitea_runner_service_user }}:100000:65536"
+    create: true
+    mode: "0644"
+
+- name: Ensure subgid entry for runner user
+  ansible.builtin.lineinfile:
+    path: /etc/subgid
+    regexp: "^{{ gitea_runner_service_user }}:"
+    line: "{{ gitea_runner_service_user }}:100000:65536"
+    create: true
+    mode: "0644"
+
+- name: Ensure XDG_RUNTIME_DIR exists
+  ansible.builtin.file:
+    path: "/run/user/{{ gitea_runner_uid }}"
+    state: directory
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0700"
+
+- name: Ensure runner data directory exists
+  ansible.builtin.file:
+    path: "{{ gitea_runner_data_dir }}"
+    state: directory
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0755"
+
+- name: Ensure runner config directory exists
+  ansible.builtin.file:
+    path: "{{ gitea_runner_config_dir }}"
+    state: directory
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0755"
+
+- name: Ensure systemd user directory exists
+  ansible.builtin.file:
+    path: "{{ gitea_runner_home }}/.config/systemd/user"
+    state: directory
+    owner: "{{ gitea_runner_service_user }}"
+    group: "{{ gitea_runner_service_user }}"
+    mode: "0755"

ansible/roles/gitea-runner/tasks/validate.yml

@@ -0,0 +1,26 @@
+---
+- name: Check gitea_runner binary exists
+  ansible.builtin.stat:
+    path: "{{ gitea_runner_binary_path }}"
+  register: gitea_runner_stat
+
+- name: Fail if gitea_runner binary is missing
+  ansible.builtin.fail:
+    msg: "gitea_runner binary not found at {{ gitea_runner_binary_path }}"
+  when: not gitea_runner_stat.stat.exists
+
+- name: Verify gitea_runner is executable
+  ansible.builtin.command: "{{ gitea_runner_binary_path }} --version"
+  register: gitea_runner_version_output
+  changed_when: false
+
+- name: Verify rootless Docker connectivity
+  ansible.builtin.command: docker version
+  become: true
+  become_user: "{{ gitea_runner_service_user }}"
+  environment:
+    DOCKER_HOST: "unix:///run/user/{{ gitea_runner_uid }}/docker.sock"
+    XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+  register: docker_version_output
+  changed_when: false
+  when: docker_rootless_setup

ansible/roles/gitea-runner/templates/docker-prune.service.j2

@@ -0,0 +1,9 @@
+[Unit]
+Description=Docker prune for Gitea runner resources
+
+[Service]
+Type=oneshot
+Environment=DOCKER_HOST=unix:///run/user/{{ gitea_runner_uid }}/docker.sock
+Environment=XDG_RUNTIME_DIR=/run/user/{{ gitea_runner_uid }}
+ExecStart=/usr/bin/docker system prune -f --filter "label={{ gitea_runner_prune_label }}" --filter "until={{ gitea_runner_prune_until }}"
+ExecStart=/usr/bin/docker volume prune -f --filter "label={{ gitea_runner_prune_label }}"

ansible/roles/gitea-runner/templates/docker-prune.timer.j2

@@ -0,0 +1,9 @@
+[Unit]
+Description=Daily Docker prune for Gitea runner resources
+
+[Timer]
+OnCalendar={{ gitea_runner_prune_schedule }}
+Persistent=true
+
+[Install]
+WantedBy=timers.target

ansible/roles/gitea-runner/templates/gitea-runner-config.yaml.j2

@@ -0,0 +1,11 @@
+log:
+  level: "{{ gitea_runner_log_level }}"
+
+runner:
+  file: "{{ gitea_runner_file }}"
+  fetch_timeout: 50s
+  fetch_interval: 2s
+
+container:
+  label: "{{ gitea_runner_container_label }}"
+  docker_host: "unix:///run/user/{{ gitea_runner_uid }}/docker.sock"

ansible/roles/gitea-runner/templates/gitea-runner-user.service.j2

@@ -0,0 +1,21 @@
+[Unit]
+Description=Gitea Actions Runner (rootless)
+After=docker.service
+Requires=docker.service
+PartOf=docker.service
+
+[Service]
+Type=simple
+ExecStart={{ gitea_runner_binary_path }} daemon --config {{ gitea_runner_config_dir }}/config.yaml
+WorkingDirectory={{ gitea_runner_data_dir }}
+Environment=DOCKER_HOST=unix:///run/user/{{ gitea_runner_uid }}/docker.sock
+Environment=XDG_RUNTIME_DIR=/run/user/{{ gitea_runner_uid }}
+ExecStop=/bin/kill -TERM $MAINPID
+TimeoutStopSec=30
+Restart=always
+RestartSec={{ gitea_runner_service_restart_sec }}
+StartLimitIntervalSec=300
+StartLimitBurst=10
+
+[Install]
+WantedBy=default.target

ansible/roles/gitea-runner/templates/runner-healthcheck.service.j2

@@ -0,0 +1,9 @@
+[Unit]
+Description=Gitea Runner health check (Docker + service + disk)
+After=docker.service gitea-runner.service
+
+[Service]
+Type=oneshot
+Environment=DOCKER_HOST=unix:///run/user/{{ gitea_runner_uid }}/docker.sock
+Environment=XDG_RUNTIME_DIR=/run/user/{{ gitea_runner_uid }}
+ExecStart={{ gitea_runner_healthcheck_script_path }}

ansible/roles/gitea-runner/templates/runner-healthcheck.sh.j2

@@ -0,0 +1,49 @@
+#!/bin/bash
+# Health check for gitea-runner: verifies Docker daemon and runner service.
+# Exits 0 if healthy, 1 if Docker is down (triggers restart), 2 if runner is down.
+set -euo pipefail
+
+DOCKER_HOST="unix:///run/user/{{ gitea_runner_uid }}/docker.sock"
+XDG_RUNTIME_DIR="/run/user/{{ gitea_runner_uid }}"
+export DOCKER_HOST XDG_RUNTIME_DIR
+
+# 1. Check Docker daemon responsiveness
+if ! docker info >/dev/null 2>&1; then
+    echo "ERROR: Docker daemon not responding at ${DOCKER_HOST}"
+    systemctl --user restart docker.service
+    sleep 3
+    if ! docker info >/dev/null 2>&1; then
+        echo "CRITICAL: Docker daemon still down after restart"
+        exit 1
+    fi
+    echo "RECOVERED: Docker daemon restarted successfully"
+fi
+
+# 2. Check gitea-runner service is active
+runner_state=$(systemctl --user is-active gitea-runner.service 2>/dev/null || true)
+if [[ "$runner_state" != "active" ]]; then
+    echo "ERROR: gitea-runner service is ${runner_state}, restarting"
+    systemctl --user restart gitea-runner.service
+    sleep 2
+    runner_state=$(systemctl --user is-active gitea-runner.service 2>/dev/null || true)
+    if [[ "$runner_state" != "active" ]]; then
+        echo "CRITICAL: gitea-runner service still down after restart"
+        exit 2
+    fi
+    echo "RECOVERED: gitea-runner service restarted successfully"
+fi
+
+# 3. Check disk space — prune aggressively if below threshold
+disk_pct=$(df -P / | awk 'NR==2 {gsub(/%/, "", $5); print $5}')
+if [[ "$disk_pct" -ge {{ gitea_runner_healthcheck_disk_threshold }} ]]; then
+    echo "WARN: Disk usage at ${disk_pct}%, pruning all runner resources"
+    docker system prune -af --filter "label={{ gitea_runner_prune_label }}" --filter "until=1h" || true
+    docker volume prune -af --filter "label={{ gitea_runner_prune_label }}" || true
+    # Also prune dangling images (no label)
+    docker image prune -af || true
+    disk_pct=$(df -P / | awk 'NR==2 {gsub(/%/, "", $5); print $5}')
+    echo "INFO: Disk usage after prune: ${disk_pct}%"
+fi
+
+echo "OK: runner healthy, disk at ${disk_pct}%"
+exit 0

ansible/roles/gitea-runner/templates/runner-healthcheck.timer.j2

@@ -0,0 +1,10 @@
+[Unit]
+Description=Periodic Gitea Runner health check
+
+[Timer]
+OnBootSec={{ gitea_runner_healthcheck_boot_delay }}
+OnUnitActiveSec={{ gitea_runner_healthcheck_interval }}
+Persistent=true
+
+[Install]
+WantedBy=timers.target

ansible/start-runner.yml

@@ -0,0 +1,37 @@
+---
+- name: Start Gitea Actions runner
+  hosts: all
+  become: true
+  vars: {}
+  tasks:
+    - name: Include systemd availability check
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: systemd_check.yml
+
+    - name: Resolve runner UID
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: resolve_uid.yml
+
+    - name: Check if runner is already registered
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_data_dir }}/.runner"
+      register: runner_registered
+
+    - name: Include registration if not registered
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: register.yml
+      when:
+        - not runner_registered.stat.exists
+        - not skip_runner_registration | default(false)
+
+    - name: Start gitea-runner user service
+      ansible.builtin.command: systemctl --user start gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+      when: systemd_available.stat.exists
+      changed_when: true

ansible/status-runner.yml

@@ -0,0 +1,39 @@
+---
+- name: Status of Gitea Actions runner
+  hosts: all
+  become: true
+  vars: {}
+  tasks:
+    - name: Include systemd availability check
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: systemd_check.yml
+
+    - name: Resolve runner UID
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: resolve_uid.yml
+
+    - name: Check systemd user service status
+      ansible.builtin.command: systemctl --user is-active gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+      register: service_status
+      changed_when: false
+      when: systemd_available.stat.exists
+
+    - name: Report service status
+      ansible.builtin.debug:
+        msg: "Service gitea-runner: {{ service_status.stdout | default('unknown') | trim }}"
+      when: systemd_available.stat.exists
+
+    - name: Check runner registration file
+      ansible.builtin.stat:
+        path: "{{ gitea_runner_data_dir }}/.runner"
+      register: runner_file_stat
+
+    - name: Report runner registration
+      ansible.builtin.debug:
+        msg: "Runner registration file exists: {{ runner_file_stat.stat.exists | default(false) }}"

ansible/stop-runner.yml

@@ -0,0 +1,24 @@
+---
+- name: Stop Gitea Actions runner
+  hosts: all
+  become: true
+  vars: {}
+  tasks:
+    - name: Include systemd availability check
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: systemd_check.yml
+
+    - name: Resolve runner UID
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: resolve_uid.yml
+
+    - name: Stop gitea-runner user service
+      ansible.builtin.command: systemctl --user stop gitea-runner
+      become: true
+      become_user: "{{ gitea_runner_service_user }}"
+      environment:
+        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid }}"
+      when: systemd_available.stat.exists
+      changed_when: true

ansible/update-runner.yml

@@ -0,0 +1,10 @@
+---
+- name: Update Gitea Actions runner
+  hosts: all
+  become: true
+  vars: {}
+  tasks:
+    - name: Update runner
+      ansible.builtin.include_role:
+        name: gitea-runner
+        tasks_from: update_runner.yml

cliff.toml

@@ -0,0 +1,71 @@
+# git-cliff configuration for GRM
+# https://git-cliff.org/docs/configuration
+
+[changelog]
+header = """
+# Changelog\n
+All notable changes to this project will be documented in this file.\n
+"""
+body = """
+{% if version %}\
+    ## [{{ version | trim_start_matches(pat="v") }}] - {{ timestamp | date(format="%Y-%m-%d") }}
+{% else %}\
+    ## [unreleased]
+{% endif %}\
+{% for group, commits in commits | group_by(attribute="group") %}
+    ### {{ group | striptags | trim | upper_first }}
+    {% for commit in commits %}
+        - {% if commit.scope %}*({{ commit.scope }})* {% endif %}\
+            {% if commit.breaking %}[**breaking**] {% endif %}\
+            {{ commit.message | upper_first }}\
+    {% endfor %}
+{% endfor %}
+"""
+trim = true
+render_always = true
+
+[git]
+conventional_commits = true
+filter_unconventional = true
+require_conventional = false
+split_commits = false
+protect_breaking_commits = false
+filter_commits = false
+fail_on_unmatched_commit = false
+use_branch_tags = false
+topo_order = false
+topo_order_commits = true
+sort_commits = "oldest"
+recurse_submodules = false
+
+commit_preprocessors = [
+    # Strip GRM-N: task ID prefix from squash-merge commits so git-cliff sees conventional commits
+    { pattern = "^GRM-\\d+:\\s+", replace = "" },
+]
+
+commit_parsers = [
+    { message = "^feat", group = "<!-- 0 -->Features" },
+    { message = "^fix", group = "<!-- 1 -->Bug Fixes" },
+    { message = "^perf", group = "<!-- 4 -->Performance" },
+    { message = "^refactor", group = "<!-- 2 -->Refactor" },
+    # Skip infrastructure-only commits — they don't affect users
+    { message = "^doc", skip = true },
+    { message = "^test", skip = true },
+    { message = "^style", skip = true },
+    { message = "^chore", skip = true },
+    { message = "^ci", skip = true },
+    # Skip release commits — they are release artifacts, not features
+    { message = "^release:", skip = true },
+    { body = ".*security", group = "<!-- 8 -->Security" },
+    { message = "^revert", group = "<!-- 9 -->Revert" },
+    # Skip anything that doesn't match above — safe default
+    { message = ".*", skip = true },
+]
+
+[bump]
+features_always_bump_minor = true
+breaking_always_bump_major = false
+initial_tag = "0.1.0"
+# Refactor commits bump patch — structural changes to src/ or pyproject.toml
+# affect users even though no new feature was added.
+refactor_always_bump_patch = true

coverage.svg

@@ -1,20 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="104" height="20" role="img"
-  aria-label="coverage: 100%">
-  <title>coverage: 100%</title>
-  <linearGradient id="s" x2="0" y2="100%">
-    <stop offset="0" stop-color="#fff" stop-opacity=".7"/>
-    <stop offset=".1" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset=".9" stop-color="#000" stop-opacity=".3"/>
-    <stop offset="1" stop-color="#bbb" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r"><rect width="104" height="20" rx="3" fill="#fff"/></clipPath>
-  <g clip-path="url(#r)">
-    <rect width="66" height="20" fill="#555"/>
-    <rect x="66" width="38" height="20" fill="#4c1"/>
-    <rect width="104" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,DejaVu Sans,sans-serif" font-size="11">
-    <text x="33" y="14">coverage</text>
-    <text x="85" y="14">100%</text>
-  </g>
-</svg>

docs.svg

@@ -1,20 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="76" height="20" role="img"
-  aria-label="docs: 100%">
-  <title>docs: 100%</title>
-  <linearGradient id="s" x2="0" y2="100%">
-    <stop offset="0" stop-color="#fff" stop-opacity=".7"/>
-    <stop offset=".1" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset=".9" stop-color="#000" stop-opacity=".3"/>
-    <stop offset="1" stop-color="#bbb" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r"><rect width="76" height="20" rx="3" fill="#fff"/></clipPath>
-  <g clip-path="url(#r)">
-    <rect width="38" height="20" fill="#555"/>
-    <rect x="38" width="38" height="20" fill="#4c1"/>
-    <rect width="76" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,DejaVu Sans,sans-serif" font-size="11">
-    <text x="19" y="14">docs</text>
-    <text x="57" y="14">100%</text>
-  </g>
-</svg>

docs/index.md

@@ -0,0 +1,67 @@
+# GRM — Gitea Runner Manager
+
+A lean command-line tool to automate the installation, configuration, and lifecycle management of Gitea Actions runners on Arch Linux, Ubuntu, and Debian hosts.
+
+Each runner runs in an isolated **rootless Docker** environment under a dedicated system user, enabling multiple runners to operate in parallel on the same host without conflicts. GRM handles the entire runner lifecycle — from initial installation and registration with Gitea, through start/stop/enable/disable operations, to clean removal with deregistration.
+
+> **Pronunciation:** GRM is short for *Gitea Runner Manager*, but say it like **ГРЪМ** (roughly "GRUM") — the Bulgarian word for **thunder**. An open-source project from **Oblachno** (облачно means *cloudy* in Bulgarian).
+
+[![CI](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions/workflows/ci.yml/badge.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+[![License: GPL-3.0](https://img.shields.io/badge/license-GPL--3.0-blue)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/src/branch/master/LICENSE)
+[![Coverage](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/coverage.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+[![Tests](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/tests.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+[![Docs](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/docs.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki)
+[![Code Quality](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/quality.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+[![Version](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/version.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/releases)
+[![Python](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/647c885cba1418fa177a9daa0ac25d7c27300a03/python.svg)](https://www.python.org/downloads/)
+
+## Overview
+
+GRM is a two-layer tool: a Python CLI (built with Click) that delegates to an idempotent Ansible role for all remote operations. The CLI handles argument parsing, environment loading, internationalisation, and local registry management. The Ansible role handles the actual runner setup — creating dedicated system users, configuring rootless Docker, downloading and registering the runner binary, creating systemd user services, and setting up Docker prune timers.
+
+### Key capabilities
+
+- **Rootless Docker isolation** — Each runner gets its own rootless Docker daemon under a dedicated system user (`grm-<name>`).
+- **Multi-instance support** — Multiple isolated runners on the same host, each with independent users, data directories, and systemd services.
+- **Full lifecycle CLI** — `install`, `update`, `start`, `stop`, `enable`, `disable`, `status`, `remove`, `list`.
+- **Idempotent Ansible role** — Safe to re-run; second run produces zero changes.
+- **Automatic integration testing** — Every installation verifies the `.runner` registration file and systemd service state.
+- **Local runner registry** — Connection details stored locally; manage runners by name after installation.
+- **Internationalisation** — Console messages in English, Bulgarian, German, Russian, Chinese, and Polish.
+- **Security-conscious** — Secrets passed via temporary JSON files with `0600` permissions (CWE-214).
+
+### Supported operating systems
+
+| OS | Versions | Package manager |
+|----|----------|-----------------|
+| Arch Linux | rolling | pacman |
+| Ubuntu | 22.04, 24.04 | apt |
+| Debian | 12 | apt |
+
+All supported OSes are tested in CI via Molecule scenarios on every PR that changes Ansible files.
+
+## User Documentation
+
+- [Getting Started](Getting-Started) — Installation, quick start, token setup, first run, log viewing
+- [Installation](Installation) — Prerequisites, setup methods, multiple instances, runner registry
+- [CLI Commands](CLI-Commands) — All commands with arguments, options, and examples
+- [Troubleshooting](Troubleshooting) — Common issues, diagnostics, and solutions
+- [FAQ](FAQ) — Frequently asked questions
+
+## Technical Documentation
+
+- [Architecture](Architecture) — High-level design, component diagram, data flow, security model, per-runner isolation
+- [Development Setup](Development-Setup) — Environment setup, project structure, dependencies, linting, testing
+- [CI/CD Workflow](CI-CD-Workflow) — PR workflow, branch protection, release pipeline, change classification, badge generation
+- [Testing Strategy](Testing-Strategy) — Unit tests, Molecule scenarios, integration tests, CI distribution
+- [Decision Log](Decision-Log) — Key technical decisions and rationale (ADRs)
+- [Contributing Guide](Contributing-Guide) — Coding standards, PR workflow, commit conventions, Ansible role conventions
+
+## Quick Links
+
+- [Repository](https://git.oblachno.oblachno.fyi/oblachno-oss/grm)
+- [Releases](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/releases)
+- [Issues](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/issues)
+- [CI/CD Pipeline](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
+- [Changelog](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/src/branch/master/CHANGELOG.md)
+- [License (GPL-3.0)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/src/branch/master/LICENSE)

docs/mapping.json

@@ -0,0 +1,14 @@
+{
+  "index.md": "Home",
+  "user/getting-started.md": "Getting-Started",
+  "user/installation.md": "Installation",
+  "user/cli-commands.md": "CLI-Commands",
+  "user/troubleshooting.md": "Troubleshooting",
+  "user/faq.md": "FAQ",
+  "tech/architecture.md": "Architecture",
+  "tech/development-setup.md": "Development-Setup",
+  "tech/ci-cd-workflow.md": "CI-CD-Workflow",
+  "tech/testing-strategy.md": "Testing-Strategy",
+  "tech/decision-log.md": "Decision-Log",
+  "tech/contributing.md": "Contributing-Guide"
+}

docs/tech/architecture.md

@@ -0,0 +1,237 @@
+# Architecture
+
+GRM consists of two layers:
+
+1. **Python CLI** (`src/gitea_runner_manager/`) — built with Click, handles argument parsing, environment loading, i18n translations, and delegates to Ansible via the `ansible-playbook` subprocess.
+2. **Ansible Role** (`ansible/roles/gitea-runner/`) — idempotent role that creates a dedicated system user, sets up rootless Docker, installs the runner binary, creates a systemd user service, and registers the runner with Gitea.
+
+## High-Level Design
+
+The CLI is a thin orchestration layer. It does not perform any remote operations itself — every action (install, update, start, stop, etc.) is delegated to an Ansible playbook. The CLI's responsibilities are:
+
+- Parsing command-line arguments and options
+- Loading configuration from `.env` (via python-dotenv)
+- Resolving runner connection details from the local registry
+- Writing secrets to temporary JSON files (CWE-214 mitigation)
+- Constructing the `ansible-playbook` command with appropriate inventory, user, key, and extra-vars
+- Capturing and streaming Ansible output to log files
+- Maintaining the local runner registry (`~/.local/share/grm/runners.json`)
+- Providing colorised console output and operation reports
+
+The Ansible role handles all remote state: user creation, package installation, Docker configuration, binary download, runner registration, systemd service management, and Docker prune timers.
+
+## Component Tree
+
+```
+grm install <host>
+  └── RunnerManager.install()
+      └── ansible-playbook ansible/install-runner.yml
+          └── role: gitea-runner
+              ├── user_setup.yml       (create per-runner system user + lingering)
+              ├── rootless_docker.yml  (rootless Docker setup under runner user)
+              ├── install_runner.yml   (download binary, config, register, service)
+              ├── prune.yml            (Docker prune timer)
+              ├── healthcheck.yml      (health check script + systemd timer)
+              └── integration_test.yml (validate service is active)
+```
+
+The Ansible role task execution order (from `AGENTS.md`):
+
+```
+main.yml → systemd_check → user_setup → rootless_docker → install_runner → prune → healthcheck → integration_test
+```
+
+- `install_runner.yml` handles: download, config, validate, register, service
+- `main.yml` handles: prune, integration_test (NOT install_runner — avoids duplicates)
+- `systemctl --user` tasks must be guarded by `docker_rootless_setup`
+- Template creation tasks are NOT guarded by `docker_rootless_setup` (they just create files)
+
+### Ansible task files
+
+| Task file | Responsibility |
+|-----------|---------------|
+| `main.yml` | Entry point — includes all other task files in order |
+| `systemd_check.yml` | Verifies systemd is available on the target host |
+| `user_setup.yml` | Creates the per-runner system user, enables lingering, configures subuid/subgid, creates data and config directories |
+| `rootless_docker.yml` | Installs Docker packages (apt for Debian/Ubuntu, pacman for Arch), runs `dockerd-rootless-setuptool.sh install`, starts and enables the rootless Docker daemon |
+| `install_runner.yml` | Downloads the gitea_runner binary, creates the config file, validates the binary, registers the runner with Gitea, creates and starts the systemd user service |
+| `download_gitea_runner.yml` | Downloads the gitea_runner binary from GitHub releases |
+| `validate.yml` | Validates the downloaded binary |
+| `register.yml` | Registers the runner with Gitea using the registration token |
+| `service.yml` | Creates the systemd user service file and starts/enables the service |
+| `prune.yml` | Creates a systemd user timer for daily Docker image and volume pruning |
+| `healthcheck.yml` | Installs a health check script and systemd timer that monitors Docker daemon, runner service, and disk space; restarts unhealthy services automatically |
+| `integration_test.yml` | Verifies the `.runner` file exists and the systemd service is active; optionally queries the Gitea API |
+| `deregister.yml` | Deregisters the runner from Gitea and removes the `.runner` file |
+| `update_runner.yml` | Downloads a new version of the gitea_runner binary |
+
+### Ansible templates
+
+| Template | Purpose |
+|----------|---------|
+| `gitea-runner-user.service.j2` | Systemd user service for the gitea_runner daemon |
+| `gitea-runner-config.yaml.j2` | Runner configuration file (labels, capacity, log level) |
+| `docker-prune.service.j2` | Systemd user service for Docker pruning (oneshot) |
+| `docker-prune.timer.j2` | Systemd user timer triggering daily Docker prune |
+| `runner-healthcheck.sh.j2` | Health check script (checks Docker, runner service, disk space; restarts if down) |
+| `runner-healthcheck.service.j2` | Systemd user service for the health check (oneshot) |
+| `runner-healthcheck.timer.j2` | Systemd user timer triggering periodic health checks |
+
+## Per-Runner Isolation
+
+Each runner runs as a systemd user service under a dedicated system user (`grm-<name>`). Each instance has fully isolated resources:
+
+- **User**: `grm-<name>` (dedicated system user with lingering enabled)
+- **Home**: `/home/grm-<name>/`
+- **Data**: `/var/lib/gitea-runner/<name>/`
+- **Config**: `/etc/gitea-runner/<name>/`
+- **Service**: `gitea-runner.service` (systemd user service)
+- **Docker socket**: `/run/user/<UID>/docker.sock` (rootless, per-runner)
+- **subuid/subgid**: `grm-<name>:100000:65536` (user namespace mapping)
+
+Lingering is enabled via `loginctl enable-linger` so the user's systemd services run without an active login session. This is essential for runners that need to operate continuously.
+
+## Component Interactions
+
+```mermaid
+flowchart TD
+    CLI["Python CLI<br/>src/gitea_runner_manager/<br/>(Click)"]
+    RM["RunnerManager<br/>runner_manager.py"]
+    EXEC["Executor<br/>executor.py"]
+    REG["Registry<br/>registry.py<br/>~/.local/share/grm/runners.json"]
+    ANS["ansible-playbook subprocess"]
+    ROLE["Ansible Role<br/>ansible/roles/gitea-runner/"]
+    USER["user_setup.yml<br/>create system user + lingering"]
+    DOCKER["rootless_docker.yml<br/>rootless Docker setup"]
+    INSTALL["install_runner.yml<br/>download, config, register, service"]
+    PRUNE["prune.yml<br/>Docker prune timer"]
+    TEST["integration_test.yml<br/>validate service active"]
+    GITEA["Gitea instance<br/>registration + API"]
+    SYSTEMD["systemd user service<br/>gitea-runner.service"]
+    LOG["Log files<br/>~/.local/state/grm/logs/"]
+
+    CLI --> RM
+    RM --> REG
+    RM --> EXEC
+    EXEC -->|subprocess| ANS
+    EXEC -->|stream output| LOG
+    ANS --> ROLE
+    ROLE --> USER
+    ROLE --> DOCKER
+    ROLE --> INSTALL
+    ROLE --> PRUNE
+    ROLE --> TEST
+    INSTALL -->|register| GITEA
+    INSTALL --> SYSTEMD
+    DOCKER --> SYSTEMD
+    TEST -->|optional API check| GITEA
+```
+
+## Data Flow
+
+### Installation flow
+
+1. User runs `grm install <host> --user <user> --key <key> --name <name>`
+2. CLI loads `.env` for `GITEA_URL` and `GITEA_REGISTRATION_TOKEN`
+3. `RunnerManager.install()` constructs extra-vars dict with registration token, runner name, Gitea URL, and optional admin token/labels
+4. Extra-vars are written to a temporary JSON file with `0600` permissions
+5. `AnsibleExecutor.run()` invokes `ansible-playbook ansible/install-runner.yml` with the temp file via `--extra-vars @tempfile`
+6. Ansible connects to the remote host via SSH and executes the role:
+   - Creates system user `grm-<name>` with lingering
+   - Installs Docker packages and sets up rootless Docker
+   - Downloads the gitea_runner binary
+   - Creates the runner config file
+   - Registers the runner with Gitea
+   - Creates and starts the systemd user service
+   - Sets up the Docker prune timer
+   - Installs the health check script and systemd timer
+   - Runs the integration test (verifies `.runner` file and service state)
+7. Ansible output is streamed to a timestamped log file at `~/.local/state/grm/logs/ansible-<timestamp>.log`
+8. On success, the runner is added to the local registry at `~/.local/share/grm/runners.json`
+9. The temporary extra-vars file is deleted
+
+### Lifecycle command flow
+
+1. User runs `grm <command> <runner_name>` (e.g., `grm stop prod-runner`)
+2. `RunnerManager._resolve_runner()` looks up the runner in the local registry
+3. If `--host` and `--user` are provided, they override registry values
+4. The corresponding playbook is executed (e.g., `stop-runner.yml`)
+5. Ansible connects to the remote host and performs the action
+
+### List command flow
+
+1. User runs `grm list`
+2. `RunnerManager.list_runners()` reads all entries from the local registry
+3. For each runner, an Ansible ad-hoc command checks `systemctl --user is-active gitea-runner`
+4. Results are displayed in a table with columns: NAME, HOST, USER, LABELS, STATUS
+
+## Security Model
+
+### Rootless Docker
+
+Each runner operates under a dedicated unprivileged system user. The Docker daemon runs in rootless mode via `dockerd-rootless-setuptool.sh install`, which configures:
+
+- User namespace mapping via `/etc/subuid` and `/etc/subgid` (range: 100000-165535)
+- Rootless Docker socket at `/run/user/<UID>/docker.sock`
+- `slirp4netns` for user-mode networking
+- `fuse-overlayfs` for rootless container storage
+
+Containers launched by the runner never have root access to the host. The rootless Docker daemon is started as a systemd user service and persists via lingering.
+
+### Secret handling
+
+Registration tokens and admin API tokens are never exposed on the command line. The `RunnerManager._extra_vars_file()` context manager:
+
+1. Creates a temporary file via `tempfile.mkstemp()`
+2. Writes the extra-vars JSON to the file
+3. Sets permissions to `0600` (owner read/write only)
+4. Passes the file to Ansible via `--extra-vars @tempfile`
+5. Deletes the file in a `finally` block, even if an exception occurs
+
+This prevents secrets from appearing in the process list (`ps aux`), addressing CWE-214.
+
+### No shell injection
+
+The CLI never uses `shell=True` with subprocess. All Ansible commands are constructed as argument lists (`list[str]`), preventing shell injection attacks. The `subprocess.Popen` and `subprocess.run` calls are marked with `nosec` comments after security review.
+
+### Bandit security scanning
+
+The CI pipeline runs Bandit on every PR to catch common Python security issues. The scan covers all source code in `src/`.
+
+## Additional Components
+
+From `AGENTS.md`, the project also includes:
+
+- **devx package** (installed from git) — Reusable CI/CD tools: auto-merge, post-merge, release, publishing, molecule distribution, PR reviews, failure notifications. This package is not part of the GRM tool itself — it provides the CI/CD automation infrastructure.
+- **Versioning** (`cliff.toml`) — git-cliff configuration for automated semver versioning from conventional commits.
+
+## Python Modules
+
+The Python CLI layer (`src/gitea_runner_manager/`) consists of the following modules:
+
+| Module | Description |
+|--------|-------------|
+| `cli.py` | Click-based CLI entry point — defines all commands (install, update, start, stop, enable, disable, status, remove, list) |
+| `runner_manager.py` | Ansible orchestration + registry integration — delegates to executor and manages runner lifecycle |
+| `executor.py` | Ansible subprocess execution — runs `ansible-playbook` with extra-vars via temp JSON files, streams output to log files |
+| `registry.py` | Local JSON runner registry at `~/.local/share/grm/runners.json` — stores connection metadata |
+| `i18n.py` | Internationalisation translations (en, bg, de, ru, zh, pl) — opt-in via `GRM_LANG` environment variable |
+| `exceptions.py` | Custom exceptions (`GRMError`, `AnsibleError`) |
+| `logging_config.py` | Logging configuration — writes all messages to `~/.local/state/grm/logs/grm.log` at DEBUG level |
+| `report.py` | Operation report tracking — prints a step-by-step report with status icons after each command |
+| `ui.py` | User-facing output utilities — colorised console output via `click.style`, with log file always receiving plain text |
+| `translations.json` | Translation strings for all supported languages |
+
+## Logging
+
+GRM writes to two destinations:
+
+| Destination | Level | Content |
+|-------------|-------|---------|
+| Console (stdout) | `GRM_LOG_LEVEL` (default: INFO) | Colorised user-facing messages and operation reports |
+| `~/.local/state/grm/logs/grm.log` | DEBUG | All messages with timestamps and severity |
+| `~/.local/state/grm/logs/ansible-<timestamp>.log` | — | Full Ansible playbook output per execution |
+
+Console output is automatically colorised via `click.style`: operation headers in bright cyan, completed steps in green, failures in red, and status updates in yellow. The log file always captures plain text (no ANSI codes) at DEBUG level regardless of the console setting.
+
+Set `GRM_LOG_LEVEL` to one of `DEBUG`, `INFO`, `WARNING`, `ERROR`, or `CRITICAL` to control console verbosity.

docs/tech/ci-cd-workflow.md

@@ -0,0 +1,334 @@
+# CI/CD Workflow
+
+GRM uses a fully automated CI/CD pipeline built on Gitea Actions. Every change to master goes through a mandatory PR workflow with branch protection, automated review, and auto-merge. Releases are automated via git-cliff and conventional commits.
+
+## Workflow Overview
+
+| Workflow | Trigger | Purpose |
+|----------|---------|---------|
+| `ci.yml` | PR opened/synchronized | Quality checks (lint, test, coverage) + molecule tests |
+| `auto-merge.yml` | PR labeled `ready-to-merge` | Validates and squash-merges the PR |
+| `post-merge.yml` | Push to `master` | Release, wiki sync, badges, Vikunja task update |
+| `publish.yml` | Tag push (`v*`) | Build and publish package to PyPI, create Gitea release |
+
+Every change to master goes through a mandatory PR workflow. No exceptions.
+
+## PR Workflow
+
+### 1. Create Vikunja Task
+
+Create a task in Vikunja project 6 to get a `GRM-N` identifier.
+
+### 2. Create Branch
+
+```bash
+git checkout master && git pull
+git checkout -b GRM-N-short-description
+```
+
+### 3. Implement Changes
+
+- Write code following conventions
+- Write/update tests (100% coverage required)
+- Update documentation (CHANGELOG, README, AGENTS.md as needed)
+
+### 4. Commit (Conventional Commits)
+
+Branch commits use conventional commit format (no `GRM-N:` prefix):
+
+```
+feat: add new feature
+fix: resolve bug
+docs: update README
+```
+
+### 5. Push and Create PR
+
+- **PR title format**: `GRM-N: <vikunja task title>` (must match the Vikunja task title exactly)
+- PR body: summary of changes, `Closes GRM-N`
+- Add `ready-to-merge` label **only after review is complete**
+
+### 6. Review the PR (Mandatory — Before Adding ready-to-merge Label)
+
+Review the full diff (`git diff master...HEAD`) focusing on:
+
+- **Functional completeness**: Does the code do what it claims? Are all requirements met?
+- **Edge cases**: Are boundary conditions, empty inputs, error paths handled?
+- **Technical excellence**:
+  - Architecture compliance and evolution
+  - Single Responsibility Principle (SRP)
+  - Deduplication (no copy-paste, single source of truth)
+  - Code smells detection and removal
+  - Best industry practices
+  - Industry-grade code quality
+  - Reusability
+  - Clean code
+  - Readability
+  - Maintainability
+  - Extensibility
+- **Performance**: No unnecessary allocations, O(n) vs O(n²), efficient data structures
+- **Security**: No secrets in logs/process list, input validation, no injection vectors
+- **User experience**: Clear error messages, intuitive CLI flags, helpful output
+- **Documentation**: Completeness and relevance of docs, CHANGELOG entries, AGENTS.md updates
+
+Post review comments using `devx.ci.pr_review`:
+
+```bash
+CI_GITEA_TOKEN=<token> python -m devx.ci.pr_review <pr_number> <owner/repo> \
+  --event REQUEST_CHANGES \
+  --body "Review summary" \
+  --comments-json comments.json
+```
+
+### 7. Address Review Comments
+
+Fix each comment one by one, commit, and push. Re-review until satisfied.
+
+### 8. Approve and Merge
+
+Once all comments are addressed:
+
+```bash
+CI_GITEA_TOKEN=<token> python -m devx.ci.pr_review <pr_number> <owner/repo> \
+  --event APPROVE \
+  --body "All comments addressed. LGTM."
+```
+
+Then add the `ready-to-merge` label. The auto-merge workflow will:
+
+1. **Validate** PR title format and match against Vikunja task title
+2. **Check** that at least one APPROVE review exists
+3. Wait for all CI checks to pass
+4. Squash-merge with title: `GRM-N <conventional commit message>` (space-separated)
+5. The post-merge workflow marks the Vikunja task as done
+6. The release workflow automatically versions, tags, and publishes
+
+### 9. Post-Merge Automation
+
+After the squash-merge:
+
+- The **post-merge workflow** (`.gitea/workflows/post-merge.yml`) triggers on push to `master` and runs `devx.ci.post_merge` to mark the Vikunja task as done, extracting the task ID from the merge commit message.
+- The **release workflow** (`.gitea/workflows/release.yml`) triggers on push to `master` and automatically versions, tags, and publishes (see below).
+
+## Branch Protection (Required Gitea Settings)
+
+Configure the following branch protection rules for `master` in Gitea repo settings:
+
+- **Require pull request**: No direct pushes to master
+- **Require approval review**: At least 1 `APPROVE` review before merge
+- **Require status checks**: CI quality + molecule tests must pass
+- **Block force pushes**: No history rewriting on master
+
+The auto-merge workflow enforces the APPROVE review check programmatically as a defense-in-depth measure, but branch protection is the primary gate.
+
+## CI Path Filtering
+
+The CI workflow (`.gitea/workflows/ci.yml`) includes a `detect-changes` job that checks whether any files under `ansible/` or `.ansible-lint` have changed. If no Ansible files are changed, molecule tests are skipped — this prevents non-Ansible changes (e.g., Python scripts, workflow YAML, docs) from being blocked by molecule test infrastructure flakiness.
+
+The `detect-changes` job:
+
+- For pull requests: compares `origin/master` against the PR head SHA
+- For pushes to master: compares `HEAD~1` against `HEAD`
+- Outputs `ansible-changed` as `true` or `false`
+
+The `molecule-tests` job depends on both `quality` and `detect-changes`, and only runs if `ansible-changed == 'true'`.
+
+CI triggers only on `opened` and `synchronize` PR events (not `labeled`).
+
+## CI Quality Job
+
+The `quality` job in `.gitea/workflows/ci.yml` runs:
+
+1. `make setup` — full environment setup
+2. `make lint-all` — ruff + pyright + bandit + ansible-lint + checkmake
+3. `make pytest-cov` — unit tests with 100% coverage enforcement
+4. `python -m devx.tools.check_test_speed --max-seconds 10` — verify unit tests run fast
+5. `PYTHONPATH=src python -m devx.ci.release --dry-run` — release dry-run validation
+
+## Automated Release Pipeline
+
+After a PR is merged to master, the release pipeline runs automatically.
+
+### Release Workflow (`.gitea/workflows/release.yml`)
+
+- Triggers on push to `master`
+- Sets up full dev environment (`make setup`) so lint and tests can run
+- Installs git-cliff (version 2.13.0)
+- Configures git as `grm-ci-bot`
+- Runs `devx.ci.release` which uses **git-cliff** to:
+  - **Checks for user-facing changes** via `devx.ci.classify_changes` — if only workflow/infrastructure files changed, the release is **skipped entirely** — no version bump, no tag, no publish
+  - Calculate the next semver version from conventional commits since the last tag
+  - Update `__version__` in `src/gitea_runner_manager/__init__.py` (single source of truth)
+  - Update `CHANGELOG.md` with the new version section
+  - **Run `make lint-ruff` and `make pytest-cov`** to verify the release is healthy
+  - If lint or tests fail, **abort immediately** — no commit, no tag
+  - Commit with `release: vX.Y.Z [skip ci]` prefix (the `[skip ci]` prevents re-triggering post-merge on the release commit)
+  - Create an annotated tag `vX.Y.Z` on the release commit
+  - Push both the commit and tag to master
+- `--skip-tests` flag bypasses test verification (emergency use only, not recommended)
+- Loops are prevented by `has_unreleased_changes` — after a release commit is tagged, the next run finds no unreleased changes and exits
+- On failure, creates a Gitea issue via `devx.ci.notify_failure`
+
+### Publish Workflow (`.gitea/workflows/publish.yml`)
+
+- Triggers on tag push (`v*`)
+- Installs git-cliff (version 2.13.0)
+- Installs build tools (`build`, `twine`, `requests`, `python-dotenv`, `click`)
+- Validates `PYPI_TOKEN` is set (warns if missing)
+- Builds the Python package
+- Optionally publishes to PyPI (if `PYPI_TOKEN` is set)
+- Creates a Gitea release with git-cliff-generated release notes
+- Uses `devx.ci.publish` for build and publish orchestration
+- On failure, creates a Gitea issue via `devx.ci.notify_failure`
+
+### Auto-Merge Workflow (`.gitea/workflows/auto-merge.yml`)
+
+- Triggers on `pull_request` labeled events
+- Runs `devx.ci.auto_merge` with the branch name, PR title, repository, PR number, and label name
+- Validates PR title format, checks for APPROVE review, waits for CI, and squash-merges
+
+### Post-Merge Workflow (`.gitea/workflows/post-merge.yml`)
+
+- Triggers on push to `master`
+- Consolidates release, wiki sync, badge generation, and Vikunja task updates into a single workflow
+- **detect-type** — Runs `devx.ci.detect_release_commit` to check if the commit is a release commit (`release: vX.Y.Z`). All subsequent jobs skip for release commits (the `[skip ci]` tag also prevents re-triggering).
+- **release** — Runs `devx.ci.release` (see Automated Release Pipeline below)
+- **sync-wiki** — Syncs documentation to the Gitea wiki via `devx.ci.sync_wiki`
+- **badges** — Generates and pushes quality badge SVGs to the `badges` branch via `devx.ci.push_badges`. Runs after the release job (even if release fails or is skipped) so the version badge always reflects the latest state.
+- **vikunja** — Marks the corresponding Vikunja task as done via `devx.ci.post_merge`
+
+### Smart CI: User-Facing vs Workflow-Only Changes
+
+Not all changes require the full CI pipeline or a new release. The project uses
+`devx.ci.classify_changes` to classify changed files into two categories.
+
+**Classification strategy (safe-by-default):** Any file NOT in the explicit
+workflow-only allowlist is treated as user-facing. This prevents new file types
+from accidentally skipping releases. Classification is config-driven via
+`[tool.devx.classify]` in `pyproject.toml`.
+
+**User-facing paths** (tool changes → release needed):
+- `src/gitea_runner_manager/**` — Python CLI source
+- `ansible/**` — Ansible role
+- `pyproject.toml` — Package metadata
+
+**Workflow-only paths** (infrastructure → no release needed):
+- `.gitea/workflows/**`, `docs/**`, `tests/**`
+- `AGENTS.md`, `README.md`, `CHANGELOG.md`, `Makefile`, `cliff.toml`, etc.
+
+**CI behavior based on classification:**
+- **Molecule tests**: Only run when `ansible/` or `.ansible-lint` files change
+- **Release dry-run**: Only runs when user-facing files change (separate `release-dry-run` job)
+- **Quality job** (lint, unit tests, coverage, doc-coverage): Always runs
+- **Release workflow**: `release.py` calls `classify_changes` to check if any
+  user-facing files changed since the last tag. If not, the release is skipped
+  entirely — no version bump, no tag, no publish.
+
+### Dynamic Runner Discovery
+
+Molecule tests are distributed across available Gitea Actions runners
+dynamically. The `discover-runners` job runs `devx.molecule.discover_runners` which queries the Gitea API for
+registered runners at three levels (repo, org, instance) and generates
+a matrix of runner indices. If the API query fails (e.g., no admin
+access for instance-level runners), it falls back to the
+`MOLECULE_RUNNERS` repo variable, then to a default of 3.
+
+The `molecule-tests` job uses `fromJSON()` to consume the dynamic
+matrix, and passes the runner count to `python -m devx.molecule.distribute_molecule
+--max-runners` so test pairs are evenly distributed.
+
+When adding or removing Gitea runners:
+1. If runners are registered at the repo/org level, they're auto-detected
+2. If runners are at the instance level, update the `MOLECULE_RUNNERS` repo variable
+3. The workflow automatically scales the matrix to match available runners
+
+### Molecule Test Distribution
+
+`devx.molecule.distribute_molecule` discovers all molecule scenarios
+under `ansible/roles/*/molecule/` and crosses them with the supported
+OS platform matrix (defined in `devx.molecule.platforms`), then splits
+the resulting test pairs evenly across the requested number of runners.
+Each pair is encoded as `scenario|platform_name|platform_image|platform_command`.
+
+`devx.molecule.molecule_ci_guard` runs the actual molecule test for a
+given test pair, with CI context (Gitea URL, token, run ID) for
+reporting results back to the commit status API.
+
+### Commit Message Validation
+
+`devx.ci.validate_commit_msg` validates that commit messages
+follow the conventional commit format (`feat:`, `fix:`, `docs:`, etc.).
+It is used by the pre-commit hook to enforce conventional commits on
+feature branches.
+
+### Release Commit Detection
+
+The `detect-type` job in the post-merge workflow runs
+`devx.ci.detect_release_commit` to check whether the latest commit
+is a release commit (format: `release: vX.Y.Z`). When a release commit
+is detected, all post-merge jobs (release, sync-wiki, badges, vikunja)
+are skipped — the tag push triggers the publish workflow instead.
+
+### Badge Generation and Push
+
+The `badges` job in the post-merge workflow runs
+`devx.ci.push_badges` which:
+1. Fetches the latest master and hard-resets to it (picks up release commits)
+2. Generates quality badge SVG files via `devx.tools.generate_badges`
+3. Creates an orphan `badges` branch
+4. Copies SVG files to the branch root
+5. Force-pushes the branch to the remote
+
+The badges job depends on the `release` job and uses `if: always()` so it
+runs even if release fails or is skipped. This ensures the version badge
+always reflects the actual state of the repository after any release
+commits have been pushed.
+
+## git-cliff Commit Preprocessing
+
+Merge commits on master have the format `GRM-N <conventional commit>`. The `GRM-N ` prefix is not a valid conventional commit prefix, so `cliff.toml` includes a `commit_preprocessors` entry that strips it before parsing:
+
+```toml
+commit_preprocessors = [
+    # Strip GRM-N task ID prefix from merge commits so git-cliff sees conventional commits
+    { pattern = "^GRM-\\d+\\s+", replace = "" },
+]
+```
+
+This ensures all merged work appears in the changelog.
+
+### git-cliff Configuration Highlights (`cliff.toml`)
+
+- `conventional_commits = true` — parse conventional commit format
+- `filter_unconventional = true` — skip non-conventional commits
+- `render_always = true` — always render the changelog
+- `trim = true` — trim whitespace
+- Commit parsers group commits into: Features, Bug Fixes, Documentation, Performance, Refactor, Styling, Testing, Miscellaneous Tasks, Security, Revert, Other
+- `chore(release): prepare for`, `chore(deps.*)`, `chore(pr)`, `chore(pull)` commits are skipped
+- `sort_commits = "oldest"` — oldest commits first
+
+## Version Bumping Rules (git-cliff)
+
+| Commit type | Version bump |
+|-------------|-------------|
+| `feat:` | minor (0.X.0) |
+| `fix:` | patch (0.0.X) |
+| `feat!:` or `BREAKING CHANGE` | minor (pre-1.0: major would be 1.0.0) |
+| `chore:`, `ci:`, `docs:` | no bump (excluded by cliff.toml) |
+
+From `cliff.toml` `[bump]` section:
+
+- `features_always_bump_minor = true`
+- `breaking_always_bump_major = false`
+- `initial_tag = "0.1.0"`
+
+The version source is `__version__` in `src/gitea_runner_manager/__init__.py`, read by setuptools via `dynamic = ["version"]` in `pyproject.toml`. The release script only updates `__init__.py` — no need to touch `pyproject.toml`. `grm --version` reports this version.
+
+## Title Format Summary
+
+| What | Format | Example |
+|------|--------|---------|
+| Branch name | `GRM-N-short-description` | `GRM-33-add-pr-review-step` |
+| Branch commits | `<conventional commit>` | `feat: add review script` |
+| PR title | `GRM-N: <vikunja task title>` | `GRM-33: Add mandatory PR review step` |
+| Merge commit | `GRM-N <conventional commit>` | `GRM-33 feat: add review script` |

docs/tech/contributing.md

@@ -0,0 +1,228 @@
+# Contributing Guide
+
+## Key Conventions
+
+- Python 3.12+ required (ruff/pyright target `py312`)
+- 100% test coverage required (`--cov-fail-under=100`)
+- Conventional commits on feature branches (no `GRM-N:` prefix)
+- Branch names must include `GRM-N` task ID
+- Line length: 120 chars
+- Secrets are passed via temp JSON files, never on the command line (CWE-214)
+- CI triggers only on `opened` and `synchronize` PR events (not `labeled`)
+- No `print()` — use `click.echo()` via `ui.say()` for console output
+- No bare `except` — catch specific exceptions
+- No `TODO`/`FIXME` comments in committed code
+- No functions longer than 50 lines
+- No `shell=True` with subprocess
+- No `eval()` or `exec()`
+- No raw strings in `click.echo()` without `_()` wrapper (i18n)
+- No `open()` without `with` statement
+- No `Popen()` without cleanup
+
+## Code Style Rules
+
+- **Python version**: 3.12+ (ruff and pyright target `py312`)
+- **Line length**: 120 characters
+- **Test coverage**: 100% required (`--cov-fail-under=100`)
+- **Secrets handling**: Secrets are passed via temp JSON files with `0600` permissions, never on the command line (CWE-214). Extra-vars are written to a temporary JSON file and passed via `--extra-vars @tempfile`, which is deleted after execution. This prevents secrets from being visible in the process list (`ps aux`).
+- **Linting**: `make lint-all` runs ruff + pyright + bandit + ansible-lint + checkmake + actionlint
+- **Formatting**: `ruff format` with double quotes and space indentation
+- **Type checking**: `pyright` in strict mode for `src/gitea_runner_manager/`
+- **Security scanning**: `bandit -r src/` on every PR
+- **Import rules**: `src/gitea_runner_manager/` NEVER imports from devx — the GRM tool is self-contained
+
+## Commit Rules
+
+Branch commits use conventional commit format (no `GRM-N:` prefix):
+
+```
+feat: add new feature
+fix: resolve bug
+docs: update README
+ci: update workflow
+refactor: simplify executor
+test: add molecule scenario
+chore: update dependencies
+```
+
+The pre-commit hook validates that commit messages follow the conventional commit format. Non-conventional commits are rejected.
+
+### Version Bumping Rules
+
+| Commit type | Version bump |
+|-------------|-------------|
+| `feat:` | minor (0.X.0) |
+| `fix:` | patch (0.0.X) |
+| `feat!:` or `BREAKING CHANGE` | minor (pre-1.0: major would be 1.0.0) |
+| `chore:`, `ci:`, `docs:` | no bump (excluded by cliff.toml) |
+
+## Branch Naming
+
+| What | Format | Example |
+|------|--------|---------|
+| Branch name | `GRM-N-short-description` | `GRM-33-add-pr-review-step` |
+| Branch commits | `<conventional commit>` | `feat: add review script` |
+| PR title | `GRM-N: <vikunja task title>` | `GRM-33: Add mandatory PR review step` |
+| Merge commit | `GRM-N <conventional commit>` | `GRM-33 feat: add review script` |
+
+## PR Workflow Summary
+
+Every change to master goes through this workflow. No exceptions.
+
+1. **Create Vikunja task** — get a `GRM-N` identifier (Vikunja project 6)
+2. **Create branch** — `GRM-N-short-description`
+3. **Implement** — write code, tests (100% coverage), update docs
+4. **Commit** — conventional commits (no `GRM-N:` prefix on branch)
+5. **Push & create PR** — title: `GRM-N: <vikunja task title>`, body: summary + `Closes GRM-N`
+6. **Review** — review the full diff focusing on: functional completeness, edge cases, technical excellence (architecture, SRP, deduplication, code smells, best practices, code quality, reusability, clean code, readability, maintainability, extensibility), performance, security, UX, documentation completeness/relevance. Post review comments via `devx.ci.pr_review`.
+7. **Address comments** — fix each comment, commit, push, re-review
+8. **Approve** — post an `APPROVE` review via `devx.ci.pr_review`
+9. **Add `ready-to-merge` label** — auto-merge workflow squash-merges with title `GRM-N <conventional commit message>`, post-merge workflow marks the Vikunja task as done, release workflow automatically versions and tags
+### 1. Create Vikunja task
+
+Create a task in Vikunja project 6 to get a `GRM-N` identifier.
+
+### 2. Create branch
+
+```bash
+git checkout master && git pull
+git checkout -b GRM-N-short-description
+```
+
+### 3. Implement changes
+
+- Write code following conventions above
+- Write/update tests (100% coverage required)
+- Update documentation (CHANGELOG, README, AGENTS.md, docs/ as needed)
+
+### 4. Commit (conventional commits)
+
+Branch commits use conventional commit format (no `GRM-N:` prefix):
+
+```
+feat: add new feature
+fix: resolve bug
+docs: update README
+```
+
+### 5. Push and create PR
+
+- **PR title format**: `GRM-N: <vikunja task title>` (must match the Vikunja task title exactly)
+- PR body: summary of changes, `Closes GRM-N`
+- Add `ready-to-merge` label **only after review is complete**
+
+### 6. Review the PR
+
+Review the full diff (`git diff master...HEAD`) focusing on:
+
+- **Functional completeness**: Does the code do what it claims? Are all requirements met?
+- **Edge cases**: Are boundary conditions, empty inputs, error paths handled?
+- **Technical excellence**:
+  - Architecture compliance and evolution
+  - Single Responsibility Principle (SRP)
+  - Deduplication (no copy-paste, single source of truth)
+  - Code smells detection and removal
+  - Best industry practices
+  - Industry-grade code quality
+  - Reusability
+  - Clean code
+  - Readability
+  - Maintainability
+  - Extensibility
+- **Performance**: No unnecessary allocations, O(n) vs O(n^2), efficient data structures
+- **Security**: No secrets in logs/process list, input validation, no injection vectors
+- **User experience**: Clear error messages, intuitive CLI flags, helpful output
+- **Documentation**: Completeness and relevance of docs, CHANGELOG entries, AGENTS.md updates
+
+Post review comments using `devx.ci.review_pr`:
+
+```bash
+CI_GITEA_TOKEN=<token> python -m devx.ci.review_pr <pr_number> <owner/repo> \
+  --event REQUEST_CHANGES \
+  --body "Review summary" \
+  --comments-json comments.json
+```
+
+### 7. Address review comments
+
+Fix each comment one by one, commit, and push. Re-review until satisfied.
+
+### 8. Approve and merge
+
+Once all comments are addressed, post an approval review:
+
+```bash
+CI_GITEA_TOKEN=<token> python -m devx.ci.review_pr <pr_number> <owner/repo> \
+  --event APPROVE --checklist-confirmed \
+  --checklist-categories 1,2,3,4,5,6,7,8,9,10,11,12,13 \
+  --body "All 13 checklist categories verified."
+```
+
+Then add the `ready-to-merge` label. The auto-merge workflow will:
+
+1. Validate PR title format and match against Vikunja task title
+2. Check that at least one APPROVE review exists
+3. Wait for all CI checks to pass
+4. Squash-merge with title: `GRM-N <conventional commit message>` (space-separated)
+5. The post-merge workflow marks the Vikunja task as done
+6. The release workflow automatically versions, tags, and publishes
+
+> **IMPORTANT**: Never manually merge PRs via the API. Always use the auto-merge workflow by adding the `ready-to-merge` label. Manual merges bypass the `GRM-N <conventional>` format enforcement.
+
+### Branch Protection (Required Gitea Settings)
+
+Branch protection is automatically configured by `devx.tools.configure_repo` (runs as a `configure-repo` job in the post-merge workflow). The following rules are enforced for `master`:
+
+- **Require pull request**: No direct pushes to master
+- **Require approval review**: At least 1 `APPROVE` review before merge
+- **Require status checks**: CI quality + molecule tests must pass
+- **Block force pushes**: No history rewriting on master
+
+The auto-merge workflow enforces the APPROVE review check programmatically as a defense-in-depth measure, but branch protection is the primary gate.
+
+## Build & Test Commands
+
+```bash
+make setup          # Create venv, install deps, set up hooks, install CI tools
+make lint-all       # ruff + pyright + bandit + ansible-lint + checkmake + actionlint
+make pytest-cov     # Unit tests with 100% coverage enforcement
+make test-unit      # Unit tests without coverage
+make molecule       # All 6 scenarios on Ubuntu 22.04
+make molecule-all   # All 6 scenarios on all 4 supported OSes
+make test-all       # pytest-cov + molecule
+make workflow-check # Static lint + dry-run of workflow YAML
+```
+
+## Ansible Role Conventions
+
+```
+main.yml → systemd_check → user_setup → rootless_docker → install_runner → prune → integration_test
+```
+
+- `install_runner.yml` handles: download, config, validate, register, service
+- `main.yml` handles: prune, integration_test (NOT install_runner — avoids duplicates)
+- `systemctl --user` tasks must be guarded by `docker_rootless_setup`
+- Template creation tasks are NOT guarded by `docker_rootless_setup` (they just create files)
+- `apt` tasks use `cache_valid_time: 3600` to avoid unnecessary cache updates
+- `remove-runner.yml` runs `loginctl disable-linger` and removes subuid/subgid entries
+
+## Change Classification
+
+Not all changes require a new release. The project classifies changes using `devx.ci.classify_changes`:
+
+**Workflow-only paths** (no release needed):
+- `.gitea/**`, `docs/**`, `tests/**`, `scripts/**`
+- `AGENTS.md`, `README.md`, `CHANGELOG.md`, `Makefile`, `cliff.toml`
+- Lint config files, `.env.example`, `.gitignore`
+
+**User-facing paths** (release needed):
+- `src/gitea_runner_manager/**` (except `__init__.py`)
+- `ansible/**`
+- `pyproject.toml`
+
+When working on workflow/CI/docs-only changes, use `ci:` or `docs:` commit prefixes. Do NOT bump the version or create tags for workflow-only changes.
+
+## Known Issues
+
+- `ansible-lint` may warn about `command-instead-of-module` for `systemctl --user` calls — this is expected (systemd module doesn't support user services) and skipped in `.ansible-lint`
+- Molecule Docker driver may print "Event loop is closed" warnings on interrupt — harmless

docs/tech/decision-log.md

@@ -0,0 +1,123 @@
+# Decision Log
+
+Key technical decisions for the GRM project, extracted from `CHANGELOG.md` and `AGENTS.md`.
+
+---
+
+## ADR-001: Dynamic Versioning via `__init__.py`
+
+**Date:** 2026-06-21 (v0.2.0 unreleased)
+
+**Decision:** Use `dynamic = ["version"]` in `pyproject.toml` with setuptools `attr` to source the version from `__version__` in `src/gitea_runner_manager/__init__.py`.
+
+**Rationale:** `__init__.py` is the single source of truth for the version. The release script (`devx.ci.release`) only updates `__init__.py` — there is no need to touch `pyproject.toml`. `grm --version` reports this version directly. This eliminates version duplication across files and ensures the runtime version always matches the tagged release.
+
+**Source:** `CHANGELOG.md` (Unreleased — Added), `AGENTS.md` (Version Bumping Rules)
+
+---
+
+## ADR-002: Rootless Docker per Runner
+
+**Date:** Project inception (documented in README Architecture)
+
+**Decision:** Each runner instance runs in an isolated rootless Docker environment under a dedicated system user (`grm-<name>`), with its own Docker socket at `/run/user/<UID>/docker.sock`.
+
+**Rationale:** Rootless Docker per-runner avoids conflicts with the host's Docker installation and enables true parallel execution of multiple runners on the same host. Each instance has fully isolated resources: user, home, data directory, config directory, systemd user service, and Docker socket. This is a core feature of GRM — enabling multiple isolated runners on the same host. User namespace mapping is configured via `/etc/subuid` and `/etc/subgid` entries (range: 100000-165535). Lingering is enabled so the user's systemd services run without an active login session.
+
+**Source:** `README.md` (Architecture, Features), `AGENTS.md` (Architecture)
+
+---
+
+## ADR-003: Conventional Commits + git-cliff for Automated Versioning
+
+**Date:** 2026-06-21 (v0.2.0 unreleased)
+
+**Decision:** Use conventional commits on feature branches and git-cliff (`cliff.toml`) to calculate the next semver version from commit history, generate the changelog, and automate releases.
+
+**Rationale:** `devx.ci.release` uses git-cliff to calculate the next version from conventional commits since the last tag. Merge commits on master have the format `GRM-N <conventional commit>`, so `cliff.toml` includes a `commit_preprocessors` entry that strips the `GRM-N ` prefix before parsing. Version bumping rules: `feat:` → minor, `fix:` → patch, `feat!:`/`BREAKING CHANGE` → minor (pre-1.0), `chore:`/`ci:`/`docs:` → no bump. This fully automates versioning and changelog generation — no manual version bumps are needed.
+
+**Source:** `CHANGELOG.md` (Unreleased — Added), `AGENTS.md` (Automated Release Pipeline, git-cliff Commit Preprocessing, Version Bumping Rules), `cliff.toml`
+
+---
+
+## ADR-004: Enforce Tests Pass Before Tagging a Release
+
+**Date:** 2026-06-21 (v0.2.2)
+
+**Decision:** The release workflow runs `make lint-ruff` and `make pytest-cov` before creating a release commit or tag. If lint or tests fail, the release aborts immediately — no commit, no tag.
+
+**Rationale:** This ensures every tagged release is healthy. A `--skip-tests` flag exists for emergency use only but is not recommended. This decision was made as a bug fix after identifying that releases could be tagged without verifying test health. Loops are prevented by `has_unreleased_changes` — after a release commit is tagged, the next run finds no unreleased changes and exits.
+
+**Source:** `CHANGELOG.md` (0.2.2 — Bug Fixes: "Enforce tests pass before tagging a release"), `AGENTS.md` (Automated Release Pipeline)
+
+---
+
+## ADR-005: Branch Protection + Auto-Merge Workflow
+
+**Date:** 2026-06-21 (v0.2.0 unreleased)
+
+**Decision:** Require branch protection on `master` (require pull request, require approval review, require status checks, block force pushes) and use an auto-merge workflow that programmatically enforces the APPROVE review check.
+
+**Rationale:** Branch protection is the primary gate — no direct pushes to master, at least 1 APPROVE review before merge, CI quality + molecule tests must pass, and no history rewriting. The auto-merge workflow (`devx.ci.auto_merge`) enforces the APPROVE review check programmatically as a defense-in-depth measure. When the `ready-to-merge` label is added, the workflow validates PR title format, checks for APPROVE review, waits for CI, and squash-merges with title `GRM-N <conventional commit message>`. The post-merge workflow then marks the Vikunja task as done. Branch protection is automatically configured by `devx.tools.configure_repo`.
+
+**Source:** `CHANGELOG.md` (Unreleased — Added: mandatory PR review step, auto_merge.py), `AGENTS.md` (Branch Protection, PR Workflow step 8)
+
+---
+
+## ADR-006: Path-Based CI Filtering for Molecule Tests
+
+**Date:** 2026-06-21 (v0.2.0 unreleased)
+
+**Decision:** The CI workflow includes a `detect-changes` job that checks whether any files under `ansible/` or `.ansible-lint` have changed. If no Ansible files are changed, molecule tests are skipped.
+
+**Rationale:** This prevents non-Ansible changes (e.g., Python scripts, workflow YAML, docs) from being blocked by molecule test infrastructure flakiness. Molecule tests are only relevant when Ansible files change. The `molecule-tests` job depends on both `quality` and `detect-changes`, and only runs if `ansible-changed == 'true'`. CI triggers only on `opened` and `synchronize` PR events (not `labeled`) to avoid redundant runs.
+
+**Source:** `AGENTS.md` (CI Path Filtering), `.gitea/workflows/ci.yml` (detect-changes job)
+
+---
+
+## ADR-007: Secrets via Temporary JSON Files (CWE-214)
+
+**Date:** Project inception
+
+**Decision:** Pass secrets (registration tokens, admin API tokens) to Ansible via temporary JSON files with `0600` permissions, never on the command line.
+
+**Rationale:** Passing secrets as command-line arguments (e.g., `--extra-vars '{"token": "..."}'`) makes them visible in the process list (`ps aux`), which is a known security weakness (CWE-214). The `RunnerManager._extra_vars_file()` context manager writes extra-vars to a temporary file via `tempfile.mkstemp()`, sets permissions to `0600`, passes the file to Ansible via `--extra-vars @tempfile`, and deletes the file in a `finally` block — even if an exception occurs. This ensures secrets are never visible in the process list.
+
+**Source:** `AGENTS.md` (Key Conventions), `src/gitea_runner_manager/runner_manager.py` (`_extra_vars_file` method)
+
+---
+
+## ADR-008: Smart CI — User-Facing vs Workflow-Only Change Classification
+
+**Date:** 2026-06-21 (v0.2.0 unreleased)
+
+**Decision:** Classify changed files into user-facing and workflow-only categories using `devx.ci.classify_changes`. Only user-facing changes trigger a release; workflow-only changes (CI, docs, tests, lint config) do not.
+
+**Rationale:** Not all changes require a new release. CI workflow updates, documentation improvements, and test additions should not produce a new version tag. The classification is config-driven via `[tool.devx.classify]` in `pyproject.toml`. The strategy is safe-by-default: any file NOT in the explicit workflow-only allowlist is treated as user-facing, preventing new file types from accidentally skipping releases. User-facing paths include `src/gitea_runner_manager/**` (except `__init__.py`) and `ansible/**`. Workflow-only paths include `.gitea/**`, `docs/**`, `tests/**`, `scripts/**`, and various config files.
+
+**Source:** `AGENTS.md` (Smart CI: User-Facing vs Workflow-Only Changes), `pyproject.toml` (`[tool.devx.classify]`)
+
+---
+
+## ADR-009: devx Package Separation
+
+**Date:** 2026-06-21 (v0.6.2)
+
+**Decision:** Separate CI/CD and development tooling into the `devx` package (installed from git), keeping the GRM tool itself self-contained in `src/gitea_runner_manager/`.
+
+**Rationale:** The GRM CLI tool must be self-contained — it never imports from devx. This ensures the installed package has no dependency on CI infrastructure. devx MAY import from `gitea_runner_manager` (one-way dependency), as it uses the tool's API clients, config, and i18n for CI automation. Cross-module imports within devx are allowed. This separation was formalised when scripts were migrated from the `scripts/` directory to the devx package in GRM-64.
+
+**Source:** `AGENTS.md` (Source Code Separation and devx Integration), `CHANGELOG.md` (0.6.2 — Refactor: "Migrate from scripts/ to devx package")
+
+---
+
+## ADR-010: Dynamic Runner Discovery for Molecule CI
+
+**Date:** 2026-06-21 (v0.5.0+)
+
+**Decision:** Molecule tests are distributed across available Gitea Actions runners dynamically via `devx.molecule.discover_runners`, which queries the Gitea API for runners at all levels (repo, org, instance) and generates a dynamic matrix.
+
+**Rationale:** Hardcoding the number of CI runners would require manual updates when runners are added or removed. Dynamic discovery auto-detects repo/org-level runners via the API. For instance-level runners (which may not be visible without admin scope), it falls back to the `MOLECULE_RUNNERS` repo variable, then to a default of 3. The workflow automatically scales the matrix to match available runners, distributing test pairs evenly.
+
+**Source:** `AGENTS.md` (Dynamic Runner Discovery), `.gitea/workflows/ci.yml` (discover-runners job)

docs/tech/development-setup.md

@@ -0,0 +1,240 @@
+# Development Setup
+
+## Project Structure
+
+```
+.
+├── src/gitea_runner_manager/      # Python CLI source
+│   ├── cli.py                     # Click commands
+│   ├── runner_manager.py          # Ansible orchestration + registry integration
+│   ├── executor.py                # Ansible subprocess execution
+│   ├── registry.py                # Local JSON runner registry
+│   ├── i18n.py                    # Translations (en, bg, de, ru, zh, pl)
+│   ├── exceptions.py              # Custom exceptions
+│   ├── logging_config.py          # Logging to ~/.local/state/grm/logs/
+│   ├── report.py                  # Operation report tracking
+│   ├── ui.py                      # Colorised console output
+│   └── translations.json          # Translation strings
+├── ansible/
+│   ├── roles/gitea-runner/        # Main Ansible role
+│   │   ├── defaults/main.yml      # Default variables
+│   │   ├── tasks/                 # Task files (13 files)
+│   │   ├── templates/             # Jinja2 templates (4 files)
+│   │   └── molecule/              # Test scenarios (7 scenarios)
+│   ├── install-runner.yml         # Install playbook
+│   ├── update-runner.yml          # Update playbook
+│   ├── start-runner.yml           # Start playbook
+│   ├── stop-runner.yml            # Stop playbook
+│   ├── enable-runner.yml          # Enable playbook
+│   ├── disable-runner.yml         # Disable playbook
+│   ├── status-runner.yml          # Status playbook
+│   └── remove-runner.yml          # Remove playbook
+├── tests/
+│   ├── unit/                      # Unit tests
+│   └── integration/               # Integration tests
+├── .gitea/workflows/              # CI/CD workflows
+├── docs/                          # Documentation (synced to wiki)
+├── Makefile                       # Build & test automation
+├── pyproject.toml                 # Python project metadata
+├── cliff.toml                     # git-cliff configuration
+└── .env.example                   # Environment variable template
+```
+
+## Prerequisites
+
+- **Python 3.12+** — Required. The Makefile verifies this before creating the venv. Use `pyenv` to manage Python versions if needed.
+- **Git** — For cloning the repository and checking out release tags.
+- **Docker** — Only needed for running Molecule tests locally (`make molecule`).
+- **Go** — Only needed if you want to install `checkmake` manually (alternatively, `make setup` installs it via `devx.tools.install_checkmake`).
+
+## Setup Development Environment
+
+### Step 1: Clone and checkout latest release
+
+```bash
+git clone https://git.oblachno.oblachno.fyi/oblachno-oss/grm.git
+cd grm
+git checkout $(git describe --tags --abbrev=0)  # Checkout latest stable release
+```
+
+> **Important:** Always checkout the latest release tag before running `make setup`. The `master` branch may contain unreleased changes that are not yet stable. To see all available releases, run `git tag --sort=-version:refname` or check the [releases page](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/releases).
+
+### Step 2: Ensure Python 3.12+ is available
+
+If you use pyenv:
+
+```bash
+pyenv install 3.12
+pyenv local 3.12
+```
+
+Verify your Python version:
+
+```bash
+python3 --version  # Must be 3.12 or higher
+```
+
+### Step 3: Run make setup
+
+```bash
+make setup
+source .venv/bin/activate
+```
+
+The `make setup` target performs the following:
+
+1. Verifies Python 3.12+ is installed
+2. Creates a virtualenv in `.venv`
+3. Installs/updates `pip`, `setuptools`, and `wheel`
+4. Creates `.env` from `.env.example` if not present
+5. Generates shell activation scripts (`activate.sh`, `activate.fish`, `activate.zsh`)
+6. Installs the `devx` package from the Oblachno PyPI registry (provides CI/CD tools)
+7. Installs `checkmake` via `devx.tools.install_checkmake` (Makefile linter)
+8. Installs CI/CD tools via `devx.tools.install_tools` (actionlint, git-cliff, act_runner, tea) to `~/.local/bin`
+9. Runs `python -m devx.tools.setup` to install Python dependencies, Ansible Galaxy collections, pre-commit hooks, and configure tea CLI login
+
+### Step 4: Configure Gitea credentials
+
+```bash
+cp .env.example .env
+# Edit .env:
+# GITEA_URL=https://git.example.com
+# GITEA_REGISTRATION_TOKEN=your-registration-token
+```
+
+`GITEA_REGISTRATION_TOKEN` is the runner registration token obtained from your Gitea instance (Admin → Actions → Runners → Create Registration Token).
+
+#### Admin API token (optional)
+
+Set `CI_GITEA_TOKEN` to enable informational API checks during integration test. This is **optional** — the test primarily verifies the runner by checking:
+
+1. **`.runner` registration file** exists and contains valid JSON (proves successful registration)
+2. **Systemd user service** is active (proves daemon is polling for jobs)
+
+API checks, if enabled, are purely informational and do not affect pass/fail.
+
+### Step 5: Verify the setup
+
+```bash
+grm --version          # Should print the version
+make lint-all          # Should pass with no errors
+make pytest-cov        # Should pass with 100% coverage
+```
+
+## Shell activation scripts
+
+`make setup` generates convenience activation scripts for different shells:
+
+```bash
+source activate.sh     # bash
+source activate.fish   # fish
+source activate.zsh    # zsh
+```
+
+These scripts activate the `.venv` virtualenv from the project root.
+
+## Running Linters
+
+```bash
+make lint          # Python (ruff + format check + pyright + bandit)
+make lint-bandit   # Security scan only
+make ansible-lint  # Ansible
+make makefile-lint # Makefile
+make workflow-lint # Gitea Actions workflows (actionlint)
+```
+
+The full lint target (`make lint-all`) runs all of the above:
+
+```bash
+make lint-all       # ruff + pyright + bandit + ansible-lint + checkmake + actionlint
+```
+
+Individual lint targets from the `Makefile`:
+
+| Target | Description |
+|--------|-------------|
+| `lint-ruff` | `ruff check src/ tests/` |
+| `lint-format` | `ruff format --check src/ tests/` |
+| `typecheck` | `pyright` |
+| `lint-bandit` | `bandit -r src/` |
+| `lint-deps` | `pip-audit` — checks dependencies for known vulnerabilities |
+| `ansible-lint` | `ansible-lint ansible/` |
+| `makefile-lint` | `checkmake Makefile` |
+| `lint` | ruff + format check + pyright + bandit |
+| `lint-all` | lint + ansible-lint + makefile-lint + workflow-lint |
+
+## Running Tests
+
+### Unit tests
+
+```bash
+make test-unit      # Without coverage
+make pytest-cov     # With 100% coverage enforcement
+```
+
+The coverage requirement is `--cov-fail-under=100` — 100% test coverage is required for all code in `src/gitea_runner_manager/`.
+
+### Integration tests
+
+```bash
+make test-integration
+```
+
+Tests the full CLI lifecycle commands end-to-end (mocked executor boundary).
+
+### Molecule tests
+
+```bash
+make molecule      # Quick: all 6 scenarios on Ubuntu 22.04
+make molecule-all  # Full: all 6 scenarios on all 4 supported OSes
+```
+
+Requires Docker to be installed and running on your machine. Molecule creates Docker containers as test hosts, applies the Ansible role, and verifies the results.
+
+### Full test suite
+
+```bash
+make test-all      # pytest-cov + molecule
+```
+
+## Workflow verification
+
+GRM includes Gitea Actions workflow files in `.gitea/workflows/`. These are verified with two tools:
+
+```bash
+make workflow-lint     # Static lint via actionlint
+make workflow-dryrun   # Dry-run via act_runner exec --dryrun
+make workflow-check    # Both of the above
+```
+
+The pre-commit hook runs actionlint automatically when workflow files change.
+
+## Pre-commit hooks
+
+`make setup` installs pre-commit hooks that run:
+
+- **pre-commit**: `ruff check`, `ruff format --check`, conventional commit message validation
+- **pre-push**: `make pytest-cov` (ensures tests pass before pushing)
+
+## Make targets reference
+
+| Target | Description |
+|--------|-------------|
+| `make setup` | Full setup: venv, deps, hooks, CI tools |
+| `make setup-ci` | Lean setup for CI jobs (pytest + lint, no Ansible collections) |
+| `make setup-quality` | Setup for the quality CI job (lint + test deps) |
+| `make setup-molecule` | Full setup for molecule testing |
+| `make setup-release` | Setup for release jobs (git-cliff, tea, lint tools) |
+| `make install-tools` | Install actionlint, git-cliff, act_runner, tea to `~/.local/bin` |
+| `make install-devx` | Install the devx package from the Oblachno PyPI registry |
+| `make lint-all` | ruff + pyright + bandit + ansible-lint + checkmake + actionlint |
+| `make pytest-cov` | Unit tests with 100% coverage enforcement |
+| `make test-unit` | Unit tests without coverage |
+| `make test-integration` | Integration tests |
+| `make molecule` | All 6 Molecule scenarios on Ubuntu 22.04 |
+| `make molecule-all` | All 6 scenarios on all 4 supported OSes |
+| `make test-all` | pytest-cov + molecule |
+| `make workflow-lint` | Static lint of workflow YAML (actionlint) |
+| `make workflow-dryrun` | Dry-run all workflows in Docker |
+| `make workflow-check` | workflow-lint + workflow-dryrun |
+| `make clean` | Remove `__pycache__`, `.pyc`, `.coverage`, `htmlcov/`, `.molecule/` |