v0.9.2

A packaging repair. No source change, no API change. The suite is green again: 4 files, 37 tests, 0 failures.

What was wrong

The package could not be resolved, built or tested by anyone. Five independent defects, none in its code:

• No sigil: field. sigil deps install refused before doing any work.
• Dependencies requested from the monorepo they no longer live in. sigil-crypto and sigil-tls were declared as url: "codeberg:sigil/sigil" package: "..." after both were extracted.
• One dependency that is obsolete rather than stale. sigil-socket has been ABSORBED into sigil-stdlib; the module ships there now, so the dependency is dropped rather than repointed.
• (scheme base) imported but never declared. src/sigil/xmpp/connection.sgl imports it; it lives in sigil-r7rs and used to arrive transitively from the pre-extraction monorepo stdlib.
• No dev-dependencies. This package pulls in native code through tls/crypto, and building a test harness for a native package requires sigil-test and sigil-test-runner. Without them the suite could not run at all — not fail, run.

What changed

    sigil: "0.20"                     bare, per the 2026-08-25 rule
    sigil-stdlib  ^0.9.0  -> ^0.20
    sigil-tls     monorepo -> codeberg:sigil/sigil-tls    ^0.16
    sigil-crypto  monorepo -> codeberg:sigil/sigil-crypto ^0.16
    sigil-sxml    ^0.9.0   -> ^0.15
    sigil-socket  monorepo -> REMOVED (now in sigil-stdlib)
    sigil-r7rs    (absent) -> codeberg:sigil/sigil-r7rs   ^0.16   [new]
    dev-dependencies: sigil-test ^0.20, sigil-test-runner ^0.20   [new]

Why 0.9.2 and not 0.7.1

master declared 0.7.0 while tags v0.8.0 and v0.9.1 already existed — v0.9.1 being a mass mis-tag that named the sigil-stdlib version a migration moved to rather than this package's own version. Releasing 0.7.1 would place a new tag below two existing ones, which no consumer range would resolve sensibly. This goes monotonic above the highest existing tag instead. Nothing currently depends on this package, so the jump costs nothing.