Repository navigation
v1.16.0
Highlight: a change's non-Markdown artifacts are visible. A schema sets each artifact's filename through generates:, and not every artifact is Markdown — event-driven requires asyncapi.yaml. spek discovered only root *.md and the specs/ tree, so such a change rendered every tab except the one its schema asks for.
- Root
.yaml/.yml/.jsonfiles are artifacts, shown as syntax-highlighted text. The tab is named for the file's stem with a format badge, using the full filename only when a Markdown artifact shares it. Thanks to @nthansen (Norman Hansen) (#50) - They sort into their schema position, count in the change-list badge, are reachable by search, and refresh live on edit — on every surface
- Discovery stays root-only and skips dotfiles, so
.openspec.yamland subdirectory files never become tabs - Code fences in
proposal.md/design.mdare highlighted too. A fence with no language stays plain - Internal:
@spekjs/core1.11.0 adds the"data"kind and the shared file listing behind count, search and discovery