propose_revision

md.mostlyright/datasets · Verify this server

Registers a proposed revision and returns its immutable recipe coordinates plus a review link. It then starts EXACTLY ONE run: a replay of the named successful run's retained inputs, which reads no upstream source and never becomes live. Nothing else runs — it confirms no run, promotes no table and approves no repair. Example: {"recipe": { …the whole revision document… }, "sources_from_run": "…"}. Returns {recipe_id, recipe_digest, dataset_id, table_id, source_ids, replay_run_id, repair_review_url}. A replay that needs a confirmation comes back with status held and its projection instead of repair_review_url — show the projected size and runtime to the user and call confirm_run with replay_run_id; do NOT propose again. If the revision registers but its replay does not start at all, the answer is revision_registered_replay_not_started carrying the same immutable coordinates — keep them, fix the replay precondition and propose again. Open repair_review_url with a person once the replay settles; approving the held full run is theirs to do there, in a signed-in browser.