Update to v1.9.2

[yhoztak]

Update for v1.9.2 release

[cursor]

[P1] Roll forward past the already-published 1.9.2

v1.9.2 already points to f817199, where this manifest is still 1.9.1. The tag workflow (run 30302459430) consequently built corgea_cli-1.9.1 artifacts and skipped every PyPI upload as already existing, while @corgea/cli@1.9.2 is now published and its bundled binary reports corgea 1.9.1. PyPI still lists 1.9.1 as latest. Merging this commit cannot retrigger the tag build or replace the immutable npm package, so keeping 1.9.2 here leaves the npm/PyPI/runtime versions permanently inconsistent. RELEASING.md:113-115 explicitly requires rolling forward after a published bad version. Bump both Cargo.toml and the root package entry in Cargo.lock to 1.9.3, then merge and tag that commit; deprecate the bad npm 1.9.2 if appropriate.

Suggested change

	version = "1.9.2"
	version = "1.9.3"