Lab idea: make hidden contract drift feel visible. The skill walks the system like a case file, comparing frontend assumptions, API schemas, database reality, jobs, permissions, and docs until the mismatch has nowhere left to hide.
The case
The app looks fine from one layer. Then a field changes name, an enum gains a state, a nullable value becomes required, or a background job mutates something the UI never learned about.
That is the crime scene: every layer is telling a slightly different story.
The detective move
Cross-layer audit should not trust docs first. It should read the code, map the contracts, and produce evidence:
- What the UI sends and expects back.
- What the API accepts, returns, and rejects.
- What the database can actually store.
- What workers, webhooks, and scheduled jobs mutate.
- Where auth, ownership, or status transitions drift.
The payoff
The output is not a vibe report. It is a ranked evidence board: finding, file proof, impact, fix direction, and verification path.
