fix(cloud): temporarily relax PAYMENT_REQUIRE_NATIVE to restore service

[Svaag]

Incident

cloud.hyrule.host is down (502). hyrule-cloud's startup guard (PAYMENT_REQUIRE_NATIVE=true requires BTC and XMR ready) refuses to boot because monero-wallet-rpc won't start:

• view-key secret was missing → fixed by operator (now a real key);
• but it now fails on invalid wallet password + ringdb permission denied (/home/hyrule/.shared-ringdb).

Not caused by the launch-proof promotion — git diff 270b65d 81e4316 -- hyrule_cloud/app.py is empty; the deploy restart merely exposed a pre-existing Monero bootstrap break.

Change (temporary)

hyrule-cloud.env.ctmpl.j2: PAYMENT_REQUIRE_NATIVE=true → false, so the app boots without requiring native XMR. BTC + x402 USDC still work; native XMR payment temporarily unavailable. Clearly commented as temporary; revert to true once monero-wallet-rpc is healthy.

Validation

• scripts/ci/iac-static.sh — pass
• ansible-playbook playbooks/cloud.yml --syntax-check — pass

Rollout

After merge: apply.yml playbook=cloud limit=api (production gate) → re-renders env + restarts → health check passes → cloud restored.

Follow-up: fix monero-wallet-rpc (wallet password mismatch + ringdb perms), then restore PAYMENT_REQUIRE_NATIVE=true (tracked separately).

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🏅 Score: 75

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Missing Revert Ticket The comment explicitly describes this as temporary but provides no link to a tracking issue or ticket number. In a high-risk infrastructure-as-code repo, a temporary disable with no tracking mechanism is a common operational footgun — it almost always becomes permanent. Add a reference to the follow-up ticket or create one if none exists before merge. # TEMPORARY: set to false to restore service while the Monero wallet-rpc # bootstrap is broken (invalid wallet password + ringdb permission denied on # /home/hyrule/.shared-ringdb). XMR native payment is unavailable until then; # BTC + x402 USDC still work. Restore to true once monero-wallet-rpc is healthy. PAYMENT_REQUIRE_NATIVE=false No Dry-Run Assertion Although the PR description mentions static check and syntax-check passing, there is no evidence that the re-rendered template was validated via the deploy pipeline's dry-run gate (e.g., --check --diff on the Vault-agent template render). A rendered env file with a typo or Vault path issue could take the whole cloud service down again on its own, even if the app boots. Add a CI step or manual verification that the template renders correctly with the actual Vault secrets before merge. # TEMPORARY: set to false to restore service while the Monero wallet-rpc # bootstrap is broken (invalid wallet password + ringdb permission denied on # /home/hyrule/.shared-ringdb). XMR native payment is unavailable until then; # BTC + x402 USDC still work. Restore to true once monero-wallet-rpc is healthy. PAYMENT_REQUIRE_NATIVE=false PAYMENT_BTC_XPUB={{ .Data.data.btc_xpub }}

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5fc8d05a3a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Disable Monero service startup for the mitigation

With the production api inventory still setting hyrule_cloud_monero_wallet_rpc_enabled: true (ansible/inventory/host_vars/api.yml:5), this env-only relaxation does not remove the apply-time dependency on the failed wallet RPC. The cloud apply imports vault.yml before health.yml, and vault.yml still runs state: started for monero-wallet-rpc.service when that flag is true (ansible/roles/hyrule_cloud/tasks/vault.yml:148-154), so in the exact incident described here (invalid wallet password/ringdb permission causing the service not to start) the production apply can fail before the post-deploy health check rather than completing the restore; also disable/bypass that service or make it non-blocking while PAYMENT_REQUIRE_NATIVE=false.

Useful? React with 👍 / 👎.