1a29ff50b2
Some checks failed
planctl / build-test (1.22, macos-latest) (push) Has been cancelled
planctl / build-test (1.22, ubuntu-latest) (push) Has been cancelled
planctl / build-test (1.22, windows-latest) (push) Has been cancelled
planctl / build-test (stable, macos-latest) (push) Has been cancelled
planctl / build-test (stable, ubuntu-latest) (push) Has been cancelled
planctl / build-test (stable, windows-latest) (push) Has been cancelled
planctl / bench (push) Has been cancelled
Pre-PR codex review found a gap in the R1.1 annotation grammar handling: * scanTagAfterOpener treated the first '_' after an opener as the closing delimiter regardless of paren nesting, so a legitimate tag like `_Requirements: R1.1 (foo_bar)_` would incorrectly close at the underscore inside the annotation. * parseTagBody split on every ', ' regardless of paren context, so `_Requirements: R1.1 (note, with comma), R2.1_` split into three bogus refs. Both are per-spec: PRD R1.1 defines annotation body as 'arbitrary non-) characters', which includes _ and ,. The state machine and the ref-splitter are now paren-depth-aware; regression tests added for both cases. |
||
|---|---|---|
| .. | ||
| jj-commitd | ||
| planctl | ||