fleet-coordination

Imported from jaywedgeworth22/AI-Fleet-Coordinator (docs/fleet-skills/by-seat/renoir/fleet-coordination/SKILL.md). Install upstream with npx skills add jaywedgeworth22/AI-Fleet-Coordinator --skill fleet-coordination. Copyright stays with the author.

Fleet Coordination Protocol (Universal)

This install is for RENOIR. Slack [RENOIR]. Notes Renoir. Branches renoir/. Worktrees ~/apps/<app>-renoir. Do not inherit another seat's tag from a shared template.

Inactive seat. Renoir is not yet active. Do not install to ~/.renoir/skills. Do not take fleet work until the owner opens the seat.

Canonical reference: /Users/jay/apps/AGENT-SYNC.md and /Users/jay/apps/EFFORT-LOG-PROTOCOL.md.
Slack Coordination Channel: #agent-sync (C0BEZDJDNKV).

This skill governs how autonomous AI agents collaborate across the entire application fleet (Socratic.Trade, Congress.Trade, Usage-Monitor, congress-trading-shared, DealDex, Personal-Site, Autorotate, ContactLogo, and AI-Fleet-Coordinator).

Canonical Fleet App Acronyms

Use these canonical acronyms in Apple Notes titles ([APP, Agent] topic), commit messages, PRs, and Slack #agent-sync communications:

FLEET is not an app acronym

FLEET is not an application, not a repository, and not this coordinator's name. Do not put FLEET in Apple Notes [APP, Agent] titles as if it were ST/CT/UM.

• App / coordinator acronym for this repo: AFC (ai-fleet-coordinator). Sign Slack as [AFC], never [FLEET], never [GB-FLEET].
• Sibling infra identity: OPS (fleet-ops).
• Slack broadcast wake only: [SENDER->FLEET] means every listening seat on every platform must spend time (Mac seats, BotFleet bots, and any Grok Bot [GB-<NAME>] still listening). Owner 2026-09-13: Grok Bot largely superseded by BotFleet — do not assume a GB seat is listening. Use ->FLEET only when every listener must act.
• Retired coordinator aliases: AFL / FLEET / AIFC / FC as self-id are retired — FLEET especially, because [SEAT->FLEET] is a broadcast wake that costs every seat time.

1. Session Startup & Identity

Every agent session must start with systematic orientation before touching code:

1. Establish Seat Identity:

   • Antigravity / Gemini: [AG] (display AG or Antigravity, branch prefix agent/ or ag/)
   • Monet: [MONET] (display Monet, branch prefix monet/)
   • Claude: [CLAUDE] (display Claude, branch prefix claude/)
   • Grok / Grok Build: [GROK] / [GROK-BUILD] (display Grok / Grok Build, branch prefix grok/ / grok-build/)
   • Cursor: [CURSOR] (display Cursor, branch prefix cursor/)
   • DeepSeek Harness (DSH): [DSH] (display DeepSeek Harness, branch prefix deepseek/). Former Slack tag DEEPSEEK is retired. A DeepSeek model inside Cursor is still [CURSOR].
   • Codex: [CODEX] (display Codex, branch prefix codex/)
   • Grok Bot: [GB-<NAME>] (GB-CONDUCTOR, GB-MONITOR, GB-FIXER, GB-DEPLOYER, GB-COMPILER, GB-NURSE, GB-HOUSEKEEPER, GB-ACCOUNTANT, GB-ORACLE — not [GROK-BOT], not [CURSOR])
   • Fx: [FX] (display Fx, branch prefix fx/)
   • Renoir: [RENOIR] (display Renoir, branch prefix renoir/)
   • MiniMax (MM): [MM] (display MiniMax, branch prefix minimax/). Former Slack tag MINIMAX is retired. (Note: KIMI is permanently retired/unavailable per owner directive 2026-08-21).

2. Poll Coordination Channel:

   AGENT_TAG=<YOUR_TAG> /usr/bin/python3 /Users/jay/apps/agent-sync-poll.py

   Skim for your agent tag or repositories you plan to touch. Every listening seat on every platform also full-reads [SENDER->FLEET] (every listener must spend time). Coordinator self-id is AFC, not FLEET.

3. Check Live Effort Boards & Work Items:

   board stats
   board list --status open,in_progress --limit 25

   Or inspect live board files directly: rg -n "In Progress" /Users/jay/apps/*EFFORT-LOG.md.

4. Fleet recall: recall "<task>" --limit 5 (or MCP recall_search) before re-deriving a lesson. At closeout, recall_contribute every reusable lesson (owner 2026-09-02). Cloud: https://agents.jays.services/mcp. Do not dump chat transcripts into the corpus.

2. Worktree & Lane Isolation

Strict Rule: NEVER work directly in /Users/jay/Code/<Repo> root checkouts. The root checkouts in ~/Code/ are shared review bases and must remain clean on main.

Always work in an isolated worktree under ~/apps/:

git -C /Users/jay/Code/<Repo> worktree add -b <seat>/<feature-slug> ~/apps/<app>-<seat>-<feature-slug>

3. Triple-Claim & Task Lifecycle

Before starting substantial work, reserve your lane across three durable surfaces:

1. Live Effort Board (/Users/jay/apps/<APP>-EFFORT-LOG.md):
   • Add/move your row to In Progress with your tag, branch, worktree, and concise objective.
   • Live boards are branch-neutral and canonical. Mirror your update to docs/EFFORT-LOG.md in the repo before committing.
2. GitHub Issue:
   • Link your branch to the corresponding GitHub Issue or create one.
3. Slack Channel #agent-sync: Post a standardized claim header:

   [<YOUR_TAG>] sync-1
   repo: <RepositoryName>
   claim: <seat>/<feature-slug>
   state: WIP
   work: <One-line summary of task>

(Reserve [<TAG>->FLEET] strictly for urgent wakes that every listening seat on every platform must spend time on. Coordinator/ops posts as [AFC], never as [FLEET].)

4. Secret Safety & The Handoff-File Grep Trap

Handoff File: /Users/jay/.secrets/global-api-keys (no .env extension).
Sole Runtime Truth: Infisical is the source of truth for all deployed app runtime secrets.

Strict Grep Trap Ban (2026-08-14):

NEVER print, cat, grep, rg, or view_file lines matching KEY=value from ~/.secrets/global-api-keys. Doing so dumps raw secrets into transcript logs.

• Inspection (Names only):

  grep -oE '^[A-Z][A-Z0-9_]*' ~/.secrets/global-api-keys | sort -u

  (Or via cloud API: GET https://mac.jays.services/files/key-names with Bearer auth).
• Extraction into single variable (Never echo):

  SECRET_VAL="$(grep -m1 '^TARGET_KEY=' ~/.secrets/global-api-keys | cut -d= -f2- | tr -d '"')"
  # Use $SECRET_VAL directly without echoing or printing

• Infisical CLI: Never run bare infisical secrets or --output json. Use bash scripts/infisical-secrets-safe.sh {set|has|names}.

5. Sentence Gap Protocol (Monet Portable Standard)

Visibly wider gap (two visible spaces) after terminal punctuation (., !, ? when a new sentence follows) in all human-readable prose:

Do not apply after abbreviations (e.g., v1.2.3) or in URLs/identifiers.

6. Apple Notes Review Standard

All plans, design docs, rollouts, audits, and completion notes for owner review must be created in Apple Notes:

1. Folder: folder Coding (local folder on this Mac, intentionally non-iCloud).
2. Title Format: [APP, Agent] Short topic (e.g. [ST, AG] Market data cascade). App acronyms FIRST, agent name in Title Case, NO date in title.
3. Second Line: Timestamp Day, Mon D, h:mmam|pm · PR #<num>.
4. Helper Script:

   /Users/jay/apps/apple-notes-coding.sh "Title" "HTML or markdown body"
   # To update in place:
   /Users/jay/apps/apple-notes-coding.sh --update "Title" "Updated body"

7. PR Landing & Verification Loop

Follow the "Always Commit + Land Finished Work" discipline:

1. Merge origin/main & Verify Locally:
   • Socratic.Trade: PATH=/opt/homebrew/opt/node@24/bin:$PATH npm run verify / bash scripts/land.sh
   • Congress.Trade: cd app && npm run typecheck && npm test
   • Usage Monitor: npm run verify
   • congress-trading-shared: npm run typecheck && npm test && npm run build
   • DealDex: npm run lint && npm run typecheck && npm test && npm run build
2. Push Branch & Open PR:

   git push -u origin HEAD
   gh pr create --fill

3. Arm Auto-Merge:

   gh pr merge <PR_NUMBER> --squash --auto

4. Unsticking Blocked PRs:
   • Test mergeability: git merge-tree --write-tree origin/main origin/<branch>.
   • If exit 0 (Phantom conflict): Rebase/merge origin/main and push fresh head.
   • If bot threads blocking: Check GraphQL reviewThreads, address genuine issues, and resolve threads.

8. Deployment Verification & Closeout

Once PR merges to main:

1. Verify Production Deploy:
   • Check public health: curl -s https://socratictrade.com/api/health, curl -s https://congress.trade/api/health, curl -s https://usage.jays.services/api/health.
   • Confirm HTTP 200 and expected build.sha.
2. Triple Closeout:
   • Effort board: Update row to Deployed (or Completed) with live verification note.
   • GitHub Issue: Close issue.
   • Slack #agent-sync: Post [<YOUR_TAG>] closeout with deployed status and health check results.
   • Apple Note: Add final verification stamp.

9. Mac Local Processes Registry

If you create, change, load, bootout, or retire a LaunchAgent, cron job, pm2 process, or shared helper script:

• Update /Users/jay/apps/MAC-LOCAL-PROCESSES.md.
• Update Apple Note: apple-notes-coding.sh --update "⭐️ Background Jobs Master List".