Skip to content

Validate the combined everyday-use release path #57

Description

@R055LE

Problem

Debug and unit checks have previously missed failures in minified, installed builds. The new identity and multi-session paths need a repeatable release boundary.

Contract

Use disposable test signing material to exercise a minified fixture build through saved-identity unlock, manual prompt replies, automatic command routing, and at least two live sessions. Keep the permanent signing key and its passwords outside public CI. Run an in-place signed owner-device update and invited-tester task checks before treating the grouped flow as accepted.

Acceptance

  • The installed update preserves existing profiles, imported keys, host trust, transcripts, and settings.
  • A trusted saved host connects through the intended one-tap plus unlock path; strict isolated failure leaves the shell usable; masked reply does not enter local history or diagnostics; sessions stay independent.
  • Any release-only or device failure is recorded on its owning implementation issue rather than waived by a debug-only pass.
  • Distribution remains direct invited sharing; public release is a separate decision.

Validation

Record exact CI, fixture, minified APK, signing, installed-update, owner-device, and tester evidence in the repo's normal status/investigation records.

Depends on #47, #48, #52, #54, #55, and #56. Part of #44.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions