Add Sunny Marker

## Font project repository

https://github.com/buildinternet/sunny-marker-font

## Family description

**Sunny Marker** is a handwritten marker family designed for small all-caps labels, margin notes and friendly annotations, with enough range for larger headings. One variable font provides continuous weight, width, optical size and slant.

Designed and maintained by **[Sam Dunn](https://samdunn.org)**. [Interactive specimen and complete glyph gallery](https://sunnysdk.com/fonts/sunny-marker/).

| Axis | Range | Default |
| --- | --- | --- |
| Weight `wght` | 300–700 | 400 |
| Width `wdth` | 75–125 | 100 |
| Optical size `opsz` | 10–36 | 14 |
| Slant `slnt` | −9–0 | 0 |

The family has 336 glyphs, including all 319 codepoints in GF Latin Core. Editable sources are 48 UFO masters and a designspace, with a fontmake build.

## Requirements

- [x] The entire font family and editable sources are public under OFL 1.1.
- [x] There is no separate proprietary, paid, Pro or larger retail edition.
- [x] I own the rights to release the project; AI use is disclosed below.
- [x] No Reserved Font Names are declared.
- [x] Fontdata's name check found no exact match for Sunny Marker on 2026-09-16.
- [x] The definitive application-menu family name is **Sunny Marker**.
- [x] GF Latin Core is fully covered.
- [x] The upstream repository provides sources, build entry point, fonts, licensing and documentation.
- [ ] Complete technical compliance: the remaining findings below need resolution or review during onboarding.
- [x] I will maintain the public repository and respond during onboarding.

I have signed Google's Contributor License Agreement.

**AI provenance:** I direct the design. The original concept artwork was created with ChatGPT, and AI tools assisted with font engineering and QA. This is also disclosed in the public contribution guide.

## Candidate and QA

[Upstream preparation PR](https://github.com/buildinternet/sunny-marker-font/pull/2).

The **1.311 onboarding candidate** adds metadata to the 1.310 general release: designer attribution, named-instance PostScript names, intermediate width labels and corrected optical-size STAT flags. Binary comparison confirms identical outlines, spacing, layout and axis ranges. The existing website/npm release stays at 1.310.

[Candidate package and current QA report](https://github.com/buildinternet/sunny-marker-font/blob/0fde8d6a4e21f56dec31d972a57058efd6e8bdae/documentation/GOOGLE_FONTS.md)

The complete, unmodified **Fontspector 1.7.4 `googlefonts` profile** reports **148 PASS / 22 WARN / 7 FAIL / 42 SKIP / 9 INFO**, with no ERROR or FATAL. No checks were excluded. All seven FAIL results are `googlefonts/tofu`, code `bad-sample-text`: inferred language support passes base exemplars, but sample strings additionally require U+0331, U+02BC or U+014B. The report lists each language. The tool suggests sample-data inconsistencies; we have not independently confirmed that diagnosis or claimed those languages as supported. We would appreciate guidance on resolving the samples versus extending coverage before production onboarding.

Other review items include Google Fonts subset routing, a designer profile/photo, and technical warnings detailed in the report. A single continuous `slnt` file is intentional; we understand Google Workspace may need a separate italic companion for its italic button and welcome onboarding guidance while preserving the self-hosted variable font.

The earlier 1.310 FontBakery run had no failures or errors (125 PASS / 9 WARN for the variable font; 413 PASS / 24 WARN for representative statics). That is separate from the current Fontspector findings. [Completed CI](https://github.com/buildinternet/sunny-marker-font/actions/runs/35109462366).

This is an initial request for design review and onboarding, not a claim that all production requirements are already satisfied.

## Image


Read documentation/GOOGLE_FONTS.md and the linked upstream preparation PR first; they contain the candidate package and current Fontspector 1.7.4 googlefonts report. Review the seven tofu failures and other onboarding items against the report. Done means the remaining compliance questions have reviewer guidance or resolution and the family is accepted for onboarding.

Written by the indexing model from the issue text.