Org issue hygiene: label taxonomy + 1.0 milestones + project boards

[LizAinslie]

Done

• Kalendee triage finished with existing labels + Kalendee 1.0 milestone
• Added c/chore on Kalendee
• Created <Project> 1.0 milestones on product repos (keel, blawk, konfy, wake, TimezoneDB, Kompass, kraft, lokus, website, brand, themes, email-worker)

Lift from Kalendee (use on every product repo)

Category (c/) — pick exactly one:

• c/bug
• c/feature — net-new capability
• c/enhancement — improve something that exists
• c/chore — CI, tooling, deps, hygiene (added on Kalendee)

Target (t/) — zero or more:

• t/android t/ios t/desktop t/web t/server

Integration (i/) — as needed (Kalendee examples):

• i/discord i/gcal

Stock: documentation good first issue help wanted duplicate invalid question wontfix

Suggested additions (org-wide / per-repo)

Label	Why
c/docs	Align docs with c/ prefix (or keep documentation)
c/epic	Parent tracking issues
a/blocked	Waiting on another issue/repo (e.g. Kalendee #31 → Keel #65)
a/needs-design	UX/API not locked
a/good-first-issue	optional rename; or keep stock
i/microsoft i/apple i/caldav i/ics	Kalendee calendar providers
i/oauth	Cross-cutting OAuth work
p/p0 p/p1 p/p2	Priority if you want it in labels not Projects
size/S size/M size/L	Optional sizing

Project-specific labels: you said you’ll add later.

Project boards

Engineer Bot’s gh token lacks read:project / project scopes, so boards can’t be created or mirrored from here.

Please either:

1. gh auth refresh -s read:project,project on the bot’s GitHub login, or
2. Duplicate the Kalendee Projects v2 board template for: Keel, blawk, Konfy, Wake, TimezoneDB, Kompass, kraft, lokus, website

Once scope exists I can clone the Kalendee board structure across repos.

[LizAinslie]

Label taxonomy doc PR opened — see linked PR for Docs/Issue Labels.md.