Upstream sync

hordecode is built on two upstream projects: opencode, at base 1.19.4, and MiMo Code, at base 0.1.11.

Release policy

hordecode 0.1.x follows the opencode 1.x line. Every opencode 1.x release is ported before the next hordecode release. If opencode stops publishing 1.x releases, hordecode stays on the last one and maintains it.

MiMo Code’s supervisor and harness designs come from version 0.1.11. From 0.1.12 on, its later changes are taken one at a time, when they help hordecode.

File ownership

Each file has an ownership class. The three main classes are:

• PARITY: identical to opencode 1.19.4. Upstream owns the file and provides each new version as-is.
• FORK_DELTA: an upstream file that hordecode has modified. Each port re-applies the hordecode changes, and every other line matches upstream.
• FORK_ONLY: a file that exists only in hordecode. hordecode owns it.

Porting

Upstream-owned files change through ports. A port is complete when its code, its version bump and its marker merge have all landed. The marker merge records the new ancestry, so git history shows which upstream release each port is based on.

What it means for you

• Existing setups keep working. Legacy configuration file and environment-variable names are still accepted as fallbacks. See Config.