Library defers the lifeboat's memory payload to the spec that wires the packer; disembark has the packer shipped with a fixed file set and no memory section

Library defers the lifeboat's memory payload to the spec that wires the packer; disembark has the packer shipped with a fixed file set and no memory section

A sequencing impossibility (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/04-surfaces/07-library.md:424 — "declaring an exact payload is deferred to the disembark spec that wires the packer (adr-28)"
• End B: .abcd/development/brief/04-surfaces/02-disembark.md:129 — "Each path derives from the brief-section-to-lifeboat-path mapping in internal/core/lifeboat/mapping.go: a section grounds into its file where the source supports it"

Library says disembark is designed to export curated project memory into the lifeboat and that declaring the exact payload is deferred to the disembark spec that wires the packer. Disembark records the pack as shipped, every path derived from the brief-section mapping, and its output shape holds the brief, graveyard, rescue, retrospectives, ADRs and issues with no memory section. The deferral waits on a wiring that, as disembark writes it, has already happened without carrying memory.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 264.