Distribution and release records

The current distributed release is 0.4.1. This public repository retains historical GPL source with its original package version; that tree does not build the current proprietary release. Use the official release feed to identify the downloadable build and read the source status. A local source patch, successful packaging command or partial test run does not establish release acceptance.

Governing documents

Rights and restrictions are defined by LICENSE, the applicable EULA, LICENSE-EXCEPTION.txt and the components' own terms. The third-party notices, credits and pinned sources, component record and full license copies retain their separate scope. This index is not a combined-distribution license clearance.

Match the artifacts to the accepted version

The package version, runtime version, installer target, tutorial edition, release notes and public download manifest must identify the accepted build. Generated kernel and component records must be regenerated by the existing release pipeline. Source candidates retain previous records as inputs; they do not relabel an old package as the repaired version.

Koder-owned private runtime source stays in the private build and acceptance workflow. Public repositories receive the intended public documentation, installers, notices, checksums and accepted distribution artifacts. Third-party components retain their licenses, notices and applicable source obligations.

Acceptance and publication

Record actual command, exit status and evidence separately for source checks, protocol fixtures, native platforms, installation, update/restart, real accounts, independent review and production readback. Retain original failures and incomplete work. A blocked runner that executes no steps is not a passing Windows run.

Version 0.4.0 is a formal release of the preview.30 baseline. The release channel does not certify untested platform/account behavior; those limits remain disclosed and the historical evidence remains unchanged. Update website content and GitHub assets together, then read back version, file sizes and SHA-256 values. A documentation-only preview must be labeled as a candidate and must not replace the current production download feed.

Tutorials and user data

The complete guide, Chinese guide and command references distinguish candidate behavior from older installed releases. Printable lessons use the same release metadata.

Projects, credentials, private conversations, browser profiles, mail and execution authority are user data and are not release inputs. New project folders use Koder Projects while private configuration remains in the user profile. Distribution tests use owned synthetic inputs; no real key is needed to print the tutorials.

Version 0.4.1

Published by explicit user authorization with recorded platform and real-account limits. Candidate results remain attributed to their exact archives. The final release assets, public download checks and isolated installer/update results have separate receipts.