Task: Capture scheduler runbook evidence and failure handling

[KazanderDad]

Parent Goal: #80
Depends on: Scheduler configuration and queue drain proof
Blocks: Production go/no-go evidence

Objective

Capture scheduler runbook evidence, including cadence, monitoring, failure handling, and operator escalation.

Expected Surfaces

• docs/engineering/wallet-release-runbook.md
• Goal Goal: Prove Supabase-side worker scheduling #80 evidence comments
• Release-alignment workflow/health outputs

Scope

• Confirm runbook instructions match actual scheduler design.
• Record how operators verify scheduler health.
• Record failure/retry/escalation guidance.

Non-Goals

• Do not create a separate evidence packet issue.
• Do not expand into unrelated Edge Function hardening.

Guardrails

• Evidence stays on Goal Goal: Prove Supabase-side worker scheduling #80.
• Keep instructions operational and specific.

Acceptance Criteria

• Scheduler runbook evidence is captured on Goal Goal: Prove Supabase-side worker scheduling #80.
• Any repo doc updates needed for scheduler operations are committed through a normal PR if required.

Validation Plan

• Review runbook against actual scheduler settings.
• Confirm evidence links and commands are present.

Stop Condition

Stop after scheduler runbook evidence is captured or doc update work is explicitly opened.

[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.

[KazanderDad]

Implementation evidence

Commit: 8cb1be6 (docs: capture scheduler runbook evidence (#90))

What changed:

• Expanded docs/engineering/wallet-release-runbook.md with scheduler operator verification steps.
• Documented the exact health fields to inspect after a manual drain/scheduled run.
• Added failure handling for one-off timeout, repeated timeout, stale/blocked queue, and scheduler-provider limitations.
• Kept evidence expectations on Goal Goal: Prove Supabase-side worker scheduling #80, per the Sprint guardrail.

Validation:

• pnpm exec vitest run services/indexer/src/touchQueue.test.ts
• pnpm exec tsc --noEmit --pretty false
• pnpm lint
• git diff --check

Boundary check:

• Docs/runbook only.
• No linked Supabase writes were run.
• No unrelated Edge Function hardening or separate evidence-packet issue was created.

[KazanderDad]

Issue Validator result

Result: pass-with-notes

Target issue: #90
Commit reviewed: 8cb1be6

Evidence reviewed:

• Implementation evidence comment on Task: Capture scheduler runbook evidence and failure handling #90.
• Goal Goal: Prove Supabase-side worker scheduling #80 runbook evidence comment.
• Commit diff for runbook and session log updates.

Validation rerun:

• pnpm exec vitest run services/indexer/src/touchQueue.test.ts passed.
• git diff --check passed.
• Previously recorded implementation validation also included pnpm exec tsc --noEmit --pretty false and pnpm lint, both passing.

Boundary check:

• Documentation/runbook only.
• No linked Supabase writes were run.
• No unrelated Edge Function hardening was included.
• Evidence remained on Goal Goal: Prove Supabase-side worker scheduling #80 rather than a separate evidence-packet issue.

Notes:

• Scheduler runbook evidence and failure handling are captured.
• This remains pass-with-notes because the actual hosted recurring scheduler cannot be enabled until a human approves the linked Supabase/operator action and a safe Preview queue-drain request is proven.

Ready for Project status: In Review.