docs: how to expose a programmatic API, and the three gaps writing it found by rjrodger · Pull Request #41 · voxgig/plugin

docs: how to expose a programmatic API from a plugin

claude

committed

fbc1638

prose: the Vale half of the gate, which ran only in CI

claude

committed

b111106

docs: five corrections to the export how-to, and two more gaps recorded

claude

committed

5c1df34

patch: build the lean port with the compiler it pins

claude

committed

022464c

export: split the spec at the LAST slash, so a scoped name has exports

claude

committed

cffa6da

export: a second scalar key on `probe`, and what it actually pins

claude

committed

7e4191b

depend: §11.1's `inst.capability(name)`, and what the corpus had to say

claude

committed

7172ccf

probe: `dep` holds a resource, in the five ports where it did not

claude

committed

2e54073

ci: build the lean port with the compiler it pins

claude

committed

a38ab7d

Navigation Menu

Repository navigation

docs: how to expose a programmatic API, and the three gaps writing it found - #41

docs: how to expose a programmatic API, and the three gaps writing it found#41
rjrodger merged 9 commits into
mainfrom
claude/sekreto-mini-vault-plugin-64l2kt

Commits on Sep 16, 2026

docs: how to expose a programmatic API from a plugin

prose: the Vale half of the gate, which ran only in CI

docs: five corrections to the export how-to, and two more gaps recorded

patch: build the lean port with the compiler it pins

export: split the spec at the LAST slash, so a scoped name has exports

export: a second scalar key on `probe`, and what it actually pins

depend: §11.1's `inst.capability(name)`, and what the corpus had to say

probe: `dep` holds a resource, in the five ports where it did not

ci: build the lean port with the compiler it pins