Skip to content

feat(harness): serve the Misoto Harness rules job and its checkers - #30

Merged
Misoto22 merged 1 commit into
mainfrom
feat(harness)/rules-workflow
Nov 8, 2026
Merged

Misoto22 merged 1 commit into
mainfrom
feat(harness)/rules-workflow

Conversation

@Misoto22

@Misoto22 Misoto22 commented Nov 8, 2026

Copy link
Copy Markdown
Owner

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, the rules job, reusable. In order, it:

    1. checks out the repository with fetch-depth: 0 and filter: blob:none
    2. sets up Node 26 and pnpm from .rulesync/package.json
    3. reads the checker sha256 from the consumer's managed .rulesync/checker.json
    4. downloads harness/checkers/<sha256>.py and refuses to run it unless sha256sum --check --strict passes
    5. runs the checker with MISOTO_HARNESS_BASE_SHA, as the old job did
    6. runs rulesync generate --check

    Its runs-on input is a JSON array, matching pr-title.yml and release.yml. The check context is rules / rules; no repository in the fleet requires rules by name, which I checked across the inventory's rulesets.

  • harness/checkers/3aac33fa08cfe72cae7aeb1d8033deb94096e7f554ddcd6c67cffb8c7fa2a633.py is the checker Harness v0.19.0 will pin: byte-identical to Harness's template, with a matching sha256. The directory is append-only (see harness/README.md).

  • README: a section for harness-rules.yml.

Checks (local)

docker run rhysd/actionlint:1.7.12   exit 0
uvx yamllint@1.38.0 --strict .        exit 0
shasum -a 256 harness/checkers/3aac…a633.py   3aac33fa08cfe72cae7aeb1d8033deb94096e7f554ddcd6c67cffb8c7fa2a633

🤖 Generated with Claude Code

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
Misoto22 merged commit 4aa358d into main Nov 8, 2026
3 checks passed
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>
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