Update badges [skip ci]

2026-08-09 22:51:28 +00:00
209 changed files with 240 additions and 19516 deletions
@@ -1,10 +0,0 @@
-# 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
@@ -0,0 +1,20 @@
+<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>
@@ -0,0 +1,20 @@
+<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>
@@ -0,0 +1,20 @@
+<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>
@@ -0,0 +1,20 @@
+<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>
@@ -0,0 +1,20 @@
+<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>
@@ -0,0 +1,20 @@
+<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>
@@ -1,4 +0,0 @@
-[checkmake]
-# Disable the phony rule which flags common .PHONY placement patterns
-# as it produces false positives for standard Makefile layouts
-disable=maxbodylength
@@ -1,185 +0,0 @@
---
-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 & Virtual Environment
-
-The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first.
-
-All Python tools run inside `.venv`. `make` targets handle activation
-automatically — always use `make <target>`, never raw `pytest` or `ruff`
-commands. If `.venv` doesn't exist, run `make setup` first.
-
-## 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/grm/__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
@@ -1,155 +0,0 @@
---
-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 & Virtual Environment
-
-The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first.
-
-All Python tools run inside `.venv`. `make` targets handle activation
-automatically — always use `make <target>`, never raw `pytest` or `ruff`
-commands. If `.venv` doesn't exist, run `make setup` 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
-.venv/bin/python -m devx.tools.check_pyproject_deps
-.venv/bin/python -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
@@ -1,138 +0,0 @@
---
-name: doc-sync-specialist
-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 & Virtual Environment
-
-The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first.
-
-All Python tools run inside `.venv`. `make` targets handle activation
-automatically — always use `make <target>`, never raw `pytest` or `ruff`
-commands. If `.venv` doesn't exist, run `make setup` 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
-.venv/bin/python -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
-.venv/bin/python -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
-.venv/bin/python -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
@@ -1,158 +0,0 @@
---
-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 & Virtual Environment
-
-The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first.
-
-All Python tools run inside `.venv`. `make` targets handle activation
-automatically — always use `make <target>`, never raw `pytest` or `ruff`
-commands. If `.venv` doesn't exist, run `make setup` 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
@@ -1,154 +0,0 @@
---
-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 & Virtual Environment
-
-The grm repo is at `/home/emo/dev/ideas/oblachno/grm`. Always `cd` there first.
-
-All Python tools run inside `.venv`. `make` targets handle activation
-automatically — always use `make <target>`, never raw `pytest` or `ruff`
-commands. If `.venv` doesn't exist, run `make setup` 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
@@ -1,38 +0,0 @@
-# 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`)
@@ -1,92 +0,0 @@
-# testing-and-debugging
-
-Make targets for testing, debugging, and CI investigation. **Use these
-instead of raw `pytest`, `ruff`, or `molecule` commands.**
-
-## Why Make Targets
-
-Make targets encapsulate the correct venv activation, PYTHONPATH, env
-vars, and flags. Running raw commands bypasses venv activation and
-produces false failures (missing dependencies, wrong Python version).
-
-## Unit Tests
-
-| Task | Command | Notes |
-|------|---------|-------|
-| Run all unit tests | `make test-unit` | Fast, no coverage |
-| Run with coverage | `make pytest-cov` | **Required before push** — enforces 100% |
-| Run single test | `make pytest-cov TEST=tests/test_foo.py::test_bar` | |
-
-## Linting
-
-| Task | Command | Notes |
-|------|---------|-------|
-| Full lint | `make lint-all` | ruff + pyright + bandit + ansible-lint + checkmake + actionlint |
-| Ruff only | `make lint-ruff` | |
-| Type check | `make typecheck` | pyright |
-| Bandit | `make lint-bandit` | Security linter |
-| Workflow lint | `make workflow-check` | actionlint + act_runner dry-run |
-
-## Molecule Tests
-
-| Task | Command | Notes |
-|------|---------|-------|
-| All scenarios | `make molecule` | All 6 scenarios on Ubuntu 22.04 |
-| All platforms | `make molecule-all` | All 6 scenarios on all 4 OSes |
-| Parallel | `make molecule-all-parallel` | MOLECULE_JOBS=4 |
-
-## Pre-Push Verification
-
-**Before pushing any branch:**
-
-```bash
-make pre-push
-```
-
-This runs `lint-all` + `pytest-cov`. The pre-push git hook only
-validates the Vikunja task exists — it does NOT run tests. You must
-run `make pre-push` manually.
-
-## CI Failure Investigation
-
-When investigating a CI failure:
-
-1. **Fetch logs via MCP** — use `mcp_call_tool` with gitea server,
-   `actions_run_read` method, `download_job_log` tool
-2. **Reproduce locally** — use `make pytest-cov` or `make lint-ci`
-   depending on which CI job failed
-3. **Never run raw pytest** — always use the make target
-
-## Virtual Environment
-
-All commands run inside `.venv`. `make` targets handle activation
-automatically. For raw commands (rare), activate first:
-
-```bash
-source activate.sh       # bash/zsh
-source activate.fish     # fish
-source activate.zsh      # zsh
-```
-
-If `.venv` doesn't exist, run `make setup` first.
-
-## Common Pitfalls
-
-### Coverage Verification Before Push
-
-**Always run `make pytest-cov` before pushing** — CI enforces 100%
-coverage and will fail the PR if any lines are uncovered. This is the
-most common cause of CI validate job failures after code changes. The
-pre-push git hook only validates Vikunja task existence, not tests.
-
-### API Response Type Checking
-
-Never use `is True`/`is False` identity checks on API response values.
-Many APIs return boolean values as strings (`"true"`/`"false"`). Use
-string comparison or truthy/falsy helpers instead.
-
-### Time Mocking in Tests
-
-Always mock `time.sleep` and `time.monotonic` in unit tests using
-`@patch` decorators. Real sleep calls make tests slow and exceed test
-speed limits.
@@ -1,74 +0,0 @@
-# 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_API_TOKEN=your-admin-api-token
-# Legacy CI_GITEA_TOKEN is also accepted.
-
-# 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=your-gitea-username
-
-# Role-based Gitea API tokens (devx 0.40.0+)
-# DEVELOPER_GITEA_API_TOKEN is used by local `grm trigger-workflow` and `make create-pr`.
-# CI_GITEA_API_TOKEN is used by CI workflows (and accepted as a fallback for local tools).
-# REVIEWER_GITEA_API_TOKEN is used by CI to post APPROVE reviews; it must belong to a
-# different user than the PR author.
-# Legacy CI_GITEA_TOKEN and REVIEW_GITEA_TOKEN are accepted as fallbacks.
-# DEVELOPER_GITEA_API_TOKEN=your-developer-token
-# CI_GITEA_API_TOKEN=your-ci-token
-# REVIEWER_GITEA_API_TOKEN=your-reviewer-token
-
-# 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/grm/__init__.py
@@ -1,9 +0,0 @@
-# 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
@@ -1,314 +0,0 @@
-name: CI
-
-on:
-  pull_request:
-    types: [opened, synchronize]
-  workflow_dispatch:
-
-env:
-  PIP_BREAK_SYSTEM_PACKAGES: "1"
-  PYTHONPATH: src
-  CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-  CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
-
-jobs:
-  # Single validation job that merges: quality, detect-changes,
-  # release-dry-run, pre-merge-check, pr-review, and discover-runners.
-  # Uses ci-full image (has git-cliff for release-dry-run).
-  # Saves ~5x checkout+setup overhead vs 6 separate jobs.
-  validate:
-    runs-on: docker
-    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-full:latest
-    timeout-minutes: 15
-    defaults:
-      run:
-        shell: bash
-    outputs:
-      ansible-changed: ${{ steps.detect.outputs.ansible-changed }}
-      user-facing-changed: ${{ steps.detect.outputs.user-facing-changed }}
-      runner-count: ${{ steps.discover-runners.outputs.runner-count }}
-      runner-indices: ${{ steps.discover-runners.outputs.runner-indices }}
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Set up environment
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
-        run: make setup-image EXTRAS=ci,lint
-      # --- quality steps ---
-      - 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 gate (coverage + stale refs + lint + version refs + prose)
-        env:
-          DEVX_DOC_COVERAGE_STRICT: "1"
-          DEVX_DOC_VERSIONS_PKG: grm
-          DEVX_VALE_LEVEL: warning
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          export PATH="$HOME/.local/bin:$PATH"
-          make devx-docs-check
-      - name: Translation completeness check
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          python3 -m devx.ci.check_translations --translations src/grm/translations.json
-      - name: Check unit test speed
-        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
-      # --- detect-changes step ---
-      - name: Detect changed paths
-        id: detect
-        env:
-          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
-      # --- validate-pr + pr-review steps (PR only) ---
-      - name: Validate auto-merge preconditions
-        if: github.event_name == 'pull_request'
-        env:
-          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 }}
-        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"
-      - name: Run automated PR review
-        if: github.event_name == 'pull_request'
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          set -euo pipefail
-          python3 -m devx.ci.pr_review \
-            "${{ github.event.number }}" \
-            "${{ github.repository }}"
-      # --- release-dry-run step (conditional) ---
-      - name: Release dry-run validation
-        if: steps.detect.outputs.user-facing-changed == 'true'
-        env:
-          DEVX_VERSION_FILE: src/grm/__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
-      # --- discover-runners step (conditional on ansible-changed) ---
-      - name: Discover available molecule runners
-        id: discover-runners
-        if: steps.detect.outputs.ansible-changed == 'true'
-        env:
-          MOLECULE_RUNNERS: ${{ vars.MOLECULE_RUNNERS }}
-        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
-      - name: Notify on failure
-        if: failure()
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-        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 "ci/validate" \
-            --commit "${{ github.sha }}"
-
-  molecule-tests:
-    needs: [validate]
-    if: needs.validate.outputs.ansible-changed == 'true'
-    runs-on: docker
-    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-full:latest
-    timeout-minutes: 15
-    strategy:
-      fail-fast: false
-      max-parallel: 4
-      matrix:
-        runner-index: [1, 2, 3, 4]
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up environment
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_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: 4
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          python3 -m devx.molecule.distribute_molecule \
-            --runner-index "$RUNNER_INDEX" \
-            --max-runners "$MAX_RUNNERS" \
-            --github-env
-      - name: Prune stale Docker data
-        id: prune
-        if: env.SKIP != 'true'
-        run: |
-          docker system prune -af --volumes 2>/dev/null || true
-          disk_pct=$(df -P / | awk 'NR==2 {gsub(/%/, "", $5); print $5}')
-          echo "Disk usage after prune: ${disk_pct}%"
-          if [ "$disk_pct" -ge 85 ]; then
-            echo "should-run=false" >> "$GITHUB_OUTPUT"
-            echo "::warning::Disk usage at ${disk_pct}% after prune — skipping molecule tests to avoid ENOSPC failures"
-          else
-            echo "should-run=true" >> "$GITHUB_OUTPUT"
-          fi
-      - name: Run molecule tests
-        if: env.SKIP != 'true' && steps.prune.outputs.should-run != 'false'
-        shell: bash
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
-          DOCKER_HOST: unix:///var/run/docker.sock
-          ANSIBLE_INJECT_INVOCATION: "1"
-        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
-          _TOKEN="$CI_GITEA_API_TOKEN"; [ -z "$_TOKEN" ] && _TOKEN="$CI_GITEA_TOKEN"
-          [ -z "$_TOKEN" ] && { echo "Gitea API token not set — skipping Docker login"; exit 0; }
-          echo "$_TOKEN" | docker login git.oblachno.oblachno.fyi -u "$CI_GITEA_USERNAME" --password-stdin
-          # Run each molecule test pair sequentially.
-          # Pairs are 4-part: scenario|platform_name|platform_image|platform_command
-          # Spaces in platform_command are encoded as __SPACE__.
-          role_dir="ansible/roles/gitea_runner"
-          # shellcheck disable=SC2086 # intentional word splitting for pair list
-          for pair in $TEST_PAIRS; do
-            IFS='|' read -r scenario platform_name platform_image platform_command <<< "$pair"
-            platform_command="${platform_command//__SPACE__/ }"
-            export MOLECULE_PLATFORM_NAME="$platform_name"
-            export MOLECULE_PLATFORM_IMAGE="$platform_image"
-            if [ -n "$platform_command" ]; then
-              export MOLECULE_PLATFORM_COMMAND="$platform_command"
-            else
-              unset MOLECULE_PLATFORM_COMMAND
-            fi
-            export ANSIBLE_ALLOW_BROKEN_CONDITIONALS=true
-            echo "--- Running: $scenario on $platform_name ---"
-            pushd "$role_dir" >/dev/null
-            if [ "$scenario" = "default" ]; then
-              molecule test || {
-                echo "FAILED: $pair — running molecule destroy"
-                molecule destroy 2>/dev/null || true
-                popd >/dev/null
-                exit 1
-              }
-            else
-              molecule test -s "$scenario" || {
-                echo "FAILED: $pair — running molecule destroy"
-                molecule destroy -s "$scenario" 2>/dev/null || true
-                popd >/dev/null
-                exit 1
-              }
-            fi
-            popd >/dev/null
-            echo "PASSED: $pair"
-            docker system prune -af --volumes 2>/dev/null || true
-          done
-          echo "All molecule tests passed."
-
-  auto-merge:
-    # Auto-merge runs after validate passes. molecule-tests is NOT in needs
-    # because Gitea Actions skips dependent jobs of skipped jobs without
-    # evaluating if: conditions — having molecule-tests in needs would
-    # cascade the skip to auto-merge when ansible-changed=false.
-    needs: [validate]
-    if: >-
-      always() &&
-      github.event_name == 'pull_request' &&
-      needs.validate.result == 'success'
-    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_API_TOKEN }}
-      - name: Set up environment
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
-        run: make setup-image EXTRAS=ci
-      - name: Post approval review
-        env:
-          REVIEWER_GITEA_API_TOKEN: ${{ secrets.REVIEWER_GITEA_API_TOKEN }}
-          PR_NUMBER: ${{ github.event.number }}
-          REPOSITORY: ${{ github.repository }}
-        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 (validate, molecule-tests)."
-      - name: Squash merge with task ID
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_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 }}
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          python3 -m devx.ci.auto_merge \
-            "$HEAD_REF" \
-            "$PR_TITLE" \
-            "$REPOSITORY" \
-            "$PR_NUMBER"
@@ -1,191 +0,0 @@
-name: Post-merge
-
-# Runs on every push to master (after CI workflow merges a PR).
-# Consolidated into 2 jobs (from 7) to reduce runner overhead:
-#   detect-and-configure ──→ release-and-maintain
-#
-# Job 1: detect release commit, validate commit msg, configure repo
-#        (branch protection, labels).
-# Job 2: release + publish + sync-wiki + vikunja + badges.
-#        Individual steps are conditional on job 1 outputs.
-#
-# The badges step always runs (even on release commits) so version
-# badge picks up the new __version__. It runs last so it sees the
-# new version if release created one.
-#
-# When release creates a "release: vX.Y.Z" commit and tag, the publish
-# step builds and publishes the package to the Gitea PyPI registry.
-# The release commit's post-merge run still updates badges. Other
-# steps (sync-wiki, vikunja) skip on release commits.
-
-on:
-  push:
-    branches: [master]
-  workflow_dispatch:
-
-concurrency:
-  group: post-merge-${{ github.ref }}
-  cancel-in-progress: true
-
-env:
-  PIP_BREAK_SYSTEM_PACKAGES: "1"
-  PYTHONPATH: src
-  CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-  CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
-
-jobs:
-  detect-and-configure:
-    runs-on: docker
-    container: git.oblachno.oblachno.fyi/oblachno-oss/runner-images/ci-base:latest
-    timeout-minutes: 10
-    defaults:
-      run:
-        shell: bash
-    outputs:
-      is-release: ${{ steps.check.outputs.is-release }}
-      is-automated: ${{ steps.check.outputs.is-automated }}
-      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_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-          CI_GITEA_USERNAME: ${{ vars.CI_GITEA_USERNAME }}
-        run: make setup-image EXTRAS=ci
-      - name: Ensure branch protection and labels
-        env:
-          DEVX_REPO_NAME: grm
-          DEVX_REPO_OWNER: oblachno-oss
-          DEVX_STATUS_CHECKS: "CI / validate (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: Check if this is a release commit
-        id: check
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          python3 -m devx.ci.detect_release_commit
-      - name: Validate latest commit message
-        if: steps.check.outputs.is-automated == 'false'
-        env:
-          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
-      - name: Detect changed paths
-        id: detect
-        if: steps.check.outputs.is-release == 'false'
-        env:
-          DEVX_TASK_PREFIX: GRM
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          python3 -m devx.ci.classify_changes \
-            --base "HEAD~1" \
-            --head "HEAD" \
-            --github-output
-      - name: Notify on failure
-        if: failure()
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-        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/detect-and-configure" \
-            --commit "${{ github.sha }}"
-
-  release-and-maintain:
-    needs: [detect-and-configure]
-    if: always() && needs.detect-and-configure.result == 'success'
-    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 }}
-    defaults:
-      run:
-        shell: bash
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          ref: master
-          token: ${{ secrets.CI_GITEA_API_TOKEN }}
-      - name: Set up environment
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_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"
-      # --- release + publish (only if not a release commit) ---
-      - name: Run release
-        id: release-tag
-        if: needs.detect-and-configure.outputs.is-release == 'false' && needs.detect-and-configure.outputs.user-facing-changed == 'true'
-        env:
-          DEVX_VERSION_FILE: src/grm/__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: Build and publish release
-        if: steps.release-tag.outputs.tag != ''
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          export PATH="$HOME/.local/bin:$PATH"
-          git fetch --tags
-          git checkout "${{ steps.release-tag.outputs.tag }}"
-          python3 -m devx.ci.publish "${{ steps.release-tag.outputs.tag }}" "${{ github.repository }}" --auto-login
-      # --- sync-wiki + vikunja (skip on automated/release commits) ---
-      - name: Sync documentation to wiki
-        if: needs.detect-and-configure.outputs.is-automated == 'false'
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          python3 -m devx.ci.sync_wiki --repo "${{ github.repository }}" --verify
-      - name: Update Vikunja task
-        if: needs.detect-and-configure.outputs.is-automated == 'false'
-        env:
-          VIKUNJA_TOKEN: ${{ secrets.VIKUNJA_TOKEN }}
-          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 }}"
-      # --- badges (always run — even on release commits) ---
-      - name: Generate and push badges
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-          PRE_COMMIT_ALLOW_NO_CONFIG: "1"
-        run: |
-          . .venv/bin/activate 2>/dev/null || true
-          export PATH="$HOME/.local/bin:$PATH"
-          # Fetch latest master to pick up any release commit that was pushed
-          git fetch origin master
-          git reset --hard origin/master
-          python3 -m devx.ci.push_badges
-      - name: Notify on failure
-        if: failure()
-        env:
-          CI_GITEA_API_TOKEN: ${{ secrets.CI_GITEA_API_TOKEN }}
-        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-and-maintain" \
-            --commit "${{ github.sha }}"
@@ -1,43 +0,0 @@
-# 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
@@ -1,138 +0,0 @@
-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: checkmake
-        name: checkmake Makefile linter
-        entry: make checkmake
-        language: system
-        files: ^Makefile$
-        pass_filenames: false
-        stages: [pre-commit]
-
-      - id: check-test-speed
-        name: unit test speed check
-        entry: .venv/bin/python -m devx.tools.check_test_speed --max-seconds 4 --max-single-seconds 0.5
-        language: system
-        types: [python]
-        pass_filenames: false
-        stages: [pre-commit]
-
-      - id: check-translations
-        name: translation completeness check
-        entry: env PYTHONPATH=src .venv/bin/python -m devx.ci.check_translations --translations src/grm/translations.json
-        language: system
-        files: ^src/grm/translations\.json$
-        pass_filenames: false
-        stages: [pre-commit]
-
-      - id: docs-check
-        name: documentation gate (coverage + stale refs + lint + version refs + prose)
-        entry: bash -c 'PYTHONPATH=src DEVX_DOC_COVERAGE_STRICT=1 DEVX_DOC_VERSIONS_PKG=grm DEVX_VALE_LEVEL=warning make devx-docs-check'
-        language: system
-        pass_filenames: false
-        always_run: true
-        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]
-
-      - id: check-ansible-no-log
-        name: ansible no_log on secret tasks
-        entry: make check-ansible-no-log
-        language: system
-        files: ^ansible/.*\.(yml|yaml)$
-        pass_filenames: false
-        stages: [pre-commit]
-
-      - id: check-ansible-no-state-absent-on-db
-        name: no state absent on DB paths
-        entry: make check-ansible-no-state-absent-on-db
-        language: system
-        files: ^ansible/.*\.(yml|yaml)$
-        pass_filenames: false
-        stages: [pre-commit]
-
-      - id: check-ansible-patterns
-        name: ansible failure-masking patterns
-        entry: make check-ansible-patterns
-        language: system
-        files: ^ansible/.*\.(yml|yaml)$
-        pass_filenames: false
-        stages: [pre-commit]
-
-      - id: check-jinja-expr
-        name: jinja2 expression validation
-        entry: make check-jinja-expr
-        language: system
-        files: ^ansible/.*\.(yml|yaml|j2)$
-        pass_filenames: false
-        stages: [pre-commit]
-
-      - id: check-ansible-set-fact-to-json
-        name: set_fact to_json misuse check
-        entry: make check-ansible-set-fact-to-json
-        language: system
-        files: ^ansible/.*\.(yml|yaml)$
-        pass_filenames: false
-        stages: [pre-commit]
@@ -1 +0,0 @@
-3.12
@@ -1,51 +0,0 @@
-# Vale configuration for grm documentation
-# https://vale.sh/docs/
-
-StylesPath = .vale/styles
-
-# Packages are downloaded via `vale sync`
-Packages = write-good, Google, Readability
-
-# Minimum alert level to display (suggestion, warning, error)
-MinAlertLevel = warning
-
-# Project vocabulary — terms not flagged as spelling errors
-Vocab = grm
-
-[*.{md}]
-# Enable style guides
-BasedOnStyles = Vale, write-good, Google, Readability, devx
-
-# Google style — relax rules too strict for technical docs
-Google.Contractions = NO
-Google.WordList = NO
-Google.Acronyms = NO
-Google.We = NO
-Google.Will = NO
-Google.Colons = NO
-Google.Headings = NO
-Google.EmDash = NO
-Google.Units = NO
-Google.Latin = NO
-Google.OptionalPlurals = NO
-
-# write-good — relax rules too strict for technical writing
-write-good.E-Prime = NO
-write-good.So = NO
-write-good.ThereIs = NO
-write-good.TooWordy = NO
-write-good.Passive = NO
-
-# Vale defaults — spelling catches too many technical terms
-Vale.Terms = NO
-Vale.Repetition = NO
-Vale.Spelling = NO
-
-# Readability — technical docs are naturally complex, downgrade to suggestions
-Readability.FleschReadingEase = suggestion
-Readability.FleschKincaid = suggestion
-Readability.AutomatedReadability = suggestion
-Readability.ColemanLiau = suggestion
-Readability.LIX = suggestion
-Readability.GunningFog = suggestion
-Readability.SMOG = suggestion
@@ -1,9 +0,0 @@
-extends: existence
-message: "Use 'AM' or 'PM' (preceded by a space)."
-link: "https://developers.google.com/style/word-list"
-level: error
-nonword: true
-tokens:
-  - '\d{1,2}[AP]M\b'
-  - '\d{1,2} ?[ap]m\b'
-  - '\d{1,2} ?[aApP]\.[mM]\.'
@@ -1,64 +0,0 @@
-extends: conditional
-message: "Spell out '%s', if it's unfamiliar to the audience."
-link: 'https://developers.google.com/style/abbreviations'
-level: suggestion
-ignorecase: false
-# Ensures that the existence of 'first' implies the existence of 'second'.
-first: '\b([A-Z]{3,5})\b'
-second: '(?:\b[A-Z][a-z]+ )+\(([A-Z]{3,5})\)'
-# ... with the exception of these:
-exceptions:
-  - API
-  - ASP
-  - CLI
-  - CPU
-  - CSS
-  - CSV
-  - DEBUG
-  - DOM
-  - DPI
-  - FAQ
-  - GCC
-  - GDB
-  - GET
-  - GPU
-  - GTK
-  - GUI
-  - HTML
-  - HTTP
-  - HTTPS
-  - IDE
-  - JAR
-  - JSON
-  - JSX
-  - LESS
-  - LLDB
-  - NET
-  - NOTE
-  - NVDA
-  - OSS
-  - PATH
-  - PDF
-  - PHP
-  - POST
-  - RAM
-  - REPL
-  - RSA
-  - SCM
-  - SCSS
-  - SDK
-  - SQL
-  - SSH
-  - SSL
-  - SVG
-  - TBD
-  - TCP
-  - TODO
-  - URI
-  - URL
-  - USB
-  - UTF
-  - XML
-  - XSS
-  - YAML
-  - ZIP
@@ -1,12 +0,0 @@
-extends: existence
-message: "Don't attribute human qualities to software or hardware ('%s')."
-link: https://developers.google.com/style/anthropomorphism
-level: suggestion
-ignorecase: true
-# Limited to the two verbs the guide itself names. Broader lists (wants, knows,
-# thinks) can't tell a software subject from a human one: on a 950-file corpus
-# they produced 8 false positives ('the customer wants', 'your audience knows')
-# for every 2 real ones.
-tokens:
-  - sees
-  - tells
@@ -1,13 +0,0 @@
-extends: existence
-message: "'%s' should be in lowercase."
-link: 'https://developers.google.com/style/colons'
-level: warning
-scope: sentence
-# The match is the word itself, not ': X', and `nonword` is off. Both are
-# required for a project Vocab to work: Vale compares accept.txt entries
-# against the matched text, and `nonword: true` opts out of that entirely.
-# So a proper noun after a colon can be exempted by adding it to accept.txt.
-# The guide's other exemption, notice labels, is handled by the lookbehinds;
-# headings are already excluded by `scope: sentence`. See issue #20.
-tokens:
-  - '(?<!Note: )(?<!Caution: )(?<!Warning: )(?<!Success: )(?<=:\s)[A-Z]\w+'
@@ -1,30 +0,0 @@
-extends: substitution
-message: "Use '%s' instead of '%s'."
-link: 'https://developers.google.com/style/contractions'
-level: suggestion
-ignorecase: true
-action:
-  name: replace
-swap:
-  are not: aren't
-  cannot: can't
-  could not: couldn't
-  did not: didn't
-  do not: don't
-  does not: doesn't
-  has not: hasn't
-  have not: haven't
-  how is: how's
-  is not: isn't
-  it is: it's
-  should not: shouldn't
-  that is: that's
-  they are: they're
-  was not: wasn't
-  we are: we're
-  we have: we've
-  were not: weren't
-  what is: what's
-  when is: when's
-  where is: where's
-  will not: won't
@@ -1,9 +0,0 @@
-extends: existence
-message: "Use 'July 31, 2016' format, not '%s'."
-link: 'https://developers.google.com/style/dates-times'
-ignorecase: true
-level: error
-nonword: true
-tokens:
-  - '\d{1,2}(?:\.|/)\d{1,2}(?:\.|/)\d{4}'
-  - '\d{1,2} (?:Jan(?:uary)?|Feb(?:ruary)?|Mar(?:ch)?|Apr(?:il)?|May|Jun(?:e)?|Jul(?:y)?|Aug(?:ust)?|Sep(?:tember)?|Oct(?:ober)?|Nov(?:ember)?|Dec(?:ember)?) \d{4}'
@@ -1,9 +0,0 @@
-extends: existence
-message: "In general, don't use an ellipsis."
-link: 'https://developers.google.com/style/ellipses'
-nonword: true
-level: warning
-action:
-  name: remove
-tokens:
-  - '\.\.\.'
@@ -1,13 +0,0 @@
-extends: existence
-message: "Don't put a space before or after a dash."
-link: "https://developers.google.com/style/dashes"
-nonword: true
-level: error
-action:
-  name: edit
-  params:
-    - trim
-    - " "
-tokens:
-  - '\s[—–]\s'
-
@@ -1,14 +0,0 @@
-extends: existence
-message: "Avoid the unverifiable claim '%s'."
-link: https://developers.google.com/style/excessive-claims
-level: suggestion
-ignorecase: true
-# The guide also names 'never', 'always', and 'ensure', but in technical writing
-# those are usually legitimate instructions ('never commit secrets') rather than
-# product claims: they accounted for 125 of 142 hits on a 950-file corpus.
-# 'best practices' is a fixed term, not a superlative.
-tokens:
-  - 'best(?! practices?)'
-  - simplest
-  - fastest
-  - guarantees?
@@ -1,12 +0,0 @@
-extends: existence
-message: "Don't use exclamation points in text."
-link: "https://developers.google.com/style/exclamation-points"
-nonword: true
-level: error
-action:
-  name: edit
-  params:
-    - trim_right
-    - "!"
-tokens:
-  - '\w+!(?:\s|$)'
@@ -1,15 +0,0 @@
-extends: existence
-message: "Avoid first-person pronouns such as '%s'."
-link: 'https://developers.google.com/style/pronouns#personal-pronouns'
-ignorecase: true
-level: warning
-# The 'I' tokens use lookaround rather than consuming the surrounding
-# whitespace. Matching ' I ' made the alert span cover both spaces, which shows
-# up as a too-wide underline in editors, and read as "such as ' I '". Dropping
-# `nonword` also lets a project Vocab apply, which it can't when set. See PR #50.
-tokens:
-  - '(?<=^|\s)I(?=[\s,])'
-  - "\\bI'm\\b"
-  - \bme\b
-  - \bmy\b
-  - \bmine\b
@@ -1,9 +0,0 @@
-extends: existence
-message: "Don't use '%s' as a gender-neutral pronoun."
-link: 'https://developers.google.com/style/pronouns#gender-neutral-pronouns'
-level: error
-ignorecase: true
-tokens:
-  - he/she
-  - s/he
-  - \(s\)he
@@ -1,43 +0,0 @@
-extends: substitution
-message: "Consider using '%s' instead of '%s'."
-ignorecase: true
-link: "https://developers.google.com/style/inclusive-documentation"
-level: error
-action:
-  name: replace
-swap:
-  (?:alumna|alumnus): graduate
-  (?:alumnae|alumni): graduates
-  air(?:m[ae]n|wom[ae]n): pilot(s)
-  anchor(?:m[ae]n|wom[ae]n): anchor(s)
-  authoress: author
-  camera(?:m[ae]n|wom[ae]n): camera operator(s)
-  door(?:m[ae]|wom[ae]n): concierge(s)
-  draft(?:m[ae]n|wom[ae]n): drafter(s)
-  fire(?:m[ae]n|wom[ae]n): firefighter(s)
-  fisher(?:m[ae]n|wom[ae]n): fisher(s)
-  fresh(?:m[ae]n|wom[ae]n): first-year student(s)
-  garbage(?:m[ae]n|wom[ae]n): waste collector(s)
-  lady lawyer: lawyer
-  ladylike: courteous
-  mail(?:m[ae]n|wom[ae]n): mail carriers
-  man and wife: husband and wife
-  man enough: strong enough
-  mankind: human kind|humanity
-  manmade: manufactured
-  manpower: personnel
-  middle(?:m[ae]n|wom[ae]n): intermediary
-  news(?:m[ae]n|wom[ae]n): journalist(s)
-  ombuds(?:man|woman): ombuds
-  oneupmanship: upstaging
-  poetess: poet
-  police(?:m[ae]n|wom[ae]n): police officer(s)
-  repair(?:m[ae]n|wom[ae]n): technician(s)
-  sales(?:m[ae]n|wom[ae]n): salesperson or sales people
-  service(?:m[ae]n|wom[ae]n): soldier(s)
-  steward(?:ess)?: flight attendant
-  tribes(?:m[ae]n|wom[ae]n): tribe member(s)
-  waitress: waiter
-  woman doctor: doctor
-  woman scientist[s]?: scientist(s)
-  work(?:m[ae]n|wom[ae]n): worker(s)
@@ -1,13 +0,0 @@
-extends: existence
-message: "Don't put a period at the end of a heading."
-link: "https://developers.google.com/style/capitalization#capitalization-in-titles-and-headings"
-nonword: true
-level: warning
-scope: heading
-action:
-  name: edit
-  params:
-    - trim_right
-    - "."
-tokens:
-  - '[a-z0-9][.]\s*$'
@@ -1,32 +0,0 @@
-extends: capitalization
-message: "'%s' should use sentence-style capitalization."
-link: "https://developers.google.com/style/capitalization#capitalization-in-titles-and-headings"
-level: warning
-scope: heading
-match: $sentence
-# No `indicators: [":"]` here. That makes Vale require a capital after a colon,
-# which is the Microsoft convention this rule was originally copied from. This
-# guide says the opposite: "the first word after a colon is generally
-# lowercase" (developers.google.com/style/colons), and Colons.yml enforces
-# exactly that. See issue #58.
-exceptions:
-  - Azure
-  - CLI
-  - Cosmos
-  - Docker
-  - Emmet
-  - gRPC
-  - I
-  - Kubernetes
-  - Linux
-  - macOS
-  - Marketplace
-  - MongoDB
-  - REPL
-  - Studio
-  - TypeScript
-  - URLs
-  - Visual
-  - VS
-  - Windows
-  - JSON
@@ -1,13 +0,0 @@
-extends: existence
-message: "Avoid the jargon '%s'."
-link: https://developers.google.com/style/jargon
-level: suggestion
-ignorecase: true
-# The guide also cites 'solution', 'support', and 'workload' as overloaded
-# terms, but those have ordinary technical meanings and accounted for every hit
-# on a 950-file corpus, so only the unambiguous figurative terms are listed.
-tokens:
-  - break-glass
-  - camel ?case
-  - out-of-the-box
-  - swim ?lane
@@ -1,15 +0,0 @@
-extends: substitution
-message: "Use '%s' instead of '%s'."
-link: 'https://developers.google.com/style/abbreviations'
-ignorecase: true
-level: error
-nonword: true
-action:
-  name: replace
-# The delimiter is a lookahead so the replacement doesn't swallow the comma or
-# space that follows (issue #18). `$` is included so the abbreviation is still
-# caught at the end of a heading, table cell, or block, which accounted for 8
-# of 10 occurrences on a 950-file corpus.
-swap:
-  '\b(?:eg|e\.g\.)(?=[\s,;]|$)': for example
-  '\b(?:ie|i\.e\.)(?=[\s,;]|$)': that is
@@ -1,14 +0,0 @@
-extends: existence
-message: "'%s' doesn't need a hyphen."
-link: "https://developers.google.com/style/hyphens"
-level: error
-ignorecase: false
-nonword: true
-action:
-  name: edit
-  params:
-    - regex
-    - "-"
-    - " "
-tokens:
-  - '\b[^\s-]+ly-\w+\b'
@@ -1,12 +0,0 @@
-extends: existence
-message: "Don't use plurals in parentheses such as in '%s'."
-link: "https://developers.google.com/style/plurals-parentheses"
-level: error
-nonword: true
-action:
-  name: edit
-  params:
-    - trim_right
-    - "(s)"
-tokens:
-  - '\b\w+\(s\)'
@@ -1,7 +0,0 @@
-extends: existence
-message: "Spell out all ordinal numbers ('%s') in text."
-link: 'https://developers.google.com/style/numbers'
-level: error
-nonword: true
-tokens:
-  - \d+(?:st|nd|rd|th)
@@ -1,28 +0,0 @@
-extends: existence
-message: "Use the Oxford comma in '%s'."
-link: 'https://developers.google.com/style/commas'
-scope: sentence
-level: warning
-nonword: true
-# List items may be several words long, not just one. Four guards keep the
-# false-positive rate down:
-#
-#   1. The comma can't be the one closing a fronted subordinate clause
-#      ('When your alarm rings, you turn it off and tumble out of bed.') --
-#      that comma separates clauses, not list items. Only the first comma of
-#      such a sentence is exempt, so 'When it rains, apples, pears or bananas
-#      get wet.' is still caught.
-#   2. The item can't open with a clause-introducer (', which ...',
-#      ', specifically ...').
-#   3. The item can't open with a subject pronoun followed by a verb, which
-#      marks a compound predicate rather than a list ('..., you walk to the
-#      fridge and get a snack.'). A pronoun directly followed by 'and'/'or'
-#      is a real list item, so ', you and me.' still matches.
-#   4. Neither item may contain an auxiliary verb, which is another compound
-#      predicate signal (', it has some downsides and is officially
-#      discouraged.').
-#
-# The trailing anchor allows end-of-scope so list fragments ('Apples, pears
-# or bananas') are still caught.
-tokens:
-  - '(?<!^(?i:when|whenever|while|if|unless|until|although|though|because|since|after|before|once|whereas|whether|as)\b[^,]{0,80}),\s(?!(?:which|who|whom|whose|that|where|when|while|because|since|although|though|if|unless|so|but|and|or|however|therefore|thus|specifically|especially|namely|then|take|see|note|consider|make|use|either|neither)\b)(?!(?i:i|you|we|they|he|she|it)\s+(?!(?:and|or)\b))(?:(?!\b(?:is|are|was|were|has|have|had|be|been|being|will|would|can|could|should|may|might|must|do|does|did)\b)\w+ ){0,4}\w+ (?:and|or) (?:(?!\b(?:is|are|was|were|has|have|had|be|been|being|will|would|can|could|should|may|might|must|do|does|did)\b)\w+ ){0,4}\w+(?:[.?!]|$)'
@@ -1,15 +0,0 @@
-extends: existence
-message: "Use parentheses judiciously."
-link: 'https://developers.google.com/style/parentheses'
-nonword: true
-level: suggestion
-# `[^)]` rather than `.+`: a greedy match ran from the first '(' on a line to
-# the last ')', so 'Text (one) and more (two).' produced a single alert
-# covering everything between them. See issue #30.
-# A bare 3-5 letter acronym is skipped: Acronyms.yml requires acronyms to be
-# defined as 'Spelled Out Term (ACRONYM)', so flagging those parentheses would
-# put the two rules in direct conflict. The acronym has to be the whole
-# parenthetical — '(NASA rocket program)' is an ordinary aside and still
-# flags. Length matches the {3,5} in Acronyms.yml. See PR #59.
-tokens:
-  - '\((?![A-Z]{3,5}\))[^)]+\)'
@@ -1,184 +0,0 @@
-extends: existence
-link: 'https://developers.google.com/style/voice'
-message: "In general, use active voice instead of passive voice ('%s')."
-ignorecase: true
-level: suggestion
-raw:
-  - \b(am|are|were|being|is|been|was|be)\b\s*
-tokens:
-  - '[\w]+ed'
-  - awoken
-  - beat
-  - become
-  - been
-  - begun
-  - bent
-  - beset
-  - bet
-  - bid
-  - bidden
-  - bitten
-  - bled
-  - blown
-  - born
-  - bought
-  - bound
-  - bred
-  - broadcast
-  - broken
-  - brought
-  - built
-  - burnt
-  - burst
-  - cast
-  - caught
-  - chosen
-  - clung
-  - come
-  - cost
-  - crept
-  - cut
-  - dealt
-  - dived
-  - done
-  - drawn
-  - dreamt
-  - driven
-  - drunk
-  - dug
-  - eaten
-  - fallen
-  - fed
-  - felt
-  - fit
-  - fled
-  - flown
-  - flung
-  - forbidden
-  - foregone
-  - forgiven
-  - forgotten
-  - forsaken
-  - fought
-  - found
-  - frozen
-  - given
-  - gone
-  - gotten
-  - ground
-  - grown
-  - heard
-  - held
-  - hidden
-  - hit
-  - hung
-  - hurt
-  - kept
-  - knelt
-  - knit
-  - known
-  - laid
-  - lain
-  - leapt
-  - learnt
-  - led
-  - left
-  - lent
-  - let
-  - lighted
-  - lost
-  - made
-  - meant
-  - met
-  - misspelt
-  - mistaken
-  - mown
-  - overcome
-  - overdone
-  - overtaken
-  - overthrown
-  - paid
-  - pled
-  - proven
-  - put
-  - quit
-  - read
-  - rid
-  - ridden
-  - risen
-  - run
-  - rung
-  - said
-  - sat
-  - sawn
-  - seen
-  - sent
-  - set
-  - sewn
-  - shaken
-  - shaven
-  - shed
-  - shod
-  - shone
-  - shorn
-  - shot
-  - shown
-  - shrunk
-  - shut
-  - slain
-  - slept
-  - slid
-  - slit
-  - slung
-  - smitten
-  - sold
-  - sought
-  - sown
-  - sped
-  - spent
-  - spilt
-  - spit
-  - split
-  - spoken
-  - spread
-  - sprung
-  - spun
-  - stolen
-  - stood
-  - stridden
-  - striven
-  - struck
-  - strung
-  - stuck
-  - stung
-  - stunk
-  - sung
-  - sunk
-  - swept
-  - swollen
-  - sworn
-  - swum
-  - swung
-  - taken
-  - taught
-  - thought
-  - thrived
-  - thrown
-  - thrust
-  - told
-  - torn
-  - trodden
-  - understood
-  - upheld
-  - upset
-  - wed
-  - wept
-  - withheld
-  - withstood
-  - woken
-  - won
-  - worn
-  - wound
-  - woven
-  - written
-  - wrung
@@ -1,7 +0,0 @@
-extends: existence
-message: "Don't use periods with acronyms or initialisms such as '%s'."
-link: 'https://developers.google.com/style/abbreviations'
-level: error
-nonword: true
-tokens:
-  - '\b(?:[A-Z]\.){3,}'
@@ -1,7 +0,0 @@
-extends: existence
-message: "Commas and periods go inside quotation marks."
-link: 'https://developers.google.com/style/quotation-marks'
-level: error
-nonword: true
-tokens:
-  - '"[^"]+"[.,?]'
@@ -1,7 +0,0 @@
-extends: existence
-message: "Don't add words such as 'from' or 'between' to describe a range of numbers."
-link: 'https://developers.google.com/style/hyphens'
-nonword: true
-level: warning
-tokens:
-  - '(?:from|between)\s\d+\s?-\s?\d+'
@@ -1,8 +0,0 @@
-extends: existence
-message: "Use semicolons judiciously."
-link: 'https://developers.google.com/style/semicolons'
-nonword: true
-scope: sentence
-level: suggestion
-tokens:
-  - ';'
@@ -1,11 +0,0 @@
-extends: existence
-message: "Don't use internet slang abbreviations such as '%s'."
-link: 'https://developers.google.com/style/abbreviations'
-ignorecase: true
-level: error
-tokens:
-  - 'tl;dr'
-  - ymmv
-  - rtfm
-  - imo
-  - fwiw
@@ -1,10 +0,0 @@
-extends: existence
-message: "'%s' should have one space."
-link: 'https://developers.google.com/style/sentence-spacing'
-level: error
-nonword: true
-action:
-  name: remove
-tokens:
-  - '[a-z][.?!] {2,}[A-Z]'
-  - '[a-z][.?!][A-Z]'
@@ -1,10 +0,0 @@
-extends: existence
-message: "In general, use American spelling instead of '%s'."
-link: 'https://developers.google.com/style/spelling'
-ignorecase: true
-level: warning
-tokens:
-  - '(?:\w+)nised?'
-  - 'colour'
-  - 'labour'
-  - 'centre'
@@ -1,13 +0,0 @@
-extends: existence
-message: "Avoid time-based words like '%s' in product documentation."
-link: https://developers.google.com/style/timeless-documentation
-level: suggestion
-ignorecase: true
-# The guide also names 'now' and 'new', but both have common senses that aren't
-# time-anchored ('create a new project'): adding them took a 950-file corpus of
-# technical documentation from 14 hits to 117. 'recently' is left out too — every
-# hit in that corpus was the UI idiom 'recently used'.
-tokens:
-  - currently
-  - latest
-  - soon
@@ -1,10 +0,0 @@
-extends: existence
-message: "Put a nonbreaking space between the number and the unit in '%s'."
-link: "https://developers.google.com/style/units-of-measure"
-nonword: true
-level: error
-tokens:
-  - '\b\d+(?:B|kB|MB|GB|TB)\b'
-  - '\b\d+(?:ns|ms|min|h|d)\b'
-  # Seconds are split out so a decade ('1990s') isn't read as a unit.
-  - '\b\d+s\b(?<!\b(?:19|20)\d\ds\b)'
@@ -1,11 +0,0 @@
-extends: existence
-message: "Try to avoid using first-person plural like '%s'."
-link: 'https://developers.google.com/style/pronouns#personal-pronouns'
-level: warning
-ignorecase: true
-tokens:
-  - we
-  - we'(?:ve|re)
-  - ours?
-  - us
-  - let's
@@ -1,7 +0,0 @@
-extends: existence
-message: "Avoid using '%s'."
-link: 'https://developers.google.com/style/tense'
-ignorecase: true
-level: warning
-tokens:
-  - will
@@ -1,29 +0,0 @@
-extends: substitution
-message: "Use '%s' instead of '%s'."
-link: "https://developers.google.com/style/word-list"
-level: warning
-# Case matters here: each key's own capitalization is what's being corrected,
-# so ignorecase would make these match their own replacements. The rest of the
-# word list lives in WordListCase.yml.
-ignorecase: false
-action:
-  name: replace
-swap:
-  Ajax: AJAX
-  Android device: Android-powered device
-  android: Android
-  API explorer: APIs Explorer
-  authN: authentication
-  authZ: authorization
-  CLI: command-line tool
-  Cloud: Google Cloud Platform|GCP
-  Container Engine: Kubernetes Engine
-  Developers Console: Google API Console|API Console
-  Google account: Google Account
-  Google accounts: Google Accounts
-  Googling: search with Google
-  HTTPs: HTTPS
-  k8s: Kubernetes
-  SHA1: SHA-1|HAS-SHA1
-  url: URL
-  World Wide Web: web
@@ -1,68 +0,0 @@
-extends: substitution
-message: "Use '%s' instead of '%s'."
-link: "https://developers.google.com/style/word-list"
-level: warning
-# The case-insensitive half of the word list, so sentence-initial use is caught
-# ('Touch the screen', not only 'touch the screen'). Entries that must stay
-# case-sensitive are in WordList.yml.
-ignorecase: true
-action:
-  name: replace
-swap:
-  "(?:API Console|dev|developer) key": API key
-  "(?:cell ?phone|smart ?phone)": phone|mobile phone
-  "(?:dev|developer|APIs) console": API console
-  "(?:e-mail|Email|E-mail)": email
-  "(?:file ?path|path ?name)": path
-  "(?:kill|terminate|abort)": stop|exit|cancel|end
-  # Longest form first: with the shortest alternative leading, 'OAuth 2' matched
-  # only 'OAuth', so applying the suggestion produced 'OAuth 2.0 2'. The rule is
-  # already case-insensitive, so the inline (?i) is redundant. See issue #41.
-  '\bOauth2\.0\b|\bOAuth ?2\b(?!\.0)|\bOauth\b(?! ?2)': OAuth 2.0
-  "(?:ok|Okay)": OK|okay
-  "(?:WiFi|wifi)": Wi-Fi
-  '[\.]+apk': APK
-  '3\-D': 3D
-  'Google (?:I\-O|IO)': Google I/O
-  "tap (?:&|and) hold": touch & hold
-  "un(?:check|select)": clear
-  above: preceding
-  account name: username
-  action bar: app bar
-  admin: administrator
-  a\.k\.a|aka: or|also known as
-  application: app
-  approx\.: approximately
-  autoupdate: automatically update
-  cellular data: mobile data
-  cellular network: mobile network
-  chapter: documents|pages|sections
-  check box: checkbox
-  click on: click|click in
-  content type: media type
-  curated roles: predefined roles
-  data are: data is
-  disabled?: turn off|off
-  ephemeral IP address: ephemeral external IP address
-  fewer data: less data
-  file name: filename
-  firewalls: firewall rules
-  functionality: capability|feature
-  grayed-out: unavailable
-  in order to: to
-  ingest: import|load
-  long press: touch & hold
-  network IP address: internal IP address
-  omnibox: address bar
-  open-source: open source
-  overview screen: recents screen
-  regex: regular expression
-  sign into: sign in to
-  '(?<!single )sign-?on': single sign-on
-  static IP address: static external IP address
-  stylesheet: style sheet
-  synch: sync
-  tablename: table name
-  tablet: device
-  'touch(?! ?(?:&|and) hold)': tap
-  vs\.: versus
@@ -1,4 +0,0 @@
-{
-  "feed": "https://github.com/errata-ai/Google/releases.atom",
-  "vale_version": ">=1.0.0"
-}
@@ -1,8 +0,0 @@
-extends: metric
-message: "Try to keep the Automated Readability Index (%s) below 8."
-link: https://en.wikipedia.org/wiki/Automated_readability_index
-
-formula: |
-  (4.71 * (characters / words)) + (0.5 * (words / sentences)) - 21.43
-
-condition: "> 8"
@@ -1,8 +0,0 @@
-extends: metric
-message: "Try to keep the Coleman–Liau Index grade (%s) below 9."
-link: https://en.wikipedia.org/wiki/Coleman%E2%80%93Liau_index
-
-formula: |
-  (0.0588 * (characters / words) * 100) - (0.296 * (sentences / words) * 100) - 15.8
-
-condition: "> 9"
@@ -1,8 +0,0 @@
-extends: metric
-message: "Try to keep the Flesch–Kincaid grade level (%s) below 8."
-link: https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readability_tests
-
-formula: |
-  (0.39 * (words / sentences)) + (11.8 * (syllables / words)) - 15.59
-
-condition: "> 8"
@@ -1,8 +0,0 @@
-extends: metric
-message: "Try to keep the Flesch reading ease score (%s) above 70."
-link: https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readability_tests
-
-formula: |
-  206.835 - (1.015 * (words / sentences)) - (84.6 * (syllables / words))
-
-condition: "< 70"
@@ -1,8 +0,0 @@
-extends: metric
-message: "Try to keep the Gunning-Fog index (%s) below 10."
-link: https://en.wikipedia.org/wiki/Gunning_fog_index
-
-formula: |
-  0.4 * ((words / sentences) + 100 * (complex_words / words))
-
-condition: "> 10"
@@ -1,17 +0,0 @@
-extends: metric
-message: "Try to keep the LIX score (%s) below 35."
-
-link: https://en.wikipedia.org/wiki/Lix_(readability_test)
-# Very Easy: 20 - 25
-#
-# Easy: 30 - 35
-#
-# Medium: 40 - 45
-#
-# Difficult: 50 - 55
-#
-# Very Difficult: 60+
-formula: |
-  (words / sentences) + ((long_words * 100) / words)
-
-condition: "> 35"
@@ -1,8 +0,0 @@
-extends: metric
-message: "Try to keep the SMOG grade (%s) below 10."
-link: https://en.wikipedia.org/wiki/SMOG
-
-formula: |
-  1.0430 * math.sqrt((polysyllabic_words * 30.0) / sentences) + 3.1291
-
-condition: "> 10"
@@ -1,4 +0,0 @@
-{
-  "feed": "https://github.com/errata-ai/Readability/releases.atom",
-  "vale_version": ">=2.13.0"
-}
@@ -1,42 +0,0 @@
-devx
-grm
-GRM
-Gitea
-ZITADEL
-OpenTofu
-Ansible
-Vaultwarden
-Nextcloud
-Vikunja
-Mattermost
-Prometheus
-Grafana
-Loki
-Alertmanager
-Promtail
-pyproject
-tofu
-act_runner
-actionlint
-hadolint
-git-cliff
-pre-commit
-semver
-changelog
-idempotent
-rootless
-OIDC
-SSO
-SAML
-LDAP
-pytest
-molecule
-ruff
-pyright
-bandit
-Vale
-oblachno
-Oblachno
-Bulgarian
-gitea-runner
-runner
@@ -1,6 +0,0 @@
-extends: existence
-message: "Unlabeled code block — add a language tag (```bash, ```yaml, etc.)"
-level: warning
-scope: raw
-raw:
-  - '(?ms)^\n```\n.*?^```\s*$'
@@ -1,13 +0,0 @@
-extends: existence
-message: "Avoid '%s' — it's condescending in technical documentation"
-level: warning
-ignorecase: true
-tokens:
-  - '\bsimply\b'
-  - '\bjust\b'
-  - '\bobviously\b'
-  - '\bof course\b'
-  - '\bas you (can )?see\b'
-  - '\beasily\b'
-  - '\btrivial\b'
-  - '\bstraightforward\b'
@@ -1,3 +0,0 @@
-# Custom Vale style for devx documentation
-
-Project-specific terminology and style rules
@@ -1,11 +0,0 @@
-extends: substitution
-message: "Use '%s' instead of '%s' (terminology consistency)"
-level: error
-ignorecase: false
-swap:
-  '\b(?i)gitea\b': Gitea
-  '\b(?i)zitadel\b': ZITADEL
-  '\b(?i)opentofu\b': OpenTofu
-  '\b(?i)vaultwarden\b': Vaultwarden
-  '\b(?i)nextcloud\b': Nextcloud
-  '\b(?i)mattermost\b': Mattermost
@@ -1,702 +0,0 @@
-extends: existence
-message: "Try to avoid using clichés like '%s'."
-ignorecase: true
-level: warning
-tokens:
-  - a chip off the old block
-  - a clean slate
-  - a dark and stormy night
-  - a far cry
-  - a fine kettle of fish
-  - a loose cannon
-  - a penny saved is a penny earned
-  - a tough row to hoe
-  - a word to the wise
-  - ace in the hole
-  - acid test
-  - add insult to injury
-  - against all odds
-  - air your dirty laundry
-  - all fun and games
-  - all in a day's work
-  - all talk, no action
-  - all thumbs
-  - all your eggs in one basket
-  - all's fair in love and war
-  - all's well that ends well
-  - almighty dollar
-  - American as apple pie
-  - an axe to grind
-  - another day, another dollar
-  - armed to the teeth
-  - as luck would have it
-  - as old as time
-  - as the crow flies
-  - at loose ends
-  - at my wits end
-  - avoid like the plague
-  - babe in the woods
-  - back against the wall
-  - back in the saddle
-  - back to square one
-  - back to the drawing board
-  - bad to the bone
-  - badge of honor
-  - bald faced liar
-  - ballpark figure
-  - banging your head against a brick wall
-  - baptism by fire
-  - barking up the wrong tree
-  - bat out of hell
-  - be all and end all
-  - beat a dead horse
-  - beat around the bush
-  - been there, done that
-  - beggars can't be choosers
-  - behind the eight ball
-  - bend over backwards
-  - benefit of the doubt
-  - bent out of shape
-  - best thing since sliced bread
-  - bet your bottom dollar
-  - better half
-  - better late than never
-  - better mousetrap
-  - better safe than sorry
-  - between a rock and a hard place
-  - beyond the pale
-  - bide your time
-  - big as life
-  - big cheese
-  - big fish in a small pond
-  - big man on campus
-  - bigger they are the harder they fall
-  - bird in the hand
-  - bird's eye view
-  - birds and the bees
-  - birds of a feather flock together
-  - bit the hand that feeds you
-  - bite the bullet
-  - bite the dust
-  - bitten off more than he can chew
-  - black as coal
-  - black as pitch
-  - black as the ace of spades
-  - blast from the past
-  - bleeding heart
-  - blessing in disguise
-  - blind ambition
-  - blind as a bat
-  - blind leading the blind
-  - blood is thicker than water
-  - blood sweat and tears
-  - blow off steam
-  - blow your own horn
-  - blushing bride
-  - boils down to
-  - bolt from the blue
-  - bone to pick
-  - bored stiff
-  - bored to tears
-  - bottomless pit
-  - boys will be boys
-  - bright and early
-  - brings home the bacon
-  - broad across the beam
-  - broken record
-  - brought back to reality
-  - bull by the horns
-  - bull in a china shop
-  - burn the midnight oil
-  - burning question
-  - burning the candle at both ends
-  - burst your bubble
-  - bury the hatchet
-  - busy as a bee
-  - by hook or by crook
-  - call a spade a spade
-  - called onto the carpet
-  - calm before the storm
-  - can of worms
-  - can't cut the mustard
-  - can't hold a candle to
-  - case of mistaken identity
-  - cat got your tongue
-  - cat's meow
-  - caught in the crossfire
-  - caught red-handed
-  - checkered past
-  - chomping at the bit
-  - cleanliness is next to godliness
-  - clear as a bell
-  - clear as mud
-  - close to the vest
-  - cock and bull story
-  - cold shoulder
-  - come hell or high water
-  - cool as a cucumber
-  - cool, calm, and collected
-  - cost a king's ransom
-  - count your blessings
-  - crack of dawn
-  - crash course
-  - creature comforts
-  - cross that bridge when you come to it
-  - crushing blow
-  - cry like a baby
-  - cry me a river
-  - cry over spilt milk
-  - crystal clear
-  - curiosity killed the cat
-  - cut and dried
-  - cut through the red tape
-  - cut to the chase
-  - cute as a bugs ear
-  - cute as a button
-  - cute as a puppy
-  - cuts to the quick
-  - dark before the dawn
-  - day in, day out
-  - dead as a doornail
-  - devil is in the details
-  - dime a dozen
-  - divide and conquer
-  - dog and pony show
-  - dog days
-  - dog eat dog
-  - dog tired
-  - don't burn your bridges
-  - don't count your chickens
-  - don't look a gift horse in the mouth
-  - don't rock the boat
-  - don't step on anyone's toes
-  - don't take any wooden nickels
-  - down and out
-  - down at the heels
-  - down in the dumps
-  - down the hatch
-  - down to earth
-  - draw the line
-  - dressed to kill
-  - dressed to the nines
-  - drives me up the wall
-  - dull as dishwater
-  - dyed in the wool
-  - eagle eye
-  - ear to the ground
-  - early bird catches the worm
-  - easier said than done
-  - easy as pie
-  - eat your heart out
-  - eat your words
-  - eleventh hour
-  - even the playing field
-  - every dog has its day
-  - every fiber of my being
-  - everything but the kitchen sink
-  - eye for an eye
-  - face the music
-  - facts of life
-  - fair weather friend
-  - fall by the wayside
-  - fan the flames
-  - feast or famine
-  - feather your nest
-  - feathered friends
-  - few and far between
-  - fifteen minutes of fame
-  - filthy vermin
-  - fine kettle of fish
-  - fish out of water
-  - fishing for a compliment
-  - fit as a fiddle
-  - fit the bill
-  - fit to be tied
-  - flash in the pan
-  - flat as a pancake
-  - flip your lid
-  - flog a dead horse
-  - fly by night
-  - fly the coop
-  - follow your heart
-  - for all intents and purposes
-  - for the birds
-  - for what it's worth
-  - force of nature
-  - force to be reckoned with
-  - forgive and forget
-  - fox in the henhouse
-  - free and easy
-  - free as a bird
-  - fresh as a daisy
-  - full steam ahead
-  - fun in the sun
-  - garbage in, garbage out
-  - gentle as a lamb
-  - get a kick out of
-  - get a leg up
-  - get down and dirty
-  - get the lead out
-  - get to the bottom of
-  - get your feet wet
-  - gets my goat
-  - gilding the lily
-  - give and take
-  - go against the grain
-  - go at it tooth and nail
-  - go for broke
-  - go him one better
-  - go the extra mile
-  - go with the flow
-  - goes without saying
-  - good as gold
-  - good deed for the day
-  - good things come to those who wait
-  - good time was had by all
-  - good times were had by all
-  - greased lightning
-  - greek to me
-  - green thumb
-  - green-eyed monster
-  - grist for the mill
-  - growing like a weed
-  - hair of the dog
-  - hand to mouth
-  - happy as a clam
-  - happy as a lark
-  - hasn't a clue
-  - have a nice day
-  - have high hopes
-  - have the last laugh
-  - haven't got a row to hoe
-  - head honcho
-  - head over heels
-  - hear a pin drop
-  - heard it through the grapevine
-  - heart's content
-  - heavy as lead
-  - hem and haw
-  - high and dry
-  - high and mighty
-  - high as a kite
-  - hit paydirt
-  - hold your head up high
-  - hold your horses
-  - hold your own
-  - hold your tongue
-  - honest as the day is long
-  - horns of a dilemma
-  - horse of a different color
-  - hot under the collar
-  - hour of need
-  - I beg to differ
-  - icing on the cake
-  - if the shoe fits
-  - if the shoe were on the other foot
-  - in a jam
-  - in a jiffy
-  - in a nutshell
-  - in a pig's eye
-  - in a pinch
-  - in a word
-  - in hot water
-  - in the gutter
-  - in the nick of time
-  - in the thick of it
-  - in your dreams
-  - it ain't over till the fat lady sings
-  - it goes without saying
-  - it takes all kinds
-  - it takes one to know one
-  - it's a small world
-  - it's only a matter of time
-  - ivory tower
-  - Jack of all trades
-  - jockey for position
-  - jog your memory
-  - joined at the hip
-  - judge a book by its cover
-  - jump down your throat
-  - jump in with both feet
-  - jump on the bandwagon
-  - jump the gun
-  - jump to conclusions
-  - just a hop, skip, and a jump
-  - just the ticket
-  - justice is blind
-  - keep a stiff upper lip
-  - keep an eye on
-  - keep it simple, stupid
-  - keep the home fires burning
-  - keep up with the Joneses
-  - keep your chin up
-  - keep your fingers crossed
-  - kick the bucket
-  - kick up your heels
-  - kick your feet up
-  - kid in a candy store
-  - kill two birds with one stone
-  - kiss of death
-  - knock it out of the park
-  - knock on wood
-  - knock your socks off
-  - know him from Adam
-  - know the ropes
-  - know the score
-  - knuckle down
-  - knuckle sandwich
-  - knuckle under
-  - labor of love
-  - ladder of success
-  - land on your feet
-  - lap of luxury
-  - last but not least
-  - last hurrah
-  - last-ditch effort
-  - law of the jungle
-  - law of the land
-  - lay down the law
-  - leaps and bounds
-  - let sleeping dogs lie
-  - let the cat out of the bag
-  - let the good times roll
-  - let your hair down
-  - let's talk turkey
-  - letter perfect
-  - lick your wounds
-  - lies like a rug
-  - life's a bitch
-  - life's a grind
-  - light at the end of the tunnel
-  - lighter than a feather
-  - lighter than air
-  - like clockwork
-  - like father like son
-  - like taking candy from a baby
-  - like there's no tomorrow
-  - lion's share
-  - live and learn
-  - live and let live
-  - long and short of it
-  - long lost love
-  - look before you leap
-  - look down your nose
-  - look what the cat dragged in
-  - looking a gift horse in the mouth
-  - looks like death warmed over
-  - loose cannon
-  - lose your head
-  - lose your temper
-  - loud as a horn
-  - lounge lizard
-  - loved and lost
-  - low man on the totem pole
-  - luck of the draw
-  - luck of the Irish
-  - make hay while the sun shines
-  - make money hand over fist
-  - make my day
-  - make the best of a bad situation
-  - make the best of it
-  - make your blood boil
-  - man of few words
-  - man's best friend
-  - mark my words
-  - meaningful dialogue
-  - missed the boat on that one
-  - moment in the sun
-  - moment of glory
-  - moment of truth
-  - money to burn
-  - more power to you
-  - more than one way to skin a cat
-  - movers and shakers
-  - moving experience
-  - naked as a jaybird
-  - naked truth
-  - neat as a pin
-  - needle in a haystack
-  - needless to say
-  - neither here nor there
-  - never look back
-  - never say never
-  - nip and tuck
-  - nip it in the bud
-  - no guts, no glory
-  - no love lost
-  - no pain, no gain
-  - no skin off my back
-  - no stone unturned
-  - no time like the present
-  - no use crying over spilled milk
-  - nose to the grindstone
-  - not a hope in hell
-  - not a minute's peace
-  - not in my backyard
-  - not playing with a full deck
-  - not the end of the world
-  - not written in stone
-  - nothing to sneeze at
-  - nothing ventured nothing gained
-  - now we're cooking
-  - off the top of my head
-  - off the wagon
-  - off the wall
-  - old hat
-  - older and wiser
-  - older than dirt
-  - older than Methuselah
-  - on a roll
-  - on cloud nine
-  - on pins and needles
-  - on the bandwagon
-  - on the money
-  - on the nose
-  - on the rocks
-  - on the spot
-  - on the tip of my tongue
-  - on the wagon
-  - on thin ice
-  - once bitten, twice shy
-  - one bad apple doesn't spoil the bushel
-  - one born every minute
-  - one brick short
-  - one foot in the grave
-  - one in a million
-  - one red cent
-  - only game in town
-  - open a can of worms
-  - open and shut case
-  - open the flood gates
-  - opportunity doesn't knock twice
-  - out of pocket
-  - out of sight, out of mind
-  - out of the frying pan into the fire
-  - out of the woods
-  - out on a limb
-  - over a barrel
-  - over the hump
-  - pain and suffering
-  - pain in the
-  - panic button
-  - par for the course
-  - part and parcel
-  - party pooper
-  - pass the buck
-  - patience is a virtue
-  - pay through the nose
-  - penny pincher
-  - perfect storm
-  - pig in a poke
-  - pile it on
-  - pillar of the community
-  - pin your hopes on
-  - pitter patter of little feet
-  - plain as day
-  - plain as the nose on your face
-  - play by the rules
-  - play your cards right
-  - playing the field
-  - playing with fire
-  - pleased as punch
-  - plenty of fish in the sea
-  - point with pride
-  - poor as a church mouse
-  - pot calling the kettle black
-  - pretty as a picture
-  - pull a fast one
-  - pull your punches
-  - pulling your leg
-  - pure as the driven snow
-  - put it in a nutshell
-  - put one over on you
-  - put the cart before the horse
-  - put the pedal to the metal
-  - put your best foot forward
-  - put your foot down
-  - quick as a bunny
-  - quick as a lick
-  - quick as a wink
-  - quick as lightning
-  - quiet as a dormouse
-  - rags to riches
-  - raining buckets
-  - raining cats and dogs
-  - rank and file
-  - rat race
-  - reap what you sow
-  - red as a beet
-  - red herring
-  - reinvent the wheel
-  - rich and famous
-  - rings a bell
-  - ripe old age
-  - ripped me off
-  - rise and shine
-  - road to hell is paved with good intentions
-  - rob Peter to pay Paul
-  - roll over in the grave
-  - rub the wrong way
-  - ruled the roost
-  - running in circles
-  - sad but true
-  - sadder but wiser
-  - salt of the earth
-  - scared stiff
-  - scared to death
-  - sealed with a kiss
-  - second to none
-  - see eye to eye
-  - seen the light
-  - seize the day
-  - set the record straight
-  - set the world on fire
-  - set your teeth on edge
-  - sharp as a tack
-  - shoot for the moon
-  - shoot the breeze
-  - shot in the dark
-  - shoulder to the wheel
-  - sick as a dog
-  - sigh of relief
-  - signed, sealed, and delivered
-  - sink or swim
-  - six of one, half a dozen of another
-  - skating on thin ice
-  - slept like a log
-  - slinging mud
-  - slippery as an eel
-  - slow as molasses
-  - smart as a whip
-  - smooth as a baby's bottom
-  - sneaking suspicion
-  - snug as a bug in a rug
-  - sow wild oats
-  - spare the rod, spoil the child
-  - speak of the devil
-  - spilled the beans
-  - spinning your wheels
-  - spitting image of
-  - spoke with relish
-  - spread like wildfire
-  - spring to life
-  - squeaky wheel gets the grease
-  - stands out like a sore thumb
-  - start from scratch
-  - stick in the mud
-  - still waters run deep
-  - stitch in time
-  - stop and smell the roses
-  - straight as an arrow
-  - straw that broke the camel's back
-  - strong as an ox
-  - stubborn as a mule
-  - stuff that dreams are made of
-  - stuffed shirt
-  - sweating blood
-  - sweating bullets
-  - take a load off
-  - take one for the team
-  - take the bait
-  - take the bull by the horns
-  - take the plunge
-  - takes one to know one
-  - takes two to tango
-  - the more the merrier
-  - the real deal
-  - the real McCoy
-  - the red carpet treatment
-  - the same old story
-  - there is no accounting for taste
-  - thick as a brick
-  - thick as thieves
-  - thin as a rail
-  - think outside of the box
-  - third time's the charm
-  - this day and age
-  - this hurts me worse than it hurts you
-  - this point in time
-  - three sheets to the wind
-  - through thick and thin
-  - throw in the towel
-  - tie one on
-  - tighter than a drum
-  - time and time again
-  - time is of the essence
-  - tip of the iceberg
-  - tired but happy
-  - to coin a phrase
-  - to each his own
-  - to make a long story short
-  - to the best of my knowledge
-  - toe the line
-  - tongue in cheek
-  - too good to be true
-  - too hot to handle
-  - too numerous to mention
-  - touch with a ten foot pole
-  - tough as nails
-  - trial and error
-  - trials and tribulations
-  - tried and true
-  - trip down memory lane
-  - twist of fate
-  - two cents worth
-  - two peas in a pod
-  - ugly as sin
-  - under the counter
-  - under the gun
-  - under the same roof
-  - under the weather
-  - until the cows come home
-  - unvarnished truth
-  - up the creek
-  - uphill battle
-  - upper crust
-  - upset the applecart
-  - vain attempt
-  - vain effort
-  - vanquish the enemy
-  - vested interest
-  - waiting for the other shoe to drop
-  - wakeup call
-  - warm welcome
-  - watch your p's and q's
-  - watch your tongue
-  - watching the clock
-  - water under the bridge
-  - weather the storm
-  - weed them out
-  - week of Sundays
-  - went belly up
-  - wet behind the ears
-  - what goes around comes around
-  - what you see is what you get
-  - when it rains, it pours
-  - when push comes to shove
-  - when the cat's away
-  - when the going gets tough, the tough get going
-  - white as a sheet
-  - whole ball of wax
-  - whole hog
-  - whole nine yards
-  - wild goose chase
-  - will wonders never cease?
-  - wisdom of the ages
-  - wise as an owl
-  - wolf at the door
-  - words fail me
-  - work like a dog
-  - world weary
-  - worst nightmare
-  - worth its weight in gold
-  - wrong side of the bed
-  - yanking your chain
-  - yappy as a dog
-  - years young
-  - you are what you eat
-  - you can run but you can't hide
-  - you only live once
-  - you're the boss
-  - young and foolish
-  - young and vibrant
@@ -1,32 +0,0 @@
-extends: existence
-message: "Try to avoid using '%s'."
-ignorecase: true
-level: suggestion
-tokens:
-  - am
-  - are
-  - aren't
-  - be
-  - been
-  - being
-  - he's
-  - here's
-  - here's
-  - how's
-  - i'm
-  - is
-  - isn't
-  - it's
-  - she's
-  - that's
-  - there's
-  - they're
-  - was
-  - wasn't
-  - we're
-  - were
-  - weren't
-  - what's
-  - where's
-  - who's
-  - you're
@@ -1,11 +0,0 @@
-extends: repetition
-message: "'%s' is repeated!"
-level: warning
-alpha: true
-action:
-  name: edit
-  params:
-    - truncate
-    - " "
-tokens:
-  - '[^\s]+'
@@ -1,183 +0,0 @@
-extends: existence
-message: "'%s' may be passive voice. Use active voice if you can."
-ignorecase: true
-level: warning
-raw:
-  - \b(am|are|were|being|is|been|was|be)\b\s*
-tokens:
-  - '[\w]+ed'
-  - awoken
-  - beat
-  - become
-  - been
-  - begun
-  - bent
-  - beset
-  - bet
-  - bid
-  - bidden
-  - bitten
-  - bled
-  - blown
-  - born
-  - bought
-  - bound
-  - bred
-  - broadcast
-  - broken
-  - brought
-  - built
-  - burnt
-  - burst
-  - cast
-  - caught
-  - chosen
-  - clung
-  - come
-  - cost
-  - crept
-  - cut
-  - dealt
-  - dived
-  - done
-  - drawn
-  - dreamt
-  - driven
-  - drunk
-  - dug
-  - eaten
-  - fallen
-  - fed
-  - felt
-  - fit
-  - fled
-  - flown
-  - flung
-  - forbidden
-  - foregone
-  - forgiven
-  - forgotten
-  - forsaken
-  - fought
-  - found
-  - frozen
-  - given
-  - gone
-  - gotten
-  - ground
-  - grown
-  - heard
-  - held
-  - hidden
-  - hit
-  - hung
-  - hurt
-  - kept
-  - knelt
-  - knit
-  - known
-  - laid
-  - lain
-  - leapt
-  - learnt
-  - led
-  - left
-  - lent
-  - let
-  - lighted
-  - lost
-  - made
-  - meant
-  - met
-  - misspelt
-  - mistaken
-  - mown
-  - overcome
-  - overdone
-  - overtaken
-  - overthrown
-  - paid
-  - pled
-  - proven
-  - put
-  - quit
-  - read
-  - rid
-  - ridden
-  - risen
-  - run
-  - rung
-  - said
-  - sat
-  - sawn
-  - seen
-  - sent
-  - set
-  - sewn
-  - shaken
-  - shaven
-  - shed
-  - shod
-  - shone
-  - shorn
-  - shot
-  - shown
-  - shrunk
-  - shut
-  - slain
-  - slept
-  - slid
-  - slit
-  - slung
-  - smitten
-  - sold
-  - sought
-  - sown
-  - sped
-  - spent
-  - spilt
-  - spit
-  - split
-  - spoken
-  - spread
-  - sprung
-  - spun
-  - stolen
-  - stood
-  - stridden
-  - striven
-  - struck
-  - strung
-  - stuck
-  - stung
-  - stunk
-  - sung
-  - sunk
-  - swept
-  - swollen
-  - sworn
-  - swum
-  - swung
-  - taken
-  - taught
-  - thought
-  - thrived
-  - thrown
-  - thrust
-  - told
-  - torn
-  - trodden
-  - understood
-  - upheld
-  - upset
-  - wed
-  - wept
-  - withheld
-  - withstood
-  - woken
-  - won
-  - worn
-  - wound
-  - woven
-  - written
-  - wrung
@@ -1,27 +0,0 @@
-Based on [write-good](https://github.com/btford/write-good).
-
-> Naive linter for English prose for developers who can't write good and wanna learn to do other stuff good too.
-
-```
-The MIT License (MIT)
-
-Copyright (c) 2014 Brian Ford
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-```
@@ -1,5 +0,0 @@
-extends: existence
-message: "Don't start a sentence with '%s'."
-level: error
-raw:
-  - '(?:[;-]\s)so[\s,]|\bSo[\s,]'
@@ -1,6 +0,0 @@
-extends: existence
-message: "Don't start a sentence with '%s'."
-ignorecase: false
-level: error
-raw:
-  - '(?:[;-]\s)There\s(is|are)|\bThere\s(is|are)\b'
@@ -1,221 +0,0 @@
-extends: existence
-message: "'%s' is too wordy."
-ignorecase: true
-level: warning
-tokens:
-  - a number of
-  - abundance
-  - accede to
-  - accelerate
-  - accentuate
-  - accompany
-  - accomplish
-  - accorded
-  - accrue
-  - acquiesce
-  - acquire
-  - additional
-  - adjacent to
-  - adjustment
-  - admissible
-  - advantageous
-  - adversely impact
-  - advise
-  - aforementioned
-  - aggregate
-  - aircraft
-  - all of
-  - all things considered
-  - alleviate
-  - allocate
-  - along the lines of
-  - already existing
-  - alternatively
-  - amazing
-  - ameliorate
-  - anticipate
-  - apparent
-  - appreciable
-  - as a matter of fact
-  - as a means of
-  - as far as I'm concerned
-  - as of yet
-  - as to
-  - as yet
-  - ascertain
-  - assistance
-  - at the present time
-  - at this time
-  - attain
-  - attributable to
-  - authorize
-  - because of the fact that
-  - belated
-  - benefit from
-  - bestow
-  - by means of
-  - by virtue of
-  - by virtue of the fact that
-  - cease
-  - close proximity
-  - commence
-  - comply with
-  - concerning
-  - consequently
-  - consolidate
-  - constitutes
-  - demonstrate
-  - depart
-  - designate
-  - discontinue
-  - due to the fact that
-  - each and every
-  - economical
-  - eliminate
-  - elucidate
-  - employ
-  - endeavor
-  - enumerate
-  - equitable
-  - equivalent
-  - evaluate
-  - evidenced
-  - exclusively
-  - expedite
-  - expend
-  - expiration
-  - facilitate
-  - factual evidence
-  - feasible
-  - finalize
-  - first and foremost
-  - for all intents and purposes
-  - for the most part
-  - for the purpose of
-  - forfeit
-  - formulate
-  - have a tendency to
-  - honest truth
-  - however
-  - if and when
-  - impacted
-  - implement
-  - in a manner of speaking
-  - in a timely manner
-  - in a very real sense
-  - in accordance with
-  - in addition
-  - in all likelihood
-  - in an effort to
-  - in between
-  - in excess of
-  - in lieu of
-  - in light of the fact that
-  - in many cases
-  - in my opinion
-  - in order to
-  - in regard to
-  - in some instances
-  - in terms of
-  - in the case of
-  - in the event that
-  - in the final analysis
-  - in the nature of
-  - in the near future
-  - in the process of
-  - inception
-  - incumbent upon
-  - indicate
-  - indication
-  - initiate
-  - irregardless
-  - is applicable to
-  - is authorized to
-  - is responsible for
-  - it is
-  - it is essential
-  - it seems that
-  - it was
-  - magnitude
-  - maximum
-  - methodology
-  - minimize
-  - minimum
-  - modify
-  - monitor
-  - multiple
-  - necessitate
-  - nevertheless
-  - not certain
-  - not many
-  - not often
-  - not unless
-  - not unlike
-  - notwithstanding
-  - null and void
-  - numerous
-  - objective
-  - obligate
-  - obtain
-  - on the contrary
-  - on the other hand
-  - one particular
-  - optimum
-  - overall
-  - owing to the fact that
-  - participate
-  - particulars
-  - pass away
-  - pertaining to
-  - point in time
-  - portion
-  - possess
-  - preclude
-  - previously
-  - prior to
-  - prioritize
-  - procure
-  - proficiency
-  - provided that
-  - purchase
-  - put simply
-  - readily apparent
-  - refer back
-  - regarding
-  - relocate
-  - remainder
-  - remuneration
-  - requirement
-  - reside
-  - residence
-  - retain
-  - satisfy
-  - shall
-  - should you wish
-  - similar to
-  - solicit
-  - span across
-  - strategize
-  - subsequent
-  - substantial
-  - successfully complete
-  - sufficient
-  - terminate
-  - the month of
-  - the point I am trying to make
-  - therefore
-  - time period
-  - took advantage of
-  - transmit
-  - transpire
-  - type of
-  - until such time as
-  - utilization
-  - utilize
-  - validate
-  - various different
-  - what I mean to say is
-  - whether or not
-  - with respect to
-  - with the exception of
-  - witnessed
@@ -1,29 +0,0 @@
-extends: existence
-message: "'%s' is a weasel word!"
-ignorecase: true
-level: warning
-tokens:
-  - clearly
-  - completely
-  - exceedingly
-  - excellent
-  - extremely
-  - fairly
-  - huge
-  - interestingly
-  - is a number
-  - largely
-  - mostly
-  - obviously
-  - quite
-  - relatively
-  - remarkably
-  - several
-  - significantly
-  - substantially
-  - surprisingly
-  - tiny
-  - usually
-  - various
-  - vast
-  - very
@@ -1,4 +0,0 @@
-{
-  "feed": "https://github.com/errata-ai/write-good/releases.atom",
-  "vale_version": ">=1.0.0"
-}
@@ -1,625 +0,0 @@
-# AGENTS.md — Project Conventions for GRM
-
-## Virtual Environment
-
-All Python tools, tests, and scripts run inside a standard `.venv` directory.
-Activate it before running any non-`make` command:
-
-```bash
-source activate.sh       # bash/zsh
-source activate.fish     # fish
-source activate.zsh      # zsh
-```
-
-If `.venv` doesn't exist, run `make setup` first. The `make` targets handle
-venv activation automatically — always prefer `make <target>` over raw commands.
-
-## 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 `validate` job runs `make setup-image` (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/grm/`) — Click-based CLI that delegates to Ansible
- **Ansible Role** (`ansible/roles/gitea_runner/`) — Idempotent role for rootless Docker runner setup with pasta networking (IPv6 support)
- **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 step in the `detect-and-configure` 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 validate + 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.
-
-**IMPORTANT:** The task title must NOT include the `GRM-N:` prefix.
-The `make create-pr` and `check_auto_merge_ready` commands automatically
-prepend `GRM-N: ` to the Vikunja task title when forming the PR title.
-If the Vikunja task title already includes the prefix, the PR title will
-have a double prefix and auto-merge validation will fail.
-
-### 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):
-```text
-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 `validate` job):** Every PR triggers an automated
-review via `python -m devx.ci.pr_review` as a step in the `validate` job.
-This 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) — perfunctory 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 `validate` 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-and-maintain job 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's `validate` job includes a pre-merge validation step
-that validates branch format, PR title, and Vikunja task match. This
-fails fast before expensive molecule tests run.
-
-The `validate` job also includes a `detect-changes` step 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 `validate` job
-includes a `discover-runners` step (conditional on ansible-changed) that
-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. Consolidated
-into 2 jobs (from 7) to reduce runner overhead:
-
-1. **detect-and-configure** — Configures repo (branch protection, labels),
-   detects release commit, validates commit message. Outputs `is-release`
-   and `is-automated` for the next job.
-
-2. **release-and-maintain** — Runs all post-merge maintenance as
-   conditional steps:
-   - **release** (if not a release commit) — Runs `devx.ci.release` which
-     checks for user-facing changes via `classify_changes` (skips if only
-     workflow/infrastructure files changed), uses git-cliff for semver,
-     updates `__version__`, updates `CHANGELOG.md`, runs lint+tests, commits
-     with `release: vX.Y.Z [skip ci]`, creates annotated tag, pushes to master.
-   - **publish** (if release created a tag) — Builds and publishes the
-     package to the Gitea PyPI registry. Checks out the release tag
-     within the same job.
-   - **sync-wiki** (if not automated) — Syncs documentation to the Gitea wiki.
-   - **vikunja** (if not automated) — Marks the corresponding Vikunja task as done.
-   - **badges** (always) — Generates and pushes quality badge SVGs to the
-     `badges` branch. Fetches latest master first to pick up release commits.
-
-### 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/grm/**` — 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, 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
- `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/grm/` | 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/grm/` NEVER imports from devx** — the GRM tool is self-contained
-2. **devx MAY import from `grm`** — 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 `grm`:
-
-| PYTHONPATH | When to use | Example modules |
-|------------|-------------|-----------------|
-| `src` | Module imports from `grm` | `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.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 `grm`.
-
-### 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 step** (in the `release-and-maintain` job, runs after the release step creates a tag):
-   - Runs after the release step creates a tag
-   - Gets the tag from the release step's output
-   - 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/grm/__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/grm/__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`)
-
-### Testing Conventions
-
- **Always run `make pytest-cov` before pushing** — CI enforces 100%
-  coverage and will fail the PR if any lines are uncovered. The pre-push
-  hook only validates Vikunja task existence, not tests.
- **Never use `is True`/`is False` identity checks on API response
-  values** — many APIs return boolean values as strings (`"true"`/
-  `"false"`). Use string comparison or truthy/falsy helpers instead.
- **Always mock `time.sleep` and `time.monotonic` in unit tests** — real
-  sleep calls make tests slow and exceed test speed limits. Use
-  `@patch("time.sleep")` and `@patch("time.monotonic")` decorators.
- **Extract complex inline shell from workflows to tested Python tools**
-  — SSH loops, curl polling, docker exec chains, and multi-line
-  if/then/else shell blocks should be Python scripts in `scripts/`
-  with unit tests. Simple variable checks and venv activation are fine
-  as inline shell.
-
-### Container-Level Fix Verification (Mandatory)
-
-**Rule:** Before pushing any fix that modifies container state (CA certs,
-config files, installed packages, daemon restarts), reproduce the exact
-sequence locally with the actual Docker image. Do not push to CI as the
-first test.
-
-This is a hard rule, not a suggestion. CI cycles take 20+ minutes and
-ephemeral staging VMs are destroyed after each run, making interactive
-debugging impossible. A local reproduction takes 30 seconds and catches
-silent failures immediately.
-
-**Procedure:**
-1. `docker pull <actual_image>`
-2. `docker run -d --name <test> ...` and wait for it to start
-3. Run the exact commands from the Ansible task or script
-4. Verify the state change took effect
-5. Clean up: `docker rm -f <test>`
-
-### Verified State Modification (Mandatory)
-
-Ansible tasks that modify container state with `changed_when: false`
-MUST include a post-task verification step that confirms the state
-change took effect. `changed_when: false` suppresses both change
-detection AND failure visibility — a task can silently do nothing and
-report `ok`.
-
-## Ansible Role Structure
-
-```text
-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 only create files)
- On Arch Linux, `rootless_docker.yml` fetches the rootless setup scripts
-  (`dockerd-rootless-setuptool.sh`, `dockerd-rootless.sh`) from `moby/moby` `contrib/`
-  at a pinned ref (`gitea_runner_rootless_scripts_ref`) into `/usr/bin` and installs
-  `rootlesskit` — Arch's `docker` package ships neither. These fetch tasks run
-  regardless of `docker_rootless_setup` so CI exercises them on the archlinux platform.
-  See ADR-011 in the decision log.
-
-## 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
-
-```text
-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 validate 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 across all projects):
-
-| 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 (validate, molecule-tests, release-and-maintain) |
-| `molecule-runner` | Run 7 molecule scenarios across 4 platforms, report pass/fail |
-| `dep-upgrader` | Python + Ansible dependency upgrades with molecule verification |
-| `doc-sync-specialist` | 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 (validate, molecule-tests, release-and-maintain) | `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-sync-specialist` | 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 minor 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 as
-a step in `detect-and-configure` 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"`.
-
@@ -1,488 +0,0 @@
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-## [0.21.0] - 2026-08-09
-
-### Features
-
- *(healthcheck)* Add two-tier disk prune with critical threshold
-
-## [0.20.0] - 2026-08-09
-
-### Features
-
- *(healthcheck)* Add two-tier disk prune with critical threshold
-
-## [0.19.0] - 2026-08-08
-
-### Features
-
- Use Gitea mirror for Ansible collection installs
-
-## [0.18.8] - 2026-08-06
-
-### Bug Fixes
-
- Pin containerd.io to compatible version for Docker 28.x
-
-
-## [0.18.7] - 2026-08-06
-
-### Bug Fixes
-
- Move StartLimit to [Unit] and make prune timer reload conditional
-
-## [0.18.6] - 2026-08-05
-
-### Bug Fixes
-
- Pre-configure daemon.json before rootless setuptool + add DBUS_SESSION_BUS_ADDRESS
-
-## [0.18.5] - 2026-08-05
-
-### Bug Fixes
-
- Pin Docker 28.x + disable containerd snapshotter + tune prune/disk
-
-## [0.18.4] - 2026-08-05
-
-### Bug Fixes
-
- Harden rootless Docker daemon resilience on CI runners
-
-## [0.18.3] - 2026-08-04
-
-### Bug Fixes
-
- Switch default network driver to slirp4netns (pasta TCP RST bug)
-
-## [0.18.2] - 2026-07-16
-
-### Bug Fixes
-
- Load tun module and pre-configure systemd override for Arch rootless Docker
-
-## [0.18.1] - 2026-07-16
-
-### Bug Fixes
-
- Fetch rootless Docker scripts on Arch Linux
-
-## [0.18.0] - 2026-07-12
-
-### Features
-
- *(runner)* Enable IPv6 in rootless Docker via pasta network driver
-
-## [0.17.2] - 2026-07-11
-
-### Refactor
-
- Adopt devx v0.40.0
-
-## [0.17.1] - 2026-07-09
-
-### Bug Fixes
-
- Disable IPv6 in rootless Docker daemon on runners
-
-## [0.17.0] - 2026-07-08
-
-### Features
-
- Bump devx to 0.38.0 and migrate to role-based Gitea tokens
-
-## [0.16.0] - 2026-07-07
-
-### Features
-
- Consolidate docs checks into devx-docs-check target
-
-### Bug Fixes
-
- Replace --strict with --verify for sync_wiki
-
-## [0.15.0] - 2026-07-06
-
-### Features
-
- Adopt documentation-as-code enhancements from devx
-
-## [0.14.4] - 2026-07-06
-
-### Refactor
-
- Remove project-specific references from grm
-
-## [0.14.3] - 2026-07-06
-
-### Refactor
-
- Rename PyPI package from gitea-runner-manager to grm
-
-## [0.14.2] - 2026-07-05
-
-### Bug Fixes
-
- Add pre-commit hooks for quality gates matching CI
-
-## [0.14.1] - 2026-07-01
-
-### Refactor
-
- Align venv management to devx.mak targets
-
-## [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
@@ -1,60 +0,0 @@
-# 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:
-
-```text
-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:
-
-```text
-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
@@ -1,232 +0,0 @@
-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  oblachno-oss
-
-     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  oblachno-oss
-     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>.
@@ -1,235 +0,0 @@
-.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 check-api-identity-checks
-.PHONY: configure-gitea-pypi
-.PHONY: create-task create-pr push-with-pr git-push
-.PHONY: check-docs docs-check
-
-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/grm
-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)
-# Fallback: when the venv doesn't exist yet, try system python3 or /opt/venv.
-# In CI, /opt/venv has devx pre-installed; locally, devx may be in system python.
-ifeq ($(strip $(DEVX_MAK)),)
-DEVX_MAK := $(shell python3 -c \
-	"from pathlib import Path; import devx; print(Path(devx.__file__).parent / 'make' / 'devx.mak')" \
-	2>/dev/null)
-endif
-ifeq ($(strip $(DEVX_MAK)),)
-DEVX_MAK := $(shell /opt/venv/bin/python -c \
-	"from pathlib import Path; import devx; print(Path(devx.__file__).parent / 'make' / 'devx.mak')" \
-	2>/dev/null)
-endif
-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
-# (validate job steps: detect-changes, discover-runners, pr-review;
-#  release-and-maintain job steps: sync-wiki, badges)
-# badges step 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 validate CI 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; \
-		_TOKEN="$$CI_GITEA_API_TOKEN"; [ -z "$$_TOKEN" ] && _TOKEN="$$DEVELOPER_GITEA_API_TOKEN"; [ -z "$$_TOKEN" ] && _TOKEN="$$CI_GITEA_TOKEN"; \
-		if [ -n "$$_TOKEN" ]; then export PIP_EXTRA_INDEX_URL="https://$$CI_GITEA_USERNAME:$${_TOKEN}@git.oblachno.oblachno.fyi/api/packages/oblachno-oss/pypi/simple/"; git config --global url."https://$$CI_GITEA_USERNAME:$${_TOKEN}@git.oblachno.oblachno.fyi/".insteadOf "https://git.oblachno.oblachno.fyi/"; fi; \
-		pip install -e .$(if $(EXTRAS),[$(EXTRAS)],); \
-	else echo "[setup-image] /opt/venv not found — falling back to setup-ci"; $(MAKE) setup-ci; fi
-
-# venv, .env, activate-scripts, and PIP_INSTALL are provided by devx.mak
-# (devx-venv, devx-env, devx-activate-scripts, DEVX_PIP_INSTALL)
-# Aliases for convenience and backward compatibility:
-.PHONY: venv activate-scripts
-PIP_INSTALL := $(DEVX_PIP_INSTALL)
-venv: devx-venv
-.env: devx-env
-activate-scripts: devx-activate-scripts
-
-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/grm --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:
-	_TOKEN="$$CI_GITEA_API_TOKEN"; [ -z "$$_TOKEN" ] && _TOKEN="$$DEVELOPER_GITEA_API_TOKEN"; [ -z "$$_TOKEN" ] && _TOKEN="$$CI_GITEA_TOKEN"; \
-	if [ -z "$$_TOKEN" ]; then echo "[configure-gitea-pypi] Gitea API token not set — skipping (devx must be on public PyPI)"; exit 0; fi; \
-	echo "[configure-gitea-pypi] Gitea PyPI registry configured (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 check-api-identity-checks check-ansible-no-log check-ansible-no-state-absent-on-db check-ansible-patterns check-jinja-expr check-ansible-set-fact-to-json
-
-check-api-identity-checks:
-	@$(BIN)/python -m devx.tools.check_api_identity_checks
-
-check-ansible-no-log:
-	@echo "[check-ansible-no-log] Checking Ansible tasks for missing no_log on secret-handling tasks..."
-	@$(BIN)/python -m devx.tools.check_ansible_no_log
-	@echo "[check-ansible-no-log] Passed."
-
-check-ansible-no-state-absent-on-db:
-	@echo "[check-ansible-no-state-absent-on-db] Checking for state: absent on DB data directories..."
-	@$(BIN)/python -m devx.tools.check_ansible_no_state_absent_on_db
-	@echo "[check-ansible-no-state-absent-on-db] Passed."
-
-check-ansible-patterns:
-	@echo "[check-ansible-patterns] Checking for dangerous failure-masking patterns..."
-	@$(BIN)/python -m devx.tools.check_ansible_patterns
-	@echo "[check-ansible-patterns] Passed."
-
-check-jinja-expr:
-	@echo "[check-jinja-expr] Validating Jinja2 expressions in Ansible files..."
-	@$(BIN)/python -m devx.tools.check_jinja_expr
-	@echo "[check-jinja-expr] Passed."
-
-check-ansible-set-fact-to-json:
-	@echo "[check-ansible-set-fact-to-json] Checking set_fact tasks for to_json misuse..."
-	@$(BIN)/python -m devx.tools.check_ansible_set_fact_to_json
-	@echo "[check-ansible-set-fact-to-json] Passed."
-
-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
-
-# --- Documentation checks (via devx.mak fragment) -----------------------------
-check-docs: devx-check-docs
-docs-check: devx-docs-check
@@ -1,406 +0,0 @@
-# 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/a9578eaecfc5bba4f295c16f9045be6f094d637d/coverage.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
-[![Tests](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/a9578eaecfc5bba4f295c16f9045be6f094d637d/tests.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
-[![Docs](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/a9578eaecfc5bba4f295c16f9045be6f094d637d/docs.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki)
-[![Code Quality](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/a9578eaecfc5bba4f295c16f9045be6f094d637d/quality.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/actions)
-[![Version](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/a9578eaecfc5bba4f295c16f9045be6f094d637d/version.svg)](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/releases)
-[![Python](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/raw/commit/a9578eaecfc5bba4f295c16f9045be6f094d637d/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 grm --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 grm
-```
-
-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 entirely (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 multiple 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/grm/`) — 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.
-
-```text
-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.
@@ -1,3 +0,0 @@
-# Troubleshooting
-
-See the [Troubleshooting guide](https://git.oblachno.oblachno.fyi/oblachno-oss/grm/wiki/Troubleshooting) in the wiki.
@@ -1,44 +0,0 @@
---
- 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-' ~ gitea_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-' ~ gitea_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 gitea_runner_skip_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-' ~ gitea_runner_name) }}"
-      environment:
-        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
-      when: systemd_available.stat.exists
-      changed_when: true
@@ -1,28 +0,0 @@
---
- 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-' ~ gitea_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-' ~ gitea_runner_name) }}"
-      environment:
-        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
-      when: systemd_available.stat.exists
-      changed_when: true
@@ -1,3 +0,0 @@
---
-# Default variables for all hosts
-ansible_python_interpreter: /usr/bin/python3
@@ -1,6 +0,0 @@
---
- name: Install Gitea Actions runner
-  hosts: all
-  become: true
-  roles:
-    - role: gitea_runner
@@ -1,13 +0,0 @@
-# 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
@@ -1,194 +0,0 @@
---
- 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-' ~ gitea_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-' ~ gitea_runner_name) }}"
-      environment:
-        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
-      when: gitea_runner_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-' ~ gitea_runner_name) }}"
-      environment:
-        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
-      when: gitea_runner_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-' ~ gitea_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-' ~ gitea_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-' ~ gitea_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 gitea_runner_skip_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-' ~ gitea_runner_name) }}"
-      environment:
-        XDG_RUNTIME_DIR: "/run/user/{{ gitea_runner_uid | default('') }}"
-      when: gitea_runner_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-' ~ gitea_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-' ~ gitea_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-' ~ gitea_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-' ~ gitea_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/' ~ gitea_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-' ~ gitea_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-' ~ gitea_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-' ~ gitea_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-' ~ gitea_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-' ~ gitea_runner_name) }}"
-        state: absent
-        remove: true
-      when: gitea_runner_remove_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-' ~ gitea_runner_name) }}/.local/share/docker"
-        state: absent
-      when: not (gitea_runner_remove_user | default(true))
-      failed_when: false
-
-    - name: Remove act cache when user is kept
-      ansible.builtin.file:
-        path: "{{ gitea_runner_home | default('/home/grm-' ~ gitea_runner_name) }}/.cache/act"
-        state: absent
-      when: not (gitea_runner_remove_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-' ~ gitea_runner_name) }}/.config/systemd/user"
-        state: absent
-      when: not (gitea_runner_remove_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-' ~ gitea_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-' ~ gitea_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/' ~ gitea_runner_name) }}"
-        state: absent
-
-    - name: Remove runner config directory
-      ansible.builtin.file:
-        path: "{{ gitea_runner_config_dir | default('/etc/gitea-runner/' ~ gitea_runner_name) }}"
-        state: absent
@@ -1,11 +0,0 @@
---
-collections:
-  - name: community.general
-    type: url
-    source: https://git.oblachno.oblachno.fyi/api/packages/emil/generic/ansible-collections/13.1.0/community-general-13.1.0.tar.gz
-  - name: ansible.posix
-    type: url
-    source: https://git.oblachno.oblachno.fyi/api/packages/emil/generic/ansible-collections/2.2.1/ansible-posix-2.2.1.tar.gz
-  - name: community.docker
-    type: url
-    source: https://git.oblachno.oblachno.fyi/api/packages/emil/generic/ansible-collections/5.2.1/community-docker-5.2.1.tar.gz
@@ -1,48 +0,0 @@
---
- 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
@@ -1,137 +0,0 @@
---
-gitea_runner_version: "2.0.1"
-gitea_runner_labels: "docker,ubuntu-latest:docker://runner-images:ubuntu-26.04"
-gitea_runner_skip_registration: false
-
-# Force re-registration even if .runner file exists.
-# Use this when Gitea no longer recognizes the runner (e.g., after a Gitea
-# server restore/reinstall or when the runner record was deleted from the
-# admin UI). The existing .runner file is removed and a new registration is
-# performed. Requires registration_token.
-gitea_runner_force_reregister: false
-
-# Per-runner user (rootless isolation)
-gitea_runner_user_prefix: "grm-"
-gitea_runner_base_home: "/home"
-gitea_runner_service_user: "{{ gitea_runner_user_prefix }}{{ gitea_runner_name }}"
-gitea_runner_home: "{{ gitea_runner_base_home }}/{{ gitea_runner_service_user }}"
-
-# Base paths (instance-scoped via gitea_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 }}/{{ gitea_runner_name }}"
-gitea_runner_config_dir: "{{ gitea_runner_base_config_dir }}/{{ gitea_runner_name }}"
-gitea_runner_binary_path: "/usr/local/bin/gitea_runner"
-
-# Prune configuration
-gitea_runner_prune_until: "24h"
-# Every 6 hours — daily is insufficient for CI runners that build dozens
-# of images per day. Accumulation between daily runs can trigger Docker
-# daemon instability (containerd snapshotter GC holds locks, blocking
-# container operations).
-gitea_runner_prune_schedule: "*-*-* 00/6:00:00"
-gitea_runner_prune_label: "gitea-runner=true"
-
-# Service configuration
-gitea_runner_service_restart_sec: "5"
-
-# Health check configuration
-# 2min interval — catches hung daemons before multiple CI jobs fail between checks.
-# The previous 5min interval was too coarse: a stuck daemon could fail 3+ molecule
-# jobs in the window between healthcheck runs.
-gitea_runner_healthcheck_interval: "2min"
-gitea_runner_healthcheck_boot_delay: "2min"
-gitea_runner_healthcheck_disk_threshold: 70
-# When disk reaches this level, prune EVERYTHING (no until-filter) — the
-# runner is dangerously full and the gentle until=1h prune isn't enough.
-# This removes all stopped containers and unused images regardless of age.
-# At 75%+, molecule containers fail with "container is not running" because
-# overlay2 runs out of space under parallel DinD load.
-gitea_runner_healthcheck_disk_critical: 75
-gitea_runner_healthcheck_script_path: "{{ gitea_runner_config_dir }}/healthcheck.sh"
-
-# Auto-recovery: when the healthcheck detects an unregistered runner, it
-# can automatically re-register if a Gitea API token is provided.
-# The token needs admin or org-level access to fetch registration tokens.
-# Stored in a file readable by the runner user (mode 0400).
-# Set to empty string to disable auto-recovery (manual re-registration required).
-gitea_runner_auto_recover_api_token: ""
-
-# Cooldown file to prevent auto-recovery loops (e.g., if Gitea is down).
-# The healthcheck writes a timestamp to this file after a re-registration
-# attempt and skips further attempts for the cooldown period.
-gitea_runner_auto_recover_cooldown_sec: 300
-
-# Docker daemon resilience settings (applied to daemon.json).
-# live-restore: containers survive daemon restarts — prevents stuck container
-#   states when the healthcheck restarts a hung daemon.
-# shutdown-timeout: grace period (seconds) for containers to stop on daemon
-#   shutdown/restart. Default 15s is too short for DinD containers with nested
-#   processes (molecule tests). 30s gives SIGTERM time to propagate.
-# max-concurrent-downloads/uploads: limits parallel transfers to reduce daemon
-#   memory pressure when multiple CI jobs pull images simultaneously.
-# default-ulimits: prevents FD exhaustion in container processes.
-gitea_runner_docker_live_restore: true
-gitea_runner_docker_shutdown_timeout: 30
-gitea_runner_docker_max_concurrent_downloads: 3
-gitea_runner_docker_max_concurrent_uploads: 3
-gitea_runner_docker_default_nofile: 65536
-
-# 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_runner_admin_token: ""
-
-# Removal defaults
-gitea_runner_remove_systemd_template: true
-gitea_runner_remove_user: true
-
-# Runner configuration
-gitea_runner_log_level: "info"
-gitea_runner_container_label: "gitea-runner=true"
-gitea_runner_file: ".runner"
-
-# Containerd version pinning — Docker 28.x vendors containerd v2.1.x internally.
-# containerd.io >= 2.3 ships a shim that returns a protobuf BootstrapResult which
-# Docker 28.x's vendored containerd code cannot parse, causing:
-#   "failed to create TTRPC connection: unsupported protocol: \b\x03\x12Yunix"
-# When Docker 29+ is installed (it vendors containerd 2.3+), this pin is not needed.
-# Set to "" to skip the compatibility check and allow any containerd.io version.
-gitea_runner_containerd_max_compatible_major: 2
-gitea_runner_containerd_max_compatible_minor: 2
-
-# Docker installation (for rootless dependencies)
-gitea_runner_docker_gpg_key_path: "/etc/apt/keyrings/docker.gpg"
-gitea_runner_docker_apt_arch: "{{ 'amd64' if ansible_facts['architecture'] == 'x86_64' else ansible_facts['architecture'] }}"
-gitea_runner_docker_apt_source_line: >-
-  deb [arch={{ gitea_runner_docker_apt_arch }} signed-by={{ gitea_runner_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)
-gitea_runner_docker_rootless_setup: true
-
-# Rootless Docker helper scripts (dockerd-rootless-setuptool.sh / dockerd-rootless.sh).
-# Arch Linux's "docker" package does not ship these (unlike Debian's docker-ce-rootless-extras),
-# and no official Arch package provides them. They are fetched from the upstream moby/moby
-# "contrib/" directory at the git ref below. The scripts are stable bash wrappers that are
-# version-agnostic with respect to the dockerd binary, so a pinned ref is safe.
-gitea_runner_rootless_scripts_ref: "v28.5.1"
-# Install dir MUST match the location of the "docker" / "dockerd" / "rootlesskit" binaries so
-# that dockerd-rootless-setuptool.sh (which derives BIN from its own dirname) finds them co-located.
-gitea_runner_rootless_scripts_install_dir: "/usr/bin"
-
-# Rootless Docker network driver: "slirp4netns" (default) or "pasta" (IPv6 support)
-# slirp4netns is the default because pasta has a TCP proxy bug that sends RST
-# packets with wrong sequence numbers, breaking TCP connections from Docker
-# containers to external hosts. slirp4netns doesn't have IPv6 support.
-# See: https://bugs.passt.top/show_bug.cgi?id=52
-gitea_runner_docker_rootless_net_driver: "slirp4netns"
-
-# IPv6 subnet for rootless Docker containers (ULA range, not routable on internet)
-gitea_runner_docker_ipv6_cidr: "fd00:dead:beef::/48"
-
-# Pre-pull Docker images that CI runners need (avoids pulling on every CI run).
-# The runner container image (ci-full) is large (~3.3GB) and the healthcheck's
-# disk-space prune only removes dangling images, so pre-pulled tagged images persist.
-# Set to [] to skip pre-pulling. Images are pulled as the runner user via rootless Docker.
-gitea_runner_pre_pull_images: []
--- a/Show More
+++ b/Show More