docs: fix file format section in CLAUDE.md to match v2 nest format
The documented entries (info.json, drawing-info.json, plate-info.json, plate-NNN) were from the old v1 format. Updated to reflect the actual v2 structure: nest.json, programs/program-N, and bestfits/bestfit-N. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -84,11 +84,9 @@ The UI application with MDI interface.
|
|||||||
## File Format
|
## File Format
|
||||||
|
|
||||||
Nest files (`.nest`, ZIP-based) use v2 JSON format:
|
Nest files (`.nest`, ZIP-based) use v2 JSON format:
|
||||||
- `info.json` — nest metadata and plate defaults
|
- `nest.json` — single JSON file containing all nest metadata: nest info (name, units, customer, dates, notes), plate defaults (size, thickness, quadrant, spacing, material, edge spacing), drawings array (id, name, color, quantity, priority, rotation constraints, material, source), and plates array (id, size, material, edge spacing, parts with drawingId/x/y/rotation)
|
||||||
- `drawing-info.json` — drawing metadata (name, material, quantities, colors)
|
- `programs/program-N` — G-code text for each drawing's cut program (N = drawing id)
|
||||||
- `plate-info.json` — plate metadata (size, material, spacing)
|
- `bestfits/bestfit-N` — JSON array of best-fit pair evaluation results per drawing, keyed by plate size/spacing (optional, only present if best-fit data was computed)
|
||||||
- `program-NNN` — G-code text for each drawing's cut program
|
|
||||||
- `plate-NNN` — G-code text encoding part placements (G00 for position, G65 for sub-program call with rotation)
|
|
||||||
|
|
||||||
## Tool Preferences
|
## Tool Preferences
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user