Use this page while Talk-to-Tux is in alpha/private beta. It is intentionally temporary and can be deleted before the public launch.
Before You Start
- Open
https://www.talk-to-tux.com. - Sign in through Cloudflare Access with GitHub.
- Use the GitHub email that was added to the Cloudflare Access tester allowlist.
- If you are a Consiliency GitHub organization member, use the GitHub account attached to that membership.
- If you are a temporary debugger, use the exact email that was explicitly allowed for alpha testing.
- Test in your normal desktop browser.
- Also test on a mobile device or mobile viewport if you can.
- Capture screenshots for anything that looks wrong.
- Do not ask for or accept a Cloudflare account seat; testers should only pass through Cloudflare Access.
Access Gate
- You see a Cloudflare Access or GitHub login screen before the site.
- GitHub authentication completes without a loop.
- You land on the Talk-to-Tux homepage after login.
- Open
/smokeafter login and confirm this checklist is reachable. - If blocked, record the Cloudflare error, the GitHub account used, the email GitHub shows, and whether the page denies access clearly instead of looping.
- If you expected to be allowed, do not retry with a different identity until the failed attempt has been reported.
Required Alpha Identity Checks
The alpha coordinator should make sure all three identity paths are tested before ALPHA is treated as complete.
- Consiliency GitHub org member: sign in with GitHub, reach
/, and then reach/smoke. - Temporary debugger: sign in with the exact allowlisted GitHub email, reach
/, and then reach/smoke. - Blocked user: try a GitHub account that is not in Consiliency and not on the temporary debugger allowlist; confirm Cloudflare shows a clear denial instead of looping or landing on the site.
For each identity check, record the tester class, timestamp with timezone, route reached or denial shown, and whether the Cloudflare Access audit log has the matching allowed or denied event.
Website Routes
Open each route and check that the page loads, the header/footer work, and the layout does not break.
//apply/privacy/terms/beta-terms/security/smoke
Visual Front-End Smoke
- Dark grid background renders consistently.
- Hero image appears and is not blurry, stretched, clipped, or missing.
- Favicon appears in the browser tab.
- Header spacing is clean at desktop and mobile widths.
- Nav links and buttons do not overlap.
- Text does not overflow cards, buttons, panels, or the viewport.
- There is no horizontal scroll on mobile.
- The bottom of the page has no dev toolbar, blank strip, or rendering artifact.
- Cards/panels line up cleanly and spacing feels intentional.
- Focus states are visible when tabbing through the page.
- Desktop and mobile results exist for each route, even when the result is pass.
Apply Form Smoke
Do not submit real beta applications unless asked.
- Required fields are clearly labeled.
- Empty required fields show understandable errors.
- Keyboard tab order moves through the form in a sensible order.
- Legal checkboxes are visible and readable.
- Links to Terms, Privacy, Beta Terms, and Security open the right pages.
- The submit button state is clear.
- If you submit a test application, use
SMOKE TESTin the use-case field and report the timestamp.
Desktop App Smoke
Run this section only if you were asked to test the app itself.
- Install from the provided alpha/beta instructions.
- Launch Talk-to-Tux from a terminal so errors are visible.
- Confirm the app starts without crashing.
- Confirm the trigger button or configured hotkey is detected.
- Record a short phrase and confirm text appears where expected.
- Test smart-paste in at least one normal app, such as a browser text field or editor.
- Confirm obvious failure states are understandable, such as missing microphone permission or missing API configuration.
- Do not share private transcripts, screenshots, API keys, logs with secrets, or sensitive app content.
Privacy-Safe Artifacts
- Screenshots and recordings should show only the website or test app state.
- Redact emails, tokens, private transcripts, local filenames, terminal secrets, browser profiles, and unrelated tabs before attaching artifacts.
- For Access problems, include the Cloudflare error text and timestamp, but do not attach raw cookies, session tokens, or one-time login links.
- For apply-form testing, use test content only and include
SMOKE TESTin the use-case field if you were explicitly asked to submit.
Report Destination
File alpha findings as GitHub issues in ViperJuice/talk-to-tux using the
Alpha smoke report template. Apply these labels:
alpha-smokeseverity:blockerseverity:majorseverity:minorpolish
Use one issue per distinct finding. Group duplicates by linking to the first issue instead of opening another copy.
Report Format
Copy this format for every issue.
Tester:
GitHub email used:
Device/browser:
Route or app area:
Pass/fail:
Screenshot or screen recording:
Issue:
Expected:
Actual:
Severity: blocker / major / minor / polish
Timestamp with timezone:
Access path: Consiliency org / temporary debugger / blocked user / not access-related
Severity Guide
blocker: prevents access, form use, install, launch, or basic app operation.major: visible broken layout, unreadable content, broken navigation, or misleading state.minor: rough behavior that does not stop the workflow.polish: copy, spacing, alignment, or fit-and-finish issue.
Operator Evidence Checklist
The alpha operator should record these items in the phase evidence artifact:
- Public DNS result for
www.talk-to-tux.com. - Unauthenticated Access redirect result for
/,/apply,/privacy,/terms,/beta-terms,/security, and/smoke. - Consiliency GitHub org member login result.
- Temporary debugger email login result.
- Blocked-user denial result.
- Cloudflare Access audit events for allowed and denied attempts.
- Desktop and mobile visual smoke result for every required route.
- Keyboard focus smoke for
/,/apply, and/smoke. - GitHub issue links or no-action rationale for every human finding.
Current Alpha Completion Items
Before declaring ALPHA done, make sure these have explicit pass evidence or a named blocker in the phase evidence artifact:
- Temporary debugger email login reaches
/smoke. - Blocked-user denial is observed without a redirect loop.
- Cloudflare Access audit logs include at least one allowed event and one denied event.
- Desktop and mobile route smoke exists for
/,/apply,/privacy,/terms,/beta-terms,/security, and/smoke. - Any human findings are filed, linked as duplicates, or recorded as no-action with rationale.