chore(release): bump to 0.10.19 so the staging hop can tag again (backend#2790)

[LukasWodka]

Why

The 2026-08-31 staging settle refused cli:

rc NOT tagged - v0.10.18 already exists and the delta DOES touch published files
(bump VERSION on develop before the next release)

v0.10.18 is tagged and the staging...develop delta touches internal/cli/*, internal/submit/* and scripts/install.ps1 — all declared publish paths. Re-tagging would make one tag name two different trees.

Patch, measured

Two commits, both fix:

• fix(ingest): report the physical destination table, not the requested name (backend#2255)
• fix(install): a VERIFIED signature no longer kills the Windows install (fix(install): a VERIFIED signature no longer kills the Windows install #611)

No feat, nothing breaking → 0.10.18 → 0.10.19. VERSION is the only tracked file carrying the string — checked rather than assumed.

The count is the finding

This is the fifth version-bump refusal today. design-system-v2 hit it at v0.1.0 and again at v0.1.1; this is cli's turn.

A fourth apparent case on design-system-v2 in this same settle turned out not to be a missing bump at all — its mirror was stale at 0.1.2 while develop had already moved to 0.2.0, so it needed a recut, not a bump. Two failure modes that produce the same refusal message and want opposite remedies, told apart only by hand. That is its own argument for automation: a human reading rc NOT tagged cannot tell them apart without going and checking the mirror's own package.json.

.github#372 builds post-release-bump.yml to open the bump PR the moment a release consumes a version. This repo needs its caller, and so does design-system-v2. That is the open third checkbox on tracebloc/backend#2790, and this PR is the fifth piece of evidence for it.

Part of tracebloc/backend#2790

---

Note

Low Risk
Single-file version string update with no runtime or security impact.

Overview
Bumps the release marker in VERSION from 0.10.18 to 0.10.19 so the next staging settle can tag a new RC without reusing v0.10.18 (which already points at a published tree while develop has additional fixes on publish paths).

No application, CLI, or install logic changes in this diff—only the version string file.

^{Reviewed by Cursor Bugbot for commit 6ea707c. Bugbot is set up for automated code reviews on this repo. Configure here.}