SVG Muscle Tracing - $30 Test, $150 Max

IMPORTANT BUDGET / TEST CLARIFICATION:
This is not a $250 job. Freelancer shows a preset range, but the actual structure is:
- $30 paid test milestone first
- $120 continuation only if the paid test passes QA
- $150 maximum total
Please do not bid above $150 total.

PRE-AWARD PROOF REQUIRED, NOT A FULL UNPAID TEST:
Before award, I need one tiny proof of competence: a screenshot or SVG snippet showing one single muscle region, or a small portion of one region, highlighted/traced over the provided PNG with clean edge intent. Do not complete the full 4-path paid test before award. The proof is only to verify that you understand the image, region boundaries, clean edges, and that this is not random clipart or a generic redraw. The paid $30 test remains the four exact production paths listed below.

CRITICAL INTERACTIVE OVERLAY CLARIFICATION:
This project is for an interactive app tap/selection overlay. The colored anatomical PNGs are the visual source of truth and must remain unchanged. The SVG paths are the invisible/selectable geometry and highlight regions that sit over those PNGs.

Each listed muscle ID must be its own separate closed SVG path/region. Each path must be independently tappable/highlightable in the app. Do not create one full-body overlay, one merged muscle layer, a whole-body outline, generic black line art, or a redrawn anatomy image.

For example, left/right regions must be separate IDs/paths. A glutes example would be back.glutes.screenLeft and back.glutes.screenRight as two separate closed paths. Hamstrings, quads, lats, pecs, calves, arms, etc. follow the same rule: one listed ID = one selectable path.

Do not add visible text labels, do not color the whole body, do not merge multiple IDs into one shape, and do not include background/grid/body areas outside the requested muscle. The selected/highlighted color should only overlay the exact requested region. Clean edges and non-overlap are required so tap mechanics stay true.

If I send visual examples in chat, they are old rough internal examples only. Use them to understand the intended app behavior, not as exact shapes to copy. For any pre-award proof, pick one listed muscle ID and show one clean closed highlighted/traced region over the provided PNG, and tell me the exact ID represented.

GOAL:
Create developer-ready SVG region paths over two existing 640x1024 anatomical PNGs: one front view and one back view. This is NOT a new illustration. Do not repaint, redraw, recolor, dim, stylize, or modify the base PNGs. The PNGs are the visual source of truth.

REGION SCOPE:
Trace the outer selectable colored muscle region for each requested ID. Do not trace every internal fiber/striated line inside the muscles as separate paths. Internal texture/detail lines stay in the PNG only. Only trace an internal boundary when it is the visible edge between two requested muscle regions.

DELIVERABLE FORMAT:
One SVG file with viewBox="0 0 640 1024". Use two top-level groups:
- <g id="front" data-view="front"> contains the front PNG reference image and all front paths.
- <g id="back" data-view="back"> contains the back PNG reference image and all back paths.

Both groups use the same 0,0,640,1024 coordinate space. Do not place the front/back views side-by-side. Do not scale or transform either image. The app will show one view at a time.

Each muscle region must be its own separate closed SVG Bezier <path> with the exact ID listed below. No transforms, clipping masks, SVG masks, rectangles, rough polygon blobs, merged bilateral shapes, or auto-trace artifacts.

PAID TEST FIRST - TRACE ONLY THESE 4 PATHS FOR THE $30 TEST:
- front.pec.major.screenLeft
- front.pec.major.screenRight
- back.latissimus_dorsi.screenLeft
- back.latissimus_dorsi.screenRight

FULL PATH ID LIST AFTER TEST PASSES:
Front:
- front.pec.major.screenLeft
- front.pec.major.screenRight
- front.deltoid.anterior.screenLeft
- front.deltoid.anterior.screenRight
- front.biceps.screenLeft
- front.biceps.screenRight
- front.forearm.flexors.screenLeft
- front.forearm.flexors.screenRight
- front.rectus_abdominis.upper
- front.rectus_abdominis.lower
- front.obliques.screenLeft
- front.obliques.screenRight
- front.quads.screenLeft
- front.quads.screenRight
- front.adductors.screenLeft
- front.adductors.screenRight
- front.calves.screenLeft
- front.calves.screenRight

Back:
- back.trapezius.upper.screenLeft
- back.trapezius.upper.screenRight
- back.upper_back.screenLeft
- back.upper_back.screenRight
- back.latissimus_dorsi.screenLeft
- back.latissimus_dorsi.screenRight
- back.deltoid.posterior.screenLeft
- back.deltoid.posterior.screenRight
- back.triceps.screenLeft
- back.triceps.screenRight
- back.forearm.extensors.screenLeft
- back.forearm.extensors.screenRight
- back.erector_spinae.screenLeft
- back.erector_spinae.screenRight
- back.glutes.screenLeft
- back.glutes.screenRight
- back.hamstrings.screenLeft
- back.hamstrings.screenRight
- back.calves.screenLeft
- back.calves.screenRight

MAPPING / NAMING RULES:
- screenLeft and screenRight mean the viewer's left/right on the PNG.
- Front view screen-left is anatomical right.
- Back view screen-left is anatomical left.
- Trace the visible muscle region matching each ID.
- If a boundary is ambiguous, follow the visible color/anatomical boundary in the PNG and ask before continuing.
- Do not include background, grid lines, hands, feet, bones, labels, or unrelated areas in any path.

QA / ACCEPTANCE:
- Paths must be closed, valid, clean Bezier geometry.
- Edges should follow the visible boundary at native 640x1024 resolution, target about 1-2 px where the boundary is clear.
- No overlapping selectable muscle regions.
- No obvious visible gaps between adjacent target regions where they touch.
- No rough blobs or blocky polygon approximations.
- Winding order is not critical if paths are valid and fill correctly; clockwise outer paths preferred if possible.
- Base PNGs must remain untouched.
- Final SVG must be parseable as app geometry.
- Full commercial usage rights required.

Attachments include the two PNG references and the brief. If you cannot open the .md brief, open it with TextEdit, Notepad, or a browser, or use the full details above.