Menu
Known bugs and quirks in dependencies and tools
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Automated quality check loops with escalation and fix sub-agents
JSON-based end-to-end test format, runner, and mock provider
Jujutsu (jj) skill for the ikigai project
How to write effective Ralph goals for Ikigai-driven workflows
Create and manage Ralph goals from Ikigai using the real ralph-pipeline scripts
Create repositories using the real ralph-pipeline repo-create script
| name | bugs |
| description | Known bugs and quirks in dependencies and tools |
Known issues, quirks, and workarounds for dependencies and tooling used in the ikigai project.
Issue: The lcov --version command reports an incorrect version string that doesn't match the installed package version.
Evidence:
Host system (Debian 13.2):
lcov 2.3.1-1lcov: LCOV version 2.0-1Debian 13.2 container:
lcov 2.3.1-1lcov: LCOV version 2.0-1Root cause: The version string is hardcoded in /usr/lib/lcov/lcovutil.pm:
our $VERSION = "2.0-1";
This hardcoded value is not updated when the package version changes.
Impact:
lcov --version to determine actual lcov versiondpkg -l lcov (Debian/Ubuntu) to get true package version--version may make incorrect decisionsWorkaround: Use package manager to check version instead of binary:
dpkg -l lcov | grep lcov # Shows actual package version
Status: This appears to be an upstream packaging issue in Debian lcov 2.3.1-1.