Castle Raid · Operator QA

Web Alpha 1 · Evidence and follow-up
Track QA cases, failures and actions in Forgejo issues. Record and export your observations here. For a failed or blocked step, review its issue draft and open Forgejo to submit it, then record the filed issue URL. Your run stays in this browser until you export or explicitly share it.
Loading plan…
Run identity and tested environment

Save a full tested commit and environment name before recording a step. The candidate and environment lock after the first recorded outcome.

These references remain editable; they do not change the tested candidate.

No automatic gate promotion

Preconditions
    Expected result

      Evidence

      Pass and fail require evidence. Synthetic-only passes never qualify for case acceptance. Use redacted references, not credentials or raw player identifiers.

      Required for fail or blocked.

      Record a failure or blocker first. After filing, paste its issue URL above and record the update.

      Actions and dependencies

      Track an exact follow-up across steps and gates. Resolving an action does not change any step outcome. Resolved or outside-alpha actions require evidence.

      Review your Forgejo issue

      Check the title and remove private information before opening Forgejo. Sign in there to update the linked issue or search for an existing one before submitting.

      Open in Forgejo ↗