Two blind spots in one rule, on two different axes
The build rule 'no TMS imports a sibling TMS' skipped any file whose extension it did not recognise, and matched only `import ... from` in the files it did read. A .rs file carrying a deliberate sibling import built green and was counted and published as example source; separately, `export ... from` and a bare `import "./x"` were invisible in JavaScript, the language the rule was written for.
判斷軌跡
- 何事 · 測試unknown-input-treated-as-nothing-to-report2026-08-06 10:55 → 至今信心 0.99
- 何事 · 測試one-syntax-standing-in-for-a-relation2026-08-06 10:55 → 至今信心 0.99
- 為何 · 測試enumeration-expanded-rather-than-rooted-out2026-08-06 10:55 → 至今信心 0.95
可執行見證
尚無。這份案卷還沒有一個修正前失敗、修正後通過的測試，所以它不是已驗證知識。
證據
- observation · 2026-08-06 10:55
A .rs file under an example's TMS/ containing `use crate::TMS::reporters::json` built green; the example's reported file count went 13 -> 14 and line count 509 -> 514, so it was published as source while exempt from the rule.
- observation · 2026-08-06 10:55
Measured on the same file, one form at a time: `import {x} from "./y"` caught; `export {x} from "./y"` not caught; `export * from "./y"` not caught; `import "./y"` not caught. After the repair all four are caught and `export const safe = 1;` is not.