B8 - executable code blocks with a real kernel:
- worker/handler/kernel.cljs: one persistent SCI interpreter session per
page, reused across block evaluations so defs/state survive between runs.
Deliberately scoped to the same privileges the existing client-side
single-shot evaluator already had (no shell/fs access, no call-api).
- Run button + result display wired into block.cljs's code-block UI.
- New :logseq.property.code/result and /executed-at properties (65.38).
B9 - live notes: pages tagged #LiveNote that fetch external content on a
refresh schedule and render it via the render-resource pipeline:
- worker/handler/live_notes.cljs: per-block credential storage, scheduled
refresh (Node-only), thread-apis for manual refresh and auth.
- worker/handler/render_resource/live_note.cljs: reads back fetched content,
watching [:entity block-uuid] for reactive invalidation.
- New :logseq.class/LiveNote + :logseq.property.livenote/* properties (65.39).
Bugs found and fixed along the way while actually exercising page creation
through page-handler/create! for the first time in a test (previously only
pure-fn tests existed for CalDAV/Event/Contact):
- logseq-property-namespaces (property.cljs) was missing the citation/event/
contact/caldav/livenote namespaces, causing auto-create-ontology to treat
already-built-in properties as new user idents.
- outliner/page.cljs's build-page-tx always added the generic #Page tag even
when the caller tagged with a built-in class that extends #Page, which
malli-schema rejects as conflicting; it also lost the property type when
building ref-typed property values for new pages, breaking non-:default
types like :number.
- entity-util/page? never recognized Event/Contact/LiveNote as pages (only
Journal/Whiteboard/Tag/Property/Page had dedicated recognition), so pages
tagged with those classes alone weren't treated as pages anywhere in the
app; added built-in-page-child? alongside the existing per-class checks.
- caldav.cljs's upsert-page! passed a bare keyword as a tag where an entity
was required, and two error logs passed raw error objects to glogi that
triggered runaway recursion in this test environment; both fixed.
- New built-in classes Event and Contact (schema 65.37), plus a
Calendar View view type alongside table/list/gallery, backed by a new
fixed month-grid calendar-view component in components/views.cljs
reusing the existing scheduled/deadline properties.
- New worker/handler/caldav.cljs: a deliberately-scoped CalDAV
(VEVENT/VTODO) + CardDAV (VCARD) client against a single Nextcloud
calendar/addressbook collection, with its own minimal iCalendar/vCard
encoder-decoder and namespace-agnostic multistatus XML extraction
(no external ical/rrule/xml dependency exists in this project).
- RRULE <-> :logseq.property.repeat/* translation covers only the
`plus` (advance-from-scheduled) repeat mode with a bare FREQ(;INTERVAL)
rule -- dotted-plus/double-plus and anything with BYDAY/COUNT/UNTIL
are left untranslated on purpose rather than mistranslated.
- Credentials live in the platform keychain (save-secret-text!), never
in the graph. Sync runs Node-only, every 15 minutes per open repo,
started/stopped alongside the repo's lifecycle in db_core.cljs.
Conflicts are last-write-wins via ETag: a 412 on push is skipped and
retried after the next pull refreshes the stored ETag.
B3: registers :logseq.class/Project and :logseq.class/Area as
built-in page-like classes (the TODO in class.cljs already asked for
this), so users can tag pages/journals with them out of the box.
Fixed a markdown-mirror test whose "Custom Tag" fixture used to be
titled "Project" and collided with the new built-in class.
B4: adds :logseq.class/Citation plus /target and /context properties,
following the :logseq.class/Comments pattern. Since target is a
:node-typed ref, citation blocks automatically show up in the
existing block/citation reference graph without any changes there.
Adds a shared common-config/contents-page-name constant and
ldb/contents?/get-contents-page, mirroring the existing Library
helpers. Contents already qualifies as an internal page, so the
existing namespace-title split mechanism (e.g. "Contents/Proyectos")
already parents pages under it via :block/parent, coexisting with
Library rather than replacing it as the default root.
Adds :logseq.property.journal/previous and /next (built-in, hidden,
single-cardinality node refs) and maintains them in
logseq.outliner.page/create whenever a new journal page is created.
Filling a gap between two already-linked journals re-links both
neighbors around the new page instead of just appending. A migration
backfills the chain across all existing journal pages ordered by day.
Establishes version control for the personal Logseq DB fork before
starting the server-client architecture migration and domain features
described in docs/agent-guide and the approved implementation plan.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
