Context
The 1.3.0 frontier smoke test manually exercised a comprehensive set of lifecycle paths (see the "What Was Exercised" and "Repeatable Shape" sections). These should be codified as foc-devnet scenarios so we can confirm we don't regress in future releases.
Note: foc-devnet issue #113 already tracks validation of pricing/termination/calldata changes in devnet. This issue is specifically about codifying the broader smoke test scenarios from the 1.3.0 report as repeatable, optional foc-devnet scenario scripts — covering the full lifecycle including abandonment, negative/security edge cases, and cross-system state validation.
Key scenarios to codify
From the smoke report's "Repeatable Shape" section:
- Create/fund/upload, 40-piece add, repeated adds forcing lockup replenish
- Piece removal with proving period flush
- SP-relayed termination and direct on-chain termination
- Normal cleanup verification (FWSS, PDP, FilecoinPay, Curio state)
- Abandonment flow (stop SP, wait past inactivity, third-party cleanup)
- Negative permission checks (unauthorized termination, malformed payloads, etc.)
Origin
Request from comment on the 1.3.0 smoke report.
Context
The 1.3.0 frontier smoke test manually exercised a comprehensive set of lifecycle paths (see the "What Was Exercised" and "Repeatable Shape" sections). These should be codified as foc-devnet scenarios so we can confirm we don't regress in future releases.
Note: foc-devnet issue #113 already tracks validation of pricing/termination/calldata changes in devnet. This issue is specifically about codifying the broader smoke test scenarios from the 1.3.0 report as repeatable, optional foc-devnet scenario scripts — covering the full lifecycle including abandonment, negative/security edge cases, and cross-system state validation.
Key scenarios to codify
From the smoke report's "Repeatable Shape" section:
Origin
Request from comment on the 1.3.0 smoke report.