Add a Python SDK: flows declared in your own repository

A data scientist keeps their code where it is and decorates it: `@node`
declares a function's ports beside the function, `Flow(name, nodes=[...])`
says which of them make a flow, and `use(fn, wire=..., **settings)` rebinds
one for a single flow. `fluksio sync` uploads the document plus a generated
import shim per node, so the store still holds a complete, runnable,
git-versioned definition while the code it imports stays theirs.

`fluksio login|run|runs` and `flow.submit().wait()` are the client half, over
the run endpoints that already existed. Runs record the user repository's
commit beside the store's, so "what code produced this number" is answerable
on the side that now holds the code.

- `fluksio/sdk/`: ports, decorators, the flow builder and its checks, the shim
  generator, an HTTP client and sync. Standard library only at import, so
  `from fluksio import node` in a training script pulls in no engine.
- `FlowDef.origin` marks a flow code-defined; `Run.origin_commit` carries the
  repository's commit; `POST /modules/refresh` retires the workers without an
  install, which every sync calls — a worker holds the imported package in
  memory, so an edit to it is invisible until the process goes.
- The canvas shows a generated body read-only and names the repository to edit
  instead; a body edited there stops the next sync rather than being discarded.
- The worker's reporter carries inert `Port`, `node`, `use` and `Flow`, since
  the shim imports a module whose first line declares them.
- `examples/myresearch` is the worked example, `make sync-example` uploads it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012ue1tkFWB1bcGy3aWhCKpU

examples/myresearch/pipeline.py

@@ -0,0 +1,48 @@
+"""Which nodes make up which flow.
+
+Membership is this list, not the file a function sits in: `fit` is declared in
+`train.py` and used by both flows below, once as itself and once rewired and
+reconfigured. Wiring is not membership either — nodes connect because one
+provides a message another requires, never because one imported the other.
+
+    fluksio sync examples/myresearch
+    fluksio run train --lr 0.05 --wait
+"""
+
+from __future__ import annotations
+
+from fluksio import Flow, Port, use
+from myresearch.data import augment, prepare
+from myresearch.evaluate import evaluate
+from myresearch.train import fit
+
+train = Flow(
+    "train",
+    title="Train",
+    nodes=[prepare, fit, evaluate],
+    inputs=[Port("lr", "float", initial=0.01)],
+    outputs=["score", "final_loss"],
+)
+
+finetune = Flow(
+    "finetune",
+    title="Finetune",
+    nodes=[
+        prepare,
+        augment,
+        # The same function, reading `augmented` instead of `dataset` and with
+        # a shorter schedule. `train` is unaffected.
+        use(fit, wire={"dataset": "augmented"}, epochs=3),
+        evaluate,
+    ],
+    inputs=[Port("lr", "float", initial=0.0001)],
+    outputs=["score"],
+)
+
+
+if __name__ == "__main__":
+    # Run it here, with no engine involved: the decorators changed nothing
+    # about calling these functions.
+    dataset = prepare(limit=64)
+    losses = list(fit(dataset["dataset"], lr=0.05, epochs=5))
+    print("losses:", [round(step["loss"], 4) for step in losses])