SDK: artifacts work outside a node, run --follow prints status and queue waits, fluksio cancel

save_artifact/load_artifact outside a node use the worker's own store code in
$FLUKSIO_ARTIFACT_DIR or <tmp>/fluksio-artifacts, so a node can be called by
hand. --follow prints status changes and each node's resource wait; the
placer's waiting snapshot now carries the run. fluksio cancel <run>...

examples/myresearch/__init__.py

@@ -2,9 +2,8 @@
 
 Each node is a thin wrapper over a plain function: `prepare` stores what
 `make_rows` made, `fit` yields what `train_curve` computed, `evaluate` reports
-what `score` worked out. That split is the point — `fluksio.save_artifact` and
-`load_artifact` only work *inside* a node, so a body calling them cannot be run
-by hand, while `python -m myresearch.pipeline` runs the arithmetic beside them
-with no engine anywhere. `fluksio sync examples/myresearch` is what turns the
-wrappers into a flow.
+what `score` worked out. That split is the point — the arithmetic stays plain
+Python, so `python -m myresearch.pipeline` runs it with no engine anywhere,
+while the wrappers own the artifact storage. `fluksio sync examples/myresearch`
+is what turns the wrappers into a flow.
 """