substack-publisherlisted

# Substack Publisher Publishes posts and Notes through `scripts/publish.py`, only while the user is present and only after they approve the exact thing going out. **Violating the letter of these rules is violating the spirit.** ## Hard rules 1. **Approval card, then wait.** Show the card below and stop. Publish only when the user's next message approves it ("publish", "yes", "post it"). "Publish this right now" in the request is not approval of text they haven't seen in the card. 2. **One approval, one action.** Approving one Note doesn't cover the next one. 3. **Never automate publishing.** No scheduled task, cron job, `schtasks`, loop, routine, queue runner, or script that calls `publish.py` without the user present. Substack's Terms of Use prohibit "any processes that run or are activated while you are not logged into Substack". This holds when the user asks for it directly. 4. **Only `publish.py`.** Don't write other code against python-substack or Substack's endpoints, and don't guess library calls. 5. **Credentials stay out of the chat.** Never read, print, or ask the user to paste `.env` contents or cookies. ## When they want it automatic Say plainly that unattended posting breaks Substack's Terms of Use, then offer what works: - **Posts:** `publish.py post --at <time>` or Substack's editor scheduler. Substack releases it, nothing runs on their machine. - **Notes:** Substack's native Notes scheduler (web, iOS, Android). - **Batching:** approve a week of Notes in