Skip to content

fork fleet: desk pool docs, a neutral example, the fork's pc pool on the desk link (D12) - #238

Draft
scuttletoby wants to merge 11 commits into
fork/desk-d11b-seed-fetchfrom
fork/desk-d12-docs
Draft

scuttletoby wants to merge 11 commits into
fork/desk-d11b-seed-fetchfrom
fork/desk-d12-docs

Conversation

@scuttletoby

@scuttletoby scuttletoby commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

Row D12 of the desktop pool plan, the last one: the docs that join D1 to D11 into one path from nothing to a working desk pool, a made-up example entry, and the fork's own pc pool moved onto the desk link. Stacked on #237 (D11b).

Why

The pieces are all there now (link, walls, agent, setup pack, Windows starter, free contract, seeds). What was missing:

  • a page that says in what order to use them
  • an example a project can copy
  • the fork's own pc pool using them

Until now, the pc pool's launch pointed at a hand-made /opt/fork-fleet/launch-pc wrapper that runs commands over plain ssh. That wrapper was never part of the fork.

  • .github/fork-fleet.json: the pc pool's launch is now python3 -I /opt/fork-fleet/fork-fleet-desk.py launch pc, the same as any desk pool. Its _doc says so.
  • .github/fork-fleet.md:
    • The pc pool paragraph now says it is a desk pool, what turns it on (its dispatcher unit and the PC's desk key), and what happens while the PC sleeps (launch exits 3 at once, and its jobs go elsewhere).
    • A host that ran an old pc dispatcher on the wrapper first stops it and lets its runners finish (this config's
      cleanup skips a pool that is down, so it would never stop them); then it may delete the wrapper.
    • Host step 3 installs the key tool fork-fleet-desk-key.py with the other desk files.
    • A made-up desk pool entry, with what waits: false and slots mean for a desktop.
  • fork-kit/desk/README.md: "From nothing to a working pool" in five steps (project config, host once: host step 3
    then the desk link, desktop install, add the key, check). Step 5 quotes the dispatcher's real log lines: a runner
    started on the desktop (RUNNER: started for JOB, attempt N), and pool POOL answers again only after the pool was
    left alone for more than one pass. There is no "link is up" line. Step 2 and host step 3 say that another project points base at its own
    repository.

What happens when this runs again, stops half-way, or meets existing, old or empty state?

Case What happens
Runs again Config and docs only. A re-released config with the same entry changes nothing on any machine.
Stops half-way Nothing here runs. A desk pool set up only partly (no dispatcher unit, or no key yet) has no heartbeat, so route never counts it and no job waits for it.
Existing / old state Once a host's dispatcher for pc runs with the new config, it calls the desk link instead of the old launch-pc wrapper. The wrapper is then unused; the docs say to stop the old pc dispatcher and let its runners finish first, then delete it. Until the PC's desk agent is installed and its key added, launch exits 3 and jobs go to other pools, the same as when the PC is off.
Empty state A fleet with no desk pool is unchanged. The pc pool with no dispatcher stays off, as before.

General vs project

  • General: the five steps, the example entry (made-up names desktop and fleet-desktop-example) and the paragraph on waits/slots.
  • Project: the one-line change to the fork's own pc pool entry in .github/fork-fleet.json, which is this repository's own fleet config. No personal names, addresses or machine ids are in it.

Upstream fit

Only fork-only files (.github/fork-fleet.*, fork-kit/desk/README.md) change. Nothing in upstream T3 changes.

It also lists the stack in FORK_CHANGES.md (new on main since #223): desk in the host kits row with #225, and
#229, #230, #236, #237 and #238 in the fleet runners row.

Tests

No new test file. Round 2 adds one test to fork-fleet-desk-key.test.py: the release's pc pool is a desk pool, so a
typo in its launch fails in CI instead of on the host. The changed config is also checked by the existing tests:

  • .github/scripts/fork-fleet.test.py loads .github/fork-fleet.json, and check_config finds no problems.
  • fork-fleet-desk-seed.test.py and fork-fleet-desk-key.test.py read the pool list from it.

Local run at round 2 (the whole stack merged in):

  • .github/scripts/fork-fleet-desk-key.test.py: 21 OK
  • .github/scripts/fork-fleet-refresh.test.py: 43 OK (1 skipped)
  • .github/scripts/fork-fleet-desk-seed.test.py: 41 OK
  • .github/scripts/fork-fleet-desk.test.py: 42 OK
  • .github/scripts/fork-fleet-desk-agent.test.py: 31 OK
  • .github/scripts/fork-fleet-walls-wsl2.test.py: 15 OK
  • fork-kit/desk/tests/install.test.py: 34 OK
  • fork-kit/desk/tests/windows.test.py: 16 OK (2 skipped: no pwsh here)
  • fork-kit/common/tests/free_contract.test.py: 17 OK
  • fork-kit/common/tests/machine_file.test.py: 17 OK

Round 1: the desk-key test drops the release's own desk pool by name (pc), not with the function under test, and
asserts vm stays; fork-fleet-refresh.test.py's list of root-run files names the desk link's files instead of
launch-pc.

Round 2: the test above; README steps 2, 4 and 5 and host step 3 reworded (see "What" above).

Red-checks

The new desk-key test guards the release config, which is already right, so it passes on round 1 too. With a typo in
the pc pool's launch (fork-fleet-dsk.py), in a copy of the tree, it fails. Everything else is config and docs,
with no new rule to break.

Round 3

  • README step 5 and fork-fleet.md ("The desk link"): answers again is logged only after more than one missed pass; one missed pass then an answer logs nothing.
  • The seed docs from fork fleet: a desktop fetches its desk pool's seeds (D11b) #237 (backoff, exit 1 after a day, .torn.json, run deadline, disk budget) are in the README and fork-fleet.md.
  • Tests (whole stack): desk-key 21 OK, desk-seed 52 OK, desk 42 OK, install 40 OK, fork-fleet 201 OK (7 skipped), windows 20 OK (3 skipped), free_contract 17 OK.

Round 4

  • Merged fork fleet: a desktop fetches its desk pool's seeds (D11b) #237 round 4 (6a6749b).
  • Host steps make /etc/fork-fleet as root's, 0700 and not a link (install -d -m 700), the same rule the kit's check and install use (4631043).
  • The docs match round 4: the install lock is in /etc/fork-fleet; install refuses a linked or non-root-owned /opt/fork-fleet, /etc/fork-fleet or desk key; stricter runner-user checks; the owed-restart mark; Wine names its process after the .exe (fork-kit/common/FREE.md); the seed refuses link members it cannot make and odd sizes, retry times are approximate, a new copy on the host is tried at once, a lost list keeps the torn record, an unwritable .torn.json exits 1, a copy lives about 25 h, and the disk budget is max_mb x (25 / every_hours, rounded up, + 2).
  • Tests (whole stack): desk-key 21 OK, refresh 43 OK (1 skipped), desk 42 OK, desk-seed 59 OK, gate-trust-docs all ok, fork-fleet 201 OK (7 skipped), install 44 OK, windows 24 OK (4 skipped), free_contract 17 OK.

Round 5

  • Merged fork fleet: a desktop fetches its desk pool's seeds (D11b) #237 round 5 (b000dca), which carries fork fleet: desk setup pack kit (D8) #225's round 5. No D12-only change was needed: the docs this PR adds do not describe the back-off, the runner-user group or the folder refusals; the README and fork-fleet.md paragraphs that do come from fork fleet: desk setup pack kit (D8) #225 and fork fleet: a desktop fetches its desk pool's seeds (D11b) #237 and say the round-5 rules (a new host copy skips the wait only once per wait; a runner user's main group must be the group named after it; a linked or non-root units, fork-fleet-walls or other manifest folder is refused; check covers both halves of the desk key).
  • Round 4's seed line, checked line by line against fork fleet: a desktop fetches its desk pool's seeds (D11b) #237's code: link members it cannot make are refused (Tar._find_link_target, unpack); odd sizes are refused (a member, and from round 5 an extended header, with a size below 0; a non-file with a size); retry times are approximate (5 min margin plus the timer's random delay); a lost list keeps the torn record (run returns before reading it); an unwritable .torn.json exits 1 (TornLog.unsaved); a copy lives about 25 h (KEEP_OLD 24 h plus the hourly prune); the disk budget formula matches. One part no longer holds: "a new copy on the host is tried at once" is now "at once, but only once per wait".
  • Tests (whole stack): desk-seed 63 OK, install 47 OK, desk-key 21 OK, refresh 43 OK (1 skipped), desk 42 OK.

🤖 Generated with Claude Code

…n the desk link (D12)

The fork's own `pc` pool now launches through the desk link
(fork-fleet-desk.py launch pc) instead of the never-made launch-pc wrapper.
The runbook gets a made-up desk pool entry any project can copy, and the desk
kit's README a five-step path from nothing to a working pool.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@scuttletoby
scuttletoby force-pushed the fork/desk-d11b-seed-fetch branch from fbf95e3 to ec41bd8 Compare November 15, 2026 20:02
@scuttletoby

Copy link
Copy Markdown
Owner Author

Review round 1 at 6a2c09b (lens238): SAFE WITH NITS. Merging the pc switch before the PC has the desk kit is safe: the host's only dispatcher unit serves vm (.github/fork-fleet.md:505), and an early pc dispatcher fails closed at every half-set-up stage (no socket folder or socket: exit 3; desk script missing: exit 2; Host._must raises, the pool is left alone with heartbeat 0, vm carries on). Fix round to follow with the rest of the stack.

  1. Docs gap, nothing installs the key tool: fork-kit/desk/README.md:15 step 4 runs fork-fleet-desk-key.py add POOL, but host step 3's file list (.github/fork-fleet.md:449-452) installs fork-fleet-desk.py, -wire, -seed, not -key. Following steps 1-5 exactly fails at step 4. Add the key tool to step 3's list and name host step 3 in README step 2 (re-run it from a commit that has the pool entry).
  2. Docs order: the new example and the waits/slots paragraph sit between the key tool's code block and "The line it writes…" (fork-fleet.md:606-625), so "it" now reads as the example; the launch command appears twice within ~10 lines. Move the example below "The pool's launch command … is …".
  3. Old wrapper state (low): a host that ran a pc dispatcher on launch-pc with live runners, then installs this config: the pool is down every pass and leftover cleanup skips down pools, so those runners are never stopped or pruned. Add one clause before "may delete it" (:579): stop the old pc dispatcher and let its runners finish first.
  4. Test nit: fork-fleet-desk-key.test.py:58 drops desk pools using dk.desk_pools(cfg), the function under test; filter by name 'pc' or assert vm stays. The pc subtest now duplicates nope.
  5. Stale list outside this diff: fork-fleet-refresh.test.py:975 still names launch-pc as a root-run file and not fork-fleet-desk.py.

Checked fine: the example entry is neutral; FORK_CHANGES.md rows match the stack; the pc launch line matches desk_pools detection and the runbook. Tests: desk-key 20, desk-seed 20, desk 42 OK.

scuttletoby and others added 3 commits November 15, 2026 20:51
Host step 3 installs the key tool and the README's step 2 names it; the
example entry sits after the key line's paragraph; a host with an old pc
dispatcher stops it and lets its runners finish first; the desk-key test
drops the release's pc pool by name; the refresh test lists the desk
link's files, not launch-pc.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@scuttletoby

Copy link
Copy Markdown
Owner Author

Fix round 1 (commit 6678d64; D11b's round 1 merged in at 6bd6f2e and e7090ff; head e7090ff). Tests: desk-key 20 OK, refresh 43 OK (1 skipped), desk-seed 30 OK, desk 42 OK, desk-agent 31 OK, walls-wsl2 15 OK, install 28 OK, windows 11 OK (1 skipped, no pwsh), free_contract 13 OK, machine_file 17 OK.

  1. Nothing installs the key tool: fixed (6678d64). Host step 3's file list installs fork-fleet-desk-key.py; the desk-link section and README step 2 name host step 3.
  2. Docs order: fixed (6678d64). The example entry and its waits/slots paragraph now come after "The pool's launch command … is …".
  3. Old pc wrapper state: fixed (6678d64). The clause now says to stop the old pc dispatcher and let its runners finish before deleting the wrapper.
  4. desk-key test: fixed (6678d64). The test drops the release's pool by name (pc) and asserts vm stays; the duplicate pc subtest is gone.
  5. Stale list: fixed (6678d64). fork-fleet-refresh.test.py lists the desk link, wire, seed and key files instead of launch-pc.

The docs follow the fixed stack: per-pool seed path, the desktop's own limits, uninstall and drop-ins (merged from the lower branches).

PR body updated. Still draft.

@scuttletoby

Copy link
Copy Markdown
Owner Author

Re-check lens 238 r1 at e7090ff: SAFE WITH NITS

Earlier findings 1-5 FIXED: key tool installed in host step 3 (.github/fork-fleet.md:452, pointed to from :594, :607 and fork-kit/desk/README.md:12; every /opt/fork-fleet/* file the runbook runs is installed there); docs order (:613-635); old wrapper state (:580-584; the dispatcher loads its config once at start, fork-fleet.py:1226); desk-key test (:59, :157); stale list (fork-fleet-refresh.test.py:976-977). Findings 4-5 are test cleanups that also pass on round-0.

The pc switch before the PC has the desk kit fails closed: no unit means no heartbeat; an early unit without socket/session/key makes launch exit 3 and the pool is marked down (fork-fleet.py:981-986, cleanup skips it :1072, :1097, :1112); a broken config makes load() raise (:82-88); re-running step 3 is safe (temp folder, SOURCE written last, fork-fleet.md:455-471). The example entry is neutral and passes check_config; FORK_CHANGES.md rows are right.

Nits:

  1. No test that the release's pc pool is a desk pool (a launch typo would only show on the host):
def test_the_releases_pc_pool_is_a_desk_pool(self):
    self.assertEqual(dk.desk_pools(dk.ff.load()), ['pc'])
  1. README.md:16 promises a "link is up" log line that does not exist; the real line is pool X answers again, after N passes left alone (fork-fleet.py:1138) and only after the pool was down. Quote the real line, or check desk-install check plus a started runner.
  2. Another project's path is unclear: step 1 says release branch, step 2 a main commit, and host step 3's URL is fixed to this repository (fork-fleet.md:440); one line saying to point base at the project's repository.
  3. Wording README.md:15: "the key the install printed".

Tests: desk-key 20, desk-seed 30, desk 42 OK; refresh Timer 8 OK. Other refresh/fork-fleet failures are fork-fleet-launch.sh tests needing a local https server, systemd or the network (not touched by this PR; not re-run on base).

scuttletoby and others added 2 commits November 16, 2026 00:21
…lines, another project's base (D12)

- desk-key test: the release's pc pool is a desk pool (a launch typo shows in CI, not on the host)
- desk README step 5: no "link is up" line; quote the real lines (runner started, pool answers again)
- host step 3 and README step 2: another project points base at its own repository
- README step 4: "the key the install printed"

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@scuttletoby

Copy link
Copy Markdown
Owner Author

Fix round 2

Re-check r1 (SAFE WITH NITS), each nit:

  1. No test that the release's pc pool is a desk pool: fixed (dcd20e2). test_the_releases_pc_pool_is_a_desk_pool in fork-fleet-desk-key.test.py. It passes on round 1 because the config is right; with a typo in launch in a copy of the tree, it fails.
  2. README step 5 promised a "link is up" line that does not exist: fixed (dcd20e2). Step 5 says there is no such line, and quotes the real ones: RUNNER: started for JOB, attempt N and, only after the pool was down, fork-fleet: pool POOL answers again, after N passes left alone.
  3. Another project's path was unclear: fixed (dcd20e2). README step 2 and host step 3 in fork-fleet.md say that another project points base at its own repository and uses a commit of its main.
  4. Wording "the key the install printed": fixed (dcd20e2).

Docs match round 2 of the stack below: this branch merges the round-2 D11b head (223795c). Its README and fork-fleet.md "Seeds" text (the seed service's last result in check, a failed seed keeps the old copy) came with that merge. The PR body has the round-2 test counts and no longer says "no new test".

Tests at dcd20e2, run one file at a time: desk-key 21, desk-seed 41, install 34, desk 42, desk-agent 31, refresh 43 (1 skipped), walls-wsl2 15, windows 16 (2 skipped: no pwsh), free_contract 17, machine_file 17, all OK.

@scuttletoby

Copy link
Copy Markdown
Owner Author

Lens: re-check r2 (lens238r2), read at: dcd20e2 — SAFE WITH NITS

Round-2 findings

  1. Test that pc is a desk pool: FIXED (.github/scripts/fork-fleet-desk-key.test.py:94, reads the repo config via fork-fleet.py:48). Mutation (pc launch typo) makes it fail; passes on round-1 code because the config was already right, so it guards future mistakes.
  2. "Link is up" lines: FIXED (fork-kit/desk/README.md:18-20 quotes real dispatcher output, fork-fleet.py:1118, :1139).
  3. Another project's base: FIXED (.github/fork-fleet.md:441-442, README :12-14).
  4. Wording: FIXED (README.md:17).
    All r0 findings still fixed (fork-fleet.md:453, :620-636, :582-585; desk-key.test.py:57-60).

Merging the pc switch before the PC has the desk kit: safe, fails closed. The host dispatcher unit runs --pool vm only (fork-fleet.md:507, fork-fleet.py:1180); no pc unit means no heartbeat, so route never counts it; an early pc unit gets launch exit 3, pool marked down, cleanup skips it, vm carries on; broken config makes load() raise. Old host that ran launch-pc: covered by the stop-the-old-dispatcher clause (:582-585). Re-running host step 3: temp folder first, SOURCE last (:455-471). Example entry is neutral; no personal data added. FORK_CHANGES.md: host-kits row adds desk and #225; other rows only re-padded.

New nit (low)

  1. README.md:20 says a pool that was down logs "answers again"; the code only logs it after more than one missed pass (fork-fleet.py:1138, gone['passes'] > 1). PC misses one pass then answers: no line, reader may think the link is broken. Fix: "down for more than one pass" or "may log".

Nothing broken by the round; this PR's own diff is docs, tests and config only (the SEED_MAX_MB change came in from the D11b base).

Tests: desk-key 21 OK, desk 42 OK; mutation run fails as expected.

verdict SAFE WITH NITS, PR #238, head dcd20e2

scuttletoby and others added 2 commits November 16, 2026 01:19
…sed pass (D12)

The dispatcher logs "pool POOL answers again" only when the pool was left
alone for more than one pass; one missed pass then an answer logs nothing.
README step 5 and the desk link section now say so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@scuttletoby

Copy link
Copy Markdown
Owner Author

Fix round 3

Commit d8992da (head; D11b merged in as 833bd7c). Findings from lens238r2:

  • New nit 1: README.md:20 claimed "answers again" is always logged. Fixed in d8992da. The line is logged only when the pool was left alone for more than one pass; one missed pass followed by an answer logs nothing. The same sentence in fork-fleet.md ("The desk link") was changed too.
  • Round-3 behaviour in the docs: the seed backoff, exit 1 after a day, .torn.json, the run deadline and the disk budget come in from fork fleet: a desktop fetches its desk pool's seeds (D11b) #237. The README and fork-fleet.md now say all of these.
  • PR body: the "answers again" wording is corrected and a round-3 section is added.

State question: this round changes docs only.

Tests (local, at d8992da, whole stack merged): fork-fleet-desk-key.test.py 21 OK, fork-fleet-desk-seed.test.py 52 OK, fork-fleet-desk.test.py 42 OK, install.test.py 40 OK, fork-fleet.test.py 201 OK (7 skipped), windows.test.py 20 OK (3 skipped), free_contract.test.py 17 OK, fork-gate-trust-docs.test.py all ok.

@scuttletoby

Copy link
Copy Markdown
Owner Author

Lens: re-check r3 (lensd8minr3), read at: d8992da — SAFE WITH NITS

  • Nit 1 ("answers again" logging): FIXED. README:20-21 and fork-fleet.md:643-644 now say it is logged only after more than one missed pass, matching the code: the first missed pass sets passes to 1 (fork-fleet.py:964) and "answers again" prints only when passes > 1 (:1138).
  • The seed docs (backoff, .torn.json, deadline, disk budget) in README:83-84 and fork-fleet.md:755-797 came in through the merge of fork fleet: a desktop fetches its desk pool's seeds (D11b) #237 (833bd7c), not this PR's own commit; nothing in them is wrong.
  • The round-3 commit touches only those two doc lines.

Tests: desk-key 21 OK, desk 42 OK.

State: docs only; nothing new runs.

verdict SAFE WITH NITS, PR #238, head d8992da

scuttletoby and others added 2 commits November 16, 2026 02:10
…eet 0700 (D12)

The desk kit's check and install hold /etc/fork-fleet to root's, 0700 and not a
link (round 4 takes the install lock there); the by-hand block made it 0755.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@scuttletoby

Copy link
Copy Markdown
Owner Author

Fix round 4

Re-check c6904850353:

  • Nit 1 (stale text): already fixed in round 3; nothing new this round.
  • No other findings.

Brief item "docs and READMEs must match round-4 behaviour":

  • Merged fork fleet: a desktop fetches its desk pool's seeds (D11b) #237 round 4 into this branch: 6a6749b.
  • Fixed: the by-hand host step made /etc/fork-fleet without the mode the kit now checks. It now uses install -d -m 700 /etc/fork-fleet and says the folder must be root's, 0700 and not a link: 4631043.
  • Checked: fork-fleet.md, fork-kit/desk/README.md and fork-kit/common/FREE.md match round 4 (the lock in /etc/fork-fleet, link and owner refusals, runner-user checks, the owed-restart mark, Wine's process name, the seed's link and size refusals, approximate retry times, a retry when the host has a new copy, the torn record kept when the list is lost, exit 1 when .torn.json cannot be written, the copy lifetime of about 25 h, and the disk budget).
  • PR body: a new "Round 4" section; no claim goes beyond the code.

Tests (head 4631043): desk-key 21 OK, refresh 43 OK (1 skipped), desk 42 OK, desk-seed 59 OK, gate-trust-docs all ok, fork-fleet 201 OK (7 skipped).

@scuttletoby

Copy link
Copy Markdown
Owner Author

Lens: re-check r4 (lensd8minr4), read at: 4631043 — SAFE WITH NITS

  • Does fork fleet: desk setup pack kit (D8) #225's installer make /etc/fork-fleet 0700? Yes. In fork fleet: desk setup pack kit (D8) #225 (base 1ccced0378) the installer refuses a linked or non-root folder (desk-install:499-502), then creates it and sets 0700 every run (:508-510); the install lock opens it with O_NOFOLLOW (:446). In this tree check holds it to 0700 (desk-install:670).
  • The by-hand step install -d -m 700 (fork-fleet.md:674-678) also sets an existing 0755 folder to 0700 (tried in scratch), so an older hand setup is fixed the next time the step runs.
  • The agent unit runs as root, so 0700 does not stop the agent reading the folder.
  • Round-3 nit: fixed in round 3; still holds.
  • PR body "Round 4" section matches what was checked (lock, refusals, owed mark, Wine). Nit: its seed lines were not re-checked line by line against fork fleet: a desktop fetches its desk pool's seeds (D11b) #237's code.
  • Tests: fork-fleet-desk-key.test.py OK, fork-fleet-refresh.test.py OK (1 skipped).
  • State: docs only; nothing new runs.

verdict SAFE WITH NITS, PR #238, head 4631043

@scuttletoby

Copy link
Copy Markdown
Owner Author

Fix round 5

Merged #237 round 5 in b000dca (it carries #225's round 5).

lensd8minr4

Tests (whole stack): desk-seed 63 OK, install 47 OK, desk-key 21 OK, refresh 43 OK (1 skipped), desk 42 OK.

Still a draft.

@scuttletoby

Copy link
Copy Markdown
Owner Author

Lens: re-check (lensd8minr5), read at: b000dca — SAFE

Round-5 merge is clean: git show --remerge-diff prints nothing.

  • Round-4 nit (seed lines in the body unchecked against fork fleet: a desktop fetches its desk pool's seeds (D11b) #237): FIXED. Each "Round 5" line is true: unmakeable links refused (_find_link_target, fork-fleet-desk-seed.py:380); odd sizes refused (:356-357 headers, :419 members); copy kept ~25 h and the disk budget formula matches (fork-fleet.md:804-805).
  • Docs vs round-5 code (merged paragraphs) all match: back-off once per wait (fork-fleet.md:785-787, TornLog.due :690, trying :697-699); host down exit 0 (:792-793, run :631); missing tarfile parts exit 2 after age-out (:794-797, :599-600, :830, :622); negative header size (:356-357); subfolder refusal (desk-install:518-524, both key halves, check :683-690); own-group rule (desk-install:114-117). /etc/fork-fleet made 0700 every install after the refusal (:529-531), held by check (:683), matches the by-hand install -d -m 700 (fork-fleet.md:678).
  • Optional wording nit (in fork fleet: a desktop fetches its desk pool's seeds (D11b) #237's text): "only once per wait" is looser than the code; a skip can happen at most every other wait ("never twice in a row").
  • State: round-4 .torn.json without early allows one skip (correct); a run killed between trying() and fetch end counts as torn (:699); this PR is docs/config only.
  • Tests at b000dca: desk-key 21 OK, refresh 43 OK (1 skipped), desk-seed 63 OK, install 47 OK, free_contract 17 OK, windows 24 OK (4 skipped).

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant