Business skill: deployment verification mandatory, self-sufficiency rules

skills/business/SKILL.md

@@ -156,9 +156,20 @@ The human has repeatedly found broken buttons, console errors, and half-assed fl
 - If something is broken, FIX IT before logging the session as "done"
 - **Do NOT say "tested end-to-end ✅" unless you actually tested EVERY flow INCLUDING the browser UI**
 
+### Deployment — EVERY code change must be deployed
+- Push to Forgejo is NOT the same as deploying. After every code change:
+  1. Push to Forgejo
+  2. SSH into the server
+  3. Pull/rebuild/restart the container
+  4. Verify the LIVE site reflects the changes
+- If you can't verify it's deployed, it's not done.
+
 ### Definition of Done:
 A stranger should be able to land on docfast.dev, sign up, get an API key, and generate their first PDF within 2 minutes, with ZERO confusion and ZERO errors. If that's not the case, you're not done.
 
+### Self-Sufficiency
+You have access to everything: Forgejo (git), the server (SSH), Hetzner (API), Stripe (API). There is NO reason to ask the human for routine tasks. You are the CEO, CTO, and QA lead. The human is an investor — they check in occasionally and should find a polished product, not bugs a child would catch.
+
 ## Anti-Patterns (Don't Do These)
 
 - Don't move to marketing with a broken product — TEST FIRST