yamlover 0.3.25 → 0.3.49

package/dist/agent-docs/AGENTS.md

@@ -6,9 +6,10 @@ yamlover web UI (`npx yamlover .`) while you read and edit the files on disk. Th
 tells you how to manipulate these files **correctly** so you don't corrupt the data or break the
 human's live view.
 
-> This file is self-contained. You do **not** need any other spec to follow it. If the project
-> also contains files like `YAMLOVER.md`, `SEPARATOR.md`, `QUERY.md`, or `ANNOTATIONS.md`, those
-> are the authoritative, deeper specs — consult them for edge cases.
+> This file is self-contained. You do **not** need any other spec to follow it. The full,
+> authoritative spec is the yamlover documentation book (the `docs/` tree of the yamlover
+> project itself — the language under `docs/language/`, the document model under
+> `docs/documents/`); consult it for edge cases.
 
 ---
 
@@ -19,13 +20,13 @@ yamlover is a **distinct, YAML-like language** — close to YAML and mostly read
 document that uses aliases/anchors does **not** round-trip identically. On top of a YAML-style
 surface it adds a small **pointer layer** so that data forms a graph, not just a tree:
 
-- **`*` pointers** — a value that *refers to* another node (a shared edge, not a copy).
+- **`*` pointers** — a value that *refers to* another node (a ref edge, not a copy).
 - **`&` path anchors** — declare that "this node also lives over there" (the push side of `*`).
 - **`!!` tags** — type/schema markers, including inline schema references `!!<…>`.
 
 There is a sibling brace surface called **json5p** (`.json5p` files) — the same pointer layer
-expressed in JSON5 syntax. Most projects use `.yamlover`; treat `.json5p` as the JSON-flavored
-twin (pointers are written as quoted strings, e.g. `*": pets[1]"`).
+expressed in JSON5 syntax. Most projects use `.yo`; treat `.json5p` as the JSON-flavored
+twin (pointers are written as quoted strings, e.g. `*": pets: 1"`).
 
 **Important:** because `*` and `&` mean something different than in stock YAML (a `*` is a path
 pointer, **not** a YAML alias), these files require the yamlover parser. Do not "fix" them with
@@ -37,29 +38,30 @@ a generic YAML formatter — you will destroy the pointers and anchors.
 
 Plain YAML forces a node to be **either** a sequence (all `- item`) **or** a mapping (all
 `key: value`). yamlover unifies them: there is **one ordered container**. Every entry has an
-integer **position** (`[0]`, `[1]`, …) and **may also** carry a string key. Keyless (positional)
+integer **position** (0, 1, …) and **may also** carry a string key. Keyless (positional)
 and keyed entries coexist in one node — this is the default ("omni"):
 
 ```yamlover
 playlist:
-  - Intro                  # [0]            keyless / positional
-  - Verse                  # [1]            keyless
-  title: Greatest Hits     # [2], key=title keyed — AND still positioned
-  - Chorus                 # [3]            keyless
-  encore: *: pets[0]       # [4], key=encore a keyed pointer, still in order
+  - Intro                  # position 0            keyless / positional
+  - Verse                  # position 1            keyless
+  title: Greatest Hits     # position 2, key=title keyed — AND still positioned
+  - Chorus                 # position 3            keyless
+  encore: *: pets: 0       # position 4, key=encore a keyed pointer, still in order
 ```
 
 A node can even carry a **scalar value AND fields at once**:
 
 ```yamlover
 rating: 5                  # the node's own scalar value …
-  - solid                  # [0]  positional field
-  scale: 10                # [2]  keyed field
+  - solid                  # position 0  positional field
+  scale: 10                # position 2  keyed field
 ```
 
-(You may see optional `!!mix` / `!!var` tags marking these shapes. They are **no-op readability
-markers** — mixing and scalar-plus-fields are the default. Don't add or remove them to change
-meaning; they don't carry any.)
+(You may see an optional `!!mix` tag marking these shapes. It is a **no-op readability marker**
+— mixing and scalar-plus-fields are the default. Don't add or remove it to change meaning; it
+doesn't carry any. `!!yo` — whose deprecated aliases `!!var` / `!!omni` still parse — is a
+DIFFERENT thing and is **semantic**: see §6.)
 
 ---
 
@@ -70,8 +72,8 @@ key c". Canonical style writes `: ` (colon + space) after each step; a colon wit
 also parses.
 
 `/` is an **ordinary character** now — MIME-type keys (`text/html`), date keys (`01/02/2026`)
-and URL-ish keys ride bare in a path. (Legacy files may still use `/` as a separator during a
-migration window; **new content you author should use `:`**.)
+and URL-ish keys ride bare in a path. (The old `/`-separator form is DEAD — it no longer
+parses as a path: `*/pets` is a dangling reference to the literal key "/pets". Author `:` only.)
 
 ### The scope ladder — more colons, wider scope
 
@@ -82,26 +84,45 @@ current: object: path                         # bare       — current scope (si
 ::: yamlover.inthemoon.net: $defs: tag        # :::        — the world (an external project)
 ```
 
-- `*pets[1]` — bare: a **sibling** named `pets`, position 1.
-- `*: pets[0]` — `:` document root.
+- `*pets: 1` — bare: a **sibling** named `pets`, position 1.
+- `*: pets: 0` — `:` document root.
 - `*:: tags: genre` — `::` this project's root.
 - `*::: host.example: $defs: tag` — `:::` a world/external reference.
 
-`[n]` addresses by **position** (integer key); a bare word addresses by **string key**. They
-chain: `*: pets[1]: name` = root → position 1 → key `name`.
+### The bare-token rule — what a portion means
+
+Every portion is typed **by its own form**:
+
+- **pure digits** = the integer key, i.e. a **position**: `*: pets: 1: name` = root → position 1
+  → key `name`.
+- **a bare `~`** = the **null key** (`~: value`; `: v` is the same entry). The *string* key
+  `"null"` is written `null:`.
+- **anything else bare, and any quoted portion** = a **string key**: `: '1'` is the numeric
+  string key, `: '~'` the literal tilde.
+
+A key whose bare form would read as something else MUST be quoted: empty, pure digits, `~`,
+`-`+digits, or a key containing a space. In a document, a plain `1:` is a **parse error** —
+author `'1':` for the numeric string key.
+
+> **The retired bracket index.** The old `[n]` position form (`*pets[1]`) still *reads* — it is
+> a permanent alias — but it is **written never**. Author the bare-integer segment. The one
+> surviving bracket operator is `[.±k]` (a position relative to the pointer's own host). The
+> former `[]` (append) and `[?]` (any position) brackets were REMOVED — both are now the `-`
+> segment: a trailing `: -` on a bookmark appends (§5), and `-` in a query matches any
+> position. A literal `-` key must be quoted (`'-'`).
 
 ---
 
 ## 4. Pointers `*` (the pull side)
 
-A `*` value dereferences a path to another node and creates a **shared edge** (not a copy):
+A `*` value dereferences a path to another node and creates a **ref edge** (not a copy):
 
 ```yamlover
 humans:
   - name: Alice
-    manager: *: pets[1]      # Alice.manager IS the node at root → pets → position 1
-feline: *pets[1]             # bare → a sibling
-topDog: *: pets[0]           # : → document root
+    manager: *: pets: 1      # Alice.manager IS the node at root → pets → position 1
+feline: *pets: 1             # bare → a sibling
+topDog: *: pets: 0           # : → document root
 ```
 
 Pointers are **lazy** and **cycle-safe** — pointing two nodes at each other is fine. Editing the
@@ -118,7 +139,7 @@ target changes everything that points at it.
 boss: &: chief             # this node is ALSO reachable as the document-root key `chief`
   name: Rex
 team:
-  lead: *: chief           # same node as `boss` — a shared edge, not a copy
+  lead: *: chief           # same node as `boss` — a ref edge, not a copy
 ```
 
 Reverse relations are spelled as anchors. `&: parent: child` means "parent holds me as child":
@@ -129,17 +150,20 @@ adam:
     &: eve: cain           # "eve holds me as cain" — the reverse of eve's cain-edge
 ```
 
-`&: container[]` (trailing `[]`, no index) means **positional membership**: "that container also
+`&: container: -` (a trailing `-` segment) means **positional membership**: "that container also
 holds me", appended after the container's own entries:
 
 ```yamlover
 fan:
   name: Bob
-  &: favorites[]           # Bob appends himself to `favorites`
+  &: favorites: -          # Bob appends himself to `favorites`
 ```
 
-Anchor paths must be **unambiguous** (no wildcards, no trailing `[n]` position claim) — they
-create real keys, so they must resolve to exactly one place.
+Anchor paths must be **unambiguous** (no wildcards, no trailing position claim — neither a bare
+integer nor a relative `[.±k]`) — they create real keys, so they must resolve to exactly one
+place. The trailing `-` is an append, not a claim; a `-` anywhere else in an anchor path is
+reserved (a parse error today). The old `&: container[]` bracket spelling was removed and no
+longer parses.
 
 > You may encounter the older `~key: *path` back-edge syntax in legacy files. It still parses but
 > is deprecated; author new reverse edges as `&` anchors.
@@ -148,8 +172,13 @@ create real keys, so they must resolve to exactly one place.
 
 ## 6. Tags `!!` and `$defs` schemas
 
-- `!!type` — a YAML-style tag. Common no-op markers: `!!mix`, `!!var` (see §2). `!!set` marks a
-  container whose membership is by identity (duplicates collapse).
+- `!!type` — a YAML-style tag. `!!mix` is the one no-op marker (see §2). The rest are
+  **semantic** and must not be added or dropped casually:
+  - `!!set` marks a container whose membership is by identity (duplicates collapse);
+  - `!!yo` (deprecated aliases `!!var` / `!!omni`) marks a node as **plain yamlover, exempt
+    from the enclosing document's schema** — a *data island*. Inside a structured document (a
+    chapter, say) a `!!yo` node is never interpreted by that schema: it is data, drawn by the
+    generic renderer.
 - **Inline schema reference** `!!<…>` binds a node to a reusable schema definition:
   ```yamlover
   mychapter: !!<*:: yamlover: $defs: chapter>
@@ -165,17 +194,43 @@ create real keys, so they must resolve to exactly one place.
 
 A node can be materialized two ways:
 
-1. **Single-file concrete** — a whole document in one `.yamlover` (or `.json5p`) file.
+1. **Single-file concrete** — a whole document in one `.yo` (or `.json5p`) file.
 2. **Directory concrete** — a directory **is** the node; its files/subdirs are its entries, and
-   two optional overlay files inside a hidden `.yamlover/` subdir add data and schema:
-   - `.yamlover/body.yamlover` — **instance** overlay: scalar values, ordering, pointers,
+   two optional overlay files inside a hidden `.yo/` subdir add data and schema:
+   - `.yo/body.yo` — **instance** overlay: scalar values, ordering, pointers,
      extra keyed/keyless entries layered onto the directory's contents.
-   - `.yamlover/meta.yamlover` — **schema** overlay: typing, format, validation.
+   - `.yo/meta.yo` — **schema** overlay: typing, format, validation.
 
 So to add a pointer or a value "to a folder", you edit (or create) that folder's
-`.yamlover/body.yamlover`. Plain files inside the directory are its members; a `.yamlover/`
+`.yo/body.yo`. Plain files inside the directory are its members; a `.yo/`
 subdir does not appear as a member — it's the overlay.
 
+A pure pointer-array body (`- *file1` …) is the ORDER overlay: it grants positions to the
+members it names (the projection shows each consumed key as a dimmed derived `&` anchor,
+`- &file1 value`); a member the body never names stays keyed-only, after the ordered block.
+Editing derives storage for NEW children by the INHERITANCE RULES (`concrete-rules.ts` — one
+pure module, an explicit `concrete:` always wins): a directory-concrete parent keeps children
+directory-concrete; a keyed container child becomes a nested real directory; an untagged
+keyless (ordinal) container child becomes an order-numbered subdirectory (`item01`,
+`item02`, …) referenced by a `- *: itemNN` pointer-array element; scalars and tagged containers
+(tables, typographical lists) go inline into `body.yo`. Title-born subchapter members are
+numbered too (`01-Введение`). The numbers are COSMETIC listing order — the body pointer-array is
+the order's data, and an existing member is NEVER renamed: an insert between neighbors slots a
+sub-number (`item01-1`, `01-1-Новая`). Content inside a file document speaks that file's
+language (a `.json5p` interior never switches to yaml).
+
+**Collapse / expand / promotion — the same node, two shapes.** The two concretes are
+freely interconvertible without changing what the data means: a child stored as
+`child.yo` (collapsed) and the same child stored as `child/` with a
+`.yo/body.yo` (expanded) are equivalent. Converting a single-file node **into**
+a directory is called **directory promotion** (the UI's action; the engine keeps inbound
+pointers valid across it, like `mv`). If you do it by hand, it is a two-step move: create the
+`child/` directory, move the file's contents into `child/.yo/body.yo` (plus any
+members as files), and delete the old `child.yo` — then let the engine reindex. Because
+it is a move, treat it with the same care as any rename: pointers that addressed the old file
+path must still resolve (prefer the mediated `mv`/promotion in the UI, which rewrites them —
+see §10).
+
 ---
 
 ## 8. Annotations & fragments (tags applied to content)
@@ -190,9 +245,12 @@ The human marks up documents in the UI. These live **on the target node**, not i
   ```yamlover
   yamlover-annotations:
     - *:: tags: genre: brevity            # parameterless
-    - {description: A math block, tag: *:: tags: topic: math}   # parametrized
+    - {description: 'A math block', tag: *:: tags: topic: math}   # parametrized
   ```
 
+  (A flow scalar carrying a SPACE must be quoted — an unquoted `A math block` inside `{…}` is a
+  parse error.)
+
 Prefer letting the human create these through the UI. If you must touch them by hand, keep the
 exact key names (`yamlover-fragments`, `yamlover-annotations`) and the tag-pointer form, and do
 not renumber or reorder fragment slugs.
@@ -227,10 +285,10 @@ pushes the change to the human's browser over a live event stream — so your ed
 UI within a moment, and theirs appear to you on disk. Work with that, not against it:
 
 - **Make small, valid saves.** A half-written file will reindex as broken. Prefer complete edits.
-- **NEVER touch `.yamlover/index.db`** (nor its `-wal` / `-shm` companions). It is the server's
+- **NEVER touch `.yo/index.db`** (nor its `-wal` / `-shm` companions). It is the server's
   generated SQLite index — it regenerates itself from the source files. Editing or deleting it
-  does nothing useful and can confuse a running server. It is the *only* thing in `.yamlover/`
-  you must not edit; `body.yamlover` / `meta.yamlover` overlays (§7) are normal editable data.
+  does nothing useful and can confuse a running server. It is the *only* thing in `.yo/`
+  you must not edit; `body.yo` / `meta.yo` overlays (§7) are normal editable data.
 - **Renames and moves break inbound pointers.** Other files may point at a node by its path
   (`*: some: node`). If you move or rename it with a plain `mv`, those pointers dangle. The
   running server exposes a **mediated move** (`POST /api/mv`) that surgically rewrites inbound
@@ -238,10 +296,11 @@ UI within a moment, and theirs appear to you on disk. Work with that, not agains
   project for pointers to the old path (`*` followed by the path) and update them too.
 - **Don't reformat with a generic YAML/JSON tool.** It will mangle `*`, `&`, `!!<…>`, the
   colon paths, and the mixed keyed/keyless ordering. Edit the text directly and preserve style.
-- **Settings live in `.yamlover/settings.yamlover`** at the project root (e.g. where new tags and
+- **Settings live in `.yo/settings.yo`** at the project root (e.g. where new tags and
   annotations are written). Treat it as configuration; change it only when asked.
 - **When unsure of a path, query it.** The server answers `GET /api/query?...` using the path
-  grammar above, and serves the tree at `GET /api/tree` / a node at `GET /api/json?path=:a:b`.
+  grammar above, and serves the tree at `GET /api/tree` / a node's yamlover at
+  `GET /api/content/a/b` (slash-spelled path; digits are positions, `~` the null key).
   Use these to confirm a path resolves before you author a pointer to it.
 
 ---
@@ -250,15 +309,17 @@ UI within a moment, and theirs appear to you on disk. Work with that, not agains
 
 ```yamlover
 # pointers (pull) — colon paths, the scope ladder
-sibling:   *pets[1]                 # current scope, by position
-rooted:    *: humans[0]: name       # document root → position 0 → key name
+sibling:   *pets: 1                 # current scope, by position (bare digits = the position)
+rooted:    *: humans: 0: name       # document root → position 0 → key name
+strkey:    *: counts: '1'           # QUOTED digits = the numeric STRING key
+nullkey:   *: doc: ~                # the null key
 projscope: *:: tags: genre          # this project's root
 world:     *::: host.example: $defs: tag
 
 # anchors (push) — "I also live there"; real keys; unambiguous only
 here:  &: chief                     # also at document-root key `chief`
 rev:   &: parent: child             # parent holds me as `child`
-mem:   &: favorites[]               # appended member of `favorites`
+mem:   &: favorites: -             # appended member of `favorites`
 
 # tags / schema
 node:  !!<*:: $defs: chapter>       # bind a reusable schema

package/dist/agent-docs/CLAUDE.md

@@ -2,6 +2,6 @@
 
 This is a **yamlover** project. The authoring rules, the pointer/anchor syntax, and the rules for
 safely co-editing the tree while the yamlover web UI is running are in **`AGENTS.md`** — read it
-before editing any `.yamlover` / `.json5p` file.
+before editing any `.yo` / `.json5p` file.
 
 @AGENTS.md

package/dist/builtin-taxonomy/$defs/{.yamlover/meta.yamlover → .yo/meta.yo}

@@ -24,5 +24,11 @@ properties:
         type: string
         format: yamlover/meta
     table:
+        type: string
+        format: yamlover/meta
+    bullets:
+        type: string
+        format: yamlover/meta
+    numbered:
         type: string
         format: yamlover/meta

package/dist/builtin-taxonomy/$defs/board

@@ -1,5 +1,5 @@
 # $defs/board — marks a DIRECTORY of tasks as an agile/kanban board. Attach it to the directory's
-# `.yamlover/body.yamlover` overlay; the `workflow:` ref names which $defs/workflow supplies the
+# `.yo/body.yo` overlay; the `workflow:` ref names which $defs/workflow supplies the
 # lanes (its states, in order). The board renderer then groups the directory's task members into
 # those lanes by each task's current state annotation, and a drag between lanes rewrites that
 # annotation (re-tags the state). format `x-yamlover-board`. Attach with  !!<*yamlover:$defs:board>.

package/dist/builtin-taxonomy/$defs/bullets

@@ -0,0 +1,12 @@
+# $defs/bullets — a typographical UNORDERED (bullet) list: an ordinary yamlover list whose
+# keyless entries are the items. An item is marklower prose (a chunk) or — when it is an
+# UNTAGGED container — a nested bullets list: unlike table's two-level budget, the list
+# schema applies at ANY depth, until an explicit !!<…> tag switches to something else.
+# A titled list is a chapter holding a list — no keyed properties here on purpose.
+# Attach with !!<*yamlover: $defs: bullets>.
+# No explicit `format:` — `type: variant` derives x-yamlover-bullets. Spec: docs/documents/marklower.
+type: variant
+items:
+  anyOf:
+    - *:: yamlover: $defs: bullets   # an untagged container item = a nested sublist, SAME kind
+    - *:: yamlover: $defs: chunk     # a list item — marklower prose

package/dist/builtin-taxonomy/$defs/chapter

@@ -1,26 +1,31 @@
-# $defs/chapter — a document node: an OMNI node with optional title/description and a
-# positional body. The body is a plain sequence of unkeyed elements, read top to bottom;
-# each element is EITHER a nested chapter (the recursion) OR a chunk (a renderable block).
+# $defs/chapter — a document node: a FULLY OMNI node. The node's own scalar SELF-VALUE is the
+# TITLE — there is no `title:` key; `description` stays keyed; every keyless entry is a
+# positional body element, read top to bottom: EITHER a nested chapter (the recursion) OR a
+# chunk (a renderable block).
 #
 # There is no `chunks` array and no `children` array — prose, media, diagrams, and
 # subchapters are siblings in ONE ordered stream. Attach it to a yamlover node with the
-# tag  !!<*yamlover/$defs/chapter>.  Spec: ../CHAPTER.md, ../META.md.
+# tag  !!<*yamlover/$defs/chapter>.  Spec: docs/documents/chapter, docs/meta.
 #
-# `type: variant` is the omni node: keyed fields (title/description) AND positional
-# elements (the body) at once. The body element type is a union — a chapter OR a chunk;
-# the two are told apart structurally (a chapter is a container, a chunk is a leaf).
-# NOTE: `properties` (keyed) + `items` (ordinal) is the JSON-Schema encoding of an omni
-# node's two facets; META.md §Vocabulary proposes a native `elements`/`additionalElements`.
+# `type: variant` is the omni node: a scalar self-value (the title, given as `value:`) AND
+# keyed fields (description) AND positional elements (the body) at once. The body element type
+# is a union — a chapter OR a chunk; the two are told apart structurally (a chapter is a
+# container, a chunk is a leaf). A BARE SCALAR body element is therefore both "a chunk" and
+# "a title-only subchapter" — the same thing, by design (docs/documents/chapter).
+# NOTE: `value` (scalar) + `properties` (keyed) + `items` (ordinal) is the JSON-Schema encoding
+# of an omni node's facets; docs/meta proposes a native `elements`/`additionalElements`.
 type: variant
+value:                             # the self-value — the chapter's TITLE
+  type: string
+  format: text/marklower
 properties:
-  title:
-    type: string
-    format: text/marklower
-  description:                     # optional subtitle / heading annotation
+  description:                     # optional subtitle / heading annotation — stays keyed
     type: string
     format: text/marklower
 items:                             # the body — a positional sequence, read top to bottom
   anyOf:
-    - *:: yamlover: $defs: chapter   # a nested subchapter (the recursion) — a container
-    - *:: yamlover: $defs: table     # a table — enters only by its EXPLICIT tag (TABLE.md)
+    - *:: yamlover: $defs: chapter   # a nested subchapter (a container) — the recursion
+    - *:: yamlover: $defs: table     # a table — enters only by its EXPLICIT tag (docs/documents/marklower)
+    - *:: yamlover: $defs: bullets   # a bullet list — enters only by its explicit tag
+    - *:: yamlover: $defs: numbered  # a numbered list — enters only by its explicit tag
     - *:: yamlover: $defs: chunk     # a content block — a leaf

package/dist/builtin-taxonomy/$defs/chunk

@@ -3,6 +3,6 @@
 # A chunk is a typed value; its (type, format) selects the renderer. The default is
 # markdown prose; a chunk overrides type/format/concrete to be a diagram, image, LaTeX,
 # CSV, a file pointer, etc. `binary` covers image/pdf/… chunks (a `*` pointer to a file).
-# Spec: ../CHAPTER.md.
+# Spec: docs/documents/chapter.
 type: [string, binary]
 format: text/marklower

package/dist/builtin-taxonomy/$defs/config

@@ -1,4 +1,4 @@
-# $defs/config — the project configuration schema for `<root>/.yamlover/settings.yamlover`
+# $defs/config — the project configuration schema for `<root>/.yo/settings.yo`
 # (settings.ts, IMPORTS.md). Settings are DEFAULTS, never constraints; reading is location-
 # independent. The format `x-yamlover-config` lets the server render the (hidden but accessible)
 # config file with the SETTINGS EDITOR — opened by the gear button, in the main pane. Locations are

package/dist/builtin-taxonomy/$defs/numbered

@@ -0,0 +1,12 @@
+# $defs/numbered — a typographical ORDERED (numbered) list: an ordinary yamlover list whose
+# keyless entries are the items. An item is marklower prose (a chunk) or — when it is an
+# UNTAGGED container — a nested numbered list: unlike table's two-level budget, the list
+# schema applies at ANY depth, until an explicit !!<…> tag switches to something else.
+# A titled list is a chapter holding a list — no keyed properties here on purpose.
+# Attach with !!<*yamlover: $defs: numbered>.
+# No explicit `format:` — `type: variant` derives x-yamlover-numbered. Spec: docs/documents/marklower.
+type: variant
+items:
+  anyOf:
+    - *:: yamlover: $defs: numbered  # an untagged container item = a nested sublist, SAME kind
+    - *:: yamlover: $defs: chunk     # a list item — marklower prose

package/dist/builtin-taxonomy/$defs/table

@@ -1,12 +1,16 @@
 # $defs/table — a grid node: an OMNI node whose keyless entries are the ROWS (top to
 # bottom), each row an array of CELLS (left to right). A row keyed `header` is the header
 # row; optional keyed `title` is the caption. The column count is inferred from the first
-# row. A cell is marklower prose (a chunk), a nested table (the untagged container), or a
-# CHAPTER — entering only by its explicit tag, for a cell mixing prose and tables; a cell
-# that is a `*` pointer to its adjacent previous cell (`*[.-1]` left, `*..[.-1][.]` up —
-# relative indexes, URIs.md) declares a MERGED cell: colspan/rowspan. Attach with
+# row. The table schema consumes exactly TWO nesting levels — rows, then cells; a cell
+# that is an untagged container switches BACK to a CHAPTER (prose, subchapters, tables —
+# the same rules as a top chapter). A NESTED table — like a list — enters a cell only by
+# its explicit !!<…> tag. A header cell may be an omni scalar carrying a keyed `width`
+# sidecar — a proportional column weight (AsciiDoc `cols` style), rendered weight/sum %;
+# `width` is deliberately schema-untyped (an omni cell must stay a LEAF for shape routing).
+# A cell that is a `*` pointer to its adjacent previous cell (`*[.-1]` left, `*..[.-1][.]`
+# up — relative indexes, docs/language/pointers/relative-indexes) declares a MERGED cell: colspan/rowspan. Attach with
 # !!<*yamlover: $defs: table>.
-# No explicit `format:` — `type: variant` derives x-yamlover-table. Spec: ../TABLE.md.
+# No explicit `format:` — `type: variant` derives x-yamlover-table. Spec: docs/documents/marklower.
 type: variant
 properties:
   title:                           # optional caption
@@ -17,13 +21,16 @@ properties:
     items:                         #   schema is repeated literally rather than *: items)
       anyOf:
         - *:: yamlover: $defs: chunk
-        - *:: yamlover: $defs: table
         - *:: yamlover: $defs: chapter
+        - *:: yamlover: $defs: table
+        - *:: yamlover: $defs: bullets
+        - *:: yamlover: $defs: numbered
 items:                             # a row
   type: array
   items:                           # a cell
     anyOf:
-      - *:: yamlover: $defs: chunk    # marklower prose (the default)
-      - *:: yamlover: $defs: table    # a nested table — the UNTAGGED container (listed first,
-      - *:: yamlover: $defs: chapter  #   so shape routing keeps picking it); a chapter cell
-                                      #   enters only by its explicit !!<…chapter> tag
+      - *:: yamlover: $defs: chunk    # marklower prose (the default leaf)
+      - *:: yamlover: $defs: chapter  # an UNTAGGED container cell IS a chapter (the first
+      - *:: yamlover: $defs: table    #   container branch wins shape routing); a nested
+      - *:: yamlover: $defs: bullets  #   table — and a list — enters a cell only by its
+      - *:: yamlover: $defs: numbered #   explicit !!<…> tag

package/dist/builtin-taxonomy/$defs/task

@@ -1,7 +1,8 @@
 # $defs/task — a unit of work (a ticket), or a study card. A task IS-A chapter: it EXTENDS
-# the chapter schema (`allOf: [*chapter]`), inheriting the optional `title`/`description`
-# and the OMNI positional body — except its subchapter recursion means SUBTASKS (a task
-# tree). On top of that it adds a few OPTIONAL structured fields for planning and automation.
+# the chapter schema (`allOf: [*chapter]`), inheriting the FULLY-OMNI shape — the scalar
+# SELF-VALUE is the title (no `title:` key), `description` stays keyed — and the positional
+# body, except its subchapter recursion means SUBTASKS (a task tree). On top of that it adds
+# a few OPTIONAL structured fields for planning and automation.
 # It carries NO `state` field: a task's lifecycle position is a TAG APPLICATION
 # (`yamlover-annotations`) into a workflow taxonomy ($defs/workflow), so the whole tag / board
 # machinery is reused. Every planning field is optional — defaults-never-constraints: an

package/dist/builtin-taxonomy/tags/{.yamlover/body.yamlover → .yo/body.yo}

@@ -1,5 +1,5 @@
 # Tag taxonomy: the built-in PALETTE (colors — pure color tags, each with an explicit
-# color) plus named tags created from the annotation picker (settings.yamlover:
+# color) plus named tags created from the annotation picker (settings.yo:
 # tags.location). The palette ships with the yamlover project (::: yamlover.inthemoon.net);
 # the engine grafts {$defs, tags} as the `yamlover` self-import key into every served
 # root, so *//yamlover/tags/colors/<name> resolves from any project. Spec: ../$defs/tag.

package/dist/client/assets/decoded-D_YQdg1-.js

@@ -0,0 +1 @@
+import{r as f,b as d,j as o}from"./index-Bf2L7I9e.js";import{StaticImageChunk as h,PanZoomImage as x}from"./imagemap-B8RthxNE.js";function E({node:t,label:a,decode:s,chunk:e}){const[r,i]=f.useState([]),[g,u]=f.useState(null);return f.useEffect(()=>{let n=!1;const c=[];return i([]),u(null),(async()=>{const l=await fetch(d(t.path)).then(m=>m.arrayBuffer()),p=await s(l);if(!n){for(const m of p)c.push(URL.createObjectURL(m));n||i(c)}})().catch(l=>!n&&u(String(l.message||l))),()=>{n=!0,c.forEach(URL.revokeObjectURL)}},[t.path]),g?o.jsxs("div",{className:"error",children:[a,": ",g]}):r.length?o.jsx(o.Fragment,{children:r.map((n,c)=>e?o.jsx(h,{src:n,path:t.path,onNavigate:e.onNavigate},c):o.jsx(x,{src:n,className:"filemap fileimagemap",fill:r.length===1},c))}):o.jsxs("div",{className:"loading",children:["decoding ",a,"…"]})}async function w(t,a,s){const e=document.createElement("canvas");e.width=a,e.height=s;const r=e.getContext("2d");if(!r)throw new Error("no 2d context");const i=r.createImageData(a,s);return i.data.set(t),r.putImageData(i,0,0),b(e)}function b(t){return new Promise((a,s)=>t.toBlob(e=>e?a(e):s(new Error("canvas export failed")),"image/png"))}export{E as D,b as c,w as r};

package/dist/client/assets/djvu-Di4fPA-J.js

@@ -0,0 +1 @@
+import{r as u,u as te,a as ne,e as oe,c as re,D as W,b as se,j as d,f as ae}from"./index-Bf2L7I9e.js";import{u as ce,a as ie}from"./paged-bLurvatj.js";const le=""+new URL("djvu-Ci0lFKxE.js",import.meta.url).href;let X=null;function ue(){return window.DjVu?Promise.resolve(window.DjVu):(X??=new Promise((s,c)=>{const i=document.createElement("script");i.src=le,i.onload=()=>window.DjVu?s(window.DjVu):c(new Error("DjVu failed to load")),i.onerror=()=>c(new Error("could not load djvu.js")),document.head.appendChild(i)}),X)}let v=null,Y=null,_=null;const m=new Map,S=new Map,de=6,Q=1500;async function he(s,c){const i=await ue();return v??=new i.Worker,c!==Y&&(Y=c,m.clear(),S.clear(),_=(async()=>(await v.createDocument(s),Number(await v.doc.getPagesQuantity().run())||0))()),_}async function ge(s,c){const i=Math.max(1,Math.round(s.height*c/s.width)),w=await createImageBitmap(s,{resizeWidth:c,resizeHeight:i,resizeQuality:"medium"}),g=document.createElement("canvas");g.width=c,g.height=i;const x=g.getContext("2d");return x.drawImage(w,0,0),w.close(),x.getImageData(0,0,c,i)}function fe(s){const c=m.get(s);if(c)return m.delete(s),m.set(s,c),Promise.resolve(c);const i=S.get(s);if(i)return i;const w=(async()=>{const[g,x,y,A]=await v.run(v.doc.getPage(s).getImageData(),v.doc.getPage(s).getNormalizedTextZones(),v.doc.getPage(s).getWidth(),v.doc.getPage(s).getHeight()),b=Number(y)||g.width,N=Number(A)||g.height,j={image:b>Q?await ge(g,Q):g,zones:Array.isArray(x)?x:[],w:b,h:N};for(S.delete(s),m.set(s,j);m.size>de;)m.delete(m.keys().next().value);return j})();return S.set(s,w),w}const p=s=>Number(s)||0;function pe({image:s}){const c=u.useRef(null);return u.useLayoutEffect(()=>{const i=c.current;i&&(i.width=s.width,i.height=s.height,i.getContext("2d")?.putImageData(s,0,0))},[s]),d.jsx("canvas",{className:"djvu-page",ref:c})}function xe({node:s}){const c=u.useRef(null),[i,w]=u.useState(0),[g,x]=u.useState(1),[y,A]=u.useState(0),[b,N]=u.useState(null),[f,j]=u.useState(null),[E,B]=u.useState(()=>new Set),[D,P]=u.useState(()=>new Map),T=u.useRef(new Map),V=te(s.path),{openCreate:H,openEdit:Z,palette:q,preview:R}=ne(V,s.path),O=V.annotations.filter(e=>e.selector?.type==="djvu").map(e=>({page:p(e.selector.page)||1,x:p(e.selector.x),y:p(e.selector.y),w:p(e.selector.w),h:p(e.selector.h),title:e.description,color:re(e),ann:oe(e)?e:void 0})),U=R?.color??W;if(R?.selector.type==="djvu"){const e=R.selector;O.push({page:p(e.page)||1,x:p(e.x),y:p(e.y),w:p(e.w),h:p(e.h),color:R.color})}const C=u.useRef(new Map),z=ce(c,()=>{const e=[];for(let n=1;n<=i;n++){const t=C.current.get(n);t&&e.push(t)}return e},i>0&&y>0);ie(c);const F=u.useRef(z);F.current=z,u.useLayoutEffect(()=>{z.restoreAnchor()},[g]),u.useEffect(()=>{const e=c.current;e&&!e.closest(".chunk-body")&&e.focus({preventScroll:!0})},[]),u.useLayoutEffect(()=>{const e=c.current;if(!e)return;const n=new ResizeObserver(([t])=>A(t.contentRect.width));return n.observe(e),()=>n.disconnect()},[]);const k=Math.min(y,1e3)*g;u.useEffect(()=>{const e=c.current;if(!e)return;let n=!1,t=0;const o=a=>{(a.ctrlKey||a.altKey||a.metaKey)&&(a.preventDefault(),n||(F.current.captureAnchor(),n=!0),clearTimeout(t),t=window.setTimeout(()=>n=!1,250),x(h=>Math.min(5,Math.max(.4,h*(a.deltaY<0?1.1:1/1.1)))))};return e.addEventListener("wheel",o,{passive:!1}),()=>{e.removeEventListener("wheel",o),clearTimeout(t)}},[]),u.useEffect(()=>{let e=!1;return w(0),N(null),B(new Set),P(new Map),C.current.clear(),T.current.clear(),(async()=>{const n=await fetch(se(s.path)).then(o=>o.arrayBuffer()),t=await he(n,s.path);e||w(t)})().catch(n=>!e&&N(String(n.message||n))),()=>{e=!0}},[s.path]),u.useEffect(()=>{if(!i)return;const e=new IntersectionObserver(n=>{B(t=>{const o=new Set(t);for(const a of n){const h=Number(a.target.dataset.page);a.isIntersecting?o.add(h):o.delete(h)}return o.size===t.size&&[...o].every(a=>t.has(a))?t:o})},{root:c.current,rootMargin:"2000px 0px"});for(const n of C.current.values())e.observe(n);return()=>e.disconnect()},[i,y>0]),u.useEffect(()=>{let e=!0;return E.forEach(n=>{D.has(n)||fe(n).then(t=>{T.current.set(n,{w:t.w,h:t.h}),e&&P(o=>new Map(o).set(n,t))}).catch(()=>{})}),P(n=>{let t=!1;const o=new Map(n);for(const a of o.keys())E.has(a)||(o.delete(a),t=!0);return t?o:n}),()=>{e=!1}},[E]);const G=()=>{const e=window.getSelection();if(!e||e.isCollapsed||!e.anchorNode)return;const t=(e.anchorNode.nodeType===1?e.anchorNode:e.anchorNode.parentElement)?.closest(".djvu-page-wrap");if(!t||!c.current?.contains(t))return;const o=Number(t.dataset.page),a=t.getBoundingClientRect(),h=a.width/(D.get(o)?.w||1);if(!h)return;const l=e.getRangeAt(0).getBoundingClientRect();l.width<2||l.height<2||H({type:"djvu",page:o,x:Math.round((l.left-a.left)/h),y:Math.round((l.top-a.top)/h),w:Math.round(l.width/h),h:Math.round(l.height/h)},{x:l.left,y:l.bottom+6})},I=(e,n)=>n.getBoundingClientRect().width/(D.get(e)?.w||1),J=(e,n)=>{const t=n.currentTarget.getBoundingClientRect(),o=I(e,n.currentTarget);j({page:e,x0:(n.clientX-t.left)/o,y0:(n.clientY-t.top)/o,x1:(n.clientX-t.left)/o,y1:(n.clientY-t.top)/o})},$=(e,n)=>{const t=n.currentTarget.getBoundingClientRect(),o=I(e,n.currentTarget);j(a=>a&&{...a,x1:(n.clientX-t.left)/o,y1:(n.clientY-t.top)/o})},ee=(e,n)=>{const t=f;if(j(null),!t||t.page!==e)return;const o=I(e,n.currentTarget),a=Math.min(t.x0,t.x1),h=Math.min(t.y0,t.y1),l=Math.abs(t.x1-t.x0),r=Math.abs(t.y1-t.y0);if(l*o<3||r*o<3)return;const M=n.currentTarget.getBoundingClientRect();H({type:"djvu",page:e,x:Math.round(a),y:Math.round(h),w:Math.round(l),h:Math.round(r)},{x:M.left+a*o,y:M.top+(h+r)*o+6})};return b?d.jsxs("div",{className:"error",children:["djvu: ",b]}):d.jsxs(d.Fragment,{children:[d.jsxs("div",{className:"filedjvu yo-zoomable",ref:c,tabIndex:0,onMouseUp:G,children:[i===0&&d.jsx("div",{className:"loading",children:"opening djvu…"}),y>0&&Array.from({length:i},(e,n)=>{const t=n+1,o=E.has(t)?D.get(t):void 0,a=T.current.get(t),h=k*(a?a.h/a.w:Math.SQRT2),l=o?k/o.w:0;return d.jsx("div",{className:"djvu-page-wrap","data-page":t,ref:r=>{r?C.current.set(t,r):C.current.delete(t)},style:{width:k,height:o?void 0:h},children:o?d.jsxs(d.Fragment,{children:[d.jsx(pe,{image:o.image}),o.zones.length>0?d.jsx("div",{className:"djvu-textlayer",children:o.zones.map((r,M)=>d.jsx("span",{style:{left:r.x*l,top:r.y*l,width:r.width*l,height:r.height*l,fontSize:r.height*l},children:r.text},M))}):d.jsx("div",{className:"djvu-marquee",onMouseDown:r=>J(t,r),onMouseMove:r=>$(t,r),onMouseUp:r=>ee(t,r),children:f?.page===t&&d.jsx("div",{className:"djvu-region",style:{left:Math.min(f.x0,f.x1)*l,top:Math.min(f.y0,f.y1)*l,width:Math.abs(f.x1-f.x0)*l,height:Math.abs(f.y1-f.y0)*l,borderColor:U,background:U+"2e"}})}),O.filter(r=>r.page===t).map((r,M)=>{const K=r.color||W;return d.jsx("div",{id:r.ann?.fragmentSlug?ae(s.path,r.ann.fragmentSlug):void 0,className:"djvu-region"+(r.ann?" editable":""),title:r.ann?r.title||"click to recolor or delete":r.title,onClick:r.ann?L=>{L.stopPropagation(),Z(r.ann,{x:L.clientX,y:L.clientY})}:void 0,style:{left:r.x*l,top:r.y*l,width:r.w*l,height:r.h*l,borderColor:K,background:K+"2e"}},M)})]}):d.jsx("div",{className:"djvu-placeholder",children:E.has(t)?"decoding…":""})},n)})]}),q]})}export{xe as DjvuView};