@@ -4,6 +4,7 @@ title: "A code's theory NAME must not equal its CATEGORY"
 area: codereg
 section: "Pitfalls found more than once (check for siblings)"
 paths: [".edml"]
+issues: []
 ---
 **A code's theory NAME must not equal its CATEGORY.** `CalcEd::
 getTheoryName()` reverses `populateTheories()`'s display convention —
 
@@ -4,6 +4,7 @@ title: "A combo whose default is a bare integer opens BLANK when the list is bui
 area: codereg
 section: "Pitfalls found more than once (check for siblings)"
 paths: ["tests/dialogs"]
+issues: []
 ---
 **A combo whose default is a bare integer opens BLANK when the list is
 built conditionally.** `wx.Choice.SetSelection()` ignores an
 
@@ -3,26 +3,18 @@ type: pitfall
 title: "A `.desc` entry's `Begin` wording can silently stop matching between versions of the same code"
 area: codereg
 section: "Pitfalls found more than once (check for siblings)"
-paths: [".desc", "Gaussian-16.expt", "gaussian-03.desc", "gaussian-09.desc", "gaussian-16.desc"]
+paths: ["scripts/parsers/gaussian-16.desc", "scripts/parsers/gaussian-09.desc", "scripts/parsers/gaussian-03.desc", "scripts/parsers/Gaussian-16.expt", "scripts/eccejobmonitor"]
 issues: [80]
 ---
 **A `.desc` entry's `Begin` wording can silently stop matching between
-versions of the same code**, not just between different codes.
-`gaussian-16.desc`'s `MULLIKEN` entry had `Begin= Mulliken atomic
-charges\:`, copied from `gaussian-09.desc`/`gaussian-03.desc` — but
-Gaussian 16 actually prints "Mulliken charges:" (no "atomic").
-`Gaussian-16.expt` (the full-output post-hoc parser) has no Mulliken
-handling of its own, so this property is *only* ever captured live
-via `eccejobmonitor` — the mismatched `Begin` regex meant it was
-silently never extracted, for every G16 job, ever (#80). Same
-no-error/job-completes-normally shape as the other `.desc` bugs
-here. Fixed with an alternation (`Mulliken (atomic )?charges\:`)
-rather than assuming the new wording fully replaced the old one.
-**Caveat that applies to any fix in this family**: because there's
-no reparse-from-saved-output path for a live-monitor-only property,
-fixing the regex does *not* retroactively recover data for
-already-completed jobs parsed under the old pattern — only a fresh
-run monitored under the fixed `.desc` will have the property. If a
-"we fixed the parser but the old job still shows nothing" report
-comes in, check whether the job actually predates the fix before
-assuming it didn't work.
+versions of the same code**, not just between codes. Gaussian 16 prints
+"Mulliken charges:" where 03/09 printed "Mulliken atomic charges:", and
+the G16 `MULLIKEN` entry copied from them never matched. `Gaussian-16.expt`
+has no Mulliken handling, so the property is captured only live by
+`eccejobmonitor`, and it was simply absent for every G16 job. Match both
+wordings (`Mulliken (atomic )?charges`) rather than assuming the new one
+replaced the old.
+
+A live-monitor-only property has no reparse from saved output: a `.desc`
+fix does not recover it for jobs that ran before the fix, only for new
+runs. Check a job's date before concluding a fix did not work.
@@ -4,6 +4,7 @@ title: "A `.desc` entry's `Skip=N` counts the `Begin`-matching line itself"
 area: codereg
 section: "Added from integrating MOPAC (issue #86) — the second code through"
 paths: [".desc", "scripts/eccejobmonitor"]
+issues: [86]
 ---
 **A `.desc` entry's `Skip=N` counts the `Begin`-matching line itself**,
 not N lines *after* it (`scripts/eccejobmonitor`'s Begin/Skip/End
 
@@ -4,6 +4,7 @@ title: "A `.desc` parse-type's `Begin` value is also its hash key, AND its match
 area: codereg
 section: "Added from integrating MOPAC (issue #86) — the second code through"
 paths: [".desc", "scripts/eccejobmonitor"]
+issues: [86]
 ---
 **A `.desc` parse-type's `Begin` value is also its hash key, AND its
 match priority** — `scripts/eccejobmonitor`'s `PDFileRead()` keys its
 
@@ -3,7 +3,8 @@ type: pitfall
 title: "A dialog's choice string must match the generator's expected string EXACTLY, or selecting it silently emits nothing"
 area: codereg
 section: "Pitfalls found more than once (check for siblings)"
-paths: ["ged{03,09,16}theory.py", "scripts/codereg/*theory.py"]
+paths: ["scripts/codereg/ged03theory.py", "scripts/codereg/ged09theory.py", "scripts/codereg/ged16theory.py", "scripts/codereg/*theory.py"]
+issues: []
 ---
 **A dialog's choice string must match the generator's expected string
 EXACTLY, or selecting it silently emits nothing.** The
 
@@ -3,6 +3,8 @@ type: rule
 title: "A hand edit is the case the checker most needs to see and the one it missed"
 area: codereg
 section: "The input checker (`scripts/parsers/verifyinput`, #148)"
+paths: ["scripts/parsers/verifyinput", "src/apps/calced/InputVerifier.C", "src/apps/calced/CalcEd.C", "tests/verify"]
+issues: [148]
 ---
 **A hand edit is the case the checker most needs to see and the one
 it missed.** `processEditCompletion()` wrote Final Edit's result
 
@@ -3,6 +3,8 @@ type: rule
 title: "A \"row of primitives\" check must be anchored"
 area: codereg
 section: "The input checker (`scripts/parsers/verifyinput`, #148)"
+paths: ["scripts/parsers/verifyinput", "src/apps/calced/InputVerifier.C", "src/apps/calced/CalcEd.C", "tests/verify"]
+issues: [148]
 ---
 **A "row of primitives" check must be anchored.** Counting numbers
 found anywhere in the line accepts the *next shell's header*
 
@@ -1,8 +1,10 @@
 ---
 type: rule
-title: "blank, not green"
+title: "An empty finding list leaves the checker's lamp blank, not green"
 area: codereg
 section: "The input checker (`scripts/parsers/verifyinput`, #148)"
+paths: ["scripts/parsers/verifyinput", "src/apps/calced/InputVerifier.C", "src/apps/calced/CalcEd.C", "tests/verify"]
+issues: [148]
 ---
 An empty finding list means *nothing was checked*, and the lamp goes
 **blank, not green**. A light that cannot distinguish "looked and
 
@@ -3,7 +3,8 @@ type: pitfall
 title: "CalcEd used to discard the input generator's error message"
 area: codereg
 section: "Pitfalls found more than once (check for siblings)"
-paths: ["/dev/null"]
+paths: ["src/apps/calced/CalcEd.C"]
+issues: []
 ---
 **CalcEd used to discard the input generator's error message.**
 `execout()` captures the generator's stdout+stderr into `message`, and