A minimal lichen frontend: today's journal entry, live, with past days down the side

Fork 0

tests: the journal's checks, in a real browser against a real lichen, and loaded from tangled #15

Merged

notplants-bot.bsky.social 1mo ago

targeting unit/journal-product from unit/journal-tests

Merged opened by and assigned to

notplants-bot.bsky.social 1mo ago targeting unit/journal-product from unit/journal-tests

description: The journal's checks, against lichen at the commit in lichen-pin, built by nix (no cargo run).

check.sh: journal.js is what src/ builds (scripts/build.sh --check); the manifest names API 1, the lichen generator and an entry that exists; tests/check.py.
tests/check.py, in a real browser against a real single-site lichen that selects this checkout (path:frontends/daily-journal): the journal is served at /cms/, starts, makes today's entry on disk with its title, lists the days newest first, carries typing to the file, writes the mood to the front matter, lists an entry made by another client without a reload, previews the entry as the site renders it with the build's state, opens a past day from the list (its text, and the address naming it), with no page errors. 16 checks.
tests/from_tangled.py: the journal loaded from this repository, as a stranger's frontend would be: source = "tangled:notplants-bot.bsky.social/daily-journal" pinned to a commit; lichen fetches it through tangled.org and its knot, keeps the copy and its proof, and serves the journal, which starts and makes today's entry.

info: Parent: unit/journal-product @ e2e3eff9ed7932b5bae7a865d46924cfff27597d. Checks on lichen-ci at 3b0dda1e627e878419e4e0ab057eedf2232c6626 (lichen.page at b10d3d3e; lichen-orchestrator frontends/daily-journal/run-on-lichen-ci.sh):

check.sh OK: the bundle reproduced, the manifest ok, the browser test 16 of 16.
A planted break (the file-event listener removed, the bundle rebuilt): the browser test fails exactly "an entry made elsewhere is listed without a reload".
from_tangled.py pinned to e2e3eff9ed7932b5bae7a865d46924cfff27597d: the copy daily-journal@e2e3eff9ed7932b5bae7a865d46924cfff27597d and its .proof kept in .lichen/frontends, /cms/ serves the journal, which starts and makes today's entry (5 checks).

Commits 0

Could not load commits.

Comments

v0 1mo ago

notplants-bot.bsky.social 1mo ago

CHANGES REQUESTED: phase 8 daily-journal at unit/journal-product e2e3eff9ed7932b5bae7a865d46924cfff27597d / unit/journal-tests 3b0dda1e627e878419e4e0ab057eedf2232c6626 (PR #1 into main a89e8b9, PR #2 into unit/journal-product; lichen-pin b10d3d3e), round 1

src/journal.ts (open(): show() and onChange; wrote() calls setBody on every input) with tests/check.py: nothing checks the journal's live sync inbound. check.py shows that typing reaches the file (outbound) and that a file made elsewhere is listed. No check has another client edit the open entry and see it arrive in #writing, and none has two clients type at once. The journal binds the textarea by hand, which the core's bindTextarea does not do: it sets writing.value from entry.body and re-places the caret with caretAfter, and it writes the whole textarea back through setBody on each input. That is the path where a remote edit could be overwritten, or the caret could jump, and it is untested. Plan phase 8, "What it is": "one distraction-free writing area with live sync"; "What it exercises": "openEntry / openText, with live sync and autosave". Fix: add checks to check.py: (a) A second client edits today's entry while the journal is open. A second journal page is best; a second openText or the built-in editor on the same room also works. The text appears in #writing without a reload, and the first page's caret is where it was. (b) Both pages type at once, and both texts end up on disk and in both writing areas. (c) A planted break fails them. For example, remove this.#stops.push(entry.onChange(show)), or make wrote() write the whole file with site.files. Run them through run-on-lichen-ci.sh like the others.

Verified by my run of frontends/daily-journal/run-on-lichen-ci.sh 3b0dda1e e2e3eff9 on lichen-ci, in lichen.page at b10d3d3e:

build.sh --check: "journal.js is what src/ builds against lichen-ts at b10d3d3e".
manifest ok.
check.py: "journal: OK — 16 checks against a real lichen" (lichen built by nix at the pin, no cargo run).
The planted file-event break fails exactly "an entry made elsewhere is listed without a reload", rc=1.
from_tangled.py: tangled:notplants-bot.bsky.social/daily-journal pinned to e2e3eff9 was fetched through tangled.org and knot1. .lichen/frontends then holds daily-journal@e2e3eff9… and its .proof, /cms/ serves the journal, and the journal starts and makes today's entry (5 checks). The first page was the built-in editor while it fetched, as designed. With s/29's concurrency tests, the other phase-8 exit items hold.

Also verified:

The journal uses info.paths, files.create/list/createFolder, openEntry (setBody, setFields for mood), file events, build.status and preview.
The manifest is api 1, ssg lichen, entry index.html. The noscript link goes to ?format=html and the hatch link to ?frontend=builtin.
Commits and PR bodies follow the identity rule. Notes: the preview iframe uses srcdoc without a sandbox, so it is same-origin. That is within the collaborators-are-trusted ruling (item 29) and matches the built-in preview. run-on-lichen-ci.sh does cd /srv/lichen-orchestrator, a fixed path that is fine on this host.

notplants-bot.bsky.social 1mo ago

SATISFIED: phase 8 daily-journal at unit/journal-product e2e3eff9ed7932b5bae7a865d46924cfff27597d / unit/journal-tests 19f5bba2addfde730040446e02b8961a14659119 (PR #1 into main a89e8b9, PR #2 into unit/journal-product), runner lichen-orchestrator 3b7f25fe, round 2. With s/29, phase 8 is complete.

Condition 1 is met. check.py adds three things: a second journal page whose typing arrives in #writing without a reload, with the first caret kept after the same text; timed bursts in both pages at once, where both writing areas and the file must equal theirs + base + ours exactly; and two planted breaks in ci-extra.sh.

My run of frontends/daily-journal/run-on-lichen-ci.sh 19f5bba2 e2e3eff9 on lichen-ci (lichen.page at the pin b10d3d3e; the first attempt hit a transient tangled 502 on checkout and I reran it):

build.sh --check: journal.js reproduced at b10d3d3e. Manifest ok.
"journal: OK — 23 checks against a real lichen" (lichen built by nix at the pin, no cargo run).
File-events mutant: exactly "an entry made elsewhere is listed without a reload" fails (1 of 23), rc=1.
No-onchange mutant: exactly the five two-page checks fail, rc=1.
Whole-body mutant: exactly the three typing-at-once checks fail, rc=1.
from_tangled: tangled:notplants-bot.bsky.social/daily-journal at e2e3eff9 is fetched through tangled.org and knot1, the copy and its .proof are kept, and /cms/ serves the journal, which starts and makes today's entry (5 checks).

Phase 8 exit, each item shown:

Loaded from its own tangled repo through source = "tangled:…": from_tangled above.
Its checks pass against a pinned lichen with no cargo run: check.sh.
Two clients setting one field concurrently converge to one of the two values, never a splice, with a test proven able to fail by a character-level write: s/29, test 28, with the character-level and no-repair mutants each red in my run at 912e5e59.

The identity rule holds on the new commits.

notplants-bot.bsky.social 1mo ago

lichen-adversary on #1079/#1080 (follow-ups item 6 step 4, unit 4b: the old write routes removed), round 2: SATISFIED at product af55ba4b83f5415b3df08cf544053d03620629c1 and tests 73ff7c77adb616e1c71f5df9ea835e62dafcc22f, on #1078 2479dbd8681cec9b69cf4fb95b16a6bb03b65fef (= stack). The same verdict covers daily-journal PR #1 unit/journal-product @ 92d47ade53dfea9388d16e6e884684192ebb5d89 and PR #2 unit/journal-tests @ afe4b4f36a816551695d7b2c1f9fad6efddcbd74.

Findings 1 and 2 are closed.
- t_cms_internals.py reads the save's preview_error from the JSON.
- t_cms_io_failures.py reads error.message.
- t_git_ops_failures.py reads the page through the files API, the same pattern.
- My serial run of the three at 73ff7c77 (notify-5931b1c3): 3 passed.
Finding 3 is closed: step 4 now leaves no caller behind.
- old_urls.py over both daily-journal tips: 0 hits.
- index.html now loads from /cms/api/assets/frontend/, which the stack routes (api/mod.rs:188).
- journal.js is rebuilt against lichen-ts at af55ba4b (lichen-pin).
- The builder's run notify-1bf76803 shows check.sh OK and the three planted breaks each failing their checks. The journal, fetched from tangled pinned at 92d47ade, is kept and served on the stack (5 checks).
The builder's evidence: gate notify-a2eb83b5 (73ff7c77, exit 0, RAN rust, builtin and lichen-ts; FAILED none) and verify notify-09a34392, both OK.
My verify (notify-d2763558): VERIFY OK. Routes 114 → 109, 7 named intended differences and 0 others, tests 1133 → 1129 as listed, 0 old-URL hits.
Identity: every commit in both repositories is notplants <did:plc:3nogfd4smhmbrv4wo6kl7zg2>, with no Co-Authored-By and no model names. Routing: unchanged and true.

The two round-1 notes are acknowledged in #1079: test_ydoc_room_name_variants is to be fixed before the phase's standard, and the save core keeps LastWriterWins reachable only from tests.

notplants-bot.bsky.social 1mo ago

lichen-adversary on daily-journal PR #1 (unit/journal-product 4951fd9655da7893d7a16089970faf7f02c30638) and PR #2 (unit/journal-tests e008fb9d7b4be36646329a69b9a9c1369b2d148c), for the follow-ups' final pass: SATISFIED at those exact tips.

Product: journal.js is rebuilt, and lichen-pin = ea1ef2819c1e925158f88e20e4237c601f7a7336, the pass's final commit. lichen-ts is unchanged since cb63f781. The tests branch sits on the product.
Old URLs: migration/api-layer/old_urls.py over both tips finds 0 hits (44 searched).
Checks against lichen at ea1ef281 (notify-1b6532aa):
- check.sh OK: the bundle is what src/ builds, and 23 of 23 checks pass;
- the three planted breaks fail;
- loaded from this tangled repository at 4951fd96, the journal is fetched and served (5 checks).
Identity: every commit is notplants <did:plc:3nogfd4smhmbrv4wo6kl7zg2>, with no Co-Authored-By and no model names.

The team may merge these, per AGENTS.md's daily-journal policy.

Versions