Release [run release-20261111T080710Z]

#14
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 +16 -0
  2. README.md +35 -35
  3. README.zh.md +35 -35
  4. campaign_files/2026-10-a-spreadsheets-with-answers-2/genesys-mod-data-source-workbooks/README.md +0 -2
  5. campaign_files/2026-10-a-spreadsheets-with-answers-2/gflohr-e-invoice-eu/README.md +0 -2
  6. campaign_files/2026-10-b-disk-images-2/exfatprogs-fsck-cases/README.md +0 -17
  7. campaign_files/2026-10-b-disk-images-2/fatcat-fat-images/README.md +0 -9
  8. campaign_files/2026-10-c-repros-2/feynman-repro/README.md +0 -2
  9. campaign_files/2026-10-c-repros-2/gdpnum-repro/README.md +0 -2
  10. campaign_files/2026-10-c-repros-2/gidney-ekera-2019-repro/README.md +0 -2
  11. campaign_files/2026-10-c-repros/fact-ai-dawlau-repro/LICENSE.txt +7 -0
  12. campaign_files/2026-10-c-repros/fact-ai-dawlau-repro/README.md +0 -2
  13. campaign_files/2026-10-c-repros/fact-ai-imandrealombardo-repro/LICENSE.txt +6 -0
  14. campaign_files/2026-10-c-repros/fact-ai-imandrealombardo-repro/README.md +0 -2
  15. campaign_files/2026-10-c-repros/fairness-attacks-repro/LICENSE.txt +6 -0
  16. campaign_files/2026-10-c-repros/fairness-attacks-repro/README.md +0 -2
  17. campaign_files/2026-10-g-solver-instances-2/francoisggg-suguru/LICENSE +3 -0
  18. campaign_files/2026-10-g-solver-instances-2/francoisggg-suguru/README.md +23 -0
  19. campaign_files/2026-10-gt-browser-tests-2/firefox-autoconfig-tests/README.md +0 -4
  20. campaign_files/2026-10-gt-browser-tests-2/firefox-enterprisepolicies-tests/README.md +0 -24
  21. campaign_files/2026-10-gt-browser-tests-2/firefox-exthandler-tests/README.md +0 -4
  22. campaign_files/2026-10-gt-browser-tests-2/firefox-libpref-tests/README.md +0 -10
  23. campaign_files/2026-10-gt-browser-tests-2/firefox-toolkit-profile-tests/README.md +0 -4
  24. campaign_files/2026-10-gt-browser-tests-2/flanker-bounce-fixtures/README.md +0 -4
  25. campaign_files/2026-10-gt-browser-tests-2/fontconfig-json-tests/README.md +0 -9
  26. campaign_files/2026-10-gt-browser-tests-2/freecad-cam-post-tests/README.md +0 -14
  27. campaign_files/2026-10-gt-browser-tests-2/freecad-fem-test-calculix/README.md +0 -8
  28. campaign_files/2026-10-gt-browser-tests-2/freecad-fem-test-elmer/README.md +0 -4
  29. campaign_files/2026-10-gt-browser-tests-2/freecad-fem-test-mystran/README.md +0 -6
  30. campaign_files/2026-10-gt-browser-tests-2/freecad-femtest-calculix/README.md +0 -12
  31. campaign_files/2026-10-hw-eda-tests-2/fluidnc-firmware-fixture-tests-main-at-commit-741ed9e-github-bdring-fluidnc/README.md +0 -8
  32. campaign_files/2026-10-hw-eda-tests-2/fpu/README.md +0 -18
  33. campaign_files/2026-10-hw-eda-tests-2/freecad-main-at-commit-200ccc4-github-freecad-freecad-the-open-source-57f0b9b0/README.md +0 -12
  34. campaign_files/2026-10-m-issue-trackers-2/eyms-passenger-gtfs/README.md +0 -4
  35. campaign_files/2026-10-m-issue-trackers-2/fdio-gerrit-changes/README.md +0 -4
  36. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-ci-tickets-issues/README.md +0 -6
  37. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-council-tickets-issues/README.md +0 -6
  38. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-dei-tickets-issues/README.md +0 -4
  39. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-design-tickets-issues/README.md +0 -4
  40. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-docs-tickets-issues/README.md +0 -4
  41. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-epel-releng/README.md +0 -6
  42. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-fesco-tickets-issues/README.md +0 -4
  43. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-flatpak-tickets-issues/README.md +0 -4
  44. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-infra-tickets/README.md +0 -10
  45. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-localization-tickets-issues/README.md +0 -4
  46. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-packaging-sponsors-issues/README.md +0 -4
  47. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-quality-tickets-issues/README.md +0 -6
  48. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-releng-tickets-issues/README.md +0 -6
  49. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-security-tickets-issues/README.md +0 -4
  50. campaign_files/2026-10-m-issue-trackers-2/fedora-forge-server-tickets/README.md +0 -8
CHANGELOG.md CHANGED
@@ -3049,3 +3049,19 @@ Changes to the content of this index, oldest first. There is one entry for each
3049
  - hf-training-records: refused
3050
  - npm: refused
3051
  - stackexchange-api-posts: refused
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3049
  - hf-training-records: refused
3050
  - npm: refused
3051
  - stackexchange-api-posts: refused
3052
+
3053
+ ## 2026-11-11: sources held back
3054
+
3055
+ - Each source below keeps its newest version that passed every check; its newer batch waits until it passes them:
3056
+ - 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
3057
+ - 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
3058
+ - cfpb-complaints: refused
3059
+ - 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
3060
+ - 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
3061
+ - 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
3062
+ - 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
3063
+ - 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
3064
+ - 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
3065
+ - hf-training-records: refused
3066
+ - npm: refused
3067
+ - stackexchange-api-posts: refused
README.md CHANGED
@@ -24,25 +24,25 @@ configs:
24
  <!-- artifact-pointer-layout: v2 -->
25
  <!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
26
 
27
- <img class="not-prose" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/banner.svg" alt="Public web, in two layers (task material in collections; corpora), one row per file (address, size, SHA-256, license), your selection, fetched and verified">
28
 
29
  **Agentic Env Index:** find public files to build agent tasks and environments from, and fetch them with one command.
30
 
31
  English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/agentic-env-catalog) · [Usage video](https://huggingface.co/spaces/Battam/agentic-env-catalog#usage-video)
32
 
33
  <picture class="not-prose">
34
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/numbers-narrow-light.svg">
35
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/numbers-wide-light.svg" alt="1,799 material sets with 4,183 units in 14 collections; 139 corpora with 1,216,362,128 rows; 4.45 PB pointed to, as the index holds addresses, not copies; 99.7% of the 37,509 rows compared match their recorded size.">
36
  </picture>
37
  <picture class="not-prose">
38
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/numbers-narrow-dark.svg">
39
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/numbers-wide-dark.svg" alt="1,799 material sets with 4,183 units in 14 collections; 139 corpora with 1,216,362,128 rows; 4.45 PB pointed to, as the index holds addresses, not copies; 99.7% of the 37,509 rows compared match their recorded size.">
40
  </picture>
41
 
42
  ## Get data in one command
43
 
44
  ```sh
45
- uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/tools/fetch.py --form spreadsheets --sample 3 --out ./data
46
  ```
47
 
48
  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.
@@ -52,7 +52,7 @@ the same command takes the same units of this release.
52
  <details>
53
  <summary>What the command takes, and in which order</summary>
54
 
55
- The command and the queries below are pinned to the release tag `release-2026-11-11.6`.
56
  [uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
57
 
58
  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`.
@@ -79,7 +79,7 @@ Choose material sets from the catalog with [DuckDB](https://duckdb.org/):
79
 
80
  ```sql
81
  SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
82
- FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.6/meta/catalog.parquet'
83
  WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
84
  ORDER BY collection, units DESC;
85
  ```
@@ -90,7 +90,7 @@ with `kind = 'corpus'` it returns corpora instead, counted in rows (`files`).
90
  Choose files in one corpus:
91
 
92
  ```sql
93
- SET VARIABLE files = (SELECT list('hf://datasets/Battam/agentic-env-index@release-2026-11-11.6/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.6/meta/catalog.parquet' WHERE source = 'if-archive'));
94
  SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
95
  FROM read_parquet(getvariable('files'))
96
  WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
@@ -112,15 +112,15 @@ A data file may hold the rows of several sources, so the query keeps this one's
112
  ### Task material: units by collection
113
 
114
  <picture class="not-prose">
115
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/material-narrow-light.svg">
116
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/material-wide-light.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 187; Disk images 179; Reproduction packages and runs 105; In no collection 9; SEC filing reviews 0.">
117
  </picture>
118
  <picture class="not-prose">
119
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/material-narrow-dark.svg">
120
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/material-wide-dark.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 187; Disk images 179; Reproduction packages and runs 105; In no collection 9; SEC filing reviews 0.">
121
  </picture>
122
 
123
- 1,799 material sets with 4,183 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
124
 
125
  <details>
126
  <summary>Task material by collection, as a table</summary>
@@ -129,10 +129,10 @@ A data file may hold the rows of several sources, so the query keeps this one's
129
  |---|---:|---:|---:|---:|---:|---:|
130
  | Spreadsheets | 67 | 536 | 670 | 55 | 250 MB | 248 MB |
131
  | Disk images | 52 | 179 | 324 | 40 | 272 MB | 272 MB |
132
- | Reproduction packages and runs | 88 | 105 | 863 | 88 | 118 MB | 118 MB |
133
  | SEC filing reviews | 0 | 0 | 0 | 0 | 0 B | 0 B |
134
- | Solver instances | 63 | 187 | 325 | 60 | 127 MB | 127 MB |
135
- | Browser tests | 123 | 439 | 852 | 88 | 32.1 MB | 32.0 MB |
136
  | Hardware design (EDA) tests | 81 | 258 | 651 | 75 | 80.9 MB | 80.8 MB |
137
  | Issue trackers | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
138
  | Media and documents | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
@@ -150,12 +150,12 @@ Upstreams are the upstream works the material sets of a collection come from.
150
  ### Corpora: rows by main domain
151
 
152
  <picture class="not-prose">
153
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/corpora-narrow-light.svg">
154
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/corpora-wide-light.svg" alt="Corpus rows by main domain, longest bar first: Data science 750,815,212; System administration 185,826,217; Many domains 109,262,742; Software engineering 45,267,701; Science 44,633,675; Operations 39,404,642; Media 12,751,612; Machine learning 9,636,889; Hardware 8,716,520; Unclassified 5,284,162; Security 4,521,631; Misc 241,125.">
155
  </picture>
156
  <picture class="not-prose">
157
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/corpora-narrow-dark.svg">
158
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/corpora-wide-dark.svg" alt="Corpus rows by main domain, longest bar first: Data science 750,815,212; System administration 185,826,217; Many domains 109,262,742; Software engineering 45,267,701; Science 44,633,675; Operations 39,404,642; Media 12,751,612; Machine learning 9,636,889; Hardware 8,716,520; Unclassified 5,284,162; Security 4,521,631; Misc 241,125.">
159
  </picture>
160
 
161
  139 corpora with 1,216,362,128 rows.
@@ -188,12 +188,12 @@ Every material set and every corpus, with its counts, size, license tier and log
188
  ## How it is made
189
 
190
  <picture class="not-prose">
191
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/steps-narrow-light.svg">
192
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/steps-wide-light.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole upstreams into corpora, one row per file or record. 2, admit: works the search found upstream and groups of corpus rows become material sets. 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-11.6.">
193
  </picture>
194
  <picture class="not-prose">
195
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/steps-narrow-dark.svg">
196
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/steps-wide-dark.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole upstreams into corpora, one row per file or record. 2, admit: works the search found upstream and groups of corpus rows become material sets. 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-11.6.">
197
  </picture>
198
 
199
  The terms, each step and how every number is made are folded below.
@@ -247,9 +247,9 @@ only their sizes add up to the size of the whole index.
247
 
248
  | Level | Recorded size | Deduplicated size | Rows read | Rows compared | Rows that match | Rows read, not compared | Rows without a recorded size | Their estimated size |
249
  |---|---:|---:|---:|---:|---:|---:|---:|---:|
250
- | Whole index | 4.45 PB | 4.11 PB | 38,394 | 37,509 | 37,378 (99.7%) | 885: address unreachable 451, file gone 82, login needed 330, no size from the server 19, other error 3 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
251
  | Corpora | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610 (99.6%) | 871: address unreachable 449, file gone 80, login needed 322, no size from the server 19, other error 1 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
252
- | Task material | 2.89 GB | 2.82 GB | 6,800 | 6,786 | 6,768 (99.7%) | 14: address unreachable 2, file gone 2, login needed 8, other error 2 | 0 | none |
253
 
254
  Rows read are the sample of rows the check reads in `meta/sizes.parquet`;
255
  a row compared matched its recorded size or did not, and a row read but not compared never reached its file.
@@ -404,7 +404,7 @@ Every row field and every column of the catalog: [`docs/fields.md`](docs/fields.
404
  | `none_known` | 3 | 0 |
405
  | `present` | 14 | 0 |
406
  | `suspected` | 1 | 0 |
407
- | Not judged yet | 121 | 1,799 |
408
  | Sample files read per judged source | 9 to 30 | none |
409
  | Days the sample files were read | 2026-10-04 and 2026-10-05 | none |
410
 
@@ -415,10 +415,10 @@ Every row field and every column of the catalog: [`docs/fields.md`](docs/fields.
415
 
416
  | Sources | Corpora | Task material |
417
  |---|---:|---:|
418
- | With a recorded size for every row | 92 of 139 | 1,799 of 1,799 |
419
- | With a summary read from sample files | 0 of 139 | 0 of 1,799 |
420
- | With personal information read from sample files | 18 of 139 | 0 of 1,799 |
421
- | Still being collected | 25 of 139 | 0 of 1,799 |
422
 
423
  - Rows whose size the source does not publish are shown as unknown and left out of the size totals, never counted as 0.
424
  - Fields not judged yet say so;
@@ -444,9 +444,9 @@ Every row field and every column of the catalog: [`docs/fields.md`](docs/fields.
444
  <details>
445
  <summary>Releases</summary>
446
 
447
- - Latest release: `release-2026-11-11.6` (its newest CHANGELOG entry is dated 2026-11-11).
448
  - Releases are listed in [CHANGELOG.md](CHANGELOG.md);
449
- each one is a commit with its own release tag (this one is [`release-2026-11-11.6`](https://huggingface.co/datasets/Battam/agentic-env-index/tree/release-2026-11-11.6)),
450
  so any earlier state stays readable at its tag.
451
  - `meta/projection.json` records the release tag and the version of the program and templates that generated this card.
452
  - Croissant metadata: [generated by the Hub](https://huggingface.co/api/datasets/Battam/agentic-env-index/croissant);
@@ -479,7 +479,7 @@ A removal covers the current version of this repository (the main branch) and th
479
  @misc{agentic_env_index,
480
  title = {agentic-env-index: an index of public materials for building agent environments},
481
  howpublished = {https://huggingface.co/datasets/Battam/agentic-env-index},
482
- note = {Release release-2026-11-11.6},
483
  year = {2026}
484
  }
485
  ```
 
24
  <!-- artifact-pointer-layout: v2 -->
25
  <!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
26
 
27
+ <img class="not-prose" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/banner.svg" alt="Public web, in two layers (task material in collections; corpora), one row per file (address, size, SHA-256, license), your selection, fetched and verified">
28
 
29
  **Agentic Env Index:** find public files to build agent tasks and environments from, and fetch them with one command.
30
 
31
  English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/agentic-env-catalog) · [Usage video](https://huggingface.co/spaces/Battam/agentic-env-catalog#usage-video)
32
 
33
  <picture class="not-prose">
34
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/numbers-narrow-light.svg">
35
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/numbers-wide-light.svg" alt="1,800 material sets with 4,184 units in 14 collections; 139 corpora with 1,216,362,128 rows; 4.45 PB pointed to, as the index holds addresses, not copies; 99.6% of the 36,835 rows compared match their recorded size.">
36
  </picture>
37
  <picture class="not-prose">
38
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/numbers-narrow-dark.svg">
39
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/numbers-wide-dark.svg" alt="1,800 material sets with 4,184 units in 14 collections; 139 corpora with 1,216,362,128 rows; 4.45 PB pointed to, as the index holds addresses, not copies; 99.6% of the 36,835 rows compared match their recorded size.">
40
  </picture>
41
 
42
  ## Get data in one command
43
 
44
  ```sh
45
+ uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/tools/fetch.py --form spreadsheets --sample 3 --out ./data
46
  ```
47
 
48
  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.
 
52
  <details>
53
  <summary>What the command takes, and in which order</summary>
54
 
55
+ The command and the queries below are pinned to the release tag `release-2026-11-11.7`.
56
  [uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
57
 
58
  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`.
 
79
 
80
  ```sql
81
  SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
82
+ FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.7/meta/catalog.parquet'
83
  WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
84
  ORDER BY collection, units DESC;
85
  ```
 
90
  Choose files in one corpus:
91
 
92
  ```sql
93
+ SET VARIABLE files = (SELECT list('hf://datasets/Battam/agentic-env-index@release-2026-11-11.7/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.7/meta/catalog.parquet' WHERE source = 'if-archive'));
94
  SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
95
  FROM read_parquet(getvariable('files'))
96
  WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
 
112
  ### Task material: units by collection
113
 
114
  <picture class="not-prose">
115
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/material-narrow-light.svg">
116
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/material-wide-light.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 188; Disk images 179; Reproduction packages and runs 105; In no collection 9; SEC filing reviews 0.">
117
  </picture>
118
  <picture class="not-prose">
119
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/material-narrow-dark.svg">
120
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/material-wide-dark.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 188; Disk images 179; Reproduction packages and runs 105; In no collection 9; SEC filing reviews 0.">
121
  </picture>
122
 
123
+ 1,800 material sets with 4,184 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
124
 
125
  <details>
126
  <summary>Task material by collection, as a table</summary>
 
129
  |---|---:|---:|---:|---:|---:|---:|
130
  | Spreadsheets | 67 | 536 | 670 | 55 | 250 MB | 248 MB |
131
  | Disk images | 52 | 179 | 324 | 40 | 272 MB | 272 MB |
132
+ | Reproduction packages and runs | 88 | 105 | 866 | 88 | 118 MB | 118 MB |
133
  | SEC filing reviews | 0 | 0 | 0 | 0 | 0 B | 0 B |
134
+ | Solver instances | 64 | 188 | 335 | 61 | 127 MB | 127 MB |
135
+ | Browser tests | 123 | 439 | 852 | 88 | 32.0 MB | 32.0 MB |
136
  | Hardware design (EDA) tests | 81 | 258 | 651 | 75 | 80.9 MB | 80.8 MB |
137
  | Issue trackers | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
138
  | Media and documents | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
 
150
  ### Corpora: rows by main domain
151
 
152
  <picture class="not-prose">
153
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/corpora-narrow-light.svg">
154
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/corpora-wide-light.svg" alt="Corpus rows by main domain, longest bar first: Data science 750,815,212; System administration 185,826,217; Many domains 109,262,742; Software engineering 45,267,701; Science 44,633,675; Operations 39,404,642; Media 12,751,612; Machine learning 9,636,889; Hardware 8,716,520; Unclassified 5,284,162; Security 4,521,631; Misc 241,125.">
155
  </picture>
156
  <picture class="not-prose">
157
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/corpora-narrow-dark.svg">
158
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/corpora-wide-dark.svg" alt="Corpus rows by main domain, longest bar first: Data science 750,815,212; System administration 185,826,217; Many domains 109,262,742; Software engineering 45,267,701; Science 44,633,675; Operations 39,404,642; Media 12,751,612; Machine learning 9,636,889; Hardware 8,716,520; Unclassified 5,284,162; Security 4,521,631; Misc 241,125.">
159
  </picture>
160
 
161
  139 corpora with 1,216,362,128 rows.
 
188
  ## How it is made
189
 
190
  <picture class="not-prose">
191
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/steps-narrow-light.svg">
192
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/steps-wide-light.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole upstreams into corpora, one row per file or record. 2, admit: works the search found upstream and groups of corpus rows become material sets. 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-11.7.">
193
  </picture>
194
  <picture class="not-prose">
195
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/steps-narrow-dark.svg">
196
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/steps-wide-dark.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole upstreams into corpora, one row per file or record. 2, admit: works the search found upstream and groups of corpus rows become material sets. 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-11.7.">
197
  </picture>
198
 
199
  The terms, each step and how every number is made are folded below.
 
247
 
248
  | Level | Recorded size | Deduplicated size | Rows read | Rows compared | Rows that match | Rows read, not compared | Rows without a recorded size | Their estimated size |
249
  |---|---:|---:|---:|---:|---:|---:|---:|---:|
250
+ | Whole index | 4.45 PB | 4.11 PB | 37,718 | 36,835 | 36,704 (99.6%) | 883: address unreachable 449, file gone 82, login needed 330, no size from the server 19, other error 3 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
251
  | Corpora | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610 (99.6%) | 871: address unreachable 449, file gone 80, login needed 322, no size from the server 19, other error 1 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
252
+ | Task material | 2.89 GB | 2.82 GB | 6,124 | 6,112 | 6,094 (99.7%) | 12: file gone 2, login needed 8, other error 2 | 0 | none |
253
 
254
  Rows read are the sample of rows the check reads in `meta/sizes.parquet`;
255
  a row compared matched its recorded size or did not, and a row read but not compared never reached its file.
 
404
  | `none_known` | 3 | 0 |
405
  | `present` | 14 | 0 |
406
  | `suspected` | 1 | 0 |
407
+ | Not judged yet | 121 | 1,800 |
408
  | Sample files read per judged source | 9 to 30 | none |
409
  | Days the sample files were read | 2026-10-04 and 2026-10-05 | none |
410
 
 
415
 
416
  | Sources | Corpora | Task material |
417
  |---|---:|---:|
418
+ | With a recorded size for every row | 92 of 139 | 1,800 of 1,800 |
419
+ | With a summary read from sample files | 0 of 139 | 0 of 1,800 |
420
+ | With personal information read from sample files | 18 of 139 | 0 of 1,800 |
421
+ | Still being collected | 25 of 139 | 0 of 1,800 |
422
 
423
  - Rows whose size the source does not publish are shown as unknown and left out of the size totals, never counted as 0.
424
  - Fields not judged yet say so;
 
444
  <details>
445
  <summary>Releases</summary>
446
 
447
+ - Latest release: `release-2026-11-11.7` (its newest CHANGELOG entry is dated 2026-11-11).
448
  - Releases are listed in [CHANGELOG.md](CHANGELOG.md);
449
+ each one is a commit with its own release tag (this one is [`release-2026-11-11.7`](https://huggingface.co/datasets/Battam/agentic-env-index/tree/release-2026-11-11.7)),
450
  so any earlier state stays readable at its tag.
451
  - `meta/projection.json` records the release tag and the version of the program and templates that generated this card.
452
  - Croissant metadata: [generated by the Hub](https://huggingface.co/api/datasets/Battam/agentic-env-index/croissant);
 
479
  @misc{agentic_env_index,
480
  title = {agentic-env-index: an index of public materials for building agent environments},
481
  howpublished = {https://huggingface.co/datasets/Battam/agentic-env-index},
482
+ note = {Release release-2026-11-11.7},
483
  year = {2026}
484
  }
485
  ```
README.zh.md CHANGED
@@ -11,25 +11,25 @@ tags:
11
  ---
12
  <!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
13
 
14
- <img class="not-prose" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/banner.zh.svg" alt="公开网络,分两层(按合集的任务材料;语料库),每个文件一行(地址、大小、SHA-256、许可证),你的选择,下载并校验">
15
 
16
  **Agentic Env Index:**在这里找到可以用来构建智能体任务和环境的公开文件,并用一条命令把它们取下来。
17
 
18
  [English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/agentic-env-catalog) · [使用示例视频](https://huggingface.co/spaces/Battam/agentic-env-catalog#usage-video)
19
 
20
  <picture class="not-prose">
21
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/numbers-narrow-light.zh.svg">
22
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/numbers-wide-light.zh.svg" alt="1,799 个材料集,共 4,183 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 37,509 行中,99.7% 与记录的大小一致。">
23
  </picture>
24
  <picture class="not-prose">
25
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/numbers-narrow-dark.zh.svg">
26
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/numbers-wide-dark.zh.svg" alt="1,799 个材料集,共 4,183 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 37,509 行中,99.7% 与记录的大小一致。">
27
  </picture>
28
 
29
  ## 一条命令取数据
30
 
31
  ```sh
32
- uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/tools/fetch.py --form spreadsheets --sample 3 --out ./data
33
  ```
34
 
35
  这条命令从每个电子表格材料集各取 3 个单元放进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
@@ -39,7 +39,7 @@ uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-
39
  <details>
40
  <summary>命令取什么、按什么顺序取</summary>
41
 
42
- 这条命令和下面的查询都固定在发布标签 `release-2026-11-11.6` 上。
43
  [uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
44
 
45
  命令返回单元:形式为 `spreadsheets` 的每个材料集各 3 个单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
@@ -66,7 +66,7 @@ uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-
66
 
67
  ```sql
68
  SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
69
- FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.6/meta/catalog.parquet'
70
  WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
71
  ORDER BY collection, units DESC;
72
  ```
@@ -77,7 +77,7 @@ ORDER BY collection, units DESC;
77
  在一个语料库里挑选文件:
78
 
79
  ```sql
80
- SET VARIABLE files = (SELECT list('hf://datasets/Battam/agentic-env-index@release-2026-11-11.6/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.6/meta/catalog.parquet' WHERE source = 'if-archive'));
81
  SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
82
  FROM read_parquet(getvariable('files'))
83
  WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
@@ -99,15 +99,15 @@ ORDER BY size_bytes LIMIT 20;
99
  ### 任务材料:按合集的单元数
100
 
101
  <picture class="not-prose">
102
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/material-narrow-light.zh.svg">
103
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/material-wide-light.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 187;磁盘镜像 179;复现包和运行 105;不属于任何合集 9;SEC 申报审查 0。">
104
  </picture>
105
  <picture class="not-prose">
106
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/material-narrow-dark.zh.svg">
107
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/material-wide-dark.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 187;磁盘镜像 179;复现包和运行 105;不属于任何合集 9;SEC 申报审查 0。">
108
  </picture>
109
 
110
- 1,799 个材料集,共 4,183 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
111
 
112
  <details>
113
  <summary>按合集的任务材料(表格)</summary>
@@ -116,10 +116,10 @@ ORDER BY size_bytes LIMIT 20;
116
  |---|---:|---:|---:|---:|---:|---:|
117
  | 电子表格 | 67 | 536 | 670 | 55 | 250 MB | 248 MB |
118
  | 磁盘镜像 | 52 | 179 | 324 | 40 | 272 MB | 272 MB |
119
- | 复现包和运行 | 88 | 105 | 863 | 88 | 118 MB | 118 MB |
120
  | SEC 申报审查 | 0 | 0 | 0 | 0 | 0 B | 0 B |
121
- | 求解器实例 | 63 | 187 | 325 | 60 | 127 MB | 127 MB |
122
- | 浏览器测试 | 123 | 439 | 852 | 88 | 32.1 MB | 32.0 MB |
123
  | 硬件设计(EDA)测试 | 81 | 258 | 651 | 75 | 80.9 MB | 80.8 MB |
124
  | 问题跟踪系统 | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
125
  | 媒体和文档 | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
@@ -137,12 +137,12 @@ ORDER BY size_bytes LIMIT 20;
137
  ### 语料库:按主要领域的行数
138
 
139
  <picture class="not-prose">
140
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/corpora-narrow-light.zh.svg">
141
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/corpora-wide-light.zh.svg" alt="按主要领域的语料库行数,条形由长到短:数据科学 750,815,212;系统管理 185,826,217;多领域 109,262,742;软件工程 45,267,701;科学 44,633,675;运营 39,404,642;媒体 12,751,612;机器学习 9,636,889;硬件 8,716,520;未分类 5,284,162;安全 4,521,631;杂项 241,125。">
142
  </picture>
143
  <picture class="not-prose">
144
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/corpora-narrow-dark.zh.svg">
145
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/corpora-wide-dark.zh.svg" alt="按主要领域的语料库行数,条形由长到短:数据科学 750,815,212;系统管理 185,826,217;多领域 109,262,742;软件工程 45,267,701;科学 44,633,675;运营 39,404,642;媒体 12,751,612;机器学习 9,636,889;硬件 8,716,520;未分类 5,284,162;安全 4,521,631;杂项 241,125。">
146
  </picture>
147
 
148
  139 个语料库,共 1,216,362,128 行。
@@ -175,12 +175,12 @@ ORDER BY size_bytes LIMIT 20;
175
  ## 怎样做成
176
 
177
  <picture class="not-prose">
178
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/steps-narrow-light.zh.svg">
179
- <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.6。">
180
  </picture>
181
  <picture class="not-prose">
182
- <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/steps-narrow-dark.zh.svg">
183
- <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.6/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.6。">
184
  </picture>
185
 
186
  术语、每一步,以及每个数字怎样得出,都折叠在下面。
@@ -234,9 +234,9 @@ ORDER BY size_bytes LIMIT 20;
234
 
235
  | 层级 | 记录的大小 | 去重后大小 | 读过的行 | 比对过的行 | 一致的行 | 读过但未比对的行 | 没有记录大小的行 | 这些行的估计大小 |
236
  |---|---:|---:|---:|---:|---:|---:|---:|---:|
237
- | 整个索引 | 4.45 PB | 4.11 PB | 38,394 | 37,509 | 37,378(99.7%) | 885:地址无法访问 451 行、文件已不存在 82 行、需要登录 330 行、服务器未给出大小 19 行、其他错误 3 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
238
  | 语料库 | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610(99.6%) | 871:地址无法访问 449 行、文件已不存在 80 行、需要登录 322 行、服务器未给出大小 19 行、其他错误 1 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
239
- | 任务材料 | 2.89 GB | 2.82 GB | 6,800 | 6,786 | 6,768(99.7%) | 14:地址无法访问 2 行、文件已不存在 2 行、需要登录 8 行、其他错误 2 行 | 0 | 无 |
240
 
241
  读过的行是核对在 `meta/sizes.parquet` 中读取的抽样行;
242
  比对过的行与记录的大小一致或不一致,读过但未比对的行没有取到它的文件。
@@ -393,7 +393,7 @@ ORDER BY size_bytes LIMIT 20;
393
  | `none_known` | 3 | 0 |
394
  | `present` | 14 | 0 |
395
  | `suspected` | 1 | 0 |
396
- | 尚未判读 | 121 | 1,799 |
397
  | 每个已判读的来源读过的样本文件数 | 9 到 30 | 无 |
398
  | 读取样本文件的日期 | 2026-10-04 和 2026-10-05 | 无 |
399
 
@@ -404,10 +404,10 @@ ORDER BY size_bytes LIMIT 20;
404
 
405
  | 来源 | 语料库 | 任务材料 |
406
  |---|---:|---:|
407
- | 每一行都有记录的大小 | 139 个中的 92 个 | 1,799 个中的 1,799 个 |
408
- | 已从样本文件读出摘要 | 139 个中的 0 个 | 1,799 个中的 0 个 |
409
- | 已从样本文件读出个人信息 | 139 个中的 18 个 | 1,799 个中的 0 个 |
410
- | 仍在采集中 | 139 个中的 25 个 | 1,799 个中的 0 个 |
411
 
412
  - 来源没有公布大小的行显示为未知,不计入大小合计,也从不按 0 计。
413
  - 尚未判读的字段会注明;
@@ -433,9 +433,9 @@ ORDER BY size_bytes LIMIT 20;
433
  <details>
434
  <summary>发布</summary>
435
 
436
- - 最新发布:`release-2026-11-11.6`(其最新的 CHANGELOG 条目日期为 2026-11-11)。
437
  - 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
438
- 每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.6`](https://huggingface.co/datasets/Battam/agentic-env-index/tree/release-2026-11-11.6)),
439
  因此任何较早的状态都可以在它的标签处读到。
440
  - `meta/projection.json` 记录发布标签,以及生成本卡片的���序和模板的版本。
441
  - Croissant 元数据:[由 Hub 生成](https://huggingface.co/api/datasets/Battam/agentic-env-index/croissant);
@@ -476,7 +476,7 @@ ORDER BY size_bytes LIMIT 20;
476
  @misc{agentic_env_index,
477
  title = {agentic-env-index: an index of public materials for building agent environments},
478
  howpublished = {https://huggingface.co/datasets/Battam/agentic-env-index},
479
- note = {Release release-2026-11-11.6},
480
  year = {2026}
481
  }
482
  ```
 
11
  ---
12
  <!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
13
 
14
+ <img class="not-prose" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/banner.zh.svg" alt="公开网络,分两层(按合集的任务材料;语料库),每个文件一行(地址、大小、SHA-256、许可证),你的选择,下载并校验">
15
 
16
  **Agentic Env Index:**在这里找到可以用来构建智能体任务和环境的公开文件,并用一条命令把它们取下来。
17
 
18
  [English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/agentic-env-catalog) · [使用示例视频](https://huggingface.co/spaces/Battam/agentic-env-catalog#usage-video)
19
 
20
  <picture class="not-prose">
21
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/numbers-narrow-light.zh.svg">
22
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/numbers-wide-light.zh.svg" alt="1,800 个材料集,共 4,184 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 36,835 行中,99.6% 与记录的大小一致。">
23
  </picture>
24
  <picture class="not-prose">
25
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/numbers-narrow-dark.zh.svg">
26
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/numbers-wide-dark.zh.svg" alt="1,800 个材料集,共 4,184 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 36,835 行中,99.6% 与记录的大小一致。">
27
  </picture>
28
 
29
  ## 一条命令取数据
30
 
31
  ```sh
32
+ uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/tools/fetch.py --form spreadsheets --sample 3 --out ./data
33
  ```
34
 
35
  这条命令从每个电子表格材料集各取 3 个单元放进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
 
39
  <details>
40
  <summary>命令取什么、按什么顺序取</summary>
41
 
42
+ 这条命令和下面的查询都固定在发布标签 `release-2026-11-11.7` 上。
43
  [uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
44
 
45
  命令返回单元:形式为 `spreadsheets` 的每个材料集各 3 个单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
 
66
 
67
  ```sql
68
  SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
69
+ FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.7/meta/catalog.parquet'
70
  WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
71
  ORDER BY collection, units DESC;
72
  ```
 
77
  在一个语料库里挑选文件:
78
 
79
  ```sql
80
+ SET VARIABLE files = (SELECT list('hf://datasets/Battam/agentic-env-index@release-2026-11-11.7/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.7/meta/catalog.parquet' WHERE source = 'if-archive'));
81
  SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
82
  FROM read_parquet(getvariable('files'))
83
  WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
 
99
  ### 任务材料:按合集的单元数
100
 
101
  <picture class="not-prose">
102
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/material-narrow-light.zh.svg">
103
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/material-wide-light.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 188;磁盘镜像 179;复现包和运行 105;不属于任何合集 9;SEC 申报审查 0。">
104
  </picture>
105
  <picture class="not-prose">
106
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/material-narrow-dark.zh.svg">
107
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/material-wide-dark.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 188;磁盘镜像 179;复现包和运行 105;不属于任何合集 9;SEC 申报审查 0。">
108
  </picture>
109
 
110
+ 1,800 个材料集,共 4,184 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
111
 
112
  <details>
113
  <summary>按合集的任务材料(表格)</summary>
 
116
  |---|---:|---:|---:|---:|---:|---:|
117
  | 电子表格 | 67 | 536 | 670 | 55 | 250 MB | 248 MB |
118
  | 磁盘镜像 | 52 | 179 | 324 | 40 | 272 MB | 272 MB |
119
+ | 复现包和运行 | 88 | 105 | 866 | 88 | 118 MB | 118 MB |
120
  | SEC 申报审查 | 0 | 0 | 0 | 0 | 0 B | 0 B |
121
+ | 求解器实例 | 64 | 188 | 335 | 61 | 127 MB | 127 MB |
122
+ | 浏览器测试 | 123 | 439 | 852 | 88 | 32.0 MB | 32.0 MB |
123
  | 硬件设计(EDA)测试 | 81 | 258 | 651 | 75 | 80.9 MB | 80.8 MB |
124
  | 问题跟踪系统 | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
125
  | 媒体和文档 | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
 
137
  ### 语料库:按主要领域的行数
138
 
139
  <picture class="not-prose">
140
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/corpora-narrow-light.zh.svg">
141
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/corpora-wide-light.zh.svg" alt="按主要领域的语料库行数,条形由长到短:数据科学 750,815,212;系统管理 185,826,217;多领域 109,262,742;软件工程 45,267,701;科学 44,633,675;运营 39,404,642;媒体 12,751,612;机器学习 9,636,889;硬件 8,716,520;未分类 5,284,162;安全 4,521,631;杂项 241,125。">
142
  </picture>
143
  <picture class="not-prose">
144
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/corpora-narrow-dark.zh.svg">
145
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/corpora-wide-dark.zh.svg" alt="按主要领域的语料库行数,条形由长到短:数据科学 750,815,212;系统管理 185,826,217;多领域 109,262,742;软件工程 45,267,701;科学 44,633,675;运营 39,404,642;媒体 12,751,612;机器学习 9,636,889;硬件 8,716,520;未分类 5,284,162;安全 4,521,631;杂项 241,125。">
146
  </picture>
147
 
148
  139 个语料库,共 1,216,362,128 行。
 
175
  ## 怎样做成
176
 
177
  <picture class="not-prose">
178
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/steps-narrow-light.zh.svg">
179
+ <img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.7。">
180
  </picture>
181
  <picture class="not-prose">
182
+ <source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/steps-narrow-dark.zh.svg">
183
+ <img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.7/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.7。">
184
  </picture>
185
 
186
  术语、每一步,以及每个数字怎样得出,都折叠在下面。
 
234
 
235
  | 层级 | 记录的大小 | 去重后大小 | 读过的行 | 比对过的行 | 一致的行 | 读过但未比对的行 | 没有记录大小的行 | 这些行的估计大小 |
236
  |---|---:|---:|---:|---:|---:|---:|---:|---:|
237
+ | 整个索引 | 4.45 PB | 4.11 PB | 37,718 | 36,835 | 36,704(99.6%) | 883:地址无法访问 449 行、文件已不存在 82 行、需要登录 330 行、服务器未给出大小 19 行、其他错误 3 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
238
  | 语料库 | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610(99.6%) | 871:地址无法访问 449 行、文件已不存在 80 行、需要登录 322 行、服务器未给出大小 19 行、其他错误 1 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
239
+ | 任务材料 | 2.89 GB | 2.82 GB | 6,124 | 6,112 | 6,094(99.7%) | 12:文件已不存在 2 行、需要登录 8 行、其他错误 2 行 | 0 | 无 |
240
 
241
  读过的行是核对在 `meta/sizes.parquet` 中读取的抽样行;
242
  比对过的行与记录的大小一致或不一致,读过但未比对的行没有取到它的文件。
 
393
  | `none_known` | 3 | 0 |
394
  | `present` | 14 | 0 |
395
  | `suspected` | 1 | 0 |
396
+ | 尚未判读 | 121 | 1,800 |
397
  | 每个已判读的来源读过的样本文件数 | 9 到 30 | 无 |
398
  | 读取样本文件的日期 | 2026-10-04 和 2026-10-05 | 无 |
399
 
 
404
 
405
  | 来源 | 语料库 | 任务材料 |
406
  |---|---:|---:|
407
+ | 每一行都有记录的大小 | 139 个中的 92 个 | 1,800 个中的 1,800 个 |
408
+ | 已从样本文件读出摘要 | 139 个中的 0 个 | 1,800 个中的 0 个 |
409
+ | 已从样本文件读出个人信息 | 139 个中的 18 个 | 1,800 个中的 0 个 |
410
+ | 仍在采集中 | 139 个中的 25 个 | 1,800 个中的 0 个 |
411
 
412
  - 来源没有公布大小的行显示为未知,不计入大小合计,也从不按 0 计。
413
  - 尚未判读的字段会注明;
 
433
  <details>
434
  <summary>发布</summary>
435
 
436
+ - 最新发布:`release-2026-11-11.7`(其最新的 CHANGELOG 条目日期为 2026-11-11)。
437
  - 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
438
+ 每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.7`](https://huggingface.co/datasets/Battam/agentic-env-index/tree/release-2026-11-11.7)),
439
  因此任何较早的状态都可以在它的标签处读到。
440
  - `meta/projection.json` 记录发布标签,以及生成本卡片的���序和模板的版本。
441
  - Croissant 元数据:[由 Hub 生成](https://huggingface.co/api/datasets/Battam/agentic-env-index/croissant);
 
476
  @misc{agentic_env_index,
477
  title = {agentic-env-index: an index of public materials for building agent environments},
478
  howpublished = {https://huggingface.co/datasets/Battam/agentic-env-index},
479
+ note = {Release release-2026-11-11.7},
480
  year = {2026}
481
  }
482
  ```
campaign_files/2026-10-a-spreadsheets-with-answers-2/genesys-mod-data-source-workbooks/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-a-spreadsheets-with-answers-2/gflohr-e-invoice-eu/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:** LibreOffice headless (soffice --headless --convert-to xlsx, recalculates on load) then openpyxl; or read content.xml directly (table:formula and office:value) with a zip and XML library such as odfpy
14
 
15
  **Licence (SPDX):** WTFPL
 
8
 
9
  **Self-contained:** Each file is self-contained.
10
 
 
 
11
  **Tools to open and check:** LibreOffice headless (soffice --headless --convert-to xlsx, recalculates on load) then openpyxl; or read content.xml directly (table:formula and office:value) with a zip and XML library such as odfpy
12
 
13
  **Licence (SPDX):** WTFPL
campaign_files/2026-10-b-disk-images-2/exfatprogs-fsck-cases/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each unit needs other upstream files is not stated.
10
 
11
- **Answers:** Each unit has one answer file, at answer/<unit path>.json (the unit path plus .json). Reference result kind: corruption_desc.
12
-
13
  **Tools to open and check:** Open with tools for these file types: .img.
14
 
15
  **Licence (SPDX):** GPL-2.0-only
@@ -20,46 +18,31 @@ Units:
20
 
21
  - `cases/bad_bitmap/exfat.img`: Exfatprogs fsck test image: bad_bitmap.
22
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_bitmap/exfat.img.tar.xz
23
- Reference result: corruption_desc
24
  - `cases/bad_dentries/exfat.img`: Exfatprogs fsck test image: bad_dentries.
25
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_dentries/exfat.img.tar.xz
26
- Reference result: corruption_desc
27
  - `cases/bad_file_size/exfat.img`: Exfatprogs fsck test image: bad_file_size.
28
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_file_size/exfat.img.tar.xz
29
- Reference result: corruption_desc
30
  - `cases/bad_first_clu/exfat.img`: Exfatprogs fsck test image: bad_first_clu.
31
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_first_clu/exfat.img.tar.xz
32
- Reference result: corruption_desc
33
  - `cases/bad_num_chain/exfat.img`: Exfatprogs fsck test image: bad_num_chain.
34
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_num_chain/exfat.img.tar.xz
35
- Reference result: corruption_desc
36
  - `cases/bad_root/exfat.img`: Exfatprogs fsck test image: bad_root.
37
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_root/exfat.img.tar.xz
38
- Reference result: corruption_desc
39
  - `cases/bs_bad_csum/exfat.img`: Exfatprogs fsck test image: bs_bad_csum.
40
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bs_bad_csum/exfat.img.tar.xz
41
- Reference result: corruption_desc
42
  - `cases/de_bad_csum/exfat.img`: Exfatprogs fsck test image: de_bad_csum.
43
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/de_bad_csum/exfat.img.tar.xz
44
- Reference result: corruption_desc
45
  - `cases/duplicate_clu/exfat.img`: Exfatprogs fsck test image: duplicate_clu.
46
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/duplicate_clu/exfat.img.tar.xz
47
- Reference result: corruption_desc
48
  - `cases/duplicated_name/exfat.img`: Exfatprogs fsck test image: duplicated_name.
49
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/duplicated_name/exfat.img.tar.xz
50
- Reference result: corruption_desc
51
  - `cases/file_invalid_clus/exfat.img`: Exfatprogs fsck test image: file_invalid_clus.
52
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/file_invalid_clus/exfat.img.tar.xz
53
- Reference result: corruption_desc
54
  - `cases/invalid_name/exfat.img`: Exfatprogs fsck test image: invalid_name.
55
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/invalid_name/exfat.img.tar.xz
56
- Reference result: corruption_desc
57
  - `cases/loop_chain/exfat.img`: Exfatprogs fsck test image: loop_chain.
58
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/loop_chain/exfat.img.tar.xz
59
- Reference result: corruption_desc
60
  - `cases/unused-dentries/exfat.img`: Exfatprogs fsck test image: unused-dentries.
61
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/unused-dentries/exfat.img.tar.xz
62
- Reference result: corruption_desc
63
  - `cases/bad_bitmap_size/exfat.img`: Exfatprogs fsck test image: bad_bitmap_size.
64
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_bitmap_size/exfat.img.tar.xz
65
- Reference result: corruption_desc
 
8
 
9
  **Self-contained:** Whether each unit needs other upstream files is not stated.
10
 
 
 
11
  **Tools to open and check:** Open with tools for these file types: .img.
12
 
13
  **Licence (SPDX):** GPL-2.0-only
 
18
 
19
  - `cases/bad_bitmap/exfat.img`: Exfatprogs fsck test image: bad_bitmap.
20
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_bitmap/exfat.img.tar.xz
 
21
  - `cases/bad_dentries/exfat.img`: Exfatprogs fsck test image: bad_dentries.
22
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_dentries/exfat.img.tar.xz
 
23
  - `cases/bad_file_size/exfat.img`: Exfatprogs fsck test image: bad_file_size.
24
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_file_size/exfat.img.tar.xz
 
25
  - `cases/bad_first_clu/exfat.img`: Exfatprogs fsck test image: bad_first_clu.
26
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_first_clu/exfat.img.tar.xz
 
27
  - `cases/bad_num_chain/exfat.img`: Exfatprogs fsck test image: bad_num_chain.
28
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_num_chain/exfat.img.tar.xz
 
29
  - `cases/bad_root/exfat.img`: Exfatprogs fsck test image: bad_root.
30
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_root/exfat.img.tar.xz
 
31
  - `cases/bs_bad_csum/exfat.img`: Exfatprogs fsck test image: bs_bad_csum.
32
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bs_bad_csum/exfat.img.tar.xz
 
33
  - `cases/de_bad_csum/exfat.img`: Exfatprogs fsck test image: de_bad_csum.
34
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/de_bad_csum/exfat.img.tar.xz
 
35
  - `cases/duplicate_clu/exfat.img`: Exfatprogs fsck test image: duplicate_clu.
36
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/duplicate_clu/exfat.img.tar.xz
 
37
  - `cases/duplicated_name/exfat.img`: Exfatprogs fsck test image: duplicated_name.
38
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/duplicated_name/exfat.img.tar.xz
 
39
  - `cases/file_invalid_clus/exfat.img`: Exfatprogs fsck test image: file_invalid_clus.
40
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/file_invalid_clus/exfat.img.tar.xz
 
41
  - `cases/invalid_name/exfat.img`: Exfatprogs fsck test image: invalid_name.
42
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/invalid_name/exfat.img.tar.xz
 
43
  - `cases/loop_chain/exfat.img`: Exfatprogs fsck test image: loop_chain.
44
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/loop_chain/exfat.img.tar.xz
 
45
  - `cases/unused-dentries/exfat.img`: Exfatprogs fsck test image: unused-dentries.
46
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/unused-dentries/exfat.img.tar.xz
 
47
  - `cases/bad_bitmap_size/exfat.img`: Exfatprogs fsck test image: bad_bitmap_size.
48
  Read out of the archive: https://raw.githubusercontent.com/exfatprogs/exfatprogs/8b427483164888f0a5af5e4ba92da4981f1094e2/tests/bad_bitmap_size/exfat.img.tar.xz
 
campaign_files/2026-10-b-disk-images-2/fatcat-fat-images/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated.
10
 
11
- **Answers:** Each file has one answer file, at answer/<unit path>.json (the unit path plus .json). Reference result kind: deleted_files; corruption_desc.
12
-
13
  **Tools to open and check:** Open with tools for these file types: .gz.
14
 
15
  **Licence (SPDX):** MIT
@@ -19,16 +17,9 @@
19
  Files:
20
 
21
  - `cases/deleted/deleted.img.gz`: Fatcat example FAT32 image with a deleted directory and file: deleted.img.
22
- Reference result: deleted_files
23
  - `cases/directory-loop/directory-loop.img.gz`: Fatcat example FAT32 image with looping directories: directory-loop.img.
24
- Reference result: corruption_desc
25
  - `cases/infinite-file/infinite-file.img.gz`: Fatcat example FAT32 image with a looping file of maximum size: infinite-file.img.
26
- Reference result: corruption_desc
27
  - `cases/full-fat/full-fat.img.gz`: Fatcat example FAT32 image whose FAT is full while no file is visible: full-fat.img.
28
- Reference result: corruption_desc
29
  - `cases/two-file-same-cluster/two-file-same-cluster.img.gz`: Fatcat example FAT32 image with two files sharing one cluster: two-file-same-cluster.img.
30
- Reference result: corruption_desc
31
  - `cases/fake-big-disk-1T/fake-big-disk-1T.img.gz`: Fatcat example FAT32 image whose boot sector claims about 1 TB: fake-big-disk-1T.img.
32
- Reference result: corruption_desc
33
  - `cases/repair/repair.img.gz`: Fatcat repair practice FAT32 image: repair.img.
34
- Reference result: corruption_desc
 
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated.
10
 
 
 
11
  **Tools to open and check:** Open with tools for these file types: .gz.
12
 
13
  **Licence (SPDX):** MIT
 
17
  Files:
18
 
19
  - `cases/deleted/deleted.img.gz`: Fatcat example FAT32 image with a deleted directory and file: deleted.img.
 
20
  - `cases/directory-loop/directory-loop.img.gz`: Fatcat example FAT32 image with looping directories: directory-loop.img.
 
21
  - `cases/infinite-file/infinite-file.img.gz`: Fatcat example FAT32 image with a looping file of maximum size: infinite-file.img.
 
22
  - `cases/full-fat/full-fat.img.gz`: Fatcat example FAT32 image whose FAT is full while no file is visible: full-fat.img.
 
23
  - `cases/two-file-same-cluster/two-file-same-cluster.img.gz`: Fatcat example FAT32 image with two files sharing one cluster: two-file-same-cluster.img.
 
24
  - `cases/fake-big-disk-1T/fake-big-disk-1T.img.gz`: Fatcat example FAT32 image whose boot sector claims about 1 TB: fake-big-disk-1T.img.
 
25
  - `cases/repair/repair.img.gz`: Fatcat repair practice FAT32 image: repair.img.
 
campaign_files/2026-10-c-repros-2/feynman-repro/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the unit needs other upstream files is not stated. 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: .hs.
14
 
15
  **Licence (SPDX):** BSD-3-Clause
 
8
 
9
  **Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** Open with tools for these file types: .hs.
12
 
13
  **Licence (SPDX):** BSD-3-Clause
campaign_files/2026-10-c-repros-2/gdpnum-repro/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether the unit needs other upstream files is not stated. 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: .py.
14
 
15
  **Licence (SPDX):** MIT
 
8
 
9
  **Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
10
 
 
 
11
  **Tools to open and check:** Open with tools for these file types: .py.
12
 
13
  **Licence (SPDX):** MIT
campaign_files/2026-10-c-repros-2/gidney-ekera-2019-repro/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each unit needs other upstream files is not stated. 2 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: .py; .txt; .md.
14
 
15
  **Licence (SPDX):** Apache-2.0
 
8
 
9
  **Self-contained:** Whether each unit needs other upstream files is not stated. 2 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: .py; .txt; .md.
12
 
13
  **Licence (SPDX):** Apache-2.0
campaign_files/2026-10-c-repros/fact-ai-dawlau-repro/LICENSE.txt ADDED
@@ -0,0 +1,7 @@
 
 
 
 
 
 
 
 
1
+ Licence: MIT AND GPL-3.0-only
2
+
3
+ - MIT: https://raw.githubusercontent.com/Dawlau/FACT-AI/9d757e75c85706c728081234336d4880f3522e2d/LICENSE (publisher: Pantea, Luca and Blahovici, Andrei (GitHub Dawlau/FACT-AI))
4
+ - GPL-3.0-only: https://raw.githubusercontent.com/Dawlau/FACT-AI/9d757e75c85706c728081234336d4880f3522e2d/Crosswalk/deepwalk/LICENSE (publisher: Pantea, Luca and Blahovici, Andrei (GitHub Dawlau/FACT-AI))
5
+ - MIT: https://raw.githubusercontent.com/Dawlau/FACT-AI/9d757e75c85706c728081234336d4880f3522e2d/LICENSE (publisher: Luca Pantea, Andrei Blahovici (GitHub Dawlau/FACT-AI); synthetic graph from the CrossWalk authors' code)
6
+
7
+ The publisher's licence file is LICENSE next to this file, fetched from https://raw.githubusercontent.com/Dawlau/FACT-AI/9d757e75c85706c728081234336d4880f3522e2d/LICENSE.
campaign_files/2026-10-c-repros/fact-ai-dawlau-repro/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
11
- **Answers:** answer/crosswalk-synth2-infmax-original-code/reported.json gives the values the paper reports for this experiment (reported, tolerance per key, table or figure number, page, how the value was read).
12
-
13
  **Tools to open and check:** Python 3.7 with gensim 3.8.3, networkx 2.5, scikit-learn-extra 0.2.0 (k-medoids); exact pins are in the package README.md.
14
 
15
  **Licence (SPDX):** MIT AND GPL-3.0-only
 
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
 
 
11
  **Tools to open and check:** Python 3.7 with gensim 3.8.3, networkx 2.5, scikit-learn-extra 0.2.0 (k-medoids); exact pins are in the package README.md.
12
 
13
  **Licence (SPDX):** MIT AND GPL-3.0-only
campaign_files/2026-10-c-repros/fact-ai-imandrealombardo-repro/LICENSE.txt ADDED
@@ -0,0 +1,6 @@
 
 
 
 
 
 
 
1
+ Licence: MIT AND CC-BY-4.0
2
+
3
+ - MIT: https://raw.githubusercontent.com/imandrealombardo/FACT-AI/868c34cafe45ded436646f9db00335f1527a1e35/LICENSE (publisher: Tafuro, Matteo and Lombardo, Andrea and Veljković, Tin Hadži and Becker-Czarnetzki, Lasse (GitHub imandrealombardo/FACT-AI))
4
+ - CC-BY-4.0 AND MIT: https://creativecommons.org/licenses/by/4.0/ (publisher: Hans Hofmann (UCI Machine Learning Repository, Statlog German Credit); preprocessed by Tafuro, Lombardo, Veljkovic, Becker-Czarnetzki (GitHub imandrealombardo/FACT-AI))
5
+
6
+ The publisher's licence file is LICENSE next to this file, fetched from https://raw.githubusercontent.com/imandrealombardo/FACT-AI/868c34cafe45ded436646f9db00335f1527a1e35/LICENSE.
campaign_files/2026-10-c-repros/fact-ai-imandrealombardo-repro/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
11
- **Answers:** answer/mehrabi2020-german-nraa-svm/reported.json gives the values the paper reports for this experiment (reported, tolerance per key, table or figure number, page, how the value was read).
12
-
13
  **Tools to open and check:** Python 3.9 with TensorFlow 2.6.2 (CPU), scikit-learn 1.0.2, cvxpy 1.1.18; exact pins are in the package README.md.
14
 
15
  **Licence (SPDX):** MIT AND CC-BY-4.0
 
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
 
 
11
  **Tools to open and check:** Python 3.9 with TensorFlow 2.6.2 (CPU), scikit-learn 1.0.2, cvxpy 1.1.18; exact pins are in the package README.md.
12
 
13
  **Licence (SPDX):** MIT AND CC-BY-4.0
campaign_files/2026-10-c-repros/fairness-attacks-repro/LICENSE.txt ADDED
@@ -0,0 +1,6 @@
 
 
 
 
 
 
 
1
+ Licence: MIT AND CC-BY-4.0
2
+
3
+ - MIT: https://raw.githubusercontent.com/toliz/fairness-attacks/84b0f5653f70067c141d425c5bc3a5fba8f6ead6/LICENSE (publisher: Nalmpantis, Angelos and Panagiotopoulos, Apostolos and Gkountouras, John and Papakostas, Konstantinos (GitHub toliz/fairness-attacks))
4
+ - CC-BY-4.0 AND MIT: https://creativecommons.org/licenses/by/4.0/ (publisher: Hans Hofmann (UCI Machine Learning Repository, Statlog German Credit); preprocessed into npz by Mehrabi et al. (GitHub Ninarehm/attack))
5
+
6
+ The publisher's licence file is LICENSE next to this file, fetched from https://raw.githubusercontent.com/toliz/fairness-attacks/84b0f5653f70067c141d425c5bc3a5fba8f6ead6/LICENSE.
campaign_files/2026-10-c-repros/fairness-attacks-repro/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
11
- **Answers:** answer/mehrabi2020-german-nraa/reported.json gives the values the paper reports for this experiment (reported, tolerance per key, table or figure number, page, how the value was read).
12
-
13
  **Tools to open and check:** Python 3.7 with PyTorch 1.10 (CPU), pytorch-lightning 1.5.8, torchmetrics 0.6.2, cvxpy 1.1.18; exact pins are in the package README.md.
14
 
15
  **Licence (SPDX):** MIT AND CC-BY-4.0
 
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
 
 
11
  **Tools to open and check:** Python 3.7 with PyTorch 1.10 (CPU), pytorch-lightning 1.5.8, torchmetrics 0.6.2, cvxpy 1.1.18; exact pins are in the package README.md.
12
 
13
  **Licence (SPDX):** MIT AND CC-BY-4.0
campaign_files/2026-10-g-solver-instances-2/francoisggg-suguru/LICENSE ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ Licence: NOASSERTION
2
+
3
+ - NOASSERTION: https://github.com/FrancoisGgg/suguru-generator/blob/3fe88e622de9cf80efe5e4aea8b8ea1bf6d6d0f7/generator.py (publisher: FrancoisGgg)
campaign_files/2026-10-g-solver-instances-2/francoisggg-suguru/README.md ADDED
@@ -0,0 +1,23 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # francoisggg-suguru
2
+
3
+ **What this is:** 1 unit (8 files) published by FrancoisGgg. Collection theme: Seeded puzzle generators (Simon Tatham puzzle collection class, with generation command, seed and solution).
4
+
5
+ **What one unit is:** Each unit is a few named upstream files, delivered together, kept at its upstream path. Format: JSONL of generated puzzles with solutions, plus a generation record.
6
+
7
+ **Where it comes from:** Upstream: FrancoisGgg/suguru-generator. Kind: generated data.
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. Dependencies named upstream are listed per unit in the notes.
10
+
11
+ **Tools to open and check:** Check: Unique solution: exact match of the grid; equivalently the upstream Grid.is_complete and Grid.is_valid (models.py lines 186-214: no duplicate in a group, no equal values in touching cells including diagonals) plus each group of size k holding values 1 to k. Wrong-answer controls must fail.
12
+
13
+ **Licence (SPDX):** NOASSERTION
14
+
15
+ **Provenance:** https://github.com/FrancoisGgg/suguru-generator
16
+
17
+ Units:
18
+
19
+ - `generated/` (8 files): FrancoisGgg/suguru-generator: seeded Suguru (Tectonic) generator with uniqueness-checked clue removal and difficulty rating.
20
+ Format: JSONL of generated puzzles with solutions, plus a generation record
21
+ Check: Unique solution: exact match of the grid; equivalently the upstream Grid.is_complete and Grid.is_valid (models.py lines 186-214: no duplicate in a group, no equal values in touching cells including diagonals) plus each group of size k holding values 1 to k. Wrong-answer controls must fail.
22
+ Companions (not included): group_generator.py; solver.py; models.py; serializer.py; difficulty.py; helper.py; main.py
23
+ Dependencies: Python 3 standard library for generator, solver, models, serializer, difficulty (version recorded); FrancoisGgg/suguru-generator at git commit 3fe88e62; not packed
campaign_files/2026-10-gt-browser-tests-2/firefox-autoconfig-tests/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_preference_values. 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:** write defaults/pref/autoconfig.js and autoconfig.cfg into the Firefox install directory with a text editor or script (the documented enterprise AutoConfig route); start Firefox headless (`firefox --headless -profile DIR`) and read the prefs back from prefs.js or through a Marionette session
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `extensions/pref/autoconfig/test/unit/autoconfig-all.cfg`: Firefox AutoConfig: write an autoconfig.cfg that sets, defaults, locks, unlocks, clears and derives eleven preferences.
22
  Format: Mozilla AutoConfig file (.cfg, JavaScript subset with pref, defaultPref, lockPref, unlockPref, clearPref, getPref, getenv), with its loader pref file autoconfig.js and the xpcshell test that states the expected prefs
23
  Origin: Firefox AutoConfig xpcshell test data written by Mozilla developers (tool_fixture)
24
- Reference result: expected_preference_values
25
- Reference source: extensions/pref/autoconfig/test/unit/test_autoconfig.js lines 36-67: _autoconfig_.test.userpref has a user value "userpref"; _autoconfig_.test.defaultpref default "defaultpref"; browser.startup.homepage reads "http://www.example.com/" (the legacy data:text/plain wrapper unwrapped); _autoconfig_.test.datapref keeps its data:text/plain wrapper; _autoconfig_.test.lockpref locked with "lockpref"; _autoconfig_.test.unlockpref unlocked with "unlockpref"; _autoconfig_.test.clearpref has no user value; getpref, getenv (environment AUTOCONFIG_TEST_GETENV=getenv, line 29) and displayerror ("function") as listed. The cfg (autoconfig-all.cfg lines 1-37) is the reference solution; autoconfig.js (general.config.filename autoconfig.cfg, obscure_value 0, sandbox_enabled true) is the loader pref file copied to defaults/pref (test_autoconfig.js line 19)
26
  Check: Final configuration state, no screenshot needed: install the agent's autoconfig.js into defaults/pref and its autoconfig.cfg into the Firefox install directory, set AUTOCONFIG_TEST_GETENV=getenv, start Firefox headless (or rerun test_autoconfig.js under xpcshell at the pinned commit) and read each listed pref: value equal, lock state and has-user-value as stated in test_autoconfig.js lines 36-67. Exact string equality, no tolerance. The cfg text itself is not compared, since many cfg files give the same prefs
27
  Tools: write defaults/pref/autoconfig.js and autoconfig.cfg into the Firefox install directory with a text editor or script (the documented enterprise AutoConfig route); start Firefox headless (`firefox --headless -profile DIR`) and read the prefs back from prefs.js or through a Marionette session
28
  Companions (not included): extensions/pref/autoconfig/test/unit/autoconfig.js; extensions/pref/autoconfig/test/unit/test_autoconfig.js; LICENSE
 
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:** write defaults/pref/autoconfig.js and autoconfig.cfg into the Firefox install directory with a text editor or script (the documented enterprise AutoConfig route); start Firefox headless (`firefox --headless -profile DIR`) and read the prefs back from prefs.js or through a Marionette session
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `extensions/pref/autoconfig/test/unit/autoconfig-all.cfg`: Firefox AutoConfig: write an autoconfig.cfg that sets, defaults, locks, unlocks, clears and derives eleven preferences.
20
  Format: Mozilla AutoConfig file (.cfg, JavaScript subset with pref, defaultPref, lockPref, unlockPref, clearPref, getPref, getenv), with its loader pref file autoconfig.js and the xpcshell test that states the expected prefs
21
  Origin: Firefox AutoConfig xpcshell test data written by Mozilla developers (tool_fixture)
 
 
22
  Check: Final configuration state, no screenshot needed: install the agent's autoconfig.js into defaults/pref and its autoconfig.cfg into the Firefox install directory, set AUTOCONFIG_TEST_GETENV=getenv, start Firefox headless (or rerun test_autoconfig.js under xpcshell at the pinned commit) and read each listed pref: value equal, lock state and has-user-value as stated in test_autoconfig.js lines 36-67. Exact string equality, no tolerance. The cfg text itself is not compared, since many cfg files give the same prefs
23
  Tools: write defaults/pref/autoconfig.js and autoconfig.cfg into the Firefox install directory with a text editor or script (the documented enterprise AutoConfig route); start Firefox headless (`firefox --headless -profile DIR`) and read the prefs back from prefs.js or through a Marionette session
24
  Companions (not included): extensions/pref/autoconfig/test/unit/autoconfig.js; extensions/pref/autoconfig/test/unit/test_autoconfig.js; LICENSE
campaign_files/2026-10-gt-browser-tests-2/firefox-enterprisepolicies-tests/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. 11 of 11 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_preference_values; expected_site_permissions; expected_policy_effects. 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:** write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser; write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
14
 
15
  **Licence (SPDX):** CC0-1.0 AND MPL-2.0 AND NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `browser/components/enterprisepolicies/tests/xpcshell/test_simple_pref_policies.js`: Firefox enterprise policies: write policies.json so that 49 policies set and lock the expected preferences.
22
  Format: JavaScript array POLICIES_TESTS of {policies, lockedPrefs, unlockedPrefs}: the policies.json object as input, the expected pref values (and whether they are locked) as answer
23
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
24
- Reference result: expected_preference_values
25
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_simple_pref_policies.js lines 31-1431: for each of the 49 entries (one per POLICY comment, e.g. DisableSecurityBypass at line 32, DisableFormHistory at line 46), lockedPrefs and unlockedPrefs give the exact pref values the policy must produce; lines 1433-1451 apply them with checkLockedPref and checkUnlockedPref
26
  Check: Final file and configuration state: the agent writes policies.json for the wanted settings; start Firefox headless with it and read each listed pref: a lockedPrefs entry must be locked and strictly equal (head.js lines 50-61), an unlockedPrefs entry strictly equal and unlocked (lines 63-75). Exact equality, no tolerance. No screenshot needed
27
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
28
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js (defines setupPolicyEngineWithJson, checkLockedPref (lines 50-61: locked and strictly equal) and checkUnlockedPref (lines 63-75)); LICENSE
@@ -30,8 +26,6 @@ Files:
30
  - `browser/components/enterprisepolicies/tests/xpcshell/test_preferences.js`: Firefox Preferences policy: set arbitrary prefs as default, locked, user or cleared, and reject forbidden branches.
31
  Format: JavaScript test: Preferences policy objects ({Value, Status}) as input; expected pref state per Status as answer
32
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
33
- Reference result: expected_preference_values
34
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_preferences.js lines 6-139: OLD_PREFERENCES_TESTS (lines 6-25, legacy values locked, ints coerced to booleans for geo.enabled and extensions.getAddons.showPane), NEW_PREFERENCES_TESTS (lines 27-117, Status default, locked, user and clear), BAD_PREFERENCES_TESTS (lines 119-139, branches outside the allowed list stay unset); lines 195-281 add the user-status, security-branch, JSON-string, bug 1666836 coercion and invalid-entry cases
35
  Check: Final file and configuration state: the agent writes the Preferences policy into policies.json; start Firefox headless with it and check each listed pref for exact value and state (locked, default branch, user branch or unset) as the helpers of head.js do. Exact equality, no tolerance. No screenshot needed
36
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
37
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js (defines setupPolicyEngineWithJson and the checkLockedPref, checkUnlockedPref, checkUserPref, checkDefaultPref, checkUnsetPref helpers (the judge)); LICENSE
@@ -39,8 +33,6 @@ Files:
39
  - `browser/components/enterprisepolicies/tests/xpcshell/test_proxy.js`: Firefox proxy settings: Proxy policy to network.proxy host, port, SOCKS, passthrough and DNS prefs.
40
  Format: JavaScript test: Proxy policy objects as input; expected network.proxy.* pref values as answer
41
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
42
- Reference result: expected_preference_values
43
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_proxy.js lines 37-122: UseProxyForDNS and AutoLogin to network.proxy.socks5_remote_dns and signon.autologin.proxy (lines 37-61), SOCKSVersion 4 and Passthrough "a, b, c" (lines 63-75), HTTP, SSL and SOCKS host:port split into host and port prefs, UseHTTPProxyForAllProtocols copying the HTTP proxy to SSL but not SOCKS, and FTPProxy leaving network.proxy.ftp unset (lines 77-122); the Mode mapping of lines 5-35 depends on PROXY_TYPES_MAP in the product source and is dropped
44
  Check: Final file and configuration state: the agent writes the Proxy policy (or sets the proxy in Connection Settings, which writes the same prefs); read network.proxy.* and signon.autologin.proxy from the profile and compare for exact equality with lines 37-122, and check that network.proxy.ftp and network.proxy.ftp_port are absent. No screenshot needed
45
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
46
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js (defines setupPolicyEngineWithJson and checkUnlockedPref (the judge)); LICENSE
@@ -48,8 +40,6 @@ Files:
48
  - `browser/components/enterprisepolicies/tests/xpcshell/config_popups_cookies_addons.json`: Firefox site permissions: allow and block lists for pop-ups, cookies and add-on installs, overriding earlier permissions.
49
  Format: policies.json file (PopupBlocking, Cookies, InstallAddonsPermission) as the target file; expected permission per site and type in an xpcshell test
50
  Origin: Firefox enterprise-policy xpcshell test data written by Mozilla developers (tool_fixture)
51
- Reference result: expected_site_permissions
52
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_popups_cookies_addons.js lines 53-121: allow.com and pre-existing-deny.com end ALLOW for popup, install and cookie; deny.com and pre-existing-allow.com end DENY for cookie only (lines 78-87); a user change to a managed site is ignored and an unmanaged site keeps the user value (lines 101-121)
53
  Check: Final file and configuration state: the agent writes policies.json (or sets the exceptions in the Permissions dialogs); start Firefox headless and read the permission of each listed site and type from permissions.sqlite (moz_perms) or the permission manager; compare with lines 53-121 exactly. No screenshot needed
54
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
55
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/test_popups_cookies_addons.js (pre-existing permissions (lines 6-42) and expected ALLOW or DENY per site and type (lines 53-121); the answer, hide from the agent); browser/components/enterprisepolicies/tests/xpcshell/head.js (defines setupPolicyEngineWithJson); LICENSE
@@ -57,8 +47,6 @@ Files:
57
  - `browser/components/enterprisepolicies/tests/xpcshell/test_clear_on_shutdown.js`: Firefox clear-on-shutdown policy: write policies.json so that the named data categories are cleared on exit and locked, the others left to the user.
58
  Format: xpcshell test: policies.json objects as input, locked pref values and lock states as answer
59
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
60
- Reference result: expected_policy_effects
61
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_clear_on_shutdown.js lines 23-84: four tasks; ClearOnShutdown {Cache: true, FormData: false} locks privacy.sanitize.sanitizeOnShutdown true, privacy.clearOnShutdown_v2.cache true and formdata false while the unnamed categories stay unlocked (checkNotManaged); Exceptions ["https://persist.example.com"] grants the persist-data-on-shutdown permission; ClearOnShutdown false locks privacy.sanitize.sanitizeOnShutdown and every category false
62
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read the six prefs named at lines 6-11: locked and strictly equal where the test calls checkLockedPref, unlocked where it calls checkNotManaged (head.js lines 50-75). Exact equality, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
63
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
64
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
@@ -66,8 +54,6 @@ Files:
66
  - `browser/components/enterprisepolicies/tests/xpcshell/test_containers.js`: Firefox containers policy: write policies.json so that the profile gets one container named Test Container with the cart icon and orange colour.
67
  Format: xpcshell test: policies.json object as input, the container identity as answer
68
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
69
- Reference result: expected_policy_effects
70
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_containers.js lines 16-37: Containers.Default [{name: "Test Container", icon: "cart", color: "orange"}] must yield exactly 1 public identity with that name, icon and colour (lines 31-35); the profile file containers.json holds them as {version, identities} (ContextualIdentityService.sys.mjs lines 381-383, version 8 at line 7)
71
  Check: Final file state, no screenshot needed: after Firefox has started with the agent's policies.json, parse the profile's containers.json and check that the public identities (public true) are exactly one, with name "Test Container", icon "cart" and color "orange" (string equality, as test_containers.js lines 31-35). Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
72
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
73
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; toolkit/components/contextualidentity/ContextualIdentityService.sys.mjs; LICENSE
@@ -75,8 +61,6 @@ Files:
75
  - `browser/components/enterprisepolicies/tests/xpcshell/test_defaultbrowsercheck.js`: Firefox default-browser policies: write policies.json so that the startup default-browser check and the set-as-default control are on or off as asked.
76
  Format: xpcshell test: policies.json objects as input, the default-browser check state and the setDefaultBrowser permission as answer
77
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
78
- Reference result: expected_policy_effects
79
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_defaultbrowsercheck.js lines 9-98: four tasks; DontCheckDefaultBrowser true makes ShellService.shouldCheckDefaultBrowser false even after the user sets it true (lines 15-32), false makes it true (lines 42-51); DefaultBrowserSettingEnabled false makes it false and Services.policies.isAllowed("setDefaultBrowser") false (lines 61-71), true makes both true (lines 84-94)
80
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read ShellService.shouldCheckDefaultBrowser and Services.policies.isAllowed("setDefaultBrowser") (or rerun test_defaultbrowsercheck.js under xpcshell at the pinned commit); boolean equality as in the test. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
81
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
82
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
@@ -84,8 +68,6 @@ Files:
84
  - `browser/components/enterprisepolicies/tests/xpcshell/test_policy_search_engine.js`: Firefox search-engine policies: write policies.json that adds, removes and sets default search engines and blocks engine installs.
85
  Format: xpcshell test: policies.json SearchEngines objects as input, the search service state as answer
86
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
87
- Reference result: expected_policy_effects
88
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_policy_search_engine.js lines 32-478: ten tasks; SearchEngines.Add with Name, URLTemplate, Method, IconURL, Encoding, SuggestURLTemplate and PostData, Default "MozSearch" (line 55), DefaultPrivate "MozSearch" (line 98), PreventInstalls true (line 142), Remove ["Foo"] (line 197); each task checks the engine list, the default names, the engine method ("POST", line 242), the query charset ("UTF-8" default, line 192) and the icon URL
89
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read the search service state (engine names, default and private default, method, charset, suggest URL), or rerun test_policy_search_engine.js under xpcshell at the pinned commit; Firefox keeps this state in the profile's search.json.mozlz4 (LZ4 compressed JSON). String equality as in the test, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
90
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
91
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
@@ -93,8 +75,6 @@ Files:
93
  - `browser/components/enterprisepolicies/tests/xpcshell/test_local_network_access.js`: Firefox local network access policy: write policies.json that enables or disables blocking of local network requests, locks it, and lists skip domains.
94
  Format: xpcshell test: policies.json LocalNetworkAccess objects as input, network.lna.* pref values and lock states as answer
95
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
96
- Reference result: expected_policy_effects
97
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_local_network_access.js lines 6-506: 15 tasks; LocalNetworkAccess with Enabled, Locked, BlockTrackers, EnablePrompting and SkipDomains sets network.lna.enabled, network.lna.block_trackers, network.lna.blocking and network.lna.skip-domains, locked only when Locked is true (for example lines 18-46 unlocked, lines 107-135 locked); SkipDomains cases at lines 421-506
98
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read the network.lna.* prefs: value equal and lock state as the test asserts with Services.prefs.getBoolPref, getCharPref and prefIsLocked. Exact equality, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
99
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
100
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
@@ -102,8 +82,6 @@ Files:
102
  - `browser/components/enterprisepolicies/tests/xpcshell/test_permissions.js`: Firefox site permissions policy: write policies.json with allow and block lists for camera, microphone, location, notifications, autoplay, VR and screen share.
103
  Format: xpcshell test: policies.json Permissions objects as input, permission manager actions as answer
104
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
105
- Reference result: expected_policy_effects
106
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_permissions.js lines 95-559: Permissions with Allow and Block lists per type (lines 95-128); checkPermission and checkAllPermissionsForType (lines 137-171) expects ALLOW for allow.com and pre-existing-deny.com, DENY for deny.com and pre-existing-allow.com, UNKNOWN for unknown.com, with expireType EXPIRE_POLICY, for camera, microphone, geo, desktop-notification, autoplay-media and xr (lines 173-195); later tasks cover tracking protection exceptions, Cookies AllowSession, AutoLaunchProtocolsFromOrigins, PasswordManagerExceptions, HttpAllowlist and SanitizeOnShutdown Exceptions (lines 297-559); action and expiry codes in nsIPermissionManager.idl lines 58-77 (ALLOW_ACTION 1, DENY_ACTION 2, EXPIRE_POLICY 3)
107
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and query the permission manager for each (site, type) pair: the action must equal the expected ALLOW, DENY or UNKNOWN code and policy permissions must have expireType EXPIRE_POLICY (nsIPermissionManager.idl lines 58-77); policy permissions live in memory, not in permissions.sqlite, so the judge reads them through the running browser or reruns test_permissions.js. Exact equality, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
108
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
109
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; netwerk/base/nsIPermissionManager.idl; LICENSE
@@ -111,8 +89,6 @@ Files:
111
  - `browser/components/enterprisepolicies/tests/xpcshell/test_webserial.js`: Firefox Web Serial policy: write policies.json so that dom.webserial.enabled is allowed, blocked and locked, or left to other policies, as asked.
112
  Format: xpcshell test: policies.json objects as input, the dom.webserial.enabled value and lock state as answer
113
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
114
- Reference result: expected_policy_effects
115
- Reference source: browser/components/enterprisepolicies/tests/xpcshell/test_webserial.js lines 1-114: PREF dom.webserial.enabled; no policy keeps it unlocked true; Certificates.ImportEnterpriseRoots alone leaves the engine inactive and the pref true; DefaultSerialGuardSetting 3 keeps it unlocked true (also with BlockAboutConfig); BlockAboutConfig alone makes it unlocked false; DefaultSerialGuardSetting 2 locks it false (lines 99-114)
116
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read dom.webserial.enabled: value strictly equal and lock state as checkLockedPref or checkUnlockedPref asserts (head.js lines 50-75). Exact equality, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
117
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
118
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 11 of 11 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:** write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser; write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
12
 
13
  **Licence (SPDX):** CC0-1.0 AND MPL-2.0 AND NOASSERTION
 
19
  - `browser/components/enterprisepolicies/tests/xpcshell/test_simple_pref_policies.js`: Firefox enterprise policies: write policies.json so that 49 policies set and lock the expected preferences.
20
  Format: JavaScript array POLICIES_TESTS of {policies, lockedPrefs, unlockedPrefs}: the policies.json object as input, the expected pref values (and whether they are locked) as answer
21
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
22
  Check: Final file and configuration state: the agent writes policies.json for the wanted settings; start Firefox headless with it and read each listed pref: a lockedPrefs entry must be locked and strictly equal (head.js lines 50-61), an unlockedPrefs entry strictly equal and unlocked (lines 63-75). Exact equality, no tolerance. No screenshot needed
23
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
24
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js (defines setupPolicyEngineWithJson, checkLockedPref (lines 50-61: locked and strictly equal) and checkUnlockedPref (lines 63-75)); LICENSE
 
26
  - `browser/components/enterprisepolicies/tests/xpcshell/test_preferences.js`: Firefox Preferences policy: set arbitrary prefs as default, locked, user or cleared, and reject forbidden branches.
27
  Format: JavaScript test: Preferences policy objects ({Value, Status}) as input; expected pref state per Status as answer
28
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
29
  Check: Final file and configuration state: the agent writes the Preferences policy into policies.json; start Firefox headless with it and check each listed pref for exact value and state (locked, default branch, user branch or unset) as the helpers of head.js do. Exact equality, no tolerance. No screenshot needed
30
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
31
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js (defines setupPolicyEngineWithJson and the checkLockedPref, checkUnlockedPref, checkUserPref, checkDefaultPref, checkUnsetPref helpers (the judge)); LICENSE
 
33
  - `browser/components/enterprisepolicies/tests/xpcshell/test_proxy.js`: Firefox proxy settings: Proxy policy to network.proxy host, port, SOCKS, passthrough and DNS prefs.
34
  Format: JavaScript test: Proxy policy objects as input; expected network.proxy.* pref values as answer
35
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
36
  Check: Final file and configuration state: the agent writes the Proxy policy (or sets the proxy in Connection Settings, which writes the same prefs); read network.proxy.* and signon.autologin.proxy from the profile and compare for exact equality with lines 37-122, and check that network.proxy.ftp and network.proxy.ftp_port are absent. No screenshot needed
37
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
38
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js (defines setupPolicyEngineWithJson and checkUnlockedPref (the judge)); LICENSE
 
40
  - `browser/components/enterprisepolicies/tests/xpcshell/config_popups_cookies_addons.json`: Firefox site permissions: allow and block lists for pop-ups, cookies and add-on installs, overriding earlier permissions.
41
  Format: policies.json file (PopupBlocking, Cookies, InstallAddonsPermission) as the target file; expected permission per site and type in an xpcshell test
42
  Origin: Firefox enterprise-policy xpcshell test data written by Mozilla developers (tool_fixture)
 
 
43
  Check: Final file and configuration state: the agent writes policies.json (or sets the exceptions in the Permissions dialogs); start Firefox headless and read the permission of each listed site and type from permissions.sqlite (moz_perms) or the permission manager; compare with lines 53-121 exactly. No screenshot needed
44
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
45
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/test_popups_cookies_addons.js (pre-existing permissions (lines 6-42) and expected ALLOW or DENY per site and type (lines 53-121); the answer, hide from the agent); browser/components/enterprisepolicies/tests/xpcshell/head.js (defines setupPolicyEngineWithJson); LICENSE
 
47
  - `browser/components/enterprisepolicies/tests/xpcshell/test_clear_on_shutdown.js`: Firefox clear-on-shutdown policy: write policies.json so that the named data categories are cleared on exit and locked, the others left to the user.
48
  Format: xpcshell test: policies.json objects as input, locked pref values and lock states as answer
49
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
50
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read the six prefs named at lines 6-11: locked and strictly equal where the test calls checkLockedPref, unlocked where it calls checkNotManaged (head.js lines 50-75). Exact equality, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
51
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
52
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
 
54
  - `browser/components/enterprisepolicies/tests/xpcshell/test_containers.js`: Firefox containers policy: write policies.json so that the profile gets one container named Test Container with the cart icon and orange colour.
55
  Format: xpcshell test: policies.json object as input, the container identity as answer
56
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
57
  Check: Final file state, no screenshot needed: after Firefox has started with the agent's policies.json, parse the profile's containers.json and check that the public identities (public true) are exactly one, with name "Test Container", icon "cart" and color "orange" (string equality, as test_containers.js lines 31-35). Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
58
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
59
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; toolkit/components/contextualidentity/ContextualIdentityService.sys.mjs; LICENSE
 
61
  - `browser/components/enterprisepolicies/tests/xpcshell/test_defaultbrowsercheck.js`: Firefox default-browser policies: write policies.json so that the startup default-browser check and the set-as-default control are on or off as asked.
62
  Format: xpcshell test: policies.json objects as input, the default-browser check state and the setDefaultBrowser permission as answer
63
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
64
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read ShellService.shouldCheckDefaultBrowser and Services.policies.isAllowed("setDefaultBrowser") (or rerun test_defaultbrowsercheck.js under xpcshell at the pinned commit); boolean equality as in the test. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
65
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
66
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
 
68
  - `browser/components/enterprisepolicies/tests/xpcshell/test_policy_search_engine.js`: Firefox search-engine policies: write policies.json that adds, removes and sets default search engines and blocks engine installs.
69
  Format: xpcshell test: policies.json SearchEngines objects as input, the search service state as answer
70
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
71
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read the search service state (engine names, default and private default, method, charset, suggest URL), or rerun test_policy_search_engine.js under xpcshell at the pinned commit; Firefox keeps this state in the profile's search.json.mozlz4 (LZ4 compressed JSON). String equality as in the test, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
72
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
73
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
 
75
  - `browser/components/enterprisepolicies/tests/xpcshell/test_local_network_access.js`: Firefox local network access policy: write policies.json that enables or disables blocking of local network requests, locks it, and lists skip domains.
76
  Format: xpcshell test: policies.json LocalNetworkAccess objects as input, network.lna.* pref values and lock states as answer
77
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
78
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read the network.lna.* prefs: value equal and lock state as the test asserts with Services.prefs.getBoolPref, getCharPref and prefIsLocked. Exact equality, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
79
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
80
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
 
82
  - `browser/components/enterprisepolicies/tests/xpcshell/test_permissions.js`: Firefox site permissions policy: write policies.json with allow and block lists for camera, microphone, location, notifications, autoplay, VR and screen share.
83
  Format: xpcshell test: policies.json Permissions objects as input, permission manager actions as answer
84
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
85
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and query the permission manager for each (site, type) pair: the action must equal the expected ALLOW, DENY or UNKNOWN code and policy permissions must have expireType EXPIRE_POLICY (nsIPermissionManager.idl lines 58-77); policy permissions live in memory, not in permissions.sqlite, so the judge reads them through the running browser or reruns test_permissions.js. Exact equality, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
86
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
87
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; netwerk/base/nsIPermissionManager.idl; LICENSE
 
89
  - `browser/components/enterprisepolicies/tests/xpcshell/test_webserial.js`: Firefox Web Serial policy: write policies.json so that dom.webserial.enabled is allowed, blocked and locked, or left to other policies, as asked.
90
  Format: xpcshell test: policies.json objects as input, the dom.webserial.enabled value and lock state as answer
91
  Origin: Firefox enterprise-policy xpcshell test written by Mozilla developers (tool_fixture)
 
 
92
  Check: Final configuration state, no screenshot needed: start Firefox headless with the agent's policies.json and read dom.webserial.enabled: value strictly equal and lock state as checkLockedPref or checkUnlockedPref asserts (head.js lines 50-75). Exact equality, no tolerance. Static judge, no screenshot needed: parse the policies.json the agent wrote and check that its "policies" object equals the policies object of the chosen test task (JSON equality, key order ignored).
93
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting state back (prefs.js and the profile files, or about:policies through a Marionette or WebDriver BiDi session); the policies.json itself can also be checked with any JSON parser
94
  Companions (not included): browser/components/enterprisepolicies/tests/xpcshell/head.js; toolkit/components/enterprisepolicies/tests/EnterprisePolicyTesting.sys.mjs; LICENSE
campaign_files/2026-10-gt-browser-tests-2/firefox-exthandler-tests/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_handler_settings. 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:** write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `uriloader/exthandler/tests/unit/handlers.json`: Firefox Applications settings: what to do with each file type and link scheme, stored in handlers.json.
22
  Format: handlers.json (Firefox profile file for the Applications panel: mimeTypes and schemes with action, ask, handlers, extensions) as the target file; expected handler infos in an xpcshell test
23
  Origin: Firefox handler-service xpcshell test data written by Mozilla developers (tool_fixture)
24
- Reference result: expected_handler_settings
25
- Reference source: uriloader/exthandler/tests/unit/test_handlerService_store.js lines 51-156: per type (example/type.handleinternally, savetodisk, usehelperapp, usesystemdefault and the schemes examplescheme.usehelperapp and examplescheme.usesystemdefault) the preferredAction, alwaysAskBeforeHandling, preferred and possible handler apps (name, uriTemplate or executable) and file extensions; lines 162-183 fill these from handlers.json
26
  Check: Final file state: parse the agent-written handlers.json and compare, per type and scheme, the action code, ask flag, handler list (name and uriTemplate, in order) and extensions with lines 51-156; exact equality, no tolerance. No screenshot needed
27
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
28
  Companions (not included): uriloader/exthandler/tests/unit/test_handlerService_store.js (assertAllHandlerInfosMatchTestData (lines 51-156) gives the expected handler settings per MIME type and URL scheme; the answer, hide from the agent); LICENSE
 
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:** write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `uriloader/exthandler/tests/unit/handlers.json`: Firefox Applications settings: what to do with each file type and link scheme, stored in handlers.json.
20
  Format: handlers.json (Firefox profile file for the Applications panel: mimeTypes and schemes with action, ask, handlers, extensions) as the target file; expected handler infos in an xpcshell test
21
  Origin: Firefox handler-service xpcshell test data written by Mozilla developers (tool_fixture)
 
 
22
  Check: Final file state: parse the agent-written handlers.json and compare, per type and scheme, the action code, ask flag, handler list (name and uriTemplate, in order) and extensions with lines 51-156; exact equality, no tolerance. No screenshot needed
23
  Tools: write distribution/policies.json (the enterprise policy file) next to the Firefox binary, or into the system policies directory, with a text editor or script; start Firefox headless (`firefox --headless -profile DIR`) so the policy engine applies it, then read the resulting prefs back from prefs.js or with a small reader of the pref syntax; the policies.json itself can also be checked with any JSON parser
24
  Companions (not included): uriloader/exthandler/tests/unit/test_handlerService_store.js (assertAllHandlerInfosMatchTestData (lines 51-156) gives the expected handler settings per MIME type and URL scheme; the answer, hide from the agent); LICENSE
campaign_files/2026-10-gt-browser-tests-2/firefox-libpref-tests/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. 4 of 4 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_preference_values. 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:** write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `modules/libpref/test/unit/data/testParser.js`: Firefox default-preference file syntax: comments, whitespace, sticky and locked attributes, integer limits and string escapes.
22
  Format: Firefox default-preferences file (pref(name, value[, sticky|locked]) lines) as input; expected values in an xpcshell test
23
  Origin: libpref xpcshell test data written by Mozilla developers (tool_fixture)
24
- Reference result: expected_preference_values
25
- Reference source: modules/libpref/test/unit/test_parser.js lines 18-113: expected values for every pref in data/testParser.js (booleans, ints from 0 to INT_MIN, strings with quotes and escapes) and the locked flags at lines 29-30
26
  Check: Final file state: the agent writes a default-prefs file meeting the listed values; load it with Services.prefs.readDefaultPrefsFromFile (as test_parser.js line 17 does) or an equivalent reader of the pref syntax, and compare every pref value and lock flag for exact equality with lines 18-113. No screenshot needed
27
  Tools: write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
28
  Companions (not included): modules/libpref/test/unit/test_parser.js (expected values; the answer, hide from the agent); modules/libpref/test/unit/head_libPrefs.js (xpcshell head file loaded before the test); LICENSE
@@ -30,8 +26,6 @@ Files:
30
  - `modules/libpref/test/unit/data/testPrefLocked.js`: Firefox locked preference: a user_pref cannot override a pref marked locked in the default file.
31
  Format: two Firefox pref files (defaults with the locked attribute, user prefs) as input; expected effective values in an xpcshell test
32
  Origin: libpref xpcshell test data written by Mozilla developers (tool_fixture)
33
- Reference result: expected_preference_values
34
- Reference source: modules/libpref/test/unit/test_locked_file_prefs.js lines 17-51: testPref.unlocked.int is 333 and testPref.locked.int stays 444 after loading the user file with 555 (lines 47-48); after unlockPref the user value 445 wins (lines 34-37)
35
  Check: Final file state: the agent writes the default-prefs and user-prefs files so that the locked pref keeps its default; read them back in the order defaults then user prefs (lines 43-45) and compare the effective values for exact equality with lines 47-48. No screenshot needed
36
  Tools: write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
37
  Companions (not included): modules/libpref/test/unit/data/testPrefLockedUser.js (user_pref override that must have no effect); modules/libpref/test/unit/test_locked_file_prefs.js (expected values; the answer, hide from the agent); LICENSE
@@ -39,8 +33,6 @@ Files:
39
  - `modules/libpref/test/unit/data/testPrefSticky.js`: Firefox sticky preference: which values get written back to prefs.js after a save.
40
  Format: two Firefox pref files (defaults with the sticky attribute, user prefs) as input; expected saved state in an xpcshell test
41
  Origin: libpref xpcshell test data written by Mozilla developers (tool_fixture)
42
- Reference result: expected_preference_values
43
- Reference source: modules/libpref/test/unit/test_stickyprefs.js lines 47-196: an unchanged sticky pref is not written on save (lines 47-63); a sticky pref loaded from a user_pref is written even when equal to its default (lines 65-80), and later cases on change, hasUserValue, clearUserPref and observers
44
  Check: Final file state: after the agent changes settings and saves, read the saved prefs.js back and check which prefs are present and their values for exact equality with the cases at lines 47-196. No screenshot needed
45
  Tools: write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
46
  Companions (not included): modules/libpref/test/unit/data/testPrefStickyUser.js (user_pref for the sticky pref, equal to its default); modules/libpref/test/unit/test_stickyprefs.js (expected values; the answer, hide from the agent); LICENSE
@@ -48,8 +40,6 @@ Files:
48
  - `modules/libpref/test/unit/data/testPref.js`: Firefox user prefs file in ISO-8859-1 and UTF-8: types, values and the non-ASCII string as libpref reads it.
49
  Format: Firefox user prefs files (user_pref lines) in two encodings as input; expected parse events in an xpcshell test
50
  Origin: libpref xpcshell test data written by Mozilla developers (tool_fixture)
51
- Reference result: expected_preference_values
52
- Reference source: modules/libpref/test/unit/test_parsePrefs.js lines 52-72: for testPref.js the six user prefs with values true, false, 23, -1236, "_testPref" and "älskar"; for testPrefUTF8.js the same except testPref.char2, read as the Latin-1 rendering of the UTF-8 bytes (line 71)
53
  Check: Final file state: parse the agent-written prefs file with Services.prefs.parsePrefsFromBuffer (as line 82 does) or an equivalent reader and compare the list of (type, kind, name, value, sticky, locked) entries for exact equality with lines 52-72. No screenshot needed
54
  Tools: write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
55
  Companions (not included): modules/libpref/test/unit/data/testPrefUTF8.js (the same prefs encoded as UTF-8); modules/libpref/test/unit/test_parsePrefs.js (expected parse events; the answer, hide from the agent); LICENSE
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 4 of 4 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:** write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `modules/libpref/test/unit/data/testParser.js`: Firefox default-preference file syntax: comments, whitespace, sticky and locked attributes, integer limits and string escapes.
20
  Format: Firefox default-preferences file (pref(name, value[, sticky|locked]) lines) as input; expected values in an xpcshell test
21
  Origin: libpref xpcshell test data written by Mozilla developers (tool_fixture)
 
 
22
  Check: Final file state: the agent writes a default-prefs file meeting the listed values; load it with Services.prefs.readDefaultPrefsFromFile (as test_parser.js line 17 does) or an equivalent reader of the pref syntax, and compare every pref value and lock flag for exact equality with lines 18-113. No screenshot needed
23
  Tools: write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
24
  Companions (not included): modules/libpref/test/unit/test_parser.js (expected values; the answer, hide from the agent); modules/libpref/test/unit/head_libPrefs.js (xpcshell head file loaded before the test); LICENSE
 
26
  - `modules/libpref/test/unit/data/testPrefLocked.js`: Firefox locked preference: a user_pref cannot override a pref marked locked in the default file.
27
  Format: two Firefox pref files (defaults with the locked attribute, user prefs) as input; expected effective values in an xpcshell test
28
  Origin: libpref xpcshell test data written by Mozilla developers (tool_fixture)
 
 
29
  Check: Final file state: the agent writes the default-prefs and user-prefs files so that the locked pref keeps its default; read them back in the order defaults then user prefs (lines 43-45) and compare the effective values for exact equality with lines 47-48. No screenshot needed
30
  Tools: write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
31
  Companions (not included): modules/libpref/test/unit/data/testPrefLockedUser.js (user_pref override that must have no effect); modules/libpref/test/unit/test_locked_file_prefs.js (expected values; the answer, hide from the agent); LICENSE
 
33
  - `modules/libpref/test/unit/data/testPrefSticky.js`: Firefox sticky preference: which values get written back to prefs.js after a save.
34
  Format: two Firefox pref files (defaults with the sticky attribute, user prefs) as input; expected saved state in an xpcshell test
35
  Origin: libpref xpcshell test data written by Mozilla developers (tool_fixture)
 
 
36
  Check: Final file state: after the agent changes settings and saves, read the saved prefs.js back and check which prefs are present and their values for exact equality with the cases at lines 47-196. No screenshot needed
37
  Tools: write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
38
  Companions (not included): modules/libpref/test/unit/data/testPrefStickyUser.js (user_pref for the sticky pref, equal to its default); modules/libpref/test/unit/test_stickyprefs.js (expected values; the answer, hide from the agent); LICENSE
 
40
  - `modules/libpref/test/unit/data/testPref.js`: Firefox user prefs file in ISO-8859-1 and UTF-8: types, values and the non-ASCII string as libpref reads it.
41
  Format: Firefox user prefs files (user_pref lines) in two encodings as input; expected parse events in an xpcshell test
42
  Origin: libpref xpcshell test data written by Mozilla developers (tool_fixture)
 
 
43
  Check: Final file state: parse the agent-written prefs file with Services.prefs.parsePrefsFromBuffer (as line 82 does) or an equivalent reader and compare the list of (type, kind, name, value, sticky, locked) entries for exact equality with lines 52-72. No screenshot needed
44
  Tools: write the preference lines into prefs.js or user.js in a Firefox profile directory (or a default-prefs file) with a text editor or script, then start Firefox headless (`firefox --headless -profile DIR`) or parse the file with a small reader of the pref() / user_pref() syntax and read the values back
45
  Companions (not included): modules/libpref/test/unit/data/testPrefUTF8.js (the same prefs encoded as UTF-8); modules/libpref/test/unit/test_parsePrefs.js (expected parse events; the answer, hide from the agent); LICENSE
campaign_files/2026-10-gt-browser-tests-2/firefox-toolkit-profile-tests/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_profiles_ini. 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:** edit profiles.ini in the Firefox data directory with a text editor or script (or run `firefox --headless -P` / `-ProfileManager`); read it back with any INI parser and compare the [Profile*] and [Install*] sections
14
 
15
  **Licence (SPDX):** CC0-1.0
@@ -21,8 +19,6 @@ Files:
21
  - `toolkit/profile/test/xpcshell/test_remove_default.js`: Firefox profile manager: delete the default profile so that profiles.ini keeps no profile and a blank install default.
22
  Format: xpcshell test: the starting profiles.ini as a JavaScript object (lines 13-27) and the expected final one (lines 59-62, 72-79); the INI layout is defined in head.js
23
  Origin: Firefox profile-service xpcshell test written by Mozilla developers (tool_fixture)
24
- Reference result: expected_profiles_ini
25
- Reference source: toolkit/profile/test/xpcshell/test_remove_default.js lines 59-79: after the removal the profiles list is empty (profiles.pop() at line 60) and the install section default is "" (lines 61 and 74-78), checked with checkProfileService after flush
26
  Check: Final file state: read the agent-modified profiles.ini and check that no [ProfileN] section remains and that the [Install<hash>] section has Default= empty, as lines 59-79 state; the hash is fixed when the task is built. Exact equality, no tolerance. No screenshot needed
27
  Tools: edit profiles.ini in the Firefox data directory with a text editor or script (or run `firefox --headless -P` / `-ProfileManager`); read it back with any INI parser and compare the [Profile*] and [Install*] sections
28
  Companions (not included): toolkit/profile/test/xpcshell/head.js (defines writeProfilesIni (line 252), readProfilesIni (line 331) and checkProfileService (line 528): the profiles.ini format and the judge); LICENSE
 
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:** edit profiles.ini in the Firefox data directory with a text editor or script (or run `firefox --headless -P` / `-ProfileManager`); read it back with any INI parser and compare the [Profile*] and [Install*] sections
12
 
13
  **Licence (SPDX):** CC0-1.0
 
19
  - `toolkit/profile/test/xpcshell/test_remove_default.js`: Firefox profile manager: delete the default profile so that profiles.ini keeps no profile and a blank install default.
20
  Format: xpcshell test: the starting profiles.ini as a JavaScript object (lines 13-27) and the expected final one (lines 59-62, 72-79); the INI layout is defined in head.js
21
  Origin: Firefox profile-service xpcshell test written by Mozilla developers (tool_fixture)
 
 
22
  Check: Final file state: read the agent-modified profiles.ini and check that no [ProfileN] section remains and that the [Install<hash>] section has Default= empty, as lines 59-79 state; the hash is fixed when the task is built. Exact equality, no tolerance. No screenshot needed
23
  Tools: edit profiles.ini in the Firefox data directory with a text editor or script (or run `firefox --headless -P` / `-ProfileManager`); read it back with any INI parser and compare the [Profile*] and [Install*] sections
24
  Companions (not included): toolkit/profile/test/xpcshell/head.js (defines writeProfilesIni (line 252), readProfilesIni (line 331) and checkProfileService (line 528): the profiles.ini format and the judge); LICENSE
campaign_files/2026-10-gt-browser-tests-2/flanker-bounce-fixtures/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: inline_expected_values. 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:** flanker.mime create.from_string plus bounce.detect (Python), or Python email.parser reading the message/delivery-status part; a script writes is_bounce, the status code, the diagnostic code and the notification text to JSON
14
 
15
  **Licence (SPDX):** Apache-2.0
@@ -21,7 +19,5 @@ Files:
21
  - `tests/fixtures/messages/bounce/zed.eml`: Detect a bounced message and extract its delivery status and diagnostic code.
22
  Format: RFC 5322 bounce message with message/delivery-status (.eml)
23
  Origin: flanker bounce test fixture (tool_fixture)
24
- Reference result: inline_expected_values
25
- Reference source: tests/mime/bounce_tests.py lines 7-35 (status 5.1.1, notification text, diagnostic_code) and lines 60-64 (eq_ on the result and is_bounce True); BOUNCE is read from this file at tests/__init__.py line 38
26
  Check: Final file state: is_bounce must be true, status must equal 5.1.1, diagnostic_code and notification must equal the strings in bounce_tests.py exactly. The score 1.875 is a flanker heuristic and is not used to judge other tools. No screenshot
27
  Tools: flanker.mime create.from_string plus bounce.detect (Python), or Python email.parser reading the message/delivery-status part; a script writes is_bounce, the status code, the diagnostic code and the notification text to JSON
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** flanker.mime create.from_string plus bounce.detect (Python), or Python email.parser reading the message/delivery-status part; a script writes is_bounce, the status code, the diagnostic code and the notification text to JSON
12
 
13
  **Licence (SPDX):** Apache-2.0
 
19
  - `tests/fixtures/messages/bounce/zed.eml`: Detect a bounced message and extract its delivery status and diagnostic code.
20
  Format: RFC 5322 bounce message with message/delivery-status (.eml)
21
  Origin: flanker bounce test fixture (tool_fixture)
 
 
22
  Check: Final file state: is_bounce must be true, status must equal 5.1.1, diagnostic_code and notification must equal the strings in bounce_tests.py exactly. The score 1.875 is a flanker heuristic and is not used to judge other tools. No screenshot
23
  Tools: flanker.mime create.from_string plus bounce.detect (Python), or Python email.parser reading the message/delivery-status part; a script writes is_bounce, the status code, the diagnostic code and the notification text to JSON
campaign_files/2026-10-gt-browser-tests-2/fontconfig-json-tests/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. 4 of 4 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_font_match_results. 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:** write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
14
 
15
  **Licence (SPDX):** HPND-sell-variant
@@ -21,8 +19,6 @@ Files:
21
  - `test/test-issue-539.json`: Set Adwaita Mono as the strongly bound default monospace font in fontconfig.
22
  Format: fontconfig test-conf JSON (fonts, load_xml, tests with method match, pattern or scan; parsed by json-c, which accepts trailing commas that strict JSON parsers reject) plus a fontconfig XML config file
23
  Origin: JSON test cases of fontconfig's test-conf runner (test/*.json, format in test/TEST-JSON-FORMAT.md), each with the config file it tests (tool_fixture)
24
- Reference result: expected_font_match_results
25
- Reference source: test/test-issue-539.json, tests: 3 match tests with spacing 100: family "Noto Sans Mono" stays Noto Sans Mono, family "monospace" gives Adwaita Mono, family "sans-serif" gives Adwaita Mono (the strong binding outranks the sans-serif alias for a monospace query)
26
  Check: Final configuration state, no screenshot needed. Load the agent's fontconfig XML file in place of %test%/test-issue-539.conf, together with the conf.d files the JSON lists in load_xml, into fontconfig at the pinned commit and run the JSON's tests with the test-conf runner (test/test-conf test/test-issue-539.json); every test must return the expected result (the runner compares each listed property exactly). Equivalently, on a system with only the JSON's fake fonts, `fc-match` on each query must print the expected family. The JSON loads conf.d/48-guessfamily.conf, 48-spacing.conf, 49-sansserif.conf and 60-latin.conf around the test conf; they are fetched and listed as companions
27
  Tools: write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
28
  Companions (not included): test/test-issue-539.conf; conf.d/48-guessfamily.conf; conf.d/48-spacing.conf; conf.d/49-sansserif.conf; conf.d/60-latin.conf; test/TEST-JSON-FORMAT.md; COPYING
@@ -30,8 +26,6 @@ Files:
30
  - `test/test-issue-525.json`: Make Lato the preferred system-ui font in fontconfig.
31
  Format: fontconfig test-conf JSON (fonts, load_xml, tests with method match, pattern or scan; parsed by json-c, which accepts trailing commas that strict JSON parsers reject) plus a fontconfig XML config file
32
  Origin: JSON test cases of fontconfig's test-conf runner (test/*.json, format in test/TEST-JSON-FORMAT.md), each with the config file it tests (tool_fixture)
33
- Reference result: expected_font_match_results
34
- Reference source: test/test-issue-525.json, tests: match with family "system-ui" returns Lato (family, style, file and fontversion of the Lato entry)
35
  Check: Final configuration state, no screenshot needed. Load the agent's fontconfig XML file in place of %test%/test-issue-525.conf, together with the conf.d files the JSON lists in load_xml, into fontconfig at the pinned commit and run the JSON's tests with the test-conf runner (test/test-conf test/test-issue-525.json); every test must return the expected result (the runner compares each listed property exactly). Equivalently, on a system with only the JSON's fake fonts, `fc-match` on each query must print the expected family. The JSON loads conf.d/48-guessfamily.conf, 49-sansserif.conf and 60-latin.conf around the test conf; they are fetched and listed as companions
36
  Tools: write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
37
  Companions (not included): test/test-issue-525.conf; conf.d/48-guessfamily.conf; conf.d/49-sansserif.conf; conf.d/60-latin.conf; test/TEST-JSON-FORMAT.md; COPYING
@@ -39,7 +33,6 @@ Files:
39
  - `test/test-issue-525-2.json`: Make Lato the preferred font for the -apple-system family name in fontconfig.
40
  Format: fontconfig test-conf JSON (fonts, load_xml, tests with method match, pattern or scan; parsed by json-c, which accepts trailing commas that strict JSON parsers reject) plus a fontconfig XML config file
41
  Origin: JSON test cases of fontconfig's test-conf runner (test/*.json, format in test/TEST-JSON-FORMAT.md), each with the config file it tests (tool_fixture)
42
- Reference result: expected_font_match_results
43
  Check: Final configuration state, no screenshot needed. Load the agent's fontconfig XML file in place of %test%/test-issue-525-2.conf, together with the conf.d files the JSON lists in load_xml, into fontconfig at the pinned commit and run the JSON's tests with the test-conf runner (test/test-conf test/test-issue-525-2.json); every test must return the expected result (the runner compares each listed property exactly). Equivalently, on a system with only the JSON's fake fonts, `fc-match` on each query must print the expected family. The JSON loads conf.d/48-guessfamily.conf, 49-sansserif.conf and 60-latin.conf around the test conf; they are fetched and listed as companions
44
  Tools: write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
45
  Companions (not included): test/test-issue-525-2.conf; conf.d/48-guessfamily.conf; conf.d/49-sansserif.conf; conf.d/60-latin.conf; test/TEST-JSON-FORMAT.md; COPYING
@@ -47,8 +40,6 @@ Files:
47
  - `test/test-genericfamily.json`: Set Foo and Baz as preferred sans-serif fonts and Bar as preferred serif font in fontconfig.
48
  Format: fontconfig test-conf JSON (fonts, load_xml, tests with method match, pattern or scan; parsed by json-c, which accepts trailing commas that strict JSON parsers reject) plus a fontconfig XML config file
49
  Origin: JSON test cases of fontconfig's test-conf runner (test/*.json, format in test/TEST-JSON-FORMAT.md), each with the config file it tests (tool_fixture)
50
- Reference result: expected_font_match_results
51
- Reference source: test/test-genericfamily.json, tests: one scan test whose result_fs gives genericfamily sans-serif for Foo and Baz and serif for Bar
52
  Check: Final configuration state, no screenshot needed. Load the agent's fontconfig XML file in place of %test%/test-genericfamily.conf, together with the conf.d files the JSON lists in load_xml, into fontconfig at the pinned commit and run the JSON's tests with the test-conf runner (test/test-conf test/test-genericfamily.json); every test must return the expected result (the runner compares each listed property exactly). Equivalently, on a system with only the JSON's fake fonts, `fc-match` on each query must print the expected family. The JSON loads only the test conf, so no conf.d companion is needed
53
  Tools: write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
54
  Companions (not included): test/test-genericfamily.conf; test/TEST-JSON-FORMAT.md; COPYING
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 4 of 4 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:** write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
12
 
13
  **Licence (SPDX):** HPND-sell-variant
 
19
  - `test/test-issue-539.json`: Set Adwaita Mono as the strongly bound default monospace font in fontconfig.
20
  Format: fontconfig test-conf JSON (fonts, load_xml, tests with method match, pattern or scan; parsed by json-c, which accepts trailing commas that strict JSON parsers reject) plus a fontconfig XML config file
21
  Origin: JSON test cases of fontconfig's test-conf runner (test/*.json, format in test/TEST-JSON-FORMAT.md), each with the config file it tests (tool_fixture)
 
 
22
  Check: Final configuration state, no screenshot needed. Load the agent's fontconfig XML file in place of %test%/test-issue-539.conf, together with the conf.d files the JSON lists in load_xml, into fontconfig at the pinned commit and run the JSON's tests with the test-conf runner (test/test-conf test/test-issue-539.json); every test must return the expected result (the runner compares each listed property exactly). Equivalently, on a system with only the JSON's fake fonts, `fc-match` on each query must print the expected family. The JSON loads conf.d/48-guessfamily.conf, 48-spacing.conf, 49-sansserif.conf and 60-latin.conf around the test conf; they are fetched and listed as companions
23
  Tools: write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
24
  Companions (not included): test/test-issue-539.conf; conf.d/48-guessfamily.conf; conf.d/48-spacing.conf; conf.d/49-sansserif.conf; conf.d/60-latin.conf; test/TEST-JSON-FORMAT.md; COPYING
 
26
  - `test/test-issue-525.json`: Make Lato the preferred system-ui font in fontconfig.
27
  Format: fontconfig test-conf JSON (fonts, load_xml, tests with method match, pattern or scan; parsed by json-c, which accepts trailing commas that strict JSON parsers reject) plus a fontconfig XML config file
28
  Origin: JSON test cases of fontconfig's test-conf runner (test/*.json, format in test/TEST-JSON-FORMAT.md), each with the config file it tests (tool_fixture)
 
 
29
  Check: Final configuration state, no screenshot needed. Load the agent's fontconfig XML file in place of %test%/test-issue-525.conf, together with the conf.d files the JSON lists in load_xml, into fontconfig at the pinned commit and run the JSON's tests with the test-conf runner (test/test-conf test/test-issue-525.json); every test must return the expected result (the runner compares each listed property exactly). Equivalently, on a system with only the JSON's fake fonts, `fc-match` on each query must print the expected family. The JSON loads conf.d/48-guessfamily.conf, 49-sansserif.conf and 60-latin.conf around the test conf; they are fetched and listed as companions
30
  Tools: write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
31
  Companions (not included): test/test-issue-525.conf; conf.d/48-guessfamily.conf; conf.d/49-sansserif.conf; conf.d/60-latin.conf; test/TEST-JSON-FORMAT.md; COPYING
 
33
  - `test/test-issue-525-2.json`: Make Lato the preferred font for the -apple-system family name in fontconfig.
34
  Format: fontconfig test-conf JSON (fonts, load_xml, tests with method match, pattern or scan; parsed by json-c, which accepts trailing commas that strict JSON parsers reject) plus a fontconfig XML config file
35
  Origin: JSON test cases of fontconfig's test-conf runner (test/*.json, format in test/TEST-JSON-FORMAT.md), each with the config file it tests (tool_fixture)
 
36
  Check: Final configuration state, no screenshot needed. Load the agent's fontconfig XML file in place of %test%/test-issue-525-2.conf, together with the conf.d files the JSON lists in load_xml, into fontconfig at the pinned commit and run the JSON's tests with the test-conf runner (test/test-conf test/test-issue-525-2.json); every test must return the expected result (the runner compares each listed property exactly). Equivalently, on a system with only the JSON's fake fonts, `fc-match` on each query must print the expected family. The JSON loads conf.d/48-guessfamily.conf, 49-sansserif.conf and 60-latin.conf around the test conf; they are fetched and listed as companions
37
  Tools: write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
38
  Companions (not included): test/test-issue-525-2.conf; conf.d/48-guessfamily.conf; conf.d/49-sansserif.conf; conf.d/60-latin.conf; test/TEST-JSON-FORMAT.md; COPYING
 
40
  - `test/test-genericfamily.json`: Set Foo and Baz as preferred sans-serif fonts and Bar as preferred serif font in fontconfig.
41
  Format: fontconfig test-conf JSON (fonts, load_xml, tests with method match, pattern or scan; parsed by json-c, which accepts trailing commas that strict JSON parsers reject) plus a fontconfig XML config file
42
  Origin: JSON test cases of fontconfig's test-conf runner (test/*.json, format in test/TEST-JSON-FORMAT.md), each with the config file it tests (tool_fixture)
 
 
43
  Check: Final configuration state, no screenshot needed. Load the agent's fontconfig XML file in place of %test%/test-genericfamily.conf, together with the conf.d files the JSON lists in load_xml, into fontconfig at the pinned commit and run the JSON's tests with the test-conf runner (test/test-conf test/test-genericfamily.json); every test must return the expected result (the runner compares each listed property exactly). Equivalently, on a system with only the JSON's fake fonts, `fc-match` on each query must print the expected family. The JSON loads only the test conf, so no conf.d companion is needed
44
  Tools: write the fontconfig XML file (an <alias> with <prefer>) into ~/.config/fontconfig/conf.d with a text editor or a script, then query the effect with `fc-match 'monospace:spacing=100'` or `fc-match -s system-ui`, or run fontconfig's own JSON test runner (test/test-conf at the pinned commit) on the unit's JSON with the agent's file in place of the %test% conf
45
  Companions (not included): test/test-genericfamily.conf; test/TEST-JSON-FORMAT.md; COPYING
campaign_files/2026-10-gt-browser-tests-2/freecad-cam-post-tests/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 6 of 6 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: golden_output_strings. 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:** FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "grbl").export(), then write the G-code text to a file. Other files: see the notes.
14
 
15
  **Licence (SPDX):** LGPL-2.1-or-later AND CC-BY-4.0 AND EUPL-1.2 AND LGPL-2.1-or-later AND CC-BY-4.0 AND LGPL-2.1-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `src/Mod/CAM/CAMTests/TestGrblPost.py`: FreeCAD CAM: post-process a box profile job to Grbl G-code under the post processor options.
22
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
23
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
24
- Reference result: golden_output_strings
25
- Reference source: the expected G-code strings and line checks written inline in src/Mod/CAM/CAMTests/TestGrblPost.py
26
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and only the line count when the time-stamped header is on. No screenshot
27
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "grbl").export(), then write the G-code text to a file
28
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
@@ -30,8 +26,6 @@ Files:
30
  - `src/Mod/CAM/CAMTests/TestMach3Mach4Post.py`: FreeCAD CAM: post-process a box profile job to Mach3/Mach4 G-code under the post processor options.
31
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
32
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
33
- Reference result: golden_output_strings
34
- Reference source: the expected G-code strings and line checks written inline in src/Mod/CAM/CAMTests/TestMach3Mach4Post.py
35
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and only the line count when the time-stamped header is on. No screenshot
36
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "mach3_mach4").export(), then write the G-code text to a file
37
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
@@ -39,8 +33,6 @@ Files:
39
  - `src/Mod/CAM/CAMTests/TestCentroidPost.py`: FreeCAD CAM: post-process a box profile job to Centroid G-code under the post processor options.
40
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
41
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
42
- Reference result: golden_output_strings
43
- Reference source: the expected G-code strings and line checks written inline in src/Mod/CAM/CAMTests/TestCentroidPost.py
44
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and only the line count when the time-stamped header is on. No screenshot
45
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "centroid").export(), then write the G-code text to a file
46
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
@@ -48,8 +40,6 @@ Files:
48
  - `src/Mod/CAM/CAMTests/TestSnapmakerPost.py`: FreeCAD CAM: post-process a box profile job to Snapmaker 2 CNC G-code with machine and toolhead options.
49
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
50
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
51
- Reference result: golden_output_strings
52
- Reference source: the expected G-code strings and line checks written inline in src/Mod/CAM/CAMTests/TestSnapmakerPost.py
53
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and the time-stamped header line by regular expression. No screenshot
54
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "snapmaker_legacy").export(), then write the G-code text to a file
55
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
@@ -57,8 +47,6 @@ Files:
57
  - `src/Mod/CAM/CAMTests/TestMassoG3Post.py`: FreeCAD CAM: post-process a box profile job to Masso G3 G-code under the post processor options.
58
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
59
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
60
- Reference result: golden_output_strings
61
- Reference source: the expected G-code strings and line checks written inline in src/Mod/CAM/CAMTests/TestMassoG3Post.py
62
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and only the line count when the time-stamped header is on. No screenshot
63
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "masso_g3").export(), then write the G-code text to a file
64
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
@@ -66,8 +54,6 @@ Files:
66
  - `src/Mod/CAM/CAMTests/TestKineticNCBeamicon2LegacyPost.py`: FreeCAD CAM: run the KineticNC Beamicon2 legacy post processor with given options and write the expected G-code (default and overridden preamble and postamble).
67
  Format: Python unittest file whose inline expected G-code strings are the goldens; input is a Path::Feature built in a new document
68
  Origin: FreeCAD CAM workbench post-processor unit test (regression guard for issue #31387), written by the FreeCAD developers (tool_fixture)
69
- Reference result: golden_output_strings
70
- Reference source: the expected G-code strings and line checks written inline in src/Mod/CAM/CAMTests/TestKineticNCBeamicon2LegacyPost.py
71
  Check: Final file state: the G-code text the post processor writes (the content of the .nc file) is compared with the expected text: whole-output exact equality in test000 and test010, three named lines in test020. No screenshot
72
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.newDocument(), add a Path::Feature with the given commands, import Path.Post.scripts.KineticNCBeamicon2_legacy_post and call export([obj], "-", args) with the option string (for example "--no-header --no-comments --no-show-editor --preamble=... --postamble=..."), then write the returned G-code to a .nc file
73
  Companions (not included): src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only); LICENSE (licence)
 
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 6 of 6 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:** FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "grbl").export(), then write the G-code text to a file. Other files: see the notes.
12
 
13
  **Licence (SPDX):** LGPL-2.1-or-later AND CC-BY-4.0 AND EUPL-1.2 AND LGPL-2.1-or-later AND CC-BY-4.0 AND LGPL-2.1-or-later
 
19
  - `src/Mod/CAM/CAMTests/TestGrblPost.py`: FreeCAD CAM: post-process a box profile job to Grbl G-code under the post processor options.
20
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
21
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
 
 
22
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and only the line count when the time-stamped header is on. No screenshot
23
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "grbl").export(), then write the G-code text to a file
24
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
 
26
  - `src/Mod/CAM/CAMTests/TestMach3Mach4Post.py`: FreeCAD CAM: post-process a box profile job to Mach3/Mach4 G-code under the post processor options.
27
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
28
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
 
 
29
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and only the line count when the time-stamped header is on. No screenshot
30
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "mach3_mach4").export(), then write the G-code text to a file
31
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
 
33
  - `src/Mod/CAM/CAMTests/TestCentroidPost.py`: FreeCAD CAM: post-process a box profile job to Centroid G-code under the post processor options.
34
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
35
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
 
 
36
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and only the line count when the time-stamped header is on. No screenshot
37
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "centroid").export(), then write the G-code text to a file
38
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
 
40
  - `src/Mod/CAM/CAMTests/TestSnapmakerPost.py`: FreeCAD CAM: post-process a box profile job to Snapmaker 2 CNC G-code with machine and toolhead options.
41
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
42
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
 
 
43
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and the time-stamped header line by regular expression. No screenshot
44
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "snapmaker_legacy").export(), then write the G-code text to a file
45
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
 
47
  - `src/Mod/CAM/CAMTests/TestMassoG3Post.py`: FreeCAD CAM: post-process a box profile job to Masso G3 G-code under the post processor options.
48
  Format: FreeCAD document (.fcstd zip) with a CAM Job as input; Python unittest file whose expected G-code strings are the goldens
49
  Origin: FreeCAD CAM workbench post-processor unit test with its fixture document, written by the FreeCAD developers (tool_fixture)
 
 
50
  Check: Final file state: the G-code text the post processor writes (export()[0][1], the content of the .nc file) is compared with the expected strings of the test: whole-output exact equality for the multi-line cases, one line by index for the single-line cases, and only the line count when the time-stamped header is on. No screenshot
51
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.open("boxtest.fcstd"), take the Job, set job.PostProcessorArgs (for example "--no-header --no-show-editor"), replace the Profile operation Path with the given commands, and call PostProcessorFactory.get_post_processor(job, "masso_g3").export(), then write the G-code text to a file
52
  Companions (not included): src/Mod/CAM/CAMTests/boxtest.fcstd (the FreeCAD document with the box model and the CAM Job the test opens); src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only)
 
54
  - `src/Mod/CAM/CAMTests/TestKineticNCBeamicon2LegacyPost.py`: FreeCAD CAM: run the KineticNC Beamicon2 legacy post processor with given options and write the expected G-code (default and overridden preamble and postamble).
55
  Format: Python unittest file whose inline expected G-code strings are the goldens; input is a Path::Feature built in a new document
56
  Origin: FreeCAD CAM workbench post-processor unit test (regression guard for issue #31387), written by the FreeCAD developers (tool_fixture)
 
 
57
  Check: Final file state: the G-code text the post processor writes (the content of the .nc file) is compared with the expected text: whole-output exact equality in test000 and test010, three named lines in test020. No screenshot
58
  Tools: FreeCADCmd (headless) runs a Python script: FreeCAD.newDocument(), add a Path::Feature with the given commands, import Path.Post.scripts.KineticNCBeamicon2_legacy_post and call export([obj], "-", args) with the option string (for example "--no-header --no-comments --no-show-editor --preamble=... --postamble=..."), then write the returned G-code to a .nc file
59
  Companions (not included): src/Mod/CAM/CAMTests/PathTestUtils.py (the test base class; assertion helpers only); LICENSE (licence)
campaign_files/2026-10-gt-browser-tests-2/freecad-fem-test-calculix/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: golden_output_files. 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:** FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.boxanalysis_static.setup(doc, "ccxtools", test_mode=True) builds the analysis and femtools.ccxtools.FemToolsCcx.write_inp_file() writes the CalculiX deck; the result half loads the stored box_static.frd with FemToolsCcx.load_results(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.boxanalysis_frequency.setup(doc, "ccxtools", test_mode=True) builds the analysis and femtools.ccxtools.FemToolsCcx.write_inp_file() writes the CalculiX deck; the result half loads the stored box_frequency.frd with FemToolsCcx.load_results(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.ccx_cantilever_faceload.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
14
 
15
  **Licence (SPDX):** LGPL-2.1-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `src/Mod/Fem/femtest/data/calculix/box_static.inp`: FreeCAD FEM: set up the static box analysis headless and write a CalculiX input deck matching the golden; read back the stored results.
22
  Format: FreeCAD FEM example script (Python) as task input; CalculiX/Abaqus .inp deck as golden; CalculiX .frd/.dat results with 13 expected statistics as the second golden
23
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
24
- Reference result: golden_output_files
25
- Reference source: src/Mod/Fem/femtest/data/calculix/box_static.inp (written-deck golden) and box_static_expected_values (result statistics), test_ccxtools.py lines 101-124
26
  Check: Final file state, two judges. Input: compare the agent's .inp with the golden by support_utils.compare_inp_files (test_ccxtools.py line 379): skip the stamp lines, then a line diff where numbers equal within 1e-10 count as equal. Results: read the stored .frd into the analysis and compare the 13 statistics of result object CCX_Results with box_static_expected_values by support_utils.compare_stats (test_ccxtools.py lines 435-436). No screenshot
27
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.boxanalysis_static.setup(doc, "ccxtools", test_mode=True) builds the analysis and femtools.ccxtools.FemToolsCcx.write_inp_file() writes the CalculiX deck; the result half loads the stored box_static.frd with FemToolsCcx.load_results()
28
  Companions (not included): src/Mod/Fem/femexamples/boxanalysis_static.py and boxanalysis_base.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_boxanalysis_tetra10.py (stored mesh used when Gmsh is absent, boxanalysis_base.py line 80); src/Mod/Fem/femtest/data/calculix/box_static.frd and box_static.dat (stored CalculiX results to read back); src/Mod/Fem/femtest/data/calculix/box_static_expected_values (13 expected result statistics; the answer, hide); src/Mod/Fem/femtest/app/test_ccxtools.py (test_box_static, input_file_writing_test, result_reading_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
@@ -30,8 +26,6 @@ Files:
30
  - `src/Mod/Fem/femtest/data/calculix/box_frequency.inp`: FreeCAD FEM: set up the frequency (eigenmode) box analysis headless and write a CalculiX input deck matching the golden; read back mode 1.
31
  Format: FreeCAD FEM example script (Python) as task input; CalculiX/Abaqus .inp deck as golden; CalculiX .frd/.dat results with 13 expected statistics as the second golden
32
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
33
- Reference result: golden_output_files
34
- Reference source: src/Mod/Fem/femtest/data/calculix/box_frequency.inp (written-deck golden) and box_frequency_expected_values (result statistics), test_ccxtools.py lines 77-99
35
  Check: Final file state, two judges. Input: compare the agent's .inp with the golden by support_utils.compare_inp_files (test_ccxtools.py line 379): skip the stamp lines, then a line diff where numbers equal within 1e-10 count as equal. Results: read the stored .frd into the analysis and compare the 13 statistics of result object CCX_EigenMode_1_Results with box_frequency_expected_values by support_utils.compare_stats (test_ccxtools.py lines 435-436). No screenshot
36
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.boxanalysis_frequency.setup(doc, "ccxtools", test_mode=True) builds the analysis and femtools.ccxtools.FemToolsCcx.write_inp_file() writes the CalculiX deck; the result half loads the stored box_frequency.frd with FemToolsCcx.load_results()
37
  Companions (not included): src/Mod/Fem/femexamples/boxanalysis_frequency.py and boxanalysis_base.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_boxanalysis_tetra10.py (stored mesh used when Gmsh is absent, boxanalysis_base.py line 80); src/Mod/Fem/femtest/data/calculix/box_frequency.frd and box_frequency.dat (stored CalculiX results to read back); src/Mod/Fem/femtest/data/calculix/box_frequency_expected_values (13 expected result statistics; the answer, hide); src/Mod/Fem/femtest/app/test_ccxtools.py (test_box_frequency, input_file_writing_test, result_reading_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
@@ -39,8 +33,6 @@ Files:
39
  - `src/Mod/Fem/femtest/data/calculix/ccx_cantilever_faceload.inp`: FreeCAD FEM: build the solid cantilever with a face load headless and write a CalculiX deck matching the golden.
40
  Format: FreeCAD FEM example script (Python) as task input; CalculiX/Abaqus .inp deck as golden
41
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
42
- Reference result: golden_output_files
43
- Reference source: src/Mod/Fem/femtest/data/calculix/ccx_cantilever_faceload.inp (test_ccxtools.py lines 203-207)
44
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
45
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.ccx_cantilever_faceload.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
46
  Companions (not included): src/Mod/Fem/femexamples/ccx_cantilever_faceload.py and ccx_cantilever_base_solid.py (the setup script); src/Mod/Fem/femexamples/meshes/mesh_canticcx_tetra10.py (stored mesh used when Gmsh is absent, ccx_cantilever_base_solid.py line 109); src/Mod/Fem/femtest/app/test_ccxtools.py (test_ccx_cantilever_faceload, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
 
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:** FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.boxanalysis_static.setup(doc, "ccxtools", test_mode=True) builds the analysis and femtools.ccxtools.FemToolsCcx.write_inp_file() writes the CalculiX deck; the result half loads the stored box_static.frd with FemToolsCcx.load_results(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.boxanalysis_frequency.setup(doc, "ccxtools", test_mode=True) builds the analysis and femtools.ccxtools.FemToolsCcx.write_inp_file() writes the CalculiX deck; the result half loads the stored box_frequency.frd with FemToolsCcx.load_results(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.ccx_cantilever_faceload.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
12
 
13
  **Licence (SPDX):** LGPL-2.1-or-later
 
19
  - `src/Mod/Fem/femtest/data/calculix/box_static.inp`: FreeCAD FEM: set up the static box analysis headless and write a CalculiX input deck matching the golden; read back the stored results.
20
  Format: FreeCAD FEM example script (Python) as task input; CalculiX/Abaqus .inp deck as golden; CalculiX .frd/.dat results with 13 expected statistics as the second golden
21
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
 
 
22
  Check: Final file state, two judges. Input: compare the agent's .inp with the golden by support_utils.compare_inp_files (test_ccxtools.py line 379): skip the stamp lines, then a line diff where numbers equal within 1e-10 count as equal. Results: read the stored .frd into the analysis and compare the 13 statistics of result object CCX_Results with box_static_expected_values by support_utils.compare_stats (test_ccxtools.py lines 435-436). No screenshot
23
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.boxanalysis_static.setup(doc, "ccxtools", test_mode=True) builds the analysis and femtools.ccxtools.FemToolsCcx.write_inp_file() writes the CalculiX deck; the result half loads the stored box_static.frd with FemToolsCcx.load_results()
24
  Companions (not included): src/Mod/Fem/femexamples/boxanalysis_static.py and boxanalysis_base.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_boxanalysis_tetra10.py (stored mesh used when Gmsh is absent, boxanalysis_base.py line 80); src/Mod/Fem/femtest/data/calculix/box_static.frd and box_static.dat (stored CalculiX results to read back); src/Mod/Fem/femtest/data/calculix/box_static_expected_values (13 expected result statistics; the answer, hide); src/Mod/Fem/femtest/app/test_ccxtools.py (test_box_static, input_file_writing_test, result_reading_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
 
26
  - `src/Mod/Fem/femtest/data/calculix/box_frequency.inp`: FreeCAD FEM: set up the frequency (eigenmode) box analysis headless and write a CalculiX input deck matching the golden; read back mode 1.
27
  Format: FreeCAD FEM example script (Python) as task input; CalculiX/Abaqus .inp deck as golden; CalculiX .frd/.dat results with 13 expected statistics as the second golden
28
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
 
 
29
  Check: Final file state, two judges. Input: compare the agent's .inp with the golden by support_utils.compare_inp_files (test_ccxtools.py line 379): skip the stamp lines, then a line diff where numbers equal within 1e-10 count as equal. Results: read the stored .frd into the analysis and compare the 13 statistics of result object CCX_EigenMode_1_Results with box_frequency_expected_values by support_utils.compare_stats (test_ccxtools.py lines 435-436). No screenshot
30
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.boxanalysis_frequency.setup(doc, "ccxtools", test_mode=True) builds the analysis and femtools.ccxtools.FemToolsCcx.write_inp_file() writes the CalculiX deck; the result half loads the stored box_frequency.frd with FemToolsCcx.load_results()
31
  Companions (not included): src/Mod/Fem/femexamples/boxanalysis_frequency.py and boxanalysis_base.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_boxanalysis_tetra10.py (stored mesh used when Gmsh is absent, boxanalysis_base.py line 80); src/Mod/Fem/femtest/data/calculix/box_frequency.frd and box_frequency.dat (stored CalculiX results to read back); src/Mod/Fem/femtest/data/calculix/box_frequency_expected_values (13 expected result statistics; the answer, hide); src/Mod/Fem/femtest/app/test_ccxtools.py (test_box_frequency, input_file_writing_test, result_reading_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
 
33
  - `src/Mod/Fem/femtest/data/calculix/ccx_cantilever_faceload.inp`: FreeCAD FEM: build the solid cantilever with a face load headless and write a CalculiX deck matching the golden.
34
  Format: FreeCAD FEM example script (Python) as task input; CalculiX/Abaqus .inp deck as golden
35
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
 
 
36
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
37
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the solver input with the solver's writer and save it; no GUI and no solver run needed; here femexamples.ccx_cantilever_faceload.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
38
  Companions (not included): src/Mod/Fem/femexamples/ccx_cantilever_faceload.py and ccx_cantilever_base_solid.py (the setup script); src/Mod/Fem/femexamples/meshes/mesh_canticcx_tetra10.py (stored mesh used when Gmsh is absent, ccx_cantilever_base_solid.py line 109); src/Mod/Fem/femtest/app/test_ccxtools.py (test_ccx_cantilever_faceload, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
campaign_files/2026-10-gt-browser-tests-2/freecad-fem-test-elmer/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: golden_output_files. 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:** FreeCADCmd (headless) sets the unit schema to mm/kg/s, runs femexamples.boxanalysis_static.setup(doc, "elmer", test_mode=True), then femsolver.elmer.writer.Writer(doc.SolverElmer, dir, testmode=True).write_solver_input() writes case.sif and ELMERSOLVER_STARTINFO (test_solver_elmer.py lines 101-124)
14
 
15
  **Licence (SPDX):** LGPL-2.1-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `src/Mod/Fem/femtest/data/elmer/box_static_0_mm.sif`: FreeCAD FEM: write the Elmer case file (case.sif) and start file for the static box in mm units, matching the golden.
22
  Format: FreeCAD FEM example script (Python) as task input; Elmer solver input file (.sif) and ELMERSOLVER_STARTINFO as goldens
23
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
24
- Reference result: golden_output_files
25
- Reference source: src/Mod/Fem/femtest/data/elmer/box_static_0_mm.sif and ELMERSOLVER_STARTINFO (test_solver_elmer.py lines 99-138; ending .sif and output name case at lines 53-54)
26
  Check: Final file state: compare the agent's case.sif and ELMERSOLVER_STARTINFO with the goldens by support_utils.compare_files (test_solver_elmer.py lines 130 and 137): drop the lines it ignores, then an exact line diff (no numeric tolerance). No screenshot
27
  Tools: FreeCADCmd (headless) sets the unit schema to mm/kg/s, runs femexamples.boxanalysis_static.setup(doc, "elmer", test_mode=True), then femsolver.elmer.writer.Writer(doc.SolverElmer, dir, testmode=True).write_solver_input() writes case.sif and ELMERSOLVER_STARTINFO (test_solver_elmer.py lines 101-124)
28
  Companions (not included): src/Mod/Fem/femexamples/boxanalysis_static.py and boxanalysis_base.py (the setup script); src/Mod/Fem/femexamples/meshes/mesh_boxanalysis_tetra10.py (stored mesh); src/Mod/Fem/femtest/data/elmer/ELMERSOLVER_STARTINFO (second golden; the answer, hide); src/Mod/Fem/femtest/app/test_solver_elmer.py (test_box_static_0_mm); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
 
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:** FreeCADCmd (headless) sets the unit schema to mm/kg/s, runs femexamples.boxanalysis_static.setup(doc, "elmer", test_mode=True), then femsolver.elmer.writer.Writer(doc.SolverElmer, dir, testmode=True).write_solver_input() writes case.sif and ELMERSOLVER_STARTINFO (test_solver_elmer.py lines 101-124)
12
 
13
  **Licence (SPDX):** LGPL-2.1-or-later
 
19
  - `src/Mod/Fem/femtest/data/elmer/box_static_0_mm.sif`: FreeCAD FEM: write the Elmer case file (case.sif) and start file for the static box in mm units, matching the golden.
20
  Format: FreeCAD FEM example script (Python) as task input; Elmer solver input file (.sif) and ELMERSOLVER_STARTINFO as goldens
21
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
 
 
22
  Check: Final file state: compare the agent's case.sif and ELMERSOLVER_STARTINFO with the goldens by support_utils.compare_files (test_solver_elmer.py lines 130 and 137): drop the lines it ignores, then an exact line diff (no numeric tolerance). No screenshot
23
  Tools: FreeCADCmd (headless) sets the unit schema to mm/kg/s, runs femexamples.boxanalysis_static.setup(doc, "elmer", test_mode=True), then femsolver.elmer.writer.Writer(doc.SolverElmer, dir, testmode=True).write_solver_input() writes case.sif and ELMERSOLVER_STARTINFO (test_solver_elmer.py lines 101-124)
24
  Companions (not included): src/Mod/Fem/femexamples/boxanalysis_static.py and boxanalysis_base.py (the setup script); src/Mod/Fem/femexamples/meshes/mesh_boxanalysis_tetra10.py (stored mesh); src/Mod/Fem/femtest/data/elmer/ELMERSOLVER_STARTINFO (second golden; the answer, hide); src/Mod/Fem/femtest/app/test_solver_elmer.py (test_box_static_0_mm); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
campaign_files/2026-10-gt-browser-tests-2/freecad-fem-test-mystran/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. 2 of 2 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: golden_output_files. 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:** FreeCADCmd (headless) runs femexamples.ccx_cantilever_faceload.setup(doc, "mystran", test_mode=True), then the MYSTRAN solver machine with target PREPARE and testmode True writes Mesh.bdf (test_solver_mystran.py lines 132-137); FreeCADCmd (headless) runs femexamples.mystran_plate.setup(doc, "mystran", test_mode=True) (plate split into faces with BOPTools, quad4 shell mesh from the stored mesh module), then the MYSTRAN solver machine with target PREPARE writes Mesh.bdf
14
 
15
  **Licence (SPDX):** LGPL-2.1-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `src/Mod/Fem/femtest/data/mystran/ccx_cantilever_faceload.bdf`: FreeCAD FEM: write the cantilever face-load model as a MYSTRAN (Nastran bulk data) deck matching the golden.
22
  Format: FreeCAD FEM example script (Python) as task input; Nastran bulk data .bdf as golden
23
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
24
- Reference result: golden_output_files
25
- Reference source: src/Mod/Fem/femtest/data/mystran/ccx_cantilever_faceload.bdf (test_solver_mystran.py lines 98-104; file ending .bdf and output name Mesh at lines 53-54)
26
  Check: Final file state: compare the agent's Mesh.bdf with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), test_solver_mystran.py line 143. No screenshot
27
  Tools: FreeCADCmd (headless) runs femexamples.ccx_cantilever_faceload.setup(doc, "mystran", test_mode=True), then the MYSTRAN solver machine with target PREPARE and testmode True writes Mesh.bdf (test_solver_mystran.py lines 132-137)
28
  Companions (not included): src/Mod/Fem/femexamples/ccx_cantilever_faceload.py and ccx_cantilever_base_solid.py (the setup script); src/Mod/Fem/femexamples/meshes/mesh_canticcx_tetra10.py (stored mesh used when Gmsh is absent, ccx_cantilever_base_solid.py line 109); src/Mod/Fem/femtest/app/test_solver_mystran.py (test_ccx_cantilever_faceload, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
@@ -30,8 +26,6 @@ Files:
30
  - `src/Mod/Fem/femtest/data/mystran/mystran_plate.bdf`: FreeCAD FEM: build the MYSTRAN shell plate example headless and write a .bdf deck matching the golden.
31
  Format: FreeCAD FEM example script (Python) as task input; Nastran bulk data .bdf as golden
32
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
33
- Reference result: golden_output_files
34
- Reference source: src/Mod/Fem/femtest/data/mystran/mystran_plate.bdf (test_solver_mystran.py lines 114-119)
35
  Check: Final file state: compare the agent's Mesh.bdf with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), test_solver_mystran.py line 143. No screenshot
36
  Tools: FreeCADCmd (headless) runs femexamples.mystran_plate.setup(doc, "mystran", test_mode=True) (plate split into faces with BOPTools, quad4 shell mesh from the stored mesh module), then the MYSTRAN solver machine with target PREPARE writes Mesh.bdf
37
  Companions (not included): src/Mod/Fem/femexamples/mystran_plate.py (the setup script); src/Mod/Fem/femexamples/meshes/mesh_plate_mystran_quad4.py (stored mesh, mystran_plate.py lines 183-185); src/Mod/Fem/femtest/app/test_solver_mystran.py (test_mystran_plate, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 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:** FreeCADCmd (headless) runs femexamples.ccx_cantilever_faceload.setup(doc, "mystran", test_mode=True), then the MYSTRAN solver machine with target PREPARE and testmode True writes Mesh.bdf (test_solver_mystran.py lines 132-137); FreeCADCmd (headless) runs femexamples.mystran_plate.setup(doc, "mystran", test_mode=True) (plate split into faces with BOPTools, quad4 shell mesh from the stored mesh module), then the MYSTRAN solver machine with target PREPARE writes Mesh.bdf
12
 
13
  **Licence (SPDX):** LGPL-2.1-or-later
 
19
  - `src/Mod/Fem/femtest/data/mystran/ccx_cantilever_faceload.bdf`: FreeCAD FEM: write the cantilever face-load model as a MYSTRAN (Nastran bulk data) deck matching the golden.
20
  Format: FreeCAD FEM example script (Python) as task input; Nastran bulk data .bdf as golden
21
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
 
 
22
  Check: Final file state: compare the agent's Mesh.bdf with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), test_solver_mystran.py line 143. No screenshot
23
  Tools: FreeCADCmd (headless) runs femexamples.ccx_cantilever_faceload.setup(doc, "mystran", test_mode=True), then the MYSTRAN solver machine with target PREPARE and testmode True writes Mesh.bdf (test_solver_mystran.py lines 132-137)
24
  Companions (not included): src/Mod/Fem/femexamples/ccx_cantilever_faceload.py and ccx_cantilever_base_solid.py (the setup script); src/Mod/Fem/femexamples/meshes/mesh_canticcx_tetra10.py (stored mesh used when Gmsh is absent, ccx_cantilever_base_solid.py line 109); src/Mod/Fem/femtest/app/test_solver_mystran.py (test_ccx_cantilever_faceload, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
 
26
  - `src/Mod/Fem/femtest/data/mystran/mystran_plate.bdf`: FreeCAD FEM: build the MYSTRAN shell plate example headless and write a .bdf deck matching the golden.
27
  Format: FreeCAD FEM example script (Python) as task input; Nastran bulk data .bdf as golden
28
  Origin: FreeCAD FEM workbench unit-test fixture written by the FreeCAD developers (tool_fixture)
 
 
29
  Check: Final file state: compare the agent's Mesh.bdf with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), test_solver_mystran.py line 143. No screenshot
30
  Tools: FreeCADCmd (headless) runs femexamples.mystran_plate.setup(doc, "mystran", test_mode=True) (plate split into faces with BOPTools, quad4 shell mesh from the stored mesh module), then the MYSTRAN solver machine with target PREPARE writes Mesh.bdf
31
  Companions (not included): src/Mod/Fem/femexamples/mystran_plate.py (the setup script); src/Mod/Fem/femexamples/meshes/mesh_plate_mystran_quad4.py (stored mesh, mystran_plate.py lines 183-185); src/Mod/Fem/femtest/app/test_solver_mystran.py (test_mystran_plate, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files, compare_files, compare_stats); LICENSE (licence)
campaign_files/2026-10-gt-browser-tests-2/freecad-femtest-calculix/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 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: golden_output_files. 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:** FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.ccx_buckling_flexuralbuckling.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.constraint_selfweight_cantilever.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.material_multiple_bendingbeam_fivefaces.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.square_pipe_end_twisted_edgeforces.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.thermomech_bimetal.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
14
 
15
  **Licence (SPDX):** LGPL-2.1-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `src/Mod/Fem/femtest/data/calculix/ccx_buckling_flexuralbuckling.inp`: FreeCAD FEM: build the Flexural Buckling example headless and write a CalculiX deck matching the golden.
22
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
23
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
24
- Reference result: golden_output_files
25
- Reference source: the stored deck src/Mod/Fem/femtest/data/calculix/ccx_buckling_flexuralbuckling.inp, compared by test_ccxtools.py input_file_writing_test
26
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
27
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.ccx_buckling_flexuralbuckling.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file()
28
  Companions (not included): src/Mod/Fem/femexamples/ccx_buckling_flexuralbuckling.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_flexural_buckling.py (stored mesh: the setup always builds the mesh from the stored module src/Mod/Fem/femexamples/meshes/mesh_flexural_buckling.py (no mesher)); src/Mod/Fem/femtest/app/test_ccxtools.py (test_ccx_buckling_flexuralbuckling, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
@@ -30,8 +26,6 @@ Files:
30
  - `src/Mod/Fem/femtest/data/calculix/constraint_selfweight_cantilever.inp`: FreeCAD FEM: build the Constraint Self Weight Cantilever example headless and write a CalculiX deck matching the golden.
31
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
32
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
33
- Reference result: golden_output_files
34
- Reference source: the stored deck src/Mod/Fem/femtest/data/calculix/constraint_selfweight_cantilever.inp, compared by test_ccxtools.py input_file_writing_test
35
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
36
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.constraint_selfweight_cantilever.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
37
  Companions (not included): src/Mod/Fem/femexamples/constraint_selfweight_cantilever.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_selfweight_cantilever_tetra10.py (stored mesh: with test_mode=True (test_ccxtools.py line 261) the setup uses the stored mesh module src/Mod/Fem/femexamples/meshes/mesh_selfweight_cantilever_tetra10.py instead of Gmsh); src/Mod/Fem/femtest/app/test_ccxtools.py (test_constraint_selfweight_cantilever, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
@@ -39,8 +33,6 @@ Files:
39
  - `src/Mod/Fem/femtest/data/calculix/material_multiple_bendingbeam_fivefaces.inp`: FreeCAD FEM: build the Multimaterial bending beam 5 faces example headless and write a CalculiX deck matching the golden.
40
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
41
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
42
- Reference result: golden_output_files
43
- Reference source: the stored deck src/Mod/Fem/femtest/data/calculix/material_multiple_bendingbeam_fivefaces.inp, compared by test_ccxtools.py input_file_writing_test
44
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
45
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.material_multiple_bendingbeam_fivefaces.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file()
46
  Companions (not included): src/Mod/Fem/femexamples/material_multiple_bendingbeam_fivefaces.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_multibodybeam_tria6.py (stored mesh: the setup always builds the mesh from the stored module src/Mod/Fem/femexamples/meshes/mesh_multibodybeam_tria6.py (no mesher)); src/Mod/Fem/femtest/app/test_ccxtools.py (test_material_multiple_bendingbeam_fivefaces, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
@@ -48,8 +40,6 @@ Files:
48
  - `src/Mod/Fem/femtest/data/calculix/square_pipe_end_twisted_edgeforces.inp`: FreeCAD FEM: build the Square Pipe End Twisted Edgeforces example headless and write a CalculiX deck matching the golden.
49
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
50
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
51
- Reference result: golden_output_files
52
- Reference source: the stored deck src/Mod/Fem/femtest/data/calculix/square_pipe_end_twisted_edgeforces.inp, compared by test_ccxtools.py input_file_writing_test
53
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
54
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.square_pipe_end_twisted_edgeforces.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file()
55
  Companions (not included): src/Mod/Fem/femexamples/square_pipe_end_twisted_edgeforces.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_square_pipe_end_twisted_tria6.py (stored mesh: the setup always builds the mesh from the stored module src/Mod/Fem/femexamples/meshes/mesh_square_pipe_end_twisted_tria6.py (no mesher)); src/Mod/Fem/femtest/app/test_ccxtools.py (test_square_pipe_end_twisted_edgeforces, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
@@ -57,8 +47,6 @@ Files:
57
  - `src/Mod/Fem/femtest/data/calculix/thermomech_bimetal.inp`: FreeCAD FEM: build the Thermomech Bimetal example headless and write a CalculiX deck matching the golden.
58
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
59
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
60
- Reference result: golden_output_files
61
- Reference source: the stored deck src/Mod/Fem/femtest/data/calculix/thermomech_bimetal.inp, compared by test_ccxtools.py input_file_writing_test
62
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
63
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.thermomech_bimetal.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
64
  Companions (not included): src/Mod/Fem/femexamples/thermomech_bimetal.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_thermomech_bimetal_tetra10.py (stored mesh: with test_mode=True (test_ccxtools.py line 338) the setup uses the stored mesh module src/Mod/Fem/femexamples/meshes/mesh_thermomech_bimetal_tetra10.py instead of Gmsh); src/Mod/Fem/femtest/app/test_ccxtools.py (test_thermomech_bimetal, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
 
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 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:** FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.ccx_buckling_flexuralbuckling.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.constraint_selfweight_cantilever.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.material_multiple_bendingbeam_fivefaces.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.square_pipe_end_twisted_edgeforces.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file(); FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.thermomech_bimetal.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
12
 
13
  **Licence (SPDX):** LGPL-2.1-or-later
 
19
  - `src/Mod/Fem/femtest/data/calculix/ccx_buckling_flexuralbuckling.inp`: FreeCAD FEM: build the Flexural Buckling example headless and write a CalculiX deck matching the golden.
20
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
21
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
 
 
22
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
23
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.ccx_buckling_flexuralbuckling.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file()
24
  Companions (not included): src/Mod/Fem/femexamples/ccx_buckling_flexuralbuckling.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_flexural_buckling.py (stored mesh: the setup always builds the mesh from the stored module src/Mod/Fem/femexamples/meshes/mesh_flexural_buckling.py (no mesher)); src/Mod/Fem/femtest/app/test_ccxtools.py (test_ccx_buckling_flexuralbuckling, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
 
26
  - `src/Mod/Fem/femtest/data/calculix/constraint_selfweight_cantilever.inp`: FreeCAD FEM: build the Constraint Self Weight Cantilever example headless and write a CalculiX deck matching the golden.
27
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
28
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
 
 
29
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
30
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.constraint_selfweight_cantilever.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
31
  Companions (not included): src/Mod/Fem/femexamples/constraint_selfweight_cantilever.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_selfweight_cantilever_tetra10.py (stored mesh: with test_mode=True (test_ccxtools.py line 261) the setup uses the stored mesh module src/Mod/Fem/femexamples/meshes/mesh_selfweight_cantilever_tetra10.py instead of Gmsh); src/Mod/Fem/femtest/app/test_ccxtools.py (test_constraint_selfweight_cantilever, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
 
33
  - `src/Mod/Fem/femtest/data/calculix/material_multiple_bendingbeam_fivefaces.inp`: FreeCAD FEM: build the Multimaterial bending beam 5 faces example headless and write a CalculiX deck matching the golden.
34
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
35
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
 
 
36
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
37
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.material_multiple_bendingbeam_fivefaces.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file()
38
  Companions (not included): src/Mod/Fem/femexamples/material_multiple_bendingbeam_fivefaces.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_multibodybeam_tria6.py (stored mesh: the setup always builds the mesh from the stored module src/Mod/Fem/femexamples/meshes/mesh_multibodybeam_tria6.py (no mesher)); src/Mod/Fem/femtest/app/test_ccxtools.py (test_material_multiple_bendingbeam_fivefaces, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
 
40
  - `src/Mod/Fem/femtest/data/calculix/square_pipe_end_twisted_edgeforces.inp`: FreeCAD FEM: build the Square Pipe End Twisted Edgeforces example headless and write a CalculiX deck matching the golden.
41
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
42
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
 
 
43
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
44
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.square_pipe_end_twisted_edgeforces.setup(doc, "ccxtools") and FemToolsCcx.write_inp_file()
45
  Companions (not included): src/Mod/Fem/femexamples/square_pipe_end_twisted_edgeforces.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_square_pipe_end_twisted_tria6.py (stored mesh: the setup always builds the mesh from the stored module src/Mod/Fem/femexamples/meshes/mesh_square_pipe_end_twisted_tria6.py (no mesher)); src/Mod/Fem/femtest/app/test_ccxtools.py (test_square_pipe_end_twisted_edgeforces, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
 
47
  - `src/Mod/Fem/femtest/data/calculix/thermomech_bimetal.inp`: FreeCAD FEM: build the Thermomech Bimetal example headless and write a CalculiX deck matching the golden.
48
  Format: FreeCAD FEM example script (Python) and stored mesh module as task input; CalculiX/Abaqus .inp deck as golden
49
  Origin: FreeCAD FEM workbench example and its golden solver input written by the FreeCAD developers (tool_fixture)
 
 
50
  Check: Final file state: compare the agent's .inp with the golden by support_utils.compare_inp_files (stamp lines skipped, numbers equal within 1e-10), as test_ccxtools.py line 379 does. No screenshot
51
  Tools: FreeCADCmd (headless) runs a Python script: open a new document, build the analysis (geometry, material, constraints, mesh, solver object), then write the CalculiX input with the writer and save it; no GUI and no solver run needed; here femexamples.thermomech_bimetal.setup(doc, "ccxtools", test_mode=True) and FemToolsCcx.write_inp_file()
52
  Companions (not included): src/Mod/Fem/femexamples/thermomech_bimetal.py (the setup script that builds the analysis); src/Mod/Fem/femexamples/meshes/mesh_thermomech_bimetal_tetra10.py (stored mesh: with test_mode=True (test_ccxtools.py line 338) the setup uses the stored mesh module src/Mod/Fem/femexamples/meshes/mesh_thermomech_bimetal_tetra10.py instead of Gmsh); src/Mod/Fem/femtest/app/test_ccxtools.py (test_thermomech_bimetal, input_file_writing_test); src/Mod/Fem/femexamples/__init__.py, manager.py, meshes/__init__.py, meshes/generate_mesh.py (example framework the setup script imports); src/Mod/Fem/femtest/app/support_utils.py (compare_inp_files); LICENSE (licence)
campaign_files/2026-10-hw-eda-tests-2/fluidnc-firmware-fixture-tests-main-at-commit-741ed9e-github-bdring-fluidnc/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 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: controller_responses. 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:** the fixture is a plain text file; an agent's predicted response list is compared with the same rules without hardware
14
 
15
  **Licence (SPDX):** GPL-3.0-or-later
@@ -20,24 +18,18 @@ Files:
20
 
21
  - `fixture_tests/fixtures/flow_control_basic.nc`
22
  Format: FluidNC fixture text: `->` lines are G-code or $ commands sent, `<-` lines are expected responses, `<~` optional responses, `<|` one-of alternatives
23
- Reference result: controller_responses
24
- Reference source: fixture_tests/fixtures/flow_control_basic.nc: the `<-` expectation lines (12 response lines for 11 sent lines) written upstream and checked by run_fixture against FluidNC hardware.
25
  Check: Judge: walk the expectation lines in order against the response lines, each response stripped of surrounding whitespace; `<-` needs exact string equality, `<~` is skipped when it does not match, `<|` accepts any listed alternative; a mismatch fails, as tool/op_entries.py does.
26
  Tools: the fixture is a plain text file; an agent's predicted response list is compared with the same rules without hardware
27
  Companions (not included): fixture_tests/run_fixture; fixture_tests/tool/op_entries.py; fixture_tests/tool/utils.py; LICENSE
28
  Dependencies: Python 3 with pyserial to run run_fixture (not packed); judging an agent answer needs only a line comparison
29
  - `fixture_tests/fixtures/flow_control_alarm.nc`
30
  Format: FluidNC fixture text: `->` lines are G-code or $ commands sent, `<-` lines are expected responses, `<~` optional responses, `<|` one-of alternatives
31
- Reference result: controller_responses
32
- Reference source: fixture_tests/fixtures/flow_control_alarm.nc: the `<-` expectation lines (8 response lines for 6 sent lines) written upstream and checked by run_fixture against FluidNC hardware.
33
  Check: Judge: walk the expectation lines in order against the response lines, each response stripped of surrounding whitespace; `<-` needs exact string equality, `<~` is skipped when it does not match, `<|` accepts any listed alternative; a mismatch fails, as tool/op_entries.py does.
34
  Tools: the fixture is a plain text file; an agent's predicted response list is compared with the same rules without hardware
35
  Companions (not included): fixture_tests/run_fixture; fixture_tests/tool/op_entries.py; fixture_tests/tool/utils.py; LICENSE
36
  Dependencies: Python 3 with pyserial to run run_fixture (not packed); judging an agent answer needs only a line comparison
37
  - `fixture_tests/fixtures/current_tool_test.nc`: Tool selection and change (T1, M6, M6T2, M61Q3, M6T0) on the FluidNC firmware: predict the $G modal state reports and the printed values of #<_current_tool> and #<_selected_tool> after each step.
38
  Format: FluidNC fixture text: `->` lines are G-code or $ commands sent, `<-` lines are expected responses, `<~` optional responses, `<|` one-of alternatives
39
- Reference result: controller_responses
40
- Reference source: fixture_tests/fixtures/current_tool_test.nc: the `<-` expectation lines (35 response lines for 20 sent lines) written upstream and checked by run_fixture against FluidNC hardware.
41
  Check: Judge: walk the expectation lines in order against the response lines, each response stripped of surrounding whitespace; `<-` needs exact string equality, `<~` is skipped when it does not match, `<|` accepts any listed alternative; a mismatch fails, as tool/op_entries.py does.
42
  Tools: the fixture is a plain text file; an agent's predicted response list is compared with the same rules without hardware
43
  Companions (not included): fixture_tests/run_fixture; fixture_tests/tool/op_entries.py; fixture_tests/tool/utils.py; LICENSE
 
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 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:** the fixture is a plain text file; an agent's predicted response list is compared with the same rules without hardware
12
 
13
  **Licence (SPDX):** GPL-3.0-or-later
 
18
 
19
  - `fixture_tests/fixtures/flow_control_basic.nc`
20
  Format: FluidNC fixture text: `->` lines are G-code or $ commands sent, `<-` lines are expected responses, `<~` optional responses, `<|` one-of alternatives
 
 
21
  Check: Judge: walk the expectation lines in order against the response lines, each response stripped of surrounding whitespace; `<-` needs exact string equality, `<~` is skipped when it does not match, `<|` accepts any listed alternative; a mismatch fails, as tool/op_entries.py does.
22
  Tools: the fixture is a plain text file; an agent's predicted response list is compared with the same rules without hardware
23
  Companions (not included): fixture_tests/run_fixture; fixture_tests/tool/op_entries.py; fixture_tests/tool/utils.py; LICENSE
24
  Dependencies: Python 3 with pyserial to run run_fixture (not packed); judging an agent answer needs only a line comparison
25
  - `fixture_tests/fixtures/flow_control_alarm.nc`
26
  Format: FluidNC fixture text: `->` lines are G-code or $ commands sent, `<-` lines are expected responses, `<~` optional responses, `<|` one-of alternatives
 
 
27
  Check: Judge: walk the expectation lines in order against the response lines, each response stripped of surrounding whitespace; `<-` needs exact string equality, `<~` is skipped when it does not match, `<|` accepts any listed alternative; a mismatch fails, as tool/op_entries.py does.
28
  Tools: the fixture is a plain text file; an agent's predicted response list is compared with the same rules without hardware
29
  Companions (not included): fixture_tests/run_fixture; fixture_tests/tool/op_entries.py; fixture_tests/tool/utils.py; LICENSE
30
  Dependencies: Python 3 with pyserial to run run_fixture (not packed); judging an agent answer needs only a line comparison
31
  - `fixture_tests/fixtures/current_tool_test.nc`: Tool selection and change (T1, M6, M6T2, M61Q3, M6T0) on the FluidNC firmware: predict the $G modal state reports and the printed values of #<_current_tool> and #<_selected_tool> after each step.
32
  Format: FluidNC fixture text: `->` lines are G-code or $ commands sent, `<-` lines are expected responses, `<~` optional responses, `<|` one-of alternatives
 
 
33
  Check: Judge: walk the expectation lines in order against the response lines, each response stripped of surrounding whitespace; `<-` needs exact string equality, `<~` is skipped when it does not match, `<|` accepts any listed alternative; a mismatch fails, as tool/op_entries.py does.
34
  Tools: the fixture is a plain text file; an agent's predicted response list is compared with the same rules without hardware
35
  Companions (not included): fixture_tests/run_fixture; fixture_tests/tool/op_entries.py; fixture_tests/tool/utils.py; LICENSE
campaign_files/2026-10-hw-eda-tests-2/fpu/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Each unit is self-contained. 8 of 8 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: self_checking_testbench_pass_fail. 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):** MIT
@@ -21,64 +19,48 @@ Units:
21
  - `adder/` (8 files): dawsonjon/fpu adder: single precision IEEE 754 adder with its Icarus Verilog testbench and C reference model.
22
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
23
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
24
- Reference result: self_checking_testbench_pass_fail
25
- Reference source: c_test/test.cpp computes a + b on 32-bit floats on the host CPU (IEEE 754, default round to nearest even) for every stimulus value; run_test.py feeds the same stimulus to the DUT through test_bench_tb, reads resp_z and compares each result with the C model; sections: regression vectors (line 99, 8 fixed values), corner cases (line 106, special values: signed zeros, infinities, NaNs), edge cases (line 114, 12 blocks of 1000 vectors, one operand fixed to a special value and the other drawn by randint); a mismatch prints `Fail ... expected: ... actual: ...` (run_test.py:72)
26
  Check: Build in a sandbox with the versions listed in dependencies: in adder/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in adder/ run run_test.py only up to line 186 (stop before `#seed(0)` at line 187 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (adder/run_test.py:9). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace adder/adder.v and keep the testbench, the driver and the C model unchanged.
27
  Companions (not included): COPYING.txt
28
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
29
  - `multiplier/` (8 files): dawsonjon/fpu multiplier: single precision IEEE 754 multiplier with its Icarus Verilog testbench and C reference model.
30
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
31
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
32
- Reference result: self_checking_testbench_pass_fail
33
- Reference source: c_test/test.cpp computes a * b on 32-bit floats on the host CPU (IEEE 754, default round to nearest even) for every stimulus value; run_test.py feeds the same stimulus to the DUT through test_bench_tb, reads resp_z and compares each result with the C model; sections: regression vectors (line 100, 6 fixed values), corner cases (line 107, special values: signed zeros, infinities, NaNs), edge cases (line 115, 12 blocks of 1000 vectors, one operand fixed to a special value and the other drawn by randint); a mismatch prints `Fail ... expected: ... actual: ...` (run_test.py:73)
34
  Check: Build in a sandbox with the versions listed in dependencies: in multiplier/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in multiplier/ run run_test.py only up to line 187 (stop before `#seed(0)` at line 188 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (multiplier/run_test.py:9). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace multiplier/multiplier.v and keep the testbench, the driver and the C model unchanged.
35
  Companions (not included): COPYING.txt
36
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
37
  - `divider/` (8 files): dawsonjon/fpu divider: single precision IEEE 754 divider with its Icarus Verilog testbench and C reference model.
38
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
39
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
40
- Reference result: self_checking_testbench_pass_fail
41
- Reference source: c_test/test.cpp computes a / b on 32-bit floats on the host CPU (IEEE 754, default round to nearest even) for every stimulus value; run_test.py feeds the same stimulus to the DUT through test_bench_tb, reads resp_z and compares each result with the C model; sections: regression vectors (line 98, 5 fixed values), corner cases (line 105, special values: signed zeros, infinities, NaNs), edge cases (line 113, 12 blocks of 1000 vectors, one operand fixed to a special value and the other drawn by randint); a mismatch prints `Fail ... expected: ... actual: ...` (run_test.py:71)
42
  Check: Build in a sandbox with the versions listed in dependencies: in divider/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in divider/ run run_test.py only up to line 185 (stop before `#seed(0)` at line 186 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (divider/run_test.py:9). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace divider/divider.v and keep the testbench, the driver and the C model unchanged.
43
  Companions (not included): COPYING.txt
44
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
45
  - `double_adder/` (8 files): dawsonjon/fpu double_adder: double precision IEEE 754 adder with its Icarus Verilog testbench and C reference model.
46
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
47
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
48
- Reference result: self_checking_testbench_pass_fail
49
- Reference source: c_test/test.cpp computes a + b on 64-bit doubles on the host CPU (IEEE 754, default round to nearest even) for every stimulus value; run_test.py feeds the same stimulus to the DUT through test_bench_tb, reads resp_z and compares each result with the C model; sections: regression vectors (line 124, 3 fixed values), corner cases (line 131, special values: signed zeros, infinities, NaNs), edge cases (line 152, 12 blocks of 1000 vectors, one operand fixed to a special value and the other drawn by randint); a mismatch prints `Fail ... expected: ... actual: ...` (run_test.py:97)
50
  Check: Build in a sandbox with the versions listed in dependencies: in double_adder/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in double_adder/ run run_test.py only up to line 224 (stop before `#seed(0)` at line 225 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (double_adder/run_test.py:17). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace double_adder/double_adder.v and keep the testbench, the driver and the C model unchanged.
51
  Companions (not included): COPYING.txt
52
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
53
  - `int_to_float/` (7 files): dawsonjon/fpu int_to_float: 32-bit integer to single precision float converter with its Icarus Verilog testbench and C reference model.
54
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
55
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
56
- Reference result: self_checking_testbench_pass_fail
57
- Reference source: c_test/test.cpp computes float(int32) on the host CPU (IEEE 754, default round to nearest even) for every stimulus value; run_test.py feeds the same stimulus to the DUT through test_bench_tb, reads resp_z and compares each result with the C model; sections: regression vectors (line 73, 9 fixed values), corner cases (line 80, special values: signed zeros, infinities, NaNs); a mismatch prints `Fail ... expected: ... actual: ...` (run_test.py:53)
58
  Check: Build in a sandbox with the versions listed in dependencies: in int_to_float/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in int_to_float/ run run_test.py as shipped: it calls exit(0) at line 78 right after the regression block, so only the 9 regression vectors run (the corner block at line 80 and the random loop at line 87 are never reached). The driver compiles with iverilog (int_to_float/run_test.py:10). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace int_to_float/int_to_float.v and keep the testbench, the driver and the C model unchanged.
59
  Companions (not included): COPYING.txt
60
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
61
  - `float_to_int/` (7 files): dawsonjon/fpu float_to_int: single precision float to 32-bit integer converter with its Icarus Verilog testbench and C reference model.
62
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
63
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
64
- Reference result: self_checking_testbench_pass_fail
65
- Reference source: c_test/test.cpp computes (int) of a 32-bit float on the host CPU (IEEE 754, default round to nearest even) for every stimulus value; run_test.py feeds the same stimulus to the DUT through test_bench_tb, reads resp_z and compares each result with the C model; sections: regression vectors (line 74, 7 fixed values), corner cases (line 80, special values: signed zeros, infinities, NaNs); a mismatch prints `Fail ... expected: ... actual: ...` (run_test.py:53)
66
  Check: Build in a sandbox with the versions listed in dependencies: in float_to_int/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in float_to_int/ run run_test.py only up to line 86 (stop before `#seed(0)` at line 87 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (float_to_int/run_test.py:10). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace float_to_int/float_to_int.v and keep the testbench, the driver and the C model unchanged.
67
  Companions (not included): COPYING.txt
68
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
69
  - `double_multiplier/` (8 files): dawsonjon/fpu double_multiplier: double precision IEEE 754 multiplier with its Icarus Verilog testbench and C reference model.
70
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
71
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
72
- Reference result: self_checking_testbench_pass_fail
73
- Reference source: c_test/test.cpp computes a * b on 64-bit doubles on the host CPU (IEEE 754, default round to nearest even) for every stimulus value; run_test.py feeds the same stimulus to the DUT through test_bench_tb, reads resp_z and compares each result with the C model; sections: regression vector (line 124), corner cases (line 131, permutations of 6 special values: signed zeros, infinities, NaNs), edge cases (line 153, 12 blocks of 1000 vectors, one operand fixed to a special value and the other drawn by randint); a mismatch prints `Fail ... expected: ... actual: ...` (run_test.py:97)
74
  Check: Build in a sandbox with the versions listed in dependencies: in double_multiplier/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in double_multiplier/ run run_test.py only up to line 225 (stop before `#seed(0)` at line 226 and the 100000-batch random loop after it, which README.rst line 33 says could take several days). The driver compiles with iverilog (double_multiplier/run_test.py:17). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace double_multiplier/double_multiplier.v and keep the testbench, the driver and the C model unchanged.
75
  Companions (not included): COPYING.txt
76
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst line 30 `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
77
  - `double_divider/` (8 files): dawsonjon/fpu double_divider: double precision IEEE 754 divider with its Icarus Verilog testbench and C reference model.
78
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
79
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
80
- Reference result: self_checking_testbench_pass_fail
81
- Reference source: c_test/test.cpp computes a / b on 64-bit doubles on the host CPU (IEEE 754, default round to nearest even) for every stimulus value; run_test.py feeds the same stimulus to the DUT through test_bench_tb, reads resp_z and compares each result with the C model; sections: regression vector (line 124), corner cases (line 131, permutations of 6 special values: signed zeros, infinities, NaNs), edge cases (line 153, 12 blocks of 1000 vectors, one operand fixed to a special value and the other drawn by randint); a mismatch prints `Fail ... expected: ... actual: ...` (run_test.py:97)
82
  Check: Build in a sandbox with the versions listed in dependencies: in double_divider/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in double_divider/ run run_test.py only up to line 225 (stop before `#seed(0)` at line 226 and the 100000-batch random loop after it, which README.rst line 33 says could take several days). The driver compiles with iverilog (double_divider/run_test.py:17). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace double_divider/double_divider.v and keep the testbench, the driver and the C model unchanged.
83
  Companions (not included): COPYING.txt
84
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst line 30 `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
 
8
 
9
  **Self-contained:** Each unit is self-contained. 8 of 8 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):** MIT
 
19
  - `adder/` (8 files): dawsonjon/fpu adder: single precision IEEE 754 adder with its Icarus Verilog testbench and C reference model.
20
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
21
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
 
 
22
  Check: Build in a sandbox with the versions listed in dependencies: in adder/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in adder/ run run_test.py only up to line 186 (stop before `#seed(0)` at line 187 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (adder/run_test.py:9). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace adder/adder.v and keep the testbench, the driver and the C model unchanged.
23
  Companions (not included): COPYING.txt
24
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
25
  - `multiplier/` (8 files): dawsonjon/fpu multiplier: single precision IEEE 754 multiplier with its Icarus Verilog testbench and C reference model.
26
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
27
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
 
 
28
  Check: Build in a sandbox with the versions listed in dependencies: in multiplier/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in multiplier/ run run_test.py only up to line 187 (stop before `#seed(0)` at line 188 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (multiplier/run_test.py:9). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace multiplier/multiplier.v and keep the testbench, the driver and the C model unchanged.
29
  Companions (not included): COPYING.txt
30
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
31
  - `divider/` (8 files): dawsonjon/fpu divider: single precision IEEE 754 divider with its Icarus Verilog testbench and C reference model.
32
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
33
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
 
 
34
  Check: Build in a sandbox with the versions listed in dependencies: in divider/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in divider/ run run_test.py only up to line 185 (stop before `#seed(0)` at line 186 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (divider/run_test.py:9). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace divider/divider.v and keep the testbench, the driver and the C model unchanged.
35
  Companions (not included): COPYING.txt
36
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
37
  - `double_adder/` (8 files): dawsonjon/fpu double_adder: double precision IEEE 754 adder with its Icarus Verilog testbench and C reference model.
38
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
39
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
 
 
40
  Check: Build in a sandbox with the versions listed in dependencies: in double_adder/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in double_adder/ run run_test.py only up to line 224 (stop before `#seed(0)` at line 225 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (double_adder/run_test.py:17). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace double_adder/double_adder.v and keep the testbench, the driver and the C model unchanged.
41
  Companions (not included): COPYING.txt
42
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
43
  - `int_to_float/` (7 files): dawsonjon/fpu int_to_float: 32-bit integer to single precision float converter with its Icarus Verilog testbench and C reference model.
44
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
45
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
 
 
46
  Check: Build in a sandbox with the versions listed in dependencies: in int_to_float/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in int_to_float/ run run_test.py as shipped: it calls exit(0) at line 78 right after the regression block, so only the 9 regression vectors run (the corner block at line 80 and the random loop at line 87 are never reached). The driver compiles with iverilog (int_to_float/run_test.py:10). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace int_to_float/int_to_float.v and keep the testbench, the driver and the C model unchanged.
47
  Companions (not included): COPYING.txt
48
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
49
  - `float_to_int/` (7 files): dawsonjon/fpu float_to_int: single precision float to 32-bit integer converter with its Icarus Verilog testbench and C reference model.
50
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
51
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
 
 
52
  Check: Build in a sandbox with the versions listed in dependencies: in float_to_int/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in float_to_int/ run run_test.py only up to line 86 (stop before `#seed(0)` at line 87 and the 100000-batch random loop after it, which README.rst lines 32-34 say could take several days). The driver compiles with iverilog (float_to_int/run_test.py:10). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace float_to_int/float_to_int.v and keep the testbench, the driver and the C model unchanged.
53
  Companions (not included): COPYING.txt
54
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst lines 29-30 `cd c_test` and `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
55
  - `double_multiplier/` (8 files): dawsonjon/fpu double_multiplier: double precision IEEE 754 multiplier with its Icarus Verilog testbench and C reference model.
56
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
57
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
 
 
58
  Check: Build in a sandbox with the versions listed in dependencies: in double_multiplier/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in double_multiplier/ run run_test.py only up to line 225 (stop before `#seed(0)` at line 226 and the 100000-batch random loop after it, which README.rst line 33 says could take several days). The driver compiles with iverilog (double_multiplier/run_test.py:17). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace double_multiplier/double_multiplier.v and keep the testbench, the driver and the C model unchanged.
59
  Companions (not included): COPYING.txt
60
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst line 30 `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
61
  - `double_divider/` (8 files): dawsonjon/fpu double_divider: double precision IEEE 754 divider with its Icarus Verilog testbench and C reference model.
62
  Format: Verilog-2001 DUT with a Verilog file-driven testbench (stimulus read from stim_a/stim_b, results written to resp_z) and a Python 2 driver that compiles with iverilog, runs a C reference model on the same stimulus and compares
63
  Origin: self-checking testbench written by the IP author for his own RTL module (tool_fixture): a C reference model on the host CPU gives the expected output for each stimulus
 
 
64
  Check: Build in a sandbox with the versions listed in dependencies: in double_divider/c_test run g++ -o test test.cpp (the shipped ELF is not used), then in double_divider/ run run_test.py only up to line 225 (stop before `#seed(0)` at line 226 and the 100000-batch random loop after it, which README.rst line 33 says could take several days). The driver compiles with iverilog (double_divider/run_test.py:17). The unit passes when the output has no line starting with `Fail` and the last `vectors passed` count equals the number of vectors in the sections run; the exit code is not a pass signal, because run_test.py exits 0 also after a failure. For a write-the-RTL task, hide or replace double_divider/double_divider.v and keep the testbench, the driver and the C model unchanged.
65
  Companions (not included): COPYING.txt
66
  Dependencies: Python 2 (run_test.py uses Python 2 print statements and xrange; upstream does not pin a version); open source, not packed; g++ (README.rst line 30 `g++ -o test test.cpp` build the C reference model; upstream does not pin a version); open source, not packed; Icarus Verilog v11_0 (iverilog and vvp; README.rst line 18 names icarus verilog, version not pinned upstream; latest release on or before the unit commit date 2021-12-04, GitHub release published 2020-10-11; https://github.com/steveicarus/iverilog/releases/tag/v11_0); open source, not packed
campaign_files/2026-10-hw-eda-tests-2/freecad-main-at-commit-200ccc4-github-freecad-freecad-the-open-source-57f0b9b0/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 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: cad_geometry_assert. 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:** FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestPointPattern; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API; FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestThickness; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API; FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t parttests.TestPartMirror; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API; FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t parttests.TestFaceMakerUnifiedPlanar; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API; FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestBaseFeature; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
14
 
15
  **Licence (SPDX):** LGPL-2.1-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `src/Mod/PartDesign/PartDesignTests/TestPointPattern.py`: FreeCAD PartDesign point pattern tests: copy a feature onto sketch or vertex points and check the patterned volume and bounding box.
22
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
23
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
24
- Reference result: cad_geometry_assert
25
- Reference source: upstream expected values written in the test file itself: line 40 `self.assertAlmostEqual(pattern.Shape.Volume, 3 * box.Shape.Volume)`; lines 41-44 bounding-box limits XMin 5, YMin 5, ZMin 5, XMax 12. Values are closed-form box geometry.
26
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); Answer is the test file's own expected values.
27
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestPointPattern; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
28
  Companions (not included): LICENSE
@@ -30,8 +26,6 @@ Files:
30
  - `src/Mod/PartDesign/PartDesignTests/TestThickness.py`: FreeCAD PartDesign thickness (shell) tests: hollow boxes and other solids by a wall thickness and check the resulting volume and shape equivalence.
31
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
32
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
33
- Reference result: cad_geometry_assert
34
- Reference source: upstream expected values written in the test file itself: line 223 `self.assertAlmostEqual(result.Volume, 5208.0, delta=1e-7)` (40 x 30 x 10 box opened at the top, 1 mm each side); helper assertShapesEquivalent lines 213-216 compares volumes and boolean differences. Values are closed-form.
35
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); Answer is the test file's own expected values.
36
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestThickness; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
37
  Companions (not included): LICENSE
@@ -39,8 +33,6 @@ Files:
39
  - `src/Mod/Part/parttests/TestPartMirror.py`: FreeCAD Part mirror tests: mirror shapes and Draft clones across planes and check the mirrored positions and areas.
40
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
41
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
42
- Reference result: cad_geometry_assert
43
- Reference source: upstream expected values written in the test file itself: lines 75-79 clone bounding-box centre 30.0 with delta=5.0; line 114 places=3. Values are closed-form placements.
44
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); The module also imports the Draft workbench, part of the FreeCAD program. Answer is the test file's own expected values.
45
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t parttests.TestPartMirror; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
46
  Companions (not included): LICENSE
@@ -48,8 +40,6 @@ Files:
48
  - `src/Mod/Part/parttests/TestFaceMakerUnifiedPlanar.py`: FreeCAD Part unified planar face maker tests: build faces from nested, touching and overlapping wires and check the resulting face areas.
49
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
50
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
51
- Reference result: cad_geometry_assert
52
- Reference source: upstream expected values written in the test file itself: line 118 `self.assertAlmostEqual(faces[0].Area, 100.0, places=3)` line 123 circle area pi * 100 with places=1, line 171 1600 - pi * 25 with places=1, and further areas of squares, circles, rings and holes. Values are closed-form areas.
53
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); One font test reads a TechDraw font from the FreeCAD resource directory (line 472) and is skipped when absent. Answer is the test file's own expected values.
54
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t parttests.TestFaceMakerUnifiedPlanar; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
55
  Companions (not included): LICENSE
@@ -57,8 +47,6 @@ Files:
57
  - `src/Mod/PartDesign/PartDesignTests/TestBaseFeature.py`: FreeCAD PartDesign base feature tests: put Part shapes into a body as the base feature, move and pad them, and check placements and bounding boxes.
58
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
59
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
60
- Reference result: cad_geometry_assert
61
- Reference source: upstream expected values written in the test file itself: lines 31-33 base x 20, body XMin 120, XMax 130; lines 54-55 base x 5, XMin 25. Closed-form placements.
62
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); The module imports TestSketcherApp (line 6), which imports the SketcherTests package. Answer is the test file's own expected values.
63
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestBaseFeature; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
64
  Companions (not included): src/Mod/Sketcher/TestSketcherApp.py; LICENSE
 
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 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:** FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestPointPattern; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API; FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestThickness; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API; FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t parttests.TestPartMirror; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API; FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t parttests.TestFaceMakerUnifiedPlanar; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API; FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestBaseFeature; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
12
 
13
  **Licence (SPDX):** LGPL-2.1-or-later
 
19
  - `src/Mod/PartDesign/PartDesignTests/TestPointPattern.py`: FreeCAD PartDesign point pattern tests: copy a feature onto sketch or vertex points and check the patterned volume and bounding box.
20
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
21
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
 
 
22
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); Answer is the test file's own expected values.
23
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestPointPattern; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
24
  Companions (not included): LICENSE
 
26
  - `src/Mod/PartDesign/PartDesignTests/TestThickness.py`: FreeCAD PartDesign thickness (shell) tests: hollow boxes and other solids by a wall thickness and check the resulting volume and shape equivalence.
27
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
28
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
 
 
29
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); Answer is the test file's own expected values.
30
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestThickness; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
31
  Companions (not included): LICENSE
 
33
  - `src/Mod/Part/parttests/TestPartMirror.py`: FreeCAD Part mirror tests: mirror shapes and Draft clones across planes and check the mirrored positions and areas.
34
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
35
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
 
 
36
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); The module also imports the Draft workbench, part of the FreeCAD program. Answer is the test file's own expected values.
37
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t parttests.TestPartMirror; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
38
  Companions (not included): LICENSE
 
40
  - `src/Mod/Part/parttests/TestFaceMakerUnifiedPlanar.py`: FreeCAD Part unified planar face maker tests: build faces from nested, touching and overlapping wires and check the resulting face areas.
41
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
42
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
 
 
43
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); One font test reads a TechDraw font from the FreeCAD resource directory (line 472) and is skipped when absent. Answer is the test file's own expected values.
44
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t parttests.TestFaceMakerUnifiedPlanar; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
45
  Companions (not included): LICENSE
 
47
  - `src/Mod/PartDesign/PartDesignTests/TestBaseFeature.py`: FreeCAD PartDesign base feature tests: put Part shapes into a body as the base feature, move and pad them, and check placements and bounding boxes.
48
  Format: Python unittest module run inside FreeCAD (FreeCADCmd) against the FreeCAD document, Part and PartDesign APIs on OpenCASCADE
49
  Origin: FreeCAD module self-test written by FreeCAD developers; expected numbers are closed-form geometry or recorded kernel results
 
 
50
  Check: Task: given the modelling recipe of each test method (primitive sizes, sketch geometry, feature parameters) with the expected values hidden, either build the model in FreeCAD and report the measured values (volume, area, bounding-box limits, positions) or derive them in closed form. Judge: compare each reported value with the test's expected value by the same rule as the upstream assertion: assertAlmostEqual passes when round(got - want, places) == 0, places 7 by default (CPython unittest/case.py lines 874-876), or abs(got - want) <= delta when delta is given (line 864); The module imports TestSketcherApp (line 6), which imports the SketcherTests package. Answer is the test file's own expected values.
51
  Tools: FreeCADCmd (FreeCAD's headless console) runs the module: FreeCADCmd -t PartDesignTests.TestBaseFeature; volumes, areas and bounding boxes read from Shape.Volume, Shape.Area and Shape.BoundBox in the FreeCAD Python API
52
  Companions (not included): src/Mod/Sketcher/TestSketcherApp.py; LICENSE
campaign_files/2026-10-m-issue-trackers-2/eyms-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/eyms/gtfs/eyms_1791452128.zip
23
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
24
  Origin: Live static GTFS feed published by East Yorkshire (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/eyms/gtfs/eyms_1791452128.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/eyms/gtfs/eyms_1791452128.zip
21
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
22
  Origin: Live static GTFS feed published by East Yorkshire (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/eyms/gtfs/eyms_1791452128.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/fdio-gerrit-changes/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 change's own review timeline (status, submit time and submitter, patch sets, votes, reviewers added or removed, review comments). 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 the Gerrit REST API (GET https://gerrit.fd.io/r/changes/{number}/detail), strip the first line ")]}'" and read the JSON with jq or Python json; the git-review CLI and Gerrit's ssh 'gerrit query --format=JSON --all-approvals --comments' reach the same data where ssh access is open
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `changes/43006/detail.json`: Vpp change 43006: http: disable timer node if session disabled.
22
  Format: Gerrit REST API ChangeInfo JSON from the /detail endpoint, preceded by the anti-XSSI line ")]}'": status, created, updated, submitted, submitter, owner, labels with every vote (DETAILED_LABELS), messages (author, real_author, date, tag, _revision_number, message text) and reviewer_updates (updated, updated_by, reviewer, state REVIEWER/CC/REMOVED). Patch-set uploads are messages tagged autogenerated:gerrit:newPatchSet; votes appear in message text as 'Patch Set N: Label+V' and in labels.*.all. The endpoint returns all messages and reviewer updates of the change, so the record is complete.
23
  Origin: Live Gerrit REST interface of a closed (merged) code review change, collected as a NOASSERTION pointer row under spec general rule 4: the detail JSON was fetched twice apart and was byte-identical. Unit file kept only outside the repository for checking and then deleted.
24
- Reference result: facts computed from the change's own review timeline (status, submit time and submitter, patch sets, votes, reviewers added or removed, review comments)
25
- Reference source: The pinned response: changes/43006/detail.json.
26
  Check: Exact match against values read from the pinned JSON: status, submitted and submitter; reviewer_updates entries (reviewer, state, updated_by, updated); messages tagged autogenerated:gerrit:newPatchSet (patch-set count, _revision_number); votes from labels.*.all (value, _account_id) and from message first lines 'Patch Set N: Label+V'. A human review comment is a message whose author is not a bot or service account, whose tag does not start with 'autogenerated:', and whose text has content beyond the 'Patch Set N: votes' first line or names inline comments '(N comments)'. Bot and service accounts excluded from the comment count: fdio.required.gha, rotterdam-jobbuilder, accounts tagged SERVICE_USER, and any account whose name, username or email matches the pattern (bot|zuul|jenkins|ci|luci|gerrit code review|service user|automation|buildbot|lint|sonar|tryjob|cq|autosubmit|copybara|tricium|gerritforge|verifier|checker|scheduler). 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 the Gerrit REST API (GET https://gerrit.fd.io/r/changes/{number}/detail), strip the first line ")]}'" and read the JSON with jq or Python json; the git-review CLI and Gerrit's ssh 'gerrit query --format=JSON --all-approvals --comments' reach the same data where ssh access is open
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** curl the Gerrit REST API (GET https://gerrit.fd.io/r/changes/{number}/detail), strip the first line ")]}'" and read the JSON with jq or Python json; the git-review CLI and Gerrit's ssh 'gerrit query --format=JSON --all-approvals --comments' reach the same data where ssh access is open
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `changes/43006/detail.json`: Vpp change 43006: http: disable timer node if session disabled.
20
  Format: Gerrit REST API ChangeInfo JSON from the /detail endpoint, preceded by the anti-XSSI line ")]}'": status, created, updated, submitted, submitter, owner, labels with every vote (DETAILED_LABELS), messages (author, real_author, date, tag, _revision_number, message text) and reviewer_updates (updated, updated_by, reviewer, state REVIEWER/CC/REMOVED). Patch-set uploads are messages tagged autogenerated:gerrit:newPatchSet; votes appear in message text as 'Patch Set N: Label+V' and in labels.*.all. The endpoint returns all messages and reviewer updates of the change, so the record is complete.
21
  Origin: Live Gerrit REST interface of a closed (merged) code review change, collected as a NOASSERTION pointer row under spec general rule 4: the detail JSON was fetched twice apart and was byte-identical. Unit file kept only outside the repository for checking and then deleted.
 
 
22
  Check: Exact match against values read from the pinned JSON: status, submitted and submitter; reviewer_updates entries (reviewer, state, updated_by, updated); messages tagged autogenerated:gerrit:newPatchSet (patch-set count, _revision_number); votes from labels.*.all (value, _account_id) and from message first lines 'Patch Set N: Label+V'. A human review comment is a message whose author is not a bot or service account, whose tag does not start with 'autogenerated:', and whose text has content beyond the 'Patch Set N: votes' first line or names inline comments '(N comments)'. Bot and service accounts excluded from the comment count: fdio.required.gha, rotterdam-jobbuilder, accounts tagged SERVICE_USER, and any account whose name, username or email matches the pattern (bot|zuul|jenkins|ci|luci|gerrit code review|service user|automation|buildbot|lint|sonar|tryjob|cq|autosubmit|copybara|tricium|gerritforge|verifier|checker|scheduler). 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 the Gerrit REST API (GET https://gerrit.fd.io/r/changes/{number}/detail), strip the first line ")]}'" and read the JSON with jq or Python json; the git-review CLI and Gerrit's ssh 'gerrit query --format=JSON --all-approvals --comments' reach the same data where ssh access is open
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-ci-tickets-issues/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. 2 of 2 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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,16 +19,12 @@ Files:
21
  - `api/v1/repos/ci/tickets/issues/571.json`: ci/tickets issue #571: rmdepcheck on eln seems to check Rawhide Koji repos.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 14 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/ci/tickets/issues/571.json and api/v1/repos/ci/tickets/issues/571/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/ci/tickets/issues/571/timeline.json
29
  - `api/v1/repos/ci/tickets/issues/558.json`: ci/tickets issue #558: rpminspect_runner.sh crashes, causing no results from rpminspect.
30
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 9 entries, fewer than 50, so it is complete.
31
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
32
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
33
- Reference source: The pinned responses: api/v1/repos/ci/tickets/issues/558.json and api/v1/repos/ci/tickets/issues/558/timeline.json.
34
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
35
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
36
  Companions (not included): api/v1/repos/ci/tickets/issues/558/timeline.json
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/ci/tickets/issues/571.json`: ci/tickets issue #571: rmdepcheck on eln seems to check Rawhide Koji repos.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 14 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/ci/tickets/issues/571/timeline.json
25
  - `api/v1/repos/ci/tickets/issues/558.json`: ci/tickets issue #558: rpminspect_runner.sh crashes, causing no results from rpminspect.
26
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 9 entries, fewer than 50, so it is complete.
27
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
28
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
29
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
30
  Companions (not included): api/v1/repos/ci/tickets/issues/558/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-council-tickets-issues/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. 2 of 2 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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,16 +19,12 @@ Files:
21
  - `api/v1/repos/council/tickets/issues/560.json`: council/tickets issue #560: Request for Sense of the Council approval of Pagure.io Migration Timeline CommsBlog Post.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 20 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/council/tickets/issues/560.json and api/v1/repos/council/tickets/issues/560/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/council/tickets/issues/560/timeline.json
29
  - `api/v1/repos/council/tickets/issues/565.json`: council/tickets issue #565: F44 Council Interview Questions (due: 21 May 2026).
30
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 30 entries, fewer than 50, so it is complete.
31
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
32
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
33
- Reference source: The pinned responses: api/v1/repos/council/tickets/issues/565.json and api/v1/repos/council/tickets/issues/565/timeline.json.
34
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
35
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
36
  Companions (not included): api/v1/repos/council/tickets/issues/565/timeline.json
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/council/tickets/issues/560.json`: council/tickets issue #560: Request for Sense of the Council approval of Pagure.io Migration Timeline CommsBlog Post.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 20 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/council/tickets/issues/560/timeline.json
25
  - `api/v1/repos/council/tickets/issues/565.json`: council/tickets issue #565: F44 Council Interview Questions (due: 21 May 2026).
26
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 30 entries, fewer than 50, so it is complete.
27
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
28
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
29
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
30
  Companions (not included): api/v1/repos/council/tickets/issues/565/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-dei-tickets-issues/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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `api/v1/repos/dei/tickets/issues/61.json`: dei/tickets issue #61: Migrate the DEI team repo to Fedora Forge (Forgejo).
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 21 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/dei/tickets/issues/61.json and api/v1/repos/dei/tickets/issues/61/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/dei/tickets/issues/61/timeline.json
 
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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/dei/tickets/issues/61.json`: dei/tickets issue #61: Migrate the DEI team repo to Fedora Forge (Forgejo).
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 21 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/dei/tickets/issues/61/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-design-tickets-issues/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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `api/v1/repos/design/tickets/issues/48.json`: design/tickets issue #48: Fedora 44 Release Party.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 29 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/design/tickets/issues/48.json and api/v1/repos/design/tickets/issues/48/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/design/tickets/issues/48/timeline.json
 
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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/design/tickets/issues/48.json`: design/tickets issue #48: Fedora 44 Release Party.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 29 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/design/tickets/issues/48/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-docs-tickets-issues/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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `api/v1/repos/docs/tickets/issues/23.json`: docs/tickets issue #23: Membership request: @theprogram Mat H.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 17 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/docs/tickets/issues/23.json and api/v1/repos/docs/tickets/issues/23/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/docs/tickets/issues/23/timeline.json
 
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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/docs/tickets/issues/23.json`: docs/tickets issue #23: Membership request: @theprogram Mat H.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 17 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/docs/tickets/issues/23/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-epel-releng/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Each file is self-contained. 2 of 2 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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,16 +19,12 @@ Files:
21
  - `api/v1/repos/epel/releng/issues/100.json`: epel/releng #100: EPEL 10.1 retirement prep work.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/epel/releng/issues/100.json and api/v1/repos/epel/releng/issues/100/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); none occur in this unit. 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 the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/epel/releng/issues/100/timeline.json
29
  - `api/v1/repos/epel/releng/issues/98.json`: epel/releng #98: RFE: new repo redirect for the testing repos for EPEL <= 9.
30
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
31
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
32
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
33
- Reference source: The pinned responses: api/v1/repos/epel/releng/issues/98.json and api/v1/repos/epel/releng/issues/98/timeline.json.
34
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); none occur in this unit. 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.
35
  Tools: curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
36
  Companions (not included): api/v1/repos/epel/releng/issues/98/timeline.json
 
8
 
9
  **Self-contained:** Each file is self-contained. 2 of 2 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:** curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/epel/releng/issues/100.json`: epel/releng #100: EPEL 10.1 retirement prep work.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); none occur in this unit. 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 the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/epel/releng/issues/100/timeline.json
25
  - `api/v1/repos/epel/releng/issues/98.json`: epel/releng #98: RFE: new repo redirect for the testing repos for EPEL <= 9.
26
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
27
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
28
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); none occur in this unit. 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.
29
  Tools: curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
30
  Companions (not included): api/v1/repos/epel/releng/issues/98/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-fesco-tickets-issues/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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `api/v1/repos/fesco/tickets/issues/3648.json`: fesco/tickets issue #3648: Reconsider approval of https://fedoraproject.org/wiki/Changes/RelocateRpmRepoConfigsToUsr as a "self-contained Change".
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 8 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/fesco/tickets/issues/3648.json and api/v1/repos/fesco/tickets/issues/3648/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/fesco/tickets/issues/3648/timeline.json
 
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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/fesco/tickets/issues/3648.json`: fesco/tickets issue #3648: Reconsider approval of https://fedoraproject.org/wiki/Changes/RelocateRpmRepoConfigsToUsr as a "self-contained Change".
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 8 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/fesco/tickets/issues/3648/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-flatpak-tickets-issues/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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `api/v1/repos/flatpak/tickets/issues/63.json`: flatpak/tickets issue #63: Migrate to forgejo (forge.fp.o).
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 16 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/flatpak/tickets/issues/63.json and api/v1/repos/flatpak/tickets/issues/63/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/flatpak/tickets/issues/63/timeline.json
 
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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/flatpak/tickets/issues/63.json`: flatpak/tickets issue #63: Migrate to forgejo (forge.fp.o).
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 16 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/flatpak/tickets/issues/63/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-infra-tickets/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. 4 of 4 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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,32 +19,24 @@ Files:
21
  - `api/v1/repos/infra/tickets/issues/13572.json`: infra/tickets issue #13572: Koji fails to download perl-Encode-EUCJPASCII-0.03-34.el9.x86_64.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 19 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/infra/tickets/issues/13572.json and api/v1/repos/infra/tickets/issues/13572/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/infra/tickets/issues/13572/timeline.json
29
  - `api/v1/repos/infra/tickets/issues/13559.json`: infra/tickets issue #13559: https://koji.fedoraproject.org/koji/ gives 503 error.
30
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 19 entries, fewer than 50, so it is complete.
31
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
32
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
33
- Reference source: The pinned responses: api/v1/repos/infra/tickets/issues/13559.json and api/v1/repos/infra/tickets/issues/13559/timeline.json.
34
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
35
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
36
  Companions (not included): api/v1/repos/infra/tickets/issues/13559/timeline.json
37
  - `api/v1/repos/infra/tickets/issues/13556.json`: infra/tickets issue #13556: reinstall some buildhw-x86's.
38
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 14 entries, fewer than 50, so it is complete.
39
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
40
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
41
- Reference source: The pinned responses: api/v1/repos/infra/tickets/issues/13556.json and api/v1/repos/infra/tickets/issues/13556/timeline.json.
42
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
43
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
44
  Companions (not included): api/v1/repos/infra/tickets/issues/13556/timeline.json
45
  - `api/v1/repos/infra/tickets/issues/13612.json`: infra/tickets issue #13612: Planned Outage - s390x reboot - 2026-10-07 21:00 UTC.
46
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 13 entries, fewer than 50, so it is complete.
47
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
48
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
49
- Reference source: The pinned responses: api/v1/repos/infra/tickets/issues/13612.json and api/v1/repos/infra/tickets/issues/13612/timeline.json.
50
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
51
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
52
  Companions (not included): api/v1/repos/infra/tickets/issues/13612/timeline.json
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 4 of 4 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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/infra/tickets/issues/13572.json`: infra/tickets issue #13572: Koji fails to download perl-Encode-EUCJPASCII-0.03-34.el9.x86_64.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 19 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/infra/tickets/issues/13572/timeline.json
25
  - `api/v1/repos/infra/tickets/issues/13559.json`: infra/tickets issue #13559: https://koji.fedoraproject.org/koji/ gives 503 error.
26
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 19 entries, fewer than 50, so it is complete.
27
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
28
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
29
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
30
  Companions (not included): api/v1/repos/infra/tickets/issues/13559/timeline.json
31
  - `api/v1/repos/infra/tickets/issues/13556.json`: infra/tickets issue #13556: reinstall some buildhw-x86's.
32
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 14 entries, fewer than 50, so it is complete.
33
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
34
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
35
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
36
  Companions (not included): api/v1/repos/infra/tickets/issues/13556/timeline.json
37
  - `api/v1/repos/infra/tickets/issues/13612.json`: infra/tickets issue #13612: Planned Outage - s390x reboot - 2026-10-07 21:00 UTC.
38
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 13 entries, fewer than 50, so it is complete.
39
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
40
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
41
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
42
  Companions (not included): api/v1/repos/infra/tickets/issues/13612/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-localization-tickets-issues/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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `api/v1/repos/localization/tickets/issues/46.json`: localization/tickets issue #46: Move glabels-qt translations to Fedora Weblate.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 18 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/localization/tickets/issues/46.json and api/v1/repos/localization/tickets/issues/46/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/localization/tickets/issues/46/timeline.json
 
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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/localization/tickets/issues/46.json`: localization/tickets issue #46: Move glabels-qt translations to Fedora Weblate.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 18 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/localization/tickets/issues/46/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-packaging-sponsors-issues/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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `api/v1/repos/packaging/sponsors/issues/795.json`: packaging/sponsors issue #795: Requesting sponsorship for user agaragna to co-maintain certmonger.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 8 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/packaging/sponsors/issues/795.json and api/v1/repos/packaging/sponsors/issues/795/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/packaging/sponsors/issues/795/timeline.json
 
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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/packaging/sponsors/issues/795.json`: packaging/sponsors issue #795: Requesting sponsorship for user agaragna to co-maintain certmonger.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 8 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/packaging/sponsors/issues/795/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-quality-tickets-issues/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. 2 of 2 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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,16 +19,12 @@ Files:
21
  - `api/v1/repos/quality/tickets/issues/940.json`: quality/tickets issue #940: Collection of this group's data for a LLM-powered weekly report.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 16 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/quality/tickets/issues/940.json and api/v1/repos/quality/tickets/issues/940/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/quality/tickets/issues/940/timeline.json
29
  - `api/v1/repos/quality/tickets/issues/926.json`: quality/tickets issue #926: Early manual validation testing for Fedora 45.
30
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 35 entries, fewer than 50, so it is complete.
31
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
32
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
33
- Reference source: The pinned responses: api/v1/repos/quality/tickets/issues/926.json and api/v1/repos/quality/tickets/issues/926/timeline.json.
34
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
35
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
36
  Companions (not included): api/v1/repos/quality/tickets/issues/926/timeline.json
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/quality/tickets/issues/940.json`: quality/tickets issue #940: Collection of this group's data for a LLM-powered weekly report.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 16 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/quality/tickets/issues/940/timeline.json
25
  - `api/v1/repos/quality/tickets/issues/926.json`: quality/tickets issue #926: Early manual validation testing for Fedora 45.
26
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 35 entries, fewer than 50, so it is complete.
27
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
28
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
29
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
30
  Companions (not included): api/v1/repos/quality/tickets/issues/926/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-releng-tickets-issues/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. 2 of 2 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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,16 +19,12 @@ Files:
21
  - `api/v1/repos/releng/tickets/issues/13510.json`: releng/tickets issue #13510: F44F updates-testing compose stuck, blocking all other updates.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 21 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/releng/tickets/issues/13510.json and api/v1/repos/releng/tickets/issues/13510/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/releng/tickets/issues/13510/timeline.json
29
  - `api/v1/repos/releng/tickets/issues/13451.json`: releng/tickets issue #13451: F45 Cycle: Mass Branching.
30
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 28 entries, fewer than 50, so it is complete.
31
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
32
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
33
- Reference source: The pinned responses: api/v1/repos/releng/tickets/issues/13451.json and api/v1/repos/releng/tickets/issues/13451/timeline.json.
34
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
35
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
36
  Companions (not included): api/v1/repos/releng/tickets/issues/13451/timeline.json
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/releng/tickets/issues/13510.json`: releng/tickets issue #13510: F44F updates-testing compose stuck, blocking all other updates.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 21 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/releng/tickets/issues/13510/timeline.json
25
  - `api/v1/repos/releng/tickets/issues/13451.json`: releng/tickets issue #13451: F45 Cycle: Mass Branching.
26
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 28 entries, fewer than 50, so it is complete.
27
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
28
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
29
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
30
  Companions (not included): api/v1/repos/releng/tickets/issues/13451/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-security-tickets-issues/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: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `api/v1/repos/security/tickets/issues/1.json`: security/tickets issue #1: Support, collaborate or integrate "Fedora-downstream-hardening" project under the umbrella of Security SIG.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 24 entries, fewer than 50, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/security/tickets/issues/1.json and api/v1/repos/security/tickets/issues/1/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
27
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/security/tickets/issues/1/timeline.json
 
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:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/security/tickets/issues/1.json`: security/tickets issue #1: Support, collaborate or integrate "Fedora-downstream-hardening" project under the umbrella of Security SIG.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 24 entries, fewer than 50, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: Forgejo user objects carry no bot flag, so bots are recognised by the named account forgebot (the Fedora forge automation account) and the login pattern (bot|action|renovate|forgejo-|-automation|assistant); bot accounts in this timeline: none. 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. An assignment where the actor and the assignee are the same account (self-assigned) is still a timeline event of type assignees and is answered as recorded.
23
  Tools: curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/security/tickets/issues/1/timeline.json
campaign_files/2026-10-m-issue-trackers-2/fedora-forge-server-tickets/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.
10
 
11
- **Answers:** No answer files are included. Reference result: Facts computed from the issue's own timeline (status changes, assignee changes, comments). 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 the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,24 +19,18 @@ Files:
21
  - `api/v1/repos/server/tickets/issues/186.json`: server/tickets #186: F44 release testing.
22
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
23
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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, assignee changes, comments)
25
- Reference source: The pinned responses: api/v1/repos/server/tickets/issues/186.json and api/v1/repos/server/tickets/issues/186/timeline.json.
26
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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 the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
28
  Companions (not included): api/v1/repos/server/tickets/issues/186/timeline.json
29
  - `api/v1/repos/server/tickets/issues/173.json`
30
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
31
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
32
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
33
- Reference source: The pinned responses: api/v1/repos/server/tickets/issues/173.json and api/v1/repos/server/tickets/issues/173/timeline.json.
34
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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.
35
  Tools: curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
36
  Companions (not included): api/v1/repos/server/tickets/issues/173/timeline.json
37
  - `api/v1/repos/server/tickets/issues/114.json`: server/tickets #114: LLMNR should be disabled in resolved in f39.
38
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
39
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
40
- Reference result: facts computed from the issue's own timeline (status changes, assignee changes, comments)
41
- Reference source: The pinned responses: api/v1/repos/server/tickets/issues/114.json and api/v1/repos/server/tickets/issues/114/timeline.json.
42
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). The assignee change was made by forgebot (an automation account), which is still a recorded assignee change event. 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.
43
  Tools: curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
44
  Companions (not included): api/v1/repos/server/tickets/issues/114/timeline.json
 
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.
10
 
 
 
11
  **Tools to open and check:** curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `api/v1/repos/server/tickets/issues/186.json`: server/tickets #186: F44 release testing.
20
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
21
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were 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: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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 the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
24
  Companions (not included): api/v1/repos/server/tickets/issues/186/timeline.json
25
  - `api/v1/repos/server/tickets/issues/173.json`
26
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
27
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
28
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). 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.
29
  Tools: curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
30
  Companions (not included): api/v1/repos/server/tickets/issues/173/timeline.json
31
  - `api/v1/repos/server/tickets/issues/114.json`: server/tickets #114: LLMNR should be disabled in resolved in f39.
32
  Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
33
  Origin: Live Forgejo REST interface of a closed issue, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
 
 
34
  Check: Exact match against values read from the pinned JSON: timeline entries of type close, reopen and merge_pull (created_at, user.login), entries of type assignees and review_request (assignee.login or assignee_team.name, removed_assignee, user.login, created_at), and entries of type comment plus type review with a non-empty body (user.login, created_at). Deterministic, no model judgement. Human comment count excludes bot accounts: forgebot (the Fedora forge automation account) and any login matching the bot pattern (bot|action|renovate|forgejo-|-automation|assistant). The assignee change was made by forgebot (an automation account), which is still a recorded assignee change event. 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.
35
  Tools: curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
36
  Companions (not included): api/v1/repos/server/tickets/issues/114/timeline.json