Skip to content

Commit 9d122dd

Browse files
authored
docs(devlog): close the provider-marks unit with what the plan got wrong (#3101)
Every phase is on dev. Providers resolving a mark went 45 -> 77 of 83; the six that keep the fallback tile have their searched paths recorded in the README. Four corrections, each a wrong assumption rather than a detail. One plate is not enough. 040 specified a single constant light plate for colour artwork too dark for the dark tile. That fixed twelve marks and left six failing, because their artwork is near-WHITE -- drawn for a dark header. They needed the opposite plate. The doc assumed the failure was one-directional because every example it had was. A mark can solve this itself. digitalocean.svg carries its own prefers-color-scheme rule, so plating it defeated the vendor and produced light-on-light at 1.01:1 -- worse than doing nothing. Only rendered measurement caught it; reading the file says #000 and stops there. Tracing a favicon traces the plate. 020 called vectorization settled because the two previous traces had transparent backgrounds. A favicon is a glyph on a filled square, and the first pass traced the square: baseten 97.7% ink, bizrouter 89.3%. The gap was older than the count suggested. The luminance guard, written for the 26 new marks, immediately failed on five old ones -- including the two files the Integrations page already masks, invisible here the whole time because the two surfaces had no shared decision. Verification: privacy:scan passed, repo-hygiene 12 pass. Docs only.
1 parent d71aa07 commit 9d122dd

7 files changed

Lines changed: 60 additions & 0 deletions

File tree

File renamed without changes.

devlog/_plan/260901_provider_marks/010_wp2_wire_present_assets.md renamed to devlog/_fin/260901_provider_marks/010_wp2_wire_present_assets.md

File renamed without changes.
File renamed without changes.
File renamed without changes.

devlog/_plan/260901_provider_marks/040_wp5_painting.md renamed to devlog/_fin/260901_provider_marks/040_wp5_painting.md

File renamed without changes.

devlog/_plan/260901_provider_marks/050_wp6_catalog_and_delivery.md renamed to devlog/_fin/260901_provider_marks/050_wp6_catalog_and_delivery.md

File renamed without changes.
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
# Outcome
2+
3+
Unit closed 2026-09-01. Every phase is on `dev`.
4+
5+
| Phase | Doc | PR | On `dev` as |
6+
|---|---|---|---|
7+
| wp1 | 000 | #3092 | `5ef84b61e` -- roadmap, docs only |
8+
| wp2 | 010 | #3093 | `a11038cb2` -- wire the committed assets + gap guard |
9+
| wp3/wp4 | 020, 030 | #3095 | `910b4c736` -- 26 marks sourced |
10+
| wp5 | 040 | #3098 | `15f92e3f6` -- the painting contract |
11+
| wp6 | 050 | #3099 | `d71aa07c0` -- catalog marks |
12+
13+
Providers resolving a mark: **45 -> 77 of 83**. Painting split on the merged
14+
head: 47 image, 17 mask, 7 light plate, 6 dark plate.
15+
16+
## What the plan got wrong
17+
18+
**One plate is not enough.** 040 specified a single constant light plate for
19+
colour artwork too dark for the dark tile. That fixed twelve marks and broke
20+
nothing, but it left six others still failing -- `parallel` at 1.00 dominant
21+
luminance, `bizrouter` 0.98, `nebius` 0.87 -- because their artwork is near-*white*,
22+
drawn for a dark header. They needed the opposite plate. The doc had assumed the
23+
failure mode was one-directional because every example it had was.
24+
25+
**A mark can solve this itself.** `digitalocean.svg` carries its own
26+
`@media (prefers-color-scheme: dark)` rule that repaints the glyph `#F4F5F5`.
27+
Plating it defeated the vendor and produced light-on-light at 1.01:1 -- worse
28+
than doing nothing. Nothing in the plan anticipated an asset that adapts, and
29+
only rendered measurement caught it; reading the file's fill colour says #000 and
30+
stops there.
31+
32+
**Tracing a favicon traces the plate.** 020 described the vectorization path as
33+
settled work because `hermes-agent.svg` and `gajae-code.svg` had gone smoothly.
34+
Those sources were transparent-background artwork. A favicon is usually a glyph
35+
on a filled rounded square, and the first pass traced the square: `baseten` came
36+
out 97.7% ink, `bizrouter` 89.3%. Border-ring plate detection was added and found
37+
real plates behind six assets.
38+
39+
**The gap was older and wider than the count suggested.** The luminance guard,
40+
written for the 26 new marks, immediately failed on five old ones:
41+
`opencode.svg` (#211e1e) and `kimi-color.svg` (#1a1a1a) are the very files the
42+
Integrations page already masks -- invisible on the provider surface the whole
43+
time, because the two surfaces had no shared decision. `grok.svg` is the same
44+
story one PR later. `ollama-color.svg` and `vercel-ai-gateway-color.svg` had never
45+
been caught by either pass.
46+
47+
## Six providers keep the fallback tile
48+
49+
`chutes`, `nscale`, `tencent-coding-plan`, and the three `volcengine` plan ids.
50+
Each was probed at its registry `baseUrl` and `dashboardUrl`, its docs subdomain,
51+
and the conventional icon paths. What was found and why it was refused is in the
52+
provider-icons README. A recorded empty is a result; borrowing a neighbouring
53+
brand's mark would be a misattribution that outlives the commit.
54+
55+
## Verification as merged
56+
57+
CI green on every PR head, including the unsharded macOS job, before each admin
58+
squash merge. On `d71aa07c0`: root and gui `tsc --noEmit` exit 0, `oxlint` clean,
59+
`privacy:scan` clean. Every guard added in this unit was driven red before being
60+
kept -- eleven falsifications across five test files.

0 commit comments

Comments
 (0)