frc-scheduler-server: pr-fix-known-vulns-run4

What happened, why, and what came out of it. Written by the harness from its own records; a person decides what to do with it. The same story opens the run's folder as README.md; the example's write-up is on its example page.

repository frc-scheduler-serverlanguage pythonmode diffbase 2ad04243861bhead cfa8f4a3292bmodel qwen/qwen3.8-27bstarted 2026-09-12T01:41:41+00:00harness 0.1.0run 76a3fa863e76

This run has not reached the review packet yet; the last stage that wrote was self-verification.

Who, what, why, where, when

Who	The AI Test Harness 0.1.0 did the work without a person in the loop. A person decides the result; nothing in this run has been merged.
What	Tests for python-jose 3.3.0 to 3.4.0, chosen from a work list of 64 packages, 5 of which this change touched. Repository frc-scheduler-server, change 2ad04243861b..cfa8f4a3292b, mode diff.
Why	python-jose (score 51, budget full): reachable from first-party code; 159 source lines changed; 5 advisories before the change, 0 after.
Where	Every test ran in a sealed sandbox (podman, network none, image docker.io/library/python:3.12-slim); the model was qwen/qwen3.8-27b in agent mode; the run's own files are in this folder.
When	Started 2026-09-12 01:41:41 UTC. The last stage to write was validation execution at 2026-09-12 05:54:29 UTC.

Decisions the harness made

python-jose: cut 3 generated test(s) before execution: 3 fails on baseline after repair.

Actions it took

None yet.

Actions it did not take, by design

It did not merge anything. Tests reach a repository only through a pull request that a person merges.
It did not change production code and did not propose a fix. Fixes come from a separate fix pipeline; this harness only tests.
It did not publish a VEX statement. The drafts are proposals for Product Security.
It did not delete any existing test. Retirements are proposed with evidence for a person to act on.

How it happened, stage by stage

What each stage read, did and wrote, with the file behind every number.

Self-verificationstage 0
Read
the harness's own code and the failure register
Did
- 12 register checks, all passed; sandbox probe skipped; model probe skipped.
Wrote
selfcheck/selfcheck.json
Intakestage 1
Read
the repository at base and head, its dependency manifest
Did
- Resolved 63 packages at head and 63 at base with ; looked every version up in OSV: 4 with advisories at head; 5 changed; work list of 64 rows.
Wrote
intake/worklist.json · intake/graph.new.json · intake/sbom.new.cdx.json · intake/vulns.json
Analysisstage 2
Read
the work list; package source, advisories, the application's call sites
Did
- 1 package(s) analyzed: python-jose score 51, budget full, 0 advisories, 0 breaking changes.
Wrote
analyze/python-jose/facts.json
Generationstage 3
Read
the fact bundle per package; the model; the sealed sandbox for baseline runs
Did
- Model qwen/qwen3.8-27b, mode agent.
- python-jose: 13 tests kept in 4 file(s), 45 model calls.
Wrote
generate/python-jose/manifest.json · tests/ · model-calls/
Validation executionstage 4
Read
the candidate tests; the environments at head, base or the fixed candidate
Did
- python-jose: sandbox runs new, new-rerun, old on podman (image digest not recorded); 13 tests, 7 pass on head, 0 flaky, 0 fix-pinning confirmed; 566 lines of the package covered.
Wrote
execute/python-jose/results.json · new/ · execute/python-jose/mutation/mutation.json · execute/python-jose/relevance.json
Triagestage 5
Read
every verdict and finding from stage 4
Did
- did not run in this run.
Wrote
nothing
Packetstage 6
Read
triage, the tests, the advisories
Did
- did not run in this run.
Wrote
nothing
Attestationstage attest
Read
the manifest, the tests, the results; UDLM's chain code
Did
- did not run in this run.
Wrote
nothing
Assessmentstage assess
Read
every record the run wrote, against the blueprint's goals
Did
- did not run in this run.
Wrote
nothing
Test pull requeststage propose
Read
the packet and the records
Did
- did not run in this run.
Wrote
nothing
Feedbackstage 7
Read
the pull request as a person decided it
Did
- did not run in this run.
Wrote
nothing

python-jose 3.3.0 → 3.4.0

Tests, one row each

Test	Category	Old	New	Verdict
`test_pysec_2025_185_fix_pinning`	cve	fail	fail	fails on the fixed version: test bug or the advisory is misread; back to generation
`test_pysec_2025_185_exposure`	cve	fail	fail	fails on the fixed version: test bug or the advisory is misread; back to generation
`test_ghsa_6c5p_j8vq_pqhj_fix_pinning`	cve	fail	fail	fails on the fixed version: test bug or the advisory is misread; back to generation
`test_ghsa_6c5p_j8vq_pqhj_exposure`	cve	pass	fail	fails on the fixed version: test bug or the advisory is misread; back to generation
`test_ghsa_cjwg_qfpm_7377_fix_pinning`	cve	fail	fail	fails on the fixed version: test bug or the advisory is misread; back to generation
`test_ghsa_cjwg_qfpm_7377_exposure`	cve	fail	fail	fails on the fixed version: test bug or the advisory is misread; back to generation
`test_jwt_encode_decode_roundtrip_hs256`	unit	pass	pass	candidate: passes on head, same on old
`test_jwt_decode_wrong_key_raises_jwt_error`	unit	pass	pass	candidate: passes on head, same on old
`test_jwt_decode_expired_token_raises_expired_signature_error`	unit	pass	pass	candidate: passes on head, same on old
`test_jwt_get_unverified_header_returns_alg`	unit	pass	pass	candidate: passes on head, same on old
`test_jwt_get_unverified_claims_returns_claims_without_verification`	unit	pass	pass	candidate: passes on head, same on old
`test_base64url_encode_decode_roundtrip`	unit	pass	pass	candidate: passes on head, same on old
`test_ensure_binary_and_timedelta_total_seconds`	unit	pass	pass	candidate: passes on head, same on old

What is in this folder, and who it is for

Every file exists for a reader or a tool named here. The plain-English files come first; the machine files stay because they are the proof and the replay.

Everyone

README.md: The story of this run: who, what, why, where, when, the outcome, the decisions and the actions.

Reviewers (the developer or team that owns the change)

intake/worklist.json: The work list: every package at base and head, what changed, what is reachable, what carries advisories.
analyze/python-jose/facts.json: The fact bundle for one package: versions, API diff, call sites, advisories, the risk score and the budget it earned.
analyze/python-jose/api-diff.json: Every added, removed or changed public symbol between the two versions, with a breaking flag.
generate/python-jose/tests/: The candidate test files as generated, before any decision.
execute/python-jose/results.json: The verdict per test: outcome on head, on the re-run and on the other version, coverage, and how each was judged.

Product Security

intake/vulns.json: Known vulnerabilities for every package version in either graph, from OSV, including malicious-package reports.
analyze/python-jose/vulns.json: The advisories on this package's versions, with the symbols they name and the fixed versions.

Supply Chain Security and auditors

run.json: What was run, with which tool versions, on which repository by name.
selfcheck/selfcheck.json: Stage 0: every failure-register check and the sandbox and model probes, before any evidence was produced.
intake/sbom.new.cdx.json: The software bill of materials at head, CycloneDX.
generate/python-jose/model-calls/: Every prompt and every response, numbered, with the call's settings; the full transcript of what the model saw and said.

The person who ran the harness

analyze/python-jose/source-diff.patch: The package's own source diff between the versions; the model reads it to find the fix.
analyze/python-jose/notes.untrusted.md: Package metadata and description as published upstream; untrusted text, kept for context.
generate/python-jose/manifest.json: What was generated: every file, every test, what was cut and discarded and why, the model, the prompt set and its digest, the prompt and response digests.
generate/python-jose/manifest.agent.json: The tool-using agent's traces: every tool call per advisory, and the budget it had.

Tools (kept for replay and proof; not meant to be read)

run-index.json: What this run holds: stages, packages, headline numbers, and where every file is; the renderers read it.
analyze/python-jose/api.new.json: The public API surface at head, extracted by tools.
analyze/python-jose/api.old.json: The public API surface at base.
analyze/python-jose/call-sites.json: Every place the application references this package.
generate/python-jose/scratch/: Every attempt that ran in the sandbox during generation, with its output; not committed.
execute/python-jose/new/: The sealed run on head: the run script, the junit report, coverage, logs.
execute/python-jose/new-rerun/: The second run on head, to catch flakes.
execute/python-jose/old/: The run on the base version, for the differential.

Rendered by tools/build-runs.py from run-index.json and the files it names, with the story from harness/src/harness/story.py. Every value is escaped; nothing here is executed or trusted.

Who, what, why, where, when

Decisions the harness made

Actions it took

Actions it did not take, by design

How it happened, stage by stage

Read

Did

Wrote

Read

Did

Wrote

Read

Did

Wrote

Read

Did

Wrote

Read

Did

Wrote

Read

Did

Wrote

Read

Did

Wrote

Read

Did

Wrote

Read

Did

Wrote

Read

Did

Wrote

Read

Did

Wrote

python-jose 3.3.0 → 3.4.0

Tests, one row each

What is in this folder, and who it is for

What is in this folder, and who it is for

Everyone

Reviewers (the developer or team that owns the change)

Product Security

Supply Chain Security and auditors

The person who ran the harness

Tools (kept for replay and proof; not meant to be read)