probe 0.2.0: write your own cases
GitHub releaseSource-backed
Why it matters: The first release HEY has recorded for this project.
Operators can now work a job without an AI key, by writing cases themselves. Added · probe case new writes a case that already meets the job's structural rules, with the fixture's helper functions and their docs listed in it. · probe case check <file...> runs the rule check and… Show allShow less
- Operators can now work a job without an AI key, by writing cases themselves. Added
- probe case new writes a case that already meets the job's structural rules, with the fixture's helper functions and their docs listed in it.
- probe case check <file...> runs the rule check and a local run on your case files, says which test failed and why, and exits 1 when a case would be rejected, so it can gate CI.
- probe work --case runs and submits your files instead of the agent's or the seed cases.
- probe job prints a job's brief: chain and contract…
Record ship:58364439… · HEY counts it as building; it does not judge the release’s quality.
Release, read from the team’s GitHub · no deployment linked
- What it names
- The team’s release names it: “probe 0.2.0: write your own cases” (v0.2.0).
- Stage
- A release is code the team published; HEY has not observed it deployed unless a link below says so.
- Reported by
- Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
- Release and deployment
- Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
- Activity
- No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
- When
- The source dates it 2026-11-19 12:02 UTC; HEY first knew on 2026-11-19.
- Not known
- HEY does not hold the commit the release was cut from.
- HEY has not observed a deployment of this change.
- Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
Evidence: ship record
A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.