Implement windward-leeward racing course

[cuccel]

No description provided.

[mpihlak]

Tee rebase praeguse seisu peale, lisasin eile stardiabi ja start-line biase ja võib olla veel midagi. Need tekitavad konflikte. Dashboardi asukoha võiks ka samaks jätta ja stardiliini pikkuse ja layouti, lisada ainult täiendav raja layout.
Eri rajatüüpide high-score jaoks peb vist ka midagi ette võtma.

[mpihlak]

@claude review the pull request

[claude]

Claude encountered an error —— View job

Failed with exit code 128

---

I'll analyze this and get back to you.

[mpihlak]

Claude encountered an error —— View job

Failed with exit code 128

I'll analyze this and get back to you.

@cuccel Ma arvan et see / seal branchi nimes ajab Claude segadusse.

[cuccel]

• nihutasin dashboardi tagasi (pikemad tekstid ei mahtunud ära - seega algsest asukohast pisut vasakul siiski)
• lisasin uue raja koos "KJK-stiilis" stardi-finišiliiniga
• muutsin "default" stardi-finišiliini tagasi.

[cuccel]

Claude encountered an error —— View job

Failed with exit code 128

I'll analyze this and get back to you.

@cuccel Ma arvan et see / seal branchi nimes ajab Claude segadusse.

uurisin ta käest järele:

No, I won't get confused by branch names containing "/". Git branch names with slashes like fork/feature/new-course are completely valid and commonly used for:

Organizing branches: feature/new-feature, bugfix/issue-123, hotfix/critical-bug
Remote tracking: origin/main, fork/development
Hierarchical naming: team/frontend/new-ui, release/v2.1/final
Git treats the slash as just another character in the branch name - it's not a directory separator in this context.

pigem on probleem selles, et action käib käesolevas repos ja siin repos tõesti feature/new-course puudub. kuna mul ei ole siia reposse õigusi siis forkisin ja tegin PR'i läbi forki.