## 1. Check tools and account identity

Inventory toolkit, account/workspace, state and unverified permissions from the snapshots. Read uploaded files only. Do not install, authorize or request secrets. Save capability.md.

Expected: Two connection records.
Check: ACTIVE is not all tools available; Slack EXPIRED stays visible.

## 2. Make filtering rules testable

Filter the three records by target week and status. Explain every inclusion/exclusion. Do not promote drafts or move R03 into the week.

Expected: Only R01 selected.
Check: All three have outcomes and original statuses remain unchanged.

## 3. Read first, then build the checklist

Write the weekly checklist for R01 with date, title, record id and source scope. State this is a file exercise, not a real Airtable read. Keep missing fields unknown and save checklist.md.

Expected: A one-record local checklist.
Check: The count is 1 and the source remains R01.

## 4. Prepare delivery while retaining the connection blocker

Draft the full Slack message with the checklist and references. Mark EXPIRED and not sent. Do not reconnect, borrow another account or call sending tools. Return the draft and the exact user action needed.

Expected: A draft and clear blocker.
Check: No sent status or fabricated message id.

## 5. Validate live read and send separately

Inspect <Airtable base/table/view> read-only, at most 10 rows. After user reconnects Slack, inspect <workspace/channel> access. Preview final text and target; send once only with explicit approval and return the actual message id. Do not update Airtable.

Expected: Read evidence and delivery status, or a blocker.
Check: Airtable remains unchanged; sending requires a real returned identity.

## 6. Handle reruns and uncertain delivery

Draft a cross-app-checklist Skill with account checks, window/status rules, limits, references, delivery confirmation and deduplication. On uncertain send, read history before retrying. Propose a Routine only; expired access stops delivery and is reported.

Expected: A reusable handoff method.
Check: No repeat message for the same confirmed batch; failure is not no new content.