Task: Configure GitHub Environment secrets and vars for TCOIN release alignment

[KazanderDad]

Parent Goal: #74
Depends on: none
Blocks: Vercel/env and release workflow validation tasks

Objective

Configure or confirm GitHub Environment secrets and variables needed by TCOIN release-alignment workflows.

Expected Surfaces

• GitHub Environment Preview – tcoin
• GitHub Environment Production – tcoin
• .github/workflows/release-alignment-tcoin.yml
• .github/workflows/supabase-deploy-tcoin.yml

Scope

• Configure secrets/vars directly where permissions allow.
• Confirm required Preview and Production values exist without printing secret values.
• Record missing values or permission blockers on Goal Goal: Align hosted release environments and remote Supabase readiness #74.

Non-Goals

• Do not write linked Supabase database state.
• Do not enable live Buy TCOIN.

Guardrails

• Never print secret values.
• Separate Preview and Production values.
• Linked Supabase writes require separate explicit approval.

Acceptance Criteria

• Required GitHub Environment secrets/vars are present or exact blockers are documented.
• Evidence is added to Goal Goal: Align hosted release environments and remote Supabase readiness #74.

Validation Plan

• Inspect GitHub Environment variable/secret names through permitted APIs/CLI.
• Trigger or prepare release-alignment workflow once env names are confirmed.

Stop Condition

Stop after environment names are confirmed/configured or after exact operator blockers are recorded.

[KazanderDad]

Vetting Note

This issue is part of Sprint #78 and is vetted for the shared implementation branch/worktree below.

Implementation Worktree

• Repo: GreenPill-TO/Genero
• Base branch: origin/dev
• Worktree path: /Users/botmaster/src/greenpill-TO/Genero
• Worktree branch: codex/tcoin-production-launch-readiness
• Use this same worktree for related Sprint Sprint: TCOIN production launch readiness #78 issues: Goal: Align hosted release environments and remote Supabase readiness #74, Goal: Prove Preview sandbox smoke and Buy TCOIN sandbox #79, Goal: Prove Supabase-side worker scheduling #80, Goal: Prove Production smoke and live Buy TCOIN gate #81, and Tasks Task: Configure GitHub Environment secrets and vars for TCOIN release alignment #82-Task: Enforce live Buy TCOIN approval gate and disabled fallback #93.
• Worktree owner: Sprint Sprint: TCOIN production launch readiness #78 / sprint-orchestrator.
• Retain until: Sprint PR is merged and approved-cleanup completes.
• Cleanup owner: sprint-orchestrator via approved-cleanup.
• Do not implement the parent Sprint issue directly; implement unblocked Ready Task issues first, then validate their parent Goal.

Implementation Expectations

• Update code, docs, tests, and agent-context/session-log/ as relevant to the issue.
• Capture evidence directly on the relevant Goal issue, not in a separate evidence packet.
• Never print or persist secret values.
• Do not run linked Supabase writes without explicit just-in-time human approval.
• For UI/browser smoke, provide route/result notes and screenshots or comparable visual evidence when practical.

Issue Validator

After implementation, local validation, session-log update, and commit, the orchestrator must run issue-validator before moving high-risk Tasks or Goals to In Review.

Validator input should include: issue URL, parent issue URL, commit hash, worktree path, changed files summary, validation commands/results, smoke evidence, visual evidence where relevant, non-goals/guardrails, skipped checks, and residual risks.

Expected validator output: pass, pass-with-notes, or fail, with concise evidence and required fixes. The validator reports back to the orchestrator; the orchestrator moves Project status only after validation passes.