Read-only Project Recovery

Use relevant native session history, resume, and memory interfaces as secondary evidence, not as the authoritative task backlog. Read current repository guidance, HANDOFF current state/next action/blockers/verification, and the authoritative task list; use TODO.md only as a fallback. Follow existing project conventions and do not invent absent records.

This skill is read-only. Do not create or rewrite project records, instructions, memory, or installed configuration. A request to recover context does not authorize meditation writes. New topics and irrelevant/stale history must not be forced onto the user's current task.

A policy-denied source remains unavailable: do not ask the user to paste, supply, or reupload its contents, or recover them through another channel. Ask only for an independently authorized task goal or next action without restricted content. Modified does not establish staged or unstaged status; keep unobserved worktree details unknown.

Load and follow the project recovery procedure for the selected recovery, worktree-state, or focus case. Count changes with git; privacy-sensitive nudges disclose counts, not filenames. Silence wins during frustration or flow, and unsolicited reminders must be relevant and nonintrusive.

For session/context mechanics use native controls and the session boundary; do not collect cross-session behavioral scores. Missing history/handoff is a named limitation, not evidence that no work exists. Return material state, blockers, next action, and evidence without claiming fresh verification from stale notes.

Delivery-check mode

Load and follow the shared storage and delivery contract to verify the approved task's artifact inventory, final repository files, dependencies, discoverability, ignore state, and actual Git state. Run the read-only session-artifact checker (node <this-skill>/scripts/check-session-artifacts.cjs --repository-root <repo>) to detect deliverables stranded in ~/.copilot/session-state/<id>/files/ for the active repository. Use --session <id> to bound a task-specific check when its session is known. The checker verifies Git-visible copies and supported recovery manifests; ignored copies do not satisfy delivery. Missing/corrupt manifests fail explicitly. Absent sessions, linked paths, unsupported formats, and no matching scope are not reported as clean. Exact-hash pruning decisions in a custody manifest can account for deliberately retired artifacts, not changed source content. This mode is also read-only: report missing delivery rather than relocating, archiving, committing, or activating files without the task's write authority. Recovery should report relevant externally stranded artifacts, not silently promote them or treat missing session history as proof of completeness.

Runtime contract references

Load only the reference selected by the triggering instruction; do not replay all runtime contracts for unrelated work. These references add no authority and do not call the instruction again.

• recovery: session-health-monitoring
• delivery-check: project artifact storage