bug: req trace reports wrong test IDs for REQ-NN-002 (shows TEST-NN-020 twice instead of TEST-NN-002a, TEST-NN-002b)

[tbitcs]

Summary

specsmith req trace reports incorrect test IDs for REQ-NN-002, showing TEST-NN-020, TEST-NN-020 (duplicated) instead of the correct TEST-NN-002a, TEST-NN-002b.

Problem

The docs/tests/nn.yml file contains two test cases correctly mapped to REQ-NN-002:

- id: TEST-NN-002a
  requirement_id: REQ-NN-002

- id: TEST-NN-002b
  requirement_id: REQ-NN-002

However specsmith req trace outputs:

✓ REQ-NN-002  → TEST-NN-020, TEST-NN-020

TEST-NN-020 is the HuggingFace LogitsProcessor test — completely unrelated to REQ-NN-002 (Admissibility Oracle Correctness).

Expected behavior

✓ REQ-NN-002  → TEST-NN-002a, TEST-NN-002b

Impact

• specsmith req orphans correctly reports "No orphaned test references" (so orphan detection is unaffected)
• specsmith audit correctly reports "All 20 accepted REQ(s) have test coverage"
• Only the req trace display output is wrong
• Misleading for audit trail and patent provenance documentation

Environment

• specsmith 0.11.5
• Python 3.12, Windows 11
• Test IDs with letter suffixes (e.g. TEST-NN-002a, TEST-NN-002b) — possible parsing issue with alphanumeric suffixes?

[tbitcs]

Fixed in PR #185 (squash-merged to develop). Root cause: _TEST_ID_PATTERN\ word boundary failure on letter-suffix IDs.