zeus-failure-archaeology

Chronicles verified Zeus repository incidents, reverts, and root causes with commit-hash evidence.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/aswin-dev-debug/Ai-Finance-analyzer --skill zeus-failure-archaeology-aswin-dev-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zeus-failure-archaeology
Source: https://github.com/aswin-dev-debug/Ai-Finance-analyzer/tree/main/lib/zeus-contrib/zeus/.claude/skills/zeus-failure-archaeology
Command: npx skills add https://github.com/aswin-dev-debug/Ai-Finance-analyzer --skill zeus-failure-archaeology-aswin-dev-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers repeatedly re-attempt fixes that were already tried, merged, and reverted in the Zeus Lightning wallet repository, wasting effort and risking regressions. This Skill provides a verified chronicle of every major investigation — symptom, root cause, evidence (commit hashes and PRs), and status — so no one re-fights a settled battle. ## Core Features & Use Cases - Incident Chronicle: Twelve documented failure entries (FA-1 through FA-12) covering iCloud keychain migrations, React Native/Fabric upgrades, settings corruption, Tor TLS, navigation regressions, LDK Node crashes, embedded LND database flips, and more, each with verified commit hashes and lessons. - Meta-Pattern Detection: Documents the rapid-revert policy (MP-1) and the stalled-branch graveyard (MP-2), teaching you to check for revert-<PR#> branches before trusting any merged fix. - Verification Commands: Provides copy-paste git and grep one-liners to confirm any cited hash, version pin, or migration flag against the current master snapshot. - Use Case: Before proposing a keychain cleanup migration, consult FA-1 to learn that three prior attempts failed, deletion is deliberately disabled, and the standing rule is namespace-and-retain. ## Quick Start Ask the assistant to check the Zeus failure chronicle before attempting a fix for stale wallet data appearing on a new iOS device.

Frequently Asked Questions about zeus-failure-archaeology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a Zeus bug was already fixed or reverted?

Search the chronicle's symptom index for a matching entry, then verify the cited hashes with git log and git merge-base --is-ancestor. Also run git log --grep='revert-<PR#>' to confirm the fix was not later reverted.

What should I check before proposing a keychain migration in Zeus?

Review entry FA-1, which documents three failed iCloud keychain attempts. The standing rule is to never delete keychain data: namespace new entries with the zeus: prefix, set cloudSync: false, and leave old entries as harmless orphans.

Why does the Zeus app crash on New Architecture after the React Native upgrade?

Fabric enforces stricter layout invariants than the legacy renderer, so pre-2026 Animated and layout patterns crash screen-by-screen. FA-2 documents the WalletHeader and keypad crashes and their verified fixes.

Can I trust a merged Zeus PR as the final resolution?

Not automatically. The repository reverts regressions found in release testing, often the same day, via auto-revert branches with empty commit messages. Always check for a revert-<PR#> merge before building on any recent fix.

When should I not use this failure chronicle?

Use a sibling skill instead for live debugging of new symptoms, current storage and migration mechanics, standing change-control rules, or architecture rationale. This chronicle covers settled historical incidents, not active triage.