v0.9.2

A packaging repair. No source change, no API change.

What was wrong

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

• No sigil: field. sigil deps install refused before doing any work.
• Three dependencies requested from the monorepo that no longer lives there. sigil-http, sigil-json and sigil-log were declared as url: "codeberg:sigil/sigil" package: "...", but all three were extracted into their own repositories, so the resolve failed outright.
• Those pins were still on ^0.9.0.
• (scheme base) was imported but never declared. src/sigil/oauth.sgl imports it; it lives in sigil-r7rs, which arrived transitively from the pre-extraction monorepo stdlib and stopped arriving when that changed.

What changed

    sigil: "0.20"                        bare, per the 2026-08-25 rule that
                                         this field is a minimum, not a range
    sigil-stdlib  ^0.9.0  -> ^0.20
    sigil-http    monorepo -> codeberg:sigil/sigil-http  ^0.18
    sigil-json    monorepo -> codeberg:sigil/sigil-json  ^0.16
    sigil-log     monorepo -> codeberg:sigil/sigil-log   ^0.17
    sigil-r7rs    (absent)  -> codeberg:sigil/sigil-r7rs ^0.16   [new]

Verification, and its limit

sigil deps install and sigil build are clean at this commit.

This package has no test/ directory, so a green build is the whole of what can be verified here. That is stated rather than left implied: nothing about runtime behaviour is being claimed by this release.

Consumers

sigil-twitch and sigil-youtube both depend on ^0.9 and were failing to build against v0.9.1 for the (scheme base) reason above. They resolve to this release without an edit.