v0.17.0

This release moves sigil-mcp onto the 0.18 runtime. It carries no new features and no behaviour changes: the version jump exists to state a runtime requirement that 0.16.5 already had but did not declare. Sigil 0.18 renamed the stdlib module (sigil env) to (sigil dotenv), and sigil-mcp imports it for load-env-file!. Because no 0.17.x runtime provides (sigil dotenv), this code cannot run on one.

Pin sigil-mcp at ^0.17 only if your project runs on Sigil 0.18 or newer. If you are still on a 0.17 runtime, stay on the 0.16 line, which v0.16.6 restores to a working state.

Changes

• Declares the real runtime floor: the package manifest now says sigil: "^0.18" instead of the inaccurate ^0.16 inherited from 0.16.5.
• No source changes. The (sigil env) to (sigil dotenv) migration itself landed in 0.16.5; this release only versions it honestly.

Upgrade notes

The failure mode this release prevents is quiet, so it is worth stating plainly. Building sigil-mcp 0.16.5 against a 0.17 runtime SUCCEEDS. Dependency resolution exits 0, the build exits 0 and prints a bundle summary, and the resulting binary then dies at startup:

    $ sigil build apiary -c release --backend bytecode --force
    Bundle created: build/release/bin/apiary
       74 modules, 2.1 MB
    $ ./build/release/bin/apiary --version
    Error loading entry module (apiary main): module-import: library not found: (sigil dotenv)

Nothing in the build output is false. It simply is not about whether the program runs. Verify an upgrade by running the binary, not by reading the build log.

Consumers on Sigil 0.18 or newer should move their pin from ^0.16 to ^0.17. Consumers still on a 0.17 runtime should pin ^0.16 and take v0.16.6.