canon 0.3.118 → 0.3.119

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 775ec23689366d5e58c5442ad78706027ba7f8e8efba6c06aede93907160f607
-  data.tar.gz: 3f73899302308caf78050f7a692a159cb5e2cc53cbf822e0773c9632bd8beeef
+  metadata.gz: 21b508095633774da379c4f7c13cfaeabce997fbdb400139e7ecf7aedbf3df95
+  data.tar.gz: 9528d6c70d4b84f43bf77e5ca7b30a4bbf2ee8f3a172a010d0c6ea90228a9c75
 SHA512:
-  metadata.gz: fb497832a82755ec47f0314429f58646c7a93be3e6597c226dc605788492db26b985f98923fd87bdac7b9d365724bb5a4907a73ca10255d99edd13621ce2e6da
-  data.tar.gz: 972cf0c38d77cea7dea322430ba681456718c0aed4d153eef40116a438a855c70371289d0d6a74c00a5a3e51e12982d069ede9650e2bc710fd0448e89b8c5f8e
+  metadata.gz: 2de6ab858f2c4ca1ba6b83cad30058af17c2427e9688b13babde2bc249fdf5234d453575c36956b5edc2b343c4876647439b8d604bc5a3bcb96c746759c31a86
+  data.tar.gz: 51ac169753e93464ff16be5e869f0d157c1dcc0446311551322fcd19ee120a38a94d5581db9f167436f1d6ed8461b4fedff2899dd1d3fd12b32ac68957521b23

data/docs/HANDOFF.adoc

@@ -5,43 +5,55 @@ published: false
 
 A snapshot of the open arcs across the org repos — what is known, where
 to dig, and what has already been proven — so any team can pick an issue
-up cold. Statuses as of 2026-10-28.
+up cold. Statuses as of 2026-11-01.
 
-== lutaml/moxml
+== State of the world
+
+Shipped since the last board (2026-10-28): leptris 1.9.398.0 (the
+#1866 adopt + parent-of-attribute fixes and the #1846/#1854/#1855 perf
+slices), yeptris 0.6.52.0/0.6.53.0 (marshal reader #322, multibyte
+breaks #782), moxml **0.6.0** (the Opal surface deleted by the owner's
+phase-4 call, lutaml/moxml#516 — the forward Opal path is the moxml-ts
+wasm binding, lutaml/moxml#489), lutaml-model 0.8.155 (admits both
+moxml lines: `>= 0.5.139, < 0.7`), canon 0.3.118 (floors `leptris ~>
+1.9.398`, `yeptris ~> 0.6.52`, `moxml ~> 0.6.0`; Opal lane retired).
+
+== lutaml/canon
 
 [cols="1,1,2"]
 |===
-|Issue |Status |Known + first moves
-
-|moxml#474 — parent-of-attribute (`./@id/..`) returns empty through the
-Ruby engine on the leptris adapter
-|Open (filed 2026-10-27 with probes)
-|The adapter routes parent-axis expressions to the Ruby engine
-(`REVERSE_AXES` in `adapter/leptris.rb`); that lane loses attribute
-inputs. The ENGINE answers correctly since leptris v1.9.385 (both eval
-paths). Easiest: widen the native gate for parent/ancestor-after-
-attribute paths; or fix `on_axis_parent` in `xpath/compiler.rb` for
-`Wrappers::Attribute` inputs (the wrappers carry `@parent_node`).
-Unblocks metanorma-standoc's `svg_uniqueids1`.
-
-|moxml#472 — `.//*[@class]` predicate segfaults the compiled evaluator
-|Open
-|Crash in `leptris_xpath_compiled_eval` (.ips on file); the
-`attribute::class` spelling does not crash. FIRST retest against
-leptris v1.9.385 — a corrupt-attribute-table class (the cross-doc
-adopt, leptris#1869) shipped fixed there and could be the fuel. If it
-still crashes: the VM's predicate lane (`src/leptris/xpath/vm.c`,
-attribute existence inside `[...]`). Production hit: standoc's
-`svg_classupdate1`.
-
-|moxml#473 — XSD compile of large occurrence products grows unbounded
-(jetsam SIGKILL, low RSS)
-|Open
-|W3C `particlesZ034_b.xsd` repro in the issue. The compiled automaton's
-product construction needs cardinality folding (`unbounded` inner terms
-to epsilon-loops) instead of enumeration.
+|Item |Status |Known + first moves
+
+|Floors raised (0.3.118)
+|Shipped
+|`leptris ~> 1.9.398`, `yeptris ~> 0.6.52`, `moxml ~> 0.6.0` — all
+verified against exactly those engines (2744 examples, 0 failures, 25
+pending). Constraints live in the gemspec only; Gemfile/Gemfile.local
+are untracked verification lanes.
+
+|Opal lane
+|Retired
+|moxml 0.6 deleted the Opal surface (moxml#516), so canon's opal
+workflow, `spec:opal` task, `:opal` group, and smoke spec are gone.
+The `RUBY_ENGINE == "opal"` branches in lib stay for the moxml-ts wasm
+migration (moxml#489).
+
+|Subset-xpath mini engine (`lib/canon/xml/xpath_engine.rb`)
+|Reported, owner decision pending
+|It silently returns `[]` for `..` and `@attr` step forms (XPath 1.0
+§2.2 names the owner element). No `lib/` caller uses those forms today
+(swept 2026-10-28); decide between implementing the steps and
+documenting/raising on unsupported forms.
 |===
 
+== lutaml/moxml
+
+All three canon-filed engine issues are CLOSED by the moxml team —
+#474 (parent-of-attribute through the Ruby engine), #472
+(attribute-existence predicate segfault), #473 (unbounded occurrence
+products at XSD compile). Nothing to pick up here; re-file against
+moxml 0.6.x if the metanorma-standoc svg lanes regress.
+
 == leptris/leptris
 
 [cols="1,1,2"]
@@ -53,34 +65,17 @@ to epsilon-loops) instead of enumeration.
 |Shipped: the adopt copy's attribute-tail resync
 (`copy_subtree_detached`, `src/leptris/dom/element_modify.c`) and the
 evaluator-path parent-of-attribute (`apply_axis`,
-`src/leptris/xpath/evaluator_axes.c`). Pin:
-`AdoptKeepsMixedPlainAndNamespacedAttrs`. Re-verify downstream crash
-reports (moxml#472) against 1.9.385.
+`src/leptris/xpath/evaluator_axes.c`).
 
-|leptris#1842 — C-face XML parse/gen/xpath ~3-4x behind pugixml
-|Open
-|Decomposed into #1846/#1854/#1855. Use the interleaved A/B harness.
-
-|leptris#1846 — parse gap is allocator-shaped (1.0x mingw -> 4.3x old
-Intel mac, same code)
-|Open, slice 3 pending
-|Allocation profile done (the issue's wave comment). ARENA
-RIGHT-SIZING with the interleaved harness — cross-wave comparison is
-INVALID (pugixml swung 1.7x between waves; only within-run interleaved
-A/B counts). A counting-malloc interposer via `DYLD_INTERPOSE` beats
-xctrace for parse loops. Prior art: `leptris-xsitype` worktree,
-branch `perf/1846-adopt-conversion-buffer`.
-
-|leptris#1854 — `to_xml` native emission: `FFI::Pointer#+` is 37% of
-the loop
-|Open
-|An address-Integer emission API (`uintptr_t` in/out, the #408 law);
-batch per subtree, not per node.
+|leptris#1846/#1854/#1855 — the parse-allocator, pointer-emission, and
+plan-path-FFI perf slices
+|CLOSED (through v1.9.398)
+|All three slices landed; the umbrella gap moved accordingly.
 
-|leptris#1855 — plan-path parse ~35% FFI materialization
-|Open
-|Batched child/string asks; mirror the `children_read` bulk face
-(leptris-ruby#530).
+|leptris#1842 — C-face XML parse/gen/xpath vs pugixml
+|Open (umbrella)
+|Re-baseline against 1.9.398 with the interleaved A/B harness before
+opening new slices — the old ~3-4x numbers predate the closed slices.
 |===
 
 == leptris/yeptris
@@ -121,12 +116,82 @@ has the trusted-into entries.
 |===
 |Issue |Status |Known + first moves
 
-|yeptris-ruby#322 — CBOR dump is marshaling-bound
-|Open
-|The JSON half shipped (the marshal face: 4.4x end-to-end). CBOR: a
-`yeptris_cbor_from_marshal`-style face, reusing the marshal reader's
-REGISTRY LAW and its pin (`test/unit/test_marshal_json.cpp`) — the
-registry law (who occupies an `@` slot) is the hard-won part; copy both.
+|yeptris-ruby#322 — dump face is marshaling-bound
+|CLOSED
+|The marshal face shipped (4.4x end-to-end, yeptris 0.6.47/0.6.48; the
+reader's REGISTRY LAW pinned in `test/unit/test_marshal_json.cpp`).
+If the CBOR face reopens, copy the registry law and its pin wholesale.
+|===
+
+== lutaml/lutaml-model and the dependent legs
+
+[cols="1,1,2"]
+|===
+|Item |Status |Known + first moves
+
+|moxml 0.6 admission
+|Shipped (0.8.155)
+|`>= 0.5.139, < 0.7`; the Opal boot lane pins moxml 0.5.x locally in
+`opal.yml` (Gemfile-append + plain `bundle update moxml` — bundler 4
+removed `update --version`) until the moxml-ts wasm migration.
+
+|update-baselines red on every main push
+|PR lutaml-model#1076
+|checkout's persisted Authorization extraheader collides with
+create-pull-request's token ("Duplicate header: Authorization", HTTP
+400) on the action's `git remote prune`. Fix: `persist-credentials:
+false` on that job's checkout (the documented pairing).
+
+|metanorma/docbook dependent leg (ubuntu/macos)
+|PR metanorma/docbook#15
+|ferrum 0.20 rejects `file://` at boot (`parse_base_url` is
+http/https-only); docbook's `Capybara.app_host = "file://"` died in a
+`before(:suite)` hook with zero examples run (windows skips the boot).
+Fix: loopback http app_host placeholder; the specs visit absolute
+file:// URLs directly. Same PR carries the pre-existing rubocop debt
+that failed docbook's own rake lane (dead `custom_data` captures).
+
+|ukiryu dependent leg (macos)
+|Transient — resolved
+|`bundle add lutaml-model` exit 7: the runner's rubygems compact index
+had not propagated yeptris 0.6.53.0 (released hours earlier; the
+version EXISTS with full platform coverage). Passed on the next
+dependent run.
+
+|glossarist/iev dependent legs (all OSes) + iev's own rake lane
+|RESOLVED (2026-11-01)
+|The republished `plurimath 0.10.0` (sha `7b870bf0...`) required
+`mml/configuration` at line 2 — an API no mml version ships; iev's
+silent LoadError rescue turned that into 21x
+`uninitialized constant Plurimath::Math` (diag: glossarist/iev#75,
+filed as plurimath/plurimath#528). Fixed by the org-wide moxml-0.6
+update (below): plurimath 0.10.0 yanked, omml released with
+`moxml ~> 0.6.0`, so 0.11.12 resolves again. Full iev suite green
+(489/0) on canon 0.3.118 + moxml 0.6.1 + omml 0.2.8 +
+lutaml-model 0.8.156. iev#75 (the diag) is revert-on-sight.
+
+**Gotcha for any release: a YANKED VERSION NUMBER STAYS INVISIBLE to
+bundler's resolution index even after re-pushing the same number** —
+omml 0.2.7 published, yanked, re-pushed identically, and bundler
+still could not see it. Always release a FRESH patch number after a
+yank (0.2.8).
+
+|The org-wide moxml 0.6 sweep (owner call, 2026-11-01)
+|Shipped
+|Every org gem now rides the moxml 0.6 line: canon 0.3.118
+(`~> 0.6.0`), omml 0.2.8, dcc 0.2.2, metanorma-standoc 3.5.5,
+relaton 3.0.4, expressir (admits), lutaml-model 0.8.156 (admits
+`< 0.7`), mml (unpinned). lutaml-xsd: owner PRs #214/#215. iev's
+suite is the executable proof: 489/0 on the resolved modern stack.
+
+|metanorma-standoc legs: parsanol 1.3.120 removed the `mode` alias
+|Open — relaton-chain grammar follow-up
+|`Parsanol::PARG::ParseError: the grammar header keyword is edition;
+mode (the pre-1.3.113 alias) was removed` fires in
+`@bibdb.fetch_async` (relaton bibdb chain) on standoc's fresh
+resolutions. Some grammar file still says `mode`; move it to
+`edition "v1"` / `edition "v2"` per the parsanol message. Separate
+from moxml entirely.
 |===
 
 == Mechanics every team hits
@@ -146,6 +211,12 @@ interning varies per process).
 swung 1.7x between waves). Only within-run interleaved A/B on fresh
 binaries counts. The perf gate is best-of-N per side.
 
+|Release cuts (canon)
+|`gh workflow run release.yml -f next_version=patch` (patch only; new
+minors/majors are the owner's stated call). The gem bump is committed
+by the workflow. Gemfile.lock is gitignored — CI resolves fresh from
+the gemspec, so constraint PRs are gemspec-only.
+
 |Release cuts (yeptris)
 |`next_version` must be a LITERAL X.Y.Z. The release PR self-closes ~2
 min after cut if checks never start: push a PARENTED trigger commit
@@ -165,6 +236,12 @@ its C `v<c_semver>` tag to EXIST first (platform legs vendor from it).
 |The same cut/trigger/approve cycle; the Unreleased section exists on
 main — keep it fed.
 
+|Dependent legs (rake-with-tools)
+|They run each downstream repo at its own main against lutaml-model's
+branch — a red leg is usually the DOWNSTREAM repo's bug (ferrum boot,
+stale locks), not lutaml-model's. Diagnose in the downstream repo and
+PR there.
+
 |Formatting
 |The repos target clang-format 14+ (CI runs LLVM 18); local 11.1/22.1
 both reject the config — the CI format job is the gate.

data/lib/canon/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Canon
-  VERSION = "0.3.118"
+  VERSION = "0.3.119"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: canon
 version: !ruby/object:Gem::Version
-  version: 0.3.118
+  version: 0.3.119
 platform: ruby
 authors:
 - Ribose Inc.
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-10-31 00:00:00.000000000 Z
+date: 2026-11-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: diff-lcs
@@ -44,14 +44,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.9.398
+        version: 1.9.401
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.9.398
+        version: 1.9.401
 - !ruby/object:Gem::Dependency
   name: moxml
   requirement: !ruby/object:Gem::Requirement
@@ -142,14 +142,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.6.52
+        version: 0.6.54
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.6.52
+        version: 0.6.54
 description: |-
   Canon provides canonicalization and pretty-printing for various serialization
   formats (XML, HTML, JSON, YAML), producing standardized forms suitable for