Each record's step names its page and its directory in `# paths:`, and the workflow's trigger lists the same four paths, so a pull request that changes a reading, a fixture, the corpus, the rule, a dictionary or either page starts the workflow, and its gate runs the two steps that hold them. Before, only a change to the step files themselves or the nightly run did. Changelog: none Co-Authored-By: Claude Opus 5.5 <[email protected]>
13 lines
984 B
Shell
13 lines
984 B
Shell
# step: text dictionary · the record and the text quoting it
|
|
# order: 31
|
|
# paths: wai/research/text-dictionary.md wai/research/text-dictionary/**
|
|
#
|
|
# The text-dictionary record (research/text-dictionary.md): the result held to the committed
|
|
# rule, split and dictionaries, every total recomputed from the per-object lengths, each by a
|
|
# formula that shares nothing with the one that wrote it, the rule applied, and every figure
|
|
# the page quotes checked (each is followed by a `txd` marker naming its place). The
|
|
# self-test changes copies of the result, a total with the dictionary's bytes left out among
|
|
# them, requires the check to refuse each, and requires a result that fails to be left
|
|
# unwritten. Standard library only, run isolated; neither run needs Zstandard.
|
|
python3 -I research/text-dictionary/measure.py check research/text-dictionary/result.json research/text-dictionary.md
|
|
python3 -I research/text-dictionary/measure.py selftest research/text-dictionary/result.json
|