Fix Gojo UI stability and renderer maintenance

[erickkkyt]

What changed

• move Satoru Gojo status chrome away from profile actions
• align skill search and filter styling with the plugin collection surface
• reconcile semantic DOM roles without redundant attribute rewrites
• keep home and Composer geometry stable during transient typing rerenders
• verify the active renderer theme before maintenance reapply
• bump the project to 0.4.4 and Satoru Gojo to 1.2.1

Why

Codex can expose combined skill filters as simultaneously pressed and can transiently rerender home children while typing. The prior maintenance loop also reapplied the full theme on every interval even when the correct style and chrome were already active. Together these behaviors caused misleading active states, text-entry jitter, and unnecessary renderer writes.

Validation

• pnpm release:check
• 34 test files / 272 tests passed
• 12 theme packages validated
• TypeScript and production build passed
• production dependency audit found no known vulnerabilities
• live Codex 26.715.52143 verification confirmed stable Composer geometry, one owned style/chrome pair, and zero maintenance rewrites while active