Jorijn van der Graaf
e2bd0b14ee
All checks were successful
Flatpak / flatpak (push) Successful in 13m7s
Crafter.Review reviews a frozen commit range before it is pushed: the approach, a static proof of the code's bugs, and every claim in the messages and in the documentation the range changes, one claude process per lens and unit, or per whole-range pass, and the owner approves the exact frozen hash before the push. This sets it up for this repository. .review-gates/config.json turns on three lenses in the commits mode, at xhigh: repo-better-solution, repo-bug-prover and repo-facts. The functional lens is off: it exercises a web application through a browser, and this repository's product is a command-line tool. The security lens is off by the owner's ruling: crafter-build stores no secret of its own, and while its Flatpak runs with the user's SSH agent (--socket=ssh-auth) and the whole host filesystem (--filesystem=host), everything it runs is code its user chose to run. The rules CI keeps around its token and signing key go to the approach lens's section instead. gate0 lists the commands run by hand before a freeze. build.sh comes first, because bin/crafter-build compiles project.cpp against the interfaces it was bootstrapped with, and lint comes after the self-host build, because lint's AST rules parse with the module PCMs a build leaves and lint builds only the std PCM itself. .review-gates/lenses/ holds this repository's section of each lens's charter, appended to the text Crafter.Review ships: that AGENTS.md is absent from the frozen tree, the layers and the consumers of interfaces/, the execution contexts a bug can hide in, where libc++ and clang are readable from the review's sandbox, and what a "passes the suite" claim traces to. The /prepush skill that crafter-review init writes stays untracked. It is generated from the installed Crafter.Review and refreshed by every init, so a committed copy would lag the binary it describes. One init per checkout restores it, which AGENTS.template.md now says, together with the rules freeze holds every commit of a range to: signed (requireSigned), with the owner's address as its author and committer (authors), and no AI attribution trailer (aiTrailers forbid).
18 lines
971 B
Markdown
18 lines
971 B
Markdown
## This repository: Crafter.Build
|
|
|
|
- A claim that a tree passes `build.sh`, the self-host build, the test
|
|
suite, `format --check` or `lint` traces to the Gate 0 log among the
|
|
evidence paths INPUTS names: each command with its exit code and the sha
|
|
it ran at. A claim of a run anywhere else (the Flatpak through
|
|
`run flatpak`, CI, wine, qemu, node, a browser) traces to a capture of
|
|
that run that names the commit, or is unverifiable.
|
|
- A test a message names exists as a `cfg.AddTest("<Name>")` line in
|
|
`project.cpp` and a `tests/<Name>/main.cpp` whose checks pin what the
|
|
message says.
|
|
- `AGENTS.md` is generated from `AGENTS.template.md` and the dependencies'
|
|
`AGENTS.consumer.md` and is not in the tree: a claim about it is checked
|
|
against those sources.
|
|
- A `<release>` entry in
|
|
`packaging/flatpak/net.catcrafts.CrafterBuild.metainfo.xml` is the
|
|
release notes users read: every sentence in it is a claim about the code
|
|
since the previous tag.
|