Closeout (MONET)

Shared ~/.claude/skills. Monet, Claude/Fable, and (when active) Renoir all load this directory. Do not treat the word Monet in examples as proof of your seat. Pin AGENT_SEAT / AGENT_TAG from the logged-in account before Slack or board --by:

• Monet → MONET, Notes Monet, monet/, ~/apps/<app>-monet
• Claude / Fable → CLAUDE, Notes Claude, claude/, ~/apps/<app>-claude
• Renoir → RENOIR, Notes Renoir, renoir/, ~/apps/<app>-renoir Cursor, Grok, Grok Bot, Codex, AG, DeepSeek, Kimi, and Fx have their own skill dirs and must not take identity from here.

Start-of-work is a Linear claim plus Zulip post. End-of-work closes Linear and Zulip plus Notes when the owner might ask "what happened?"

1. Truth check

• Merged to main? (gh pr view / git merge-base --is-ancestor)
• Production verified? (deploy-verify) Completed ≠ Deployed.
• Uncommitted files? Commit or explicitly report why not (failing tests, secrets, owner hold).

2. Linear

board status <id> completed --resolution "Landed in #<PR>.  <one line>."
# or: deployed — only after health verify

Effort logs are archived — do not edit live ~/apps/*-EFFORT-LOG.md or repo docs/EFFORT-LOG.md. A Linear comment is useful context for peers.

3. Linear + GitHub

• Completed = merged to main and reflected on the Linear issue.
• Deployed = released and verified (say how).
• If you executed a numbered GitHub issue, comment or close it so it is not abandoned.
• Cross-app work gets a Linear issue (or explicit comment) on each affected app team.

4. Zulip (#Work-In-Progress)

printf '%s\n' "[$AGENT_SEAT] sync-N
repo: <project>
state: DONE
pr: #<n>
board: <id>
work: <what landed>" > /tmp/sync-note.md && chmod 600 /tmp/sync-note.md
AGENT_SEAT="${AGENT_SEAT:?set MONET, CLAUDE, or RENOIR}" simple-chat post --topic "<project> sync" --body-file /tmp/sync-note.md

Not FLEET for a normal closeout.

5. Apple Notes

Substantial work: living Completion note, --update in place. Title [APP, Monet] short topic. See apple-notes. Cloud sessions: skip Notes, say so, leave the handoff in the PR.

6. Mac local processes

If this unit created, loaded, bootout, or retired a LaunchAgent, cron, login item, pm2 KeepAlive job, or a helper other agents run: add/update a row on /Users/jay/apps/MAC-LOCAL-PROCESSES.md and --update "⭐️ Background Jobs Master List" in the same change. Say always-on vs on-demand. Retire in place; never delete historical rows.

Do not SIGKILL com.jay.claude-remote-control.

7. Default-off features

If you shipped a flag that is off, reserve a Planned enablement row (ST: also docs/FEATURE-ENABLEMENT-BACKLOG.md).

Parked, not done

If you stop without merge: board stays accurate (open or a comment "parked because …"), Slack says BLOCKED/parked, worktree is not dirty with uncommitted finished code. In Progress after you left is how three agents redo the same slice.

Canon

• /Users/jay/apps/FLEET-PROTOCOL.md — triple closeout; Apple Notes; Mac local processes; always-commit
• /Users/jay/apps/EFFORT-LOG-PROTOCOL.md
• Skills: board-ops, apple-notes, deploy-verify, land-lane

Living Handoff Morphing to Closeout

Throughout execution, maintain a brief big-picture outline of task state. When the task is complete, this outline naturally becomes your Closeout Report by:

1. Marking all milestones as completed with commit/PR references.
2. Replacing in-flight WIP notes with live production deployment verification (/api/health 200, build SHA).
3. If closing out work adopted from a peer, posting a direct [<SUB_TAG>-><ORIGINAL_TAG>] notification to #Work-In-Progress.