verify-proof-reuse
Check ProofReuse.tla, how CI and jmerge reuse a pass a marker names, and the guards' stop; use when changing green.py, reuse.py, Guards.of or Guards.checked.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- verify-proof-reuse
- paths
- features/jmerge/spec/ProofReuse.tla, features/jmerge/src/jmerge/green.py, features/jmerge/src/jmerge/reuse.py, features/jmerge/src/jmerge/treeguards.py, features/jmerge/src/jmerge/cli.py
- description
- Check ProofReuse.tla, how CI and jmerge reuse a pass a marker names, and the guards' stop; use when changing green.py, reuse.py, Guards.of or Guards.checked.
03 SKILL.md 正文
verify-proof-reuse
features/jmerge/spec/ProofReuse.tla extends PrVerdict.tla with the reuse of a pass: CI's check or its reuse of a pass of the same pair, the markers any run of the repo leaves, and jmerge's guards step at main's tip (merge on its check, on a pass a marker names, or on the guards, which pass, fail or stop at 600 s).
Its prose, the rules, the canaries and what it leaves out are in features/jmerge/spec/ProofReuse.md.
ReuseNamesItsTrees: a pass CI or jmerge reuses was left by a run whose head is the head's tree, over the tip's tree; the harm if it breaks: a head passes or merges on a pass of other trees, a forged one among them.NoMergeOnAStoppedTree: the harm, a tree no guard finished merges.MergesOrWaitsOnYou, PrVerdict's: the harm, a stopped tree waits for ever on main.
The model is the design of rows pv-reuse-binds-run and pv-stale-all-update; today's code is its canaries head (no head check) and update (a stop with no overlap waits on main).
The record
Model: features/jmerge/spec/ProofReuse.tla
Sync: 7c969c3e97f1af9d32753131cf92933b9a556039
Covers:
features/jmerge/src/jmerge/green.py:checked,green_run,whosefeatures/jmerge/src/jmerge/reuse.py:answer,mainfeatures/jmerge/src/jmerge/treeguards.py:Guards.of,Guards.checked,Guards.was,Guards.kept,Guards.in_tree,LIMIT_SECONDSfeatures/jmerge/src/jmerge/cli.py:Repo.over_main,Repo.judged,Repo.merge_holding
At the sync commit each quote was read against the code it cites, rp-proof-reuse-model's first read.
features/repo-guards/tests/test_model_sync.py fails when a file or name above is gone.
Move Sync: forward only after you read every change to these files since it against the model, as /maintain-formal-verification-skill says, and never because the check passes.
Does a change touch it
Rerun it when the diff touches a file of the record, changes what a marker names or who may leave one, what a lookup checks, or what a stop of the guards does.
Row pv-reuse-binds-run makes today's code the design's head: once it lands, the Drop "head" comment's quote moves to the new check, and ProofReuse.chart.cfg draws today's code as the design.
Run it
uv run pytest features/jmerge/tests/test_proof_reuse_spec.py -q
It runs TLC on the design, the four canaries, the two reach runs and the chart's config, in under a minute, and skips where no Java runs TLC; a run that ends in seconds took TLC's verdict from the statechart tools' cache (tools.kept).
- Bounds:
Moves = 2,Drop = "none", 241,982 distinct states; the chart's config moves main once. - Assumptions: PrVerdict's, with no holds for your word, no line and no batch; trees kept relative to today's tip and head; each step atomic, a reuse and its merge under the merge lock.
A real bug or a modeling error
Each condition of a step quotes its code. Replay a trace at the code: a step the code cannot take there is a modeling error, and the model is what gets fixed; when every step is backed, it is a bug, told as what CI's reuse job and jmerge said at each step, and the rule stays as it is.
04 同仓库更多 Skills
no-key
A skill its skills.json lists as hidden that a model may still call by itself, kept broken so the lint is seen to catch it.
fake-skill
A FAKE skill in a FAKE tree, named for its folder until the test renames the folder.
extra-key
A skill its skills.json does not list as hidden that a model still cannot call, kept broken so the lint is seen to catch it.
unslop
Cut AI tells from writing. Use when the user says text reads like AI, asks to unslop it, or before prose ships to people.
technical-writing
Write or review docs, READMEs, RFCs, PR descriptions and commit messages to a layered standard: Diataxis structure, Google developer style, STE rules and Global English.
why
Find why code is the way it is, from its history and every evidence source this session can query, with citations. Use for 'why does X work this way', 'why did we pick Y', regressions and postmortems. Use how for runtime behavior.