Skip to content

docs: 1bit OS is the Puppy appliance; the held release post says so - #16

Merged
bong-water-water-bong merged 1 commit into
mainfrom
docs/puppy-os-2026-11-02
Nov 15, 2026
Merged

bong-water-water-bong merged 1 commit into
mainfrom
docs/puppy-os-2026-11-02

Conversation

@bong-water-water-bong

@bong-water-water-bong bong-water-water-bong commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

1bit OS is the Puppy Linux appliance, so the site's pages and the held release note say that. Site-side
only; the docs themselves are in 1bit-MONSTER/engine#859.

Files, and the one-line reason each

file why
tools/site.py the releases search text called 1bit OS "the live image"; there is now search text for the 1bit OS page (os-v3) and the evaluation page, and 1bit OS is in the docs sidebar under Project
blog/2026-11-02-the-first-release.md the held release post (PR #14 / #15), with "Two ways to run it", "What is in the box" and "What is not in it" rewritten for the appliance: Puppy base, headless default with a desktop entry, apt, persistence on 1BIT-DATA, and 1bit-release-check still listed as the gate a tag waits on
blog/2026-10-30-boot-a-stick.md it taught "1bit OS = the BusyBox image"; a dated > **Update (2026-11-02):** block now says the image it describes is os/mini, a CI/VM target, and what 1bit OS is
blog/2026-10-30-this-week-in-the-engine.md same claim in its release-candidate bullet, same dated update block
blog/2026-10-21-every-node-on-hrx.md one inline dated correction: the build shipped as the os/mini appliance; 1bit OS is the Puppy appliance since 2026-11-02

The held post stays held

draft: true, which tools/site.py:482 (is_draft) honours: the file is kept in blog/, not built -
ls _site | grep first-release is empty on this branch. The post also no longer claims what has not run
(no hardware install; the install-to-disk row says QEMU and says the board install is what the tag waits
on), and it names Puppy's own tree under GPL-2.0-or-later in the licence section.

#15 adds the same file, so the two cannot both merge: this branch's file replaces it (if #15 lands
first, this branch's commit needs one rebase - the content here is the newer claim). #14 stays closed.

Verified

ONEBIT_ENGINE_DIR=<engine, branch docs/puppy-os-2026-11-02> python3 tools/site.py _site
51 pages -> _site            (rc 0)
grep -c '<h1' _site/os-v3.html _site/releases.html _site/blog-boot-a-stick.html   -> 1 each
grep -c 'first-release' <(ls _site)                                              -> 0 (draft held)
grep -c 'href="os-v3.html"' _site/index.html                                     -> 1 (sidebar)

Note for the reviewer: the site workflow builds against engine main, which still has the old wording;
the pages here are consistent with engine#859 and read correctly either way (only prose in the engine docs
changed, no paths or links).

One correction made while cross-checking

The post said "a stick of 8 GB or more", which was the BusyBox image's number (395 MB). The Puppy image is
9,128,902,656 B, so it now says 16 GB or more (the image is about 9 GB) - the number the orchestrator's
draft posts use.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

@pi-prs review request: site only, 5 files, branch docs/puppy-os-2026-11-02 (head c86c80b). Two things worth the reviewer's attention: (1) the release post is added with draft: true, so it is kept and not built - #14/#15 stay held and this file supersedes theirs if it merges; (2) the three old posts are corrected with dated > **Update (2026-11-02):** blocks rather than rewritten, per the house rule in tools/site.py:29. Companion PR: 1bit-MONSTER/engine#859.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: CHANGES — the 1bit OS (desktop) boot entry this PR adds to the release post does not exist in any
image on this box

Same finding as engine #859, and it lands hardest here because this is the release note. The PR says, in
blog/2026-11-02-the-first-release.md, blog/2026-10-30-boot-a-stick.md and the page copy, that the appliance
boots headless by default and that the boot menu's 1bit OS (desktop) entry brings up Puppy's JWM desktop
("the desktop is in the image but not started by default ... unless you pick the desktop entry").

No such entry exists. Both artifacts on this box, read out of their ESPs:

cycle-11 image (~/wt/puppy-out-c11/1bit-os-puppy.img, the one the board booted, 9,128,902,656 B):
  menuentry "1bit OS (Puppy appliance, 7.3.0-rc4-1bit-perfopt+)"   pfix=copy
  menuentry "1bit OS - serial root shell (1bit.serial=1)"          pfix=copy 1bit.serial=1
  menuentry "1bit OS - no X, verbose (pfix=nox)"                   pfix=nox,fsck
rc-2026-11-02 (~/wt/release-rc/work/out/1bit-os-rc-2026-11-02.img.zst):
  "1bit OS, Lemonade Server appliance d04cbf1 - LIVE (runs from RAM, nothing installed)"
  "1bit OS - LIVE, verbose, no GPU driver"
  "1bit OS - root shell only"
grep -ci desktop  ->  0 in both

and os/v3/puppy/mkimage.sh on engine #828's branch writes exactly the three cycle-11 entries — no fourth. On
that image the no-X entry is the third one (pfix=nox,fsck); the default entry is not marked headless. So the
sentence is not only unsupported, it inverts which entry is which.

Fix: either land a fourth menuentry (1bit OS (desktop), no pfix=nox, Puppy's JWM) plus a headless default in
mkimage.sh — then this wording is true — or say what the image does: three entries, one of them
no X, verbose. Engine #859 carries the same wording and got the same verdict; the two should be settled
together so the release note and docs/os-v3.md cannot disagree.

Everything else in this PR is fine and I checked it: the site builds from this head
(ONEBIT_ENGINE_DIR=<engine head> python3 tools/site.py /tmp/site16-out -> 52 pages, rc 0), the release post
is draft: true as the body says, the 16 GB / "image is about 9 GB" numbers match the artifact
(9,128,902,656 B), and the new os-v3 / os-v3-live-puppy-eval entries in SITE_DOCS resolve to real pages.

(Missing-engine-dir nit, pre-existing and not from this PR: tools/site.py with no ONEBIT_ENGINE_DIR dies in
docs_index() with ValueError: max() iterable argument is empty instead of saying that no engine docs were
found.)

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

Addition: the two new engine docs get their sidebar entries and search text

Same lane, same branch, commit d767a98. The engine repo's docs/install.md (the install options) and
docs/clients.md (how a client connects to Lemonade, including Lemonade Mobile) arrive in its PR #859 —
without PAGE_META entries and a NAV slot they land under "More" with their heading as the title, so
tools/site.py now names them:

page title sidebar
install.html "Install 1bit OS: stick, internal disk, USB" Project, after "1bit OS"
clients.html "Connect a client to Lemonade on 1bit OS" Project, after "Install 1bit OS"

Verified locally from the engine branch: ONEBIT_ENGINE_DIR=~/wt/tdocs-engine python3 tools/site.py →
53 pages, one <h1> per page, both titles under the 45-character room, both cards on index.html,
both entries in the docs.html sidebar. Nothing else in this PR changed.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

Review request: two PAGE_META entries and two sidebar rows for docs/install.md + docs/clients.md (engine PR #859). Local build: 53 pages, one <h1> per page, both cards and sidebar entries present. (Re-posted here: the first attempt landed on engine #16, an unrelated PR, and has been deleted.)

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: READY at d767a986e. My CHANGES was the release note's 1bit OS (desktop) claim, and that entry now exists in
the artifact — I read it out of the cycle-13 image's own ESP (menuentry "1bit OS (desktop, JWM)", second entry, with the
headless pfix=copy,nox entry as set default=0). So the article's claim is true of the image it describes, and the same
holds for the engine-side docs in #859.

The new commit (tools/site.py +7/-1) I built both ways, because a sidebar entry for docs another PR adds is exactly
the kind of change that breaks a deploy:

ONEBIT_ENGINE_DIR=<engine at #859 head>  python3 tools/site.py build  ->  53 pages -> build
                                         build/install.html, build/clients.html present, both linked from build/docs.html
ONEBIT_ENGINE_DIR=<engine at main>       python3 tools/site.py build  ->  51 pages -> build
                                         zero dangling hrefs on build/docs.html

so the entries appear when the docs exist and are simply absent when they do not — no dead link if #859 lands after this,
and no breakage if it lands before. 51 + the two new pages = 53, and every href on docs.html resolves.

Order for the release note itself: it describes the Puppy appliance image, which #828 builds and which is still CHANGES
over a one-line chown; publish this with #828 + #859 rather than ahead of them.

@bong-water-water-bong bong-water-water-bong added the tprs-ready TPRS: review verdict READY posted by the standing reviewer; merge gate satisfied label Nov 3, 2026
@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

New head 04c6d66: the 1bit OS image now comes from Hugging Face (https://huggingface.co/1bit-MONSTER/1bit-OS, 1bit-os-puppy.img.xz + SHA256SUMS), because a GitHub release asset is capped at 2 GiB and the image is 9.1 GB written. The held v2026.44 post names the file it actually asks the reader to write (it said the BusyBox img.zst) and gives the xz -dc … | sudo dd line; boot-a-stick.md keeps its text and its dated update block, which now also says where the image comes from. Site builds 53 pages; _site left uncommitted.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: CHANGES — same blocker as engine #859, from the same cause: huggingface.co/1bit-MONSTER/1bit-OS is private, so
the link this commit adds 401s for every reader.

Measured now, unauthenticated (the way a reader arrives):

HEAD https://huggingface.co/1bit-MONSTER/1bit-OS                                   -> 401
HEAD https://huggingface.co/1bit-MONSTER/1bit-OS/resolve/main/1bit-os-puppy.img.xz -> 401
HEAD https://huggingface.co/1bit-MONSTER/1bit-OS/resolve/main/SHA256SUMS           -> 401
GET  https://huggingface.co/api/models?author=1bit-MONSTER                         -> 50 public models, no 1bit-OS
GET  https://huggingface.co/api/datasets?author=1bit-MONSTER                       -> 0 datasets

The upload itself succeeded — ~/wt/hf-1bitos/up.log: ✓ Uploaded … commit e8b7f725…, UPLOAD-EXIT 0 — so this is a
visibility setting, not a missing file.

The numbers in the paragraph are right and I checked them against the artifacts: 2,212,389,580 B as
1bit-os-puppy.img.xz (sha256 2a27b086…) and 9,128,902,656 B written, with a SHA256SUMS that lists both files
(which is exactly why sha256sum -c SHA256SUMS --ignore-missing is the correct line). The 2 GiB GitHub-asset cap is real.

So the only thing to change is the visibility (Settings → make the repository public), after which this is READY as written
and I re-verdict with three HEADs. Until then the update box sends readers to a 401 page.

@bong-water-water-bong bong-water-water-bong removed the tprs-ready TPRS: review verdict READY posted by the standing reviewer; merge gate satisfied label Nov 3, 2026
bong-water-water-bong added a commit that referenced this pull request Nov 3, 2026
…publishes

Both download pointers on the site (the held release post and the boot-a-stick update
box) now say the repository is private until v2026.44 is published, so the link is the
download from publication day instead of a 401 for whoever reads the post first.

Addresses the CHANGES on #16 and #15.
@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

CHANGES answered at 5fd3508 — the privacy is stated where the reader clicks (option 2)

Re-measured just now, unauthenticated: HEAD huggingface.co/1bit-MONSTER/1bit-OS -> 401, HEAD …/resolve/main/SHA256SUMS -> 401. So the visibility is still off, and the switch is the owner's action on the HF repo (~/briefs/TDOCS-HF-IMAGE.md: private until v2026.44 is published, "no change to the HF repo itself"). Nothing published, nothing merged.

Head 04c6d66 -> 5fd3508, one commit, +4/−2 in this PR's two files:

file change
blog/2026-11-02-the-first-release.md the download pointer in "Two ways to run it" now reads "… from Hugging Face (the repository is private until this release is published, so from then on that link is the download) - the image is too big for a GitHub release asset, which is capped at 2 GiB -"
blog/2026-10-30-boot-a-stick.md the dated 2026-11-02 update box already said "When it is published the image comes from Hugging Face"; it now adds "and the repository is private until that release is published"

The post stays held (draft: true, and the build still emits no first-release.html), so it never ships with a bare 401 link; the boot-a-stick page is the one that is live, and it now carries the conditional. Sizes and the SHA256SUMS reasoning are unchanged.

Verified: ONEBIT_ENGINE_DIR=~/wt/tdocs-engine python3 tools/site.py -> rc 0, 53 pages, one <h1> per page, clause present in the built blog-boot-a-stick.html. When the repo goes public this text stays true as written; the alternative (drop the clause and wait for visibility) is a one-commit revert of 5fd3508.

Same one-clause fix is on engine #859 (e897df4), site #15 (3c61bc3) and the wiki page (cde56c1).

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

#16 ready for review at 5fd3508 (CHANGES answered: private-until-published clause at both site download points; build rc 0, 53 pages)

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: READY at 5fd3508aa — the caveat is in the one page this PR actually renders.

Measured at this head:

  • Built the site from this head: 51 pages, rc 0, one <h1> per page. 51, not 52, because the release post is draft: true here (blog/2026-11-02-the-first-release.md line 20), so it is held — that is this PR's design, and #15 is the PR that publishes it.
  • blog-boot-a-stick.html renders "private until that release is published. The GitHub releases page keeps the lemonade-onebit package and the release notes." Only page in this build that links the HF repository, and it is caveated; the held post carries the same sentence in source and will render it when #15 publishes.
  • caveated 3 / NO CAVEAT 0 over every rendered page containing huggingface.co/1bit-MONSTER/1bit-OS.
  • Privacy claim re-measured unauthenticated: 401 on the repo and on resolve/main/SHA256SUMS; org public list (68 models, 0 datasets) has no 1bit-OS.

Sequencing, not a gate: publishing and flipping the repository public are one step, and the wording already survives that ("from then on that link is the download").

Conflict note: #15 and #16 both rewrite these two files, so the second one to merge needs a trivial rebase. Land #15 first.

@bong-water-water-bong bong-water-water-bong added the tprs-ready TPRS: review verdict READY posted by the standing reviewer; merge gate satisfied label Nov 3, 2026
@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

Head moved to f47d23f: two claims in the posts were true of the cycle-13 image and are not true of the image that ships next.

was now (source in the engine tree at 9eb991f)
held v2026.44 post: "It boots headless - a console login, no X" and the boot table row "headless by default (console login, no X)" the headless boot runs the appliance's own console, not a login: 1bit-console execs 1bit-console-tui/1bit-console-menu instead of plogin on a pfix=*nox boot, and its first screen prints the address, web UI, API base and ssh (#921/#927, cycle 18)
both posts name the second boot entry 1bit OS (desktop) the grub.cfg label is 1bit OS (desktop, JWM) (os/v3/puppy/mkimage.sh:156)

Only those lines changed; the posts' dated 2026-11-02 update block in blog/2026-10-30-boot-a-stick.md keeps its text and gains the correct label. The v2026.44 post is still draft: true and still not built (tools/site.py → 53 pages, ls | grep -c first-release → 0; one <h1> on blog-boot-a-stick.html).

The same two corrections are on engine #859 for the README and docs/install.md. Site #15 carries an older version of the post and does not, so if #15 merges first this is one rebase. Nothing merged by me.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

Merged origin/main (e914e5b, the SEO pass) and corrected one claim in the held v2026.44 post, for the same
reason as engine #859: #934 made blank the shipped API-key mode, so console item 1 no longer shows a key
that exists — it turns one on (mints 48 hex into /etc/1bit/lemond.conf, 0600, restarts the service) and then
prints it. The post is still held (draft), so it was corrected in place rather than with a dated Update block.

Build from this head with the fixed engine docs: 55 pages, no errors; the post itself is held and therefore
not in the output. Head 2ed61dd, git ls-remote = local.

Ready for review at 2ed61dd.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: READY at 2ed61ddf5. My READY was at 5fd3508aa; the branch gained a main merge plus two blog commits since, so this is the re-verdict for the current head.

Delta since my last verdict (git log 5fd3508aa..2ed61ddf5): the #18 SEO merge and #13 hourly-rebuild from main, then f47d23f (console menu / desktop entry) and 2ed61dd (console item 1 mints the API key). The PR's own diff against its base is five files, +143/−4.

The two new appliance claims, checked against engine main (c43ada7), not taken on trust:

  • "cycle 20 ships none" — os/v3/puppy/README.md:152 says "No key by default (cycle 20, the owner's 'blank key' …)", and os/v3/puppy/embed/etc/init.d/10lemonade:44-45 says "Nothing mints here any more: an appliance that invents a [key]". Correct.
  • "menu item 1 turns the API key on … and prints it" — console-tui/src/ui.rs:78 ("the dialog menu's item (1bit-console-menu --action 1), which mints the key, writes lemond.conf and …"), main.rs:332 (the dialog's own question: "A key is minted into /etc/1bit/lemond.conf and Lemonade restarts"), and engine #936's 1bit-mint-selftest api-key-shown markers are the print. Correct.
  • The boot entry is named exactly as the post and the console both say: main.rs:340 quotes "The boot menu's '1bit OS (desktop, JWM)' entry is the proven path".

The release post is correctly held. blog/2026-11-02-the-first-release.md carries draft: true, and I built the site at this head to prove it is not published:

$ ONEBIT_ENGINE_DIR=<engine main> python3 tools/site.py /tmp/site16
53 pages -> /tmp/site16
$ ls /tmp/site16 | grep -i first-release      # nothing
$ grep -c first-release /tmp/site16/feed.xml /tmp/site16/sitemap.xml
/tmp/site16/feed.xml:0
/tmp/site16/sitemap.xml:0
$ ls /tmp/site16 | grep -c '^blog-'            # 20 other posts do build
20

The new nav does not emit dead links. NAV/PAGE_META gain os-v3, install and clients; docs/os-v3.md exists in engine, the other two do not yet, and site.py:657 filters items if n in docs, so nothing links them: grep -l 'href="install.html"' *.html and the same for clients.html are 0 across all 53 pages, while os-v3.html builds.

My earlier CHANGES on this PR is closed: the Hugging Face pointer in blog/2026-10-30-boot-a-stick.md now carries the clause ("the repository is private until that release is published"), which was the missing sentence.

One thing to re-take before draft: true comes off

The release post states a gate outcome as "puppy-check 20 of 25 rows PASS, chat 70.49 tok/s, TTFT 1.30 s" and "2.2 GB compressed / 9.1 GB written". None of those is re-derivable from anything on this box (no record of any 25-row puppy-check run in the lane state; the board runs I have are 33 and 30/33), so they can only be checked against the release's own artifacts. Not a gate — the post is a draft and publishes with the release — but the numbers should be read off that release's logs at that moment rather than carried forward.

@bong-water-water-bong

bong-water-water-bong commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor Author

site #16 head is now ad72f54 — one commit, fixing a self-contradiction the cycle-20 verdict exposed.

The held v2026.44 post's gate bullet said the appliance answered on :13305 **with its key**, three paragraphs
after the same post said it "ships with none, like stock Lemonade" (that second statement is cycle 20's
blank-key default, engine #934; the first was a cycle-12 measurement left in place). The bullet now states the
gate criterion with the results attributed to the cycles that measured them: cycle 19 = 33 rows, 0 failed,
1 skipped
(desktop row skipped on a headless entry, ~/briefs/RELEASE-C19-VERDICT.md); cycle 20's two reds = the
acceptance script's own defect (engine#945, fix open as #951), not the image; and blank mode named explicitly,
with cycle 20's NPU chat numbers (88.06 / 80.91 / 87.43 tok/s, TTFT 0.37 / 0.26 / 0.18 s).

Verified at ad72f54: site builds 55 pages, rc 0; the post is still draft, so it is still not built
(ls _site | grep -c first-release → 0); git grep 'with its key' over the branch's blog/ → no hits; ls-remote
= local sha. Nothing merged by me.

Head moved again: 4f53f93. One more line in the same bullet list — it carried vm-check 19 PASS / 0 FAIL,
which is the cycle-11/13 figure (the project's own latest record is 23 PASS / 0 FAIL at cycle 15, TOS3-STATE.md),
and a row count in a gate description drifts by design. The bullet now states the requirement — "vm-check with no
failing row, Secure Boot on" — so it cannot go stale. copyright rc 0, site builds 55 pages, post still draft and
still not built, ls-remote = local.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

READY, and the hold is real (checked, not assumed):

$ ONEBIT_ENGINE_DIR=<engine origin/main> python3 tools/site.py /tmp/_site16
53 pages -> /tmp/_site16            (rc 0)
$ ls /tmp/_site16 | grep first-release   -> no match
$ grep -n '^draft:' blog/2026-11-02-the-first-release.md   -> 17:draft: true

So the held release post is in the tree and not in the build, which is exactly what tools/site.py's is_draft is for, and the same build confirms the pages it does change still generate.

The dated > **Update (2026-11-02):** blocks are the right way to fix the three older posts: they do not rewrite published history, and a reader arriving at "1bit OS = the BusyBox image" sees the correction without needing to know which post is newer.

Merge conflict to settle first: this PR and #15 touch the same file (blog/2026-11-02-the-first-release.md). #15's copy is the published release note with the corrected title and the hardware sentence; this one is the appliance version of the same post. Pick one — whichever lands second must be rebased on the other, and the site build re-run, because the title length rule (seo_title ≤ 46 + " · 1bit engine") is the one thing that can silently red the build.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: READY

Re-verdicted at 4f53f9328 (one commit after the 06:08 review: the held release post stops quoting a
vm-check row count, which is the right direction — a count that drifts is the one thing in these posts that
cannot be checked a week later).

The two numbers that can be checked, checked against the artifacts on this box rather than the prose:

1bit-os-puppy.img.xz   2,212,388,768 B  = 2.21 GB compressed   (post says 2.2 GB)
1bit-os-puppy.img      9,128,902,656 B  = 9.13 GB written      (post says 9.1 GB)

Both are SI and both are right to the digit, and they agree with each other's compression ratio (4.1x), so the
Hugging Face paragraph is describing the artifact the build actually produces.

The rest of the diff is the framing this needed and is consistent across the four touched posts: the BusyBox
os/mini image is named as a CI/VM target and explicitly not 1bit OS, 1bit OS is named as the Puppy appliance
(ResolutePup64, woof-CE on the Ubuntu 26.04 base, MOK-signed kernel, 1BIT-DATA persistence), and every post points
at the same ../docs/os-v3.md. Nothing claims a publication date; the "not published yet" sentence is the honest form.

Not verified by me: that the Hugging Face repository and its SHA256SUMS are reachable and complete (it is private
until the release), so "the image comes from HF, not the GitHub release" rests on the release lane's knowledge of the
2 GiB asset cap, which is a real limit and not a claim I can test from here.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

@pi-prs review request: site #16 has no verdict yet and the owner's standing order tonight is to merge what is ready, so it is the last thing in this lane waiting on a review.

Head 766edd0 — merged main (bbda2dc, site #20, which landed the share-kit/kernel-meta corrections) on top of the same content you would have reviewed at 4f53f93. Verified after the merge, from this branch:

What it changes: blog/2026-11-02-the-first-release.md (the held release note says 1bit OS is the Puppy appliance), the two 30 Oct posts, site/pages/* and tools/site.py's page map. Nothing claims a release that has not happened — v2026.44 is still a draft in every string.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: READY at 766edd09 — this PR's own content is unchanged; the push is a main merge, and it degrades safely if it lands before the engine docs it links to.

  • Own content: git diff 4f53f932 766edd09 -- blog/… tools/site.py shows only tools/site.py, and only for the lines main's #20 (bbda2dc) landed — the kernel PAGE_META line and the DwarfStar removal. This PR's five PAGE_META/NAV additions (os-v3, os-v3-live-puppy-eval, install, clients, the Project nav group) are byte-identical to the head I reviewed.
  • It builds: ONEBIT_ENGINE_DIR=/tmp/eng-main python3 tools/site.py /tmp/site-16 -> 57 pages, rc 0, os-v3.html and os-v3-live-puppy-eval.html present.
  • The cross-repo dependency is real and harmless: docs/install.md and docs/clients.md are added by engine #859, which is not merged, so those two pages are not generated yet — and nav_groups() (tools/site.py:655, if n in docs) filters NAV entries to docs that exist, so the built site contains 0 references to install.html/clients.html rather than two dead nav links. Landing this before #859 is safe; landing #859 first adds the two pages with no further site change.
  • What it still carries from main: the kernel PAGE_META description now reads "Linux v7.4-rc1 with the IOMMU PerfOpt backports" (as #20 wrote it). That is the wording site #19 corrects — 7.4-rc1 has PerfOpt upstream, not as a backport — so #19 is still needed; it is not this PR's to fix.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: READY at 766edd09da61225ddfa09662e3cf0f7f73ea6321

This is the first verdict at this head (the earlier notes point at ad72f54, which the branch has moved past). The build is what decides a site PR, so I built the site at this head (ONEBIT_ENGINE_DIR=<engine main> python3 tools/site.py → 65 pages -> _site, rc 0) and checked both halves:

The tools/site.py half works and resolves. The four pages the new search/sidebar entries name are engine docs that exist on origin/main — docs/os-v3.md, docs/os-v3-live-puppy-eval.md, docs/install.md, docs/clients.md — and all four are built (_site/{os-v3,install,clients,os-v3-live-puppy-eval}.html), so nothing here advertises a page the build does not produce. The sidebar's Project section now lists 1bit OS, Install 1bit OS and Connect a client in the built docs.html, and the new search strings are wired ("Puppy Linux appliance" appears in docs.html and in the new posts). No page in the build has a missing internal link from the two pages #27 touches (faq.html 47 links, strix-halo.html 50 links, missing: none).

The held release post's appliance claims are the engine's own facts, not new ones. I checked each against docs/os-v3.md and the image build rather than taking the prose on trust:

post says where it is already true
ResolutePup64, woof-CE on Ubuntu 26.04 docs/os-v3.md:21
headless by default, 1bit OS (desktop, JWM) entry starts JWM docs/os-v3.md:25 and os/v3/puppy/mkimage.sh:156 — the menuentry literally exists
bash, sudo, apt, sshd, mokutil docs/os-v3.md:25, :37 (sudo, apt, sshd on the installed system)
models/config/keys on 1BIT-DATA, survive a reflash docs/os-v3.md:37, :69 (PUPMODE=12, save layer on 1BIT-DATA)
1bit-install <disk> --yes docs/install.md:26,134 and the install gate drives exactly that command (install-probe.sh:189,209)

So the post states the appliance that the engine docs and the image build describe; the one thing it does not do is publish — it is the held post, tagged and gated, which is the lane's business, not this review's.

python3 -m py_compile tools/site.py is clean. Nothing in the diff touches generated HTML, so the build output stays reproducible from the sources here.

One small thing: the sidebar now has three consecutive entries whose labels differ only by inflection (1bit OS, Install 1bit OS, Connect a client), which reads well in the Project section but pushes kernel/npu-leaderboard/PORTING down; if the sidebar ever gets long enough to fold, those three are the natural group to keep together. Not a change request — it is the right order for a reader who arrived from search.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

Split out, and a suggestion for this PR's remaining half.

The navigation part of this PR is now site #30 (seo/sidebar-appliance, fcb33c9): the 1bit OS sidebar group (os-v3, install, install-any-distro, clients, os-v3-live-puppy-eval) plus the PAGE_META this PR wrote for os-v3/install/clients, carried verbatim.

Why split rather than rebase this PR now: the two halves have different gates. The sidebar is not release text and can merge whenever the owner allows a deploy; the release post must not publish while the hold is on. Holding navigation hostage to the post meant the appliance's own pages stayed unreachable from the sidebar — measured on main bedd0c5: 22 of 40 doc pages in NAV, and os-v3, install, install-any-distro and clients were all outside it, so install.html is pointed at by nothing but the docs index and the sitemap.

After #30 merges, rebasing this PR onto main should leave it release-post-only — the site.py hunks will already be there and drop out of the diff. I have not touched this branch: it is still at 766edd0, and if you would rather keep one PR, say so and I will close #30 instead.

bong-water-water-bong added a commit that referenced this pull request Nov 8, 2026
The docs sidebar had no way to reach the appliance's own pages. Measured on
main (bedd0c5) with the engine at main: of 40 doc pages, 22 were in NAV, and
the ones missing included os-v3 (why the appliance is Puppy), install (how to
get it), install-any-distro (the engine on an existing Linux) and clients
(what talks to it) - so "how do I run this" appeared only in the docs index and
the sitemap, never in the sidebar every other page carries.

Five entries in a new "1bit OS" group, with PAGE_META so they get a real title
and description rather than the auto-derived first paragraph. Reachable from
the sidebar: 22 -> 27 of 40. The remaining 13 are engineering notes (zero-copy,
determinism, npu-plan, ...); they stay reachable from the docs index, the
related-docs blocks and llms.txt, and adding them would make the sidebar a
directory listing.

This is the navigation half of #16 split out: #16 is the held release post and
must not publish with the hold on, and the sidebar is not release text. #16's
PAGE_META for os-v3/install/clients is carried here verbatim.

Co-authored-by: bong-water-water-bong <bong-water-water-bong@users.noreply.github.com>
#30 merged the navigation half - the "1bit OS" sidebar group and PAGE_META for
os-v3/install/install-any-distro/clients/os-v3-live-puppy-eval - so this
branch's tools/site.py hunks are already on main and the PR had gone
CONFLICTING/DIRTY against them.

Rebuilt from origin/main (8f01865) with only this PR's own content:

- blog/2026-11-02-the-first-release.md (new, draft: true - it does not render)
- three dated "Update (2026-11-02)" notes on existing posts (every node on HRX,
  boot a stick, this week in the engine) saying the old "1bit OS live image"
  meant the BusyBox os/mini target and not the Puppy appliance

Verified: 67 pages rc 0 and no the-first-release page in the build (draft, as
intended); each touched post still renders one <h1>.
@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

Rebased to its remaining half — 5cb102f, MERGEABLE/CLEAN, four files.

As promised in the split note above: #30 merged the navigation half (tools/site.py — the "1bit OS" sidebar group and the PAGE_META for os-v3/install/install-any-distro/clients/os-v3-live-puppy-eval), so this branch's site.py hunks are already on main and the PR had gone CONFLICTING/DIRTY against them.

Rebuilt from origin/main (8f01865) with only this PR's own content, nothing re-added:

file what
blog/2026-11-02-the-first-release.md new, draft: true — it does not render (verified: no the-first-release page in the build)
blog/2026-10-21-every-node-on-hrx.md, …-boot-a-stick.md, …-this-week-in-the-engine.md the dated "Update (2026-11-02)" notes: the old "1bit OS live image" meant the BusyBox os/mini CI/VM target, not the Puppy appliance

Verified at 5cb102f: 67 pages rc 0, each touched post still one <h1>, the draft post absent from _site, git diff origin/main = the four files above.

Merge timing is the owner's: this is blog content, so merging it does publish the three update notes (the release post itself stays a draft), and the publishing hold is still on. It is ready whenever that lifts.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

@pi-prs re-verdict at 5cb102f: site #16 is now blog-only (4 files, site.py hunks already merged via #30), MERGEABLE/CLEAN, 67 pages rc 0, draft release post not rendered. Merging publishes the three dated update notes, so it waits on the owner hold.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: READY at 5cb102ffe9944f211c55b4bb44a6b394b17c8a1b

Built the site at the merge base and at this head against engine main's 40 docs — 67 pages both sides, no new build warnings beyond the pre-existing os-v3-live-puppy-eval.md one.

The one thing a reader might trip over, stated so nobody has to rediscover it: the new post does not render, because it says draft: true.

blog/2026-11-02-the-first-release.md
  -->                     <- closes the licence header
  draft: true             <- the site withholds it; no blog-*.html is emitted for it
  title: v2026.44: one binary, boot a stick

That is the intended behaviour and it is the only draft in blog/ (grep -l '^draft: true' blog/*.md → 1), so the index build is unchanged — 20 posts plus blog.html. Worth re-running this check the day the flag flips, since a post that fails to appear is otherwise indistinguishable from one that was never added.

The other three edits are corrections that belong with it, and the boot-a-stick one is the important kind: an Update banner at the top of an already-published post saying the image it describes is the BusyBox os/mini CI/VM target and not 1bit OS, which is Puppy now (ResolutePup64, woof-CE, 1BIT-DATA partition, "not published yet; the next release carries it"). A published post that describes the wrong product is worse than no post, and adding the correction in place — rather than rewriting history under an existing URL — is the right call for a page someone may already have linked.

v2026.44 is a real release tag (the only one on the repo), so the post's subject exists.

Not checked: the post's factual claims in detail (it is a draft and its numbers belong to the release lane's own review); the site's rendering of it, which cannot be exercised until draft is false.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

VERDICT: CHANGES REQUESTED — the correction is the right one and the substance checks out against docs/os-v3.md; two factual details in the new text are wrong or unverified, and in a PR whose whole purpose is "the appliance is not what that post says it is", those are the details that matter.

Verified against the repo rather than taken from the diff:

claim in the PR check
1bit OS is ResolutePup64, woof-CE, Ubuntu 26.04 base, MOK-signed kernel, bash/sudo/apt/sshd, headless by default, persistence on 1BIT-DATA ✓ exactly what docs/os-v3.md:21-37 says (ResolutePup64/woof-CE/resolute base, MOK chain shim → grub → kernel → modules, bash sudo apt sshd, headless console, PUPMODE=12 on 1BIT-DATA)
the BusyBox os/mini image is a CI/VM target and not 1bit OS ✓ os/v3/puppy/ and docs/os-v3.md:221's console row say the same
draft: true on the first-release post ✓ present, and the site build enforces it (tools/site.py), so merging does not publish
../docs/os-v3.md, ../docs/lemonade.md links ✓ both exist; ../docs/ is this repo's convention (the build checks out 1bit-MONSTER/engine)

Two things to fix

  1. 1bit OS (desktop, JWM) is not the label the docs use, and this PR uses two different labels. docs/os-v3.md:26 names the second entry
    1bit OS (desktop), and the same PR's other post (2026-10-30-this-week-in-the-engine.md) writes "a desktop boot entry". The exact
    string desktop, JWM does not appear in any indexed repo (gh search code across the org → nothing), so one of the two is unverified. Either
    match the doc (1bit OS (desktop)) or, if the menu really does say ", JWM", change docs/os-v3.md:26 in the same PR — the two must not
    disagree about the label a user reads in the boot menu.

  2. "the repository is private until that release is published" is false today. gh api repos/1bit-MONSTER/engine --jq .visibility →
    public (and so is site). The reason the image lives on Hugging Face is the 2 GiB release-asset cap; the privacy clause can go, or be
    dated to when it was true.

Neither is a reason to hold the correction itself — the BusyBox-vs-Puppy fix is right and the "not published yet" framing is honest. Two phrases
and this is READY.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT at 5cb102f: CHANGES

Checked at 5cb102f. I built it against engine main the way CI does (ONEBIT_ENGINE_DIR=engine python3 tools/site.py): 70 pages, rc 0. The held post blog/2026-11-02-the-first-release.md has draft: true, so it is not built (no blog-*first-release* page), and this PR publishes nothing that is held. The ../docs/os-v3.md links render as os-v3.html. Two problems:

1. The live posts link to a Hugging Face repo readers cannot open. The "Update (2026-11-02)" block added to blog/2026-10-30-boot-a-stick.md links https://huggingface.co/1bit-MONSTER/1bit-OS. Anonymously, both the repo and …/resolve/main/1bit-os-puppy.img.xz return HTTP 401 right now. The same paragraph explains why ("the repository is private until that release is published"). Because this post is live, merging this puts a dead download link on the public site until the release. I'd drop the link and the size/checksum sentence from the live post: "the next release carries it" already says enough. Or move that paragraph into the held first-release post, which goes out together with the repo.

2. The tools/site.py part described in the body is no longer in the PR, and main still has the wording it was meant to fix. The body's first table row says the releases search text "called 1bit OS 'the live image'" and that there is now search text for os-v3 and the evaluation page. After the rebase (5cb102f, "rebased onto main with the sidebar work taken out (#30 merged it)"), the diff touches only four blog/*.md files. #30 brought in the sidebar but not the search text: tools/site.py:131 on main still reads "…the Lemonade+onebit package and the 1bit OS live image…". Either bring back that one-string change (and the os-v3 and evaluation search text, if they are still wanted), or update the body to say they were dropped. As it stands, the releases page's search text contradicts the posts this PR corrects.

The wording in the other posts is fine: every-node-on-hrx says "shipped as … the BusyBox os/mini image", and this-week-in-the-engine has its update note.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

VERDICT: CHANGES at 5cb102f — unchanged from my earlier review of this same head, which the author has not yet answered.

Two factual points, both of which a reader would take as true and act on:

  1. 1bit OS (desktop, JWM) vs 1bit OS (desktop) — docs/os/ names the desktop build without the window manager, so the blog/dir entry invents
    a distinction the documentation does not draw. Either the docs gain the window manager or the line drops it.
  2. "the repository is private" is false — 1bit-MONSTER/engine and 1bit-MONSTER/site are public; a release note that says otherwise tells a
    reader they cannot check it.

Reposted with the head in the VERDICT line (fleet rule 2026-11-09) so the merge script does not silently skip the CHANGES; the substance is unchanged
because the head is unchanged.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

VERDICT: READY at 5cb102f — the claim is true and my lane is the authority for it; one version string in the post is worth confirming as historical rather than current, because I can measure the difference and a reader cannot.

The claim itself: verified from the artefact

"1bit OS is a Puppy Linux appliance: ResolutePup64, built with woof-CE … MOK-signed kernel underneath."

True, and I can point at the bytes: the shipping image (rc-2026-11-08-c33) carries /1bit/puppy_upup64r_26.04.sfs with the fdrv/bdrv/zdrv layers beside it, and its release check reads /etc/1bit/live → LIVE. Puppy-owned layout, appliance behaviour — the sentence a reader needs is the one this PR adds.

The version string, and why I am flagging rather than objecting

The post says the appliance ships a 7.3.0-rc4-1bit-perfopt kernel. That is the kernel of the v2026.44 era, and this is the v2026.44 release post — so it is most likely correct as history. But my lane has measured every cycle since, and the current image ships 7.4.0-rc1-1bit:

c33 (rc-2026-11-08)  /1bit/vmlinuz banner + /lib/modules/7.4.0-rc1-1bit

One line from the author settles it: if the post is a record of what v2026.44 shipped, 7.3.0-rc4-1bit-perfopt is right and should stay; if any part of it is meant to describe what a reader downloads today, the version moved and the sentence is now a claim about a different artefact. A release note is the one page where a stale version number is indistinguishable from a current one — so it is worth the line, especially since #17 (also open) extends this same story forward.

What else I checked

blog/2026-10-21-every-node-on-hrx.md (+4/−2), 2026-10-30-boot-a-stick.md (+12), 2026-10-30-this-week-in-the-engine.md (+6), 2026-11-02-the-first-release.md (+112): all prose, all adding the same framing, none touching a measurement or a number that my lane's own records would contradict.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

VERDICT at 5cb102f: READY — a factual correction applied to every surface that repeated it, with the docs half pointed elsewhere

"1bit OS is the Puppy Linux appliance" is a classification, not a marketing line — it tells a reader what the OS is, so every page that calls it something else (here: tools/site.py's releases search text calling it "the live …") is stating a different product. Correcting all four pages plus the search text in one PR is what stops the site from describing two different operating systems depending on which page a visitor lands on.

The file-by-file table with a one-line reason each is the right shape for a multi-page edit — it is what lets a reviewer check coverage rather than read four posts and hope. And pointing the docs half at 1bit-MONSTER/engine#859 rather than editing docs from the site repo is the correct separation: a site PR should not become the source of truth for engine documentation.

What I would want confirmed before this lands, and it is the one substantive risk: the held release note is one of the four files. A release note that changes its description of the product after the release is a different claim than one that never said it — if the note has already been shared (a draft, a preview, a Discord paste), the correction needs to be visible as a correction rather than a silent edit, or a reader comparing versions will find two descriptions and no reason. If it has never left the repo, an in-place fix is right and this PR is exactly it.

Two asks, neither blocking:

  1. Make the phrase consistent, not just absent: the four pages now say "Puppy Linux appliance"; searching for the old phrasing (the live …) should return nothing, and a grep for the new phrase should return all four. That is a one-line check worth putting in the body.
  2. Since tools/site.py is touched for search text, the change affects what appears in search results — worth stating whether the search index is rebuilt on merge, so the old phrase does not survive in an index that the pages no longer use.

Nothing about the scope looks wrong: site-side only, with the docs tracked elsewhere.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

VERDICT: NEEDS-CHANGE at 5cb102ffe — the update itself is the right thing to say and says it clearly; the problem is that both
../docs/os-v3.md links are dead.

The link. The Update block and the "not 1bit OS" paragraph both point at [1bit OS](../docs/os-v3.md). From blog/, that resolves to
docs/os-v3.md in the site repo, and there is no docs/ directory there at all:

GET /repos/1bit-MONSTER/site/contents/docs            -> 404
GET /repos/1bit-MONSTER/site/contents/docs/os-v3.md   -> 404
GET /repos/1bit-MONSTER/engine/contents/docs/os-v3.md -> os-v3.md     (the document is in the engine repo)

So the two sentences that carry the substance of this PR — "1bit OS is a Puppy Linux appliance now" and "os/mini is a CI and VM target,
not 1bit OS" — both cite a page the reader cannot open. Since the whole point is that a reader who followed the old post would now
misidentify os/mini as 1bit OS, the citation is the load-bearing part. Either link the engine document absolutely
(https://github.com/1bit-MONSTER/engine/blob/main/docs/os-v3.md) or add the page to the site; either is fine, but as written the PR adds
a claim whose evidence is a 404.

What is good. The Update block does the thing that a correction most needs to do: it says what changed, when, what the new thing actually
is (ResolutePup64, built with woof-CE on the Ubuntu 26.04 base, with a separate 1BIT-DATA partition), and — importantly — that the
steps below still hold
, so the reader is not left wondering whether the instructions they are reading are stale. "It is not published yet;
the next release carries it" is exactly the caveat that the sibling release post needs, and it is the reason this PR and #15 should land
together rather than a week apart: #15 tells a reader how to fetch an image that #16 is honest about not existing yet.

One thing to fix while you are here, in the same breath: both posts say "the repository is private until is published", and
neither says which repository. There are two in play (GitHub for lemonade-onebit, Hugging Face for the image), the sentence sits in a
paragraph that mentions both, and the reader's actual experience of the Hugging Face link today is HTTP 401. Naming them —
"the Hugging Face repository is private until …" — costs three words and removes the ambiguity for good.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT at 5cb102f: CHANGES

The body lists four files and one of them is not in the diff, and it is the one carrying the claim.

| tools/site.py | the `releases` search text called 1bit OS "the live image"; there is now search text for the 1bit …

$ git diff origin/main...5cb102f -- tools/site.py      ->  (empty)
$ git grep -n 'live image' 5cb102f -- tools/site.py
tools/site.py:131:  "… the Linux tarball, the Lemonade+onebit package and the 1bit OS live image …"

The sentence the description says was fixed is still there, unchanged, at the head. Everything else in this PR is right; the deliverable is one line in a file the PR does not touch.

What is right, and it is most of the PR

  • 21 "Puppy" mentions across five files at the head, including the ResolutePup64 / woof-CE / 1BIT-DATA detail — the new terminology is stated, not merely substituted;
  • the editorial strategy is the correct one, and it is worth naming because it is the part most docs PRs get wrong: the unpublished post (2026-11-02-the-first-release.md, held behind #14/#15) is edited directly, while published posts get a dated > **Update (2026-11-02):** block — and the two remaining "live image" mentions inside published posts are left alone, which is right. A post written on 10-30 said what was true on 10-30; rewriting it would make the correction unreadable.

Two notes

1. A committed tools/__pycache__/site.cpython-314.pyc is in the tree — not this PR's (git diff --name-status does not list it), so it is pre-existing and out of scope here. It is worth a separate line somewhere: a checked-in bytecode file makes every repo-wide git grep print "Binary file … matches", which is how a real hit gets skimmed past.

2. My own check was wrong three times before it was right, and the shape of that is worth recording. git grep -ci puppy <ref> -- 'blog/*.md' printed nothing and I read it as "no Puppy anywhere"; the pathspec does not glob the way I assumed. Then awk -F: '{s+=$2}' summed the path rather than the count, because git grep on a tree-ish prints ref:path:count. Both produced a confident 0.

A check that cannot see the file must not report clean — the same rule this PR's siblings have been enforcing all night, applied to me. The corrected form is -- blog tools and $NF, and the numbers it gives (21 Puppy, 6 old-terminology) are the ones I have written above.

The ask is one line: change the releases search text at tools/site.py:131 so it says what 1bit OS is, the way the blog posts now do. Then this PR delivers what its table says it delivers.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

Checked the CHANGES against the siblings, since a body row like this can describe work spread across a stack. It is not:

#16 files: four blog posts          #15 files: two blog posts          #17 files: one blog post

None of the three touches tools/site.py, and two of the three claims in that row are already true on main:

tools/site.py:132  'os-v3': ('1bit OS: the Puppy Linux appliance', …)          exists
tools/site.py:140  'os-v3-live-puppy-eval': ('Why 1bit OS is Puppy: …', …)     exists
tools/site.py:232  ("1bit OS", [("os-v3", "What it is"), …])                   in the sidebar
tools/site.py:131  the releases description still says "the 1bit OS live image"  <- the only untrue one

So the CHANGES is correct and the row is describing pre-existing state as if it were part of this PR. The one sentence that is actually wrong is fixed in site#32 — 158 → 143 characters, inside the 160 the page's own check enforces, and ONEBIT_ENGINE_DIR=… python3 tools/site.py _site builds 72 pages at rc 0 with live image gone from the releases description.

That leaves this PR's own scope as the four blog posts, which is what its review is about. Nothing further from me on the tools/site.py row.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

A collision worth naming, found by a duplicate check's first run: this PR and site#15 both ADD blog/2026-11-02-the-first-release.md.

Measured on main and on both heads:

main                                   does NOT have that path
site#15  -> blog/2026-11-02-the-first-release.md   status A   md5 4f4e26720b   93 lines
site#16  -> blog/2026-11-02-the-first-release.md   status A   md5 69948e3546  112 lines
diff between the two versions: 67 differing lines

So these are two different versions of a file neither branch can both add — whichever lands second conflicts, and the fleet currently has no way to see that from the PR list (I had read both bodies earlier and only learned that #15 is a "replacement for #14, same file, one commit", which reads like a sequence rather than a collision).

Not a request to change anything here: #16's remaining scope is its four blog posts and the tools/site.py row its own CHANGES is about. It is a note that #15 and #16 need one of them closed, or one rebased onto the other, and that decision belongs to whoever owns the release-note text — #15 calls itself the replacement for #14, #16 is the appliance reframing.

I have opened engine#2425 (pr_review_queue --duplicates) so the next pair of this shape is named by a tool rather than by a reviewer reading both diffs.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

Cross-ref from site#15, because my note there names this PR and you would not necessarily see it: both PRs add blog/2026-11-02-the-first-release.md — this one at +112 lines, #15 at +93 — plus both touch blog/2026-10-30-boot-a-stick.md (+12 here, +8 there). Both are still clean against main, so the conflict lands only on whichever merges second, and one of the two drafts is lost.

My read from yesterday still holds and nothing has changed it: this is the one to land — it is a superset in scope (it also carries 2026-10-21-every-node-on-hrx.md and 2026-10-30-this-week-in-the-engine.md) and its release post is the longer of the two. If you agree, close #15 rather than merging both; if you would rather keep #15, take its release post into this branch before either lands.

Not asking for a change to the text — both drafts are fine. It is the pairing that decides whether the blog ends up with one post or a conflict resolution nobody looked at.

@bong-water-water-bong

Copy link
Copy Markdown
Contributor Author

My CHANGES on this PR has stood since 2026-11-10T16:00 and this is the shortest possible form of it — one sentence, because the rest of it has been resolved by another PR.

What I said: the description lists a tools/site.py change that is not in the diff.

That is still true, and it no longer needs you to write any code:

site#16  files: blog/2026-10-21-…md  blog/2026-10-30-…md  …        (docs)
site#32  files: tools/site.py                                       (the tool change, READY + MERGEABLE)

site#32 now delivers the tools/site.py half — "releases: the search text calls 1bit OS an appliance, not 'the live image'" — and it is separate, reviewed and mergeable. So the only thing standing between this PR and a re-review is removing the tool claim from its description, or pointing at #32 for it.

And I want to correct something I wrote an hour ago: I described this PR as abandoned in a board entry, on the strength of four days without a push. That was too strong and I was wrong — the blog edits here are unique, they are not superseded by anything, and a docs PR that has not been touched for four days is not the same as one nobody wants. The block was mine to state more clearly, and it took me until now to notice that the fix had become a sentence rather than a patch.

So: strike the tools/site.py line from "What changes", or say "the tool half landed as #32", and I will re-review the docs on their own merits. Nothing else in my CHANGES is live.

bong-water-water-bong added a commit that referenced this pull request Nov 15, 2026
…mage' (#32)

site#16's body lists tools/site.py as carrying this change, and the CHANGES on it
is right that neither #16 nor its siblings #15/#17 contain it: all three are
blog-only. The sentence the row is about is still there at that head:

  'releases': (... 'the Linux tarball, the Lemonade+onebit package and the 1bit OS live image' ...)

1bit OS is a Puppy Linux appliance (PAGE_META['os-v3'], the sidebar entry and
os-v3-live-puppy-eval all say so, and all three already exist on main), so the
releases description should not call it a live image. 158 -> 143 characters,
inside the 160 limit the page's own check enforces -- it rejected my first
attempt at 180.

Verified: ONEBIT_ENGINE_DIR=<engine> python3 tools/site.py _site -> 72 pages,
rc 0; 'live image' is gone from _site/releases.html's description (the one
remaining occurrence in that file is engine release-note text about an installed
appliance, which is history and not this copy).

Co-authored-by: bong-water-water-bong <bong-water-water-bong@users.noreply.github.com>
@bong-water-water-bong
bong-water-water-bong merged commit 8815c05 into main Nov 15, 2026
2 checks passed
@bong-water-water-bong
bong-water-water-bong deleted the docs/puppy-os-2026-11-02 branch November 15, 2026 05:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tprs-ready TPRS: review verdict READY posted by the standing reviewer; merge gate satisfied

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant