Development and contribution

HorneroOS is developed across repositories. Start by identifying the layer that owns the behavior, then read that repository’s AGENTS.md, README, and contributor instructions before editing.

Choose a contributor path

• Architecture — find the owner of a change.
• Testing — select focused checks and graphical acceptance.
• Contributing — branch, review, and cross-repository expectations.
• Internationalization — current language and string contract.
• Historical dotfiles wiki disposition — how earlier knowledge was evaluated before being reused.

Source-of-truth rule

Implement behavior in the repository that owns it. Keep this handbook focused on user and contributor guidance; keep API details and code-level contracts with their implementation. The website imports this repository at a reviewed commit and owns navigation and presentation, not a parallel copy of the documentation.

Product truth

HorneroOS is in development. A working developer setup or component package does not imply a supported end-user installation. Check current release and installation status before writing guides or claims. Label preview-only behavior and package-specific constraints explicitly.

Report a bug

Open a focused report in the repository that owns the failing behavior. Include the component revision, expected and actual result, shortest reproduction, and the first relevant sanitized error lines. Never attach private screenshots or full personal logs.

• Shell — desktop and Settings.
• Config — defaults and theme packs.
• horneroctl — CLI behavior.
• Website — public pages and docs presentation.