Pelican on a bicycle · hy4

We need build index.html self-contained, inline SVG pelican bicycle. Need use browser inspect initial output console and representative checks. Need likely make high quality illustration. Need carefully design SVG with paths. Need verify with screenshot. Need understand browser tool capabilities. We can write file then browser reload/screenshot/inspect. Need fit viewport 1200x800. Need complete subject visible responsive. Need no external resources. Need accessible title/desc. Need likely provide CSS style and perhaps JS optional—not needed. But add inline JS maybe set dynamic? User says as needed, animation controls not required. Could just CSS and SVG. Need make compelling.

Let's plan geometry in a viewBox 0 0 1200 800 perhaps illustration nicely centered. Need bicycle recognizable: two wheels at (330,590) and (870,590), radius 150 maybe. Frame connected: rear hub A=(330,590), front hub B=(870,590), bottom bracket C=(590,590), seat tube top S=(530,390), head tube top H=(810,390), lower H2=(835,450). Bike frame triangles:
- rear triangle: A-C, C-S, S-A
- front triangle: S-H or S-H2, H2-C, C-S.
- top tube S=(510,390) to H=(800,390)
- down tube H2=(810,455) to C=(590,590)
- seat tube S=(530,390) to C=(590,590)
- chain stay C to A.
- seat stay S to A.
- fork H=(800,390?) through head tube to B=(870,590). Need head tube around (805,390)-(835,460), fork from (820,440) to B 870,590. Handlebar extending above/backward: from head tube top (810,380) stem to (760,345), then curved handlebars to (700,320?) maybe, perhaps pelican wing reaches it. Need choose rider pose.

Pelican body positioned above saddle around (530,360) and leaning forward toward handlebars at (760,330). Pelican should have recognizable long bill + pouch, wings, feet near pedals. Need a plausible riding pose. We need design a large pelican body, neck/head/bill. Body maybe oval from (430,280) to (640,475), with saddle at (515,380). Pelican sits on saddle at lower body around (515,400). Body oriented right; head/neck rises to around (650,210), long beak points right to (930,245), pouch hanging beneath. Pelican wing reaching forward to handlebar around (750,340). Legs from body down to pedals around bottom bracket (590,590): crank arms perhaps from C=(590,590), pedals at (630,625) and (550,555). Feet near those pedals. Need pose credible with one or both legs from lower body to pedals. Could have legs:
- rear/left leg from hip (505,425) down/back along (540,500) to knee (560,520), then foot to pedal (550,555), colored orange.
- front/right leg from hip (560,430) down to knee (625,500) then foot to pedal (630,625). Need these visually near pedals. Need two pedal crank lines from center C to pedal positions. Need maybe one foot on each.
Need ensure bird attached to bike: lower body overlaps saddle; perhaps saddle under body at y=405; wing tip wraps handlebar grip; feet contact pedals. Saddle maybe at (500,390) with seat post from C/S. Need avoid layering confusion.

Need think composition and style. Could use a warm sky / setting sun / horizon and ground shadow; shapes only. Could use SVG gradients? Inline defs gradients fine. Background perhaps pale aqua sky with large sun circle, stylized cloud paths, dunes / sea, line pattern. Main art bold outlines. Need not overcomplicate but clear. Need use SVG shapes and paths only, no image. Need viewBox and responsive sizing. Maybe CSS center card with SVG width min(100vw, ...) height auto. Since browser viewport 1200x800, perhaps SVG aspect 3:2, use width:min(100vw,1200px); height:auto; max-height:100vh; object fit. Need ensure full subject visible. Could include a border / caption? Main content should be inline SVG. Could have header text? Better just a centered SVG with all art. Use body background that matches SVG cream. Need title and desc within SVG, role img aria-labelledby. Might include labels? Not needed, but could add small visual annotation? No.

Let's map precise coordinates and layer order.

Canvas viewBox="0 0 1200 800", perhaps full viewport aspect 1.5. Bicycle centers at y=590, r=145: extents x=185..1015, y=445..735. Ground at y=735. Rider head/beak extends up to y~120 and right to x~1010, perhaps within. Need subject complete. Background sun at (910,170) r=110 maybe behind bill; could interfere. Maybe sun at (170,150) to avoid. Pelican beak from head x=680 y=220 to x=1000 y=250; fits. Need beak and pouch recognizable. Pelican head perhaps white / cream. Body pear-shaped white with black primary feathers. Neck curved S shape rising from body to head. Beak long, yellow/orange, long upper mandible and huge pouch underneath.

Detailed pelican anatomy:
- Pelican body: large white oval / pear from roughly (390,270) to (640,460). Tail feathers to left. Sitting leaning forward? Body perhaps angled -20 degrees? Need saddle at x=520,y=405; body lower edge perhaps y=440, so overlap. Body center (515,360), radius horizontal 145, vertical 115. Neck extends from shoulder at (590,290) up/right to head at (680,185). Head maybe circle-ish at (700,180), crown to y=145. Long beak starts at (735,190) and runs to (1010,225), upper line, tip down; lower pouch from (735,205) curving down to (880,300), then back to (1010,225). Need large throat pouch distinctive. But if beak points right and pouch hangs below as orange/yellow shape, this reads pelican. A pelican's pouch is attached along lower bill from base to tip, often triangular deep bag. Upper bill can be long pale yellow narrow shape, with lower pouch broad orange area. Need maybe pouch starts x=735,y=205, curves C790,230 880,315 1005,235, L735,215. Add shading / inner curve. Head maybe white with yellow crown, black eye.

Need perhaps head at (660,185), bill base (710,198), tip (1020,250). Pouch extends to y=315. Need neck from body top right (610,300) to (635,210) and head (660,150), maybe curved S. Could draw a white thick path with dark outline:
M 570 320
C 610 295, 595 235, 620 195
C 640 160, 690 145, 710 180
C 725 205, 700 225, 675 220
C 650 215, 655 260, 635 290
C 620 320, 600 330, 570 320 Z
But need head and neck integrated. Perhaps separate neck path with fill white and stroke:
M 570,320 C 615,315 600,255 625,215 C 640,185 660,165 685,165 C 715,165 735,190 730,210 C 725,230 700,235 680,225 C 665,217 665,250 650,280 C 635,315 610,340 570,335 Z
Then head circle/ellipse at (685,190) rx=55 ry=45. But neck plus head overlap. Need perhaps body behind neck.

Beak upper mandible path:
M 720 190
C 800 180 910 195 1020 225
C 1025 227 1025 234 1018 236
C 910 220 800 210 725 210
C 715 207 715 192 720 190 Z
This might be narrow and tapered. Better exact pelican bill: long straight upper bill, slight point hook. Base around x=720 y=190-212, tip x=1015 y=230. Path:
M 720 190 C 820 185 930 200 1015 225 Q 1025 228 1018 235 L 1012 239 C 910 218 810 207 720 210 Q 710 203 720 190 Z.
But lower edge perhaps a line. Pouch shape:
M 720 210
C 770 220 850 300 930 295
C 975 290 1000 255 1018 235
C 920 215 810 205 720 210 Z
This gives deep hanging pouch around y=310, triangular. Need integrate with lower bill (orange). Use fill gold/coral, stroke brown. Add inner curve/shading to show pouch: M745 218 C790 245 845 280 915 280 C950 278 980 255 1005 236 maybe; and vertical pouch crease lines. Could include small fish? No.

Need ensure beak doesn't overlap handlebar? Handlebar around x=760,y=340; pouch down to y=300, fine. Wing can reach from body around (570,330) toward handlebar at (760,350), maybe a long white wing/arm with feather tip. Need one obvious contact near handlebars. Draw wing as elongated path from shoulder (~560,325) to grip (~760,335), perhaps:
M 540 315
C 585 290 650 300 705 318
C 735 328 760 330 775 340
C 780 350 770 360 750 355
C 710 345 660 360 615 385
C 580 405 545 385 530 350 Z
But need wing end at handlebar grip around (750,350), perhaps feathers curling around. Could show three primary feather tips at end. Or a distinct "wing hand" contact. Since birds don't have hands, wing tip near handlebar enough; perhaps draw wingtip feathers wrapping grip with small orange? White feathers. Need clearly contact around handlebars. Handlebar grip at x=740? Let's define handlebar geometry carefully.

Bicycle frame:
Wheels center rear=(320,600), front=(880,600), radius=145. Need preserve space for pelican beak to x=1020 y=220. Bike front handlebar maybe at x=800,y=360, which is under pouch maybe. Head tube goes from (790,390) to (820,455). Stem to (760,355). Handlebar extends from (760,355) to (710,330) (backwards/up), grip perhaps from x=690 to 730 y=325. Typical handlebar: stem from head tube top to x=770 y=350; bar curves up/back to x=720 y=320, then grip segment x=680-720. We can draw thick dark stroke with round caps:
M 800 385 L 765 350
C 750 335 735 325 715 325
L 685 325
Maybe handlebars if side view: a curved bar extending left/up from stem, grip at left end. Then wing tip reaches (700,325). Need perhaps place contact at (700,325). Pelican body shoulder around (560,310), wing can extend right to (700,330). Good. Need handlebar visible beyond pouch: pouch extends x=720..1018 y=210..300, so bar at y=325 just below, visible. Wing path from x=560,y=320 to x=690,y=325 can touch grip. Need maybe handlebar with bright coral grip and wing tip overlapping at x=690. Need avoid birds' body covering all frame. Body lower edge y=440; seat tube etc from y=400 to 590 partially behind body. That's okay if saddle/body overlap. Layer order: background, sun/clouds/ground, rear wheel? Wheels and frame maybe behind rider, then frame, then legs/body etc. Need bicycle geometry connected visually. If body covers central parts, still recognizable via wheels and exposed frame triangles. Need draw frame strokes with e.g. teal 14px, dark outline 18px behind. Could draw all frame lines as dark under-stroke and teal top stroke. Need precise connected endpoints.

Potential issue: two wheels behind frame but spokes should be visible; use circles and spokes. Wheels: outer tire dark navy thick stroke, inner rim thin light. Spokes lines from hub to 12 points. Could use <g> for each wheel and duplicate with transform or <defs><g id="wheel"> then <use>. But user says main artwork consists of inline SVG shapes and paths; use is okay maybe but to avoid any interpretation, draw explicit circles/lines for each wheel. Could use JavaScript to generate spokes, but static SVG shapes preferable. Could utilize a <pattern>? No. We can use many <line> elements. 12 or 16 spokes each wheel. Could create with JS at runtime? But then screenshot maybe works, but static is more robust. Need write maybe 24 line elements. Fine.

Wheel geometry:
- Outer tire circle r=145 fill="none" stroke="#17324d" stroke-width="18"
- Rim circle r=127 fill="none" stroke="#e7f3f0" stroke-width="7" plus maybe dark thin.
- inner tire aqua highlight? Maybe outer stroke with coral dash? Could add rim stroke.
- spokes from center to points on r=123 at angles 0, 22.5, etc. Need calculate. Could programmatically generate via JS inserted into <g id="spokes"> to reduce code, but that creates inline shapes at runtime. Yet requirement no network, fine. But if browser runs JS, works. However static is easier maybe with a path containing multiple M/L commands. A single `<path d="M320 600 L465 600 M320 600 L434 653 ...">` etc. Path qualifies. Could define wheel spoke set with <path> using exact coordinate pairs. Use transform translate? We can define one path around origin then `<use>`? Actually could use `transform="translate(320 600)"`, path d="M0 0 L123 0 ...". Then duplicate second with transform. Use `id` in defs and `<use href="#spoke-set">`; no external resources. But perhaps "shapes and paths embedded" still yes. Better explicit each group with `<path>` and transform.
Compute 16 radial endpoints on r=126:
angle 0: (126,0)
22.5: (116.4,48.2)
45: (89.1,89.1)
67.5: (48.2,116.4)
90: (0,126)
112.5: (-48.2,116.4)
135: (-89.1,89.1)
157.5: (-116.4,48.2)
180: (-126,0)
202.5: (-116.4,-48.2)
225: (-89.1,-89.1)
247.5: (-48.2,-116.4)
270: (0,-126)
292.5: (48.2,-116.4)
315: (89.1,-89.1)
337.5: (116.4,-48.2)
Need path with M0 0 L... repeated. Fine. Add hubs circles.

Ground line at y=745, wheel bottom y=745 exactly. Need stroke of tire extends to 754 maybe; perhaps set y=585 r=145 + stroke 10 = 739, ground y=740. Let's use centers y=585, r=140, tire stroke width=16 => extends to 733. Ground y=735. Pelican head top y=120, beak x=1020. All within viewBox. Let's settle:
Rear hub R=(320,585), front hub F=(880,585), radius=140.
Bottom bracket B=(590,585) (same horizontal y as hubs; typical bottom bracket slightly above hub centers maybe y=570? Actually cranks at y=585, hubs on same level. Fine.)
Seat tube top S=(520,390)
Head tube top T=(800,380), bottom U=(825,445)
Frame:
seat tube S-B (520,390 to 590,585)
top tube S-T (520,390 to 800,380)
down tube U-B (825,445 to 590,585)
chain stay R-B (320,585 to 590,585)
seat stay R-S (320,585 to 520,390)
front fork U-F? from U=(825,445) to F=(880,585), plus perhaps head tube T-U.
Need head tube itself perhaps a thick slanted capsule from (790,365) to (830,455). A dark navy/teal thick stroke. Fork line U-F perhaps two parallel lines for fork blades: from (818,438) to (865,585) and (832,438) to (895,585) perhaps center F? Need not too complex. Simpler thick line from (820,440) to (880,585), maybe dark outline and mint inner stroke. But center should meet front hub. Need connected. Frame diamond visible. Typical frame:
- top tube from seat top (520,390) to head top (800,390)
- down tube from (800,390) to bottom bracket (590,585)
- seat tube from S to B
- chain stay from B to R
- seat stay from S to R
- fork from head top at (800,390) to F (880,585), maybe via head tube.
Could use T=(800,390) and draw fork from (815,430) to F. Head tube from (790,370) to (820,440). Down tube from (815,430) to B. Top tube end at (795,385). Handlebar stem from (790,370) to (755,335). Clear.

Crank:
bottom bracket circle at B=(590,585), radius 19 dark, inner gold.
Crank arms dynamic positions: one to pedal P1=(630,625) (down-right), another to P2=(550,545) (up-left). Need pedal positions separated 180°: vector (40,40), other (-40,-40). Draw thick dark lines B-P1 and B-P2. Pedals as horizontal little rounded rectangles around P1 and P2: at P1 center x=630,y=625, rect x=605 y=618 width=55 height=12; at P2 center x=550,y=545 rect x=525 y=538 width=55 height=12. But feet need near/on pedals. Need draw bird legs after frame maybe overlapping pedal. Could place orange webbed feet on top of pedals with toes wrapping. Determine legs:
- Near/front leg from hip around (565,425) to knee (620,500), then ankle (625,610), foot on P1=(630,625). Use orange stroke width 22, round caps/joins, maybe dark outline under-stroke width 28 then orange 18. Need maybe bird legs are scaly / thin but pelican legs are short. Since saddle y=390 and pedal y=625 difference 235, need long legs—cartoon pelican can have long legs. Perhaps start lower body at (550,425). Path M550 420 C580 455 615 475 610 515 C605 550 625 580 630 615. Need look plausible. Could show knee bend clearly: M540 420 C570 455 620 470 625 510 C630 550 620 590 630 615. But overly squiggly. Use straight segments with angled knee: M550 420 L625 500 L630 615. This is long and bent. Pelican leg maybe orange, with dark outline. Near foot on down-right pedal: webbed foot shape around (630,620) extends right and left. Need perhaps toe shapes.
- Far leg from hip (500,425) to knee (485,500) to (550,545) (upper-left pedal); path M500 420 L480 500 L550 545. But leg crosses frame / maybe okay. Both feet near pedals. Could draw far leg slightly darker orange and thinner behind frame; but frame should likely be on top? Need layering:
  1 wheels
  2 frame
  3 far leg perhaps behind frame? Actually bird sits on bike and legs in front of frame. Could draw frame first, then legs, then body and wing, then crank/pedals maybe pedals should be under feet but visible. If feet drawn after pedals, they cover pedal details; draw crank and pedals before feet/legs? Need feet contact clearly. Sequence: wheels/spokes, frame, crank arms/pedals, far leg, near leg, tail/body/neck/head/bill/wing/saddle? Saddle should perhaps be between bicycle and body. Need saddle drawn after frame but before body, so body overlaps. Legs are attached under body; can draw after body or before body. If legs before body, hip origins hidden by body. Draw far leg, near leg, then body overlays top endpoints; feet remain. But pedals drawn before legs, so feet overlap pedals. Good. Yet crank arms need visible; legs might cross but fine.
  - Wheels + spokes.
  - frame.
  - saddle (at y~390).
  - crank/pedals.
  - far and near legs (with feet).
  - tail / body / wing? If body after legs hides upper legs, good.
  - neck/head/beak.
  - wing reaching handlebar should perhaps draw after body and after handlebar. Handlebar is part of frame; if wing drawn after, contact looks overlapped. Need maybe draw handlebar grip after wing to show wing wraps? Could draw handlebars before wing, then small feather tips around grip after. Fine.
  - maybe saddle after body? Actually body should cover saddle partially, but saddle nose and rear visible. Draw saddle before body, then maybe a small visible seat outline under body. Body lower edge around y=440, saddle at y=405; if body filled to y=440, saddle would be entirely hidden. Need body position adapted: body lower edge maybe y=405 around saddle, and body "rests" on seat. If saddle y=400, body lower edge at y=415, overlap 15 px. Seat extends x=470..570; body could have lower contour at y=415 from x=430..600. Then seat mostly hidden. Need perhaps draw saddle on top of body lower edge, showing a horizontal dark seat under rump. But anatomically saddle should be under the bird. Could draw body first, then saddle around y=420, maybe overlapping just lower edge; this gives clear contact. Seat post from S=(520,390) to B; saddle perhaps sits at y=390, but body lower edge y=425. Maybe seat post top could be at y=420 and seat tube top S=(520,420), not 390. Let's rethink bike geometry relative to rider.

Traditional bike: wheel radius 140, hubs y=585; frame seat top S y=390 (195 above hubs), saddle y=370. A pelican body center y=320, lower edge y=420, so saddle at y=400. Fine. Seat tube top S=(525,405), saddle surface y=390. Body lower contour around y=410. Draw body first, then saddle on top at y=400 with a dark shape partially covering body bottom—looks like bird sitting on it. Seat post from S=(525,405) down to B. Top tube from S to head. Need rest of frame adjust. Let's set:
R=(320,585), F=(880,585), B=(590,585)
S=(525,400)
T=(795,390)
U=(820,450)
Frame:
seat tube S-B
top tube S-T
down tube U-B
seat stay R-S
chain stay R-B
head tube T-U (short diagonal)
fork U-F
Handlebar stem from T=(795,390) to (755,350), then bar to (700,325).

Saddle at y=390: `path d="M470 390 Q500 375 550 384 Q570 386 575 395 Q540 405 490 402 Q470 400 470 390 Z"` dark navy with coral highlight. Body lower edge maybe around y=400 from x=460..590. Draw saddle on top after body to show contact? If saddle drawn after body, it covers lower body, okay. Need seat post visible below. The saddle could be around x=470..575 and body is from x=400..640, so visible. Good.

Body shape perhaps pear/oval angled forward:
M 430 275
C 500 235 600 260 635 325
C 665 380 630 420 570 420
C 500 425 440 400 410 350
C 390 315 400 290 430 275 Z
This leaves lower edge x~440..600 around y=410. Saddle overlays around x=470..575 y=390. Bird clearly sitting. Tail feathers extend left to x=350,y=330 and x=380,y=390. Body perhaps cream/white with outline dark navy. Wing on body can be a separate folded wing shape from x=440,y=295 to x=610,y=380 with feathers, maybe gray/blue shading. But we also need a wing reaching handlebar. Could draw two wings: one folded on body (far wing) and one extended (near wing). This makes recognizable. Need avoid confusing. Extended wing from shoulder around (585,310) to handlebar at (700,325):
M 575 300
C 620 285 660 295 695 315
C 710 323 720 325 720 335
C 718 345 705 347 690 340
C 660 330 630 350 605 375
C 585 395 555 370 560 335
C 562 318 568 306 575 300 Z
Need actually reach x=700,y=325 where grip is. Handlebar grip might be at x=690-730 y=325, so wing overlays it. Need point of contact highlighted: perhaps wingtip feathers drawn around grip at x=700,y=325, e.g. three small curved feathers wrapping bar. Use path(s):
M 690 318 C 705 313 720 318 725 328 C 715 340 700 340 690 330
and dark line. Maybe enough.
Need perhaps wing is an "arm" and wingtip at handlebar; make it lighter with blue-gray feather separations. Draw extended wing after handlebars, with dark outline; its rightmost tip x=710,y=330 covers grip. Add three feather tips ending around x=705..725 y=330; clear contact.

Folded wing on body:
M 445 295 C 490 275 550 290 590 330 C 610 350 600 385 575 400 C 530 390 475 370 445 335 Z
fill pale blue-gray, stroke dark. Add three feather curves. But extended wing might overlap folded wing. Maybe folded wing is the far wing and extended near wing starts at (570,315). Could draw one large folded wing that extends to handlebar—perhaps no need second. But requirement wings plural? "body, wings, and feet" perhaps should show wings. Better show both: a visible folded wing on left/body and one extended right wing. Need careful layering.

Maybe body shape angled and neck arises right. Tail feathers left. Folded wing drawn on left side with dark primary tips at bottom. Extended wing drawn from shoulder (570,300) to handlebar. Could look like two wings (one reaching, one folded). Fine.

Pelican color palette:
- outline dark navy #17324d, stroke widths 5-7.
- body warm white #fff9e9 / cream; shadow #e3eef0.
- wing pale teal #c9e3e1 with dark navy feather tips #2d526d.
- beak upper #ffd166 / gold, lower pouch #f28c5a / coral with gradient; perhaps `<linearGradient id="pouchGrad">`.
- legs and feet #e9943a orange, dark outlines.
- bike frame teal #28a6a0 or coral #e75a5a? Need contrast with peach pouch. Maybe bicycle deep teal with coral accents. Frame dark outline plus teal inner. Could use thick strokes with round joins.
- tires dark navy, rims cream/mint.
- background sky pale #d9f3f2, sun #ffe3a3 at (170,160), clouds white, distant sea/waves, ground #f5d99d with dark line. Need keep uncluttered. Maybe no JS needed, but could add JavaScript to add a tiny interaction? Not required. Add inline `<script>` with perhaps `document.documentElement...` not needed. Since user says HTML, CSS, JS as needed, static CSS and SVG fine. Could include JS to set current year or no. Better no unnecessary script. But add perhaps a script that assigns `data-ready="true"` after DOM content loaded for verification? Not needed. Could include a small JS that handles responsive viewport? CSS enough. Need likely browser tool checks "console" maybe no errors. No script means no console errors. Good.

Need maybe use `<svg role="img" aria-labelledby="artTitle artDesc">` with `<title id="artTitle">Pelican riding a bicycle</title>` and `<desc id="artDesc">...`. Need perhaps a visible heading? Could add `<h1>` but main content SVG. Maybe accessible description enough. Could have a small subtitle in the SVG as `<text>`? Text is SVG shape-ish, okay, but not needed. Could include a banner caption "PELICAN ON WHEELS" perhaps stylistic. But may distract and need no external fonts. Use generic sans-serif. Could add title ribbon at top? Better focus on illustration.

Need robust responsive sizing:
```
html, body { height:100%; margin:0; }
body { display:grid; place-items:center; background:#bde8e5; padding:clamp(8px,2vw,24px); }
.artwork { width:min(100%, 1200px); max-height:100vh; aspect-ratio:3/2; box-shadow...; border-radius:24px; overflow:hidden; }
svg { display:block; width:100%; height:100%; }
```
If width 1200 and height auto 800, body padding might make total > viewport 800, so use:
```
.frame { width: min(100vw, calc(100vh * 1.5), 1200px); aspect-ratio: 3/2; }
```
Need support CSS `min(100vw, 150vh, 1200px)`? `calc(100vh * 1.5)` valid maybe multiplication not broadly supported? CSS calc can multiply? Modern CSS supports `calc(100vh * 1.5)`? CSS values multiplication is newer; better `min(100vw, 150vh, 1200px)`—150vh is 1.5*vh and valid. `width: min(100vw, 150vh, 1200px);` then `aspect-ratio:3/2; max-height:100vh;`. Use `svg { width:100%; height:auto; }`; frame can have border radius and overflow hidden. If body padding absent, fits exact viewport. Perhaps body `padding:0`. For 1200x800 viewport, frame width=min(1200,1200,1200)=1200, height=800, exact. At other aspect ratio, width constrained by 150vh, height=100vh; fits. Could also use `width:min(100vw, 150vh, 1200px)` and `svg{width:100%;height:auto;aspect-ratio:3/2}`. Add body background matching maybe. Need include no scrollbars. Fine.
Maybe use `@media` to adjust border-radius; not necessary.

Need perhaps add subtle shadow under bicycle via ellipse at ground y=738. Wheels bottom around y=733, ellipse y=735. Ground line etc.

Need think layering and paths exact. Let's draft full SVG with defs:
- linearGradient skyGrad from #c9edf0 to #fdf0cf maybe.
- radialGradient sunGlow? Might be okay.
- linearGradient pouchGrad from top #ffd46b to bottom #f28a58.
- linearGradient bodyGrad #fffdf2 to #e7f2ee.
- maybe filter drop shadow? SVG filter okay but can be heavy; avoid.
- maybe patterns for spokes? no.
- `<clipPath>` not needed.
- maybe use `<style>` in SVG? CSS in head already can style. Could define classes via CSS to simplify. Use classes like `.ink`, `.frame-shadow`, `.frame`, `.spoke` etc. Need CSS in `<style>` tag. All inline. Good.

Potential problem with CSS `.frame-outline` could conflict with HTML `.frame`; use distinct names. Need ensure SVG stroke attributes works. Could use CSS classes:
```
.outline { stroke:#17324d; stroke-linecap:round; stroke-linejoin:round; }
.spokes { stroke:#90b4b5; stroke-width:2; opacity:.7; }
.frame-under { fill:none; stroke:#17324d; stroke-width:19; ...}
.frame-color { fill:none; stroke:#2b9fa2; stroke-width:11; ...}
```
But if multiple lines in a path with different segments, okay.
Need make frame connected: draw a single `<path class="bike-outline" d="M320 585 L590 585 L525 400 L320 585 M525 400 L795 390 M820 450 L590 585 M795 390 L820 450 M820 450 L880 585" />` and then duplicate same path colored. This gives all connected lines with joins. But crossing geometry partly. Need perhaps add head tube as separate thick line. Need ensure top tube end at 795,390; head tube from 795,390 to 820,450; down tube from 820,450 to B. Fork from 820,450 to F; all connected. Good. Need separate rear triangle chain stay/seat stay etc. `M320 585 L590 585 L525 400 L320 585` draws closed rear triangle. Then top tube from 525,400 to 795,390. Then down tube from 820,450 to 590,585. Need also maybe link 795,390 to 820,450. Fine. Use two same paths with stroke. Need perhaps chain stay from R to B and seat tube S to B; yes. Need maybe front triangle missing S-B? It's in rear triangle path. Good. Need head tube/fork separately maybe same path. Need outline on all. Could ensure frame color doesn't cover spokes too much; okay.

Handlebar:
```
<path d="M795 376 L760 345 C748 334 736 326 718 326 L690 326" class="bar-outline"/>
<path ... class="bar"/>
<rect x=676 y=316 width=45 height=18 rx=9 fill="#f26b5b" stroke...>
```
Stem perhaps from (795,376), curve to (760,345), bar to (690,326). T is (795,390), so start at (795,376) maybe head tube upper. Need connect visually. We could use start (792,385), line (760,350), curve (740,320) to (715,325), then line (680,325). A typical drop bar maybe U shape:
`M795 385 L760 348 Q740 315 710 325 L680 325` with grip at x=680..710. Fine.
Could add brake lever line from (720,325) to (700,355), dark. Need contact wing at grip x=690..715 y=325. Good.

Saddle:
seat post from S=(525,400) perhaps to (525,385) and saddle around y=380. Need body lower edge ~410; if saddle y=390 and drawn after body maybe visible. Maybe saddle at y=405? Let's set seat tube top S=(525,405) rather than 400. This shifts frame slightly. Let's settle exact numbers:
R=(320,585), F=(880,585), B=(590,585), S=(525,405), T=(795,390), U=(820,450). Seat post from S=(525,405) to (525,382) maybe saddle centered y=382. Body lower edge ~420, so saddle would be covered if body drawn after saddle. But draw saddle after body, could show dark cap at y=390 across body's lower portion. Yet seat post ends at y=382, body covers part. Hmm.

Alternative body lower edge around y=390; saddle y=400 below. Easier: body lower contour at y=395 around x=470..590; saddle at y=400, visible directly under body, slight overlap. Bird body could be smaller vertically: center y=315, lower edge y=400. Neck to head y=150. We can do:
M420 275 C465 235 555 245 610 285 C655 320 645 375 595 395 C540 415 455 395 420 350 C395 315 398 290 420 275 Z
Lower edge around y=400. Saddle at y=398-410 might overlap bottom. Good. Body sits on saddle. Legs start near (515,390), extending down. This might be plausible; body less tall but still large enough. Need beak at y=200. Neck from (580,290) to (650,170) etc. Fine.
Tail at x=350..420 y=300..375.

Saddle path:
M465 399 Q485 385 535 388 Q568 389 580 399 Q570 410 535 410 L485 410 Q468 408 465 399 Z
dark navy, with coral top highlight. This sits under body lower edge; if body lower edge at y=395 around x=500, saddle overlaps a few px. Draw saddle after body to show. Seat post from (525,405) down to B, so its upper end can be hidden by saddle. Fine.

Need legs start at lower body (perhaps y=385) and to pedals. For far leg, start (490,380), knee (475,485), ankle (550,545). Near leg start (555,385), knee (625,480), ankle (630,615). Draw legs before body, so upper starts hidden. Need body reaches y=400, so a bit of leg visible from y=400 down. Good. But saddle drawn after body could cover hip origins too. Fine.

Could add short feather "pants" at hips? Not needed.

Feet:
- On P2 at (550,545), draw webbed foot perhaps `M535 535 L550 540 L570 532 L580 540 L570 550 L545 553 Z` orange with outline; but foot should be horizontal on pedal. Need foot near pedal. Maybe path for webbed toes:
```
<path d="M540 538 C550 532 557 540 566 535 C573 532 577 536 575 542 C573 549 560 552 545 550 Z" fill orange .../>
```
Pedal at x=525..580 y=538..550; this foot overlaps. Need perhaps three toe lobes visible. Could draw three separate orange ellipses or path with scalloped edge. Use a single path with three curves:
`M535 540 C540 530 550 530 553 539 C558 530 568 530 570 539 C577 533 585 537 582 545 C575 553 545 553 535 546 Z`. dark outline. This looks like webbed foot.
- On P1 at (630,625), draw foot from x=610..665 y=615..632, similar shape. Need maybe orientation slightly right. Use same path translated. Could define reusable path with transform? Could use `<g transform="translate(80 80)">` etc. But explicit simpler.
Need ankle line should meet foot at x=630,y=615 and foot center y=621. Good.
Maybe draw toes with small dark lines. Fine.

Need perhaps chain and gears for bicycle recognizability. Add a chain ring around B and rear cog at R; chain loop as dark path around them. But could clutter. A bicycle needs pedals; already. Could add chain thin path:
`M590 560 L320 559 A26 26...` Hmm. Maybe not needed. But chain ring at B and rear cog help. Draw rear cog circle at R radius 18, chain ring at B radius 28, and chain lines from top and bottom of circles as dark thin path. Need perhaps frame stroke overlaps. Could draw after frame:
```
<path d="M320 560 L590 552 M320 610 L590 618" stroke="#17324d" stroke-width=4...>
<circle cx=320 cy=585 r=17 ...>
<circle cx=590 cy=585 r=30 ...>
```
But bottom bracket and crank center already. Could add chain ring behind crank. Use r=28 gold fill? Typical chainring dark outline with pale fill. Need not distract. Perhaps enough.

Need maybe wheel spokes path with stroke light and hub circles. Need add main tire outer dark stroke and inner rim. Draw `circle` dark outer, then cream inner stroke, then spokes. If spokes drawn after rims, they connect. Maybe order:
- wheel shadow ellipse at y=735.
- tire circles: outer dark stroke 18, rim circle light 6 at r=122, spokes path from hub to r=120, hub circles. Actually spokes should be behind rim and tire. Draw spokes first then rim/tire, but endpoints covered by tire stroke. Fine.
- maybe colored fender? Not necessary.
Need perhaps use one group local transform for spokes:
```
<g transform="translate(320 585)" class="spokes">
 <path d="M0 0 L120 0 ..."/>
 <circle ... />
</g>
```
CSS class `.spokes path{...}`. Need maybe transform works with class. Fine.

Background:
```
<rect width=1200 height=800 fill="url(#sky)"/>
<circle cx=180 cy=150 r=85 fill="#ffe3a3" opacity=".9"/>
<circle cx=180 cy=150 r=115 fill="#fff3bf" opacity=".35"/>
<g fill="#fff" opacity=.8> cloud paths...
<path d="M0 500 C..." fill="#addbd7" opacity=".6"/> distant dunes/water
<rect y=735 ... fill="#f5d99d"/>
<path d="M0 735 H1200" stroke ...>
```
Need ground starts y=710 maybe; wheel bottoms y=733, so tires touch ground. Distant horizon at y=520. Could add wave lines at y=560, etc. Keep subtle.
Maybe add wind swooshes around pelican to show motion: thin white/cyan curves near x=220..400 y=250 etc. Not needed but nice. Could add small leaves. Need avoid clutter.
Maybe a banner/plaque at top left with "A PELICAN ON A BICYCLE" using SVG `<text>`; user asks accessible title but visible caption optional. Could include text top center? Might make illustration more polished. But main focus should be clear. A small title plaque at (70,55) with text "THE GREAT PELICAN RIDE" in dark navy could be nice. Yet viewBox space top y=0..120 mostly empty; could place a header. Need perhaps not hide beak. Could use HTML `<h1>` above SVG? But single page should fit. Maybe use SVG text at x=60 y=70, font-size 28, letter-spacing 2, fill dark navy. This is inline SVG text (not external). Fine. But user specifically wants accessible title/description; that counts. Could add decorative small star. But perhaps less is more. We can use top-left sun and a small caption. Need beak extends right around y=200, so top-left caption at y=60 no conflict. Could include `font-family="Verdana, sans-serif"` (system font, no network). Fine. However "main artwork consists of inline SVG shapes and paths"—text is okay but not a shape; small caption not main. Fine.

Need perhaps use SVG `<desc>` detailed with pose: "A cream pelican with a long yellow bill and orange throat pouch leans over a teal bicycle. Its wing rests on left handlebar grip, webbed feet on two pedals..." That helps accessible description. Good.

Need maybe have one wing contacting handlebar at x=700,y=325; need visually clear. Could draw a small coral grip behind and wing tip over it, with perhaps three feathers curling under. Add a tiny dark stroke from wing tip around grip. Maybe label? Not needed.

Need perhaps make long bill with pouch more obvious and not hidden by neck/head. Need design head/neck carefully:
Body from x=400..640, y=245..400. Neck should emerge from upper right around (585,285) and rise to (650,175), then head at (690,180). Head/bill base x=730. Let's draft:
Neck path:
```
<path class="bird-outline" fill="url(#bodyGrad)" d="
M565 300
C595 300 600 260 610 225
C620 185 640 150 675 145
C705 140 730 158 735 182
C740 205 720 222 698 220
C680 218 670 205 658 210
C647 215 650 245 638 275
C625 305 600 330 565 320 Z"/>
```
But this path is a thick S-like neck with head integrated. Need check shape: start at body (565,300), up to (610,225), then (675,145), head arc to (735,182), then back to (698,220), then (658,210), then down (638,275), then (565,320), close. Could form weird loop but recognizable. Maybe draw a separate white neck using a thick stroked path with round linecap:
`<path d="M580 305 C620 285 600 220 640 180 C660 155 690 160 700 185" fill="none" stroke="#17324d" stroke-width="72" .../>` then same with white width=62. This yields a curved thick neck, perhaps simpler and connected to body/head. Then draw head ellipse at (695,185) rx=55 ry=42. Need avoid disconnect. Use outline around head ellipse. Let's do:
- neck outline path stroke dark width 82, then inner stroke cream width 70, round caps. Path `M575 315 C610 295 595 245 620 205 C640 170 665 165 690 180`. This will be a broad curved neck.
- head ellipse cx=690 cy=185 rx=58 ry=43 fill cream stroke dark 6, perhaps slightly rotated -8°. This overlaps upper neck end.
- maybe cheek path shading.
- eye at (705,170), black circle r=6 with white highlight.
- crown crest feathers at top maybe three small tufts. Pelican often has a shaggy crest; add path around (660,145) etc. Could help. But neck stroke might already create shape. Add small feather tufts dark-outlined cream:
`<path d="M650 154 C640 135 650 128 660 145 C660 126 675 123 678 146 C687 130 700 136 692 154 Z"...>` maybe. Need not.
- head has slight yellow patch at base of bill. Could add `<path d="M720 180 Q745 178 745 200 Q730 205 720 198 Z" fill="#ffe0a3">`.
- Beak starts at (730,187), upper bill to (1020,230), lower edge around (730,210). Pouch starts at (730,210) to tip (1018,232) with deep curve to (890,315). Need layer order: neck/head, then pouch (maybe pouch behind upper bill but in front of head). Draw pouch first starting at bill base, then upper bill on top. Need perhaps the pouch shape lower boundary and inner shading. Pouch can overlap head at base. Add dark outline width 6.
   Pouch path:
```
M728 201
C790 205 835 260 890 295
C940 325 990 275 1018 232
C930 218 820 202 728 201 Z
```
Wait lower pouch should be a continuous shape from base to tip: upper boundary maybe line from base to tip (following lower edge of upper bill), and lower boundary is deep curve. If path starts at base (728,205), then `C830 205 930 217 1018 232` upper boundary to tip; then `C990 295 940 320 890 310 C820 295 770 245 728 205 Z` lower boundary deep. This yields pouch body. Need shape not weird. Let's define:
```
M 725 205
C 810 205 920 215 1018 232
C 1000 276 960 310 910 312
C 840 315 780 260 725 205 Z
```
This is a broad bag; lower boundary from tip (1018,232) back to base via C1000 276 960 310 910 312 C840 315 780 260 725 205. Deep around x=900,y=310. Good. Fill gradient peach to gold. Add inner lower curve from (755,216) to (920,292) to (1003,238) as darker stroke, perhaps fill none. Add 3 curved crease lines from base to pouch bottom: path M770 220 C800 255 835 285 880 300; M820 213 C850 250 880 285 920 302; M875 218 C900 250 930 280 965 285. But too many lines; maybe add one or two to show pouch.
Upper bill:
```
M725 185
C820 180 930 198 1018 224
Q1030 228 1023 236
Q1019 240 1012 236
C920 215 815 205 728 208
Q715 205 720 193 Q721 187 725 185 Z
```
Need upper bill over pouch. Maybe tip has downward hook: `Q1030 228 1022 238 L1018 232` etc. Could draw tip hook dark. Add a thin line along upper bill from (750,197) to (1000,226). Add nostril near (755,195). Need perhaps upper bill tip x=1025, within viewBox. Fine.
Need perhaps pouch upper edge aligns with lower edge of upper bill; draw pouch first, then upper bill. Good.
Need bill base perhaps starting at x=730 y=190 in front of head, head extends to x=748. Fine.
Need perhaps eye at x=705 y=175, but upper bill starts x=725 y=185; eye visible. Good.
Need perhaps throat pouch's dark outline around entire shape; upper bill covers top boundary partly, but dark line may show through. Good.
Need perhaps bill/pouch partly overlaps handlebar? Pouch y down to 312, handlebar y=325, close but not overlapping. Wing at y=325. Fine. Need maybe pelican head looks above bicycle, plausible.

Body with wings:
Body path maybe:
```
M420 275
C465 235 550 240 610 280
C655 310 655 365 615 392
C575 420 490 415 440 380
C400 352 392 305 420 275 Z
```
Tail feathers left:
```
M425 315 C390 295 360 292 335 305 C355 320 380 330 410 335 Z
M410 345 C375 335 350 345 330 365 C360 370 390 375 420 370 Z
```
Draw tail behind body with dark outlines and blue-gray fill. Need maybe two/three pointed feathers, recognizable bird. Could use single path with points:
`M430 305 L350 285 L385 325 L330 325 L395 355 L350 380 L445 375 Z` but maybe too jagged. Draw 3 separate feather paths with cream/blue. Better:
```
<path d="M430 305 C395 285 365 285 340 295 C365 310 390 325 425 328 Z" .../>
<path d="M420 330 C385 315 355 320 330 338 C360 348 390 355 425 350 Z" .../>
<path d="M425 350 C395 345 365 355 345 375 C375 380 400 380 440 370 Z" .../>
```
Then body overlays their right ends. Fine.

Folded wing on body:
```
M445 285
C490 260 550 275 585 310
C610 335 605 370 575 390
C535 385 480 360 450 330
C438 315 435 298 445 285 Z
```
fill pale blue-ish, outline. Add feather curves:
`M470 310 C510 330 540 355 565 380`, etc. Add dark primary feather tips perhaps path along lower edge with dark teal fill. But extended wing starts at shoulder and might overlap. Need draw folded wing before extended wing. Maybe folded wing on left side x=430..570. Extended wing from x=560..710. Good.
- folded wing shading fill `#d7e9e6`, stroke dark 5.
- 3 dark teal feathers at bottom: path `M465 342 C500 365 535 382 575 388 C550 395 510 385 475 365 Z` fill `#5f8c98` maybe. Could make wing recognizable.
- feather lines from (470,300) etc.

Extended wing:
```
M565 290
C610 275 655 290 690 315
C705 326 718 323 724 332
C727 340 716 349 700 344
C670 336 640 350 610 375
C585 395 555 375 550 340
C548 315 553 298 565 290 Z
```
Need maybe its rightmost tip around (724,332) covers grip at y=326. Handlebar grip x=680..720 y=316..334; wing tip x=724,y=332 touching. But path shape might look like a blob. Add 3 feather tips at right:
- main extended wing fill cream/blue with outline.
- `path d="M650 310 C675 310 700 318 715 330 C700 335 680 330 660 325 Z" fill...` etc.
Maybe draw a separate "wingtip grasp" shape:
```
<path d="M675 310 C695 305 715 312 724 322 C730 328 724 338 714 338 C705 338 695 331 680 327 Z" fill="#eef5ee" stroke.../>
<path d="M700 316 Q710 325 720 326" .../>
```
But if wing path already ends at x=724, okay. Need perhaps grip in coral drawn behind wing, with a small coral sliver visible at x=680..695. The wingtip overlays right part. Could draw a small dark curved feather line wrapping around bar at x=710,y=330. Need show contact. Maybe add three pale feather "fingers" curling around the bar:
```
<path d="M692 318 C705 316 718 321 724 330 C716 340 704 340 695 332" fill cream stroke dark/>
<path d="M690 330 C704 332 714 340 714 348" ...>
```
Could be enough.

Maybe draw a wing path from body to handlebar as a long arm-like shape with feather separations:
```
M560 300
C605 280 650 295 695 320
L715 327
Q720 335 710 340
L690 335
C660 345 625 375 590 380
C565 375 550 340 560 300 Z
```
Then feather lines:
`M590 305 C620 315 650 325 690 330`
`M580 330 C615 340 640 350 665 350`
Need body and wing colors distinct. Add dark blue primary tips at left? Hmm.

Need perhaps maintain perspective: near wing reaching handlebar should be in front of neck/body? It can overlap shoulder. Good.

Need perhaps show a second wing folded on body with darker tips. Good.

Need perhaps add a cyclist helmet? Pelican recognizable maybe a small cap could be cute but might obscure head; not necessary. Could add a tiny coral cycling cap on crown maybe, but pelican crest more important. Maybe small teal cap with visor? Could make look like rider, but no requirement. Perhaps helmet could reinforce riding pose. Yet birds' head with long bill is clear; a cap not needed. Could add a small scarf trailing backward for motion (coral ribbon) at neck/body, but optional. Might enhance composition. Need not overdo.

Need perhaps two wheels with spokes and frame connected. Need ensure central frame lines not all hidden by body/legs. Body covers top tube portion x=525..640 maybe, but top tube to x=795 visible from x=640..795. Down tube from (820,450) to (590,585) visible mostly below body. Rear triangle from R to S etc visible behind body partially. Fine.
Need perhaps saddle drawn after body, but frame top tube behind body. Seat post from S=(525,405) to B hidden partly by body but visible below y=410. Fine.
Need perhaps handlebar stem visible from head tube at x=795,y=390 to x=760,y=350; pouch ends y~312, so visible. Good.
Need maybe front fork from U=(820,450) to F=(880,585) visible. Good.

Need perhaps a small front basket? No.

Need write file. Need perhaps use browser tool after. We should likely use bash to check file and maybe `grep` for title/desc/image tags. Need use browser screenshot and inspect DOM/console. Need maybe inspect screenshot visually. Let's generate carefully. We have plenty time (15 min, but model speed). Need maybe create with write. Let's compose full HTML.

Let's define CSS:
```
*{box-sizing:border-box}
html,body{margin:0;height:100%;}
body{display:grid;place-items:center;background:#b7dddc;overflow:hidden;font-family:...}
.illustration{width:min(100vw,150vh,1200px);height:auto;aspect-ratio:3/2;max-height:100vh;box-shadow:0 20px 60px rgba(...);border-radius:clamp(0px,2vw,24px);overflow:hidden;background:#d9f2ef}
svg{display:block;width:100%;height:100%}
```
Potential border radius clipping subject? Subject has margins >100, so fine. Could maybe omit border radius due viewBox corners. Fine.
Need responsive via preserveAspectRatio default xMidYMid meet and viewBox. Good.
Need maybe no `<script>`? The addendum says CSS in style, JS in script, inline — perhaps maybe expects all assets inline; "JS in a <script> tag, inline" if JS used. We could include a tiny inline script to make no-op or enhance. But perhaps requirement says "Use HTML, CSS, and JavaScript as needed" and "CSS in a <style> tag, JS in a <script> tag, inline" — we can include a script with a small feature, maybe adjust `document.querySelector('svg').setAttribute('data-rendered','true')` or dynamic subtle parallax? Not needed. But to satisfy literal "JS in a <script> tag", maybe include a small script that adds a `data-ready` attribute and maybe listens for pointer to toggle `pedaling` class? Animation not required; no need. Could include an empty `<script>`? Better a tiny script that sets `aria` fallback maybe:
```
<script>
  document.addEventListener('DOMContentLoaded', () => {
    document.querySelector('.illustration').dataset.ready = 'true';
  });
</script>
```
No network, no console errors. But unnecessary. Could instead implement a tiny interaction to cycle through 3 wind streak opacity on click? That would be superfluous. However having JS present may help requirement. Need consider "single-page web app" addendum—might expect JS. But static app is fine. Yet including a simple inline JS for a subtle "honk" interaction? Could be fun but not required and could distract. Perhaps add clicking SVG toggles a `.rolling` class that animates wheel spoke groups and wind lines via CSS. But animation not required and perhaps no need to verify. Could add a tiny script to support reduced motion and toggle with click. But user says "Animation and interactive controls are not required"; adding them could introduce complexity. Better keep static and only a script setting `data-ready` for browser check. No external. Could also use JS to generate spokes from arrays, reducing static code. But then accessible checks via DOM after load still see shapes; likely okay. Yet static is safer. Let's include minimal JS to set `data-ready` and maybe no errors. It technically fulfills JS inline.

Need maybe use CSS variables? Fine.

Let's write SVG in order. Need ensure all tags closed, no malformed path. Need maybe use HTML entities? No.

Detailed SVG structure:
```
<div class="illustration" id="scene">
<svg viewBox="0 0 1200 800" ... role="img" aria-labelledby="artTitle artDesc">
<title .../>
<desc .../>
<defs> gradients ... maybe reusable `path id="spokes16"`? use explicit paths. </defs>
<rect ...>
<!-- sun -->
...
<!-- clouds -->
...
<!-- distant water -->
<path ...>
...
<!-- ground -->
<rect y=735 ...>
...
<!-- decorative title -->
<text ...>THE PELICAN EXPRESS</text>
...
<!-- speed lines -->
...
<!-- bike shadow -->
<ellipse cx=600 cy=735 rx=470 ry=18 .../>
<!-- wheels -->
<g aria-hidden="true"> ... spokes paths, circles, hubs ...</g>
<!-- chain -->
...
<!-- frame -->
<g> paths ... </g>
<!-- handlebar -->
...
<!-- crank -->
...
<!-- legs -->
...
<!-- tail/body -->
...
<!-- saddle -->
...
<!-- neck/head -->
...
<!-- beak pouch -->
...
<!-- wings? -->
```
Need layering: neck/head should perhaps be behind body? The neck originates from body; draw neck before body so lower part hidden, then head/bill after? Maybe:
- tail
- neck (behind body)
- body (over neck base)
- folded wing, extended wing
- head/bill (in front)
- saddle after body? Need saddle on top of body. Could draw saddle after body but before wings.
- legs before body.
- crank/pedals before feet? Actually feet are part of legs and need overlap pedals. If legs drawn after crank, yes. Need body after legs. Good.
- saddle after body maybe.
- neck can be drawn before body; head/bill after body (head doesn't overlap body much).
- extended wing after saddle, perhaps after body. Need wing contact handlebar drawn on top of handlebar.
- Handlebar is drawn with frame before body. Then wing overlays grip. Fine.
- Head/bill maybe drawn after extended wing? Beak/pouch at y<315, wing at y~300-375; they may overlap around x=690,y=300. Need the wing should be under pouch perhaps; draw extended wing before head/bill so pouch overlays wing at upper edge. But wing contact at x=700,y=325 unaffected. Good.
- Folded wing on body maybe before extended wing.
- Head/neck? Neck drawn before body. Head ellipse after neck and body, then bill. Fine.
- crest maybe after head.
- Eye after bill? Eye at x=705, not covered by bill mostly. Draw eye after head/bill maybe.

Need maybe saddle after body but before wings; body lower edge around y=400 and saddle top y=390, drawing saddle over body. Fine.

Need perhaps bird legs drawn before frame? We planned frame first then legs. If legs drawn after frame, they can overlap seat tube and down tube, which is natural. But hip origins hidden by body. Good. Need crank/pedals should be drawn before legs. Fine.

Need maybe chain path behind frame/spokes? Could draw after wheels but before frame. Need chain ring visible perhaps partly covered by crank. Fine.

Need maybe handlebar grip drawn with frame before wing; then wing overlays. Need brake lever visible perhaps draw after wing? If brake lever line is under wing maybe still visible to left/right. Could draw grip and handlebar under wing. Fine.

Let's draft elements precisely.

Background:
```
<defs>
<linearGradient id="sky" x1="0" y1="0" x2="0" y2="1">...
<linearGradient id="sand" ...>
<linearGradient id="body" ...>
<linearGradient id="pouch" x1=0 y1=0 x2=0 y2=1>...
<linearGradient id="bill" ...>
<radialGradient id="sunGlow">...
</defs>
```
Need perhaps `gradientUnits` default objectBoundingBox works with x2="0" y2="1" (values 0/1 accepted). Could use percentages to be safe: x2="0%" y2="100%". Fine.
Body gradient from top-left to bottom-right.
Maybe add `<filter id="softShadow">`? Could be slow but fine. Not needed.

Background paths:
- sky rect.
- sunGlow circle at (1050,140)? Could be behind beak tip, maybe nice. But bill at x=1020,y=230; sun at (180,140) less clutter. Use (175,145) r=100.
- sun circle r=72.
- clouds perhaps at (330,120), (880,100). Need from x maybe 780..1020 y=100; beak at y=200, fine. Use white with opacity .7:
  path `M760 125 C770 100 795 95 815 108 C825 82 865 82 875 110 C900 102 920 115 922 132 C900 140 780 140 760 125 Z`. Another at (320,180) maybe behind neck? use left.
- water band from y=500 to 735 fill #a8d9d3, with top path curves. Maybe ground starts y=730. Could draw `path d="M0 510 C180 490 320 530 500 510 ... L1200 735 H0 Z"` fill pale aqua. Then wave lines. But ground sandy starts y=725, so water band y=510..725. Add wave strokes around 560,620,680 with low opacity. Could perhaps make bicycle tires visually grounded. Good.
- ground rect y=730, fill sand gradient. Need wheel bottoms at y=733 (r=140 + 9 stroke), so a few px overlap into ground. Ground should be drawn behind bicycle, so fine. Top edge line y=730. Shadow ellipse y=730.
- decorative dune curves maybe.
- small title at x=65,y=70 perhaps dark navy, font 26, letter spacing 3. Add a line under it. Need ensure sun at 175,145 doesn't overlap. Title y=70 fine.
- speed lines around x=230..380 y=270 etc. Could draw paths with light blue stroke. Need not hide tail. Use `M220 280 H340`, `M180 320 H310`, etc behind bird.

Wheels:
Need maybe spokes path with multiple M commands:
```
<g transform="translate(320 585)" class="spoke-set">
<path d="M0 0 L122 0 M0 0 L113 47 ..."/>
</g>
```
Need CSS `.spoke-set path { fill:none; stroke:#6e9fa2; stroke-width:2; opacity:.75; }`
Could define d once in `<defs><path id="spokePattern" d="..."/></defs>` then `<use href="#spokePattern" x?` but local transform. Use in defs and `<use>` with `transform="translate(...)"`. But CSS styling of `<use>` maybe tricky. Better duplicate path manually, or use `<g>` with path and <use> transform. Could define `<g id="spoke-wheel"><path .../></g>`, then `<use href="#spoke-wheel" transform="translate(320 585)"/>`, etc. This is internal reference, allowed. But "shapes and paths embedded" still yes. To be absolutely static and avoid browser quirks with href, duplicate path twice. We'll duplicate. Need perhaps use `d` string once? We can copy. Fine.
Need all 16 spokes. path:
`M0 0 L122 0 M0 0 L113 47 M0 0 L86 86 M0 0 L47 113 M0 0 L0 122 M0 0 L-47 113 M0 0 L-86 86 M0 0 L-113 47 M0 0 L-122 0 M0 0 L-113 -47 M0 0 L-86 -86 M0 0 L-47 -113 M0 0 L0 -122 M0 0 L47 -113 M0 0 L86 -86 M0 0 L113 -47`
Need maybe rim at r=126? endpoints 122, okay.
- tire circles r=140 dark stroke 18, fill maybe #eaf8f4 with opacity? If fill none, background shows through. Use `fill="#eaf8f4" fill-opacity=".16"` etc. But water/ground inside wheel could show; that's okay. Could use `fill="none"`.
- rim circle r=124 stroke white width 6.
- inner rim circle r=132 stroke navy width 2 maybe.
- hub circle r=12 fill dark, inner r=6 cream.
Need perhaps add small coral valve markers? Not needed.
Need perhaps front wheel center etc.

Chain:
```
<path d="M320 560 L590 552 M320 610 L590 618" stroke dark width 5 .../>
<circle cx=320 cy=585 r=20 ...>
<circle cx=590 cy=585 r=30 ...>
```
But chain lines cross frame maybe okay. Use dark teal thin. Need maybe draw chain before frame so frame overlays. Add rear cog after spokes but before frame. Chain ring around B could be behind frame but visible. Fine.
Need maybe chain ring fill cream with dark outline and teeth? Add small dashed circle? Could use `stroke-dasharray="4 6"`. Nice.
Frame:
Use one path under + one path color:
```
<path class="frame-shadow" d="M320 585 L590 585 L525 405 L320 585 M525 405 L795 390 M795 390 L820 450 M820 450 L590 585 M820 450 L880 585"/>
<path class="frame-core" same/>
```
Actually first subpath `M320 585 L590 585 L525 405 L320 585` draws chain stay, seat tube, seat stay. Good.
Need top tube S->T. head tube T->U; down tube U->B; fork U->F. Good.
Need maybe front triangle lacks connection S to U? Top tube to T, head tube to U, down tube to B, seat tube to S; connected.
Need hidden top tube under body but okay.
Need maybe seat post separate from S to saddle y=385, line with dark/cream. Add maybe `<path d="M525 405 L525 385" ...>`. Good.
Need handlebar path under and color core:
`M795 386 L760 348 C748 335 738 326 720 326 L685 326` outline stroke 16, core stroke 8 perhaps dark? Could use dark for bar with coral grip. Need bike frame teal; handlebar dark navy perhaps. Draw `stroke="#17324d" width=10` no outline? Need shape. Use under 16 dark, core 8 light aqua perhaps. Then grip rect at x=675 y=316 w=50 h=20 rx=10 fill coral stroke dark 4. Maybe wing tip overlays right side. Add brake lever path `M720 328 C710 340 700 345 690 346` dark thin. Need maybe no weird.
Need frame head tube maybe integrated.

Saddle:
seats. Could draw after body though seat post drawn with frame earlier. Need saddle shape with dark outline 5. Add coral highlight path. Need perhaps body lower edge behind saddle. Fine.

Crank:
draw after frame:
- chainring maybe already.
- crank circle at B r=20 dark, inside r=10 gold.
- crank arms to P1/P2: under dark stroke 14, top gold stroke 8 perhaps. Need endpoints at pedal centers.
- pedals: dark rectangles with coral top stripe. At P2 center (550,545), rect x=518 y=538 width=64 height=14 rx=5; P1 x=600 y=618 width=64 height=14. Need feet overlap.
Actually crank arms from B=(590,585) to P2=(550,545) vector (-40,-40), P1=(630,625) vector (40,40). Good. Draw line to pedal centers. Pedal rectangles centered at those points. Need perhaps P2 y=545, foot top y=530; foot drawn after hides pedal. Fine.
Could add small pedal caps. Fine.

Legs:
Need draw dark outline and orange core as path. For far leg behind maybe use darker orange and stroke width 18, near 22.
Far leg path `M495 382 C480 425 475 470 490 500 L545 540` maybe. Wait foot at P2=(550,545), leg endpoint around (545,540). Need ankle. Use path with segments: `M495 382 C480 430 475 470 490 500 C505 520 530 525 548 540`. Might not show clear knee; use `M495 382 L478 480 L548 540`. That's a bent leg but second segment from (478,480) to (548,540). Fine. Use stroke-linecap round, join round. However body covers start to y=400, leaving from (490,400) downward. Good. Add a knee circle maybe at (478,480) orange r=11 with dark outline; not necessary.
Near leg path `M555 385 C585 420 620 450 625 495 C630 545 620 580 628 615`. Could have clear bend at (625,495). Or `M550 385 L625 490 L628 615` straight segments. Use curved outline maybe. For plausible riding, knee should point forward (right) and lower leg down to pedal. Start hip (550,385), knee (635,490), ankle (630,615) gives knee forward and foot slightly back. Good. Use `M550 385 C585 415 620 450 632 490 C642 535 620 580 628 615`. This is curved but plausible. Need maybe stroke thick 23 orange with dark 29 outline. Add knee highlight maybe.
Far leg perhaps darker and thinner to indicate depth, drawn first. Need perhaps foot shapes after body? If feet drawn before body, body doesn't overlap feet; okay. Need draw legs and feet before body, but body not near feet. Fine.
Need foot shapes coordinates:
P2 foot (on upper-left pedal):
```
<path d="M530 540 C534 530 545 528 551 537 C558 528 568 529 571 538 C579 532 588 537 585 545 C579 552 542 553 532 548 C528 546 528 543 530 540 Z" fill dark outline? Use same path with stroke dark 4, fill orange; />
```
Pedal center x=550,y=545; foot spans x=528..588, y=528..553. Fine.
P1 foot:
`M610 620 C614 610 625 608 631 617 C638 608 648 609 651 618 C659 612 668 617 665 625 C659 632 622 633 612 628 C608 626 608 623 610 620 Z`.
Need perhaps orange webbed toes dark outlines on each; add small lines from center to lobes maybe:
`M551 542 L550 550 M571 541 L572 550`, etc. Use dark orange stroke width 2. Fine.
Need perhaps legs drawn in front of frame; yes.

Tail/body:
Draw tail feathers before body.
Tail paths with dark outline and fill cream/blue. Need perhaps use `stroke-width=5`.
Body path with `fill="url(#bodyGrad)" stroke="#17324d" stroke-width=7`. Need ensure no conflict with neck. Draw neck before tail? Actually neck emerges behind body. Let's order:
- legs
- neck (thick curved stroke)
- tail
- body
- saddle
- folded wing
- extended wing
- head/bill/eye/crest
But neck path may be partially hidden by tail? no. Need neck from (575,310) to (690,180), body overlays lower part. Good.
Need perhaps head ellipse drawn after bill? Head behind bill; draw head before pouch/bill, then eye after. Good.
Need crest maybe after head but before bill. Fine.
Need extended wing may overlap neck at shoulder around (575,300); likely okay if wing drawn after neck/body. Need head/bill draw after wing, pouch perhaps overlays upper part of wing around x=700,y=300. Fine.
Need saddle drawn after body, but folded wing maybe overlaps top of saddle? no.

Neck path:
```
<path d="M570 318 C610 300 595 245 620 205 C640 173 665 165 690 180" fill="none" stroke="#17324d" stroke-width="80" stroke-linecap="round" stroke-linejoin="round"/>
<path ... stroke="url(#bodyGrad)" stroke-width="68"/>
```
Potential issue gradient on stroke with objectBoundingBox of path? Could use solid `#fff9e9` instead to avoid weird. Use fill `none`, stroke `#fffaf0` width 68. Add subtle blue shadow stroke maybe along one side. Need maybe neck outline appears thick but body covers lower endpoint. Good.
Maybe head ellipse at (690,184) rx=58 ry=43 rotated -8; use `<ellipse transform="rotate(-8 690 184)" ...>`. Need outline 6.
Crest path:
`M648 154 C640 138 647 128 659 145 C660 128 674 124 678 148 C688 131 701 137 693 156` fill cream, stroke dark 5, linejoin round. Need maybe head ellipse covers lower part. Draw crest after head maybe. Fine.
Head maybe has a yellow face patch around bill base:
`<path d="M720 171 C740 172 750 185 748 203 C738 211 724 207 716 197 Z" fill="#ffe7a8" stroke="none"/>` but bill overlaps. Maybe not.
Eye at (706,174) dark circle r=7 plus highlight at (708,171) r=2.
Maybe eyebrow / cheek curve.
Need perhaps little smile line at bill base? no.

Pouch and bill:
Pouch path starting at (728,203) to (1018,232), deep lower. Need maybe draw dark outline width 6. Add inner shading path with `fill="#e76f4d" opacity=".35"` perhaps lower region:
```
<path d="M745 214 C810 235 850 290 910 302 C950 307 985 278 1005 237 C970 260 930 285 890 284 C830 280 785 240 745 214 Z" fill="#dc694b" opacity=".28"/>
```
Need perhaps crease lines:
`<path d="M760 212 C790 250 830 285 875 299 M815 213 C845 250 875 290 920 302 M875 219 C900 250 930 280 965 285" fill=none stroke="#b75b45" stroke-width=3 opacity=.55 stroke-linecap=round/>`
Need maybe these start inside pouch and end near lower edge.
Upper bill:
```
<path d="M725 186 C815 180 930 198 1016 223 C1027 226 1030 233 1022 239 C1019 241 1014 240 1008 237 C915 215 815 204 728 208 C716 207 715 192 725 186 Z" fill="url(#billGrad)" stroke="#17324d" stroke-width=6 />
```
Need maybe lower edge line from (742,204) to (1008,232):
`M742 201 C830 198 920 211 1003 230` dark orange stroke width 3. Add nostril at (757,194) small ellipse. Hook at tip:
`M1016 223 C1027 226 1030 233 1022 239` maybe already. Could add dark line `M1016 224 Q1028 228 1022 238` stroke dark 4. Good.
Need perhaps pouch upper boundary partly hidden by upper bill. Fine.
Need maybe bill base on head at x=725; head ellipse extends to 748. Good.

Wing contact:
Need define handlebar grip at x=675..725,y=316..336. Extended wing tip at x=720,y=328. To make clear contact, perhaps draw a small coral grip visible from x=675..700 and wingtip curls around x=700..725. Need wing path. Let's draw:
```
<path d="M558 294
 C590 278 630 286 674 308
 C690 316 706 317 718 322
 C728 326 728 337 718 341
 C707 346 692 337 675 334
 C645 342 618 367 590 381
 C562 382 546 355 550 326
 C551 310 553 300 558 294 Z" fill="#e5f1ec" stroke dark 6/>
```
This wing has a rightmost shape around (718,322..341), definitely over grip. Add feather separators:
`M575 305 C610 308 650 320 700 330`
`M565 330 C600 337 625 350 655 350`
`M590 360 C615 350 635 342 665 343`
Need perhaps tip wrapping bar:
`<path d="M695 316 C710 314 726 320 727 330 C727 340 713 344 700 336" fill="none" stroke="#17324d" stroke-width=4/>` This maybe outline. Add 3 small feather tips around grip:
```
<path d="M685 319 C700 313 715 317 723 327 C712 329 700 327 685 324 Z" fill="#fffaf0" stroke.../>
<path d="M688 329 C702 328 714 334 719 341 C706 345 695 338 688 329 Z" .../>
```
But this could overly clutter. Maybe one path indicates folded feathers around bar. Need clear contact: perhaps a small dark curved claw-like line? Birds wings don't have claws, but feathers can wrap. Use `path d="M707 322 C717 319 727 324 727 331 C727 340 716 343 708 338"` fill cream stroke dark. This overlays grip and looks like curled feather. Could draw it as part of wing after main wing. Fine.

Need perhaps wing itself could be interpreted as a second beak? But body and extended wing should read. Add dark blue primary feather tips at far end? Maybe not. Need the folded wing on body show wing anatomy.

Folded wing path:
```
<path d="M440 285 C480 260 540 270 580 305 C607 330 608 365 580 388 C535 386 480 362 450 330 C437 314 432 296 440 285 Z" fill="#cde3e2" stroke dark 5/>
<path d="M455 325 C490 355 535 378 580 388 C555 398 505 382 470 355 Z" fill="#6f9aa5" stroke dark 4/>
<path d="M465 295 C500 310 530 335 560 370 M485 286 C520 305 550 330 575 360" .../>
```
Need perhaps extended wing starts at x=558,y=294 and overlays folded wing right side. Good.

Tail perhaps dark blue tips to match.

Need maybe a small jersey or scarf on pelican to make rider pose? Could add a coral scarf along neck trailing left: `path M620 235 C590 220 570 210 540 210 L555 235 ...` etc. But might obscure neck and clutter. Maybe add a tiny teal cycling cap? Hmm no.

Need maybe visible feet near pedals clearly. Need perhaps legs are orange and dark outline. Good.

Need perhaps body not float: saddle after body and legs to pedals, wing to handlebars. Good.

Need perhaps add small "click" lines at contact points? Not needed.

Need maybe accessible text description exactly. Fine.

Let's write now.

Need inspect browser. Use browser reload then screenshot and inspect maybe parallel? Need first reload and screenshot perhaps browser tool. Let's call reload then screenshot maybe sequential. Could use multi_tool parallel? Actions perhaps need sequential as screenshot after reload; but tool likely reload loads page. Let's do reload, then screenshot.

We have screenshot. Need evaluate. It looks quite good! Need check specifics:
- Pelican recognizable: long bill with huge pouch, body, wings, feet. Yes.
- Riding pose: feet near pedals? One foot around x550,y545 and one at x630,y625; screenshot shows one foot at left pedal near bottom bracket, one at bottom pedal. Yes. Wing reaches handlebar? Actually handlebar seems mostly hidden / maybe visible as teal curve from head tube to wing. Need inspect: screenshot shows near wing tip around x=708, y=337 touching maybe a small white oval shape; handlebar grip may be hidden by wing and pouch? We need see. The handlebars: from head tube at (795,386) to (760,348) etc, but screenshot shows a teal curve from around x718,y325 to x800,y385 maybe. Actually top tube is from saddle to head tube at y390; handlebar stem from (795,386) to (760,348) to (685,326). But screenshot: at x720,y325 there is a teal diagonal line curving down-right to x800,y385 (head tube), likely handlebar stem? Need wing tip at x700,y330 touching grip. We should zoom maybe screenshot crop via browser? Browser tool doesn't support zoom maybe can use click? Could inspect DOM or maybe use `motion` etc. We can take screenshot and perhaps use external image processing with python? Could use browser screenshot attachment and maybe `read`? There's no direct file path. But can perhaps use `browser screenshot` result with image attached; can visually zoom mentally. Could use bash to parse index coordinates. Need maybe use browser DOM inspect to check title/desc and no image. We can use `browser inspect` with text perhaps returns DOM summary. Need perhaps verify complete subject unclipped: screenshot shows all within 1200x800 yes; wheels bottom at 733, border at 730, fully visible. Beak tip x=1030, with margins. Cloud etc. Good.

Potential issue: bicycle handlebars: are they recognizable? Requirement specifically "Make bicycle recognizable through ... handlebars". If handlebar grip is hidden by wing, need ensure at least some visible. In screenshot, I see a turquoise curved line from wing tip (around x720,y325) to head tube at x800,y385)—this could be interpreted as the handlebar connected to head tube, but no obvious horizontal grip. Actually look carefully: top tube from saddle around x570,y393 to head tube x795,y390. There is a teal diagonal from x720,y325 to x800,y390; perhaps that's handlebar stem merged with head tube, yes. The wing tip at x700,y330 is adjacent to the start of this diagonal, perhaps contact. But the grip rectangle at x674..726 y316..337 is likely completely under wing (white oval), so not visible. The line from x720,326 to x685,326 with coral grip may be hidden under wing tip. Wait screenshot near wing tip: from x~680 to 720 there is a white oval with dark outline, and a small dark line inside. Behind it maybe no coral grip. The wing itself covers the grip. Could still satisfy "wing or other clear contact near handlebars" because wing is near teal diagonal stem. But handlebars as recognizable bicycle part may be weak. Need perhaps adjust to make a visible grip / bar. Could draw grip or brake lever in front of wing, perhaps a coral curved grip piece at x675..705 and dark bar extending from there to stem. Need not hide entirely. Could add after wing/head maybe a visible short handlebar segment over wing? But then contact may be clearer if wingtip wraps around it, with grip visible to left and perhaps a small dark line across feather tip. Need think.

Also bicycle frame: front fork from head tube to front hub is visible, down tube to bottom bracket is visible, top tube from under wing to head tube visible. Rear triangle visible. Great.

Potential issue: saddle is a small red/dark shape at x465..580 y398; body sits on it, clear. Good.

Potential issue: legs: far leg orange path from hip to foot at x550,y545. Near leg from hip (550,385) to foot x630,y625. Both visible. But body/bike geometry across legs: far leg foot at x550,y545 sits above chainring at x590,y585. Near foot at x630,y625 is on lower-right pedal. Good. Need maybe both pedals visible? One pedal under foot at x550,y545 perhaps only orange foot and dark pedal maybe behind; screenshot shows small dark pedal to right. Fine.

Potential issue: head/neck: neck looks like a white thick S curve; head with eye and tuft. Long bill huge pouch. Very recognizable. Good.

Need maybe could improve handlebars. Let's inspect a zoom by taking screenshot maybe browser tool can use `motion`? Could perhaps use python to crop from attached screenshot? Tool result image maybe saved somewhere inaccessible? Need perhaps browser screenshot action returns file path? It gave attached image only. Could use browser `screenshot` maybe same. Could use custom browser action scroll? Could perhaps zoom the page by keyboard Ctrl+? Not likely. Could temporarily modify CSS with devtools? Not needed. We can use pixel visual from given screenshot. Could perhaps use `browser inspect` with text to query elements? Tool might support DOM inspect with selector? Need see docs? Browser tool schema only action, x,y,text etc. `inspect` maybe returns DOM info. Could use text as XPath/CSS? Need perhaps `browser inspect` with text field can be selector. Let's test maybe. Need also HTML file static checks with bash. We'll do browser inspect and maybe screenshot again after modifications. First perhaps use bash to check counts and external resources. Need maybe use `grep` for `<image`/`http`. Use bash. Could run in parallel with browser inspect? They can be independent. Let's do multi_tool parallel with browser inspect and bash.

Need perhaps `<title>` count 2 because HTML title + SVG title. okay. External references only xmlns namespace and internal `url(#...)`—fine. No raster images. Need maybe refine handlebars. Let's zoom mentally. In screenshot, wing tip at ~700,330, and teal handlebar from x720,y326 to x795,y386. Actually that teal diagonal is likely not handlebar stem but head tube + down tube? Let's map frame:
- top tube from (525,405) to (795,390) is nearly horizontal, visible from x580 to x795 at y390-405. In screenshot, horizontal teal line from under wing around x575,y394 to x795,y390.
- head tube from (795,390) to (820,450) slants down-right; in screenshot there's a dark teal diagonal from x795,y390 to x820,y450.
- down tube from (820,450) to (590,585) slopes down-left; visible.
- fork from (820,450) to (880,585) slopes down-right.
- handlebar stem from (795,386) to (760,348) to (720,326) to (685,326), which slopes up-left. In screenshot, I see teal diagonal from x720,y325 to x795,y385, yes this is handlebar stem. So the handlebar has no distinct grip because wing covers it. The wing is contacting at its end. Good enough? The requirement "bicycle recognizable through two wheels, a connected frame, handlebars, saddle, and pedals." A viewer might see the diagonal line from head tube to wingtip as handlebar/stem but perhaps not unmistakable. Could improve by adding a clearly visible curved handlebar in front of wing: maybe expose a small coral grip to left of wing at x650..690 and a dark/teal line from x690 to x720, then stem to x795. Since wing currently extends x550..727 and covers grip entirely from x674..726. We can move grip left to x640..690, with wingtip at x690..727 touching its right end. Then grip visible from x640..690; but bird body/folded wing and extended wing may overlap x640..690 at y316..337, so a portion could still be hidden by main wing path which covers this region. Need draw grip after wing, on top, to ensure visible. But then wing contact could still be clear if wingtip wraps around grip. Could draw a coral bar grip from x648..694 y316..333 atop the wing, then a small cream feather tip curling over its right end. But if grip drawn on top of wing, might look like wing is behind grip rather than holding it. Could then draw a small feather over right edge of grip. Need maybe visible grips and wing contact. Maybe add a separate dark curved handlebar section to left of contact, drawn after wing:
```
<path d="M690 326 H650 Q640 326 640 338" .../>
```
Actually typical handlebar extends backward (left) from stem, so grip could be at x640..690, while wing reaches from body to x690. If we draw a coral grip at x640..682 on top of the wing, the wing would appear to hold at x690 via feather tip. Need maybe modify handlebar path to extend from stem at (795,386) to (760,348) to (710,326) to (650,326), with grip x640..690. Then wing tip at x700..727 is near right end; body wing may overlap from x550..675. Draw bar after wing? We need layer ordering. Currently handlebar is before legs/body/wing. Could add a "front exposed grip" after wings near x640..690. But then it might cover folded wing/body, maybe okay if strategically. Maybe better to put the wingtip at x650..680 and handlebar grip at x640..690, overlapping. But current wingtip at x695..727. Could draw short dark/coral grip from x640 to x700 at y326, then feather tip around x700. It would be visible over wing (from x640..695) but body may look like an arm lying on grip. That's okay.

Alternative simpler: keep same handlebars but add a visible brake hood / lever from x690,y326 to x670,y300, after wings. But might still be obscure.

Need maybe check requirement "wing or other clear contact near handlebars." The contact near handlebars currently clear because wing tip ends exactly at start of teal handlebar stem. We can perhaps add a small dark circular "grip" outline around wingtip and a visible coral segment extending left from it. Let's design a layered visible grip:
- After wing path and feather lines but before head/pouch, add:
```
<path d="M720 326 L664 326" stroke="#17324d" width=16 .../>
<path ... stroke="#70c7bd" width=8 .../>
<rect x=642 y=316 w=50 h=21 rx=10 fill="#e96e58" stroke="#17324d" width=5/>
```
This is drawn atop wing, so the bar line from x664..720 traverses the wing; might look like wing is pierced. But we can limit to x642..690 and let wingtip feather cover from x695. Actually if we draw a rect x638..688 and a dark line x688..720, then wingtip at x695..727 partly covers right end if drawn after. We can reorder: draw grip before wing (already there), but shift it left so part visible; then wing path may cover some but not all. Need modify original grip x=620..680 perhaps. Handlebar path from stem to x625. The wing spans from x550..727; at y316..337, the wing shape covers roughly x570..718. So any grip under wing from x620..680 will be hidden. Need draw grip after wing. Could draw just a short segment that emerges to left of wing at y330 from x625..650 (wing starts at x550 but shape at y330 includes x550..705). Actually wing fill covers x550..718 at y330, so no. Need draw on top. Maybe okay.
Could perhaps move wingtip contact to x680 and draw grip from x640..700 on top, with a feather tip curling around right end. The wing body still under grip but that's plausible as grip crossing in front. Need add feather over rightmost 12px of grip. That would show contact. Need maybe not too crowded.

Maybe better to make clear handlebar by adding a distinctive upward curved bar from head tube with a visible drop: currently `M795 386 L760 348 C748 335 738 326 720 326 L685 326`. The segment from 685..720 is hidden under wing, but the stem from 720..795 is visible. A handlebar can be recognized by that angled line; no need grip. But perhaps a viewer might interpret it as another tube. Add a visible curved "drop" below head to make bar shape:
```
<path d="M795 386 L760 348 C748 335 738 326 720 326 L685 326 C675 326 670 335 672 345 L680 360" ...>
```
This drop handlebar extends down-left from grip and would be visible below wing around x680,y345-360 perhaps; wing may cover x550..700 at y340-360. Could be partially hidden. Add after wing perhaps. Hmm.

Maybe make handlebar like cruiser handlebars extending up and back with a visible high grip at x700,y290, above pouch/wing? But pouch ends around y312, so could place grip at y300 and wingtip contact there. That would be a clear handlebar arch above wing, but wing currently at y330. Could make wing reach up to x700,y300. But bill/pouch overlaps y200..312. The grip at x700,y300 would be near pouch base, perhaps okay. Yet more complexity.

We could keep current composition and add a small coral grip visible on top of wing at x650..690, with a dark outline and a feather tip wrapping around its right end. This likely improves recognition. Need test screenshot.

Let's think visual layering. If we draw a coral rounded rect at x650..700 y316..337 on top of the wing, it will appear as a horizontal grip over the wing, perhaps like the wing is under the handlebar. Add a cream feather tip at x690..727 already there (currently drawn before grip if we insert grip after wing tip? Need order). We can place grip after the main wing but before the small feather tip `M695 317...` so the feather tip overlays right end. Then it looks like feather curls around grip. Need modify:
- Original handlebar grip x674..726 could remain behind wing, but hidden. Shift it to x640..700 perhaps, but still behind wing partly. Could just add "visible grip overlay" after wing lines but before feather tip. We don't need draw a whole new bar line; use existing stem from x720..795. If grip x645..706 ends at x706, there might be a gap to stem start at x720, but wing feather at x695..727 bridges it. We can add dark short line from x705 to x725 on top. Actually the underlying handlebar path from x685 to x720 exists, hidden by wing; if grip x645..705 and feather x695..727, the visual connection through wing to stem at x720 is okay. Need perhaps move original grip x640..706; then add overlay same. But duplicate unnecessary. Could edit original grip to x640..706 and then add overlay after wing with same shape, maybe weird duplicate. Better remove original grip and add new one after wing, before feather tip. But the handlebar path from 795..685 remains, and a grip at x640..705 could be drawn later. Need ensure no coral rectangle under wing; if remove original, no hidden artifact. Good.

Need:
1. edit original `<rect x="674" y="316" width="52"...>` to perhaps `<path d="M685 326 H650" ...>`? We could leave no grip initially. The bar path already goes to x685, which is under wing. Need visible grip from x640..705. We can remove rect and brake lever perhaps move after wing. But brake lever currently under wing and hidden; could add visible small lever after grip. Not essential.
2. After wing lines, just before feather tip, insert:
```
<rect x="642" y="316" width="70" height="21" rx="10" fill="#e96e58" stroke="#17324d" stroke-width="5"/>
<path d="M707 326 H725" ... dark maybe.
```
But if rect from 642..712, the wing feather tip from 695..727 overlays right 17px, making a clear clasp. Need perhaps bar line from 712..725 dark to stem at 720; the feather tip overlays. Good.
3. Add brake lever after feather maybe `<path d="M706 331 C696 344 688 348 678 349" .../>` on top of wing but visible. Could be okay.
Need perhaps grip should not look like a random red rectangle on wing; but with teal stem at x720 it reads handlebar. Maybe add a small dark/teal segment from x650 to x720 visible over wing. The grip itself can be coral and dark outlined. Fine.

However, drawing a coral bar over the wing might obscure feather lines and make wing look like it's holding it from below. That's okay. Need maybe body-wing contact near handlebar even clearer.

Alternatively place a small coral grip at x720..770 above the wing? But stem line from x760..795; could be visible. Wing tip x727, so grip from x715..760 touches wing at left end and connects to stem. That might be simpler: draw a horizontal grip from x715..765 y320..340 on top of pouch? It would be visible to right of wing and connect to stem at x760,348. But typical handlebar grip extends left from stem, not right. Could still be seen. Yet wingtip at x727 touches left end. Need maybe draw coral grip at x710..760 y318..338; this would be above teal stem; visible. But pouch bottom at x710..1018 y203..312; grip y318 just below pouch, fine. This gives clear contact. The handlebar stem from (760,348) to (795,386) would connect to grip around (750,338), perhaps via a small curve. Could place grip x705..755 y316..337, with wingtip at x695..727 overlapping left part. Then visible right part x727..755. That seems best: keep wheel/frame, update handlebar path perhaps to apex at (755,326) then stem to (795,386); grip from x700..755. But original path is `M795 386 L760 348 C748 335 738 326 720 326 L685 326`. This already has a bar through x720..685. A grip at x705..755 would sit across the curved stem near x748,335; might look odd. Could use a cruiser style: from head tube (795,386) up-left to (755,340), then horizontal grip x700..755 at y328. Need slight curved connection. Could modify path:
`M795 386 L760 348 C755 335 750 326 735 326 L685 326`
Then grip x685..735. Wingtip x695..727 overlaps most. Only left x685..695 visible. Hmm.
Maybe handlebar grip x735..785, with stem endpoint at (760,348), but wingtip x727 not quite touching; could extend wingtip to x745. That could work. Need more changes.

Maybe current is acceptable; don't over-engineer. The task asks "handlebars" plural as part of recognizable bike; stem + curved bar is visible. Also wing contact near handlebars is clear because wing tip touches that angled bar. A grip doesn't need to be visible. The diagonal teal line from wing tip to head tube is unmistakably a handlebar in side-view maybe. Need perhaps perhaps no need changes. But let's scrutinize screenshot: The wingtip at x700,330 has a white oval over a teal line that extends right-down to x795,390. The line might be interpreted as a second top tube (since there is horizontal top tube from saddle to head tube). Together they form a triangle with head tube and perhaps down tube. Actually the diagonal from x720,y325 to x795,y390 and horizontal from x525,y405 to x795,y390 form a triangle with seat tube; could be interpreted as another frame tube rather than handlebar. But because it ends at wingtip and curves, perhaps still handlebar. Need maybe add a more recognizable vertical/upward curve or grip. Let's do a modest adjustment: add a small visible coral grip on top of wing near x650..705 and a small dark brake lever. This will clearly mark handlebars. Need perhaps update original grip to align and avoid hidden duplicate. We can edit:
- Original grip rect from x674 w52 to x640 w70 perhaps. But hidden under wing; no visual effect. Could leave.
- Insert after wing feather lines (before feather tip) a visible grip and bar segment. That might be enough.
Maybe simpler: after all bird art (at very end) add a small handlebar grip with dark outline at x655..710,y316..337, plus a dark/teal bar from x710..760,y326..326? But drawing at end means it will overlay wing and perhaps pouch? Pouch at y312 bottom; grip y316 not overlap. Fine. This will mark handlebar. Need perhaps wingtip feather should overlay right end; if grip drawn at end, it covers feather tip. Could draw grip before feather tip in source order by inserting in middle. Need use edit. Let's locate wing section. Need exact text. Read relevant lines around 200-225 maybe.

Could perhaps leave as is because screenshot pretty good. But handlebar recognition maybe weak. Let's improve with a visible curved drop and grip that doesn't obscure too much. Need perhaps use a simple overlay at end: a coral grip from x650 to x700 y315-337 can be drawn on top of wing. But would look like a red bar crossing the wing with no connection to stem because hidden segment x700..720. Add a dark/teal short line from x700 to x745 y326 on top, then stem from x745 to x795 perhaps already visible. Actually original handlebar path visible from x720 to x795. So if we draw a bar segment from x650 to x720 on top of wing (coral grip from x650..700 and teal from x700..720), it will connect to visible stem at x720. Then the wingtip feather at x695..727 can be drawn on top of the right end to show contact. This could turn wing into being crossed by handlebar from x650 to x727. Not terrible. Need perhaps draw this overlay before feather tip. We can insert a group after wing feather lines:
```
<!-- Re-expose the grip and short bar in front of the wing -->
<path d="M650 326 H720" stroke="#17324d" stroke-width=16 .../>
<path d="M650 326 H720" stroke="#70c7bd" stroke-width=8 .../>
<rect x="645" y="316" width="58" height="21" rx="10" fill coral stroke dark/>
<path d="M700 331 C690 344 680 349 670 349" ... brake lever />
```
Then feather tip path after this overlays x695..727, covering the bar around x695..720. But if feather tip covers the entire teal segment x700..720, the grip might seem disconnected from stem. Need maybe feather tip only covers bottom of bar? We can adjust feather tip to be smaller or place bar after feather tip. Could draw bar after feather tip but then a cream feather tip could be partially hidden. Perhaps draw bar first, then a small feather at x695..715 that wraps around top of bar rather than covers all. Could use a narrow path around grip:
`M695 317 C705 313 715 317 716 324` etc. Hmm.
Maybe simpler: overlay grip only from x635..690, and leave visible teal bar from x690..720 underlying wing? Not visible. Could draw teal line x690..720 on top, then feather tip at x695..727 would cover it. Need maybe draw feather tip first then bar; then bar crosses feather tip, making it look like wing under bar. Contact still clear because feather touches bar. That's acceptable; no need wrap.

Let's settle on a visible grip `x=635..695` and a bar segment `M695 326 H730` on top of wing, with the existing stem from x720 onward. Then draw a small cream feather curl over the left part of the bar maybe after:
`M690 320 C700 316 710 319 713 326 C708 333 698 332 690 327 Z`—this overlaps grip right end and bar left. Need not cover entire connection; bar continues x713..730 visible to stem. This reads as feather holding bar. Great. Need perhaps modify existing feather tip from x695..727 to smaller x685..713. Could edit that path and line. Need perhaps draw visible grip overlay after main wing lines but before feather tip. Sequence:
- Main wing path and feather lines.
- Overlay grip+bar:
```
<path d="M635 326 H730" dark 16>
<path ... teal 8>
<rect x=628 y=316 width=70 height=21 ... coral>
<path brake lever ...>
```
- Smaller feather curl:
`M686 317 C699 313 711 318 714 327 C711 337 697 337 690 328 C688 324 687 320 686 317 Z` fill cream stroke dark. This overlays right end of grip (x690..714), leaving bar from x714..730 visible. Need perhaps feather covers a bit of bar but not all. Add small line.
- Original feather tip path at x695..727 replaced with this smaller shape. Need perhaps line `M697 322 C705 321 710 324 713 328`.
This would make grip visible from x628..690 (about 62px) on top of wing. But x628..690 is inside wing body; likely okay. It might look like a coral stripe over the wing, but with dark outline and teal bar connecting to stem, clearly handlebar. The wing still reaches and curls over right end. Good.

Need perhaps handlebar path originally has grip x674..726 hidden; we can edit it to x628..698 to align, but since overlay will cover, hidden original can remain. Could change original to same coordinates so no weird hidden colors; hidden anyway. Need maybe brake lever originally at x718..688 hidden; overlay draws new lever. Could edit original path to x690 etc. But simpler: remove original grip and lever, add overlay after wing. Need edit:
1. Replace original handlebar comment section lines with paths plus perhaps no rect/lever. Keep bar path maybe extend to x635:
`M795 386 L760 348 C748 335 738 326 720 326 L635 326` (both dark and teal). Then overlay grip at x628..698 y316..337 on top of wing; bar segment from x698..730 perhaps needs visible overlay. We can overlay a short `M698 326 H730` dark/teal, which connects to original stem at x720. Good.
2. Insert overlay group in wing section.
3. Replace feather tip path/line with smaller curl.

Need evaluate screenshot after. This is a moderate change. Let's do exact edits. Use one edit call with multiple disjoint replacements. Need ensure old text unique. We'll target handlebar block, wing tip block. Also maybe `desc` mention handlebar grip okay. Need perhaps no need to change desc.

Proposed handlebar block:
```
      <!-- Handlebar, stem, and brake lever -->
      <path d="M795 386 L760 348 C748 335 738 326 720 326 L635 326" ... />
      <path same ... />
```
No rect/lever initially.
Then overlay insertion after wing lines:
```
      <!-- The forward grip is re-drawn over the wing so the contact stays legible -->
      <path d="M698 326 H730" fill=none stroke dark width=16 .../>
      <path ... stroke teal width=8/>
      <rect x="628" y="316" width="72" height="21" rx="10" .../>
      <path d="M698 331 C688 344 678 349 667 349" .../>
      <path d="M686 ... small feather ..."/>
```
Need layering: If grip rect x628..700 and bar line x698..730 drawn before feather. Good. Brake lever maybe starts x698,331. Fine.
Feather curl x686..714,317..337, drawn after bar, covers right 14px of grip and left 16px of bar, leaving bar x714..730 and grip x628..686 visible. Nice.
Need perhaps original bar path dark line from x635..720 is under wing and hidden; overlay visible segment from x698..730 plus grip x628..700 makes full bar visible. Good.
Need maybe there's a gap x700..720 color transformed from coral to teal but feather covers part; okay.
Need maybe brake lever will overlay wing and perhaps show curved dark line below. Fine.
Need perhaps existing feather lines go under grip; okay.
Need perhaps pouch lower edge ends y312 at x780; grip y316 just below, no overlap. Head/bill drawn after overlay, but pouch path at x725..1018 y203..312—could cover overlay at x725..730 y316? no. Good.

Let's edit.

Need reload and screenshot.

Now visible coral grip on wing, perhaps looks like a red slot but okay. Wingtip white feather at x690..714 with teal bar to head tube. Handlebar now clearer. Need perhaps check if grip overlay looks like a small red object floating on wing—not too bad; dark outline and teal bar connects. Perhaps could be more natural if grip were dark/teal rather than coral, but illustrative. Need perhaps make the grip larger or aligned with stem? It is horizontal at y326, right end x700, then teal bar x698..730 then stem starts x720..795. Looks connected. Good.

Need maybe check all subject unclipped. Yes. Need perhaps verify responsive sizing at a narrower viewport. Browser tool viewport fixed 1200x800, but can perhaps use `scroll` or key? No direct resize. Could use screenshot with different window? Maybe browser tool has fixed viewport. Could use CSS inference; width min(100vw,150vh,1200px) aspect-ratio. Fine. We can perhaps use browser `inspect` to query computed style? It didn't return detailed DOM. Could run JS via browser key? No. But we can use a headless browser perhaps installed? Need maybe check with `node`? We can use bash to see if puppeteer/playwright available, but browser tool already serves. Could perhaps use browser `key` with something? Not needed. Need perhaps do a quick static XML validation maybe using Python's html.parser or xmllint on SVG portion? Need ensure no broken tags. Browser rendered fine and console no errors. Need maybe check `data-ready` set, no console errors. Browser inspect didn't show detailed DOM but no errors. Could perhaps use browser `screenshot` action after reload to confirm final. We already have screenshot from reload. Need perhaps check console output after reload = `[]`. Good.

Need maybe verify no external network requests. Static grep found only `xmlns` and internal `url(#...)`, no external src or network. Could perhaps use browser `inspect` with text selector to get more info? It returned minimal. Could use JavaScript through browser? Not in schema. But static grep enough. Need perhaps use bash with Python to parse DOM and check accessibility and no `<image>`, no `<script src>`, etc. Could run quick Python script with html.parser. Also perhaps check all SVG elements inside viewBox extents roughly; screenshot confirms unclipped. Need maybe check title/desc. Could use `grep` lines. Need maybe inspect file around final script and root. Use maybe a simple Python parse to ensure `viewBox`, `role=img`, `aria-labelledby`, title/desc IDs. Also no external resources. Need maybe output succinct final report with what checked and what remains unverified. Need mention unverified perhaps responsive behavior at other viewport sizes / screen readers. The addendum says "briefly report what you actually checked and which behaviors remain unverified." Need mention actual checks: browser reload at 1200x800, console clean, screenshot visually checked pelican anatomy, bicycle geometry, pose, framing; static checks for inline shapes, no external images, viewBox, title/desc. Remaining unverified: other viewport sizes and actual screen reader output / nonvisual accessibility; maybe animation/interaction absent. Need not mention "I didn't test" too much. Need perhaps maybe verify responsive sizing with a quick local script using CSS maybe no need. Could use browser tool maybe can simulate viewport by `scroll`? Not. Could use a headless browser from node_modules perhaps? Need maybe see environment. But under time budget, we can perhaps run `which chromium` etc. Yet browser tool fixed. Could maybe use Chrome's developer tool via shell? Not needed. We can report unverified other viewport sizes.

Need perhaps maybe check that screenshot includes all relevant features: handlebars now visible; saddle visible; pedals; wheels. Fine. Need maybe perhaps inspect DOM for accessible title/desc via bash Python to be thorough. Also maybe check no `<image>` tag or external URL. Let's run a concise script.

No python3. Could use node maybe. Need maybe just grep with shell. We already did. Could use `node` if available. Need maybe not essential, but need not leave failed check as final? We can rerun using node or shell. Need maybe inspect command result not harmful. Let's check `command -v node`. Could use node to parse. Need perhaps ensure no Python. Use bash with grep. Let's do a compact shell check.

Need maybe no more edits. Could perhaps check browser console after final reload already clean. Need maybe maybe browser screenshot final confirms. Good.

Need perhaps consider user asked "Write it to index.html in current working directory using file tools." Done. Need final concise report with what checked and unverified. Need perhaps mention file path clearly. Need mention no external resources. Need perhaps perhaps note `data-ready` script but no need. Need perhaps mention responsive sizing code but unverified alternate viewports. Need maybe mention "actual screen reader output" unverified. Need maybe mention no third-party libs.

Need perhaps ensure "single-page web app" with inline CSS/JS and self-contained. Yes. Need maybe mention no network requests added. Good.

Could there be hidden issue: `xmlns="http://www.w3.org/2000/svg"` is technically a URL but not a network request; okay. Need perhaps maybe no external CDNs. Fine.

Need maybe mention "checked complete illustration at 1200×800" and "browser console empty". Maybe "Static source has 65 paths etc". Need perhaps "remaining unverified: actual screen-reader output and resizing across physical devices; CSS uses min()/aspect-ratio but only one viewport tested." Good.

Need final answer not too long. Also perhaps mention "I adjusted handlebar grip after first render." Fine.

Let's formulate:
"Created /tmp/job-LeIFr6/index.html. Verified via browser reload/screenshot: unclipped viewBox, pelican long bill/pouch, body wings, feet on pedals, wing feather on exposed handlebar grip, connected two-wheel frame/fork/saddle/pedals; console empty. Static checks: inline SVG shapes/paths, title/desc role img aria-labelledby, no img/image/data URI/external script/CDN; CSS/JS inline. Remaining unverified: alternate viewport sizes and screen-reader output (only default 1200×800 visual browser pass)." Need perhaps mention responsive CSS present. Good.

Need maybe no need to mention file size. Fine. Ensure final says index.html present. Good.