Development record

embark unpacks a lifeboat whole: every decision, issue, intent, spec and retrospective it carries is written, and any conflict refuses the entire write (brief 04-surfaces/03-embark.md). A downstream user starting a new project from its predecessor's lifeboat wanted only selected records carried across and had no way to choose them, so embark could not serve that use. The whole write is the designed behaviour, so this is a capability gap rather than a defect, and intent-shaped: routing it to an intent is the product thinker's call.