Standalone Cheap LFS versus Git LFS Pages acceptance — 2026-07-28

Current state

Local Pages acceptance is complete. The assembled site passed the route contracts and an installed-Chrome run through the exact Lowlevel MCP HTTP service. The accepted run completed 35/35 checks across six phases, served 33 requests with 33 HTTP 200 responses, recorded no console, page, request, or HTTP errors, and closed its browser and server.

This local receipt deliberately does not claim a pushed commit, a live route, or a successful Pages deployment. Those post-push results belong in the rolling GitHub Discussion and final publication handoff, where the exact remote SHA and Actions run can be named without pretending they existed during this capture.

The milestone adds a separate /cheap-lfs-vs-git-lfs.html decision surface with:

72 row-level sourced differences in 12 categories;
Cheap LFS, Git LFS, tie, and depends fit signals;
six browser-style tabs with pin, reorder, overflow, hash, and appearance state;
provider-first versus pre-push and product-orbit SVG diagrams;
an exact six-stage Cheap LFS git push handoff beside the Git LFS track/filter/pre-push path;
plain-text, category, and outcome filters plus an explicit worker-isolated regular-expression mode;
an interactive fit finder;
English, playful Hong Kong Cantonese, and bilingual modes with independent persisted 1–5 funny levels; and
desktop and narrow layouts that must avoid document-level horizontal overflow.

Evidence boundary

The two SVGs are concept diagrams, not screenshots of the Windows app. The accepted captures for this receipt will be genuine renderings of the assembled Pages site in installed Chrome on an off-screen Win32 desktop through the exact Lowlevel MCP HTTP service. They do not prove the Electron application or a provider transaction.

The comparison facts are dated July 28, 2026. Git LFS core facts come from its official specification and manuals. GitHub file limits, billing, forks, Releases, archives, and Pages behavior are separately labelled host policy. Cheap LFS facts come from the repository feature reference, implementation contracts, and named open evidence boundaries. The page does not claim:

pointer interoperability;
unlimited logical file size;
perpetual free Release or registry service;
universal performance or reliability;
Git LFS core payload encryption; or
completion of open issues #80, #85, #87, or #96.

Automated evidence

Gate	Required proof	Result
Route contract	72 rows, 12 categories, row-level sources, six tabs, six push stages, bounded regex, fit finder, languages, and local assets	Passed — 72 rows, 12 categories, 36 bibliography entries, six tabs, six stages
Existing guide regression	Original 30-row product guide and its six-stage push path remain intact	Passed — 30 criteria, six stages, 17 images
JavaScript and formatting	Syntax, Prettier, SVG, and diff checks	Passed
Documentation site	Catalog and docs-hub contracts include the new feature and receipt	Passed — catalog 18/18, hub 15/15, worker/controller 14/14, search/builder 12/12
Lowlevel preflight	Exact endpoint, scheduled-task action, service status, and MCP checkout SHA	Passed — ready service at `http://127.0.0.1:8765/mcp`, fixed checkout `f2edfe442555cfe35a519dd0b058986cb09d6ee3`
Application build boundary	Do not misreport the known pre-fix production multi-compiler path as a Pages acceptance success	Bounded non-success — the base predates renderer fix `6903c9ae1e`; only the owned ten-process build tree was stopped, with `returncode=4294967295`, empty stderr, and `timed_out=false`
Wide browser acceptance	1440×960, bilingual, 72-row model, filters/tabs/regex, local graphics, zero document overflow	Passed — 35-check run, light bilingual marketing overview
Narrow browser acceptance	390×844, dark Cantonese push tab, focusable commands, six stages, zero document overflow	Passed — exact push commands and all six stage nodes verified
Runtime hygiene	No console, page, request, or HTTP errors; owned browser and server close	Passed — 33/33 HTTP 200; zero recorded runtime errors
Remote publication	Pushed `origin/main` SHA, Pages run, live route, and remote asset/hash proof	Pending at capture time — recorded after push outside this historical local receipt

Accepted captures

File	Target state	SHA-256
`comparison-atlas-wide.png`	1440×960 bilingual marketing overview and product-orbit graphic	`3a21d531f0ab415fdbda6d6a7b8ab7c0282ce14aa334cb8c118061ec3d35f418`
`comparison-push-narrow.png`	390×844 dark Cantonese push handoff with the ordered stages in frame	`a65681aceb89a79974de63ce10b4d2b9789b7558e3b47fb1b80b7e5546555ab3`

Bilingual Cheap LFS versus Git LFS marketing overview with the product-orbit graphic

Narrow dark Cantonese Cheap LFS push handoff with the first ordered stages in frame

Run ownership

The exact task boundary and publication allowlist are in run-manifest.md. Owned process and cleanup names are in cleanup-ledger.md.

The work lives in a new isolated worktree based on remote 823f7fa0e5b4ebefd35ee8434c9c90ed420a6127. The active renderer checkout, renderer profiles, helper branch/worktree, .codex/runs, indexes, and the frozen close-out branch at f2629903525684ea4073557a186b0e58ce397c70 are explicitly outside this run.

The accepted browser pass ran from 2026-07-28T19:09:07Z through 2026-07-28T19:09:19Z using installed Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe. Its 35 checks covered the 72-row/12-category/36-source structure, category + outcome + text filter composition, valid and invalid regex, a catastrophically backtracking regex terminated at 750 ms, tab keyboard/pin/order persistence, language/theme/tone state, exact push commands, local images, both viewport overflow boundaries, and runtime error channels.