0.1.19: the comparison travels with the report

--against scored two trees and then threw one of them away. The movement is the whole point of a ratchet, and anything reading the JSON had to score the base itself to find it — work this command had already done.

The report now carries against: the ref, its category scores, and its line count.

cqx as an action, and an installer instead of a filename

deka already had a cqx workflow and its download was broken: it asks for cqx-linux-x86_64, which the release renamed to cqx-linux-x64 at v0.1.15. Both its jobs fail on that, and have been.

The pull request job becomes two lines. The publish job stops naming the binary it wants and uses the installer, which picks the right one for the runner and checks it against the sums published beside it.

Reporting only to begin with: a gate that fails the author teaches the author to turn it off.

Score deka with cqx on every pull request

Reporting only to begin with: a gate that fails people before anybody has agreed what the number should be teaches them to turn it off.

On a pull request it scores the branch, scores the commit the branch is based on, and says what moved. Findings go to code scanning, so each one lands on its own line in Files changed.

cqx as an action, and an installer instead of a filename

The pull request job was fifty lines of bash and python doing what the action now does in two: score the branch, score its base, say what moved, and put each finding on its own line in Files changed. Reporting only to begin with — dsc's score moves every day, and a gate that fails the author teaches the author to turn it off.

The publish job stops naming the binary it wants. That is what broke: the release renamed cqx-linux-x86_64 to cqx-linux-x64 at v0.1.15 and this went on asking for a file that no longer exists. The installer picks the right one for the runner and checks it against the sums published beside it.

Claude-Session: https://claude.ai/code/session_01XHuN9xFKcoJaoTJfBwxsb1

Score cqx with cqx

The tool has to hold its own standard before it is worth asking anybody else to, and this is where the action is proved: if it breaks, it breaks here first.

Reporting only, for now. cqx is being written quickly and its own score moves every day; a gate that fails the author of the gate teaches the author to turn it off.

0.1.18

Merge pull request #1163 from dekaruntime/samifouad-patch-1

Update README.md

Update README.md

Merge pull request #1162 from dekaruntime/claude/cqx-export

Score every pull request, publish every commit to main

Merge pull request #303 from dekaruntime/claude/cqx-export

Score every pull request, publish every commit to main