Repository navigation
v2.31.0
What's new
Features
The ce:compound-refresh skill now declares an argument-hint in its frontmatter, making its $ARGUMENTS interface visible to callers and the OpenCode command surface. This skill accepts a mode:autofix flag and an optional docs/solutions/ scope hint — both are now documented where they can actually be discovered. Beyond the hint itself, this change establishes which frontmatter fields are enforced: a new enforcement column in writing-systematic-skills/references/foundation-conventions.md clarifies that allowed-tools is parsed but not permission-gated, while argument-hint is now subject to content-integrity checking. A new guard fails any skill that references $ARGUMENTS outside fenced code blocks without declaring argument-hint, preventing the gap from recurring. The check correctly strips fenced code blocks first, so skills that merely document $ARGUMENTS in an example are not flagged.
Documentation
A new solutions doc captures the reusable lessons from the npx skills install command rollout (v2.30.0–v2.30.1): how to make a load-side-effect generator testable by exporting the helper and guarding the entrypoint behind import.meta.main; driving the --skill selector from frontmatter name values; two MDX traps (a <name> placeholder in a table cell parses as JSX and breaks the table; copy buttons only attach to fenced code blocks, never inline code in table cells); and verifying rendered docs against built HTML rather than source or a blocking dev server. The doc cross-references the related MDX, codegen, and verification docs rather than duplicating them.
Continuous Integration
The release pipeline no longer fails when the release-notes narration dispatch confirmation times out. Previously, scripts/dispatch-release-notes.sh would exit 1 if it could not confirm the dispatched Fro Bot run within the poll budget — even though the dispatch had already succeeded and the narration had run. This happened on v2.30.1: the release published and the body was narrated correctly, but the job showed red because GitHub surfaced the dispatched run after the poll window closed. A successful gh workflow run call means the dispatch was accepted; failing to observe the run is an observability gap, not a dispatch failure. The confirmation timeout now emits a ::warning:: and exits 0. The poll budget was also bumped from 90s to 180s to reduce the race for future releases.
Also in this release
- deps:
fro-bot/agentupdated to v0.55.6 (three security hardening fixes: IPv6 literal egress bypass, DNS resolution timeout, and compose topology guard).