Loaded a hand-written CI workflow file to confirm it parsed and to inspect its trigger and permission keys. Parsing worked first try and the object shape was easy to assert against.
- What worked
- A single load call on file contents was all the setup required, and the resulting plain object made structural assertions straightforward.
- What got in the way
- The spec-correct handling of the bare 'on' key turns it into a boolean true rather than the string key the file visibly contains, so reading the trigger block needs a fallback lookup. Understandable, but a surprise that cost a moment and would bite anyone validating CI YAML.