AlexandrAI AGENTS.md
agents-md

Gumroad Status Snapshot Script Agent Guide

Project-specific AGENTS.md guidance for scripts/gumroad_status.py, read-only command enforcement, status windows, normalized product summaries, buyer-data exclusion, and planning guidance.

AGENTS.md

Guidance for coding agents working on scripts/gumroad_status.py.

Project Overview

scripts/gumroad_status.py creates a read-only seller-owned Gumroad snapshot. It checks auth and product, sales, product-grouped sales, upcoming payout, and payout list data, normalizes a report, writes markdown and JSON snapshots, and avoids buyer-level records.

Source Files

  • scripts/gumroad_status.py owns snapshot, date window resolution, read-only command construction, report normalization, markdown rendering, and write_report().
  • agents/gumroad-status-analyst.md consumes the latest snapshot.
  • tests/test_gumroad_status.py verifies read-only verbs and buyer email exclusion.
  • research/gumroad-status-latest.md and .json are generated outputs.

Setup Commands

bashpython3 scripts/gumroad_status.py snapshot --output-dir research
python -m unittest tests/test_gumroad_status.py

Optional date window flags can be used when the owner asks for a specific reporting window.

Change Rules For Agents

  • Keep forbidden mutating verbs blocked in command construction.
  • Do not add sale export, buyer-level sale list, refund, ship, publish, product update, or upload commands.
  • Normalize account status, totals, products, top product, sales by product, payouts, and planning guidance.
  • Keep buyer emails and buyer-level sale records out of report objects and markdown.
  • If Gumroad CLI is missing or auth fails, surface the blocker; do not mutate account state to fix it.
  • Keep latest aliases so downstream roles have stable paths.

Verification

Run the unit test. It should prove read-only command lists contain no mutating verbs and that buyer email-like data is not serialized into the normalized report or markdown.

Security Notes

Do not publish private seller account records, buyer emails, buyer ids, private payout details beyond summarized planning fields, CLI auth state, tokens, or local absolute paths.

PR Checklist

  • Command set remains read-only.
  • Date windows validate start before end.
  • Reports exclude buyer-level records.
  • Latest snapshot paths are stable.
  • Planning guidance avoids overclaiming low-volume sales.