Skip to content

ci: add the intent contract check against the playbook binary - #28

Merged
igorjs merged 1 commit into
mainfrom
ci/intents-contract
Oct 13, 2026
Merged

igorjs merged 1 commit into
mainfrom
ci/intents-contract

Conversation

@igorjs

@igorjs igorjs commented Oct 13, 2026

Copy link
Copy Markdown
Member

Summary

The skills, commands and agents here call intents from the playbook binary, and nothing tells us when a binary release drops one. This check catches it on every PR and once a day.

What Changed

  • intents.json lists the 48 intents the plugin relies on, named like the entries of playbook tools map. Each entry has a required flag.
  • scripts/check-intents.sh validates the file first (sorted, unique, kebab-case ids, boolean required). Given a binary, it compares the list with tools map --json. A missing intent prints a warning, and fails the run only when it's marked required.
  • A new contract workflow runs on pull requests, the merge queue, by hand, and daily at 06:41 UTC. It downloads the latest stable playbook release for linux musl, checks it against SHA256SUMS, runs shellcheck on the scripts, then runs the check. Egress is locked to GitHub hosts through harden-runner.
  • The README gets a short section on the contract and how to run the script by hand.

Notes for reviewers

  • Every intent is required: false for now. A missing intent only warns until we flip one to true.
  • If the released binary has no tools map command yet, the script prints a WARN and exits 0. The job stays green until a release ships the map.
  • No test files here. The workflow run on this PR exercises the script, and shellcheck lints it.

Signed-off-by: igorjs <2278164+igorjs@users.noreply.github.com>
@igorjs
igorjs marked this pull request as ready for review October 13, 2026 08:32
@igorjs
igorjs added this pull request to the merge queue Oct 13, 2026
Merged via the queue into main with commit cc0949a Oct 13, 2026
9 checks passed
@igorjs
igorjs deleted the ci/intents-contract branch October 13, 2026 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant