Release [run release-20261112T120125Z]

#36
by Battam - opened
This view is limited to 50 files because it contains too many changes. See the raw diff here.
Files changed (50) hide show
  1. CHANGELOG.md +20 -0
  2. README.md +21 -21
  3. README.zh.md +21 -21
  4. campaign_files/2026-10-a-spreadsheets-with-answers-2/uky-ccd-crop-budgets/README.md +0 -2
  5. campaign_files/2026-10-c-repros-2/trixi-2024-generalized-upwind-sbp-repro/README.md +0 -2
  6. campaign_files/2026-10-g-solver-instances-2/timpasslib/README.md +0 -6
  7. campaign_files/2026-10-g-solver-instances-2/trick-traveling-tournament/README.md +0 -4
  8. campaign_files/2026-10-g-solver-instances-2/trick-ttp/README.md +0 -4
  9. campaign_files/2026-10-g-solver-instances-2/tuwien-dbai-shift-design/README.md +0 -6
  10. campaign_files/2026-10-g-solver-instances-2/tuwien-musliu-rotating-workforce/README.md +0 -4
  11. campaign_files/2026-10-hw-eda-tests-2/tock-libtock-c-examples-and-tock-tock-tools-ci-qemu-virt-ci-runner-github/README.md +0 -16
  12. campaign_files/2026-10-hw-eda-tests-2/tock-tock-capsules-core-and-tools-ci-qemu-virt-ci-runner-github/README.md +0 -4
  13. campaign_files/2026-10-hw-eda-tests-2/tscircuit-checks-tests-assets-fixtures-and-tests-lib-answer-carrying-e8ea1860/README.md +0 -46
  14. campaign_files/2026-10-m-issue-trackers-2/torproject-tor-dev/README.md +0 -4
  15. campaign_files/2026-10-m-issue-trackers-2/transdevblazefield-passenger-gtfs/README.md +0 -4
  16. campaign_files/2026-10-m-issue-trackers-2/transport-data-gouv-fr-tdg-81876/README.md +0 -4
  17. campaign_files/2026-10-m-issue-trackers-2/trillium-bcferries-bc-ca/README.md +0 -4
  18. campaign_files/2026-10-m-issue-trackers-2/trustedfirmware-tf-a/README.md +0 -4
  19. campaign_files/2026-10-m-issue-trackers-2/tug-texhax/README.md +0 -4
  20. campaign_files/2026-10-m-issue-trackers-2/tuhs/README.md +0 -4
  21. campaign_files/2026-10-m-issue-trackers-2/typescript-github-issues/README.md +0 -4
  22. campaign_files/2026-10-m-issue-trackers-2/ubuntu-devel/README.md +0 -4
  23. campaign_files/2026-10-m-issue-trackers-2/unibus-passenger-gtfs/README.md +0 -4
  24. campaign_files/2026-10-md-media-and-documents/tingerrr-subpar-tests/README.md +0 -4
  25. campaign_files/2026-10-md-media-and-documents/touying-typ-touying-tests/README.md +0 -4
  26. campaign_files/2026-10-md-media-and-documents/turndown-test-index-html/README.md +0 -4
  27. campaign_files/2026-10-md-media-and-documents/typsium-alchemist-tests/README.md +0 -4
  28. campaign_files/2026-10-md-media-and-documents/typst-community-glossarium-tests/README.md +0 -4
  29. campaign_files/2026-10-md-media-and-documents/typst-tests-suite/README.md +0 -8
  30. campaign_files/2026-10-md-media-and-documents/u-fischer-newpax-testfiles/README.md +0 -4
  31. campaign_files/2026-10-md-media-and-documents/u-fischer-tagpdf-testfiles/README.md +0 -4
  32. campaign_files/2026-10-md-media-and-documents/uci-bach-choral-harmony/README.md +0 -4
  33. campaign_files/2026-10-md-media-and-documents/ummels-ccicons-testfiles/README.md +0 -4
  34. campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-modify-header-scenario/README.md +0 -4
  35. campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-request-quotation-scenario/README.md +0 -4
  36. campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-requisition-scenario/README.md +0 -4
  37. campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-scenarios/README.md +0 -16
  38. campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-secondary-unit-scenario/README.md +0 -4
  39. campaign_files/2026-10-op-rule-calculations-2/tryton-stock-scenarios/README.md +0 -30
  40. campaign_files/2026-10-op-rule-calculations-2/uci-275-bike-sharing/README.md +0 -4
  41. campaign_files/2026-10-op-rule-calculations-2/uci-292-wholesale-customers/README.md +0 -4
  42. campaign_files/2026-10-op-rule-calculations-2/uci-468-online-shoppers-purchasing-intention/README.md +0 -4
  43. campaign_files/2026-10-op-rule-calculations-2/uci-488-facebook-live-sellers-thailand/README.md +0 -4
  44. campaign_files/2026-10-s-security-detection-2/trail-of-bits-semgrep-rules/README.md +0 -4
  45. campaign_files/2026-10-s-security-detection-2/trivy-checks-kubernetes-checks/README.md +0 -4
  46. campaign_files/2026-10-s-security-detection-2/trivy-checks-kubernetes-misconfiguration-checks/README.md +0 -4
  47. campaign_files/2026-10-s-security-detection-2/trivy-checks-rego-check-with-tests-and-examples/README.md +0 -4
  48. campaign_files/2026-10-s-security-detection-2/tudctf-2024-public-challenges/README.md +0 -12
  49. campaign_files/2026-10-s-security-detection-2/umdctf-public-challenges-archive/README.md +0 -8
  50. campaign_files/2026-10-s-security-detection/trailofbits-semgrep-rules/README.md +0 -4
CHANGELOG.md CHANGED
@@ -3460,3 +3460,23 @@ Changes to the content of this index, oldest first. There is one entry for each
3460
  - npm: refused
3461
  - scotland-government-workbooks: changed pointer group file data/scotland-government-workbooks/2026-10-a-spreadsheets-with-answers-2/part-00000.parquet: 2 key(s) of the old version are in no data file of source scotland-government-workbooks after the commit (row 3 from batch 2026-10-a-spreadsheets-with-answers-2, row 6 from batch 2026-10-a-spreadsheets-with-answers-2); the removal record holds none of them, and none fails a publish check now
3462
  - stackexchange-api-posts: refused
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3460
  - npm: refused
3461
  - scotland-government-workbooks: changed pointer group file data/scotland-government-workbooks/2026-10-a-spreadsheets-with-answers-2/part-00000.parquet: 2 key(s) of the old version are in no data file of source scotland-government-workbooks after the commit (row 3 from batch 2026-10-a-spreadsheets-with-answers-2, row 6 from batch 2026-10-a-spreadsheets-with-answers-2); the removal record holds none of them, and none fails a publish check now
3462
  - stackexchange-api-posts: refused
3463
+
3464
+ ## 2026-11-12: sources held back
3465
+
3466
+ - Each source below keeps its newest version that passed every check; its newer batch waits until it passes them:
3467
+ - borealis-dataverse-workbooks-cc-by: changed pointer group file data/borealis-dataverse-workbooks-cc-by/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 2 key(s) of the old version are in no data file of source borealis-dataverse-workbooks-cc-by after the commit (row 4 from batch 2026-10-a-spreadsheets-with-answers, row 5 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
3468
+ - borealis-dataverse-workbooks-cc0: changed pointer group file data/borealis-dataverse-workbooks-cc0/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source borealis-dataverse-workbooks-cc0 after the commit (row 7 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
3469
+ - cfpb-complaints: refused
3470
+ - data-gov-uk-workbooks: changed pointer group file data/data-gov-uk-workbooks/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 4 key(s) of the old version are in no data file of source data-gov-uk-workbooks after the commit (row 5 from batch 2026-10-a-spreadsheets-with-answers, row 6 from batch 2026-10-a-spreadsheets-with-answers, row 12 from batch 2026-10-a-spreadsheets-with-answers, 1 more); the removal record holds none of them, and none fails a publish check now
3471
+ - data-gov-uk-workbooks-noassertion: changed pointer group file data/data-gov-uk-workbooks-noassertion/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source data-gov-uk-workbooks-noassertion after the commit (row 6 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
3472
+ - dataversenl-workbooks-cc-by: changed pointer group file data/dataversenl-workbooks-cc-by/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source dataversenl-workbooks-cc-by after the commit (row 17 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
3473
+ - dataversenl-workbooks-cc0: changed pointer group file data/dataversenl-workbooks-cc0/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 3 key(s) of the old version are in no data file of source dataversenl-workbooks-cc0 after the commit (row 7 from batch 2026-10-a-spreadsheets-with-answers, row 13 from batch 2026-10-a-spreadsheets-with-answers, row 16 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
3474
+ - dvn-fvhlgg-repro: changed pointer group file data/dvn-fvhlgg-repro/2026-10-c-repros/part-00000.parquet: 3 key(s) of the old version are in no data file of source dvn-fvhlgg-repro after the commit (row 5 from batch 2026-10-c-repros, row 7 from batch 2026-10-c-repros, row 16 from batch 2026-10-c-repros); the removal record holds none of them, and none fails a publish check now
3475
+ - eu-institution-workbooks-cc-by: changed pointer group file data/eu-institution-workbooks-cc-by/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 3 key(s) of the old version are in no data file of source eu-institution-workbooks-cc-by after the commit (row 2 from batch 2026-10-a-spreadsheets-with-answers, row 4 from batch 2026-10-a-spreadsheets-with-answers, row 5 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
3476
+ - hdx-workbooks-cc0: changed pointer group file data/hdx-workbooks-cc0/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 2 key(s) of the old version are in no data file of source hdx-workbooks-cc0 after the commit (row 4 from batch 2026-10-a-spreadsheets-with-answers, row 5 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
3477
+ - hdx-workbooks-odbl: changed pointer group file data/hdx-workbooks-odbl/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source hdx-workbooks-odbl after the commit (row 4 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
3478
+ - hf-training-records: refused
3479
+ - npm: refused
3480
+ - scotland-government-workbooks: changed pointer group file data/scotland-government-workbooks/2026-10-a-spreadsheets-with-answers-2/part-00000.parquet: 2 key(s) of the old version are in no data file of source scotland-government-workbooks after the commit (row 3 from batch 2026-10-a-spreadsheets-with-answers-2, row 6 from batch 2026-10-a-spreadsheets-with-answers-2); the removal record holds none of them, and none fails a publish check now
3481
+ - stackexchange-api-posts: refused
3482
+ - uk-government-workbooks: changed pointer group file data/uk-government-workbooks/2026-10-a-spreadsheets-with-answers-2/part-00000.parquet: 1 key(s) of the old version are in no data file of source uk-government-workbooks after the commit (row 22 from batch 2026-10-a-spreadsheets-with-answers-2); the removal record holds none of them, and none fails a publish check now
README.md CHANGED
@@ -35,18 +35,18 @@ this dataset is the foundation's public index.
35
  English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/training-data-foundation) · [Usage video](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
36
 
37
  <picture class="not-prose">
38
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/stages-narrow-light.svg">
39
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/stages-wide-light.svg" alt="What each training stage can use in this release. Pre-training (provisional): 30.6 TB deduplicated size, 149,118,607 rows, 29.9 TB allowed for training. Mid-training (provisional): 3.86 TB deduplicated size, 34,079,767 rows, 1.42 TB allowed for training. Post-training: 1,761 material sets, from 1,818 upstream sources, 1,409 allowed for training.">
40
  </picture>
41
  <picture class="not-prose">
42
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/stages-narrow-dark.svg">
43
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/stages-wide-dark.svg" alt="What each training stage can use in this release. Pre-training (provisional): 30.6 TB deduplicated size, 149,118,607 rows, 29.9 TB allowed for training. Mid-training (provisional): 3.86 TB deduplicated size, 34,079,767 rows, 1.42 TB allowed for training. Post-training: 1,761 material sets, from 1,818 upstream sources, 1,409 allowed for training.">
44
  </picture>
45
 
46
  ## Get data in one command
47
 
48
  ```sh
49
- uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/tools/fetch.py --form spreadsheets --sample 3 --out ./data
50
  ```
51
 
52
  This fetches 3 units of every spreadsheet material set into `./data`, one folder per unit, and checks each file against the size and hashes its row records.
@@ -56,7 +56,7 @@ the same command takes the same units of this release.
56
  <details>
57
  <summary>What the command takes, and in which order</summary>
58
 
59
- The command and the queries below are pinned to the release tag `release-2026-11-12.7`.
60
  [uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
61
 
62
  The command returns units: 3 units from each material set whose form is `spreadsheets`, each in a folder of its own named after its `unit_id`.
@@ -84,7 +84,7 @@ Choose material sets from the catalog with [DuckDB](https://duckdb.org/):
84
 
85
  ```sql
86
  SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
87
- FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-12.7/meta/catalog.parquet'
88
  WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
89
  ORDER BY collection, units DESC;
90
  ```
@@ -95,7 +95,7 @@ with `kind = 'corpus'` it returns corpora instead, counted in rows (`files`).
95
  Choose files in one corpus:
96
 
97
  ```sql
98
- SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-12.7/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-12.7/meta/catalog.parquet' WHERE source = 'if-archive'));
99
  SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
100
  FROM read_parquet(getvariable('files'))
101
  WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
@@ -111,12 +111,12 @@ A data file may hold the rows of several sources, so the query keeps this one's
111
  ## What's inside
112
 
113
  <picture class="not-prose">
114
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/inside-narrow-light.svg">
115
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/inside-wide-light.svg" alt="The training stages by top-level domain, largest first. Pre-training (provisional), deduplicated size, by domain: Data science 29.8 TB; Science 531 GB; Machine learning 82.8 GB; Media 48.9 GB; System administration 35.7 GB; Hardware 29.6 GB; Many domains 29.6 GB; Security 4.18 GB; Unclassified 1.43 GB; Misc 376 MB; Software engineering 175 MB; Operations 4.08 KB. Mid-training (provisional), deduplicated size, by domain: System administration 1.27 TB; Many domains 1.00 TB; Machine learning 503 GB; Science 461 GB; Data science 429 GB; Hardware 177 GB; Security 13.9 GB; Misc 3.45 GB; Software engineering 2.48 GB; Unclassified 2.21 GB; Media 701 MB; Operations 13.8 MB. Post-training, material sets, by domain: Data science 348; Software engineering 286; Media 273; Operations 206; Machine learning 182; Science 174; Security 103; Hardware 87; System administration 71; Misc 31.">
116
  </picture>
117
  <picture class="not-prose">
118
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/inside-narrow-dark.svg">
119
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/inside-wide-dark.svg" alt="The training stages by top-level domain, largest first. Pre-training (provisional), deduplicated size, by domain: Data science 29.8 TB; Science 531 GB; Machine learning 82.8 GB; Media 48.9 GB; System administration 35.7 GB; Hardware 29.6 GB; Many domains 29.6 GB; Security 4.18 GB; Unclassified 1.43 GB; Misc 376 MB; Software engineering 175 MB; Operations 4.08 KB. Mid-training (provisional), deduplicated size, by domain: System administration 1.27 TB; Many domains 1.00 TB; Machine learning 503 GB; Science 461 GB; Data science 429 GB; Hardware 177 GB; Security 13.9 GB; Misc 3.45 GB; Software engineering 2.48 GB; Unclassified 2.21 GB; Media 701 MB; Operations 13.8 MB. Post-training, material sets, by domain: Data science 348; Software engineering 286; Media 273; Operations 206; Machine learning 182; Science 174; Security 103; Hardware 87; System administration 71; Misc 31.">
120
  </picture>
121
 
122
  <details>
@@ -124,16 +124,16 @@ A data file may hold the rows of several sources, so the query keeps this one's
124
 
125
  | Domain | Pre-training: deduplicated size | Pre-training: rows | Mid-training: deduplicated size | Mid-training: rows | Post-training: material sets |
126
  |---|---:|---:|---:|---:|---:|
127
- | Software engineering | 175 MB | 58,928 | 2.48 GB | 241,069 | 286 |
128
  | System administration | 35.7 GB | 1,997,853 | 1.27 TB | 11,372,393 | 71 |
129
  | Data science | 29.8 TB | 105,523,069 | 429 GB | 264,581 | 348 |
130
  | Machine learning | 82.8 GB | 237,230 | 503 GB | 219,905 | 182 |
131
- | Science | 531 GB | 13,352,880 | 461 GB | 197,348 | 174 |
132
  | Operations | 4.08 KB | 18,862,045 | 13.8 MB | 423 | 206 |
133
  | Hardware | 29.6 GB | 388,557 | 177 GB | 4,945,550 | 87 |
134
- | Security | 4.18 GB | 80,662 | 13.9 GB | 117,484 | 103 |
135
  | Media | 48.9 GB | 16,365 | 701 MB | 34,670 | 273 |
136
- | Misc | 376 MB | 2,403 | 3.45 GB | 102,989 | 31 |
137
  | Many domains | 29.6 GB | 8,262,018 | 1.00 TB | 16,181,781 | 0 |
138
  | Unclassified | 1.43 GB | 336,597 | 2.21 GB | 401,574 | 0 |
139
 
@@ -148,12 +148,12 @@ Every material set and every corpus, with its counts, size, license tier and log
148
  ## How it is made
149
 
150
  <picture class="not-prose">
151
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/steps-narrow-light.svg">
152
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/steps-wide-light.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole public upstreams into corpora, one row per file or record, the material of pre-training and mid-training. 2, admit: works the search found upstream and groups of corpus rows become material sets, the material of post-training. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-12.7.">
153
  </picture>
154
  <picture class="not-prose">
155
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/steps-narrow-dark.svg">
156
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/steps-wide-dark.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole public upstreams into corpora, one row per file or record, the material of pre-training and mid-training. 2, admit: works the search found upstream and groups of corpus rows become material sets, the material of post-training. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-12.7.">
157
  </picture>
158
 
159
  Collectors read whole public upstreams into corpora, the material of pre-training and mid-training, and admission turns works found upstream and chosen corpus rows into material sets, the material of post-training.
@@ -180,7 +180,7 @@ The full text, with the license details, personal information read from sample f
180
  @misc{training_data_foundation,
181
  title = {training-data-foundation: an index of public materials for building agent environments},
182
  howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
183
- note = {Release release-2026-11-12.7},
184
  year = {2026}
185
  }
186
  ```
 
35
  English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/training-data-foundation) · [Usage video](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
36
 
37
  <picture class="not-prose">
38
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/stages-narrow-light.svg">
39
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/stages-wide-light.svg" alt="What each training stage can use in this release. Pre-training (provisional): 30.6 TB deduplicated size, 149,118,671 rows, 29.9 TB allowed for training. Mid-training (provisional): 3.86 TB deduplicated size, 34,084,498 rows, 1.42 TB allowed for training. Post-training: 1,763 material sets, from 1,820 upstream sources, 1,411 allowed for training.">
40
  </picture>
41
  <picture class="not-prose">
42
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/stages-narrow-dark.svg">
43
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/stages-wide-dark.svg" alt="What each training stage can use in this release. Pre-training (provisional): 30.6 TB deduplicated size, 149,118,671 rows, 29.9 TB allowed for training. Mid-training (provisional): 3.86 TB deduplicated size, 34,084,498 rows, 1.42 TB allowed for training. Post-training: 1,763 material sets, from 1,820 upstream sources, 1,411 allowed for training.">
44
  </picture>
45
 
46
  ## Get data in one command
47
 
48
  ```sh
49
+ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/tools/fetch.py --form spreadsheets --sample 3 --out ./data
50
  ```
51
 
52
  This fetches 3 units of every spreadsheet material set into `./data`, one folder per unit, and checks each file against the size and hashes its row records.
 
56
  <details>
57
  <summary>What the command takes, and in which order</summary>
58
 
59
+ The command and the queries below are pinned to the release tag `release-2026-11-12.8`.
60
  [uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
61
 
62
  The command returns units: 3 units from each material set whose form is `spreadsheets`, each in a folder of its own named after its `unit_id`.
 
84
 
85
  ```sql
86
  SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
87
+ FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-12.8/meta/catalog.parquet'
88
  WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
89
  ORDER BY collection, units DESC;
90
  ```
 
95
  Choose files in one corpus:
96
 
97
  ```sql
98
+ SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-12.8/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-12.8/meta/catalog.parquet' WHERE source = 'if-archive'));
99
  SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
100
  FROM read_parquet(getvariable('files'))
101
  WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
 
111
  ## What's inside
112
 
113
  <picture class="not-prose">
114
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/inside-narrow-light.svg">
115
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/inside-wide-light.svg" alt="The training stages by top-level domain, largest first. Pre-training (provisional), deduplicated size, by domain: Data science 29.8 TB; Science 531 GB; Machine learning 82.8 GB; Media 48.9 GB; System administration 35.7 GB; Hardware 29.6 GB; Many domains 29.6 GB; Security 4.18 GB; Unclassified 1.43 GB; Misc 376 MB; Software engineering 176 MB; Operations 4.08 KB. Mid-training (provisional), deduplicated size, by domain: System administration 1.27 TB; Many domains 1.00 TB; Machine learning 503 GB; Science 461 GB; Data science 429 GB; Hardware 177 GB; Security 13.9 GB; Misc 3.45 GB; Software engineering 2.66 GB; Unclassified 2.21 GB; Media 701 MB; Operations 13.8 MB. Post-training, material sets, by domain: Data science 348; Software engineering 286; Media 273; Operations 206; Machine learning 182; Science 174; Security 103; Hardware 87; System administration 71; Misc 33.">
116
  </picture>
117
  <picture class="not-prose">
118
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/inside-narrow-dark.svg">
119
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/inside-wide-dark.svg" alt="The training stages by top-level domain, largest first. Pre-training (provisional), deduplicated size, by domain: Data science 29.8 TB; Science 531 GB; Machine learning 82.8 GB; Media 48.9 GB; System administration 35.7 GB; Hardware 29.6 GB; Many domains 29.6 GB; Security 4.18 GB; Unclassified 1.43 GB; Misc 376 MB; Software engineering 176 MB; Operations 4.08 KB. Mid-training (provisional), deduplicated size, by domain: System administration 1.27 TB; Many domains 1.00 TB; Machine learning 503 GB; Science 461 GB; Data science 429 GB; Hardware 177 GB; Security 13.9 GB; Misc 3.45 GB; Software engineering 2.66 GB; Unclassified 2.21 GB; Media 701 MB; Operations 13.8 MB. Post-training, material sets, by domain: Data science 348; Software engineering 286; Media 273; Operations 206; Machine learning 182; Science 174; Security 103; Hardware 87; System administration 71; Misc 33.">
120
  </picture>
121
 
122
  <details>
 
124
 
125
  | Domain | Pre-training: deduplicated size | Pre-training: rows | Mid-training: deduplicated size | Mid-training: rows | Post-training: material sets |
126
  |---|---:|---:|---:|---:|---:|
127
+ | Software engineering | 176 MB | 58,988 | 2.66 GB | 245,628 | 286 |
128
  | System administration | 35.7 GB | 1,997,853 | 1.27 TB | 11,372,393 | 71 |
129
  | Data science | 29.8 TB | 105,523,069 | 429 GB | 264,581 | 348 |
130
  | Machine learning | 82.8 GB | 237,230 | 503 GB | 219,905 | 182 |
131
+ | Science | 531 GB | 13,352,880 | 461 GB | 197,363 | 174 |
132
  | Operations | 4.08 KB | 18,862,045 | 13.8 MB | 423 | 206 |
133
  | Hardware | 29.6 GB | 388,557 | 177 GB | 4,945,550 | 87 |
134
+ | Security | 4.18 GB | 80,666 | 13.9 GB | 117,641 | 103 |
135
  | Media | 48.9 GB | 16,365 | 701 MB | 34,670 | 273 |
136
+ | Misc | 376 MB | 2,403 | 3.45 GB | 102,989 | 33 |
137
  | Many domains | 29.6 GB | 8,262,018 | 1.00 TB | 16,181,781 | 0 |
138
  | Unclassified | 1.43 GB | 336,597 | 2.21 GB | 401,574 | 0 |
139
 
 
148
  ## How it is made
149
 
150
  <picture class="not-prose">
151
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/steps-narrow-light.svg">
152
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/steps-wide-light.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole public upstreams into corpora, one row per file or record, the material of pre-training and mid-training. 2, admit: works the search found upstream and groups of corpus rows become material sets, the material of post-training. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-12.8.">
153
  </picture>
154
  <picture class="not-prose">
155
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/steps-narrow-dark.svg">
156
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/steps-wide-dark.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole public upstreams into corpora, one row per file or record, the material of pre-training and mid-training. 2, admit: works the search found upstream and groups of corpus rows become material sets, the material of post-training. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-12.8.">
157
  </picture>
158
 
159
  Collectors read whole public upstreams into corpora, the material of pre-training and mid-training, and admission turns works found upstream and chosen corpus rows into material sets, the material of post-training.
 
180
  @misc{training_data_foundation,
181
  title = {training-data-foundation: an index of public materials for building agent environments},
182
  howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
183
+ note = {Release release-2026-11-12.8},
184
  year = {2026}
185
  }
186
  ```
README.zh.md CHANGED
@@ -22,18 +22,18 @@ tags:
22
  [English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/training-data-foundation) · [使用示例视频](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
23
 
24
  <picture class="not-prose">
25
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/stages-narrow-light.zh.svg">
26
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/stages-wide-light.zh.svg" alt="本次发布中每个训练阶段能用的数据。预训练(暂定):去重后大小 30.6 TB,149,118,607 行,其中 29.9 TB 允许用于训练。中训练(暂定):去重后大小 3.86 TB,34,079,767 行,其中 1.42 TB 允许用于训练。后训练:材料集 1,761,来自 1,818 个上游来源,其中 1,409 允许用于训练。">
27
  </picture>
28
  <picture class="not-prose">
29
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/stages-narrow-dark.zh.svg">
30
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/stages-wide-dark.zh.svg" alt="本次发布中每个训练阶段能用的数据。预训练(暂定):去重后大小 30.6 TB,149,118,607 行,其中 29.9 TB 允许用于训练。中训练(暂定):去重后大小 3.86 TB,34,079,767 行,其中 1.42 TB 允许用于训练。后训练:材料集 1,761,来自 1,818 个上游来源,其中 1,409 允许用于训练。">
31
  </picture>
32
 
33
  ## 一条命令取数据
34
 
35
  ```sh
36
- uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/tools/fetch.py --form spreadsheets --sample 3 --out ./data
37
  ```
38
 
39
  这条命令从每个电子表格材料集各取 3 个单元放进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
@@ -43,7 +43,7 @@ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/r
43
  <details>
44
  <summary>命令取什么、按什么顺序取</summary>
45
 
46
- 这条命令和下面的查询都固定在发布标签 `release-2026-11-12.7` 上。
47
  [uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
48
 
49
  命令返回单元:形式为 `spreadsheets` 的每个材料集各 3 个单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
@@ -71,7 +71,7 @@ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/r
71
 
72
  ```sql
73
  SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
74
- FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-12.7/meta/catalog.parquet'
75
  WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
76
  ORDER BY collection, units DESC;
77
  ```
@@ -82,7 +82,7 @@ ORDER BY collection, units DESC;
82
  在一个语料库里挑选文件:
83
 
84
  ```sql
85
- SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-12.7/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-12.7/meta/catalog.parquet' WHERE source = 'if-archive'));
86
  SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
87
  FROM read_parquet(getvariable('files'))
88
  WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
@@ -98,12 +98,12 @@ ORDER BY size_bytes LIMIT 20;
98
  ## 内容概览
99
 
100
  <picture class="not-prose">
101
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/inside-narrow-light.zh.svg">
102
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/inside-wide-light.zh.svg" alt="按顶层领域分的各训练阶段,由大到小。预训练(暂定),去重后大小,按领域:数据科学 29.8 TB;科学 531 GB;机器学习 82.8 GB;媒体 48.9 GB;系统管理 35.7 GB;硬件 29.6 GB;多领域 29.6 GB;安全 4.18 GB;未分类 1.43 GB;杂项 376 MB;软件工程 175 MB;运营 4.08 KB。中训练(暂定),去重后大小,按领域:系统管理 1.27 TB;多领域 1.00 TB;机器学习 503 GB;科学 461 GB;数据科学 429 GB;硬件 177 GB;安全 13.9 GB;杂项 3.45 GB;软件工程 2.48 GB;未分类 2.21 GB;媒体 701 MB;运营 13.8 MB。后训练,材料集,按领域:数据科学 348;软件工程 286;媒体 273;运营 206;机器学习 182;科学 174;安全 103;硬件 87;系统管理 71;杂项 31。">
103
  </picture>
104
  <picture class="not-prose">
105
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/inside-narrow-dark.zh.svg">
106
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/inside-wide-dark.zh.svg" alt="按顶层领域分的各训练阶段,由大到小。预训练(暂定),去重后大小,按领域:数据科学 29.8 TB;科学 531 GB;机器学习 82.8 GB;媒体 48.9 GB;系统管理 35.7 GB;硬件 29.6 GB;多领域 29.6 GB;安全 4.18 GB;未分类 1.43 GB;杂项 376 MB;软件工程 175 MB;运营 4.08 KB。中训练(暂定),去重后大小,按领域:系统管理 1.27 TB;多领域 1.00 TB;机器学习 503 GB;科学 461 GB;数据科学 429 GB;硬件 177 GB;安全 13.9 GB;杂项 3.45 GB;软件工程 2.48 GB;未分类 2.21 GB;媒体 701 MB;运营 13.8 MB。后训练,材料集,按领域:数据科学 348;软件工程 286;媒体 273;运营 206;机器学习 182;科学 174;安全 103;硬件 87;系统管理 71;杂项 31。">
107
  </picture>
108
 
109
  <details>
@@ -111,16 +111,16 @@ ORDER BY size_bytes LIMIT 20;
111
 
112
  | 领域 | 预训练:去重后大小 | 预训练:行 | 中训练:去重后大小 | 中训练:行 | 后训练:材料集 |
113
  |---|---:|---:|---:|---:|---:|
114
- | 软件工程 | 175 MB | 58,928 | 2.48 GB | 241,069 | 286 |
115
  | 系统管理 | 35.7 GB | 1,997,853 | 1.27 TB | 11,372,393 | 71 |
116
  | 数据科学 | 29.8 TB | 105,523,069 | 429 GB | 264,581 | 348 |
117
  | 机器学习 | 82.8 GB | 237,230 | 503 GB | 219,905 | 182 |
118
- | 科学 | 531 GB | 13,352,880 | 461 GB | 197,348 | 174 |
119
  | 运营 | 4.08 KB | 18,862,045 | 13.8 MB | 423 | 206 |
120
  | 硬件 | 29.6 GB | 388,557 | 177 GB | 4,945,550 | 87 |
121
- | 安全 | 4.18 GB | 80,662 | 13.9 GB | 117,484 | 103 |
122
  | 媒体 | 48.9 GB | 16,365 | 701 MB | 34,670 | 273 |
123
- | 杂项 | 376 MB | 2,403 | 3.45 GB | 102,989 | 31 |
124
  | 多领域 | 29.6 GB | 8,262,018 | 1.00 TB | 16,181,781 | 0 |
125
  | 未分类 | 1.43 GB | 336,597 | 2.21 GB | 401,574 | 0 |
126
 
@@ -135,12 +135,12 @@ ORDER BY size_bytes LIMIT 20;
135
  ## 怎样做成
136
 
137
  <picture class="not-prose">
138
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/steps-narrow-light.zh.svg">
139
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整的公开上游,每个文件或每条记录记一行,成为语料库,供预训练和中训练使用。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集,供后训练使用。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-12.7。">
140
  </picture>
141
  <picture class="not-prose">
142
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/steps-narrow-dark.zh.svg">
143
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.7/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整的公开上游,每个文件或每条记录记一行,成为语料库,供预训练和中训练使用。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集,供后训练使用。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-12.7。">
144
  </picture>
145
 
146
  采集器整批读取完整的公开上游,记成语料库,供预训练和中训练使用,收录则把检索在上游找到的作品和选出的语料库行做成材料集,供后训练使用。
@@ -167,7 +167,7 @@ ORDER BY size_bytes LIMIT 20;
167
  @misc{training_data_foundation,
168
  title = {training-data-foundation: an index of public materials for building agent environments},
169
  howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
170
- note = {Release release-2026-11-12.7},
171
  year = {2026}
172
  }
173
  ```
 
22
  [English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/training-data-foundation) · [使用示例视频](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
23
 
24
  <picture class="not-prose">
25
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/stages-narrow-light.zh.svg">
26
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/stages-wide-light.zh.svg" alt="本次发布中每个训练阶段能用的数据。预训练(暂定):去重后大小 30.6 TB,149,118,671 行,其中 29.9 TB 允许用于训练。中训练(暂定):去重后大小 3.86 TB,34,084,498 行,其中 1.42 TB 允许用于训练。后训练:材料集 1,763,来自 1,820 个上游来源,其中 1,411 允许用于训练。">
27
  </picture>
28
  <picture class="not-prose">
29
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/stages-narrow-dark.zh.svg">
30
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/stages-wide-dark.zh.svg" alt="本次发布中每个训练阶段能用的数据。预训练(暂定):去重后大小 30.6 TB,149,118,671 行,其中 29.9 TB 允许用于训练。中训练(暂定):去重后大小 3.86 TB,34,084,498 行,其中 1.42 TB 允许用于训练。后训练:材料集 1,763,来自 1,820 个上游来源,其中 1,411 允许用于训练。">
31
  </picture>
32
 
33
  ## 一条命令取数据
34
 
35
  ```sh
36
+ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/tools/fetch.py --form spreadsheets --sample 3 --out ./data
37
  ```
38
 
39
  这条命令从每个电子表格材料集各取 3 个单元放进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
 
43
  <details>
44
  <summary>命令取什么、按什么顺序取</summary>
45
 
46
+ 这条命令和下面的查询都固定在发布标签 `release-2026-11-12.8` 上。
47
  [uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
48
 
49
  命令返回单元:形式为 `spreadsheets` 的每个材料集各 3 个单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
 
71
 
72
  ```sql
73
  SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
74
+ FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-12.8/meta/catalog.parquet'
75
  WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
76
  ORDER BY collection, units DESC;
77
  ```
 
82
  在一个语料库里挑选文件:
83
 
84
  ```sql
85
+ SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-12.8/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-12.8/meta/catalog.parquet' WHERE source = 'if-archive'));
86
  SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
87
  FROM read_parquet(getvariable('files'))
88
  WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
 
98
  ## 内容概览
99
 
100
  <picture class="not-prose">
101
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/inside-narrow-light.zh.svg">
102
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/inside-wide-light.zh.svg" alt="按顶层领域分的各训练阶段,由大到小。预训练(暂定),去重后大小,按领域:数据科学 29.8 TB;科学 531 GB;机器学习 82.8 GB;媒体 48.9 GB;系统管理 35.7 GB;硬件 29.6 GB;多领域 29.6 GB;安全 4.18 GB;未分类 1.43 GB;杂项 376 MB;软件工程 176 MB;运营 4.08 KB。中训练(暂定),去重后大小,按领域:系统管理 1.27 TB;多领域 1.00 TB;机器学习 503 GB;科学 461 GB;数据科学 429 GB;硬件 177 GB;安全 13.9 GB;杂项 3.45 GB;软件工程 2.66 GB;未分类 2.21 GB;媒体 701 MB;运营 13.8 MB。后训练,材料集,按领域:数据科学 348;软件工程 286;媒体 273;运营 206;机器学习 182;科学 174;安全 103;硬件 87;系统管理 71;杂项 33。">
103
  </picture>
104
  <picture class="not-prose">
105
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/inside-narrow-dark.zh.svg">
106
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/inside-wide-dark.zh.svg" alt="按顶层领域分的各训练阶段,由大到小。预训练(暂定),去重后大小,按领域:数据科学 29.8 TB;科学 531 GB;机器学习 82.8 GB;媒体 48.9 GB;系统管理 35.7 GB;硬件 29.6 GB;多领域 29.6 GB;安全 4.18 GB;未分类 1.43 GB;杂项 376 MB;软件工程 176 MB;运营 4.08 KB。中训练(暂定),去重后大小,按领域:系统管理 1.27 TB;多领域 1.00 TB;机器学习 503 GB;科学 461 GB;数据科学 429 GB;硬件 177 GB;安全 13.9 GB;杂项 3.45 GB;软件工程 2.66 GB;未分类 2.21 GB;媒体 701 MB;运营 13.8 MB。后训练,材料集,按领域:数据科学 348;软件工程 286;媒体 273;运营 206;机器学习 182;科学 174;安全 103;硬件 87;系统管理 71;杂项 33。">
107
  </picture>
108
 
109
  <details>
 
111
 
112
  | 领域 | 预训练:去重后大小 | 预训练:行 | 中训练:去重后大小 | 中训练:行 | 后训练:材料集 |
113
  |---|---:|---:|---:|---:|---:|
114
+ | 软件工程 | 176 MB | 58,988 | 2.66 GB | 245,628 | 286 |
115
  | 系统管理 | 35.7 GB | 1,997,853 | 1.27 TB | 11,372,393 | 71 |
116
  | 数据科学 | 29.8 TB | 105,523,069 | 429 GB | 264,581 | 348 |
117
  | 机器学习 | 82.8 GB | 237,230 | 503 GB | 219,905 | 182 |
118
+ | 科学 | 531 GB | 13,352,880 | 461 GB | 197,363 | 174 |
119
  | 运营 | 4.08 KB | 18,862,045 | 13.8 MB | 423 | 206 |
120
  | 硬件 | 29.6 GB | 388,557 | 177 GB | 4,945,550 | 87 |
121
+ | 安全 | 4.18 GB | 80,666 | 13.9 GB | 117,641 | 103 |
122
  | 媒体 | 48.9 GB | 16,365 | 701 MB | 34,670 | 273 |
123
+ | 杂项 | 376 MB | 2,403 | 3.45 GB | 102,989 | 33 |
124
  | 多领域 | 29.6 GB | 8,262,018 | 1.00 TB | 16,181,781 | 0 |
125
  | 未分类 | 1.43 GB | 336,597 | 2.21 GB | 401,574 | 0 |
126
 
 
135
  ## 怎样做成
136
 
137
  <picture class="not-prose">
138
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/steps-narrow-light.zh.svg">
139
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整的公开上游,每个文件或每条记录记一行,成为语料库,供预训练和中训练使用。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集,供后训练使用。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-12.8。">
140
  </picture>
141
  <picture class="not-prose">
142
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/steps-narrow-dark.zh.svg">
143
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-12.8/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整的公开上游,每个文件或每条记录记一行,成为语料库,供预训练和中训练使用。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集,供后训练使用。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-12.8。">
144
  </picture>
145
 
146
  采集器整批读取完整的公开上游,记成语料库,供预训练和中训练使用,收录则把检索在上游找到的作品和选出的语料库行做成材料集,供后训练使用。
 
167
  @misc{training_data_foundation,
168
  title = {training-data-foundation: an index of public materials for building agent environments},
169
  howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
170
+ note = {Release release-2026-11-12.8},
171
  year = {2026}
172
  }
173
  ```
campaign_files/2026-10-a-spreadsheets-with-answers-2/uky-ccd-crop-budgets/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Each file is self-contained.
10
 
11
- **Answers:** Each file with an answer has one answer file, at answer/<unit path>.json (the unit path plus .json). Reference result kind: key_formula_values.
12
-
13
  **Tools to open and check:** openpyxl (formulas and cached values); LibreOffice headless recalculation (soffice --headless --convert-to xlsx)
14
 
15
  **Licence (SPDX):** NOASSERTION
 
8
 
9
  **Self-contained:** Each file is self-contained.
10
 
 
 
11
  **Tools to open and check:** openpyxl (formulas and cached values); LibreOffice headless recalculation (soffice --headless --convert-to xlsx)
12
 
13
  **Licence (SPDX):** NOASSERTION
campaign_files/2026-10-c-repros-2/trixi-2024-generalized-upwind-sbp-repro/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each unit needs other upstream files is not stated. 1 of 2 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
10
 
11
- **Answers:** Each unit with an answer has one answer file, at answer/<package>/reported.json.
12
-
13
  **Tools to open and check:** Open with tools for these file types: .jl; .toml; .md; .mesh.
14
 
15
  **Licence (SPDX):** MIT
 
8
 
9
  **Self-contained:** Whether each unit needs other upstream files is not stated. 1 of 2 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** Open with tools for these file types: .jl; .toml; .md; .mesh.
12
 
13
  **Licence (SPDX):** MIT
campaign_files/2026-10-g-solver-instances-2/timpasslib/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Each file is self-contained.
10
 
11
- **Answers:** No answer files are included. Reference result: Proven optimum; best known objective (not proven optimal). Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Program: check every activity duration of the agent's Timetable.csv lies within its periodic bounds (mod period), then route passengers by shortest paths (format.html line 284) with the change penalty and require total travel time at most 21466; Program: as for toy, feasibility of the periodic timetable then shortest-path routing with change penalty; total travel time at most 140850920.
14
 
15
  **Licence (SPDX):** MIT AND CC-BY-4.0
@@ -21,12 +19,8 @@ Files:
21
  - `data/toy.zip`: TimPassLib instance toy: integrated periodic timetabling and passenger routing, solved optimally (objective 21466).
22
  Format: zip of 4 CSV files (Activities.csv, Events.csv, OD.csv, Config.csv; period_length 60, ean_change_penalty 5) in the format of format.html; one case; solution is a Timetable.csv (format.html line 259)
23
  Origin: generated algorithmically with LinTim (solutions.html line 373)
24
- Reference result: proven optimum
25
- Reference source: solutions.html line 392 status "solved optimally"; line 471 best objective 21466 (P. Schiewe, A. Schoebel, Transportation Science)
26
  Check: Program: check every activity duration of the agent's Timetable.csv lies within its periodic bounds (mod period), then route passengers by shortest paths (format.html line 284) with the change penalty and require total travel time at most 21466
27
  - `data/Hamburg.zip`: TimPassLib instance Hamburg (S-Bahn Hamburg, 68 stations, 7 lines): best objective 140850920, lower bound 139892927.
28
  Format: zip of 4 CSV files (Activities.csv, Events.csv, OD.csv, Config.csv; period_length 10, ean_change_penalty 5); one case
29
  Origin: OD matrix from automatic passenger counts, annual timetable 2023 (solutions.html lines 66 to 85); aggregated counts, no persons
30
- Reference result: best known objective (not proven optimal)
31
- Reference source: solutions.html line 172: 140850920 (B. Ramos, 31.08.2026); line 195 lower bound 139892927
32
  Check: Program: as for toy, feasibility of the periodic timetable then shortest-path routing with change penalty; total travel time at most 140850920
 
8
 
9
  **Self-contained:** Each file is self-contained.
10
 
 
 
11
  **Tools to open and check:** Check: Program: check every activity duration of the agent's Timetable.csv lies within its periodic bounds (mod period), then route passengers by shortest paths (format.html line 284) with the change penalty and require total travel time at most 21466; Program: as for toy, feasibility of the periodic timetable then shortest-path routing with change penalty; total travel time at most 140850920.
12
 
13
  **Licence (SPDX):** MIT AND CC-BY-4.0
 
19
  - `data/toy.zip`: TimPassLib instance toy: integrated periodic timetabling and passenger routing, solved optimally (objective 21466).
20
  Format: zip of 4 CSV files (Activities.csv, Events.csv, OD.csv, Config.csv; period_length 60, ean_change_penalty 5) in the format of format.html; one case; solution is a Timetable.csv (format.html line 259)
21
  Origin: generated algorithmically with LinTim (solutions.html line 373)
 
 
22
  Check: Program: check every activity duration of the agent's Timetable.csv lies within its periodic bounds (mod period), then route passengers by shortest paths (format.html line 284) with the change penalty and require total travel time at most 21466
23
  - `data/Hamburg.zip`: TimPassLib instance Hamburg (S-Bahn Hamburg, 68 stations, 7 lines): best objective 140850920, lower bound 139892927.
24
  Format: zip of 4 CSV files (Activities.csv, Events.csv, OD.csv, Config.csv; period_length 10, ean_change_penalty 5); one case
25
  Origin: OD matrix from automatic passenger counts, annual timetable 2023 (solutions.html lines 66 to 85); aggregated counts, no persons
 
 
26
  Check: Program: as for toy, feasibility of the periodic timetable then shortest-path routing with change penalty; total travel time at most 140850920
campaign_files/2026-10-g-solver-instances-2/trick-traveling-tournament/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained.
10
 
11
- **Answers:** No answer files are included. Reference result: Proven optimum (objective value). Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Program: check the submitted 10-slot schedule is a double round robin (every ordered pair plays once), has no more than three consecutive home or away games per team, no repeaters (index.html lines 49 to 51); compute the total distance with teams starting and ending at home (line 52) and require it at most 23916.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,6 +19,4 @@ Files:
21
  - `TOURN/data6.txt`: Traveling Tournament Problem instance NL6: 6-team distance matrix, double round robin, proven optimum 23916.
22
  Format: plain text 6 by 6 integer distance matrix (team order ATL NYM PHI MON FLA PIT per index.html); one case; the rules are stated on index.html lines 49 to 52
23
  Origin: classic sports timetabling benchmark from Easton, Nemhauser and Trick (2001); index.html line 14 says the page is no longer updated and points to RobinX
24
- Reference result: proven optimum (objective value)
25
- Reference source: TOURN/index.html lines 91 to 93: NL6 feasible solution 23916 (Easton May 7, 1999) and lower bound 23916 (Easton, September 27, 1999), so 23916 is optimal
26
  Check: Program: check the submitted 10-slot schedule is a double round robin (every ordered pair plays once), has no more than three consecutive home or away games per team, no repeaters (index.html lines 49 to 51); compute the total distance with teams starting and ending at home (line 52) and require it at most 23916
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** Check: Program: check the submitted 10-slot schedule is a double round robin (every ordered pair plays once), has no more than three consecutive home or away games per team, no repeaters (index.html lines 49 to 51); compute the total distance with teams starting and ending at home (line 52) and require it at most 23916.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `TOURN/data6.txt`: Traveling Tournament Problem instance NL6: 6-team distance matrix, double round robin, proven optimum 23916.
20
  Format: plain text 6 by 6 integer distance matrix (team order ATL NYM PHI MON FLA PIT per index.html); one case; the rules are stated on index.html lines 49 to 52
21
  Origin: classic sports timetabling benchmark from Easton, Nemhauser and Trick (2001); index.html line 14 says the page is no longer updated and points to RobinX
 
 
22
  Check: Program: check the submitted 10-slot schedule is a double round robin (every ordered pair plays once), has no more than three consecutive home or away games per team, no repeaters (index.html lines 49 to 51); compute the total distance with teams starting and ending at home (line 52) and require it at most 23916
campaign_files/2026-10-g-solver-instances-2/trick-ttp/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Proven optimum (feasible solution equals lower bound). Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Program: read the agent's schedule (opponent and home or away per team per slot), check the double round robin, at most three consecutive home or away games, no repeaters, then sum each team's travel starting and ending at home using data8.txt; pass when the total is at most 39721.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `TOURN/data8.txt`: Traveling tournament problem NL8 (8 teams, double round robin); optimum distance 39721.
22
  Format: 8 by 8 integer distance matrix, one row per line; team order Atl Nym Phi Mon Fla Pit Cin Chi as in the NL8 tables on index.html lines 137 to 151
23
  Origin: Easton, Nemhauser and Trick traveling tournament problem, NL instances
24
- Reference result: proven optimum (feasible solution equals lower bound)
25
- Reference source: TOURN/index.html lines 129 to 133 (NL8 entry): feasible solution 39721 (Easton, August 25 2002) and lower bound 39721 (Irnich and Schrempp, June 24 2008); rules on lines 49 to 52
26
  Check: Program: read the agent's schedule (opponent and home or away per team per slot), check the double round robin, at most three consecutive home or away games, no repeaters, then sum each team's travel starting and ending at home using data8.txt; pass when the total is at most 39721.
27
  Companions (not included): TOURN/index.html
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Program: read the agent's schedule (opponent and home or away per team per slot), check the double round robin, at most three consecutive home or away games, no repeaters, then sum each team's travel starting and ending at home using data8.txt; pass when the total is at most 39721.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `TOURN/data8.txt`: Traveling tournament problem NL8 (8 teams, double round robin); optimum distance 39721.
20
  Format: 8 by 8 integer distance matrix, one row per line; team order Atl Nym Phi Mon Fla Pit Cin Chi as in the NL8 tables on index.html lines 137 to 151
21
  Origin: Easton, Nemhauser and Trick traveling tournament problem, NL instances
 
 
22
  Check: Program: read the agent's schedule (opponent and home or away per team per slot), check the double round robin, at most three consecutive home or away games, no repeaters, then sum each team's travel starting and ending at home using data8.txt; pass when the total is at most 39721.
23
  Companions (not included): TOURN/index.html
campaign_files/2026-10-g-solver-instances-2/tuwien-dbai-shift-design/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Each unit is self-contained.
10
 
11
- **Answers:** No answer files are included. Reference result: Best known objective (fitness) stored in the unit file. Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** Check: Program: parse the agent's shifts (start, length, workers per weekday), check each start and length lies within the file's shift templates, compute shortage plus excess (in worker-minutes, weight 1) plus 60 per shift used plus 1000 per duties-per-week violation, and require the total at most 720; Program: parse the agent's shifts (start, length, workers per weekday), check each start and length lies within the file's shift templates, compute shortage plus excess (in worker-minutes, weight 1) plus 30 per shift used plus 1000 per duties-per-week violation, and require the total at most 330.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -22,13 +20,9 @@ Units:
22
  Read out of the archive: https://www.dbai.tuwien.ac.at/proj/Rota/DataSet2.zip
23
  Format: plain text, '#'-commented sections (slot length, cycle, requirements per slot and day, shift types, weights); lines 42 to 43 give 'Fitness of assumed optimal Solution: 720' and lines 45 onward the solution itself
24
  Origin: randomly generated set from Musliu, Schaerf and Slany, 'Local search for shift design' (EJOR 2004); Set 2 instances 1 to 10 were constructed so that the best known solution has 12 shifts (benchmarks.html lines 86 to 87)
25
- Reference result: best known objective (fitness) stored in the unit file
26
- Reference source: DataSet2/RandomExample1.txt lines 42 to 43: '#Fitness of assumed optimal Solution: # 720'; the solution is listed in lines 45 onward (12 shifts); benchmarks.html line 71 gives the weights
27
  Check: Program: parse the agent's shifts (start, length, workers per weekday), check each start and length lies within the file's shift templates, compute shortage plus excess (in worker-minutes, weight 1) plus 60 per shift used plus 1000 per duties-per-week violation, and require the total at most 720
28
  - `DataSet1/RandomExample10.txt`: Shift design instance DataSet1 RandomExample10.txt: weekly staffing curve, 30-minute slots, assumed optimal fitness 330 stored in the file.
29
  Read out of the archive: https://www.dbai.tuwien.ac.at/proj/Rota/DataSet1.zip
30
  Format: plain text, '#'-commented sections (slot length, cycle, requirements per slot and day, shift types, weights); lines 42 to 43 give 'Fitness of assumed optimal Solution: 330' and lines 45 onward the solution itself
31
  Origin: randomly generated set from Musliu, Schaerf and Slany, 'Local search for shift design' (EJOR 2004); Set 1, generator rules in benchmarks.html lines 50 to 80
32
- Reference result: best known objective (fitness) stored in the unit file
33
- Reference source: DataSet1/RandomExample10.txt lines 42 to 43: '#Fitness of assumed optimal Solution: # 330'; the solution is listed in lines 45 onward (11 shifts); benchmarks.html line 71 gives the weights
34
  Check: Program: parse the agent's shifts (start, length, workers per weekday), check each start and length lies within the file's shift templates, compute shortage plus excess (in worker-minutes, weight 1) plus 30 per shift used plus 1000 per duties-per-week violation, and require the total at most 330
 
8
 
9
  **Self-contained:** Each unit is self-contained.
10
 
 
 
11
  **Tools to open and check:** Check: Program: parse the agent's shifts (start, length, workers per weekday), check each start and length lies within the file's shift templates, compute shortage plus excess (in worker-minutes, weight 1) plus 60 per shift used plus 1000 per duties-per-week violation, and require the total at most 720; Program: parse the agent's shifts (start, length, workers per weekday), check each start and length lies within the file's shift templates, compute shortage plus excess (in worker-minutes, weight 1) plus 30 per shift used plus 1000 per duties-per-week violation, and require the total at most 330.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
20
  Read out of the archive: https://www.dbai.tuwien.ac.at/proj/Rota/DataSet2.zip
21
  Format: plain text, '#'-commented sections (slot length, cycle, requirements per slot and day, shift types, weights); lines 42 to 43 give 'Fitness of assumed optimal Solution: 720' and lines 45 onward the solution itself
22
  Origin: randomly generated set from Musliu, Schaerf and Slany, 'Local search for shift design' (EJOR 2004); Set 2 instances 1 to 10 were constructed so that the best known solution has 12 shifts (benchmarks.html lines 86 to 87)
 
 
23
  Check: Program: parse the agent's shifts (start, length, workers per weekday), check each start and length lies within the file's shift templates, compute shortage plus excess (in worker-minutes, weight 1) plus 60 per shift used plus 1000 per duties-per-week violation, and require the total at most 720
24
  - `DataSet1/RandomExample10.txt`: Shift design instance DataSet1 RandomExample10.txt: weekly staffing curve, 30-minute slots, assumed optimal fitness 330 stored in the file.
25
  Read out of the archive: https://www.dbai.tuwien.ac.at/proj/Rota/DataSet1.zip
26
  Format: plain text, '#'-commented sections (slot length, cycle, requirements per slot and day, shift types, weights); lines 42 to 43 give 'Fitness of assumed optimal Solution: 330' and lines 45 onward the solution itself
27
  Origin: randomly generated set from Musliu, Schaerf and Slany, 'Local search for shift design' (EJOR 2004); Set 1, generator rules in benchmarks.html lines 50 to 80
 
 
28
  Check: Program: parse the agent's shifts (start, length, workers per weekday), check each start and length lies within the file's shift templates, compute shortage plus excess (in worker-minutes, weight 1) plus 30 per shift used plus 1000 per duties-per-week violation, and require the total at most 330
campaign_files/2026-10-g-solver-instances-2/tuwien-musliu-rotating-workforce/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Feasibility with published witness solution. Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** Check: Program: parse the agent's 9 by 7 cyclic schedule; require the count of each shift on each day to equal the demand matrix exactly, every shift block, work block and days-off block (read cyclically) within the bounds, and no forbidden successions N-D, N-A, A-D; pass if all hold.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -22,7 +20,5 @@ Units:
22
  Read out of the archive: https://www.dbai.tuwien.ac.at/staff/musliu/benchmarks/workforceScheduling.zip
23
  Format: plain text, '#'-commented sections: schedule length, employees, shifts, temporal requirements matrix (lines 10 to 13), shift block bounds (lines 15 to 18), days-off and work block bounds (lines 20 to 24), forbidden sequences (lines 29 onward)
24
  Origin: benchmark of Musliu, 'Heuristic Methods for Automatic Rotating Workforce Scheduling' (IJCIR 2006), cited at the foot of solutions.txt
25
- Reference result: feasibility with published witness solution
26
- Reference source: benchmarks/solutions.txt line 10 '-----PROBLEM...1 SOLUTION' and the 9 rows after it.
27
  Check: Program: parse the agent's 9 by 7 cyclic schedule; require the count of each shift on each day to equal the demand matrix exactly, every shift block, work block and days-off block (read cyclically) within the bounds, and no forbidden successions N-D, N-A, A-D; pass if all hold
28
  Companions (not included): benchmarks/solutions.txt
 
8
 
9
  **Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Program: parse the agent's 9 by 7 cyclic schedule; require the count of each shift on each day to equal the demand matrix exactly, every shift block, work block and days-off block (read cyclically) within the bounds, and no forbidden successions N-D, N-A, A-D; pass if all hold.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
20
  Read out of the archive: https://www.dbai.tuwien.ac.at/staff/musliu/benchmarks/workforceScheduling.zip
21
  Format: plain text, '#'-commented sections: schedule length, employees, shifts, temporal requirements matrix (lines 10 to 13), shift block bounds (lines 15 to 18), days-off and work block bounds (lines 20 to 24), forbidden sequences (lines 29 onward)
22
  Origin: benchmark of Musliu, 'Heuristic Methods for Automatic Rotating Workforce Scheduling' (IJCIR 2006), cited at the foot of solutions.txt
 
 
23
  Check: Program: parse the agent's 9 by 7 cyclic schedule; require the count of each shift on each day to equal the demand matrix exactly, every shift block, work block and days-off block (read cyclically) within the bounds, and no forbidden successions N-D, N-A, A-D; pass if all hold
24
  Companions (not included): benchmarks/solutions.txt
campaign_files/2026-10-hw-eda-tests-2/tock-libtock-c-examples-and-tock-tock-tools-ci-qemu-virt-ci-runner-github/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each unit needs other upstream files is not stated. 7 of 7 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: emulator_serial_substrings; emulator_serial_and_screen_hash. Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** Tools are named in the check written per unit in the notes.
14
 
15
  **Licence (SPDX):** Apache-2.0 OR MIT
@@ -21,56 +19,42 @@ Units:
21
  - `examples/tests/console/console/` (3 files): Tock on emulated RISC-V: console echo app; after "Entering main loop." it must answer each received character with "Got character: '<c>'".
22
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
23
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "console"
24
- Reference result: emulator_serial_substrings
25
- Reference source: tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs lines 89-113 (test case "console"): needle "Entering main loop." then send "a" and expect "Got character: 'a'", send "R" and expect "Got character: 'R'"
26
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "console" and passes only if every step passes.
27
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
28
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
29
  - `examples/tests/button_print/` (3 files): Tock on emulated RISC-V: button event app; a key press injected through QEMU must print "Button Press! Button: 0 Status: 0".
30
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
31
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "button_print"
32
- Reference result: emulator_serial_substrings
33
- Reference source: tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs lines 74-88 (test case "button_print"): sleep 500 ms, send key "up" through QMP, expect "Button Press! Button: 0 Status: 0"
34
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "button_print" and passes only if every step passes.
35
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
36
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
37
  - `examples/tests/exit/` (3 files): Tock on emulated RISC-V: app exit; the app must print "Testing exit." and "Exiting." then terminate so that the process console list shows it as Terminated.
38
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
39
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "exit"
40
- Reference result: emulator_serial_substrings
41
- Reference source: tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs lines 161-179 (test case "exit"): needles "Testing exit.", "Exiting." in order, then after sending "list\n\r" to the process console the needles "exit", "Terminated" in order
42
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "exit" and passes only if every step passes.
43
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
44
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
45
  - `examples/tests/led/led-odd/` (3 files): Tock on emulated RISC-V: LED pattern app; after "Entering main loop." the emulated LED panel screen must match a recorded SHA-256 screendump hash.
46
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
47
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "led-odd"
48
- Reference result: emulator_serial_and_screen_hash
49
- Reference source: tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs lines 32-44 (test case "led-odd"): needle "Entering main loop.", then screen hash c4d49a185592f23074ae5b83caa7d506967fbe8f93a547fa60de93bc2ddd282f (line 42)
50
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "led-odd" and passes only if every step passes. The screen hash depends on the QEMU display model, so the QEMU version must be pinned to one the hash was recorded with.
51
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
52
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
53
  - `examples/tests/u8g2-demos/tock-logo/` (4 files): Tock on emulated RISC-V: u8g2 display demo drawing the Tock logo; the emulated screen must match a recorded SHA-256 screendump hash.
54
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
55
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "tock-logo"
56
- Reference result: emulator_serial_and_screen_hash
57
- Reference source: tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs lines 45-57 (test case "tock-logo"): needle "Entering main loop.", then screen hash 4150b38c3cf468a388c0a09eb309ac8c480f692599cc0fc3e2684e0fafb5463d (line 55)
58
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "tock-logo" and passes only if every step passes. The screen hash depends on the QEMU display model, so the QEMU version must be pinned to one the hash was recorded with.
59
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
60
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
61
  - `examples/c_hello/` (2 files): Tock on emulated RISC-V: hello app; must print "Hello World!" on boot, coexist with the process console prompt and survive a serial byte arriving before it starts.
62
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
63
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "c_hello", "hello-pconsole", "unexpected-rx"
64
- Reference result: emulator_serial_substrings
65
- Reference source: tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs lines 21-31 ("c_hello": "Hello World!"), 114-128 ("hello-pconsole": send "\n\r", expect "Hello World!" and "tock$" in any order), 180-192 ("unexpected-rx": send "a" first, expect "Hello World!")
66
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "c_hello", "hello-pconsole" and "unexpected-rx" and passes only if every step passes.
67
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
68
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
69
  - `examples/blink/` (3 files): Tock on emulated RISC-V: LED blink app loaded together with c_hello; the process console "list" command must show both processes.
70
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
71
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "pconsole-list"
72
- Reference result: emulator_serial_substrings
73
- Reference source: tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs lines 146-160 (test case "pconsole-list", apps c_hello and blink): after sending "list\n\r" expect "blink" and "c_hello" in any order
74
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "pconsole-list" and passes only if every step passes. The c_hello app is loaded as the second process (companion files examples/c_hello/).
75
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT; examples/c_hello/Makefile; examples/c_hello/main.c
76
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
 
8
 
9
  **Self-contained:** Whether each unit needs other upstream files is not stated. 7 of 7 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** Tools are named in the check written per unit in the notes.
12
 
13
  **Licence (SPDX):** Apache-2.0 OR MIT
 
19
  - `examples/tests/console/console/` (3 files): Tock on emulated RISC-V: console echo app; after "Entering main loop." it must answer each received character with "Got character: '<c>'".
20
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
21
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "console"
 
 
22
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "console" and passes only if every step passes.
23
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
24
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
25
  - `examples/tests/button_print/` (3 files): Tock on emulated RISC-V: button event app; a key press injected through QEMU must print "Button Press! Button: 0 Status: 0".
26
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
27
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "button_print"
 
 
28
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "button_print" and passes only if every step passes.
29
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
30
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
31
  - `examples/tests/exit/` (3 files): Tock on emulated RISC-V: app exit; the app must print "Testing exit." and "Exiting." then terminate so that the process console list shows it as Terminated.
32
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
33
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "exit"
 
 
34
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "exit" and passes only if every step passes.
35
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
36
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
37
  - `examples/tests/led/led-odd/` (3 files): Tock on emulated RISC-V: LED pattern app; after "Entering main loop." the emulated LED panel screen must match a recorded SHA-256 screendump hash.
38
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
39
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "led-odd"
 
 
40
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "led-odd" and passes only if every step passes. The screen hash depends on the QEMU display model, so the QEMU version must be pinned to one the hash was recorded with.
41
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
42
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
43
  - `examples/tests/u8g2-demos/tock-logo/` (4 files): Tock on emulated RISC-V: u8g2 display demo drawing the Tock logo; the emulated screen must match a recorded SHA-256 screendump hash.
44
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
45
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "tock-logo"
 
 
46
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "tock-logo" and passes only if every step passes. The screen hash depends on the QEMU display model, so the QEMU version must be pinned to one the hash was recorded with.
47
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
48
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
49
  - `examples/c_hello/` (2 files): Tock on emulated RISC-V: hello app; must print "Hello World!" on boot, coexist with the process console prompt and survive a serial byte arriving before it starts.
50
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
51
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "c_hello", "hello-pconsole", "unexpected-rx"
 
 
52
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "c_hello", "hello-pconsole" and "unexpected-rx" and passes only if every step passes.
53
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT
54
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
55
  - `examples/blink/` (3 files): Tock on emulated RISC-V: LED blink app loaded together with c_hello; the process console "list" command must show both processes.
56
  Format: libtock-c C app directory (Makefile, main.c, README.md) built to a TAB with elf2tab and loaded next to the Tock kernel in QEMU; expectations in a Rust test table of the CI runner
57
  Origin: a libtock-c userspace app that tock/tock CI runs on the Tock kernel inside qemu-system-riscv64 (board qemu_rv64_virt); the expected serial strings (and screen hash where present) are written by the Tock project in the runner board file; test case(s): "pconsole-list"
 
 
58
  Check: Task: given the app (or a broken or blank variant of it) and the board, write or repair the libtock-c app so that its run on the emulated board meets the runner expectations. Judge: build the qemu_rv64_virt test-ci kernel and the app, run tools/ci/qemu-virt-ci-runner with --board qemu_rv64_virt --libtock-c <dir>; it boots QEMU, performs the steps of test case "pconsole-list" and passes only if every step passes. The c_hello app is loaded as the second process (companion files examples/c_hello/).
59
  Companions (not included): tock/tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tock/tools/ci/qemu-virt-ci-runner/src/main.rs; tock/tools/ci/qemu-virt-ci-runner/README.md; tock/LICENSE-APACHE; tock/LICENSE-MIT; LICENSE-APACHE; LICENSE-MIT; examples/c_hello/Makefile; examples/c_hello/main.c
60
  Dependencies: Tock kernel for board qemu_rv64_virt (boards/configurations/qemu_rv64_virt/qemu_rv64_virt-test-ci) built from tock/tock at commit 101a9939 (whole kernel tree, Rust nightly toolchain pinned by its rust-toolchain file; not packed); libtock-c libraries (libtock, libtock-sync, newlib/libc++ fetched by its build) from tock/libtock-c at commit ab071148 (not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
campaign_files/2026-10-hw-eda-tests-2/tock-tock-capsules-core-and-tools-ci-qemu-virt-ci-runner-github/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: emulator_serial_substrings. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Task: given the process console capsule with its help output or command dispatch removed or broken, restore it so that the kernel answers "help" with the exact command list. pass only if the needle is seen in time.
14
 
15
  **Licence (SPDX):** Apache-2.0 OR MIT
@@ -21,8 +19,6 @@ Files:
21
  - `capsules/core/src/process_console.rs`: Tock kernel on emulated RISC-V: process console capsule; the "help" command must print the exact list of valid commands.
22
  Format: one Rust source file of the Tock kernel (capsule), compiled into the qemu_rv64_virt test-ci kernel; expectations in a Rust test table of the CI runner
23
  Origin: the Tock kernel process console capsule; tock/tock CI boots the kernel with no apps in qemu-system-riscv64 (board qemu_rv64_virt), sends "help" and checks the exact command list line (test case "pconsole-help")
24
- Reference result: emulator_serial_substrings
25
- Reference source: tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs lines 129-145 (test case "pconsole-help", no apps): after sending "help\n\r" expect the line "Valid commands are: help status list stop start fault boot terminate process kernel reset panic console-start console-stop" (line 138)
26
  Check: Task: given the process console capsule with its help output or command dispatch removed or broken, restore it so that the kernel answers "help" with the exact command list. pass only if the needle is seen in time.
27
  Companions (not included): tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tools/ci/qemu-virt-ci-runner/src/main.rs; tools/ci/qemu-virt-ci-runner/README.md; LICENSE-APACHE; LICENSE-MIT
28
  Dependencies: the rest of the Tock kernel tree at commit 101a9939 (the capsule compiles only inside the kernel crates; whole tree, not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Task: given the process console capsule with its help output or command dispatch removed or broken, restore it so that the kernel answers "help" with the exact command list. pass only if the needle is seen in time.
12
 
13
  **Licence (SPDX):** Apache-2.0 OR MIT
 
19
  - `capsules/core/src/process_console.rs`: Tock kernel on emulated RISC-V: process console capsule; the "help" command must print the exact list of valid commands.
20
  Format: one Rust source file of the Tock kernel (capsule), compiled into the qemu_rv64_virt test-ci kernel; expectations in a Rust test table of the CI runner
21
  Origin: the Tock kernel process console capsule; tock/tock CI boots the kernel with no apps in qemu-system-riscv64 (board qemu_rv64_virt), sends "help" and checks the exact command list line (test case "pconsole-help")
 
 
22
  Check: Task: given the process console capsule with its help output or command dispatch removed or broken, restore it so that the kernel answers "help" with the exact command list. pass only if the needle is seen in time.
23
  Companions (not included): tools/ci/qemu-virt-ci-runner/src/boards/qemu_rv64_virt.rs; tools/ci/qemu-virt-ci-runner/src/main.rs; tools/ci/qemu-virt-ci-runner/README.md; LICENSE-APACHE; LICENSE-MIT
24
  Dependencies: the rest of the Tock kernel tree at commit 101a9939 (the capsule compiles only inside the kernel crates; whole tree, not packed); qemu-system-riscv64; RISC-V GCC (riscv64-unknown-elf), elf2tab and tockloader as used by .github/workflows/qemu_virt.yml of tock/tock; the CI runner tools/ci/qemu-virt-ci-runner (Rust; the board file and main.rs are packed as companions, its Cargo.toml and the rest of the crate are not)
campaign_files/2026-10-hw-eda-tests-2/tscircuit-checks-tests-assets-fixtures-and-tests-lib-answer-carrying-e8ea1860/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 24 of 24 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: drc_violation_count. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `tests/assets/traces1.solution.json`: Tscircuit DRC fixture traces1: an autorouter solution where checkEachPcbTraceNonOverlapping must report exactly 1 trace overlap error.
22
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
23
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
24
- Reference result: drc_violation_count
25
- Reference source: tests/lib/check-each-pcb-trace-non-overlapping/overlapping-bug-traces1.test.ts: exactly 1 error from checkEachPcbTraceNonOverlapping
26
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
27
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
28
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/overlapping-bug-traces1.test.ts
@@ -30,8 +26,6 @@ Files:
30
  - `tests/assets/traces2.solution.json`: Tscircuit DRC fixture traces2: an autorouter solution where checkEachPcbTraceNonOverlapping must report exactly 12 trace overlap errors.
31
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
32
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
33
- Reference result: drc_violation_count
34
- Reference source: tests/lib/check-each-pcb-trace-non-overlapping/overlapping-bug-traces2.test.ts: exactly 12 errors from checkEachPcbTraceNonOverlapping
35
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
36
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
37
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/overlapping-bug-traces2.test.ts
@@ -39,8 +33,6 @@ Files:
39
  - `tests/assets/traces3.solution.json`: Tscircuit DRC fixture traces3: exactly 1 trace overlap error and exactly 1 pad to trace clearance error.
40
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
41
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
42
- Reference result: drc_violation_count
43
- Reference source: tests/lib/check-each-pcb-trace-non-overlapping/overlapping-bug-traces3.test.ts: exactly 1 error from checkEachPcbTraceNonOverlapping and exactly 1 from checkPadTraceClearance
44
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
45
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
46
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/overlapping-bug-traces3.test.ts
@@ -48,8 +40,6 @@ Files:
48
  - `tests/assets/via-too-close-to-trace.json`: Tscircuit DRC fixture via-too-close-to-trace: no trace overlap, exactly 1 via to trace clearance error with a positive measured clearance.
49
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
50
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
51
- Reference result: drc_violation_count
52
- Reference source: tests/lib/check-each-pcb-trace-non-overlapping/vias-in-trace-margin.test.ts: checkEachPcbTraceNonOverlapping returns no errors; checkViaTraceClearance returns exactly 1 error whose actual_clearance is above 0
53
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
54
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
55
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/vias-in-trace-margin.test.ts
@@ -57,8 +47,6 @@ Files:
57
  - `tests/assets/breakout-repros/repro-breakout-sot23-regulator-overlap.json`: Tscircuit DRC fixture SOT-23 regulator breakout: after removing stored error elements, runAllRoutingChecks must report exactly 2 pad to trace clearance errors at two given pad centres.
58
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
59
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
60
- Reference result: drc_violation_count
61
- Reference source: tests/lib/breakout/repro-breakout-sot23-regulator-overlap.test.ts: after filtering out every element whose type ends in _error, runAllRoutingChecks returns exactly 2 errors, both "too close" pad to trace clearance errors, none of the overlap, disconnected endpoint or missing connection kinds; each pad to trace clearance error centre lies at distance 0.75 + actual_clearance / 2 from (-4.73, -1), the edge of a circular plated hole
62
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: the fixture stores 9 pcb_trace_error and 2 pcb_pad_trace_clearance_error elements from an earlier run; strip every element whose type ends in _error before handing it to the agent, as the test does at lines 8-10.
63
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
64
  Companions (not included): tests/lib/breakout/repro-breakout-sot23-regulator-overlap.test.ts
@@ -66,8 +54,6 @@ Files:
66
  - `tests/assets/component-out-of-L-board-shape.json`: Tscircuit DRC fixture L-shaped board: exactly 1 component (pcb_component_0) lies outside the board outline.
67
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
68
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
69
- Reference result: drc_violation_count
70
- Reference source: tests/lib/pcb-component-boundary/component-out-of-L-shaped board.test.ts: checkPcbComponentsOutOfBoard returns exactly 1 error, for pcb_component_0
71
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
72
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
73
  Companions (not included): tests/lib/pcb-component-boundary/component-out-of-L-shaped board.test.ts
@@ -75,8 +61,6 @@ Files:
75
  - `tests/assets/component-out-of-board.json`: Tscircuit DRC fixture rectangular board: exactly 1 component (pcb_component_0) lies outside the board.
76
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
77
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
78
- Reference result: drc_violation_count
79
- Reference source: tests/lib/pcb-component-boundary/component-out-of-board.test.ts: checkPcbComponentsOutOfBoard returns exactly 1 error, for pcb_component_0
80
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
81
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
82
  Companions (not included): tests/lib/pcb-component-boundary/component-out-of-board.test.ts
@@ -84,8 +68,6 @@ Files:
84
  - `tests/assets/component-out-of-hex-board-shape.json`: Tscircuit DRC fixture hexagonal board: exactly 1 component (pcb_component_3) lies outside the board outline.
85
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
86
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
87
- Reference result: drc_violation_count
88
- Reference source: tests/lib/pcb-component-boundary/component-out-of-hex-board.test.ts: checkPcbComponentsOutOfBoard returns exactly 1 error, for pcb_component_3
89
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
90
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
91
  Companions (not included): tests/lib/pcb-component-boundary/component-out-of-hex-board.test.ts
@@ -93,8 +75,6 @@ Files:
93
  - `tests/assets/component-out-of-polygon-board.json`: Tscircuit DRC fixture polygon board: exactly 1 component (pcb_component_1) lies outside the board outline.
94
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
95
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
96
- Reference result: drc_violation_count
97
- Reference source: tests/lib/pcb-component-boundary/component-out-of-polygon-board.test.ts: checkPcbComponentsOutOfBoard returns exactly 1 error, for pcb_component_1
98
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
99
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
100
  Companions (not included): tests/lib/pcb-component-boundary/component-out-of-polygon-board.test.ts
@@ -102,8 +82,6 @@ Files:
102
  - `tests/assets/traces-outside-board.json`: Tscircuit DRC fixture traces outside board: of 4 traces, exactly trace_outside_right, trace_outside_top and trace_crossing_boundary violate the board edge, trace_inside does not.
103
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
104
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
105
- Reference result: drc_violation_count
106
- Reference source: tests/lib/check-trace-out-of-board/check-trace-out-of-board.test.ts: checkPcbTracesOutOfBoard flags trace_outside_right, trace_outside_top and trace_crossing_boundary and does not flag trace_inside; error count is at least 3 (one trace may give more than one error)
107
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
108
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
109
  Companions (not included): tests/lib/check-trace-out-of-board/check-trace-out-of-board.test.ts
@@ -111,8 +89,6 @@ Files:
111
  - `tests/assets/traces-u-shaped-board.json`: Tscircuit DRC fixture U-shaped board: of 3 traces only trace_bad_crosses_gap crosses the board gap.
112
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
113
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
114
- Reference result: drc_violation_count
115
- Reference source: tests/lib/check-trace-out-of-board/u-shaped-board.test.ts: checkPcbTracesOutOfBoard flags trace_bad_crosses_gap and neither trace_good_left nor trace_good_right; error count at least 1
116
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
117
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
118
  Companions (not included): tests/lib/check-trace-out-of-board/u-shaped-board.test.ts
@@ -120,8 +96,6 @@ Files:
120
  - `tests/assets/keyboard1.json`: Tscircuit DRC fixture keyboard1: a routed keyboard PCB with exactly 27 trace overlap errors and 21 pad, via and hole clearance errors (48 in all).
121
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
122
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
123
- Reference result: drc_violation_count
124
- Reference source: tests/lib/check-each-pcb-trace-non-overlapping/keyboard1.test.ts: checkEachPcbTraceNonOverlapping errors of type pcb_trace_error: exactly 27; checkPadTraceClearance plus checkViaTraceClearance plus checkHoleTraceClearance: exactly 21; total 48
125
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
126
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
127
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/keyboard1.test.ts
@@ -129,8 +103,6 @@ Files:
129
  - `tests/assets/keyboard-default60.json`: Tscircuit DRC fixture keyboard-default60: a routed 60 percent keyboard PCB with no trace overlap and exactly 7 trace to non-plated hole clearance errors under the 0.2 mm default.
130
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
131
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
132
- Reference result: drc_violation_count
133
- Reference source: tests/lib/check-each-pcb-trace-non-overlapping/keyboard-default60.test.ts: checkEachPcbTraceNonOverlapping returns no errors; checkHoleTraceClearance returns exactly 7 errors, every message containing "non-plated hole"
134
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: the fixture stores 56 stale pcb_trace_error overlap elements from an older core version (the current checker finds no overlap) and no hole clearance error; strip every element whose type ends in _error before handing it to the agent so they do not mislead.
135
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
136
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/keyboard-default60.test.ts
@@ -138,8 +110,6 @@ Files:
138
  - `tests/assets/gameboy-advance-clearance.json`: Tscircuit DRC fixture Game Boy Advance board: after removing stored error elements, pad to trace, via to trace and via to pad checks must report exactly 11 clearance errors matching the 11 stored ones.
139
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
140
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
141
- Reference result: drc_violation_count
142
- Reference source: tests/repros/gameboy-clearance-locations.test.ts: after filtering out every element whose type ends in _error, checkPadTraceClearance plus checkViaTraceClearance plus checkViaPadClearance return exactly 11 errors, in order, each matching the stored _clearance_error element at the same index on every field except its id, center and message, and no message naming a raw pcb_, source_ or schematic_ id
143
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: the fixture stores the 11 expected clearance errors (4 pcb_pad_trace_clearance_error, 1 pcb_via_trace_clearance_error, 6 pcb_pad_pad_clearance_error) and 1 pcb_placement_error; they are the answer key, so strip every element whose type ends in _error before handing it to the agent, as the test does at lines 11-13, and keep the stripped set as the reference.
144
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
145
  Companions (not included): tests/repros/gameboy-clearance-locations.test.ts
@@ -147,8 +117,6 @@ Files:
147
  - `tests/assets/repro-trace-disconnection.json`: Tscircuit DRC fixture trace disconnection repro: the continuity check must flag trace source_net_1_mst3_0 for a disconnected (floating) endpoint.
148
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
149
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
150
- Reference result: drc_violation_count
151
- Reference source: tests/lib/repro-trace-disconnection.test.ts: checkTracesAreContiguous returns at least 1 error, among them one for pcb_trace_id source_net_1_mst3_0 whose message contains "disconnected endpoint"
152
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
153
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
154
  Companions (not included): tests/lib/repro-trace-disconnection.test.ts
@@ -156,8 +124,6 @@ Files:
156
  - `tests/assets/traces-with-vias-corrupted.json`: Tscircuit DRC fixture traces-with-vias-corrupted: the continuity check must report a misaligned via and a missing pad connection on the R1.pin1 to C1.pin1 trace, with exact messages.
157
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
158
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
159
- Reference result: drc_violation_count
160
- Reference source: tests/lib/check-traces-are-contiguous.test.ts: checkTracesAreContiguous: errors[0].message is exactly "Via in trace [.R1 > .pin1 to .C1 > .pin1] is misaligned at position {x: -1.875, y: 1.875}." and errors[1].message is exactly "Trace [.R1 > .pin1 to .C1 > .pin1] is missing a connection to SMD pad C1.pin1"
161
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
162
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
163
  Companions (not included): tests/lib/check-traces-are-contiguous.test.ts
@@ -165,8 +131,6 @@ Files:
165
  - `tests/assets/pedometer-v1.1.3-missing-via.circuit.json`: Tscircuit DRC fixture pedometer v1.1.3 missing via: a 4-layer board where one trace ends on inner2 at a top-only pad without a via; the continuity, port and aggregate checks must each diagnose it.
166
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
167
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
168
- Reference result: drc_violation_count
169
- Reference source: tests/lib/pedometer-missing-via.test.ts: trace source_net_6_mst1_0 ends on inner2 at pad pcb_port_66 (top only, pcb_component_18) at (-8.20005, -3.199898) with no via; checkTracesAreContiguous, checkEachPcbPortConnectedToPcbTraces and runAllRoutingChecks each return at least one error diagnosing it (a pcb_trace_error for that trace or a pcb_port_not_connected_error listing that port); checkTracesAreContiguous returns exactly 1 such error, with center (-8.20005, -3.199898), pcb_port_ids [pcb_port_66], pcb_component_ids [pcb_component_18] and a message containing inner2
170
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
171
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
172
  Companions (not included): tests/lib/pedometer-missing-via.test.ts
@@ -174,8 +138,6 @@ Files:
174
  - `tests/assets/pedometer-pushbutton-self-connection.json`: Tscircuit netlist (ERC-style) fixture pedometer pushbutton: both schematic contacts of switch SW1_WAKE resolve to one net, and the netlist checks must report exactly one fatal misconfiguration error.
175
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
176
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
177
- Reference result: drc_violation_count
178
- Reference source: tests/repros/repro-pushbutton-connected-to-itself.test.ts: the two schematic ports of SW1_WAKE map to source ports with one shared subcircuit_connectivity_map_key; runAllNetlistChecks returns exactly one element, a source_component_misconfigured_error with message exactly "Switch SW1_WAKE has both schematic contacts connected to the same net. Check internallyConnectedPins and the footprint pin mapping.", source_component_ids [source_component_2], source_port_ids [source_port_15, source_port_16] and is_fatal true
179
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
180
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
181
  Companions (not included): tests/repros/repro-pushbutton-connected-to-itself.test.ts
@@ -183,8 +145,6 @@ Files:
183
  - `tests/assets/rc-car-style-analysis.circuit.json`: Tscircuit PCB style fixture RC car board: with style checks enabled, exactly 2 long trace segments at odd angles on pcb_trace_3 (bottom layer) must be reported, with their route indices and measurements.
184
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
185
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
186
- Reference result: drc_violation_count
187
- Reference source: tests/lib/check-pcb-trace-style.test.ts: checkPcbTraceStyle with pcbStyleChecksEnabled true returns exactly 2 pcb_trace_style_warning elements, with [start_route_index, end_route_index, layer] equal to [4, 5, bottom] and [5, 6, bottom]; the first is on pcb_trace_3 (source_trace_44), styling_issue_type long_segment_at_odd_angle, segment from (-15.5, 9.1) to (-3, -12.000000000000002), center (-9.25, -1.450000000000001), segment_length close to 24.5246814454337 and angle_deviation_degrees close to 14.35677595345652; with style checks not enabled the result is empty
188
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no pcb_trace_style_warning and no element whose type ends in _error; 25 unrelated warning elements (refdes, missing trace, courtyard, pin specification) from an earlier run, harmless for this check, may be stripped. The README companion says the board has two qualifying long segments, so hide it from the agent.
189
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
190
  Companions (not included): tests/lib/check-pcb-trace-style.test.ts; tests/assets/rc-car-style-analysis.README.md
@@ -192,8 +152,6 @@ Files:
192
  - `tests/fixtures/bt1-mounting-hole-keepout.circuit.json`: Tscircuit DRC fixture BT1 mounting-hole keepout (reduced from an ESP32 e-reader board): copper is clear of the keepout, but the battery connector courtyard enters it; exactly 1 courtyard-over-keepout placement error.
193
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
194
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
195
- Reference result: drc_violation_count
196
- Reference source: tests/lib/check-pcb-courtyard-over-keepout.test.ts: checkPcbCopperOverKeepout returns an empty list; checkPcbCourtyardOverKeepout returns exactly 1 error, of type pcb_placement_error with pcb_placement_error_id exactly "courtyard_over_keepout_pcb_component_60_pcb_keepout_0" and a message containing BT1; runAllPlacementChecks contains that same error
197
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
198
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
199
  Companions (not included): tests/lib/check-pcb-courtyard-over-keepout.test.ts
@@ -201,8 +159,6 @@ Files:
201
  - `tests/repros/repro02.json`: Tscircuit DRC fixture repro02: a board where pin 1 of the J_SWD header (plated hole) overlaps mounting hole pcb_hole_0; the placement checks must report an issue naming both.
202
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
203
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
204
- Reference result: drc_violation_count
205
- Reference source: tests/repros/repro02.test.ts: the JSON serialisation of runAllPlacementChecks(circuitJson) contains the strings pcb_plated_hole_4 and pcb_hole_0 (the J_SWD pin 1 plated hole at (-15.81, -13.5) and the mounting hole at (-15.5, -15.5)); the fixture holds no error element, so a task form asks the agent to find the overlapping pair
206
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
207
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
208
  Companions (not included): tests/repros/repro02.test.ts
@@ -210,8 +166,6 @@ Files:
210
  - `tests/fixtures/mspm0g3507-usb-c-dev-board.json`: Tscircuit DRC fixture MSPM0G3507 USB-C dev board: the ground copper pour touches pads of other nets; the copper-pour short check must report exactly the two shorts to the USB-C VBUS pads.
211
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
212
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
213
- Reference result: drc_violation_count
214
- Reference source: tests/lib/check-copper-pour-shorts.test.ts: checkCopperPourShorts returns errors whose sorted pcb_placement_error_id list equals exactly ["copper_pour_short_pcb_copper_pour_54_pcb_smtpad_10", "copper_pour_short_pcb_copper_pour_54_pcb_smtpad_11"] (two shorts between pour pcb_copper_pour_54 and the two USB-C VBUS pads)
215
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error; 1 unrelated supplier_footprint_mismatch_warning element from an earlier run, harmless for this check, may be stripped.
216
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
217
  Companions (not included): tests/lib/check-copper-pour-shorts.test.ts
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 24 of 24 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `tests/assets/traces1.solution.json`: Tscircuit DRC fixture traces1: an autorouter solution where checkEachPcbTraceNonOverlapping must report exactly 1 trace overlap error.
20
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
21
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
22
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
23
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
24
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/overlapping-bug-traces1.test.ts
 
26
  - `tests/assets/traces2.solution.json`: Tscircuit DRC fixture traces2: an autorouter solution where checkEachPcbTraceNonOverlapping must report exactly 12 trace overlap errors.
27
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
28
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
29
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
30
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
31
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/overlapping-bug-traces2.test.ts
 
33
  - `tests/assets/traces3.solution.json`: Tscircuit DRC fixture traces3: exactly 1 trace overlap error and exactly 1 pad to trace clearance error.
34
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
35
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
36
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
37
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
38
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/overlapping-bug-traces3.test.ts
 
40
  - `tests/assets/via-too-close-to-trace.json`: Tscircuit DRC fixture via-too-close-to-trace: no trace overlap, exactly 1 via to trace clearance error with a positive measured clearance.
41
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
42
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
43
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
44
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
45
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/vias-in-trace-margin.test.ts
 
47
  - `tests/assets/breakout-repros/repro-breakout-sot23-regulator-overlap.json`: Tscircuit DRC fixture SOT-23 regulator breakout: after removing stored error elements, runAllRoutingChecks must report exactly 2 pad to trace clearance errors at two given pad centres.
48
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
49
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
50
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: the fixture stores 9 pcb_trace_error and 2 pcb_pad_trace_clearance_error elements from an earlier run; strip every element whose type ends in _error before handing it to the agent, as the test does at lines 8-10.
51
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
52
  Companions (not included): tests/lib/breakout/repro-breakout-sot23-regulator-overlap.test.ts
 
54
  - `tests/assets/component-out-of-L-board-shape.json`: Tscircuit DRC fixture L-shaped board: exactly 1 component (pcb_component_0) lies outside the board outline.
55
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
56
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
57
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
58
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
59
  Companions (not included): tests/lib/pcb-component-boundary/component-out-of-L-shaped board.test.ts
 
61
  - `tests/assets/component-out-of-board.json`: Tscircuit DRC fixture rectangular board: exactly 1 component (pcb_component_0) lies outside the board.
62
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
63
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
64
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
65
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
66
  Companions (not included): tests/lib/pcb-component-boundary/component-out-of-board.test.ts
 
68
  - `tests/assets/component-out-of-hex-board-shape.json`: Tscircuit DRC fixture hexagonal board: exactly 1 component (pcb_component_3) lies outside the board outline.
69
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
70
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
71
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
72
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
73
  Companions (not included): tests/lib/pcb-component-boundary/component-out-of-hex-board.test.ts
 
75
  - `tests/assets/component-out-of-polygon-board.json`: Tscircuit DRC fixture polygon board: exactly 1 component (pcb_component_1) lies outside the board outline.
76
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
77
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
78
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
79
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
80
  Companions (not included): tests/lib/pcb-component-boundary/component-out-of-polygon-board.test.ts
 
82
  - `tests/assets/traces-outside-board.json`: Tscircuit DRC fixture traces outside board: of 4 traces, exactly trace_outside_right, trace_outside_top and trace_crossing_boundary violate the board edge, trace_inside does not.
83
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
84
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
85
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
86
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
87
  Companions (not included): tests/lib/check-trace-out-of-board/check-trace-out-of-board.test.ts
 
89
  - `tests/assets/traces-u-shaped-board.json`: Tscircuit DRC fixture U-shaped board: of 3 traces only trace_bad_crosses_gap crosses the board gap.
90
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
91
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
92
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
93
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
94
  Companions (not included): tests/lib/check-trace-out-of-board/u-shaped-board.test.ts
 
96
  - `tests/assets/keyboard1.json`: Tscircuit DRC fixture keyboard1: a routed keyboard PCB with exactly 27 trace overlap errors and 21 pad, via and hole clearance errors (48 in all).
97
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
98
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
99
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
100
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
101
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/keyboard1.test.ts
 
103
  - `tests/assets/keyboard-default60.json`: Tscircuit DRC fixture keyboard-default60: a routed 60 percent keyboard PCB with no trace overlap and exactly 7 trace to non-plated hole clearance errors under the 0.2 mm default.
104
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
105
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
106
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: the fixture stores 56 stale pcb_trace_error overlap elements from an older core version (the current checker finds no overlap) and no hole clearance error; strip every element whose type ends in _error before handing it to the agent so they do not mislead.
107
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
108
  Companions (not included): tests/lib/check-each-pcb-trace-non-overlapping/keyboard-default60.test.ts
 
110
  - `tests/assets/gameboy-advance-clearance.json`: Tscircuit DRC fixture Game Boy Advance board: after removing stored error elements, pad to trace, via to trace and via to pad checks must report exactly 11 clearance errors matching the 11 stored ones.
111
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
112
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
113
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: the fixture stores the 11 expected clearance errors (4 pcb_pad_trace_clearance_error, 1 pcb_via_trace_clearance_error, 6 pcb_pad_pad_clearance_error) and 1 pcb_placement_error; they are the answer key, so strip every element whose type ends in _error before handing it to the agent, as the test does at lines 11-13, and keep the stripped set as the reference.
114
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
115
  Companions (not included): tests/repros/gameboy-clearance-locations.test.ts
 
117
  - `tests/assets/repro-trace-disconnection.json`: Tscircuit DRC fixture trace disconnection repro: the continuity check must flag trace source_net_1_mst3_0 for a disconnected (floating) endpoint.
118
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
119
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
120
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
121
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
122
  Companions (not included): tests/lib/repro-trace-disconnection.test.ts
 
124
  - `tests/assets/traces-with-vias-corrupted.json`: Tscircuit DRC fixture traces-with-vias-corrupted: the continuity check must report a misaligned via and a missing pad connection on the R1.pin1 to C1.pin1 trace, with exact messages.
125
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
126
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
127
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
128
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
129
  Companions (not included): tests/lib/check-traces-are-contiguous.test.ts
 
131
  - `tests/assets/pedometer-v1.1.3-missing-via.circuit.json`: Tscircuit DRC fixture pedometer v1.1.3 missing via: a 4-layer board where one trace ends on inner2 at a top-only pad without a via; the continuity, port and aggregate checks must each diagnose it.
132
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
133
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
134
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
135
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
136
  Companions (not included): tests/lib/pedometer-missing-via.test.ts
 
138
  - `tests/assets/pedometer-pushbutton-self-connection.json`: Tscircuit netlist (ERC-style) fixture pedometer pushbutton: both schematic contacts of switch SW1_WAKE resolve to one net, and the netlist checks must report exactly one fatal misconfiguration error.
139
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
140
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
141
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
142
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
143
  Companions (not included): tests/repros/repro-pushbutton-connected-to-itself.test.ts
 
145
  - `tests/assets/rc-car-style-analysis.circuit.json`: Tscircuit PCB style fixture RC car board: with style checks enabled, exactly 2 long trace segments at odd angles on pcb_trace_3 (bottom layer) must be reported, with their route indices and measurements.
146
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
147
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
148
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no pcb_trace_style_warning and no element whose type ends in _error; 25 unrelated warning elements (refdes, missing trace, courtyard, pin specification) from an earlier run, harmless for this check, may be stripped. The README companion says the board has two qualifying long segments, so hide it from the agent.
149
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
150
  Companions (not included): tests/lib/check-pcb-trace-style.test.ts; tests/assets/rc-car-style-analysis.README.md
 
152
  - `tests/fixtures/bt1-mounting-hole-keepout.circuit.json`: Tscircuit DRC fixture BT1 mounting-hole keepout (reduced from an ESP32 e-reader board): copper is clear of the keepout, but the battery connector courtyard enters it; exactly 1 courtyard-over-keepout placement error.
153
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
154
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
155
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
156
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
157
  Companions (not included): tests/lib/check-pcb-courtyard-over-keepout.test.ts
 
159
  - `tests/repros/repro02.json`: Tscircuit DRC fixture repro02: a board where pin 1 of the J_SWD header (plated hole) overlaps mounting hole pcb_hole_0; the placement checks must report an issue naming both.
160
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
161
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
162
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error (scan of every element type).
163
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
164
  Companions (not included): tests/repros/repro02.test.ts
 
166
  - `tests/fixtures/mspm0g3507-usb-c-dev-board.json`: Tscircuit DRC fixture MSPM0G3507 USB-C dev board: the ground copper pour touches pads of other nets; the copper-pour short check must report exactly the two shorts to the USB-C VBUS pads.
167
  Format: tscircuit circuit JSON (array of pcb_board, pcb_component, pcb_smtpad, pcb_trace, pcb_via and source elements); TypeScript bun:test file as answer carrier
168
  Origin: regression fixture of the tscircuit DRC library; the expected values are hand-set in the test file.
 
 
169
  Check: Two routes. Upstream assertion: in a sandbox without network, check out tscircuit/checks at the pinned commit and run `bun test` on the companion test file; the unit passes when its assertions hold. Task form: give the agent the circuit JSON (and the checker name or the rule set), ask for the DRC violations (ids, kinds, counts) or a fixed layout; Hide the test file from the agent. Answer hints inside the unit: no element whose type ends in _error; 1 unrelated supplier_footprint_mismatch_warning element from an earlier run, harmless for this check, may be stripped.
170
  Tools: headless TypeScript: load the circuit JSON file and call the named @tscircuit/checks function under Bun or Node (no GUI); the tscircuit CLI (tsci) runs the same checks; circuit JSON is a plain JSON array that can also be read and edited as text with jq or Python json
171
  Companions (not included): tests/lib/check-copper-pour-shorts.test.ts
campaign_files/2026-10-m-issue-trackers-2/torproject-tor-dev/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the thread headers. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `m027-08/2019-March.txt.gz`: [tor-dev] Tor Friendliness Scanner (11 messages, 2019-03-04 to 2019-03-18).
22
  Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure. Addresses written as 'x at y'.
23
  Origin: Real list traffic in a closed past month of the list's Pipermail archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer.
24
- Reference result: facts computed from the thread headers
25
- Reference source: Message-ID, In-Reply-To, References, From and Date headers of the messages in the thread.
26
  Check: Exact match against values computed from the pinned month file: parse it as mbox, take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC and compare sender names. People are counted by person, not address (the row's scale names the people). Deterministic. The thread-cutting program was checked against a hand reading on 2 threads of this list (spec general rule 5): on the chosen thread the header closure and the Subject lines agree message for message; on a second thread every difference was traced by hand to the In-Reply-To headers (a renamed subject inside the reply chain, or a separate root with the same subject), and the program followed the headers correctly. Questions that need the body (what was asked, what fixed it) need a model or human judge and are listed separately. Hand-check second sample: 'Updating Proposal 299' (6 messages; header closure and Subject lines agree).
27
  Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `m027-08/2019-March.txt.gz`: [tor-dev] Tor Friendliness Scanner (11 messages, 2019-03-04 to 2019-03-18).
20
  Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure. Addresses written as 'x at y'.
21
  Origin: Real list traffic in a closed past month of the list's Pipermail archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer.
 
 
22
  Check: Exact match against values computed from the pinned month file: parse it as mbox, take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC and compare sender names. People are counted by person, not address (the row's scale names the people). Deterministic. The thread-cutting program was checked against a hand reading on 2 threads of this list (spec general rule 5): on the chosen thread the header closure and the Subject lines agree message for message; on a second thread every difference was traced by hand to the In-Reply-To headers (a renamed subject inside the reply chain, or a separate root with the same subject), and the program followed the headers correctly. Questions that need the body (what was asked, what fixed it) need a model or human judge and are listed separately. Hand-check second sample: 'Updating Proposal 299' (6 messages; header closure and Subject lines agree).
23
  Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
campaign_files/2026-10-m-issue-trackers-2/transdevblazefield-passenger-gtfs/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
14
 
15
  **Licence (SPDX):** OGL-UK-3.0
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/transdevblazefield/gtfs/transdevblazefield_1790939447.zip
23
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
24
  Origin: Live static GTFS feed published by transdevblazefield (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/transdevblazefield/gtfs/transdevblazefield_1790939447.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
25
- Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
26
- Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
27
  Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
28
  Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
29
  Companions (not included): calendar_dates.txt; agency.txt
 
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
12
 
13
  **Licence (SPDX):** OGL-UK-3.0
 
20
  Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/transdevblazefield/gtfs/transdevblazefield_1790939447.zip
21
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
22
  Origin: Live static GTFS feed published by transdevblazefield (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/transdevblazefield/gtfs/transdevblazefield_1790939447.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
 
 
23
  Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
24
  Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
25
  Companions (not included): calendar_dates.txt; agency.txt
campaign_files/2026-10-m-issue-trackers-2/transport-data-gouv-fr-tdg-81876/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
14
 
15
  **Licence (SPDX):** etalab-2.0
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: https://static.data.gouv.fr/resources/reseau-rtca/20260910-145902/gtfs.zip
23
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
24
  Origin: Live static GTFS feed published by Carcassonne Agglo urban network RTCA (Occitanie) at https://www.data.gouv.fr/api/1/datasets/r/941123b0-004e-4f48-81e7-8c62fb4f07aa. calendar.txt and its companions were read by member out of the zip (spec general rule 4: by member); kept as a snapshot pinned by sha256.
25
- Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
26
- Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
27
  Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
28
  Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
29
  Companions (not included): calendar_dates.txt; agency.txt
 
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
12
 
13
  **Licence (SPDX):** etalab-2.0
 
20
  Read out of the archive: https://static.data.gouv.fr/resources/reseau-rtca/20260910-145902/gtfs.zip
21
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
22
  Origin: Live static GTFS feed published by Carcassonne Agglo urban network RTCA (Occitanie) at https://www.data.gouv.fr/api/1/datasets/r/941123b0-004e-4f48-81e7-8c62fb4f07aa. calendar.txt and its companions were read by member out of the zip (spec general rule 4: by member); kept as a snapshot pinned by sha256.
 
 
23
  Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
24
  Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
25
  Companions (not included): calendar_dates.txt; agency.txt
campaign_files/2026-10-m-issue-trackers-2/trillium-bcferries-bc-ca/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: http://data.trilliumtransit.com/gtfs/bcferries-bc-ca/bcferries-bc-ca.zip
23
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
24
  Origin: Live static GTFS feed published by BC Ferries (British Columbia), hosted by Trillium Solutions, at http://data.trilliumtransit.com/gtfs/bcferries-bc-ca/bcferries-bc-ca.zip. calendar.txt and its companions were read by member out of the zip (spec general rule 4: by member); kept as a snapshot pinned by sha256.
25
- Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
26
- Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
27
  Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
28
  Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
29
  Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
 
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
12
 
13
  **Licence (SPDX):** NOASSERTION
 
20
  Read out of the archive: http://data.trilliumtransit.com/gtfs/bcferries-bc-ca/bcferries-bc-ca.zip
21
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
22
  Origin: Live static GTFS feed published by BC Ferries (British Columbia), hosted by Trillium Solutions, at http://data.trilliumtransit.com/gtfs/bcferries-bc-ca/bcferries-bc-ca.zip. calendar.txt and its companions were read by member out of the zip (spec general rule 4: by member); kept as a snapshot pinned by sha256.
 
 
23
  Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
24
  Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
25
  Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
campaign_files/2026-10-m-issue-trackers-2/trustedfirmware-tf-a/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the thread headers. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Fetch or open the thread JSON and process it with jq or Python's json module (group by sender.mailman_id, sort by date in UTC, follow parent links); the month export opens as mbox in mutt -f or Python's mailbox module.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `m259-09/thread_USJEBW46RK7SGGEBZLLLXIQDRWWIEGOU_emails.json`: [TF-A] Glitching protection (9 messages, 2021-03-26 to 2021-03-29).
22
  Format: HyperKitty REST API JSON (Mailman 3): list of the thread's messages, each with message_id, message_id_hash, subject, sender (address obfuscated, mailman_id), sender_name, date (ISO 8601 with zone), parent (URL of the parent message or null for the root) and children. The thread id is the base32 SHA-1 of the root Message-ID.
23
  Origin: Real list traffic in a closed past month of the list's archive. The unit is the HyperKitty thread JSON of one thread; HyperKitty assigns each message to the thread, so the JSON already holds the whole thread.
24
- Reference result: facts computed from the thread headers
25
- Reference source: message_id, sender, sender_name, date and parent fields of the entries in the pinned thread JSON.
26
  Check: Exact match against values computed from the pinned thread JSON: one entry per message; the root is the entry with parent null; direct replies are entries whose parent is the root's URL; dates are converted to UTC from their ISO 8601 offsets; people are counted by sender.mailman_id (one Mailman sender record per address). The first-reply interval is the exact difference in whole seconds between the root date and the earliest reply date; the dates carry one-second resolution, so no rounding is involved. Deterministic. Hand check on 2 threads of this host (general rule 5): the chosen thread and '[TF-A] Firmware FuSa workshop' (root <CAHFG_=VdbNuf9tOaOG_DMfzK8j--YrNV20nytbSmghmDG0FbkQ@mail.gmail.com>); for each, the thread JSON was compared with the same thread rebuilt from the month mbox export by two independent parsers (Python mailbox module, and a regular-expression parser); message count, people, last message time and first-reply seconds agreed on the chosen thread.
27
  Tools: Fetch or open the thread JSON and process it with jq or Python's json module (group by sender.mailman_id, sort by date in UTC, follow parent links); the month export opens as mbox in mutt -f or Python's mailbox module.
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** Fetch or open the thread JSON and process it with jq or Python's json module (group by sender.mailman_id, sort by date in UTC, follow parent links); the month export opens as mbox in mutt -f or Python's mailbox module.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `m259-09/thread_USJEBW46RK7SGGEBZLLLXIQDRWWIEGOU_emails.json`: [TF-A] Glitching protection (9 messages, 2021-03-26 to 2021-03-29).
20
  Format: HyperKitty REST API JSON (Mailman 3): list of the thread's messages, each with message_id, message_id_hash, subject, sender (address obfuscated, mailman_id), sender_name, date (ISO 8601 with zone), parent (URL of the parent message or null for the root) and children. The thread id is the base32 SHA-1 of the root Message-ID.
21
  Origin: Real list traffic in a closed past month of the list's archive. The unit is the HyperKitty thread JSON of one thread; HyperKitty assigns each message to the thread, so the JSON already holds the whole thread.
 
 
22
  Check: Exact match against values computed from the pinned thread JSON: one entry per message; the root is the entry with parent null; direct replies are entries whose parent is the root's URL; dates are converted to UTC from their ISO 8601 offsets; people are counted by sender.mailman_id (one Mailman sender record per address). The first-reply interval is the exact difference in whole seconds between the root date and the earliest reply date; the dates carry one-second resolution, so no rounding is involved. Deterministic. Hand check on 2 threads of this host (general rule 5): the chosen thread and '[TF-A] Firmware FuSa workshop' (root <CAHFG_=VdbNuf9tOaOG_DMfzK8j--YrNV20nytbSmghmDG0FbkQ@mail.gmail.com>); for each, the thread JSON was compared with the same thread rebuilt from the month mbox export by two independent parsers (Python mailbox module, and a regular-expression parser); message count, people, last message time and first-reply seconds agreed on the chosen thread.
23
  Tools: Fetch or open the thread JSON and process it with jq or Python's json module (group by sender.mailman_id, sort by date in UTC, follow parent links); the month export opens as mbox in mutt -f or Python's mailbox module.
campaign_files/2026-10-m-issue-trackers-2/tug-texhax/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the thread headers. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `m141-13/2019-March.txt.gz`: .bib help (7 messages, 2019-03-30 to 2019-03-31).
22
  Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
23
  Origin: Real list traffic in a closed past month of the list's Pipermail archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
24
- Reference result: facts computed from the thread headers
25
- Reference source: Message-ID, In-Reply-To, References, From and Date headers of the messages in the thread, read from the pinned month file.
26
  Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and 'How to get a texdoc in a window' (17 messages, root <QB1PR01MB33160204E5719CB343CEE65B9C580@QB1PR01MB3316.CANPRD01.PROD.OUTLOOK.COM>); message count, people, last sender and time, first-reply seconds and direct replies agreed on both.
27
  Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `m141-13/2019-March.txt.gz`: .bib help (7 messages, 2019-03-30 to 2019-03-31).
20
  Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
21
  Origin: Real list traffic in a closed past month of the list's Pipermail archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
 
 
22
  Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and 'How to get a texdoc in a window' (17 messages, root <QB1PR01MB33160204E5719CB343CEE65B9C580@QB1PR01MB3316.CANPRD01.PROD.OUTLOOK.COM>); message count, people, last sender and time, first-reply seconds and direct replies agreed on both.
23
  Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
campaign_files/2026-10-m-issue-trackers-2/tuhs/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the thread headers. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `m329-02/2020-March.txt.gz`: [TUHS] Question: stdio - Who invented and ... (10 messages, 2020-03-23 to 2020-03-24).
22
  Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
23
  Origin: Real list traffic in a closed past month of the list's archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
24
- Reference result: facts computed from the thread headers
25
- Reference source: Message-ID, In-Reply-To, References, From and Date headers of the messages in the thread, read from the pinned month file.
26
  Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC (a Date header without zone is read as UTC) and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and '[TUHS] Command options and complexity' (5 messages, 5 people, root <202003130304.02D343ok099975@tahoe.cs.Dartmouth.EDU>); message count, Message-ID set, last message time and first-reply seconds agreed on both.
27
  Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `m329-02/2020-March.txt.gz`: [TUHS] Question: stdio - Who invented and ... (10 messages, 2020-03-23 to 2020-03-24).
20
  Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
21
  Origin: Real list traffic in a closed past month of the list's archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
 
 
22
  Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC (a Date header without zone is read as UTC) and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and '[TUHS] Command options and complexity' (5 messages, 5 people, root <202003130304.02D343ok099975@tahoe.cs.Dartmouth.EDU>); message count, Message-ID set, last message time and first-reply seconds agreed on both.
23
  Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
campaign_files/2026-10-m-issue-trackers-2/typescript-github-issues/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the issue's own timeline (status changes, assignments, comments and their authors). Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** curl -H 'Accept: application/vnd.github+json' https://api.github.com/repos/microsoft/TypeScript/issues/43300/timeline?per_page=100 and read the JSON with jq or Python json; 'gh api repos/microsoft/TypeScript/issues/43300/timeline' reaches the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `repos/microsoft/TypeScript/issues/43300/timeline.json`: microsoft/TypeScript issue #43300: New Error: union narrowing.
22
  Format: GitHub REST API issue timeline JSON (GET /repos/{owner}/{repo}/issues/{number}/timeline, per_page=100; one page, fewer than 100 entries, so the record is complete): an array of timeline entries with 'event' (kinds in this unit: assigned, closed, commented, labeled, locked, mentioned, milestoned, subscribed), actor or user, created_at, assignee/assigner, label, commit and, for 'commented' entries, the comment body and author_association. This unit has no 'cross-referenced' entries (those embed live repository counters and are not byte-stable, see report).
23
  Origin: Live GitHub REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the timeline JSON was fetched twice apart and was byte-identical. Unit files kept only outside the repository for checking and then deleted.
24
- Reference result: facts computed from the issue's own timeline (status changes, assignments, comments and their authors)
25
- Reference source: The pinned response: repos/microsoft/TypeScript/issues/43300/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: closed/reopened/merged entries (actor, created_at), assigned/unassigned/review_requested entries (assignee or requested_reviewer, assigner or review_requester, created_at), and comments (author login, created_at). A human comment is a 'commented' entry whose author is not a bot. Bot accounts excluded from the comment count: accounts with type 'Bot', logins ending in '[bot]', and the named automation accounts azure-pipelines, bors, codecov, dotnet-bot, dotnet-issue-labeler, dotnet-maestro, dotnet-policy-service, facebook-github-bot, flutter-dashboard, fluttergithubbot, google-cla, grafanabot, homeassistant, k8s-ci-robot, k8s-triage-robot, linux-foundation-easycla, msftbot, netlify, probot-home-assistant, pytorch-bot, pytorch-probot, rust-highfive, rustbot, typescript-bot, vs-code-engineering, vscode-triage-bot, vscodenpm. Bot accounts seen in this record: none. Deterministic, no model judgement. Before answers are issued, the extraction program must pass on 2 hand-checked units of this source (spec general rule 5); hand-checking is pending for the delivery step.
27
  Tools: curl -H 'Accept: application/vnd.github+json' https://api.github.com/repos/microsoft/TypeScript/issues/43300/timeline?per_page=100 and read the JSON with jq or Python json; 'gh api repos/microsoft/TypeScript/issues/43300/timeline' reaches the same data
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** curl -H 'Accept: application/vnd.github+json' https://api.github.com/repos/microsoft/TypeScript/issues/43300/timeline?per_page=100 and read the JSON with jq or Python json; 'gh api repos/microsoft/TypeScript/issues/43300/timeline' reaches the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `repos/microsoft/TypeScript/issues/43300/timeline.json`: microsoft/TypeScript issue #43300: New Error: union narrowing.
20
  Format: GitHub REST API issue timeline JSON (GET /repos/{owner}/{repo}/issues/{number}/timeline, per_page=100; one page, fewer than 100 entries, so the record is complete): an array of timeline entries with 'event' (kinds in this unit: assigned, closed, commented, labeled, locked, mentioned, milestoned, subscribed), actor or user, created_at, assignee/assigner, label, commit and, for 'commented' entries, the comment body and author_association. This unit has no 'cross-referenced' entries (those embed live repository counters and are not byte-stable, see report).
21
  Origin: Live GitHub REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the timeline JSON was fetched twice apart and was byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
22
  Check: Exact match against values read from the pinned JSON: closed/reopened/merged entries (actor, created_at), assigned/unassigned/review_requested entries (assignee or requested_reviewer, assigner or review_requester, created_at), and comments (author login, created_at). A human comment is a 'commented' entry whose author is not a bot. Bot accounts excluded from the comment count: accounts with type 'Bot', logins ending in '[bot]', and the named automation accounts azure-pipelines, bors, codecov, dotnet-bot, dotnet-issue-labeler, dotnet-maestro, dotnet-policy-service, facebook-github-bot, flutter-dashboard, fluttergithubbot, google-cla, grafanabot, homeassistant, k8s-ci-robot, k8s-triage-robot, linux-foundation-easycla, msftbot, netlify, probot-home-assistant, pytorch-bot, pytorch-probot, rust-highfive, rustbot, typescript-bot, vs-code-engineering, vscode-triage-bot, vscodenpm. Bot accounts seen in this record: none. Deterministic, no model judgement. Before answers are issued, the extraction program must pass on 2 hand-checked units of this source (spec general rule 5); hand-checking is pending for the delivery step.
23
  Tools: curl -H 'Accept: application/vnd.github+json' https://api.github.com/repos/microsoft/TypeScript/issues/43300/timeline?per_page=100 and read the JSON with jq or Python json; 'gh api repos/microsoft/TypeScript/issues/43300/timeline' reaches the same data
campaign_files/2026-10-m-issue-trackers-2/ubuntu-devel/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the thread headers. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `m027-12/2016-March.txt.gz`: changelogs.ubuntu.com questions/issues? (5 messages, 2016-03-09 to 2016-03-11).
22
  Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure. Addresses written as 'x at y'.
23
  Origin: Real list traffic in a closed past month of the list's Pipermail archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer.
24
- Reference result: facts computed from the thread headers
25
- Reference source: Message-ID, In-Reply-To, References, From and Date headers of the messages in the thread.
26
  Check: Exact match against values computed from the pinned month file: parse it as mbox, take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC and compare sender names. People are counted by person, not address (the row's scale names the people). Deterministic. The thread-cutting program was checked against a hand reading on 2 threads of this list (spec general rule 5): on the chosen thread the header closure and the Subject lines agree message for message; on a second thread every difference was traced by hand to the In-Reply-To headers (a renamed subject inside the reply chain, or a separate root with the same subject), and the program followed the headers correctly. Questions that need the body (what was asked, what fixed it) need a model or human judge and are listed separately. Hand-check second sample: 'Knocking Python 2 off the desktop ISO' (10 messages; header closure and Subject lines agree).
27
  Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `m027-12/2016-March.txt.gz`: changelogs.ubuntu.com questions/issues? (5 messages, 2016-03-09 to 2016-03-11).
20
  Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure. Addresses written as 'x at y'.
21
  Origin: Real list traffic in a closed past month of the list's Pipermail archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer.
 
 
22
  Check: Exact match against values computed from the pinned month file: parse it as mbox, take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC and compare sender names. People are counted by person, not address (the row's scale names the people). Deterministic. The thread-cutting program was checked against a hand reading on 2 threads of this list (spec general rule 5): on the chosen thread the header closure and the Subject lines agree message for message; on a second thread every difference was traced by hand to the In-Reply-To headers (a renamed subject inside the reply chain, or a separate root with the same subject), and the program followed the headers correctly. Questions that need the body (what was asked, what fixed it) need a model or human judge and are listed separately. Hand-check second sample: 'Knocking Python 2 off the desktop ISO' (10 messages; header closure and Subject lines agree).
23
  Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
campaign_files/2026-10-m-issue-trackers-2/unibus-passenger-gtfs/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
14
 
15
  **Licence (SPDX):** OGL-UK-3.0
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/unibus/gtfs/unibus_1790244600.zip
23
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
24
  Origin: Live static GTFS feed published by Unibus (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/unibus/gtfs/unibus_1790244600.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
25
- Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
26
- Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
27
  Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
28
  Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
29
  Companions (not included): calendar_dates.txt; agency.txt
 
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
12
 
13
  **Licence (SPDX):** OGL-UK-3.0
 
20
  Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/unibus/gtfs/unibus_1790244600.zip
21
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
22
  Origin: Live static GTFS feed published by Unibus (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/unibus/gtfs/unibus_1790244600.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
 
 
23
  Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
24
  Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
25
  Companions (not included): calendar_dates.txt; agency.txt
campaign_files/2026-10-md-media-and-documents/tingerrr-subpar-tests/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Reference rendering (PNG) compared pixel by pixel. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** tt run core/ok/default (tytanic, headless Typst compile and pixel compare)
14
 
15
  **Licence (SPDX):** MIT
@@ -21,8 +19,6 @@ Files:
21
  - `tests/core/ok/default/test.typ`: Subpar Typst package test core/ok/default: sub-figure grid numbering, outline and references, with reference PNG.
22
  Format: Typst source (.typ) plus reference PNG
23
  Origin: visual regression test written by the package author (also the tytanic author); ref/1.png is the accepted rendering
24
- Reference result: reference rendering (PNG) compared pixel by pixel
25
- Reference source: tests/core/ok/default/ref/1.png, the rendering the author accepted
26
  Check: compile test.typ with tytanic 0.2.2 (Typst 0.13.1) at the default resolution and compare with ref/1.png pixel by pixel; hide ref/ when posing the task
27
  Tools: tt run core/ok/default (tytanic, headless Typst compile and pixel compare)
28
  Companions (not included): tests/core/ok/default/ref/1.png; src/default.typ; src/lib.typ; src/util.typ; typst.toml; tests/util.typ
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** tt run core/ok/default (tytanic, headless Typst compile and pixel compare)
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `tests/core/ok/default/test.typ`: Subpar Typst package test core/ok/default: sub-figure grid numbering, outline and references, with reference PNG.
20
  Format: Typst source (.typ) plus reference PNG
21
  Origin: visual regression test written by the package author (also the tytanic author); ref/1.png is the accepted rendering
 
 
22
  Check: compile test.typ with tytanic 0.2.2 (Typst 0.13.1) at the default resolution and compare with ref/1.png pixel by pixel; hide ref/ when posing the task
23
  Tools: tt run core/ok/default (tytanic, headless Typst compile and pixel compare)
24
  Companions (not included): tests/core/ok/default/ref/1.png; src/default.typ; src/lib.typ; src/util.typ; typst.toml; tests/util.typ
campaign_files/2026-10-md-media-and-documents/touying-typ-touying-tests/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Reference rendering (11 PNG pages) compared pixel by pixel. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** tt run features/footnote (tytanic, headless Typst compile and pixel compare)
14
 
15
  **Licence (SPDX):** MIT
@@ -21,8 +19,6 @@ Files:
21
  - `tests/features/footnote/test.typ`: Touying Typst slide package test features/footnote: footnotes across animated slides (simple theme), with 11 reference PNG pages.
22
  Format: Typst source (.typ) plus reference PNG pages
23
  Origin: visual regression test written by the Touying maintainers; ref/1.png to ref/11.png are the accepted renderings
24
- Reference result: reference rendering (11 PNG pages) compared pixel by pixel
25
- Reference source: tests/features/footnote/ref/1.png to ref/11.png, the renderings the maintainers accepted
26
  Check: compile test.typ with tytanic 0.4.1 at 72 ppi and compare each page with ref/N.png pixel by pixel; page count must match; hide ref/ when posing the task
27
  Tools: tt run features/footnote (tytanic, headless Typst compile and pixel compare)
28
  Companions (not included): typst.toml; tests/features/footnote/ref/1.png; tests/features/footnote/ref/2.png; tests/features/footnote/ref/3.png; tests/features/footnote/ref/4.png; tests/features/footnote/ref/5.png; tests/features/footnote/ref/6.png; tests/features/footnote/ref/7.png; tests/features/footnote/ref/8.png; tests/features/footnote/ref/9.png; tests/features/footnote/ref/10.png; tests/features/footnote/ref/11.png
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** tt run features/footnote (tytanic, headless Typst compile and pixel compare)
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `tests/features/footnote/test.typ`: Touying Typst slide package test features/footnote: footnotes across animated slides (simple theme), with 11 reference PNG pages.
20
  Format: Typst source (.typ) plus reference PNG pages
21
  Origin: visual regression test written by the Touying maintainers; ref/1.png to ref/11.png are the accepted renderings
 
 
22
  Check: compile test.typ with tytanic 0.4.1 at 72 ppi and compare each page with ref/N.png pixel by pixel; page count must match; hide ref/ when posing the task
23
  Tools: tt run features/footnote (tytanic, headless Typst compile and pixel compare)
24
  Companions (not included): typst.toml; tests/features/footnote/ref/1.png; tests/features/footnote/ref/2.png; tests/features/footnote/ref/3.png; tests/features/footnote/ref/4.png; tests/features/footnote/ref/5.png; tests/features/footnote/ref/6.png; tests/features/footnote/ref/7.png; tests/features/footnote/ref/8.png; tests/features/footnote/ref/9.png; tests/features/footnote/ref/10.png; tests/features/footnote/ref/11.png
campaign_files/2026-10-md-media-and-documents/turndown-test-index-html/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Expected Markdown for each HTML fragment. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** node -e with new TurndownService(options).turndown(html) (JavaScript library); pandoc -f html -t markdown is the comparable command line conversion
14
 
15
  **Licence (SPDX):** MIT
@@ -21,8 +19,6 @@ Files:
21
  - `test/index.html`: Turndown test page: HTML fragments converted to Markdown (147 cases).
22
  Format: HTML page (35476 bytes) of 147 div.case elements, each with a div.input HTML fragment, a pre.expected Markdown text and optional data-options JSON
23
  Origin: test page written by the turndown maintainers for their HTML to Markdown converter (headings, lists, code, links, tables of escaping rules); direction is HTML to Markdown, the reverse of most rows of this family; text is lorem ipsum and placeholder links
24
- Reference result: expected Markdown for each HTML fragment
25
- Reference source: the pre.expected text of each div.case
26
  Check: for each div.case show the agent the input HTML (and the data-options, which set heading style, bullet marker and the like); hide pre.expected; pass when the Markdown equals the expected text exactly (turndown-attendant t.equal)
27
  Tools: node -e with new TurndownService(options).turndown(html) (JavaScript library); pandoc -f html -t markdown is the comparable command line conversion
28
  Dependencies: turndown; turndown-attendant @651033cae3862b2fadea2f778ab7902ca5f3eee8 (test runner); a DOM implementation for Node
 
8
 
9
  **Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** node -e with new TurndownService(options).turndown(html) (JavaScript library); pandoc -f html -t markdown is the comparable command line conversion
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `test/index.html`: Turndown test page: HTML fragments converted to Markdown (147 cases).
20
  Format: HTML page (35476 bytes) of 147 div.case elements, each with a div.input HTML fragment, a pre.expected Markdown text and optional data-options JSON
21
  Origin: test page written by the turndown maintainers for their HTML to Markdown converter (headings, lists, code, links, tables of escaping rules); direction is HTML to Markdown, the reverse of most rows of this family; text is lorem ipsum and placeholder links
 
 
22
  Check: for each div.case show the agent the input HTML (and the data-options, which set heading style, bullet marker and the like); hide pre.expected; pass when the Markdown equals the expected text exactly (turndown-attendant t.equal)
23
  Tools: node -e with new TurndownService(options).turndown(html) (JavaScript library); pandoc -f html -t markdown is the comparable command line conversion
24
  Dependencies: turndown; turndown-attendant @651033cae3862b2fadea2f778ab7902ca5f3eee8 (test runner); a DOM implementation for Node
campaign_files/2026-10-md-media-and-documents/typsium-alchemist-tests/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Reference rendering (1 PNG page at 100 ppi) compared pixel by pixel. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** tt run molecules-ethanol (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
14
 
15
  **Licence (SPDX):** MIT
@@ -21,8 +19,6 @@ Files:
21
  - `tests/molecules-ethanol/test.typ`: Alchemist Typst package test molecules-ethanol: skeletal formula of ethanol drawn from a bond description, with a reference PNG.
22
  Format: Typst source (.typ) plus reference PNG page
23
  Origin: visual regression test written by the package author; ref/1.png is the accepted rendering stored by tytanic
24
- Reference result: reference rendering (1 PNG page at 100 ppi) compared pixel by pixel
25
- Reference source: tests/molecules-ethanol/ref/1.png, the rendering the author accepted
26
  Check: compile test.typ with tytanic 0.3.4 at 100 ppi and compare the page with ref/1.png pixel by pixel; a pixel deviates when any channel differs by more than max delta; hide ref/ when posing the task
27
  Tools: tt run molecules-ethanol (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
28
  Companions (not included): .github/workflows/run-tests.yml; typst.toml; lib.typ; LICENSE; tests/molecules-ethanol/ref/1.png; src/cetz/process.typ; src/default.typ; src/drawer.typ; src/drawer/branch.typ; src/drawer/cram.typ; src/drawer/cycle.typ; src/drawer/fragment.typ; src/drawer/hide.typ; src/drawer/hook.typ; src/drawer/link.typ; src/drawer/operator.typ; src/drawer/parenthesis.typ; src/elements/fragment.typ; src/elements/lewis.typ; src/elements/links.typ; src/utils/anchors.typ; src/utils/angles.typ; src/utils/context.typ; src/utils/utils.typ
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** tt run molecules-ethanol (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `tests/molecules-ethanol/test.typ`: Alchemist Typst package test molecules-ethanol: skeletal formula of ethanol drawn from a bond description, with a reference PNG.
20
  Format: Typst source (.typ) plus reference PNG page
21
  Origin: visual regression test written by the package author; ref/1.png is the accepted rendering stored by tytanic
 
 
22
  Check: compile test.typ with tytanic 0.3.4 at 100 ppi and compare the page with ref/1.png pixel by pixel; a pixel deviates when any channel differs by more than max delta; hide ref/ when posing the task
23
  Tools: tt run molecules-ethanol (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
24
  Companions (not included): .github/workflows/run-tests.yml; typst.toml; lib.typ; LICENSE; tests/molecules-ethanol/ref/1.png; src/cetz/process.typ; src/default.typ; src/drawer.typ; src/drawer/branch.typ; src/drawer/cram.typ; src/drawer/cycle.typ; src/drawer/fragment.typ; src/drawer/hide.typ; src/drawer/hook.typ; src/drawer/link.typ; src/drawer/operator.typ; src/drawer/parenthesis.typ; src/elements/fragment.typ; src/elements/lewis.typ; src/elements/links.typ; src/utils/anchors.typ; src/utils/angles.typ; src/utils/context.typ; src/utils/utils.typ
campaign_files/2026-10-md-media-and-documents/typst-community-glossarium-tests/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Reference rendering (1 PNG page) compared pixel by pixel. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** tt run capitalize (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
14
 
15
  **Licence (SPDX):** MIT
@@ -21,8 +19,6 @@ Files:
21
  - `tests/capitalize/test.typ`: Glossarium Typst package test capitalize: capitalised glossary references and the printed glossary, with a reference PNG.
22
  Format: Typst source (.typ) plus reference PNG page
23
  Origin: visual regression test written by the package authors; ref/1.png is the accepted rendering stored by tytanic
24
- Reference result: reference rendering (1 PNG page) compared pixel by pixel
25
- Reference source: tests/capitalize/ref/1.png, the rendering the authors accepted
26
  Check: compile test.typ with tytanic 0.2.2 and compare the page with ref/1.png pixel by pixel; a pixel deviates when any channel differs by more than max delta; hide ref/ when posing the task
27
  Tools: tt run capitalize (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
28
  Companions (not included): tests/capitalize/ref/1.png; themes/default.typ; glossarium.typ; typst.toml; LICENSE; .github/workflows/CI.yml; justfile
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** tt run capitalize (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `tests/capitalize/test.typ`: Glossarium Typst package test capitalize: capitalised glossary references and the printed glossary, with a reference PNG.
20
  Format: Typst source (.typ) plus reference PNG page
21
  Origin: visual regression test written by the package authors; ref/1.png is the accepted rendering stored by tytanic
 
 
22
  Check: compile test.typ with tytanic 0.2.2 and compare the page with ref/1.png pixel by pixel; a pixel deviates when any channel differs by more than max delta; hide ref/ when posing the task
23
  Tools: tt run capitalize (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
24
  Companions (not included): tests/capitalize/ref/1.png; themes/default.typ; glossarium.typ; typst.toml; LICENSE; .github/workflows/CI.yml; justfile
campaign_files/2026-10-md-media-and-documents/typst-tests-suite/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 3 of 3 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Reference PNG rendering per test. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** typst compile <file>.typ out.png --ppi 72 (headless CLI) or the repository test runner (cargo test --workspace --test tests, stack); typst compile <file>.typ out.png (headless CLI) or the repository test runner (cargo test --workspace --test tests, math-cases); typst compile <file>.typ out.png (headless CLI) or the repository test runner (cargo test --workspace --test tests, pad)
14
 
15
  **Licence (SPDX):** Apache-2.0
@@ -21,8 +19,6 @@ Files:
21
  - `tests/suite/layout/stack.typ`: Typst stack layout tests: 8 tests (spacing, overflow, fractional sizing, right-to-left) with 7 reference renderings.
22
  Format: Typst source (.typ) holding 8 tests separated by "--- name paged ---" headers, plus 7 PNG references in tests/ref/render/ (one per test with visual output)
23
  Origin: Typst compiler test file for the stack layout element, with reference renderings, written by the Typst developers
24
- Reference result: reference PNG rendering per test
25
- Reference source: tests/ref/render/<test name>.png for the 7 tests with visual output; issue-1918-stack-with-infinite-spacing has no PNG and is judged by its inline error annotation in stack.typ
26
  Check: split stack.typ at the "--- name ---" headers (tests/README.md describes the format); give the agent the target image (or the description) and have it write the Typst code, or give the code and hide the PNG; the error test passes when the compiler emits the annotated error
27
  Tools: typst compile <file>.typ out.png --ppi 72 (headless CLI) or the repository test runner (cargo test --workspace --test tests, stack)
28
  Companions (not included): tests/ref/render/stack-basic.png; tests/ref/render/stack-spacing.png; tests/ref/render/stack-overflow.png; tests/ref/render/stack-fr.png; tests/ref/render/stack-rtl-align-and-fr.png; tests/ref/render/issue-1240-stack-h-fr.png; tests/ref/render/issue-1240-stack-v-fr.png
@@ -30,8 +26,6 @@ Files:
30
  - `tests/suite/math/cases.typ`: Typst math cases tests: 6 tests (gap, delimiter, line breaks, delimiter class) with 6 reference renderings.
31
  Format: Typst source (.typ) holding 6 tests marked "paged html", plus 6 PNG references in tests/ref/render/
32
  Origin: Typst compiler tests for the math cases construct (piecewise definitions), with reference renderings, written by the Typst developers
33
- Reference result: reference PNG rendering per test
34
- Reference source: tests/ref/render/<test name>.png for the paged output; the HTML output of these tests is stored upstream only as a hash in the shared tests/ref/html/hashes.txt (e.g. "20f646ed1b658d2dc5dc804f73cabfa0 math-cases") and is not part of this unit
35
  Check: split at the "--- name ---" headers; the html target is left out because its reference is a hash of the exact HTML output, not a readable answer
36
  Tools: typst compile <file>.typ out.png (headless CLI) or the repository test runner (cargo test --workspace --test tests, math-cases)
37
  Companions (not included): tests/ref/render/math-cases.png; tests/ref/render/math-cases-gap.png; tests/ref/render/math-cases-delim.png; tests/ref/render/math-cases-linebreaks.png; tests/ref/render/math-cases-linebreaks-trailing.png; tests/ref/render/math-cases-delim-class.png
@@ -39,8 +33,6 @@ Files:
39
  - `tests/suite/layout/pad.typ`: Typst pad layout tests: 6 tests (padding, expanding content, 100 percent padding, unbreakable pad) with 5 reference renderings.
40
  Format: Typst source (.typ) holding 6 tests, plus 5 PNG references; pad-adding-to-100-percent is marked "paged empty" (no visual output expected)
41
  Origin: Typst compiler tests for the pad layout element, with reference renderings, written by the Typst developers
42
- Reference result: reference PNG rendering per test
43
- Reference source: tests/ref/render/<test name>.png for the 5 tests with output; the empty test passes when it produces no non-trivial output (tests/README.md line 147: "`empty`: Indicates that a test shouldn't produce any non-trivial output.")
44
  Check: split at the "--- name ---" headers.
45
  Tools: typst compile <file>.typ out.png (headless CLI) or the repository test runner (cargo test --workspace --test tests, pad)
46
  Companions (not included): tests/ref/render/pad-basic.png; tests/ref/render/pad-expanding-contents.png; tests/ref/render/pad-followed-by-content.png; tests/ref/render/issue-5044-pad-100-percent.png; tests/ref/render/issue-5160-unbreakable-pad.png
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 3 of 3 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** typst compile <file>.typ out.png --ppi 72 (headless CLI) or the repository test runner (cargo test --workspace --test tests, stack); typst compile <file>.typ out.png (headless CLI) or the repository test runner (cargo test --workspace --test tests, math-cases); typst compile <file>.typ out.png (headless CLI) or the repository test runner (cargo test --workspace --test tests, pad)
12
 
13
  **Licence (SPDX):** Apache-2.0
 
19
  - `tests/suite/layout/stack.typ`: Typst stack layout tests: 8 tests (spacing, overflow, fractional sizing, right-to-left) with 7 reference renderings.
20
  Format: Typst source (.typ) holding 8 tests separated by "--- name paged ---" headers, plus 7 PNG references in tests/ref/render/ (one per test with visual output)
21
  Origin: Typst compiler test file for the stack layout element, with reference renderings, written by the Typst developers
 
 
22
  Check: split stack.typ at the "--- name ---" headers (tests/README.md describes the format); give the agent the target image (or the description) and have it write the Typst code, or give the code and hide the PNG; the error test passes when the compiler emits the annotated error
23
  Tools: typst compile <file>.typ out.png --ppi 72 (headless CLI) or the repository test runner (cargo test --workspace --test tests, stack)
24
  Companions (not included): tests/ref/render/stack-basic.png; tests/ref/render/stack-spacing.png; tests/ref/render/stack-overflow.png; tests/ref/render/stack-fr.png; tests/ref/render/stack-rtl-align-and-fr.png; tests/ref/render/issue-1240-stack-h-fr.png; tests/ref/render/issue-1240-stack-v-fr.png
 
26
  - `tests/suite/math/cases.typ`: Typst math cases tests: 6 tests (gap, delimiter, line breaks, delimiter class) with 6 reference renderings.
27
  Format: Typst source (.typ) holding 6 tests marked "paged html", plus 6 PNG references in tests/ref/render/
28
  Origin: Typst compiler tests for the math cases construct (piecewise definitions), with reference renderings, written by the Typst developers
 
 
29
  Check: split at the "--- name ---" headers; the html target is left out because its reference is a hash of the exact HTML output, not a readable answer
30
  Tools: typst compile <file>.typ out.png (headless CLI) or the repository test runner (cargo test --workspace --test tests, math-cases)
31
  Companions (not included): tests/ref/render/math-cases.png; tests/ref/render/math-cases-gap.png; tests/ref/render/math-cases-delim.png; tests/ref/render/math-cases-linebreaks.png; tests/ref/render/math-cases-linebreaks-trailing.png; tests/ref/render/math-cases-delim-class.png
 
33
  - `tests/suite/layout/pad.typ`: Typst pad layout tests: 6 tests (padding, expanding content, 100 percent padding, unbreakable pad) with 5 reference renderings.
34
  Format: Typst source (.typ) holding 6 tests, plus 5 PNG references; pad-adding-to-100-percent is marked "paged empty" (no visual output expected)
35
  Origin: Typst compiler tests for the pad layout element, with reference renderings, written by the Typst developers
 
 
36
  Check: split at the "--- name ---" headers.
37
  Tools: typst compile <file>.typ out.png (headless CLI) or the repository test runner (cargo test --workspace --test tests, pad)
38
  Companions (not included): tests/ref/render/pad-basic.png; tests/ref/render/pad-expanding-contents.png; tests/ref/render/pad-followed-by-content.png; tests/ref/render/issue-5044-pad-100-percent.png; tests/ref/render/issue-5160-unbreakable-pad.png
campaign_files/2026-10-md-media-and-documents/u-fischer-newpax-testfiles/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Expected normalised PDF (.tpf), one per engine. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** l3build check newpax-link-parens (headless LaTeX run; the produced PDF is normalised and compared with the .tpf)
14
 
15
  **Licence (SPDX):** LPPL-1.3c
@@ -21,8 +19,6 @@ Files:
21
  - `testfiles/newpax-link-parens.pvt`: Newpax PDF test link-parens: link annotations of an included PDF page whose URIs contain parentheses are carried into the new PDF.
22
  Format: LaTeX PDF test file (.pvt) plus expected normalised PDFs (.tpf) and a support PDF
23
  Origin: regression test of the package author; the .tpf files are the accepted normalised PDFs per engine
24
- Reference result: expected normalised PDF (.tpf), one per engine
25
- Reference source: testfiles/newpax-link-parens.tpf (LuaTeX, the standard engine), .pdftex.tpf and .xetex.tpf, saved by the author from checked runs
26
  Check: put the support PDF and its .newpax file next to the test, run the .pvt with l3build on each engine; l3build normalises the produced PDF and the check passes when it equals the matching .tpf; hide the .tpf files when posing the task
27
  Tools: l3build check newpax-link-parens (headless LaTeX run; the produced PDF is normalised and compared with the .tpf)
28
  Companions (not included): testfiles/support/test-link-parens.pdf; testfiles/support/test-link-parens.newpax; build.lua; Readme.md
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** l3build check newpax-link-parens (headless LaTeX run; the produced PDF is normalised and compared with the .tpf)
12
 
13
  **Licence (SPDX):** LPPL-1.3c
 
19
  - `testfiles/newpax-link-parens.pvt`: Newpax PDF test link-parens: link annotations of an included PDF page whose URIs contain parentheses are carried into the new PDF.
20
  Format: LaTeX PDF test file (.pvt) plus expected normalised PDFs (.tpf) and a support PDF
21
  Origin: regression test of the package author; the .tpf files are the accepted normalised PDFs per engine
 
 
22
  Check: put the support PDF and its .newpax file next to the test, run the .pvt with l3build on each engine; l3build normalises the produced PDF and the check passes when it equals the matching .tpf; hide the .tpf files when posing the task
23
  Tools: l3build check newpax-link-parens (headless LaTeX run; the produced PDF is normalised and compared with the .tpf)
24
  Companions (not included): testfiles/support/test-link-parens.pdf; testfiles/support/test-link-parens.newpax; build.lua; Readme.md
campaign_files/2026-10-md-media-and-documents/u-fischer-tagpdf-testfiles/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Expected normalised log of the tagging structure per engine. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** l3build check mc-parent-child (pdftex, luatex, pdftexmain configs) in the repository root
14
 
15
  **Licence (SPDX):** LPPL-1.3c+
@@ -21,8 +19,6 @@ Files:
21
  - `testfiles/mc-parent-child.lvt`: Tagpdf regression test mc-parent-child: tagged PDF structure for paragraph tag roles, log per engine.
22
  Format: LaTeX source (.lvt) plus expected logs (.tlg)
23
  Origin: l3build regression test of the tagpdf package (accessible tagged PDF from LaTeX), written by its author
24
- Reference result: expected normalised log of the tagging structure per engine
25
- Reference source: testfiles/mc-parent-child.tlg, .luatex.tlg and .pdftexmain.tlg, written by the author
26
  Check: run the .lvt with l3build on each engine and compare its normalised .log with the matching .tlg line by line; hide the .tlg files when posing the task
27
  Tools: l3build check mc-parent-child (pdftex, luatex, pdftexmain configs) in the repository root
28
  Companions (not included): testfiles/mc-parent-child.tlg; testfiles/mc-parent-child.luatex.tlg; testfiles/mc-parent-child.pdftexmain.tlg; build.lua
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** l3build check mc-parent-child (pdftex, luatex, pdftexmain configs) in the repository root
12
 
13
  **Licence (SPDX):** LPPL-1.3c+
 
19
  - `testfiles/mc-parent-child.lvt`: Tagpdf regression test mc-parent-child: tagged PDF structure for paragraph tag roles, log per engine.
20
  Format: LaTeX source (.lvt) plus expected logs (.tlg)
21
  Origin: l3build regression test of the tagpdf package (accessible tagged PDF from LaTeX), written by its author
 
 
22
  Check: run the .lvt with l3build on each engine and compare its normalised .log with the matching .tlg line by line; hide the .tlg files when posing the task
23
  Tools: l3build check mc-parent-child (pdftex, luatex, pdftexmain configs) in the repository root
24
  Companions (not included): testfiles/mc-parent-child.tlg; testfiles/mc-parent-child.luatex.tlg; testfiles/mc-parent-child.pdftexmain.tlg; build.lua
campaign_files/2026-10-md-media-and-documents/uci-bach-choral-harmony/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: chord_label_column. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Hide the label column (attribute 17); the agent labels each event; exact-match accuracy of the label string per event and per chorale, no enharmonic or spelling normalisation (the .names file gives none).
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `md033-10/bach+choral+harmony.zip`: Chord labelling of Bach chorale events: name the chord (101 labels) from pitch-class sets, bass and meter.
22
  Format: zip 42,978 bytes holding jsbach_chorals_harmony.data (393,200 bytes, CSV, 5,665 events from 60 chorales: chorale id, event no., 12 pitch-class YES/NO flags, bass pitch class, meter 1 to 5, chord label) and .names (5,109 bytes)
23
  Origin: hand chord labels on events extracted from public-domain chorales
24
- Reference result: chord_label_column
25
- Reference source: last column, chord labels annotated by hand by the dataset authors (101 distinct labels)
26
  Check: hide the label column (attribute 17); the agent labels each event; exact-match accuracy of the label string per event and per chorale, no enharmonic or spelling normalisation (the .names file gives none)
27
  Companions (not included): jsbach_chorals_harmony.names (attribute description, inside the zip)
 
8
 
9
  **Self-contained:** The file is self-contained. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Hide the label column (attribute 17); the agent labels each event; exact-match accuracy of the label string per event and per chorale, no enharmonic or spelling normalisation (the .names file gives none).
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `md033-10/bach+choral+harmony.zip`: Chord labelling of Bach chorale events: name the chord (101 labels) from pitch-class sets, bass and meter.
20
  Format: zip 42,978 bytes holding jsbach_chorals_harmony.data (393,200 bytes, CSV, 5,665 events from 60 chorales: chorale id, event no., 12 pitch-class YES/NO flags, bass pitch class, meter 1 to 5, chord label) and .names (5,109 bytes)
21
  Origin: hand chord labels on events extracted from public-domain chorales
 
 
22
  Check: hide the label column (attribute 17); the agent labels each event; exact-match accuracy of the label string per event and per chorale, no enharmonic or spelling normalisation (the .names file gives none)
23
  Companions (not included): jsbach_chorals_harmony.names (attribute description, inside the zip)
campaign_files/2026-10-md-media-and-documents/ummels-ccicons-testfiles/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: Expected normalised TeX log (.tlg) with box dumps. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** l3build check icons (headless LaTeX run, log normalised and diffed against the .tlg)
14
 
15
  **Licence (SPDX):** LPPL-1.3c+
@@ -21,8 +19,6 @@ Files:
21
  - `testfiles/icons.lvt`: Ccicons l3build test icons: every Creative Commons icon command typeset between two digits, checked through the box log.
22
  Format: LaTeX test file (.lvt) plus expected log (.tlg)
23
  Origin: regression test of the package author; the .tlg is the accepted normalised log with \showbox dumps of each icon
24
- Reference result: expected normalised TeX log (.tlg) with box dumps
25
- Reference source: testfiles/icons.tlg, saved by the author from checked runs (one file for both engines)
26
  Check: run the .lvt with l3build on pdfTeX and LuaTeX and compare the normalised .log with the .tlg line by line; hide the .tlg when posing the task
27
  Tools: l3build check icons (headless LaTeX run, log normalised and diffed against the .tlg)
28
  Companions (not included): testfiles/icons.tlg; testfiles/support/regression-test.cfg; build.lua; README.md
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** l3build check icons (headless LaTeX run, log normalised and diffed against the .tlg)
12
 
13
  **Licence (SPDX):** LPPL-1.3c+
 
19
  - `testfiles/icons.lvt`: Ccicons l3build test icons: every Creative Commons icon command typeset between two digits, checked through the box log.
20
  Format: LaTeX test file (.lvt) plus expected log (.tlg)
21
  Origin: regression test of the package author; the .tlg is the accepted normalised log with \showbox dumps of each icon
 
 
22
  Check: run the .lvt with l3build on pdfTeX and LuaTeX and compare the normalised .log with the .tlg line by line; hide the .tlg when posing the task
23
  Tools: l3build check icons (headless LaTeX run, log normalised and diffed against the .tlg)
24
  Companions (not included): testfiles/icons.tlg; testfiles/support/regression-test.cfg; build.lua; README.md
campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-modify-header-scenario/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_test_assertions. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
14
 
15
  **Licence (SPDX):** GPL-3.0-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `modules/purchase/tests/scenario_purchase_modify_header.rst`: Tryton purchase modify header scenario: totals recomputed after changing the supplier and its taxes.
22
  Format: reStructuredText doctest scenario (proteus), 54 doctest prompts with expected outputs
23
  Origin: scenario test written by the module authors; parties, products and prices are made up
24
- Reference result: expected_test_assertions
25
- Reference source: modules/purchase/tests/scenario_purchase_modify_header.rst: printed outputs at lines 80 and 92 and the states around them
26
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
27
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
28
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
12
 
13
  **Licence (SPDX):** GPL-3.0-or-later
 
19
  - `modules/purchase/tests/scenario_purchase_modify_header.rst`: Tryton purchase modify header scenario: totals recomputed after changing the supplier and its taxes.
20
  Format: reStructuredText doctest scenario (proteus), 54 doctest prompts with expected outputs
21
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
22
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
23
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
24
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-request-quotation-scenario/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_test_assertions. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
14
 
15
  **Licence (SPDX):** GPL-3.0-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `modules/purchase_request_quotation/tests/scenario_purchase_request_quotation.rst`: Tryton purchase request quotation scenario: supplier quotations and choice of the supplier for the purchase.
22
  Format: reStructuredText doctest scenario (proteus), 109 doctest prompts with expected outputs
23
  Origin: scenario test written by the module authors; parties, products and prices are made up
24
- Reference result: expected_test_assertions
25
- Reference source: modules/purchase_request_quotation/tests/scenario_purchase_request_quotation.rst: printed outputs (states, chosen supplier, unit prices) at lines 168 to 198
26
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
27
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
28
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
12
 
13
  **Licence (SPDX):** GPL-3.0-or-later
 
19
  - `modules/purchase_request_quotation/tests/scenario_purchase_request_quotation.rst`: Tryton purchase request quotation scenario: supplier quotations and choice of the supplier for the purchase.
20
  Format: reStructuredText doctest scenario (proteus), 109 doctest prompts with expected outputs
21
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
22
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
23
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
24
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-requisition-scenario/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_test_assertions. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
14
 
15
  **Licence (SPDX):** GPL-3.0-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `modules/purchase_requisition/tests/scenario_purchase_requisition.rst`: Tryton purchase requisition scenario: internal requisition, approval, purchase requests and purchase.
22
  Format: reStructuredText doctest scenario (proteus), 172 doctest prompts with expected outputs
23
  Origin: scenario test written by the module authors; parties, products and prices are made up
24
- Reference result: expected_test_assertions
25
- Reference source: modules/purchase_requisition/tests/scenario_purchase_requisition.rst: printed outputs after each >>> prompt (states, total_amount, request quantities, unit prices), e.g. lines 126 to 127 and 184 to 185
26
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
27
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
28
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
12
 
13
  **Licence (SPDX):** GPL-3.0-or-later
 
19
  - `modules/purchase_requisition/tests/scenario_purchase_requisition.rst`: Tryton purchase requisition scenario: internal requisition, approval, purchase requests and purchase.
20
  Format: reStructuredText doctest scenario (proteus), 172 doctest prompts with expected outputs
21
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
22
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
23
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
24
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-scenarios/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_doctest_outputs. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
14
 
15
  **Licence (SPDX):** GPL-3.0-or-later
@@ -21,56 +19,42 @@ Files:
21
  - `modules/purchase/tests/scenario_purchase.rst`: Tryton purchase scenario: quote, confirm, receive, return and invoice purchase orders with tax, checking amounts and order, shipment and invoice states.
22
  Format: reStructuredText doctest scenario (proteus), 393 doctest prompts with expected outputs
23
  Origin: scenario test written by the module authors; parties, products and prices are made up
24
- Reference result: expected_doctest_outputs
25
- Reference source: expected outputs printed under each >>> prompt, e.g. untaxed, tax and total (25.00, 2.50, 27.50) at lines 164, 168 and 181 (3 at 5.0000 plus 2 at 5.0000 with 10% tax), state processing at line 171, shipment_state waiting at line 173, invoice_state pending at line 175
26
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
27
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
28
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
29
  - `modules/purchase/tests/scenario_purchase_manual_invoice.rst`: Tryton purchase with manual invoice method: quantity to invoice before and after a manual invoice, then a second invoice after the invoiced quantity is cut to 5.
30
  Format: reStructuredText doctest scenario (proteus), about 64 doctest prompts
31
  Origin: scenario test written by the module authors; parties, products and prices are made up
32
- Reference result: expected_doctest_outputs
33
- Reference source: invoice_state none at line 78, quantity_to_invoice 10.0 at line 85 and 0.0 at line 98 after manual_invoice, invoice line quantity set to 5 at line 105, two invoices at line 117
34
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
35
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
36
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
37
  - `modules/account_invoice_stock/tests/scenario_account_invoice_stock_correction.rst`: Tryton supplier invoice price correction linked to a receipt move: received 10 at 40, correction line of -10 updates the stock move unit price.
38
  Format: reStructuredText doctest scenario (proteus), about 76 doctest prompts
39
  Origin: scenario test written by the module authors; parties, products and prices are made up
40
- Reference result: expected_doctest_outputs
41
- Reference source: move unit_price 40.0000 after the invoice (before the correction), 39.0000 at line 130 after a correction line of quantity 1 at -10.0000 (line 119)
42
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
43
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
44
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
45
  - `modules/purchase_amendment/tests/scenario_purchase_amendment.rst`: Tryton purchase amendment: amend quantities and prices of a confirmed purchase order and check the new total.
46
  Format: reStructuredText doctest scenario (proteus), 4490 bytes, one scenario
47
  Origin: scenario test written by the module authors; parties, products and prices are made up
48
- Reference result: expected_doctest_outputs
49
- Reference source: total_amount 55.00 at line 84 before the amendment and 46.00 at line 138 after it
50
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
51
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
52
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
53
  - `modules/purchase_product_quantity/tests/scenario_purchase_product_quantity.rst`: Tryton purchase requests under a supplier minimal quantity (0.1 kg) and rounding (0.05 kg): the purchased quantity in grams is raised and rounded.
54
  Format: reStructuredText doctest scenario (proteus), 3681 bytes, one scenario
55
  Origin: scenario test written by the module authors; parties, products and prices are made up
56
- Reference result: expected_doctest_outputs
57
- Reference source: quantity_minimal 0.1 and quantity_rounding 0.05 set at lines 58-59; a request of 30 g gives 100.0 at line 93, a request of 1001 g gives 1050.0 at line 119
58
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
59
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
60
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
61
  - `modules/purchase_shipment_cost/tests/scenario_purchase_shipment_cost.rst`: Tryton landed cost: carrier cost of 3 allocated to received moves by value, or equally per line when values are zero, changing move unit prices.
62
  Format: reStructuredText doctest scenario (proteus), 4444 bytes, one scenario
63
  Origin: scenario test written by the module authors; parties, products and prices are made up
64
- Reference result: expected_doctest_outputs
65
- Reference source: carrier cost 3 at line 45; 50 units at 8 give unit price 8.0600 at line 86; moves of 1, 3 and 5 units at 8 give [8.3334, 8.3333, 8.3333] at line 108; zero-value moves of 75 and 25 give (0.0200, 0.0600) at line 135
66
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
67
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
68
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
69
  - `modules/purchase_blanket_agreement/tests/scenario_purchase_blanket_agreement.rst`: Tryton purchase blanket agreement: call-off purchases against an agreed quantity of 20 at 7.0000, remaining quantity, and the warning when a call-off goes over it.
70
  Format: reStructuredText doctest scenario (proteus), 5434 bytes, one scenario
71
  Origin: scenario test written by the module authors; parties, products and prices are made up
72
- Reference result: expected_doctest_outputs
73
- Reference source: agreement line 20 at 7.0000 (lines 87, 89); remaining_quantity 20.0 at line 116 and 15.0 at line 127 after a call-off; purchase line quantity 15.0 and price 7.0000 at lines 158 and 160; quantity 20 at line 161 goes over the remainder
74
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
75
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
76
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
 
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
12
 
13
  **Licence (SPDX):** GPL-3.0-or-later
 
19
  - `modules/purchase/tests/scenario_purchase.rst`: Tryton purchase scenario: quote, confirm, receive, return and invoice purchase orders with tax, checking amounts and order, shipment and invoice states.
20
  Format: reStructuredText doctest scenario (proteus), 393 doctest prompts with expected outputs
21
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
22
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
23
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
24
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
25
  - `modules/purchase/tests/scenario_purchase_manual_invoice.rst`: Tryton purchase with manual invoice method: quantity to invoice before and after a manual invoice, then a second invoice after the invoiced quantity is cut to 5.
26
  Format: reStructuredText doctest scenario (proteus), about 64 doctest prompts
27
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
28
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
29
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
30
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
31
  - `modules/account_invoice_stock/tests/scenario_account_invoice_stock_correction.rst`: Tryton supplier invoice price correction linked to a receipt move: received 10 at 40, correction line of -10 updates the stock move unit price.
32
  Format: reStructuredText doctest scenario (proteus), about 76 doctest prompts
33
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
34
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
35
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
36
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
37
  - `modules/purchase_amendment/tests/scenario_purchase_amendment.rst`: Tryton purchase amendment: amend quantities and prices of a confirmed purchase order and check the new total.
38
  Format: reStructuredText doctest scenario (proteus), 4490 bytes, one scenario
39
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
40
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
41
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
42
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
43
  - `modules/purchase_product_quantity/tests/scenario_purchase_product_quantity.rst`: Tryton purchase requests under a supplier minimal quantity (0.1 kg) and rounding (0.05 kg): the purchased quantity in grams is raised and rounded.
44
  Format: reStructuredText doctest scenario (proteus), 3681 bytes, one scenario
45
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
46
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
47
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
48
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
49
  - `modules/purchase_shipment_cost/tests/scenario_purchase_shipment_cost.rst`: Tryton landed cost: carrier cost of 3 allocated to received moves by value, or equally per line when values are zero, changing move unit prices.
50
  Format: reStructuredText doctest scenario (proteus), 4444 bytes, one scenario
51
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
52
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
53
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
54
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
55
  - `modules/purchase_blanket_agreement/tests/scenario_purchase_blanket_agreement.rst`: Tryton purchase blanket agreement: call-off purchases against an agreed quantity of 20 at 7.0000, remaining quantity, and the warning when a call-off goes over it.
56
  Format: reStructuredText doctest scenario (proteus), 5434 bytes, one scenario
57
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
58
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
59
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
60
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
campaign_files/2026-10-op-rule-calculations-2/tryton-purchase-secondary-unit-scenario/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_test_assertions. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
14
 
15
  **Licence (SPDX):** GPL-3.0-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `modules/purchase_secondary_unit/tests/scenario_purchase_secondary_unit.rst`: Tryton purchase secondary unit scenario: ordering in a supplier unit and converting quantity and unit price.
22
  Format: reStructuredText doctest scenario (proteus), 92 doctest prompts with expected outputs
23
  Origin: scenario test written by the module authors; parties, products and prices are made up
24
- Reference result: expected_test_assertions
25
- Reference source: modules/purchase_secondary_unit/tests/scenario_purchase_secondary_unit.rst: printed outputs on secondary_quantity, secondary_unit_price, unit_price and quantity at lines 88 to 135
26
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
27
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
28
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
 
8
 
9
  **Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
12
 
13
  **Licence (SPDX):** GPL-3.0-or-later
 
19
  - `modules/purchase_secondary_unit/tests/scenario_purchase_secondary_unit.rst`: Tryton purchase secondary unit scenario: ordering in a supplier unit and converting quantity and unit price.
20
  Format: reStructuredText doctest scenario (proteus), 92 doctest prompts with expected outputs
21
  Origin: scenario test written by the module authors; parties, products and prices are made up
 
 
22
  Check: hide the expected outputs (or give only the business setup and ask for the end states and amounts); compare the agent's values, or the state of the agent's Tryton database after it performs the steps, with the printed outputs exactly; reference run is the doctest on pinned trytond
23
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
24
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
campaign_files/2026-10-op-rule-calculations-2/tryton-stock-scenarios/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 2 of 14 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_doctest_outputs. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
14
 
15
  **Licence (SPDX):** GPL-3.0-or-later
@@ -21,80 +19,60 @@ Files:
21
  - `modules/stock/tests/scenario_stock_average_cost_price.rst`: Tryton stock scenario: average cost price of a product through receipts at different prices, cost revaluation and negative stock.
22
  Format: reStructuredText doctest scenario (proteus), 162 doctest prompts with expected outputs
23
  Origin: scenario test written by the module authors; products, quantities and prices are made up
24
- Reference result: expected_doctest_outputs
25
- Reference source: expected outputs printed under each >>> prompt: product cost price 100.0000 (line 92), 150.0000 (line 112), 175.0000 (line 149), 140.0000 (line 158), 154.0000 (line 169); negative-stock steps 5.0000 (lines 188, 207), 3.0000 (line 227), 2.0000 (lines 247, 254)
26
  Check: hide the expected outputs (or give the receipts, deliveries and revaluations as records and ask for the cost price after each step); compare with the printed values exactly at 4 decimals; reference run is the doctest on pinned trytond
27
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
28
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
29
  - `modules/product_cost_fifo/tests/scenario_product_cost_fifo.rst`: Tryton FIFO cost scenario: product cost price and outgoing move cost prices under first-in first-out costing.
30
  Format: reStructuredText doctest scenario (proteus), 102 doctest prompts with expected outputs
31
  Origin: scenario test written by the module authors; products, quantities and prices are made up
32
- Reference result: expected_doctest_outputs
33
- Reference source: expected outputs: after 4 at 10 and 2 at 25 the cost price is 15.0000 (line 97); selling 3 gives product cost 20.0000 and move cost 10 (lines 117, 119); selling 1 then 1 gives product 25 and move costs [10, 25] (lines 158, 160)
34
  Check: hide the expected outputs (or give the incoming and outgoing moves and ask for the FIFO cost of each outgoing move and the product cost price); compare exactly at 4 decimals; reference run is the doctest on pinned trytond
35
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
36
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
37
  - `modules/stock/tests/scenario_stock_inventory.rst`: Tryton physical inventory scenario: expected quantities, counted quantities and the adjustment moves an inventory posts.
38
  Format: reStructuredText doctest scenario (proteus), 178 doctest prompts with expected outputs
39
  Origin: scenario test written by the module authors; products, quantities and prices are made up
40
- Reference result: expected_doctest_outputs
41
- Reference source: expected outputs: expected quantity 1.0 (line 113) and 2.5 (line 117) before, 2.0 (line 152) and 3.8 (line 157) after receipts of 1 and 1.3; adjustment move quantity 1.0 at line 169 (counted 3 against expected 2)
42
  Check: hide the expected outputs (or give the stock moves and the counts and ask for the expected quantities and the adjustment moves); compare exactly; reference run is the doctest on pinned trytond
43
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
44
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
45
  - `modules/stock_supply/tests/scenario_stock_supply_purchase_request.rst`: Tryton stock supply scenario: purchase requests generated from shortages and order points (minimum and target quantities).
46
  Format: reStructuredText doctest scenario (proteus), 102 doctest prompts with expected outputs
47
  Origin: scenario test written by the module authors; products, quantities and prices are made up
48
- Reference result: expected_doctest_outputs
49
- Reference source: expected outputs: two customer shipments of 1 with no stock give a request of 2.0 (line 120); an order point with minimum 5 and target 10 gives 12.0 (line 155, 10 minus a forecast of -2); minimum -2 gives no request (line 141); minimum 0 gives 12.0 (line 169)
50
  Check: hide the expected outputs (or give stock, open shipments and order points and ask for the purchase request quantities); compare exactly; reference run is the doctest on pinned trytond
51
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
52
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
53
  - `modules/stock/tests/scenario_stock_shipment_out.rst`: Tryton customer shipment scenario: assignment of outgoing moves against available stock, partial assignment and packing.
54
  Format: reStructuredText doctest scenario (proteus), 175 doctest prompts with expected outputs
55
  Origin: scenario test written by the module authors; products, quantities and prices are made up
56
- Reference result: expected_doctest_outputs
57
- Reference source: expected outputs: with 1 unit in stock and two lines of 1 the move states are ['assigned', 'draft'] (line 141); after packing the inventory move quantities are [0.0, 1.0] (line 156)
58
  Check: hide the expected outputs (or give stock and shipment lines and ask which lines can be reserved and what is packed); compare exactly; reference run is the doctest on pinned trytond
59
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
60
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
61
  - `modules/stock/tests/scenario_stock_product_quantities_by_warehouse.rst`: Tryton product quantities by warehouse scenario: stock per day from done and planned moves, and the cumulative balance per move.
62
  Format: reStructuredText doctest scenario (proteus), 75 doctest prompts with expected outputs
63
  Origin: scenario test written by the module authors; products, quantities and prices are made up
64
- Reference result: expected_doctest_outputs
65
- Reference source: expected outputs: quantities per day [(yesterday, 10), (today, 10), (tomorrow, 6)] (line 107); per-move cumulative rows (yesterday, 0, 10, 10), (tomorrow, 10, -6, 4), (tomorrow, 4, 5, 9), (tomorrow, 9, -3, 6) (lines 123-126)
66
  Check: hide the expected outputs (or give the done and planned moves and ask for stock per day and the running balance per move); compare exactly; reference run is the doctest on pinned trytond
67
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
68
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
69
  - `modules/stock/tests/scenario_stock_recompute_average_cost_price.rst`: Tryton scenario: recompute the average cost price of stock moves after back-dated moves and price changes.
70
  Format: reStructuredText doctest (proteus)
71
  Origin: test written by the project authors; products, quantities and prices are made up
72
- Reference result: expected_doctest_outputs
73
- Reference source: doctest outputs: move cost prices [105, 120, 100, 100] (lines 94-95), product cost 105.0000 (lines 98-99), after recompute [105, 120, 120, 100] (lines 106-107), later [107.5, 130, 130, 100] (line 154) and [105, 120, 120, 100] (line 175)
74
  Check: give the dated moves and prices of the scenario and ask the average cost price of each move after recomputation; compare at the 4 decimals of the doctest output
75
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
76
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
77
  - `modules/stock/tests/scenario_stock_reporting_margin.rst`: Tryton scenario: stock margin reporting per product and category (quantity, cost, revenue, profit, margin).
78
  Format: reStructuredText doctest (proteus)
79
  Origin: test written by the project authors; products, quantities and prices are made up
80
- Reference result: expected_doctest_outputs
81
- Reference source: doctest outputs: product row (5.0, 100.00, 170.00, 70.00, 0.4118) (lines 150-151), time series (lines 160-165), Root category (140, 270, 130, 0.4815) (line 205)
82
  Check: give the moves with cost and sale prices and ask quantity, cost, revenue, profit and margin per product or category; compare money at 2 decimals and margin at the 4 decimals the doctest prints
83
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
84
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
85
  - `modules/stock/tests/scenario_stock_inventory_tolerance.rst`: Tryton scenario: inventory count over quantity and cost tolerance raises a warning.
86
  Format: reStructuredText doctest (proteus)
87
  Origin: test written by the project authors; products, quantities and prices are made up
88
- Reference result: expected_doctest_outputs
89
- Reference source: doctest outputs: expected 1.0, counted 2, variation 1.0, quantity tolerance variation 10.0, cost variation 100.0000 (lines 108-116); expected 2.5, counted 5, cost variation 175.0000, cost tolerance variation 0.8750 (lines 119-125); confirming raises InventoryOverToleranceWarning
90
  Check: give expected and counted quantities with cost prices and the two tolerances and ask the variations and whether confirming the inventory is over tolerance; compare the variations at the decimals printed and the over-tolerance verdict exactly
91
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
92
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
93
  - `modules/stock/tests/scenario_stock_reporting_inventory.rst`: Tryton scenario: inventory reporting by date (stock on a date, per-move and per-day balances) and inventory turnover.
94
  Format: reStructuredText doctest (proteus) with a JSON parameter file for 4 runs (period_close and product_type)
95
  Origin: test written by the project authors; products, quantities and prices are made up
96
- Reference result: expected_doctest_outputs
97
- Reference source: doctest outputs: quantity 9.0 (lines 156-157), 7.0 (line 166), 4.0 (line 174), move and day balance lists (lines 182-190), turnover output_quantity 0.25, average_quantity 5.5, turnover 0.045 (lines 240-245)
98
  Check: give the dated moves of the scenario and ask the stock on a date, the running balance per move and per day, and the turnover over a date range; compare quantities exactly and turnover at the decimals printed
99
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
100
  Companions (not included): modules/stock/tests/scenario_stock_reporting_inventory.json
@@ -102,24 +80,18 @@ Files:
102
  - `modules/stock/tests/scenario_stock_inventory_count.rst`: Tryton scenario: counting stock with the count wizard, adding counted quantities to inventory lines.
103
  Format: reStructuredText doctest (proteus)
104
  Origin: test written by the project authors; products, quantities and prices are made up
105
- Reference result: expected_doctest_outputs
106
- Reference source: doctest outputs: running total quantities 1.0 then 2.0 for the unit product (lines 76-84), 10.0 for the kilogram product (line 96), 2 inventory lines (line 104), line quantities 2.0 and 10.0 (lines 106-111)
107
  Check: give the count actions and ask the resulting inventory line quantities; compare exactly
108
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
109
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
110
  - `modules/stock/tests/scenario_stock_recompute_average_cost_price_production.rst`: Tryton scenario: recompute the average cost price when production consumption and returns move stock.
111
  Format: reStructuredText doctest (proteus), 114 lines
112
  Origin: test written by the project authors; products, quantities and prices are made up
113
- Reference result: expected_doctest_outputs
114
- Reference source: doctest outputs: move cost prices [40, 40] before recompute (line 79), [0, 0] after (line 87), product cost 0.0000 (line 91), then [20, 20, 20] (line 110) and 20.0000 (line 114)
115
  Check: give the dated moves (production consumption, return, later receipt) with unit prices and ask the cost price of each move and of the product after recomputation; compare at the 4 decimals of the doctest output
116
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
117
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
118
  - `modules/stock_supply/tests/scenario_stock_internal_supply.rst`: Tryton scenario: internal supply from order points (min and target quantity) and negative stock in a provisioned location.
119
  Format: reStructuredText doctest (proteus), 156 lines, run twice by its companion JSON (with and without warehouses)
120
  Origin: test written by the project authors; products, quantities and prices are made up
121
- Reference result: expected_doctest_outputs
122
- Reference source: doctest outputs: internal shipment move quantity 15.0 (line 100) and 10.0 (line 139)
123
  Check: give the order point (minimum, target), the stock in each location and the provisioning links and ask the quantity of the internal shipment the supply wizard creates; compare exactly at the printed one decimal
124
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
125
  Companions (not included): modules/stock_supply/tests/scenario_stock_internal_supply.json
@@ -127,8 +99,6 @@ Files:
127
  - `modules/stock_quantity_issue/tests/scenario_stock_quantity_issue.rst`: Tryton scenario: forecast stock quantity issues from planned moves, with their priority and resolution.
128
  Format: reStructuredText doctest (proteus), 148 lines
129
  Origin: test written by the project authors; products, quantities and prices are made up
130
- Reference result: expected_doctest_outputs
131
- Reference source: doctest outputs: 2 issues (line 110), priority 7 each (lines 115, 117), quantity and forecast (0.0, -6.0) (line 121), then (0.0, 0.0) (line 140) and 0 issues after regeneration (line 148)
132
  Check: give the dated planned moves in and out and ask how many shortfall issues arise, their priority, and the quantity and forecast quantity on a given date; compare exactly
133
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
134
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
 
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 2 of 14 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
12
 
13
  **Licence (SPDX):** GPL-3.0-or-later
 
19
  - `modules/stock/tests/scenario_stock_average_cost_price.rst`: Tryton stock scenario: average cost price of a product through receipts at different prices, cost revaluation and negative stock.
20
  Format: reStructuredText doctest scenario (proteus), 162 doctest prompts with expected outputs
21
  Origin: scenario test written by the module authors; products, quantities and prices are made up
 
 
22
  Check: hide the expected outputs (or give the receipts, deliveries and revaluations as records and ask for the cost price after each step); compare with the printed values exactly at 4 decimals; reference run is the doctest on pinned trytond
23
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
24
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
25
  - `modules/product_cost_fifo/tests/scenario_product_cost_fifo.rst`: Tryton FIFO cost scenario: product cost price and outgoing move cost prices under first-in first-out costing.
26
  Format: reStructuredText doctest scenario (proteus), 102 doctest prompts with expected outputs
27
  Origin: scenario test written by the module authors; products, quantities and prices are made up
 
 
28
  Check: hide the expected outputs (or give the incoming and outgoing moves and ask for the FIFO cost of each outgoing move and the product cost price); compare exactly at 4 decimals; reference run is the doctest on pinned trytond
29
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
30
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
31
  - `modules/stock/tests/scenario_stock_inventory.rst`: Tryton physical inventory scenario: expected quantities, counted quantities and the adjustment moves an inventory posts.
32
  Format: reStructuredText doctest scenario (proteus), 178 doctest prompts with expected outputs
33
  Origin: scenario test written by the module authors; products, quantities and prices are made up
 
 
34
  Check: hide the expected outputs (or give the stock moves and the counts and ask for the expected quantities and the adjustment moves); compare exactly; reference run is the doctest on pinned trytond
35
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
36
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
37
  - `modules/stock_supply/tests/scenario_stock_supply_purchase_request.rst`: Tryton stock supply scenario: purchase requests generated from shortages and order points (minimum and target quantities).
38
  Format: reStructuredText doctest scenario (proteus), 102 doctest prompts with expected outputs
39
  Origin: scenario test written by the module authors; products, quantities and prices are made up
 
 
40
  Check: hide the expected outputs (or give stock, open shipments and order points and ask for the purchase request quantities); compare exactly; reference run is the doctest on pinned trytond
41
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
42
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
43
  - `modules/stock/tests/scenario_stock_shipment_out.rst`: Tryton customer shipment scenario: assignment of outgoing moves against available stock, partial assignment and packing.
44
  Format: reStructuredText doctest scenario (proteus), 175 doctest prompts with expected outputs
45
  Origin: scenario test written by the module authors; products, quantities and prices are made up
 
 
46
  Check: hide the expected outputs (or give stock and shipment lines and ask which lines can be reserved and what is packed); compare exactly; reference run is the doctest on pinned trytond
47
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
48
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
49
  - `modules/stock/tests/scenario_stock_product_quantities_by_warehouse.rst`: Tryton product quantities by warehouse scenario: stock per day from done and planned moves, and the cumulative balance per move.
50
  Format: reStructuredText doctest scenario (proteus), 75 doctest prompts with expected outputs
51
  Origin: scenario test written by the module authors; products, quantities and prices are made up
 
 
52
  Check: hide the expected outputs (or give the done and planned moves and ask for stock per day and the running balance per move); compare exactly; reference run is the doctest on pinned trytond
53
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
54
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
55
  - `modules/stock/tests/scenario_stock_recompute_average_cost_price.rst`: Tryton scenario: recompute the average cost price of stock moves after back-dated moves and price changes.
56
  Format: reStructuredText doctest (proteus)
57
  Origin: test written by the project authors; products, quantities and prices are made up
 
 
58
  Check: give the dated moves and prices of the scenario and ask the average cost price of each move after recomputation; compare at the 4 decimals of the doctest output
59
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
60
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
61
  - `modules/stock/tests/scenario_stock_reporting_margin.rst`: Tryton scenario: stock margin reporting per product and category (quantity, cost, revenue, profit, margin).
62
  Format: reStructuredText doctest (proteus)
63
  Origin: test written by the project authors; products, quantities and prices are made up
 
 
64
  Check: give the moves with cost and sale prices and ask quantity, cost, revenue, profit and margin per product or category; compare money at 2 decimals and margin at the 4 decimals the doctest prints
65
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
66
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
67
  - `modules/stock/tests/scenario_stock_inventory_tolerance.rst`: Tryton scenario: inventory count over quantity and cost tolerance raises a warning.
68
  Format: reStructuredText doctest (proteus)
69
  Origin: test written by the project authors; products, quantities and prices are made up
 
 
70
  Check: give expected and counted quantities with cost prices and the two tolerances and ask the variations and whether confirming the inventory is over tolerance; compare the variations at the decimals printed and the over-tolerance verdict exactly
71
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
72
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
73
  - `modules/stock/tests/scenario_stock_reporting_inventory.rst`: Tryton scenario: inventory reporting by date (stock on a date, per-move and per-day balances) and inventory turnover.
74
  Format: reStructuredText doctest (proteus) with a JSON parameter file for 4 runs (period_close and product_type)
75
  Origin: test written by the project authors; products, quantities and prices are made up
 
 
76
  Check: give the dated moves of the scenario and ask the stock on a date, the running balance per move and per day, and the turnover over a date range; compare quantities exactly and turnover at the decimals printed
77
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
78
  Companions (not included): modules/stock/tests/scenario_stock_reporting_inventory.json
 
80
  - `modules/stock/tests/scenario_stock_inventory_count.rst`: Tryton scenario: counting stock with the count wizard, adding counted quantities to inventory lines.
81
  Format: reStructuredText doctest (proteus)
82
  Origin: test written by the project authors; products, quantities and prices are made up
 
 
83
  Check: give the count actions and ask the resulting inventory line quantities; compare exactly
84
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
85
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
86
  - `modules/stock/tests/scenario_stock_recompute_average_cost_price_production.rst`: Tryton scenario: recompute the average cost price when production consumption and returns move stock.
87
  Format: reStructuredText doctest (proteus), 114 lines
88
  Origin: test written by the project authors; products, quantities and prices are made up
 
 
89
  Check: give the dated moves (production consumption, return, later receipt) with unit prices and ask the cost price of each move and of the product after recomputation; compare at the 4 decimals of the doctest output
90
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
91
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
92
  - `modules/stock_supply/tests/scenario_stock_internal_supply.rst`: Tryton scenario: internal supply from order points (min and target quantity) and negative stock in a provisioned location.
93
  Format: reStructuredText doctest (proteus), 156 lines, run twice by its companion JSON (with and without warehouses)
94
  Origin: test written by the project authors; products, quantities and prices are made up
 
 
95
  Check: give the order point (minimum, target), the stock in each location and the provisioning links and ask the quantity of the internal shipment the supply wizard creates; compare exactly at the printed one decimal
96
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
97
  Companions (not included): modules/stock_supply/tests/scenario_stock_internal_supply.json
 
99
  - `modules/stock_quantity_issue/tests/scenario_stock_quantity_issue.rst`: Tryton scenario: forecast stock quantity issues from planned moves, with their priority and resolution.
100
  Format: reStructuredText doctest (proteus), 148 lines
101
  Origin: test written by the project authors; products, quantities and prices are made up
 
 
102
  Check: give the dated planned moves in and out and ask how many shortfall issues arise, their priority, and the quantity and forecast quantity on a given date; compare exactly
103
  Tools: Tryton proteus scripting interface (the scenario itself is a proteus doctest) against a headless trytond with SQLite; python -m doctest on the .rst file reproduces the reference run
104
  Dependencies: trytond, proteus and the Tryton modules named in the scenario header at commit 14f9f80be3acff956fc6a46e7c11163b70aa509d (Tryton 7.x series), Python 3, SQLite backend.
campaign_files/2026-10-op-rule-calculations-2/uci-275-bike-sharing/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: published_metric_values. Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** read hour.csv and day.csv with Python csv, aggregate hourly casual, registered and cnt per day and compare with day.csv, count records; write the daily totals to CSV
14
 
15
  **Licence (SPDX):** CC-BY-4.0
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: https://archive.ics.uci.edu/static/public/275/bike+sharing+dataset.zip
23
  Format: CSV hour.csv (17,379 rows, 1,156,736 bytes) with companions day.csv (731 rows), Readme.txt and the UCI dataset page (HTML)
24
  Origin: real Capital Bikeshare system logs, Washington D.C., 2011-2012
25
- Reference result: published_metric_values
26
- Reference source: Readme.txt lines 56-57: "hour.csv : bike sharing counts aggregated on hourly basis. Records: 17379 hours" and "day.csv - bike sharing counts aggregated on daily basis. Records: 731 days"; line 85: "cnt: count of total rental bikes including both casual and registered"; day.csv is the published daily aggregate of hour.csv
27
  Check: give hour.csv only; ask for the daily totals of casual, registered and cnt per date and the number of hourly and daily records; compare every daily value with day.csv exactly and the record counts with Readme.txt
28
  Tools: read hour.csv and day.csv with Python csv, aggregate hourly casual, registered and cnt per day and compare with day.csv, count records; write the daily totals to CSV
29
  Companions (not included): day.csv; Readme.txt; dataset_page_275.html
 
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** read hour.csv and day.csv with Python csv, aggregate hourly casual, registered and cnt per day and compare with day.csv, count records; write the daily totals to CSV
12
 
13
  **Licence (SPDX):** CC-BY-4.0
 
20
  Read out of the archive: https://archive.ics.uci.edu/static/public/275/bike+sharing+dataset.zip
21
  Format: CSV hour.csv (17,379 rows, 1,156,736 bytes) with companions day.csv (731 rows), Readme.txt and the UCI dataset page (HTML)
22
  Origin: real Capital Bikeshare system logs, Washington D.C., 2011-2012
 
 
23
  Check: give hour.csv only; ask for the daily totals of casual, registered and cnt per date and the number of hourly and daily records; compare every daily value with day.csv exactly and the record counts with Readme.txt
24
  Tools: read hour.csv and day.csv with Python csv, aggregate hourly casual, registered and cnt per day and compare with day.csv, count records; write the daily totals to CSV
25
  Companions (not included): day.csv; Readme.txt; dataset_page_275.html
campaign_files/2026-10-op-rule-calculations-2/uci-292-wholesale-customers/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: published_metric_values. Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** read the CSV with Python csv, compute min, max, mean and sample standard deviation of the six spending columns and the frequency of each Region and Channel code; write them to JSON
14
 
15
  **Licence (SPDX):** CC-BY-4.0
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: https://archive.ics.uci.edu/static/public/292/wholesale+customers.zip
23
  Format: CSV, 440 rows plus header, 15,021 bytes; companion: the UCI dataset page (HTML) that prints the statistics
24
  Origin: real clients of a wholesale distributor in Portugal (Cardoso 2014), annual spending in monetary units
25
- Reference result: published_metric_values
26
- Reference source: dataset_page_292.html, Additional Variable Information: "Descriptive Statistics: (Minimum, Maximum, Mean, Std. Deviation) FRESH ( 3, 112151, 12000.30, 12647.329) ..." for six columns, and "REGION Frequency Lisbon 77 Oporto 47 Other Region 316 Total 440 CHANNEL Frequency Horeca 298 Retail 142 Total 440" (Region coded 1 Lisbon, 2 Oporto, 3 Other; Channel 1 Horeca, 2 Retail)
27
  Check: give the CSV; ask for min, max, mean and standard deviation of each spending column and the counts per Region and Channel; compare each number with the page values to its printed precision (means to the cent, std to three decimals, counts and min/max exactly)
28
  Tools: read the CSV with Python csv, compute min, max, mean and sample standard deviation of the six spending columns and the frequency of each Region and Channel code; write them to JSON
29
  Companions (not included): dataset_page_292.html
 
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** read the CSV with Python csv, compute min, max, mean and sample standard deviation of the six spending columns and the frequency of each Region and Channel code; write them to JSON
12
 
13
  **Licence (SPDX):** CC-BY-4.0
 
20
  Read out of the archive: https://archive.ics.uci.edu/static/public/292/wholesale+customers.zip
21
  Format: CSV, 440 rows plus header, 15,021 bytes; companion: the UCI dataset page (HTML) that prints the statistics
22
  Origin: real clients of a wholesale distributor in Portugal (Cardoso 2014), annual spending in monetary units
 
 
23
  Check: give the CSV; ask for min, max, mean and standard deviation of each spending column and the counts per Region and Channel; compare each number with the page values to its printed precision (means to the cent, std to three decimals, counts and min/max exactly)
24
  Tools: read the CSV with Python csv, compute min, max, mean and sample standard deviation of the six spending columns and the frequency of each Region and Channel code; write them to JSON
25
  Companions (not included): dataset_page_292.html
campaign_files/2026-10-op-rule-calculations-2/uci-468-online-shoppers-purchasing-intention/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: published_metric_values. Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** read the CSV with Python csv, count sessions and sessions with Revenue TRUE / FALSE, compute the conversion rate; write it to JSON
14
 
15
  **Licence (SPDX):** CC-BY-4.0
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: https://archive.ics.uci.edu/static/public/468/online+shoppers+purchasing+intention+dataset.zip
23
  Format: CSV, 12,330 rows plus header, 1,072,063 bytes; companion: the UCI dataset page (HTML)
24
  Origin: real sessions of an online store over one year (Sakar et al. 2019)
25
- Reference result: published_metric_values
26
- Reference source: dataset_page_468.html, abstract: "Of the 12,330 sessions in the dataset, 84.5% (10,422) were negative class samples that did not end with shopping, and the rest (1908) were positive class samples ending with shopping."
27
  Check: give the CSV; ask for the number of sessions, the number and share that ended in a purchase and that did not; compare counts exactly and the share to its printed precision (one decimal of a percent)
28
  Tools: read the CSV with Python csv, count sessions and sessions with Revenue TRUE / FALSE, compute the conversion rate; write it to JSON
29
  Companions (not included): dataset_page_468.html
 
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** read the CSV with Python csv, count sessions and sessions with Revenue TRUE / FALSE, compute the conversion rate; write it to JSON
12
 
13
  **Licence (SPDX):** CC-BY-4.0
 
20
  Read out of the archive: https://archive.ics.uci.edu/static/public/468/online+shoppers+purchasing+intention+dataset.zip
21
  Format: CSV, 12,330 rows plus header, 1,072,063 bytes; companion: the UCI dataset page (HTML)
22
  Origin: real sessions of an online store over one year (Sakar et al. 2019)
 
 
23
  Check: give the CSV; ask for the number of sessions, the number and share that ended in a purchase and that did not; compare counts exactly and the share to its printed precision (one decimal of a percent)
24
  Tools: read the CSV with Python csv, count sessions and sessions with Revenue TRUE / FALSE, compute the conversion rate; write it to JSON
25
  Companions (not included): dataset_page_468.html
campaign_files/2026-10-op-rule-calculations-2/uci-488-facebook-live-sellers-thailand/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: published_metric_values. Where the reference result comes from and how a solution is checked is written per unit in the notes.
12
-
13
  **Tools to open and check:** read the CSV with Python csv, split the rows into the 10 seller pages by the row ranges given in the article, compute mean, sample SD and max of the 8 engagement columns per page; write them to CSV
14
 
15
  **Licence (SPDX):** CC-BY-4.0
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: https://archive.ics.uci.edu/static/public/488/facebook+live+sellers+in+thailand.zip
23
  Format: CSV, 7,050 rows plus header, 366,355 bytes; companions: the UCI dataset page (HTML) and the article full text (JATS XML)
24
  Origin: real posts collected through the Facebook API (article Specifications table)
25
- Reference result: published_metric_values
26
- Reference source: PMC7218155_fullTextXML.xml, Table 1 "Descriptive statistics of engagement metrics for each Facebook seller in the Dataset": mean, SD and max of Comment, Share, Like, Love, Wow, Haha, Sad, Angry for pages 1 to 10 by spreadsheet start and end row (page 1 rows 2-2636, ...), 240 values
27
  Check: give the CSV and the row range of each seller page; ask for mean, SD and max of the 8 engagement columns per page; compare every value to two decimals
28
  Tools: read the CSV with Python csv, split the rows into the 10 seller pages by the row ranges given in the article, compute mean, sample SD and max of the 8 engagement columns per page; write them to CSV
29
  Companions (not included): dataset_page_488.html; PMC7218155_fullTextXML.xml
 
8
 
9
  **Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** read the CSV with Python csv, split the rows into the 10 seller pages by the row ranges given in the article, compute mean, sample SD and max of the 8 engagement columns per page; write them to CSV
12
 
13
  **Licence (SPDX):** CC-BY-4.0
 
20
  Read out of the archive: https://archive.ics.uci.edu/static/public/488/facebook+live+sellers+in+thailand.zip
21
  Format: CSV, 7,050 rows plus header, 366,355 bytes; companions: the UCI dataset page (HTML) and the article full text (JATS XML)
22
  Origin: real posts collected through the Facebook API (article Specifications table)
 
 
23
  Check: give the CSV and the row range of each seller page; ask for mean, SD and max of the 8 engagement columns per page; compare every value to two decimals
24
  Tools: read the CSV with Python csv, split the rows into the 10 seller pages by the row ranges given in the article, compute mean, sample SD and max of the 8 engagement columns per page; write them to CSV
25
  Companions (not included): dataset_page_488.html; PMC7218155_fullTextXML.xml
campaign_files/2026-10-s-security-detection-2/trail-of-bits-semgrep-rules/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_findings_by_line. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Task: report the lines that load a DLL unsafely. Score precision and recall against the lines after each ruleid comment; a line after an ok comment reported counts as a false positive.
14
 
15
  **Licence (SPDX):** AGPL-3.0-only
@@ -21,8 +19,6 @@ Files:
21
  - `go/unsafe-dll-loading.go`: Unsafe-dll-loading: find the Go DLL loads that are open to DLL search order hijacking (CWE-427).
22
  Format: Go source (2,090 B) annotated with Semgrep ruleid and ok comments; rule in YAML
23
  Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
24
- Reference result: expected_findings_by_line
25
- Reference source: Semgrep test annotations: 13 ruleid comments (lines 10, 14, 22, 31, 36, 50, 58, 61, 71, 76, 82, 86, 89) each mark the next line as a finding, 6 ok comments (lines 18, 26, 41, 46, 55, 65) mark safe loads; no todoruleid or todook
26
  Check: Task: report the lines that load a DLL unsafely. Score precision and recall against the lines after each ruleid comment; a line after an ok comment reported counts as a false positive
27
  Companions (not included): go/unsafe-dll-loading.yaml; LICENSE
28
  Dependencies: Semgrep CLI (LGPL-2.1): needed only to rerun the rule test; not used by the judge; version pinned when the pool is built; not packed
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Task: report the lines that load a DLL unsafely. Score precision and recall against the lines after each ruleid comment; a line after an ok comment reported counts as a false positive.
12
 
13
  **Licence (SPDX):** AGPL-3.0-only
 
19
  - `go/unsafe-dll-loading.go`: Unsafe-dll-loading: find the Go DLL loads that are open to DLL search order hijacking (CWE-427).
20
  Format: Go source (2,090 B) annotated with Semgrep ruleid and ok comments; rule in YAML
21
  Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
 
 
22
  Check: Task: report the lines that load a DLL unsafely. Score precision and recall against the lines after each ruleid comment; a line after an ok comment reported counts as a false positive
23
  Companions (not included): go/unsafe-dll-loading.yaml; LICENSE
24
  Dependencies: Semgrep CLI (LGPL-2.1): needed only to rerun the rule test; not used by the judge; version pinned when the pool is built; not packed
campaign_files/2026-10-s-security-detection-2/trivy-checks-kubernetes-checks/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_verdict_per_case. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Task: for each manifest say whether it mounts the Docker socket. Score: exact match of the verdict per manifest (2 cases); variant: the agent writes the Rego deny rule and it must pass the shipped test.
14
 
15
  **Licence (SPDX):** MIT
@@ -21,8 +19,6 @@ Files:
21
  - `checks/kubernetes/mounts_docker_socket.yaml`: Trivy-checks KSV-0006: decide whether a Pod mounts the Docker socket.
22
  Format: YAML with one good and one bad Pod manifest; Rego check KSV-0006 importing data.lib.kubernetes; Rego unit test
23
  Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
24
- Reference result: expected_verdict_per_case
25
- Reference source: mounts_docker_socket.yaml good and bad sections (the bad Pod mounts hostPath /var/run/docker.sock); mounts_docker_socket_test.rego asserts a deny on the bad input and none on the good one
26
  Check: Task: for each manifest say whether it mounts the Docker socket. Score: exact match of the verdict per manifest (2 cases); variant: the agent writes the Rego deny rule and it must pass the shipped test
27
  Companions (not included): checks/kubernetes/mounts_docker_socket.rego; lib/kubernetes/kubernetes.rego; checks/kubernetes/mounts_docker_socket_test.rego; LICENSE
28
  Dependencies: Open Policy Agent or trivy (Apache-2.0): needed only to rerun the Rego test; not used by the judge; version pinned when the pool is built; not packed
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Task: for each manifest say whether it mounts the Docker socket. Score: exact match of the verdict per manifest (2 cases); variant: the agent writes the Rego deny rule and it must pass the shipped test.
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `checks/kubernetes/mounts_docker_socket.yaml`: Trivy-checks KSV-0006: decide whether a Pod mounts the Docker socket.
20
  Format: YAML with one good and one bad Pod manifest; Rego check KSV-0006 importing data.lib.kubernetes; Rego unit test
21
  Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
 
 
22
  Check: Task: for each manifest say whether it mounts the Docker socket. Score: exact match of the verdict per manifest (2 cases); variant: the agent writes the Rego deny rule and it must pass the shipped test
23
  Companions (not included): checks/kubernetes/mounts_docker_socket.rego; lib/kubernetes/kubernetes.rego; checks/kubernetes/mounts_docker_socket_test.rego; LICENSE
24
  Dependencies: Open Policy Agent or trivy (Apache-2.0): needed only to rerun the Rego test; not used by the judge; version pinned when the pool is built; not packed
campaign_files/2026-10-s-security-detection-2/trivy-checks-kubernetes-misconfiguration-checks/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: per_resource_verdict. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Task: for each of the 4 Pods (2 from the YAML, 2 from the test inputs, labels hidden) say whether KSV024 denies it, and give the deny message for denied ones. Score: exact match of the verdict; message compared as exact string against test line 23.
14
 
15
  **Licence (SPDX):** MIT
@@ -21,8 +19,6 @@ Files:
21
  - `checks/kubernetes/access_to_host_ports.rego`: Trivy-checks KSV024 access_to_host_ports: decide for the good and bad Pod examples and the 2 Rego test inputs whether the check denies host ports.
22
  Format: Rego check (access_to_host_ports.rego, METADATA id KSV-0024, severity HIGH), a YAML file with one good and one bad Pod, and a Rego unit test with 2 inputs and expected deny counts
23
  Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
24
- Reference result: per_resource_verdict
25
- Reference source: access_to_host_ports.yaml: good Pod lines 2 to 15, bad Pod lines 16 to 31 (hostPort 8080); access_to_host_ports_test.rego line 22 count(r) == 1 with message line 23, line 43 count(r) == 0
26
  Check: Task: for each of the 4 Pods (2 from the YAML, 2 from the test inputs, labels hidden) say whether KSV024 denies it, and give the deny message for denied ones. Score: exact match of the verdict; message compared as exact string against test line 23
27
  Companions (not included): checks/kubernetes/access_to_host_ports.yaml; checks/kubernetes/access_to_host_ports_test.rego; lib/kubernetes/kubernetes.rego; LICENSE
28
  Dependencies: trivy or opa at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Task: for each of the 4 Pods (2 from the YAML, 2 from the test inputs, labels hidden) say whether KSV024 denies it, and give the deny message for denied ones. Score: exact match of the verdict; message compared as exact string against test line 23.
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `checks/kubernetes/access_to_host_ports.rego`: Trivy-checks KSV024 access_to_host_ports: decide for the good and bad Pod examples and the 2 Rego test inputs whether the check denies host ports.
20
  Format: Rego check (access_to_host_ports.rego, METADATA id KSV-0024, severity HIGH), a YAML file with one good and one bad Pod, and a Rego unit test with 2 inputs and expected deny counts
21
  Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
 
 
22
  Check: Task: for each of the 4 Pods (2 from the YAML, 2 from the test inputs, labels hidden) say whether KSV024 denies it, and give the deny message for denied ones. Score: exact match of the verdict; message compared as exact string against test line 23
23
  Companions (not included): checks/kubernetes/access_to_host_ports.yaml; checks/kubernetes/access_to_host_ports_test.rego; lib/kubernetes/kubernetes.rego; LICENSE
24
  Dependencies: trivy or opa at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
campaign_files/2026-10-s-security-detection-2/trivy-checks-rego-check-with-tests-and-examples/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: per_example_verdict. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Task: with the good and bad labels and resource names hidden, say which definition violates the rule. Score: per-example verdict exact match; the variant asks for a Rego rule that passes the 2 upstream unit tests.
14
 
15
  **Licence (SPDX):** MIT
@@ -21,8 +19,6 @@ Files:
21
  - `checks/cloud/azure/keyvault/specify_network_acl.yaml`: Trivy-checks AZU-0013: decide which Azure Key Vault Terraform definition lacks a network ACL with default action Deny.
22
  Format: check example file (923 B) with good and bad Terraform and ARM examples; Rego rule and Rego unit test as companions
23
  Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
24
- Reference result: per_example_verdict
25
- Reference source: specify_network_acl.yaml good and bad lists; specify_network_acl_test.rego lines 7 to 15: default action Allow gives 1 denial, Deny gives 0
26
  Check: Task: with the good and bad labels and resource names hidden, say which definition violates the rule. Score: per-example verdict exact match; the variant asks for a Rego rule that passes the 2 upstream unit tests
27
  Companions (not included): checks/cloud/azure/keyvault/specify_network_acl_test.rego; checks/cloud/azure/keyvault/specify_network_acl.rego; LICENSE
28
  Dependencies: trivy or OPA at this commit (MIT): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Task: with the good and bad labels and resource names hidden, say which definition violates the rule. Score: per-example verdict exact match; the variant asks for a Rego rule that passes the 2 upstream unit tests.
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `checks/cloud/azure/keyvault/specify_network_acl.yaml`: Trivy-checks AZU-0013: decide which Azure Key Vault Terraform definition lacks a network ACL with default action Deny.
20
  Format: check example file (923 B) with good and bad Terraform and ARM examples; Rego rule and Rego unit test as companions
21
  Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
 
 
22
  Check: Task: with the good and bad labels and resource names hidden, say which definition violates the rule. Score: per-example verdict exact match; the variant asks for a Rego rule that passes the 2 upstream unit tests
23
  Companions (not included): checks/cloud/azure/keyvault/specify_network_acl_test.rego; checks/cloud/azure/keyvault/specify_network_acl.rego; LICENSE
24
  Dependencies: trivy or OPA at this commit (MIT): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
campaign_files/2026-10-s-security-detection-2/tudctf-2024-public-challenges/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 5 of 5 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: flag_string. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,40 +19,30 @@ Files:
21
  - `forensics/why_even_pretend/dist/output.cap`: TUDCTF 2024 forensics/Why Even Pretend?: an 802.11 capture of a WEP-protected network; crack the WEP key and report it as the flag.
22
  Format: one 802.11 (radiotap, link-type 105) capture (5,514,315 B, 66,111 frames) of a WEP network SSID 'Major domus' with two stations
23
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
24
- Reference result: flag_string
25
- Reference source: challenge.yml line 18 gives TUDCTF{DDE4E548F0} and the description states the flag is the recovered key in hex. Verified offline only that the capture is a WEP 802.11 trace (66,111 frames, SSID 'Major domus', two stations).
26
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
27
  Companions (not included): challenge.yml
28
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built
29
  - `forensics/cybercrime_battle_royale/dist/card.zip`: TUDCTF 2024 forensics/Cybercrime Battle Royale: a ZipCrypto archive whose plaintext (card.jpg) is known; recover the PIN and decrypt (a known-plaintext / weak-PIN exercise).
30
  Format: one ZipCrypto-encrypted zip (210,146 B) plus the known plaintext file card.jpg (216,603 B); the archive was made with a short numeric PIN
31
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
32
- Reference result: flag_string
33
- Reference source: challenge.yml line 17 gives TUDCTF{01189998819991197253} (a synthetic flag, not derivable from the zip bytes). Verified offline: the zip entry CRC 0xa4c86080 equals the CRC of card.jpg, and decrypting with PIN 4856 (the PIN is public in the repo's encrypt.sh, zip -P 4856, https://raw.githubusercontent.com/TU-Delft-CTF-Team/tudctf-2024-challenges/0f1778439b837f94796c9c2be011c3b69455cc57/forensics/cybercrime_battle_royale/encrypt.sh) yields a JPEG byte-equal to card.jpg
34
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
35
  Companions (not included): card.jpg; challenge.yml
36
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built; encrypt.sh in the repository holds the PIN (zip -P 4856).
37
  - `forensics/coati-intelligence-agency/secret_report.pdf`: TUDCTF 2024 forensics/Coati Intelligence Agency: a PDF whose redaction only draws black boxes over the text; recover the hidden text under the redaction.
38
  Format: one PDF (131,572 B, PDF 1.7, 3 pages, produced by Microsoft Word) with visually redacted text that is still present in the content stream
39
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
40
- Reference result: flag_string
41
- Reference source: challenge.yml line 15 gives TUDCTF{b4d_pdf_r3d4ct10n_s1nks_sh1ps}. Verified offline that the PDF is benign (PDF 1.7, 3 pages; /JS, /JavaScript, /OpenAction, /AA, /Launch, /EmbeddedFile and /URI all count 0).
42
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
43
  Companions (not included): challenge.yml
44
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built
45
  - `forensics/repo_on_the_wire/dist/capture.pcapng`: TUDCTF 2024 forensics/Repo on the wire: a capture of a git clone over the unencrypted git protocol; reassemble the pack and read the flag from a committed file.
46
  Format: one pcapng (5,512 B) carrying a git smart-protocol transfer (a zlib-compressed git pack with the repository objects)
47
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
48
- Reference result: flag_string
49
- Reference source: challenge.yml line 18 gives TUDCTF{it5_2024_u53_55h_4nd_n0t_g1t_pr0t0c01}. Verified offline: a zlib scan of the git pack bytes in the pcap recovers flag.py containing exec(b64decode('cHJpbnQoJ1RVRENURntpdDVfMjAyNF91NTNfNTVoXzRuZF9uMHRfZzF0X3ByMHQwYzAxfScp')), which base64-decodes to a Python print of exactly this flag
50
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
51
  Companions (not included): challenge.yml
52
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built
53
  - `stego/weird-flex-but-ok/random_leaderboard.jpg`: TUDCTF 2024 stego/Weird flex, but ok: a JPEG whose XMP title carries a password; use it to decrypt the repo's flag ciphertext (steghide-style password recovery).
54
  Format: one JPEG (808,460 B, a game leaderboard screenshot) whose XMP dc:title field holds the password IWillNotGiveUpMySecretsEasily
55
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
56
- Reference result: flag_string
57
- Reference source: challenge.yml line 13 gives TUDCTF{a-hug-7o-all-our-fr13nd5-at-VU}. Verified offline: the JPEG XMP dc:title holds the password IWillNotGiveUpMySecretsEasily, and the repo's flag.txt.enc decrypts with openssl enc -d -aes-256-cbc -pbkdf2 -a (password as above) to exactly this flag.
58
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
59
  Companions (not included): challenge.yml
60
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 5 of 5 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `forensics/why_even_pretend/dist/output.cap`: TUDCTF 2024 forensics/Why Even Pretend?: an 802.11 capture of a WEP-protected network; crack the WEP key and report it as the flag.
20
  Format: one 802.11 (radiotap, link-type 105) capture (5,514,315 B, 66,111 frames) of a WEP network SSID 'Major domus' with two stations
21
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
 
 
22
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
23
  Companions (not included): challenge.yml
24
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built
25
  - `forensics/cybercrime_battle_royale/dist/card.zip`: TUDCTF 2024 forensics/Cybercrime Battle Royale: a ZipCrypto archive whose plaintext (card.jpg) is known; recover the PIN and decrypt (a known-plaintext / weak-PIN exercise).
26
  Format: one ZipCrypto-encrypted zip (210,146 B) plus the known plaintext file card.jpg (216,603 B); the archive was made with a short numeric PIN
27
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
 
 
28
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
29
  Companions (not included): card.jpg; challenge.yml
30
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built; encrypt.sh in the repository holds the PIN (zip -P 4856).
31
  - `forensics/coati-intelligence-agency/secret_report.pdf`: TUDCTF 2024 forensics/Coati Intelligence Agency: a PDF whose redaction only draws black boxes over the text; recover the hidden text under the redaction.
32
  Format: one PDF (131,572 B, PDF 1.7, 3 pages, produced by Microsoft Word) with visually redacted text that is still present in the content stream
33
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
 
 
34
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
35
  Companions (not included): challenge.yml
36
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built
37
  - `forensics/repo_on_the_wire/dist/capture.pcapng`: TUDCTF 2024 forensics/Repo on the wire: a capture of a git clone over the unencrypted git protocol; reassemble the pack and read the flag from a committed file.
38
  Format: one pcapng (5,512 B) carrying a git smart-protocol transfer (a zlib-compressed git pack with the repository objects)
39
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
 
 
40
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
41
  Companions (not included): challenge.yml
42
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built
43
  - `stego/weird-flex-but-ok/random_leaderboard.jpg`: TUDCTF 2024 stego/Weird flex, but ok: a JPEG whose XMP title carries a password; use it to decrypt the repo's flag ciphertext (steghide-style password recovery).
44
  Format: one JPEG (808,460 B, a game leaderboard screenshot) whose XMP dc:title field holds the password IWillNotGiveUpMySecretsEasily
45
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
 
 
46
  Check: Exact string match of the submitted flag against challenge.yml flags; no tolerance
47
  Companions (not included): challenge.yml
48
  Dependencies: challenge.yml holds the flag (hidden from the solver); the official solution path is public in the repository; solver tools are free choices (for example a pcap, zip, image or PDF tool), version fixed when the pool is built
campaign_files/2026-10-s-security-detection-2/umdctf-public-challenges-archive/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Each file is self-contained. 3 of 3 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: flag_string. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Compute sha256 of the submitted string (UTF-8, no trailing newline) and compare for equality with the README digest. Exact string match against the generate.py flag (the README digest is not used because it does not match).
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,24 +19,18 @@ Files:
21
  - `UMDCTF2018/Forensics/Eternally Crying/Microsoft-Windows-Sysmon%4Operational.evtx`: UMDCTF 2018 Forensics/Eternally Crying: reconstruct the message a ransomware sample leaked through Run-key registry writes in a Sysmon log.
22
  Format: Sysmon Operational EVTX (1,118,208 B)
23
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and writeup (fixture of a competition, not recorded production telemetry)
24
- Reference result: flag_string
25
- Reference source: README.md line 5 (sha256 cbe25dc525340a2e9d7697d4b44c1cd194779b1738ce61c5fab089832259e3dd); plaintext UMDCTF-{its-quite-noisy-here} checked by me to hash to it
26
  Check: Compute sha256 of the submitted string (UTF-8, no trailing newline) and compare for equality with the README digest.
27
  Companions (not included): README.md
28
  Dependencies: README.md gives the flag only as a sha256 digest; the plaintext is recovered from the evidence (the dev/mal.py simulator source is not packed)
29
  - `UMDCTF2020/Forensics/NefariousBits/prod/attack.pcap`: UMDCTF 2020 Forensics/NefariousBits: recover a message hidden in the IP reserved (evil) bit of a TCP SYN stream.
30
  Format: pcap (19,064 B, 272 packets)
31
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and writeup (fixture of a competition, not recorded production telemetry)
32
- Reference result: flag_string
33
- Reference source: dev/generate.py line 7 (UMDCTF-{3vil_b1ts_@r3_4lw4ys_3vi1}); my offline decode of the 272 packets gives the same string; the README line 9 digest does not match it
34
  Check: Exact string match against the generate.py flag (the README digest is not used because it does not match).
35
  Companions (not included): README.md; dev/generate.py
36
  Dependencies: dev/generate.py is the organiser generator holding the flag (line 7), read as text only, never run, hidden from the solver
37
  - `UMDCTF2021/Forensics/Protocol-One-And-Zero/protocol_one_and_zero.pcapng`: UMDCTF 2021 Forensics/Protocol-One-And-Zero: recover a message hidden in ICMP echo payloads on localhost.
38
  Format: pcapng (46,808 B, 176 echo requests)
39
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and writeup (fixture of a competition, not recorded production telemetry)
40
- Reference result: flag_string
41
- Reference source: README.md line 7 (sha256 e1638d36a248af238ff61ba9cbcf90abdbafcbf729ea2dcfbdc80b005b8dce16); my offline decode gives UMDCTF-{b1n_p1Ng_P0ng}, which hashes to it
42
  Check: Compute sha256 of the submitted string (UTF-8, no trailing newline) and compare for equality with the README digest.
43
  Companions (not included): README.md
44
  Dependencies: README.md gives the flag only as a sha256 digest
 
8
 
9
  **Self-contained:** Each file is self-contained. 3 of 3 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Compute sha256 of the submitted string (UTF-8, no trailing newline) and compare for equality with the README digest. Exact string match against the generate.py flag (the README digest is not used because it does not match).
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `UMDCTF2018/Forensics/Eternally Crying/Microsoft-Windows-Sysmon%4Operational.evtx`: UMDCTF 2018 Forensics/Eternally Crying: reconstruct the message a ransomware sample leaked through Run-key registry writes in a Sysmon log.
20
  Format: Sysmon Operational EVTX (1,118,208 B)
21
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and writeup (fixture of a competition, not recorded production telemetry)
 
 
22
  Check: Compute sha256 of the submitted string (UTF-8, no trailing newline) and compare for equality with the README digest.
23
  Companions (not included): README.md
24
  Dependencies: README.md gives the flag only as a sha256 digest; the plaintext is recovered from the evidence (the dev/mal.py simulator source is not packed)
25
  - `UMDCTF2020/Forensics/NefariousBits/prod/attack.pcap`: UMDCTF 2020 Forensics/NefariousBits: recover a message hidden in the IP reserved (evil) bit of a TCP SYN stream.
26
  Format: pcap (19,064 B, 272 packets)
27
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and writeup (fixture of a competition, not recorded production telemetry)
 
 
28
  Check: Exact string match against the generate.py flag (the README digest is not used because it does not match).
29
  Companions (not included): README.md; dev/generate.py
30
  Dependencies: dev/generate.py is the organiser generator holding the flag (line 7), read as text only, never run, hidden from the solver
31
  - `UMDCTF2021/Forensics/Protocol-One-And-Zero/protocol_one_and_zero.pcapng`: UMDCTF 2021 Forensics/Protocol-One-And-Zero: recover a message hidden in ICMP echo payloads on localhost.
32
  Format: pcapng (46,808 B, 176 echo requests)
33
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and writeup (fixture of a competition, not recorded production telemetry)
 
 
34
  Check: Compute sha256 of the submitted string (UTF-8, no trailing newline) and compare for equality with the README digest.
35
  Companions (not included): README.md
36
  Dependencies: README.md gives the flag only as a sha256 digest
campaign_files/2026-10-s-security-detection/trailofbits-semgrep-rules/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is marked self-contained upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_findings_by_line. Where the reference result comes from and how a solution is checked is written per file in the notes.
12
-
13
  **Tools to open and check:** Check: Semgrep --test (open-source engine) or compare the agent's flagged lines with the markers; precision and recall over marked lines. Markers by their meaning (general item 5): lines marked ruleid or todoruleid are real issues that must be flagged; lines marked ok or todook are false-positive traps that must not be. This file has 6 ruleid (lines 13, 17, 25, 29, 38, 42), 8 ok and no todoruleid or todook.
14
 
15
  **Licence (SPDX):** AGPL-3.0-only
@@ -21,7 +19,5 @@ Files:
21
  - `python/pandas-eval.yaml`: Trail of Bits Semgrep rule pandas-eval with its annotated test file (ruleid / ok markers).
22
  Format: Semgrep rule YAML + test source with inline expected-finding comments
23
  Origin: test cases written by hand for the detection project's test suite (was constructed)
24
- Reference result: expected_findings_by_line
25
- Reference source: # ruleid: pandas-eval marks each line that must be flagged; # ok: pandas-eval marks lines that must not be
26
  Check: semgrep --test (open-source engine) or compare the agent's flagged lines with the markers; precision and recall over marked lines. Markers by their meaning (general item 5): lines marked ruleid or todoruleid are real issues that must be flagged; lines marked ok or todook are false-positive traps that must not be. This file has 6 ruleid (lines 13, 17, 25, 29, 38, 42), 8 ok and no todoruleid or todook
27
  Companions (not included): python/pandas-eval.py
 
8
 
9
  **Self-contained:** The file is marked self-contained upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
10
 
 
 
11
  **Tools to open and check:** Check: Semgrep --test (open-source engine) or compare the agent's flagged lines with the markers; precision and recall over marked lines. Markers by their meaning (general item 5): lines marked ruleid or todoruleid are real issues that must be flagged; lines marked ok or todook are false-positive traps that must not be. This file has 6 ruleid (lines 13, 17, 25, 29, 38, 42), 8 ok and no todoruleid or todook.
12
 
13
  **Licence (SPDX):** AGPL-3.0-only
 
19
  - `python/pandas-eval.yaml`: Trail of Bits Semgrep rule pandas-eval with its annotated test file (ruleid / ok markers).
20
  Format: Semgrep rule YAML + test source with inline expected-finding comments
21
  Origin: test cases written by hand for the detection project's test suite (was constructed)
 
 
22
  Check: semgrep --test (open-source engine) or compare the agent's flagged lines with the markers; precision and recall over marked lines. Markers by their meaning (general item 5): lines marked ruleid or todoruleid are real issues that must be flagged; lines marked ok or todook are false-positive traps that must not be. This file has 6 ruleid (lines 13, 17, 25, 29, 38, 42), 8 ok and no todoruleid or todook
23
  Companions (not included): python/pandas-eval.py