land

/land — land the plane

Run this before you stop working on a session that touched real tasks. It reconciles the agent-workspace task cards with what this session actually did, so the next session (yours or a teammate's) starts from an accurate state instead of re-deriving it. "Land the plane" = leave the runway clear: nothing half-flipped, nothing undocumented, one clear next step.

Work the checklist top to bottom. Each step is a small, verifiable action — do the work, don't narrate it. Finish with the landing report in step 7.

Paths used throughout: the task CLI is the plugin's ${CLAUDE_PLUGIN_ROOT}/bin/agent-work.sh. It resolves the workspace from AGENT_PROJECT (+ optional AGENT_WORKSPACE_ROOT); without AGENT_PROJECT it falls back to a legacy project-local .claude-workspace/.

AW="${CLAUDE_PLUGIN_ROOT}/bin/agent-work.sh"
WS="${AGENT_WORKSPACE_ROOT:-$HOME/swarmery-workspace}/${AGENT_PROJECT:-}/workspace"
[ -d "$WS" ] || WS="${CLAUDE_PROJECT_DIR:-.}/.claude-workspace"   # legacy layout

1. Identify the task dir(s) this session worked on

Do not guess — cross-check three signals and keep only the intersection.

# a) active tasks the workspace knows about
bash "$AW" list active

# b) newest active task dir (both layouts: dated + flat legacy)
find "$WS/working" -mindepth 5 -maxdepth 5 -name README.md 2>/dev/null
find "$WS/working" -mindepth 2 -maxdepth 2 -name README.md 2>/dev/null

# c) files this session actually touched (activity tracker)
today=$(date +%Y%m%d)
for f in /tmp/claude-session-*-${today}.jsonl /tmp/claude-session-${today}.jsonl; do
  [ -f "$f" ] && jq -r 'select(.file!="") | .file' "$f" 2>/dev/null
done | sort -u

• The canonical task id is yyyy-mm-dd-slug; on disk the leaf folder is just the slug under working/YYYY/MM/DD/. list prints ids; the find gives you dirs.
• Match the touched-files list against what you remember doing this turn. A task that only shows up in list active but you never touched this session → leave it alone.
• If exactly one active task and it's obviously the one you worked on, proceed with it as the primary. If several, decide which is primary (still in-flight, gets the NEXT.md) vs which are done.