security: add optional archive integrity verification

.gitignore

@@ -1,10 +1,12 @@
 __pycache__
 config.json
 .mp/
+.playwright-mcp/
 venv/
 Songs/
 google-maps-scraper-0.9.7/
 niche.txt
 *.exe
 auto.sh
-.DS_Store
+.DS_Store
+excalidraw.log

AGENTS.md

@@ -1,5 +1,56 @@
 # Repository Guidelines
 
+## Current Product Direction
+- This fork is Frank's custom `MoneyPrinter`, not a generic client-acquisition helper.
+- Prioritize business layers in this order:
+  - `Asset Printer`: reusable content assets, checklists, SOPs, templates, comparison pages.
+  - `Lead Printer`: owned audience, subscribers, repeat traffic, search/social entry points.
+  - `Cash Printer`: selective service revenue only as bootstrap support.
+- Strategy test for new work:
+  - Prefer features and content that create reusable assets, strengthen owned audience, or improve low-touch monetization.
+  - Avoid changes that mainly optimize for selling more hours or turning the repo into a generic agency machine.
+- Current first asset path:
+  - free asset first: `开源 AI 项目部署前检查清单`
+  - then paid asset: launch / hardening SOPs, templates, or other low-touch digital products
+- Site positioning:
+  - `fzhang.dev` should remain content-first.
+  - Homepage CTA should bias toward owned-asset capture, not hard service selling.
+- Canonical strategy docs:
+  - `docs/FrankMoneyPrinter.md`
+  - `docs/Roadmap.md`
+  - `docs/FirstAssetSpec.md`
+  - `docs/FinancialFreedomPath.md`
+  - `docs/FzhangHomepageCopy.md`
+  - `docs/ShopPaymentArchitecture.md`
+- When work touches agent-facing site structure, AEO / GEO, AI citation visibility, or how `fzhang.dev` / `shop.fzhang.dev` should be optimized for agents and LLM discovery, also consult the upstream `GEO` repo at:
+  - `/Users/frank_zhang/Documents/文稿 - Frank's MacBook Air/Github项目/GEO`
+
+## Cross-Project Financial Freedom Context
+- This repo should be evaluated as one lane inside Frank's broader financial-freedom system, not in isolation.
+- Canonical cross-project references for that system:
+  - `docs/FinancialFreedomExecutionStack.md`
+  - `docs/Roadmap.md`
+  - `/Users/frank_zhang/Documents/文稿 - Frank's MacBook Air/Github项目/paperclip/doc/plans/2026-03-31-paperclip-financial-freedom-positioning.md`
+  - `/Users/frank_zhang/Library/Mobile Documents/com~apple~CloudDocs/Obsidian 库/5.知识库/07个人成长/08财务自由之路/1当前财务自由系统的项目分工与顺序（2026-03-31）.md`
+- When work touches monetization order, project prioritization, `fzhang.dev`, asset funnels, paid SOPs/templates, bootstrap services, or possible `paperclip` integration, consult the references above before making strategic changes.
+- When work touches `shop.fzhang.dev`, payment processors, subscriptions, refunds, billing, entitlement sync, or order mirrors, consult `docs/ShopPaymentArchitecture.md` first.
+- `InsForge` should not be introduced by default. Re-evaluate it only if `shop.fzhang.dev` later needs a real internal backend for entitlements, order mirrors, admin operations, and repeated backend iteration after payment integration is already stable.
+- Current cross-project operating model:
+  - `cash flow survival layer + asset compounding layer + product optionality layer`
+  - `MoneyPrinterV2` is the current main execution repo for the asset-compounding layer.
+  - `fzhang.dev` is the trust, traffic, and owned-audience surface.
+  - The knowledge base is a source-material and evidence ledger, not just storage.
+  - `paperclip` is currently later-stage product optionality, not the main short-term monetization engine.
+- Guardrail:
+  - Do not let `paperclip` or other product bets consume execution budget needed for the current asset loop:
+    - close the checklist funnel
+    - verify email delivery and tagging
+    - publish monetizable long-tail content
+    - validate paid SOP / template demand
+    - build proof from real traffic, downloads, replies, and purchases
+- Promotion rule:
+  - Larger product bets should be activated by repeated external proof, not by excitement alone.
+
 ## Project Structure & Module Organization
 - `src/` contains the application code. Use `src/main.py` as the interactive entrypoint.
 - `src/classes/` holds provider-specific components (for example `YouTube.py`, `Twitter.py`, `Tts.py`, `AFM.py`, `Outreach.py`).

README.md

@@ -1,5 +1,7 @@
 # MoneyPrinter V2
 
+Frank's fork is being repurposed from a generic faceless-content tool into a long-term income asset printer: long-tail content generation, cross-platform distribution, owned-audience capture, and monetization experiments around AI / developer workflows.
+
 Sponsored by Post Bridge
 
 <a href="https://www.post-bridge.com/?ref=moneyprinter">
@@ -15,8 +17,8 @@ Sponsored by Post Bridge
 [![GitHub stars](https://img.shields.io/github/stars/FujiwaraChoki/MoneyPrinterV2?style=for-the-badge)](https://github.com/FujiwaraChoki/MoneyPrinterV2/stargazers)
 [![Discord](https://img.shields.io/discord/1134848537704804432?style=for-the-badge)](https://dsc.gg/fuji-community)
 
-An Application that automates the process of making money online.
-MPV2 (MoneyPrinter Version 2) is, as the name suggests, the second version of the MoneyPrinter project. It is a complete rewrite of the original project, with a focus on a wider range of features and a more modular architecture.
+An application that automates repetitive parts of online monetization.
+MPV2 (MoneyPrinter Version 2) is, as the name suggests, the second version of the MoneyPrinter project. This fork keeps the modular core, but is being redirected toward owned content assets, conversion paths, and low-touch revenue experiments instead of pure service lead generation.
 
 > **Note:** MPV2 needs Python 3.12 to function effectively.
 > Watch the YouTube video [here](https://youtu.be/wAZ_ZSuIqfk)
@@ -27,6 +29,19 @@ MPV2 (MoneyPrinter Version 2) is, as the name suggests, the second version of th
 - [x] YouTube Shorts Automator (with CRON Jobs => `scheduler`)
 - [x] Affiliate Marketing (Amazon + Twitter)
 - [x] Find local businesses & cold outreach
+- [x] Service-led content profiles for case-study style YouTube / X accounts
+- [x] Cross-post YouTube uploads to TikTok / Instagram via Post Bridge
+
+## This Fork's Goal
+
+This fork is being re-optimized around long-term monetizable assets:
+
+- publish reusable content with long-tail utility
+- turn distribution into owned audience instead of one-off impressions
+- direct attention toward assets such as newsletters, resource packs, templates, and selective affiliate offers
+- treat service revenue as optional bootstrap fuel, not the end state
+
+See [docs/FrankMoneyPrinter.md](docs/FrankMoneyPrinter.md) for the specialization strategy, [docs/FinancialFreedomPath.md](docs/FinancialFreedomPath.md) for the staged monetization path, [docs/FirstAssetSpec.md](docs/FirstAssetSpec.md) for the first asset decision, and [docs/Roadmap.md](docs/Roadmap.md) for the implementation phases.
 
 ## Versions
 

config.example.json

@@ -13,6 +13,7 @@
   "zip_url": "",
   "is_for_kids": false,
   "google_maps_scraper": "https://github.com/gosom/google-maps-scraper/archive/refs/tags/v0.9.7.zip",
+  "google_maps_scraper_sha256": "",
   "email": {
     "smtp_server": "smtp.gmail.com",
     "smtp_port": 587,

docs/CaseBriefTemplate.md

@@ -0,0 +1,34 @@
+# Case Brief Template
+
+Use one file like this per repeatable content angle or client-safe case study.
+
+```md
+# Case Brief
+
+## Context
+- Project:
+- Customer type:
+- Starting situation:
+
+## Problem
+- What was broken, risky, or blocked?
+- What did most people miss?
+
+## Work Performed
+- Deployment steps:
+- Hardening steps:
+- Customization steps:
+
+## Outcome
+- What changed?
+- What business or technical result mattered?
+
+## Safe-To-Publish Notes
+- What details must stay generic?
+- Which tool / stack names are safe to mention?
+
+## CTA Direction
+- Which offer should this case study lead into?
+```
+
+Then store the file anywhere inside the repo and reference its relative path when creating a YouTube or X account.