picurv run --post-process is incremental: it processes only the requested steps whose output is missing or stale (no output, a changed recipe, or a changed checkpoint) and launches nothing when every step is up to date. Each produced step is recorded in the recipe's state.json; output written before these records existed is kept when it is newer than its checkpoint. Steps need not be contiguous, so a single missing file is reprocessed alone.--recompute regenerates every requested step, for every selected stage. Rebuilding the postprocessor does not invalidate output; the run reports how many steps another build made.--continue now belongs to --solve; on a post-only command it is ignored with a warning.--solve --continue from a start_step before, or past, the run's last committed checkpoint is refused; branch with --restart-from to redo a stretch.picurv submit accepts a post-only staging, submits a study's latest staged set (including sweep --continue --no-submit), and chains the study's metrics aggregation job.[WARNING]/[FATAL] prefixes, several stale or misleading messages are corrected, and post runs no longer list the solver's PETSc options as unused.