Expand description
The publish milestones a setup check reads back: what the forge and the registry can show, and what only the operator can.
Two milestones have a public read-back: the first version published,
which the registry answers, and an automated release proven, which
the forge answers by a successful publish run on the trunk and a
release beside it. Every registry form no API exposes reads
operator, with the binding’s own read-back check, so a skill
sequences the operator’s steps without guessing where they stand.
Milestones are information: none weighs on the check’s verdict.
SATISFIES setup-proof:the-check-reads-the-publish-milestones
Structs§
- Milestone
- One milestone, as the check reports it.
Constants§
- AUTOMATED_
RELEASE - The milestone for one release through the automated path.
- FIRST_
VERSION - The milestone for the first version on the registry.
Functions§
- observe
- Read every milestone this target’s pair has.