Repository navigation
feat(harness): serve the Misoto Harness rules job and its checkers - #30
Merged
Merged
Conversation
Misoto Harness is private and governs repositories under four owners, so a consumer cannot read its workflows or files. This public repository now serves the rules job (`harness-rules.yml`) and every released checker under `harness/checkers/<sha256>.py` (Harness ADR 0004). The job runs a checker only when its sha256 equals the pin in the consumer's managed `.rulesync/checker.json`, so the trust anchor is the governed repository, not this branch. The first checker is 3aac33fa…a633, the one Harness v0.19.0 renders. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
misoto22-release-bot Bot
added a commit
that referenced
this pull request
Nov 8, 2026
🤖 I have created a release *beep* *boop* --- ## [0.10.0](v0.9.0...v0.10.0) (2026-11-08) ### Features * **harness:** serve the Misoto Harness rules job and its checkers ([#30](#30)) ([4aa358d](4aa358d)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: misoto22-release-bot[bot] <330222185+misoto22-release-bot[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Misoto Harness ADR 0004 (owner decision 2026-11-08). Today every governed repository carries its own copy of the 3,800-line Harness checker and a workflow that pins three actions. The release bot may not push workflow files, so each release that changes that workflow leaves about 20 sync PRs red until someone pushes the file by hand. Harness is private, so the shared job has to live in this public repository.
What
.github/workflows/harness-rules.yml, therulesjob, reusable. In order, it:fetch-depth: 0andfilter: blob:none.rulesync/package.json.rulesync/checker.jsonharness/checkers/<sha256>.pyand refuses to run it unlesssha256sum --check --strictpassesMISOTO_HARNESS_BASE_SHA, as the old job didrulesync generate --checkIts
runs-oninput is a JSON array, matchingpr-title.ymlandrelease.yml. The check context isrules / rules; no repository in the fleet requiresrulesby name, which I checked across the inventory's rulesets.harness/checkers/3aac33fa08cfe72cae7aeb1d8033deb94096e7f554ddcd6c67cffb8c7fa2a633.pyis the checker Harness v0.19.0 will pin: byte-identical to Harness's template, with a matching sha256. The directory is append-only (seeharness/README.md).README: a section for
harness-rules.yml.Checks (local)
🤖 Generated with Claude Code