[milutinke]

Make mining and block placement follow vanilla targeting, permissions, geometry, interaction results and swing order across protocols 47–777. Reuse the existing session owners and keep unavailable context explicit. This PR remains incomplete and draft.

The component checkpoint (b03301b, documentation 2c19272) preserves held mining when a new inventory packet carries an equivalent enchantment map on protocols 766–777. Meaningful key, final-level, explicit-zero or applicable tooltip changes still reset mining. It also connects measured can_break and can_place_on codecs and permissions through protocols 771–773 (1.21.6–1.21.10), preserving activation precedence, post-USE PASS decisions and unknown context. Protocol 774 onward retains its distinct unbound predicate wire form. Versions, dependencies, DI lifetimes and existing public action signatures stay unchanged.

The latest checkpoint (f2b2d70, documentation 72873c0) adds native final-map validation for both enchantment component forms on protocols 766–777. It rejects final levels outside 0–255 after all entries and the legacy tooltip, while allowing valid same-key overwrites and preserving accepted raw bytes. The 344 new bound-codec cases first reproduce 192 causal failures/152 controls, then all pass after the codec-only fix; all 1,324 retained checks and the complete 6,959-case Protocol suite pass with zero skips. Normal two-file formatting changes nothing. The expected seventeen-suite total is now 50,462, not a claimed fresh seventeen-suite run.

Seven-job CI for published 72873c0 is in progress in run 41354137087. The successful 2c19272 results below remain the preceding checkpoint. New producer-matched consumers/AOT/package runtime and native/live acceptance remain separate.

Check	Result and limits
Component checkpoint local runtime	Full Client 36,131, Protocol 6,615 and Conformance 892 pass with zero skips. All 1,324 focused/regression cases pass. Source/PDB hashes match the committed eleven-file implementation; private libraries retain D5 compiler metadata. The Protocol wrapper's one shape-derived display mismatch is accepted by an exact source-bound offline audit; the successful suite is retained and the original wrapper remains failed.
Native comparisons	33 original Adventure codec/hash cases and 190 original enchantment identity/admission/definition checks pass. These execute controlled original methods, separate from native client input, world ticks or live-server acceptance.
Generated reference checks	Three expected identity-pin failures and 98 controls precede documented generation. Only protocol 771/772/773 identity files change: 33 lines/36 nested digest tokens, with all 404 other fixtures unchanged. Strict focused302/full892 pass with update switches absent.
Component checkpoint local format/counts	Normal formatting of the eleven reviewed files passes with zero changes, both analyzer phases on all four affected owners and no workspace warnings/errors. Deliberate additions are Client +190 and Protocol +19; 50,118 is the expected seventeen-suite total, not a fresh local seventeen-suite result.
Previous-head CI (2c19272)	All seven jobs pass for published 2c19272 in run 41350348597. All three OSes report seventeen-suite totals 50,118, with unchanged normal skips 23/25/25. Full formatting loads 47 projects, analyzes all 44 authored owners and changes zero of 2,484 files without workspace warnings. CI AOT is 24,787,528 < 25,165,824 bytes, exactly one passing smoke and the XML guard. Packages 14+13 and isolated consumer restore/build pass; package-consumer runtime remains open.
Earlier consumer/AOT checkpoint	On the earlier D5/1c31d97 tuple: DMCBK 1,999 and MCC 918 pass, all 33 endpoint DLL comparisons and 26 test-runtime hashes match, and local AOT is 24,775,104 < 25,165,824 bytes with exactly one executed passing smoke and the CI XML guard. These results do not identify the new component candidate; fresh local producer-matched consumers/AOT remain required.

The earlier published 1c31d97/run41331365182 passes all seven CI jobs: seventeen-suite totals 49,909 per OS, normal opt-in skips 23/25/25, full healthy formatting of 47 projects, strict AOT/exactly one smoke, packages and isolated consumer restore/build. Package-consumer runtime remains open. Historical local memory, formatter-selection, consumer cleanup-snapshot and native-wrapper schema failures remain recorded under their original checkpoints.

Retained live evidence includes the older-producer 1.21.5 six-scene placement result and the D5 1.11 eleven-scene Wolf placement/replay result. The latter proves exclusion of the distant Wolf by its known envelope, not its exact body/motion, Horse participation or original graphical-client input parity. Required new-producer native/live acceptance remains separate.

Remaining behavior includes the later Adventure wire form and richer predicates, specialized placement/fluid/tool interactions, contextual targeting, participating entity/rider/authority cases and the 50-protocol/75-release pack. Final local aggregate/package-runtime, fresh producer-matched consumer/AOT and native/live checks remain required. Protocol 47 keeps its 1.8.9 client profile. Merging and package/release publication are outside this task.

DMCBK #7 contains the committed consumer command changes as a draft. Its stock CI is blocked because pinned UMPK 0.9.0-beta.7 lacks five APIs supplied by this upstream work; unit tests did not run there. The dependency version, sibling source/Git state and uncommitted tooling files are unchanged.

Verification index · Component checkpoint evidence · Enchantment admission evidence · Completion ledger