rtmx-ai / rtmx / 27844337053

83%

push

github

feat(verify): configurable requirement-ID pattern, multi-segment default (REQ-VERIFY-011) (#124)

The results validator enforced a fixed `^REQ-[A-Z]+-[0-9]+$`, which rejected
alphanumeric and multi-segment category prefixes (e.g. REQ-E2E-010,
REQ-INFRA-DT-002, REQ-MODE-S-006). Because this is a hard error in the
cross-language `rtmx verify --results` path, projects using such IDs (e.g. the
Phoenix radar RTM) could never close the verification loop even with otherwise
well-formed markers.

- Broaden the built-in default to `^REQ-[A-Z][A-Z0-9]*(-[A-Z0-9]+)*-[0-9]+$`,
  accepting single- and multi-segment uppercase-alphanumeric category prefixes
  while still rejecting malformed IDs (lowercase, missing number, digit-leading
  category). Applied consistently to the results validator, the marker spec
  validator, the pkg/rtmx test marker, and the adapter extraction regex.
- Add `rtmx.req_id_pattern` config to override the pattern for results
  validation -- the validation-layer complement to the configurable dimension
  vocabularies of REQ-VERIFY-010. An invalid pattern is reported once and falls
  back to the default rather than aborting.
- Tests: default + override behavior (internal/results/schema_reqid_test.go);
  multi-segment adapter extraction cases.

Backward-compatible: every previously valid ID still matches.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

41 of 48 new or added lines in 4 files covered. (85.42%)

16423 of 19820 relevant lines covered (82.86%)

29.82 hits per line