5.2 Snapshot lifecycle
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 149
Description
# 5.2 Snapshot lifecycle
**Parent:** Story 5 (#7232)
**Tool file:** `forge/ee/lib/mcp/tools/snapshots.js` (extend)
## Summary
Complete snapshot management. List and create already ship; this adds the read surface (get/full) and the write lifecycle (export, import, edit, set-target) plus deletes. Snapshots span both hosted instances and devices, plus a generic `/snapshots/:id` surface. Deletes are separated from ordinary writes so MCP clients gate them behind confirmation by default.
Contributor guide
Research direction
Start in forge/ee/lib/mcp/tools/snapshots.js and read the existing list and create implementations. Map the requested get/full, export, import, edit, set-target, and delete surfaces across hosted instances, devices, and /snapshots/:id. Done means the read and write lifecycle is covered, with deletes separated for confirmation gating.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100