Self-Serve Testing: PR-Based Workflow for Implementation and Ecosystem Teams

[parthshah1]

Enable implementation and ecosystem teams to test changes via PR. A team forks the repo, makes a change, pushes a PR, and CI builds the affected images, triggers a 1-hour Antithesis run, and posts results on the PR???

Version tracking

• Create versions.env — LOTUS_COMMIT, FOREST_COMMIT, etc.
• Build workflows auto-bump versions.env after push
• Nightly runs read from versions.env instead of latest

PR workflow (pr-test.yml)

• Detect what changed (versions.env / workload/ / filwizard/ / ecosystem/)
• Build only affected images, tag pr-<number>
• Auto-select endpoint (filecoin vs filecoin-foc)
• Trigger 1hr Antithesis run + post results on PR
• Fork security: maintainer-approved trigger initially

Implementation team pathway

• Doc: change LOTUS_COMMIT → push PR → get cross-client report
• Doc: network upgrade testing (version + upgrade height)
• Add upgrade-boundary vectors (chain progress, state survival, gas estimation, finality)

Rolling upgrade support

• Update upgrade test workflow for two version tags
• Create run_version_pair_test.yml
• Document: for releases, not network upgrades

Relates to #165, #147