lazy-fortran/fortcov

AI Summary: This enhancement proposes a new CI job to automatically validate FortCov's markdown output against a trusted pycobertura baseline. The job will involve building with coverage, generating Cobertura XML, rendering markdown via pycobertura, running FortCov, and then comparing key metrics (line rate, totals per file) to fail the build on any detected deltas.

AI Summary: The issue addresses fragmented and confusing documentation for the coverage workflow, where quick start guides contradict detailed instructions regarding manual `gcov`. The proposed solution is to consolidate all coverage workflow guidance into a single canonical document under `doc/`, linked from the README, clearly outlining both the current bridge script and a future built-in auto-gcov path, ensuring all examples are consistent and runnable.

AI Summary: This tech-debt issue addresses the incomplete Meson build system support within the project, which currently includes a `meson.build` file marked as an incomplete subset and a `build_meson/` directory. The goal is to either fully implement minimal Meson support or relocate the existing Meson scaffolding to an `examples/` directory, clearly marking it as experimental, and updating the documentation accordingly.

AI Summary: This enhancement proposes adding a built-in `--gcov` mode to FPM to streamline code coverage analysis. Currently, users rely on external scripts to bridge FPM build layouts and generate `.gcov` files. The new mode would automatically detect FPM build directories, run `gcov` within them, and collect relevant `.gcov` files for analysis, using an existing script as a reference.

AI Summary: This GitHub issue identifies a discrepancy where the project's README example shows a textual summary block, but the actual markdown output is currently table-only. The proposed solution involves either enhancing the markdown reporter to include the summary header or updating the README example to reflect the current output. Additionally, the issue suggests adding a verified example file and a test to prevent future inconsistencies.

AI Summary: This issue reports two formatting bugs in the CLI output: an unexpected newline character breaking the "Discovery returned X files" message and a duplicate "Build system detected" log line. The proposed solution involves fixing string formatting and ensuring the build system detection is logged only once, along with adding a smoke test to prevent future regressions.

AI Summary: This bug report identifies an issue where filenames in reports and runtime logs contain duplicated extensions (e.g., `.f90.f90`) and double slashes in paths, which reduces clarity. The proposed solution involves normalizing filename extraction from `.gcov` output to strip duplicate extensions and tool suffixes, normalizing path joins, and adding comprehensive tests for clean filename rendering.

AI Summary: The GitHub issue highlights a discrepancy between the `fortcov` README and its actual behavior: the documentation promises automatic `gcov` invocation for code coverage, but the tool currently requires `.gcov` files to be pre-generated. This forces users to manually run `gcov` before using `fortcov`. The proposed solutions include either implementing built-in `gcov` invocation within `fortcov` or updating the README to reflect the current manual workflow, along with adding an integration test.

AI Summary: The `fortcov` tool's coverage reports (Markdown, JSON) are incorrectly calculating coverage by counting files instead of actual executable lines. This bug results in all files showing only one statement and an overall 100% coverage, regardless of actual code execution. The proposed solution involves fixing the gcov parsing and aggregation logic to accurately count executable and covered lines, along with adding comprehensive unit and integration tests.