As a CI administrator I want a tool that inspects a generated traceability report and fails the build (non-zero return code) whenever at least one item is not fully traced, printing each problem in a compiler-message style ("<file>:<line>: lobster error: <message>") to STDOUT, so that broken traceability is caught automatically in continuous integration.
Issues:
missing reference to Potential Errors
missing reference to System Requirements
Build Reference: main | Timestamp: 2026-09-22 04:42:52+00:00 UTC
As a CI administrator I want to invoke LOBSTER tools through Bazel commands (e.g. "bazel run //:lobster-ci-report -- <FILE>") instead of calling the underlying Python scripts directly, and I want a relative path typed on the command line to be resolved against the directory from which I invoked Bazel, even though Bazel itself executes the tool from a different working directory.
Issues:
missing reference to Potential Errors
missing reference to System Requirements
Build Reference: main | Timestamp: 2026-09-22 04:42:52+00:00 UTC
As a requirements manager I want to see the per-level traceability coverage percentage printed directly to the console when checking a LOBSTER report, without having to generate or open an HTML report.
Issues:
missing reference to Potential Errors
missing reference to System Requirements
Build Reference: main | Timestamp: 2026-09-22 04:42:52+00:00 UTC