fix(engine): FILE-MISSING named the class for a trait-sourced requirement
security -> SECURITY.md read as "missing required file for class `standalone`", sending the operator to a class definition that never listed the requirement. requirementsFor now carries each required file's origin (class vs. trait) and checkRequiredFiles names whichever actually required it. Failing test written first per the Iron Law. No release forced by this alone. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuWwACwhun35j52AnTxRKV
This commit is contained in:
parent
f422b63bb3
commit
e5cd1bfaaf
4 changed files with 35 additions and 6 deletions
|
|
@ -6,6 +6,15 @@ versioning is [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|||
|
||||
## [Unreleased]
|
||||
|
||||
### Fixed
|
||||
|
||||
- **`FILE-MISSING` named the class even when a TRAIT required the file.**
|
||||
`security` → `SECURITY.md` read as "missing required file for class
|
||||
`standalone`", sending the operator looking for a requirement the class
|
||||
never listed. `requirementsFor` now carries the source (`class` vs. `trait`)
|
||||
alongside each required file, and the message names whichever actually
|
||||
required it. 245 tests, from 243.
|
||||
|
||||
## [0.11.1] — 2026-08-13
|
||||
|
||||
### Fixed
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue