Three fewer things to remember

**The portal link puts itself back up.** It already retried a connection that
raised, but a session that ended *cleanly* — a portal restarting, a proxy
closing an idle socket — returned normally and went straight back round the
loop with no wait at all, so an engine could spin against a portal that was
merely saying goodbye politely. Every ending now reconnects on a delay, and
the delay turns on whether the attempt got as far as attaching: one that stood
up and dropped is a network event and retries at once, one that never stood up
waits longer each time. Jittered, so a portal coming back is not met by every
installation it serves in the same instant. Ping timeouts are named rather
than defaulted, since they are what bounds how long a suspended laptop's dead
socket looks alive, and the keepalive task is awaited so the reason a link
went reaches the log instead of the garbage collector.

**`fluksio enroll <code>`** is the whole command now; hub.fluksio.com is the
default and `--portal` names another. The one command run before anything
works should not need two flags.

**`fluksio run` syncs first.** The reason a run exists is usually the edit
before it, so remembering to sync was remembering to do something the computer
could do — including the worker refresh, which is what makes an edit to your
own package take effect at all. `--no-sync` opts out for a tight loop.

That last one needed discovery fixed: it only ever looked at top-level `*.py`,
so a repository whose code is in a package — the ordinary shape — found
nothing from its own root. It now descends into the packages it holds.

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

docs/getting-started/data-science.md

@@ -26,7 +26,7 @@ Fluksio 0.1.0 — data in /home/you/my-research/.fluksio
   Nodes    /home/you/my-research/.venv/bin/python
            your environment, adopted. Add packages with pip.
   No portal. Pair this installation with:
-    fluksio enroll <code> --portal https://hub.example.com
+    fluksio enroll <code>
   Signed in as admin@example.com
            token in /home/you/my-research/.fluksio/client.json
 ```
@@ -397,6 +397,11 @@ fluksio run train --lr 0.003 --seed 7
 fluksio runs --flow train
 ```
 
+`run` syncs first, so after an edit the command is just `fluksio run` — there
+is no step to forget. `--no-sync` skips it for a tight loop where nothing
+changed, since syncing retires the workers and the next call pays its imports
+again.
+
 `--lr` is typed by the flow's own inputs, so `0.003` arrives as a float. A
 parameter you did not declare, or one of the wrong type, is refused before
 anything executes. It answers immediately with a queued run — training is