corpus: pin chant 0.110.0, declaring spec 2.3

[lex00]

The corpus and the conformance cross-check move from chant 0.109.0 to chant 0.110.0, which declares spec 2.3.

Changes

• Root @intentius/chant 0.109.0 to 0.110.0, and CHANT_REF in corpus.yml to chant-v0.110.0.
• chant-agreement.test.ts: three hold-outs are gone. Both F-Call fixtures (chant#3610) agree now that 0.110.0 carries chant#3618. F-Obs-Provenance/a-host-call-in-a-field-is-unknown (tsad#248) agrees now that chant#3619 reports a host call or host value in a resource field as unknown.
• Two fixtures stay held: F-Obs-Provenance/a-host-call-at-an-export-is-unknown and F-Obs-Provenance/a-host-value-is-unknown. Both assert the origin of a plain export (export const k = count([1, 2]), export const large = SIZES.large), and chant keeps no provenance record for a non-resource export at all, a limit chant#3619 states. chant reports app.ts: k: no origin reported and app.ts: large: no origin reported. No chant issue tracks this yet.
• corpus-report.md and provenance-report.md regenerated at chant-v0.110.0 (037f355dd, clean), with the Rust evaluator built and the external checkout fetched.
• paper/measurements.md and paper/draft.md carry the new pin: a history row for 0.110.0, the provenance table and its reasons, six of eight provenance fixtures passing, and the appendix's pin and date.

Before and after

	chant 0.109.0	chant 0.110.0
Corpus totals	467 files, 466 comparable, 466 agreed, 310 both fold	unchanged
data-host column	467 of 467 agreed, 149 both fold	unchanged
Checker column	990 exports, 944 out of scope, 31 pass, 15 unchecked, 0 fail	unchanged
Isolation	16 files lost	unchanged
Provenance, fold: direct / unknown	1442 / 5249	1368 / 5323
Provenance, fold: known share	21.8%	20.7%
Provenance, all: direct / unknown	2658 / 6211	2584 / 6285
Provenance, all: known share	30.1%	29.3%
Known among composite-built fields	18 of 5267 (0.3%)	18 of 5267 (0.3%)

The 74 fold-side fields that moved from direct to unknown are host calls (11) and host values (63) written in resource fields outside any composite, the new host-call and host-value reasons. Composite fields did not move: every lexicon composite's field is still composite-not-interpreted.

Gates run locally

npm run typecheck, npm test (151 passed, 9 skipped, with TSAD_EXPECT_CHANT_PROVENANCE=1), npm run lint:prose (0 gated, no regressions), npm run docs:build.