feat: add 15 commands from fuji — cart, index, issue, pass, receive, recall, remember, search, status, summary, plan, work, why, insight, ask

receive.md

@@ -0,0 +1,25 @@
+Resume from the most recent session handover. Execute in order:
+
+1. SEARCH: Run memory_recall for subject `handover.session` to find all handover entries. Sort by date (newest first from created_at). Also run memory_recall with query "session handover open items next steps" to catch any handovers stored with variant subject names.
+
+2. FOUND PATH — if a handover exists:
+   a. Fetch the full handover memory via memory_get (no truncation).
+   b. Present a summary to Pilot:
+      - What was worked on last session (numbered list, one line each)
+      - Key artifacts modified (file paths)
+      - Open items / next steps (numbered, actionable)
+      - How old the handover is (date + days ago)
+   c. Ask Pilot via Question tool:
+      - "Accept this handover?" with options: "Accept all", "Accept and review open items", "Show full handover", "Skip — start fresh"
+   d. If accepted: load the handover context, state which open items you're ready to work on, ask Pilot which to tackle first.
+   e. If "show full": display the complete handover memory content, then re-ask acceptance.
+   f. If skipped: proceed as a normal session with no inherited context.
+
+3. NOT FOUND PATH — if no handover exists:
+   a. State: "No session handover found in EEMS."
+   b. Ask Pilot via Question tool:
+      - "How would you like to start?" with options: "Search EEMS for recent work", "Start fresh — tell me what to do", "Run /summary to audit EEMS first"
+   c. If "search EEMS": run memory_recall for recent entries (last 24h via created_at), summarize what's in memory, ask what to continue.
+   d. Otherwise: proceed per selection.
+
+4. BOOT: Regardless of path, complete standard identity boot (memory_recall for core.* subjects) before starting work. The handover provides task context, not identity context.