feat: replicate delivery cartons, and print notes and slips onto the paper

[rexlManu]

Closes #80. Closes #82.

Two changes that landed together because they meet on one prop.

#80 — cartons reach a joined client

Co-op was complete host-side and unplayable as a guest: a client saw the bay and the truck and no boxes, so it could not carry one in, open one, or reach a vial. The day never started.

CartonView + NoteLineView are the same kind of NetworkList row VialView and SlipView are, with a CartonReconciler following SlipReconciler. CartonProp, CartonLid and DeliveryBayStation read through a new CartonFeed, which answers from this process own DeliveryBay first and the last snapshot otherwise — the LabView.Current rule MachineStation already follows, so one piece of code draws a host box and a client one.

Hard rule 2

The interesting part of this change is what does not travel.

• The box carries a count, never a manifest. Carton.Contents is the answer to [gameplay] Reconciling the delivery note against what actually arrived #32. What crosses is VialsRemaining; the bottles travel as VialView rows naming this carton as their container, so a client can draw the room and read "3 vials still in it" without being told which three. CartonView.From takes the count as a parameter rather than the carton manifest, so there is no signature through which sample ids could start travelling.
• A note line carries the claim, not the vial that answers it. DeliveryNote.Line.Sample is absent and has no wire equivalent. A client holding it could tick off the answered rows, and a note that reconciled itself leaves nothing to find. That argument has to survive the wire or it only protects whoever is hosting.
• Views_NameNothingThatOnlyTheHostMayKnow gains Contents and Manifest. The sweep discovers views by reflection, so both new views were already in scope for it.

No new authority code. LabCommandExecutor.CanReachInCarton is still the only route a vial leaves a box by, and a client request reaches it by the identical path. A sealed carton also registers no vial slots, so there is nothing for a client to address in the first place.

#82 — the paper says what it says

Notes and printouts were blank grey sheets whose words lived only in the bottom-left overlay. Both now carry their text, through the PixelText/PixelCanvas rasteriser the reference book has used since #50. The overlay stays — additive, not a replacement.

This is not a material swap on the existing sheet. ProcMesh.Box gives every vertex the same single palette-atlas texel — correct for flat untextured props — so painting through those UVs would sample one colour across the page. PrintedSheetSurface builds its own quad with real UVs, sized from the sheet renderer own bounds. The shared palette material is never written to and LabSceneBuilder did not have to change.

Paper and ink only. A printout that coloured a reading by severity would spend hard rule 4 on a prop.

A redraw is skipped when the words have not changed: SlipReconciler re-binds every visible slip once a frame by design, and redrawing on each would push the whole buffer to the GPU per slip per frame for words that change at most once in a slip life.

Verification

• Both headless compile checks clean.
• Unity imported and compiled everything with zero errors — that is the pass that enforces asmdef boundaries, where a hard-rule-2 violation would actually surface.
• New EditMode tests: carton view round-trip and the two leak sweeps, note lines reaching the desk in printed order, client carton/note reconcile including the shelf-then-held sequence, and the printed sheet surface lifetime.
• The EditMode suite was not run — it is not run in this project at present. Tests here are compile-verified only.
• Not yet verified by eye: whether the header band moulded proud of the sheet collides with the printed title line, and a real two-instance co-op session.