GeezerVison

LLM Description written by Claude Code:claude-opus-5-5

Fixes #936

Summary

Vendored Poetry chose its forward splicer by the lock's line endings. Legacy and CRLF locks went through the shared utils::poetry_lock engine, while LF 2.x locks went through a private toml_surgery line scanner. Now every lock goes through the engine, which writes Poetry's own one-file-per-line files array for 2.x locks. The scanner and its Poetry-only helpers are deleted.

Why

• Issue #936, register row E66, living document Part 5 (doc/05-vendored.md, "Vendored Poetry has two forward splicers").
• The two paths had drifted, and two runs of the audit's test confirmed it:
  • they wrote different files shapes for the same lock depending on core.autocrlf;
  • only the engine checked the wheel name and lowercased the digest;
  • only the scanner required a literal name = "…" line.
• Leverage: B 0, U 1 (the E23 shared PyPI lock envelope and Tracking: revert every vendored backend through one record-revert engine instead of nine hand-written mechanisms #989 step 3 need one Poetry forward path), D 1 plus 129 net production lines deleted, S 0, R M. It was the best-ranked candidate whose files no open arch-refactor/* or agent/fix-* PR changes.
  • One exception: vendor/common.rs is also changed by my own #1160. Its hunks (the imports and the JSON BOM helpers, lines 9–220) don't overlap this PR's single deletion at line 626, so the two merge cleanly in either order.

What changed

1. utils::poetry_lock writes a 2.x package's patched files with the multi-line renderer that the 1.0/1.1 [metadata.files] entries already use (multiline_files, split out of legacy_files_entry).
2. wire_poetry calls rewrite_poetry_lock_with_edits for every lock generation and line ending.

Deleted

• pypi_poetry::rewrite_target_package_unit
• toml_surgery::package_unit_lines, toml_surgery::replace_files_array and their tests
• common::unit_has_canon_name
• Production: +37 / −166 (net −129). Tests: +144 / −140 across the unit tests and one CLI test. Two equivalence goldens are re-blessed.

Behavior

These changes are intended, and the issue's acceptance criteria ask for them:

• Hosted rewrites of a 2.x poetry.lock (Poetry 1.3+) now write files = [\n {file = …, hash = …},\n] instead of files = [{ file = …, hash = … }]. Vendored CRLF 2.x locks get the same shape. Vendored LF output is unchanged: the fixture test wiring_matches_fixtures_byte_identically_both_lock_versions stays byte-identical. Legacy 0/1.0/1.1 output is unchanged.
• A vendored LF 2.x lock spelled name="six", or one whose unit has no files array, now wires and reverts byte-exact, as a CRLF lock already did. Before, it was refused with pypi_poetry_lock_package_missing / pypi_poetry_lock_parse_failed.
• Vendored LF 2.x now gets the engine's wheel-name and digest-case gates. Today's orchestrator always passes a matching wheel and a lowercase sha, so this changes nothing in practice.
• Revert is unchanged, because both paths already reverted through revert_lock_fragment_splice_atomic. Ledgers written by the old LF path still revert: their fragments are spliced back verbatim.

Golden re-bless

• poetry_rewrite.golden: only the 2.x generations (1.3.2 through 2.4.3, 8 cases each) move. The 0.12.17, 1.0.10, 1.1.15 and 1.2.2 cases keep their digests.
• poetry_lock_reused_parse.golden: cases 0–231 (the 4 legacy generations × 58) keep their digests, and cases 232–869 (the 11 2.x generations) move.

Tests

• New:
  • lf_and_crlf_locks_wire_to_the_same_fixture: each 2.x fixture wired as LF and as CRLF gives the same lock, and that lock is Poetry's own fixture. It fails on main, where CRLF wrote the inline shape.
  • wire_accepts_a_unit_spelled_without_spaces (LF and CRLF) and wire_adds_files_to_a_unit_without_one: these replace the two fail-closed tests that pinned the scanner's refusals. Both wire and then revert byte-exact.
  • lock_2x_files_keep_poetrys_multiline_shape: the hosted (url) and vendored (file) rewrite of 3 2.x fixtures, plus an idempotent re-run.
• Commands:
  • cargo clippy --workspace --all-features -- -D warnings: clean.
  • cargo test -p socket-patch-core --lib: 5,799 passed. 4 failed, the known root-only tests (relax_loop_must_not_traverse_symlinked_root, an_unremovable_hidden_lock_keeps_every_store_entry, wire_write_failure_maps_error_and_leaves_lock_untouched, wire_failure_rolls_back_already_written_files).
  • cargo test -p socket-patch-core --test '*': all passed.
  • CLI suites, all passing: e2e_vex_lockfile (343), in_process_redirect_poetry (7), in_process_vendor (122) and hosted_memory_engine (34). covgap_commands_vendor passed 51; 3 failed, all root-only (*_state_write_failure_*, which chmod the vendor dir to 0555).
• No changes are needed in the wrappers (npm/, pypi/, gem/).

Risk

Medium. The user-visible change is the hosted 2.x files layout, which now matches what Poetry writes. Hosted restore already rebuilds files through multiline_toml_array, and VEX discovery reads files through the parsed TOML, so neither depends on the layout.

🤖 Generated with Claude Code

https://claude.ai/code/session_019qW3rRLpBivgBuWXHMZ36z

Generated by Claude Code