Tags: bzync/nextsql-php

drivers: move the package version forward to 0.1.1

#264 moved the four manifests to 0.0.1 and #266 showed why that can never
ship: 0.0.1 published beside the existing 0.1.0 is not what pip, gem or
composer resolve, and npm refused to move dist-tags.latest backwards onto
it.

The registries are not just holding a different number. drivers/ has
changed by 55 files, +2140/-1258 since the commit that was master when
0.1.0 published, including protocol/errors/client on both Python and
Ruby -- the ERR_* taxonomy of #247 landed after that publish. So every
ecosystem currently installs materially stale, pre-ERR_* code.

Going forward to 0.1.1 dissolves the dilemma: it is higher than anything
published, so default resolution moves to it by the normal rules, with
nothing deleted and nothing irreversible. The engine stays at v0.0.1 and
the driver line decouples -- which the driver docs already stated and
release-drivers.yml already supports via its own drivers-v* tag.

The resolve gate was reproduced locally against want=0.1.1 (exit 0). Node
30/30, python test_protocol.py 49 OK, ruby 46 runs / 200 assertions, php
unit.php ok; the live suites want a server, as before.

This does not publish. A drivers-v0.1.1 tag still cannot reach PyPI until
that environment's deployment rule accepts drivers-v* -- TODO.md #267.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LGj2YnNFoFWNkH6JKhZ3kK