Historical licensing and toolchain remediation
Development work authorized for Historical distributions om... (STV_PR_008) (PRSA-001) and Build and test environments... (STV_PR_009) (PRSA-003). Prior PRSA-002 implementation is retained and included in regression. No release, tag, commit or publication is performed. The owner removed former hosted Releases; retained history receives a complete historical license supplement.
Changes and verification scope
Ten distinct retained historical archives have matching audited ELK fingerprints. One historical frontend lock dependency set was found across available Git history. The full notices and source references therefore apply to those versions. Thirteen historical archive download roles were retired; 24 generated binary copies were moved to ignored local quarantine, preserving their hashes. Original archives, test results and Git history are unchanged.
Both active environments now use Python 3.13.17 with patched certifi, pip and setuptools. Documentation uses Pillow 13 and implementation uses pytest 9. Exact maintained pins remain in the requirements files. Documentation/test tooling requires Python 3.11+; base package runtime remains Python 3.10+. The offline wheelhouse was resolved separately on actual Python 3.10 and 3.13. Inactive former environments/wheelhouse are retained locally as old evidence. They are not used by the build/test scripts or published as dependency supplies.
The initial requirements install failed on a pre-existing first-line encoding
marker; the requirements file was normalized and installation passed. The
first Python 3.10 offline attempt exposed an omitted version-marker dependency
(tomli), because cross-version pip resolution did not evaluate every marker
for the target interpreter. Resolving under both actual interpreters corrected
this; both attempts remain retained. Final checks are consolidated below.
Review and release limits
The supplement, tooling documentation and new case designs await owner review. Requirement verification and prior concept acceptance are unchanged. No capacity qualification or new release readiness claim is made. PRSA-004 and later findings await separate proposal approval. Removed hosted source archives were not available for inspection and are not republished or described as repaired.
Retained evidence
Both active environments (retained in the engineering checkout)
Offline wheel identities (retained in the engineering checkout)
Current package advisory queries (retained in the engineering checkout)
Official Python provenance (retained in the engineering checkout)
Retired generated archive hashes (retained in the engineering checkout)
Initial requirements install error (retained in the engineering checkout)
Corrected implementation install (retained in the engineering checkout)
Documentation install (retained in the engineering checkout)
Initial cross-version wheel resolution (retained in the engineering checkout)
Actual Python 3.10 wheel resolution (retained in the engineering checkout)
Actual Python 3.13 wheel resolution (retained in the engineering checkout)
Initial offline Python 3.10 attempt (retained in the engineering checkout)
Offline Python 3.10 host checks (retained in the engineering checkout)
Development-only package build (retained in the engineering checkout)
Python regression log (retained in the engineering checkout)
Python JUnit results (retained in the engineering checkout)
JavaScript JUnit results (retained in the engineering checkout)
Final development outcomes
84 regression cases passed: 62 Python cases and all 22 JavaScript cases,
using the refreshed implementation environment. This includes the full existing
browser, Windows-path, host integration, package and legal-build-guard cases;
the two release capacity cases were excluded. The separate Python 3.10 offline
bootstrap/install/build and installed-module identity checks passed.
Both active environments pass pip check. The final OSV query reports no
matches across both environments and all current wheelhouse package versions.
This is a point-in-time advisory check, not a guarantee against unknown flaws.
Exact commands and source/artifact hashes (retained in the engineering checkout)
The initial documentation build ran before the regression JUnit report existed and failed on that missing download target. It is retained in sphinx-initial.log (retained in the engineering checkout). The corrected final build runs after all linked results have been written.
Canonical case results
84 regression outcomes and two standalone integration checks are linked below. New and refined case designs await owner review; historical acceptance remains in prior review records. No requirement verification field is promoted.
Case-result mapping (retained in the engineering checkout)
Historical supplement verification (retained in the engineering checkout)
Final documentation and distribution checks
The normal HTML output was rebuilt successfully with warnings treated as errors. Its download tree contains zero historical STV wheels/source archives. All five rendered supplement downloads exist and match the maintained source files exactly. Strict executable coverage has no unmapped active requirements; the shared validator passes repository-relative evidence checks and complete requirement-to-test coverage. These structural checks are separate from owner review and release approval.
Successful Sphinx build (retained in the engineering checkout)
Successful traceability validation (retained in the engineering checkout)
Rendered supplement/download checks (retained in the engineering checkout)
Historical frontend lock identities (retained in the engineering checkout)
Validation command (<shared-skill> is the configured
reverse-engineer-requirements skill):
.venv-implementation/Scripts/python.exe scripts/check-coverage.py --strict
.venv-implementation/Scripts/python.exe <shared-skill>/scripts/validate_traceability.py docs/_build/html/needs.json --version 1.0 --repo-root . --require-test-coverage