Initial commit: VaultMesh Skills collection

Collection of operational skills for VaultMesh infrastructure including:
- backup-sovereign: Backup and recovery operations
- btc-anchor: Bitcoin anchoring
- cloudflare-tunnel-manager: Cloudflare tunnel management
- container-registry: Container registry operations
- disaster-recovery: Disaster recovery procedures
- dns-sovereign: DNS management
- eth-anchor: Ethereum anchoring
- gitea-bootstrap: Gitea setup and configuration
- hetzner-bootstrap: Hetzner server provisioning
- merkle-forest: Merkle tree operations
- node-hardening: Node security hardening
- operator-bootstrap: Operator initialization
- proof-verifier: Cryptographic proof verification
- rfc3161-anchor: RFC3161 timestamping
- secrets-vault: Secrets management

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

dns-sovereign/references/cloudflare_dns_mirror_notes.md

@@ -0,0 +1,16 @@
+# Cloudflare DNS Mirror Notes
+
+This skill treats Cloudflare as a **mirror**, not the source of truth.
+
+## Mirror Records File
+Create: outputs/mirror_records.json
+
+Example:
+[
+  {"type":"A","name":"app","content":"1.2.3.4","ttl":120},
+  {"type":"CNAME","name":"git","content":"app.example.com","ttl":120}
+]
+
+## Rollback
+When mirroring, record IDs are saved in outputs/cloudflare_record_ids.txt.
+undo_cloudflare.sh will delete those IDs (best effort).

dns-sovereign/references/powerdns_notes.md

@@ -0,0 +1,12 @@
+# PowerDNS Notes
+
+## v1 Design
+- Authoritative server: powerdns/pdns-auth (Docker)
+- Backend: sqlite3 in PDNS_DATA_DIR
+- API enabled and published to localhost only
+
+## Production Hardening
+- Run behind firewall; restrict UDP/TCP 53 to known resolvers or public as needed
+- Keep API bound to localhost
+- Consider a second NS (ns2) on a separate node/provider for resilience
+- Back up PDNS_DATA_DIR using backup-sovereign