Files
archy/Release & Testing/Detailed Plans/05-Guarded-Installed-UAT.md

13 KiB
Raw Permalink Blame History

Sanitized detailed source transcription S05, captured 2026-10-24. Original planning steps, acceptance criteria and historical evidence are retained rather than condensed. Read current context and precedence first: dated holds, approvals, test counts and “latest” labels below belong to their original checkpoint and do not grant current execution/publication authority. Privacy replacements preserve roles and test semantics. See section coverage.

Guarded incremental operator node UAT

Authority: operator requested coherent qualified parts be delivered to operator node and now authorized development execution. This is a scoped candidate delivery allowance, not blanket spending/publication/hardware/other-node authority. CI workers NEVER access production. Only the authorized coordinator applies a reviewed frozen batch through the verified managed path.

Current state (2026-10-14): operator UAT of the prior candidate is FAILED/WITHDRAWN because it showed the old interface, omitted the Archipelago source, and advertised a false update. A guarded frontend-only correction is installed as PRIVATE_Y1_UAT_PENDING_RETEST; do not call Y1 operator UAT passed until the operator confirms the visible source and update state. The correction requires dynamic same-origin /relay at immutable build time, aligns the runtime repository/version identity with the app catalog, and makes the PWA shell revalidate. The current frontend is the corrected node-source d6f9046… artifact; API remains 0be4165…. Exact image IDs, 110 migrations, listener/health, served-byte identity, provider policy, backup validation, data/operation-boundary preservation, core restart and delayed anti-reversion passed. Installed 390px/1440px browse, film-details focus/Escape/restore, sign-in dialog focus/Escape/restore, responsive overflow, unauthenticated Backstage boundary, and all four anonymous upload denials passed. Authorized synthetic UAT also passed native sign-in, JWT/profile identity matching, profile-menu SPA navigation to Backstage, UI private-project creation, authenticated multipart initialize/abort, supported project deletion, UI sign-out, credential clearing and native-selection clearing. Actual installed Cloud connector and complete computer-file transfer remain NOT_RUN; disposable pinned-MinIO restart/resume and full-API authority/revocation passed. Two synthetic accounts and one inaccessible unpublished draft remain because no owner self-delete API exists and direct DB/admin cleanup was prohibited. Canonical IndeeHub acceptance and independent review remain unresolved; this installation is not release qualification or authority for funds, publication, exposure, or a second node. Retain the runner-owned two-service pins and validated rollback inputs until an accepted signed catalog selects the exact images.

Batch plan

Batch Coherent deliverable Minimum task evidence before delivery
Y1 original-style identity/Backstage UI; Mesh rendering slice if diagnosed T00/T01/T02, T03/T04 and affected T28 G1–G3; no unsupported payment promises
Y2 publication/catalog/shared discussion T05/T06 plus prior dependencies G1–G3; actual public posts need separate approval
Y3 native/external checkout, rentals, original zaps and FIPS player T07/T08/T09/T12/T26 plus prior dependencies G1–G3, funds/security independent review
Y4 bounded ecash streaming, profits, safe app update and availability T25/T27/T11, T10 when exposing replica promises; integrated monetary recovery evidence
Y5 coherent Cloud/connectivity/system/developer slices T13/T16/T17/T20/T21 as applicable, shared dependency regressions, not one unchecked omnibus
Y6 hardware/public-channel, tunnels and sharing T18/T19/T14; hardware/network mutation separately authorized
Y7 completed media/background and last artwork fix T15 and affected companion/device gates
Final frozen integrated app/backend/UI/APK candidate T22/T23, all mandatory source/integration/artifact gates and explicit outstanding physical scope

Batch numbers describe product grouping, not authority to deploy incomplete dependencies. Split only when install/runtime contracts remain compatible and user-visible controls are truthful. Do not ship an enabled mock payment feature or half-updated schema. Current ledger deployment_ready=false for all tasks.

Before any mutation (record private evidence)

  1. Verify current node identity, platform, lifecycle owner and supported installed versions through approved local access configuration. Do not paste endpoints, keys or private inventories into Git/logs here. Stop if identity/ownership differs from expectation.
  2. Freeze candidate component commits, review dispositions, image digests/artifact hashes, capability compatibility and affected units. Require G1–G3 appropriate to slice and no known blocker. Record prior candidate/user UAT status; do not silently overwrite it.
  3. Record identities, wallet/account availability and monetary operation IDs/status WITHOUT secrets; app inventory/uninstall tombstones, files/drafts/comments, permissions and volumes. Inspect pending jobs/purchases/zaps/chunks and admission controls.
  4. Verify scope-specific consistent backups and a tested restore path with ownership/permissions and enough space. Rehearse rollback on disposable equivalent nonempty monetary state. Preserve current code/images/config before update.
  5. Specify exact managed commands, health endpoints, expected versions, restart set, timeout and stop conditions from current tooling. This document is not an executable blind SSH script. Notify operator of intended slice/restarts and UAT steps; no surprise broad outage.
  6. Obtain extra approval where needed: new spending total including fees/recipient/network; public publication/comments/zaps; hardware/RF/reboot; peer-node changes; destructive migrations; release signing/publication. Old historical caps are invalid for new spends.

Apply and headless smoke

  • Drain/block new writes as required by reviewed update journal; wait for safe pending-operation boundary. Do not terminate an uncertain financial operation to force progress.
  • Apply exact frozen candidate via native managed update/lifecycle ownership path. Never edit inside a running container as the final fix or copy a dirty source tree.
  • Verify installed AND served bytes/versions, startup/readiness, migration state, correct native identities, app login/sign-out, catalog access and no unexpected restarts/resurrected apps. Check unrelated wallet/service health and source data preservation.
  • Exercise applicable money-free functional paths and previously paid access WITHOUT repayment. Verify FIPS diagnostics and pending state. No actual purchase/public event unless separately approved.
  • Capture result per gate. Healthy services are not functional UAT. Give operator the exact deployed version/hash, visible changes, click path/expected outcome, known limits and what remains untested.

Operator scenarios

Y1: original navigation/black modals, film details/social controls then checkout, original player, original orange zap amounts. Native account swap/logout. Backstage Cloud/computer selection, save/reopen, processing/retry, draft privacy. Mesh only after sanitized root-cause proof; confirm device sender header, intact body, icon-only audio when clarified.

Y2: approved film publish on P, unrelated B/C late discovery, shared comment/reply/reaction identity and offline catch-up, withdrawal and private master denial. Public event authorization is a separate gate.

Y3: each native/external rail availability/fee/review/pending/recovery; original approval boundary and no BTCPay. Paid-ready first play, expiry/renewal, FIPS-only play/seek and recovery. Zap pending/confirmed separate from rent and once-only totals. Real-funded steps require explicit cap; destructive faults remain isolated.

Y4: set zero/finite ceiling, chunks/spend/reserved/remaining, pause/stop, below-next-chunk stop, raise without history reset, paid retry without another debit. Networking Profits receipts reconcile pending/confirmed/creator/network income without private budgets. Approved replica failover only if qualified.

Y5–Y7: specialize mapped parent-plan scenarios for connectors, requests/Fleet/HTTPS/AI/terminal/apps, standard public radio, routes/sharing and physical media/artwork. Do not label a unavailable hardware case passed because its UI loads.

Prepared two-node IndeeHub qualification (operator node + separately approved peer)

This stage follows a successful operator node single-node smoke; it is not permission to mutate a second node. Before using approved peer node or any other peer, obtain explicit approval naming both nodes, exact immutable artifact/manifest, restart scope, backup/rollback plan, test identities, and whether private test publication is permitted. Default scope is no funds, no public events, no DNS/firewall change and no hardware mutation.

  1. Freeze and compare: verify both nodes start from recorded installed/served hashes and supported schema/protocol revisions. Do not overwrite a different candidate or copy a operator node worktree. Back up each node independently and prove restore on disposable equivalents.
  2. Authority isolation: select distinct test identities A and B. Confirm opening a peer listing never transfers cookies, signer, wallet bridge, Backstage routes, file authority or owner session. A sign-out/account switch must not affect B.
  3. Read-only discovery first: with no new publication, verify native peer discovery is bounded and uses authenticated node transport; fixed browser peer lists are absent. An unavailable peer must retain the last verified catalog and must not substitute demo data.
  4. Private publication only if separately approved: publish one synthetic non-sensitive fixture from A to the approved private test relay/transport. Verify B and a restarted/late B discover the same signed film identity and revision; a draft and private master remain unavailable. Do not post to public relays under this procedure.
  5. Discussion only if separately approved: use synthetic comments/replies on the private fixture, then partition/reconnect and verify exact signed-event deduplication and stable film discussion identity. Otherwise record this step NOT_RUN, not passed.
  6. Money-free rental protocol: inspect offered methods and consent screens without approving a spend. Producer-side unavailable choices show only “Not offered.” Cancellation creates no invoice/token/transaction. Existing previously paid synthetic entitlement may be replayed only from isolated fixtures; never pay again for recovery.
  7. FIPS transport: request authorized fixture media from B and verify remote bytes traverse authenticated FIPS while browser delivery remains local-node presentation. Deny FIPS and confirm fail-closed/no fallback/no repayment; restore and recover the same entitlement. Real media and protected keys require their normal authorization.
  8. Faults and recovery: restart one peer, interrupt discovery/media preparation, and restore connectivity. Confirm bounded retries, original operation identity, no duplicate publication/payment, no leaked private route, and no service/resource runaway.
  9. Evidence: record sanitized source pins, installed/served hashes, role-labelled node results, exact scenario pass/fail/blocked state and resource observations. Keep endpoints, machine identifiers, credentials, wallet data and raw operational evidence outside repository artifacts.
  10. Rollback: if either node shows identity/data loss, authority leakage, unexpected financial activity, FIPS bypass, wrong artifact or unhealthy unrelated services, stop both-node testing and follow the per-node rehearsed rollback/reconciliation procedure.

A successful operator node-only run is not node-to-node acceptance. A successful two-node source simulation is not installed-node acceptance, and operator node + approved peer node do not substitute for an unrelated late third-node test required by T05.

Failure and rollback

Stop new rollout on unexpected money movement, auth/FIPS bypass, missing data/identity, unknown migration state, unhealthy wallet/unrelated apps, wrong artifact or writer-drain failure. Preserve diagnostics and current journals before intervention. Reconcile external settlement before restoring monetary state; NEVER blindly revert live wallet/receipt databases to an older snapshot. Distinguish code rollback, schema/data restore and irreversible external effects.

Use the rehearsed owner-aware rollback only if safe for current state; otherwise keep service restricted/read-only and escalate with original operation IDs and reviewed recovery plan. Report restored vs forward-committed accurately. Verify served old hashes, health/data and affected user recovery. No reinstall/reset/prune or payment replay as troubleshooting.

Every UAT failure becomes a ledger defect with repro, owner, fix commit, focused rerun, dependency regression and rebuilt artifact. An amended batch gets a new immutable manifest and operator notice. Sign-off applies only to the tested artifact. Final release remains an independent owner action.