canon 0.3.117 → 0.3.119

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 223b5ab0201bbebfe8bfee1de2f23229260f574bd6d42fed426256b199f03d6c
-  data.tar.gz: 803eaba7a9fd850a38669c9ea2bbd567503fbc936fd39147a473d2526b3539ce
+  metadata.gz: 21b508095633774da379c4f7c13cfaeabce997fbdb400139e7ecf7aedbf3df95
+  data.tar.gz: 9528d6c70d4b84f43bf77e5ca7b30a4bbf2ee8f3a172a010d0c6ea90228a9c75
 SHA512:
-  metadata.gz: 24ae7e292b598242df4c98bad7d98d98815d7d28ddebd6d1ed79df4451e40017cd3840f2a3556bf4b78681ee7b6653ee91a67623d806d2aec1d8e170093a19d8
-  data.tar.gz: 35a5642e0e6b5b0268935d6888470614058888a3e4cc33d587ea079737a3817b9543aa63fbae986da95240a2c4c72174419eae1fba9336e871859ae6aae6ee3d
+  metadata.gz: 2de6ab858f2c4ca1ba6b83cad30058af17c2427e9688b13babde2bc249fdf5234d453575c36956b5edc2b343c4876647439b8d604bc5a3bcb96c746759c31a86
+  data.tar.gz: 51ac169753e93464ff16be5e869f0d157c1dcc0446311551322fcd19ee120a38a94d5581db9f167436f1d6ed8461b4fedff2899dd1d3fd12b32ac68957521b23

data/CLAUDE.md

@@ -128,18 +128,18 @@ The comparison pipeline flows through four independent layers:
 - `lib/canon/formatters/` — Pretty-printers for canonicalization/formatting (distinct from diff formatters). `XmlFormatter` supports Canonical XML (C14N).
 - `lib/canon/config.rb` — Global configuration with per-format settings (profiles, preprocessing, diff options). Read at runtime via `Canon::Config.instance`.
 - `lib/canon/rspec_matchers.rb` — RSpec matchers (`be_xml_equivalent_to`, `be_json_equivalent_to`, etc.). These delegate to `Canon::Comparison.equivalent?` with the global config. Automatically included in RSpec.
-- `lib/canon/xml/sax_builder.rb` — SAX-based canon-tree builder (~6x faster than DOM parsing for large documents). Engine-neutral; `lib/canon/xml/sax.rb` selects the driver following the resolved adapter (`MoxmlDriver` → leptris SAX under the leptris default, `NokogiriDriver` when the adapter is nokogiri, `MoxmlDriver` under Opal).
+- `lib/canon/xml/sax_builder.rb` — SAX-based canon-tree builder (~6x faster than DOM parsing for large documents). Engine-neutral; `lib/canon/xml/sax.rb` selects the driver following the resolved adapter (`MoxmlDriver` → leptris SAX under the leptris default, `NokogiriDriver` when the adapter is nokogiri).
 
 ### XML Engines
 
 Canon is engine-agnostic across three seams (MECE — one concern per module):
 
-- `Canon::XmlBackend` — XML engine selection. The default follows moxml's resolved adapter: **leptris whenever it is installed** (parse ~1.6x, serialize ~3.8x vs Nokogiri), raw Nokogiri otherwise (wrapping Nokogiri in moxml buys nothing — the wrapper adds 2-3x overhead). `:moxml` under Opal. `CANON_XML_BACKEND=nokogiri|moxml` forces either engine.
+- `Canon::XmlBackend` — XML engine selection. The default follows moxml's resolved adapter: **leptris whenever it is installed** (parse ~1.6x, serialize ~3.8x vs Nokogiri), raw Nokogiri otherwise (wrapping Nokogiri in moxml buys nothing — the wrapper adds 2-3x overhead). Opal is retired (moxml 0.6 deleted the Opal surface, lutaml/moxml#516; the forward path is the moxml-ts wasm binding, lutaml/moxml#489). `CANON_XML_BACKEND=nokogiri|moxml` forces either engine.
 - `Canon::XmlParsing` — the only place that talks to engines for XML parse/serialize (moxml parses pass `readonly: true` — canon never mutates engine documents); node type queries answer for ANY recognized node (Nokogiri or moxml) by type, never by active backend — user-supplied Nokogiri nodes keep working under the moxml engine.
 - `Canon::Html::NokogiriSupport` — HTML engine seam. **HTML is engine-served end-to-end** since 0.3.86-0.3.101: `HtmlParser.parse` routes through moxml `Context#parse_html_fragment` (WHATWG fragment parsing, moxml#353 riding leptris) and builds a Canon tree via the materialize-records fast path — whitespace text nodes survive the parse unconditionally (HTML whitespace significance is the comparison profile's decision, #112/#137), and `parse_node` walks Canon trees directly. The semantic lane's `DataModel.from_html`, the `:format` string normalizer, the canonical HTML formatters, `format_html`'s default/XHTML display modes, and `validate_xhtml!` are all engine-served (0.3.99/0.3.100/0.3.101) — **HTML comparison and formatting run nokogiri-less** (pinned by the optionality contract spec). The Nokogiri HTML fragment path remains only for runtimes without an engine HTML adapter and for user-supplied Nokogiri nodes. Nokogiri's residual roles: the `fixture_ready` display mode (libxml FORMAT|AS_XHTML — moxml#390 filed for an engine XHTML mode), the HTML5 validation lint layer (gumbo error-level classification — leptris#1771 filed), and the fragment-records lane once delivered nil URIs for prefixed attributes (moxml#367, fixed in moxml 0.5.130 — the bulk read now falls back to the reserved-prefix table); the TreeBuilder keeps the one legal `xml`-prefix binding as standing defense.
-- `Canon::Xml::Sax` — SAX driver selection follows the resolved adapter: `MoxmlDriver` (leptris SAX — the comparison hot path, CI-gated in the split flip) under the leptris default, `NokogiriDriver` when the resolved adapter is nokogiri, `MoxmlDriver` under Opal. The builder (`SaxBuilder`) is engine-neutral.
+- `Canon::Xml::Sax` — SAX driver selection follows the resolved adapter: `MoxmlDriver` (leptris SAX — the comparison hot path, CI-gated in the split flip) under the leptris default, `NokogiriDriver` when the resolved adapter is nokogiri. The builder (`SaxBuilder`) is engine-neutral.
 
-Engine parity is complete through libleptris 1.9.8 / leptris-ruby 1.9.33 / moxml 0.5.12: attribute-value normalization, prolog/epilog PIs and comments, DTD ATTLIST defaults off by default (opt-in via `ParseOptions::DTDATTR`), PI-data whitespace matching libxml2, materialize with namespace declarations and a root-subtree-only record contract (moxml#140), readonly parse, deterministic `Document#free` (wired into `from_moxml_xml` — moxml#134). Canon's moxml conversion is record-based (`build_from_moxml` consumes `materialize` records — no per-node wrapper allocation; ~0.55x the Nokogiri conversion). `spec/canon/xml/engine_parity_spec.rb` is fully green. Pretty-printing runs the leptris serializer through `PrettyPrinter::Xml#moxml_format` (byte parity via moxml#153/#155/#156; the #167 escaping race fixed in 0.5.28), with Nokogiri serving the fallback engine and Opal — pretty-printed bytes are canon's product, gated by the fixture-integrity suite and the CI performance gate.
+Engine parity is complete through libleptris 1.9.8 / leptris-ruby 1.9.33 / moxml 0.5.12: attribute-value normalization, prolog/epilog PIs and comments, DTD ATTLIST defaults off by default (opt-in via `ParseOptions::DTDATTR`), PI-data whitespace matching libxml2, materialize with namespace declarations and a root-subtree-only record contract (moxml#140), readonly parse, deterministic `Document#free` (wired into `from_moxml_xml` — moxml#134). Canon's moxml conversion is record-based (`build_from_moxml` consumes `materialize` records — no per-node wrapper allocation; ~0.55x the Nokogiri conversion). `spec/canon/xml/engine_parity_spec.rb` is fully green. Pretty-printing runs the leptris serializer through `PrettyPrinter::Xml#moxml_format` (byte parity via moxml#153/#155/#156; the #167 escaping race fixed in 0.5.28), with Nokogiri serving the fallback engine — pretty-printed bytes are canon's product, gated by the fixture-integrity suite and the CI performance gate.
 
 Engine A/B testing: `CANON_XML_BACKEND=nokogiri bundle exec rspec` (or `=moxml` to force leptris when it isn't the resolved default). The default suite must stay green under BOTH values; the only expected pendings are the upstream-tracked ones. The benchmark header (`rake performance:quick`) reports the active engine.
 

data/Rakefile

@@ -5,50 +5,10 @@ require "rspec/core/rake_task"
 
 RSpec::Core::RakeTask.new(:spec)
 
-begin
-  require "opal/rspec/rake_task"
-
-  # Configure Opal load paths at load time (same pattern as moxml)
-  if defined?(Opal)
-    Opal.append_path File.expand_path("lib", __dir__)
-
-    # moxml gem
-    begin
-      moxml_spec = Gem::Specification.find_by_name("moxml")
-      moxml_lib = moxml_spec.full_require_paths.first
-      Opal.append_path moxml_lib
-      moxml_compat = File.expand_path("compat/opal", moxml_lib)
-      Opal.append_path moxml_compat if File.directory?(moxml_compat)
-    rescue Gem::MissingSpecError
-      # moxml not installed
-    end
-
-    # REXML: bundled gem since Ruby 3.4
-    rexml_lib = $LOAD_PATH.find do |p|
-      File.exist?(File.join(p, "rexml", "document.rb"))
-    end
-    Opal.append_path rexml_lib if rexml_lib
-  end
-rescue LoadError
-  # Opal not available or incompatible with current Ruby version
-end
-
 require "rubocop/rake_task"
 
 RuboCop::RakeTask.new
 
 Dir.glob("lib/tasks/**/*.rake").each { |r| load r }
 
-namespace :spec do
-  if defined?(Opal::RSpec::RakeTask)
-    desc "Run Opal (JavaScript) tests"
-    Opal::RSpec::RakeTask.new(:opal) do |_server, runner|
-      runner.default_path = "spec"
-      runner.requires = %w[rexml_compat rexml/document rexml/xpath
-                           moxml moxml/adapter/rexml spec_helper]
-      runner.pattern = "spec/canon/opal_xml_smoke_spec.rb"
-    end
-  end
-end
-
 task default: %i[spec rubocop]

data/docs/HANDOFF.adoc

@@ -0,0 +1,255 @@
+---
+published: false
+---
+= Cross-team handoff: the engine issue board
+
+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-11-01.
+
+== 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"]
+|===
+|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"]
+|===
+|Issue |Status |Known + first moves
+
+|leptris#1866 — cross-doc replace + `@id/..` + serialize
+|CLOSED (v1.9.385, #1869)
+|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`).
+
+|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#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
+
+[cols="1,1,2"]
+|===
+|Issue |Status |Known + first moves
+
+|yeptris#739 — JSON parse 2x behind yyjson
+|Open
+|The 12x WRITE gap is closed (serialize 16->221 MB/s: the one-pass
+route, the run-batched `emit_dq_json` SWAR scan, the `emit_json_value`
+walker). Parse remains; profile with the counting-malloc interposer.
+
+|yeptris#742 — YAML emit ~1.5x behind rapidyaml; CBOR decode 1.3-2.2x
+behind tinycbor
+|Open
+|13-leg matrix. The emit side shares machinery with the closed #739
+write work — reuse the walker patterns.
+
+|yeptris#474 — `parse_json_tape` 0.61x vs simdjson on arm64 (ubuntu
+1.07x, same binary)
+|Open
+|Platform-specific: diff the arm64 SIMD kernels vs the scalar fallback
+(`src/yeptris/common/simd_text*`), starting from the kernel-selection
+law.
+
+|yeptris#352 — yaml generation 1.4-1.7x behind rapidyaml (10/12
+platforms)
+|Open, partially improved
+|Remaining: scalar-route derivation cost. `benchmarks/PERF-LEDGER.md`
+has the trusted-into entries.
+|===
+
+== leptris/yeptris-ruby
+
+[cols="1,1,2"]
+|===
+|Issue |Status |Known + first moves
+
+|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
+
+[cols="1,3"]
+|===
+|Topic |The law
+
+|Differential corpora
+|Random-tree corpora never produce repeated keys or shared references —
+shift/registration bugs survive 300/300 "green". Include linked shapes
+(users-style rows). Lock byte-level fixtures to FILES (Ruby's fstring
+interning varies per process).
+
+|Performance claims
+|Cross-wave serialbench comparison is INVALID (runner noise; pugixml
+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
+(`git commit-tree -p "$sha" -m ... "$sha^{tree}"` — without `-p` the
+commit orphans and the PR creation fails) within the window, then
+approve runs gated at `conclusion == "action_required"` (the `status`
+field reads `completed` while gated). The changelog gate requires an
+`## [Unreleased]` section before EVERY cut, version-only ones included.
+
+|Release cuts (yeptris-ruby)
+|RELEASE_TOKEN unset -> the bump job's 60-min wait step always fails;
+the PR opens anyway. Hand-merge on green, then dispatch the republish
+with EMPTY next_version (reuses main's VERSION). A new gem version needs
+its C `v<c_semver>` tag to EXIST first (platform legs vendor from it).
+
+|Release cuts (leptris)
+|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.
+
+|CI flakes
+|`pull_request` events intermittently vanish for fresh PRs (yeptris,
+leptris). Fallback: `gh workflow run test.yml format.yml asan.yml --ref
+<branch>` — sha-keyed check runs satisfy required-context protection.
+A "failed" check may be CANCELLED by a concurrent push (concurrency
+groups) — read the conclusion, `gh run rerun <id> --failed`.
+|===

data/lib/canon/version.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: canon
 version: !ruby/object:Gem::Version
-  version: 0.3.117
+  version: 0.3.119
 platform: ruby
 authors:
 - Ribose Inc.
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-10-24 00:00:00.000000000 Z
+date: 2026-11-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: diff-lcs
@@ -44,28 +44,28 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.9.376
+        version: 1.9.401
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.9.376
+        version: 1.9.401
 - !ruby/object:Gem::Dependency
   name: moxml
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.5.149
+        version: 0.6.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.5.149
+        version: 0.6.0
 - !ruby/object:Gem::Dependency
   name: paint
   requirement: !ruby/object:Gem::Requirement
@@ -142,14 +142,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.6.32
+        version: 0.6.54
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.6.32
+        version: 0.6.54
 description: |-
   Canon provides canonicalization and pretty-printing for various serialization
   formats (XML, HTML, JSON, YAML), producing standardized forms suitable for
@@ -171,6 +171,7 @@ files:
 - Rakefile
 - docs/.lycheeignore
 - docs/Gemfile
+- docs/HANDOFF.adoc
 - docs/INDEX.adoc
 - docs/_config.yml
 - docs/_references/canonical-digests.adoc