read theme from hero_proc secret/env var, not env.sh #94
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_proc#94
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Overview
The active light/dark theme is currently sourced from
env.sh(or worse, hardcoded). Per the canonical Hero meta-config rules, all hero_ services read configuration fromhero_procsecrets or env vars set by hero_proc — never from OS env or config files.* Theme is no exception.Why
Meeting 2026-05-06: "hero proc env var not env.sh var / hero proc secret, etc. light or dark".
Skill
hero_proc_metadefines the rule. Today's theme handling violates it.Acceptance
THEME(or equivalent) is a hero_proc secret/env varhero_ui_themeskill)THEMERelated
hero_proc_meta,hero_ui_themeSource: meeting notes 2026-05-06.