KIP Interfaces — Installation and Updater Guide v0.1.46 (development; unapproved)

Layout

The ZIP includes KIP-Interfaces/ and KIP-Interfaces-Updater/ sibling directories. The live installation expects these directories beside each other under public_html. Persistent data is stored outside the application tree.

Normal self-update

  1. Confirm the existing external updater is installed and functional; preserve an independent recovery copy and data backup.
  2. Sign in as administrator, open Self Update, and upload the release ZIP.
  3. An administrator initiates staging. The application checks version lineage and package integrity; the protected approval-registry/key is not required by this development source.
  4. The existing external updater installs the application. Verify the reported version, client operations, authorization, data integrity, and recovery capability using an approved test plan.
  5. The bundled updater is not automatically installed by this flow. Installing a newer external updater requires a separate, explicitly planned operation with rollback.

Recovery warning

The supplied v0.1.22 external updater has known source-audit concerns: previous backup removal before new backup verification, archive retention of only two indexed packages, and insufficient failure-path checks. Stage 3 deployment-safety remediation and live interruption testing are pending. Do not assume that a successful normal update proves rollback safety.

Release gate

For a release candidate, run the validator from the extracted application directory, supplying both the candidate ZIP and its actual predecessor ZIP:

python3 tools/validate-release.py /path/to/KIP-Interfaces-v0.1.46.zip /path/to/KIP-Interfaces-v0.1.44.zip

The candidate filename is illustrative only; v0.1.46 is a development checkpoint, not an approved release. The validator requires both ZIP arguments and cannot establish semantic correctness, installed updater compatibility, or deployment approval.

External updater compatibility: v0.1.46 source requires updater v0.1.36 or newer. The server's previously observed v0.1.22 updater cannot complete this upgrade through the current Self Update form. A separate manual updater installation is currently required by the source; the requested browser-only migration is not implemented and blocks release.

Historical release notes and development appendices

Earlier checkpoint descriptions are retained in the versioned Release-Notes-v0.1.41.md through Release-Notes-v0.1.44.md and historical continuity records. They do not describe current v0.1.46 behavior.